On Monday 22 January 2007 17:47, M Harris wrote:

On Monday 22 January 2007 17:26, stevens wrote:

...

10.2 has stopped booting. On powerup, after bios check and the 10.2 splash/grub menu, the startup process stops with a "Resume device (hda2) not found - ignoring" then "Waiting for device /dev/hda1 to appear".

I booted to the install dvd, selected rescue and from the prompt did a e2fsck -nv /dev/hdda1 and everything looked ok. I can mount the volume and everything looks ok. I tried booting with a "noresume" option, but all that did was drop the "Resume device" messaage. The system still dies waiting for hda1.

I do not remember doing anything to break it. What happened?

Your grub phase 1 loader can not find the disk for phase 2...

One of your devices is corrupted (hda1, hda2 ?). You will need to fix it obviously... are you using ext3? ext2? reiserfs?

I hate to even hint at this, but you may have a bad hard drive. :(

Nope, no bad drive but you were right about grub not seeing the drive. DO NOT EVER change the ide driver and forget to change it back. It took a long time to decide that I should actually read the boot info off the screen and figure out that I now had all scsi drives. It was then a simple matter of giving grub the right info so it would boot and, once booted, I changed that damned driver back. Oops! Thanks, all, for the help. Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 24 January 2007 15:08, M Harris wrote:

On Tuesday 23 January 2007 02:30, Stevens wrote:

...

It was then a simple matter of giving grub the right info so it would boot and, once booted, I changed that damned driver back. Oops!

... beauty babe...

What you just experienced is (IMHO) one of the main reasons to use grub... because it can be directed (altered) at bootup. Even though you made an error you were able to correct it easily.... grub(1) other bootloaders(0).

Yes, but many people would say there is another side to the story. (just playing devils advocate here) What if the machine you are working on is remote? and the boot (grub) wasn't set up right? If you try to reboot the machine, you'll never hear from it again until someone comes to the console. (who hopefully knows enough to fix things) The argument is that when you run lilo to do the setup, it checks for all mounted filesystems that it needs and whether there are any errors in the config. Thus you are forewarned about errors. So like everything else in linux-life, there are choices to be made. I use grub myself.... and I don't work on machines remotely. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org