In <4d56a6be.9070...@home.nl>, steef wrote: >with grub2 as bootloader under squeeze i cannot mount other hd's anymore >when independently on the *other* hd' s a bootloader (grub2) in the mbr >is installed. without installing grub2 in the mbr of a sata-hd the hd on >which i am mounting *does* recognize the other hd *with the exception of >(old) ata hd's.
GRUB (both 1 and 2) care very little about what your OS calls disks. They have their own naming scheme that they use to locate files and/or block lists. They will pass arbitrary strings set by you to your kernel so that it can find a root device or other devices. When installing the boot sector, GRUB cares a little bit, since it has to use OS routines to access the disk, but that's about it. The Linux kernel in Squeeze renames a lot of devices, particularly block devices, so names like /dev/sdb and /dev/hdc shouldn't be used anymore. These names are based on the order the kernel discovers the device and what subsystem is used to handle it. Disk discovery used to be a serial, deterministic, synchronous process; it is now a parallel, non-deterministic, asynchronous process. This means these device names might change from boot to boot, even if the hardware layout does not change. Also, PATA devices used be to handled by the IDE subsystem and assigned names under /dev/hd*; now, they are handled by the SCSI/SATA subsystem and assigned names used /dev/sd*. >my question: what do i miss if anything? or is this normal for the new >grub? is there anything to do about this? has this got to do with >UUID-numbers? Read the Squeeze release notes. There are instructions there for what tasks to perform before upgrade so that your system cleanly reboots. There are also instructions for what you failed to prepare and your system no longer boots after the upgrade. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
signature.asc
Description: This is a digitally signed message part.
