After installing Suse 10.2 on a Raid 5 Rocketraid 1740 on initial boot receive error Kernel panic - not syncing: VGS: Unable to mount root fs on unknown-block(8,2)

After installing Suse 10.2 on a Raid 5 Rocketraid 1740 on initial boot receive error Kernel panic - not syncing: VGS: Unable to mount root fs on unknown-block(8,2)

I am using LiLO as the loader, 4 SATA HD 500 GB each on Raid 5, during installation process all partitions where done as recomended by the installation utility.  Its reading from HD because I see load various drivers.

This is the few lines before the error and the error;

md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Cannot open root device "802" or unkown-block(8,2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VGS: Unable to mount root fs on unknown-block(8,2)

gatekeeperprAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
gatekeeperprConnect With a Mentor Author Commented:
After multiple installs and test have found the problem, for this SATA IDE RAID controller to work properly the /boot has to be installed in sda1 partition.
0
 
rokovCommented:
Please post your lilo.conf or grub.conf and /etc/fstab.
0
 
gatekeeperprAuthor Commented:
I am not able to access the information, this reboot was the first one after installation but it never completed (I have installed from different media multiple times).  The only this that LILO is doing is showing;

LILO 22.7 Loading oS_10.2....................................
BIOS data check successful then it starts to load multiple drivers like

apm:
audit:
vesafb:
console:
serial:
serial8250:
Floppy drive(s):
serio:
mice:
input:
md:

Then error above.

( I have not written the additional information after the : its just describe version and detected equipment)

0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
rokovCommented:
To get this files you need to boot from livecd (install cd) and mount root (and boot, if separate) partition manually. Then copy this files somewhere (flashdrive, for example).
0
 
gatekeeperprAuthor Commented:
Here is the lilo.conf;
**************************************

# Modified by YaST2. Last modification on Thu Jan 31 22:46:29 UTC 2008
menu-scheme = Wb:kw:Wb:Wb
timeout = 80
lba32
change-rules
reset
read-only
default = oS_10.2
message = /boot/message
boot = /dev/sda2

image = /boot/vmlinuz-2.6.18.2-34-default
###Don't change this comment - YaST2 identifier: Original name: linux###
    label = oS_10.2
    append = "   resume=/dev/sda1 splash=silent showopts"
    vga = 0x31a
    initrd = /boot/initrd-2.6.18.2-34-default
    root = /dev/sda2

image = /boot/vmlinuz-2.6.18.2-34-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
    label = Failsafe
    append = "showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3"
    vga = normal
    initrd = /boot/initrd-2.6.18.2-34-default
    root = /dev/sda2
0
 
gatekeeperprAuthor Commented:
Here is fstab;


/dev/sda2            /                    ext3       acl,user_xattr        1 1
/dev/sda3            /home                ext3       acl,user_xattr        1 2
/dev/sda1            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
~
0
 
rokovConnect With a Mentor Commented:
Looks like it is not related to bootloader configuration...
Maybe the problem is hardware (driver) related? Have you seen kernel messages messages about raid controller and disk detection?

Example from my dmesg:
megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
megasas: 00.00.03.10-rc5 Thu May 17 10:09:32 PDT 2007
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi0 : ioc0: LSI53C1030 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=17
scsi 0:0:0:0: Direct-Access     VMware,  VMware Virtual S 1.0  PQ: 0 ANSI: 2
...
target0:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
...
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
0
All Courses

From novice to tech pro — start learning today.