LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   No root device found on boot up (http://www.linuxquestions.org/questions/linux-software-2/no-root-device-found-on-boot-up-538220/)

treydock 03-17-2007 02:30 AM

No root device found on boot up
 
I have been getting this error message for two days now. The only way I can get into my system is using the install disk.

resume device /dev/sdc1 not found (ignoring)
Waiting for device /dev/sdc2 to appear .... not found -- exiting to /bin/sh


I've tried reinstalling opensuse 4 times, tried repair 4 times , I wrote zero to all my hard drives and tried fresh install , always get the same error. It all started when I did an update which included a kernel update. No idea how it's still effecting my system since I've erased and tried to start fresh. I run RAID 10 , hardware and am completely out of ideas. I've searched forums , I even found the bug solution on Norton's site but that did not work for me.

Please help :)
Thank You

GrapefruiTgirl 03-17-2007 12:52 PM

Is your root folder located on a RAID drive?
I stand to be corrected, but I don't think that works.
Perhaps posting the contents of your /etc/fstab file would help someone diagnose the issue?
Another possibility is that the kernel module needed to access the RAID drive is not compiled in statically, but rather as a module.
What sort of kernel upgrade was it?

treydock 03-17-2007 11:54 PM

Yes my entire file system is on the RAID 10 array. I know it works , I had the system running for about a month with no problems

The update I did was through Yast. I did all the security updates and I believe the kernel was in that list. I terned off my computer , later turned it on and since I have not been able to boot without installation disk.

Currently doing my 5th or so install hoping something will work.

My file system was

/dev/sdc1 - /boot

/dev/sdc2 - /root

/dev/sdc3 - /home

/dev/sdc4 - swap

The weird thing is , I've done numerous fresh installs. I wrote all zeros to my disks then did another install . I've customized and compiled latest kernel, and everything gives the same result. I have no idea or can't even image why suddenly my computer would stop reading my partitions. I always have them the same ... /boot first 80mb , root in this case was 150gb home was 250gb and swap 2gb.

Any advice or help is very much appreciated.

Once this installation finishes , if it still isn't working I'll post as much relevant data I can come up with.

Thanks

jay73 03-18-2007 12:10 AM

The error messages appear to indicate that your root partition is not on the expected disk. I had a similar issue only a few weeks ago. For some strange reason, the install DVD and the installed OS read the disk order differently so that Suse thought of its disk as sdb whereas the intaller showed it as sdc. As GRUB pointed to sdc, it couldn't find the root partition and so it gave up with precisely the kind of error you're seeing on your own system. I would suggest having a look at your GRUB and /etc/fstab.

treydock 03-18-2007 12:54 AM

Here is my /etc/fstab

Code:

/dev/sdc2            /                    ext3      acl,user_xattr        1 1
/dev/sdc3            /home                ext3      acl,user_xattr        1 2
/dev/sdc1            swap                swap      defaults              0 0
proc                /proc                proc      defaults              0 0
sysfs                /sys                sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts              /dev/pts            devpts    mode=0620,gid=5      0 0
/dev/fd0            /media/floppy        auto      noauto,user,sync      0 0

grub.conf

Code:

setup --stage2=/boot/grub/stage2 (hd0,1) (hd0,1)
quit

/boot/grub/menu.lst

Code:

# Modified by YaST2. Last modification on Sun Mar 18 00:44:48 CDT 2007
default 0
timeout 8
gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sdc2 vga=0x31a resume=/dev/sdc1 splash=silent showopts
    initrd /boot/initrd-2.6.18.2-34-default

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
    rootnoverify (hd0,0)
    chainloader (fd0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 10.2
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sdc2 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3
    initrd /boot/initrd-2.6.18.2-34-default

my /boot/grub/device.map

Code:

(fd0)        /dev/fd0
(hd0)        /dev/sdc

I am at a lost. the only thing I think could be wrong is the hd(0,0) , does that work with RAID systems?

Any ideas or help is more than appreciated...I'm a college undergrad in computer science....so having my main desktop down is a very huge inconvenience.

Thanks

GrapefruiTgirl 03-18-2007 01:27 AM

Well, Jay73 probably has a much better idea than I do, as I use Slackware, LILO, and ATA (non-raid) disks.. But he may be on the right track.
Once you get something booted, if you have the lshw command, type lshw in a console as root and see what it lists as the devices (or check /var/dmesg after booting from CD), to make sure the drives are named as you suspect they should be.
I really can't help much more unfortunately. I know little about RAID or GRUB.
I hope you get it sorted soon, I imagine it is frustrating and weird.
:)

treydock 03-18-2007 01:34 AM

Quote:

Originally Posted by jay73
The error messages appear to indicate that your root partition is not on the expected disk. I had a similar issue only a few weeks ago. For some strange reason, the install DVD and the installed OS read the disk order differently so that Suse thought of its disk as sdb whereas the intaller showed it as sdc. As GRUB pointed to sdc, it couldn't find the root partition and so it gave up with precisely the kind of error you're seeing on your own system. I would suggest having a look at your GRUB and /etc/fstab.


Your advice lead me to the solution, and for that I thank you.

I have SATA optical drives (long story) and had them set as AHCI in bios, so I turned them to IDE. I also noticed GRUB was looking for drives that were sdc..sdc1..sdc2 so on. But I did a list all of /dev folder and found out the only sd* items were sda. So changed hard drive names in grub's menu.lst file and in my /etc/fstab file. Somehow Suse set the drives as sda but told everything to look for sdc. Also found this helpful article.

http://www.intel.com/support/motherb.../CS-025446.htm

It might offer an explanation for what happened , cause I did notice that on some installs it'd ask what to name the USB storage device and some it wouldn't.


Thanks again for your help , hopefully this thread can help others.


All times are GMT -5. The time now is 09:35 AM.