LinuxQuestions.org - HDDs and kernel panic

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - HDDs and kernel panic (https://www.linuxquestions.org/questions/linux-hardware-18/hdds-and-kernel-panic-710772/)

HDDs and kernel panic

Hi... these are my hdds all are sata

320G file system
500G mp3s :P
160G empty

So.. look at this.. the 2 first are connected always and the system runs great...When im gonna connect the 160G hdd it returns this error at boot time

Quote:

md: Autodetecting RAID arrays
md: Scanned 0 and added 0 devices
md: autorun...
md: ...autorun DONE
VFD: Cannot open root device "802" or unkown-block(8,2)
please appent a correct "root=" boot option; here
are the available partitions

a list with my partitions

Kernel panic - not syncing : VFS:unable to mount root FS on unknown-block(8,2)

Hmm.. any ideas...on what goes wrong? Where to put the right root= ?

Are any of these drives removable?

Nope ... there are all inside...the tower...:s When i disconnect the 160G the system boots great...

Any ideas guyz ??? What may cause this problem ?

So, the SATA controllers on your motherboard, do some of them Support RAID ?

is there a setting in the BIOS to disable the RAID mode on that controller ?

Is there a Different connector on the motherboard you can use that does not have RAID support ?

Looks like the new drive is remapping the others. There are a couple of things you can try. Could try booting with a live cd and running fdisk and checking that the new drive does not have a boot partition enabled on it and also determine the drive order then modify the menu.lst file to the appropriate drive for you linux system.

Hi,

How about posting system information. Motherboard manufacture, model and version would certainly aid in diagnosing.

This is my mobo...

Quote:

http://www3.dealtime.com/xPF-ASUS-As...p-to-DDR400-mi

I ll now try to disable the raid from bios...

Hmmm...listen this...

i disconnect the third hdd (160g) and when the system open i connect it. in fdisk -l gives me this back:

Quote:

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x06706357

Device Boot Start End Blocks Id System
/dev/sda1 1 124 995998+ 82 Linux swap
/dev/sda2 125 1369 10000462+ 83 Linux
/dev/sda3 1370 38913 301572180 8e Linux LVM

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x076f5e24

Device Boot Start End Blocks Id System
/dev/sdb1 1 60801 488384001 83 Linux

Disk /dev/sdc: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdc doesn't contain a valid partition table

I can mount it perfectly...but if i connect it before system start...it returns the kernel panic :( Any ideas...? Also i dont have it in fstab file ..but i don't think that this causes the problem...:s

After this i make a partition in /dev/sdc with cfdisk with type 83

in

Quote:

mount -a

returns this:

Quote:

mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

and in

Quote:

dmesg | tail

returns this:

Quote:

kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
sd 2:0:0:0: [sdc] 320173056 512-byte hardware sectors (163929 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1
VFS: Can't find ext3 filesystem on dev sdc1.
VFS: Can't find ext3 filesystem on dev sdc1

This is my fstab file:

Quote:

/dev/sda1 swap swap defaults 0 0
/dev/sda2 / ext3 defaults 1 1
/dev/slackvg/home /home ext3 defaults 1 2
/dev/slackvg/usr /usr ext3 defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
/dev/sdb1 /media/disk ext3 defaults 1 2
/dev/hdd1 /media/disk-1 ext3 user,rw,exec,sync 0 0
/dev/sdc1 /media/disk-2 ext3 user,rw,exec,sync 0 0

any ideas...now ? :s im confused :S:S

OK so you created an ext3 partition.. Did you format the partition ?

man mkfs

So... after the fdisk and type 83 i give this mfks.ext3 /dev/sdc1. Now i can mount the disk... but only after the system boots...:-s The kernel panic still pop up if the hdd is connected before system's booting..

Ant ideas now ? Why this happen? What the error means ?

Quote:

please append a correct "root=" boot option; here
are the available partitions

Where is the "root=" in which file?

Also something else...When i go to create a file in this hdd says that permission denied...What is wrong in my fstab above..?

So... :) what you think ? Is the problem the raid ? I don't know a lot about this technology (i mean raid)..So.. if you have any idea... on how to disable ...or anything else... let me know... Thanx... ;)

Hi,

Apparently you don't have the bootloader setup properly or you could still have the raid enabled in the BIOS.

Hmm this is the lilo.conf

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 10
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Linux
read-only
# Linux bootable partition config ends

I think that root = is ok...What you say..?Also in the bios i can see the third hdd as master...

Nothing ehh...? :S I can't understand...