On Tue, Aug 17, 2010 at 7:56 PM, Wayne E. Van Loon Sr. <[email protected]>wrote:Maybe you can tell me. After a SuSE screen to choose what mode to boot,
> Open SuSE 11.1 > Open SuSE 11.1 (Failsafe) etc... > > it starts booting, switches to a screen with a "progress bar". The > progress bar is stuck on the left side and after a couple seconds, a > console type black and white screen appears with the last lines reading: > > Could not find > /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9CUM7063-part2. > Want me to fall back to /dev/sda2? (Y/n) > > That looks like your problem. The by-id disk name may not be the same from system to system and so GRUB can't find the disk. If you wanted to fix this you should switch to uuids. The uuids are in /dev/disk/by-uuid/. If you go to that directory and do ls -altr you will see which uuid is associated with which partition. > Obviously it found the disk, the only disk on the machines in both > cases, and loaded some sort of boot menu. Why it could (would) not find > (mount) the / partition seems to me to be the result of some sort of > The same problem that grub has, fstab also has. You should use uuids in fstab to indicate which partitions to mount where. For example here is my / partition in /etc/fstab UUID=e0dcbbf3-a4fa-4a94-9ee0-c0466aa6fb9d / jfs errors=remount-ro 0 1 over complication. I have been using Linux since 1995 and OpenSuSE 11.1 > is the first distribution I have encountered that would only boot on the > machine it was originally installed on. > > The older bioses were simpler. The boot disk was usually /dev/hda and this was pretty consistent from bios to bios. The newer motherboards are more complex and hence the more complexity in grub and fstab. Bill _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
