I used to get the same thing (Debian 2.0) on the first disk access after my PC went into suspended mode. I thought it was the powersave features of the bios but I didn't have the correct utilities to turn it off. (Too lazy to download them)
On a long shot I used the utility hdparm to turn off the spindown of my harddisk (see: man hdpram) and the problem disappeared. P.S. I also took smail out on the mail cron-tab at the same time as this was the software that accessed the disk every 20mins keeping the PC out of suspend. Cheers David -----Original Message----- From: EXT Alvin Oga [mailto:[EMAIL PROTECTED] Sent: 17. August 1999 09:05 To: [EMAIL PROTECTED] Subject: Re: Kernel panic! hi > VFS: cannot open root device 03:01 > Kernel panic: VFS: Unable to mount root fs on 03:01 i get the same silly error when I tried 2.2.10 on my rh-6.0 box... ( that is /dev/hda1 ) i gave up trying to find out why....and just reverted back to 2.2.5-15 from rh... will try again later... have fun alvin > What does this message mean?? The kernel booted from /dev/hda1 so why can't it > mount the root partition now? I've tried giving Linux the different > combinations of the "root=..." parameter but it doesn't seem to work. > > Does it matter which version of LILO I use to install the boot sector?? > This system is running kernel 2.2.10 (custom build) and most packages are from > potato. Due to some problems I had to use an older (slink) version of LILO -- > will this screw it up? It seemed to be fine when I booted this same HD on my > other machine (with the LILO setup for the other machine, of course). > > Also, if LILO is the cause of the problem, how would I run a glibc2.1 version > of LILO from a slink rescue disk??? I don't have a potato boot disk handy... > -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
