kernel panic after adding 3rd hard drive?

ssl6 · 2008-08-15 23:24:06

so i picked up s 750gb seagate today, since im running out of storage on my home drive. thought id format it and mount it to my movie folder since thats whats sucking up my space.

after a long hard struggle of running the wires in a clean fashion, dusting out my case, making sure that the drive is plugged in to the port labeled sata 3 so as not to mess with my boot order or anything. i booted it up, only to find a kernel panic when it tries to load root filesystem, whatever that means

to sum it up, ill try to post what i can copy off my other screen

:: loading root filesystem module
Attempting to create root device '/dev/sda3'
/bin/mknod "/dev/root" b 8 3
/init: 1: cannot open /dev/root: no such device or address

waiting for devices to settle...done
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
Waiting 0 s before mounting root device...
kinit: Unable to mount root fs on device dev(8,3)
kinit: init not found!
Kernel panic - not synching: attempted to kill init!

could use some help? i was able to boot it with the sata cable on the new drive disconnected, just plugged it in after i was logged on and mounted it manually, but that doesnt help me in the event that i need to reboot

Last edited by ssl6 (2008-08-15 23:26:13)

ssl6 · 2008-08-16 00:35:28

ok, now im getting that with or without the new drive installed.

is there a way that i can fix that without reloading my system like i just did for my laptop? i don't want to screw something up and wipe everything off my drive

kett · 2008-08-16 01:25:44

I'm not sure how much I can help, but more information is always useful.

That said. Are you using grub or lilo? If so, you could post your configuration file for it.

Also, your /etc/fstab file seems like it would be relevant as well.

ssl6 · 2008-08-16 02:17:10

i dont have anyway of accessing any thing on the drive in my desktop.

basically, after connecting the new drive after startup, formatting, and mounting. i rebooted to see if i would get that error again, which i did. so i had to force it off. so i disconnected the drive and now it gives me the same thing. so i dunno, im probly just going to try and get to a friends tomorrow with a high speed connection reload the system

mclang · 2008-08-17 10:33:24

I have exactly same problem

Except the fallback image works... I'm using grub, and the relevant lines of menu.lst looks like this:

# general configuration:
timeout   5
default   0
color light-blue/black light-cyan/blue

# (0) Arch Linux
title  Arch Linux  [/boot/vmlinuz26]
root   (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 vga=775 ro devfs="nomount"
initrd /kernel26.img

# (1) Fallback
title  Fallback Kernel [/boot/vmlinuz26]
root   (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 vga=775 ro devfs="nomount"
initrd /kernel26-fallback.img

fstab looks following:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
# /etc/fstab: static file system information
none            /dev/pts      devpts  defaults      0      0
none            /dev/shm      tmpfs   defaults      0      0
tmpfs           /tmp          tmpfs   defaults      0      0
usbfs           /proc/bus/usb usbfs   defaults      0      0

/dev/sda1       /boot        ext2     defaults 0 1
/dev/sda2       swap         swap     defaults 0 0
/dev/sda3       /            ext3     defaults 0 1
/dev/sda4       /var         reiserfs defaults 0 0
/dev/sdb1       /home        xfs      defaults 0 0

# fam managed entries:
/dev/hdc                /media/dvdwriter        auto    user,exec,noauto,comment=managed 0 0
/dev/fd0                /media/floppy           auto    user,exec,noauto,comment=managed 0 0

Can mkinitcpio create somehow invalid default kernel image? The 'MODULES/BINARIES/FILES' arrays in mkinitcpio.conf are empty, and the 'HOOKS' look like:

HOOKS="base udev autodetect pata scsi sata filesystems"

Kernel version is 2.6.26.2-1 from (base). What else information would be usefull? Sorry if this issue is solved elsewhere - this thread was the first that came up with the search...

rooloo · 2008-08-17 10:53:51

devfs="nomount"

where did you get that option from? I am not sure, but why would you NOT wanna mount the devives filesystem?

Ramses de Norre · 2008-08-17 10:57:37

Remove that option mentioned above and look into persistent device naming, it simplifies adding hard disks.

ssl6 · 2008-08-17 15:00:11

well, what happened to mine was, instead of formatting my sdg (new drive), a different drive got formatted......sda3.....which was my / partition, so i dunno, im sure i formatted the right one, i used qtparted to do it. but something happened to my main drive anyway.

i reinstalled everything yesterday, its working now mostly. just gotta configure my fstab again for my ntfs drives and get samba up an running again

mclang · 2008-08-17 16:23:33

rooloo wrote:

devfs="nomount"
where did you get that option from? I am not sure, but why would you NOT wanna mount the devives filesystem?

The "nomount" option is given as a tip in my menu.lst file:

# TIP: To use udev, add "devfs=nomount" to your kernel line.

That line was in the basic menu.lst file which got installed when I first installed Arch. I don't know why it was suggested back then, I just followed blindly... I remove that if it is not needed anymore and look into persistent block device naming. Older threads seems to indicate that that is the solution.

Thank You.

Arch Linux

#1 2008-08-15 23:24:06

kernel panic after adding 3rd hard drive?

#2 2008-08-16 00:35:28

Re: kernel panic after adding 3rd hard drive?

#3 2008-08-16 01:25:44

Re: kernel panic after adding 3rd hard drive?

#4 2008-08-16 02:17:10

Re: kernel panic after adding 3rd hard drive?

#5 2008-08-17 10:33:24

Re: kernel panic after adding 3rd hard drive?

#6 2008-08-17 10:53:51

Re: kernel panic after adding 3rd hard drive?

#7 2008-08-17 10:57:37

Re: kernel panic after adding 3rd hard drive?

#8 2008-08-17 15:00:11

Re: kernel panic after adding 3rd hard drive?

#9 2008-08-17 16:23:33

Re: kernel panic after adding 3rd hard drive?

Board footer