{solved} kernel panic - cannot open root device

sinister99 · 2007-09-08 21:55:50

I got a kernel panic after swapping a couple hard drives, which is nothing new to me. I chrooted into my system to update and re-run lilo, but my root drive is still sde1, so I didn't need to update anything. I don't know what to do since I've always just changed my drive letter before. The last few lines before the panic are below

:: Initramfs Completed - control passing to kinit
IP-Confi: no devices to configure
Waiting 0 s before mounting root device...
kinit: cannot open root device dev(8,1)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

Last edited by sinister99 (2007-09-09 17:54:21)

fwojciec · 2007-09-08 22:11:40

What file system do you have on dev(8,1)?

sinister99 · 2007-09-08 23:16:49

fwojciec wrote:

What file system do you have on dev(8,1)?

reiserfs, the filesystem should be clean.

fwojciec · 2007-09-08 23:22:26

Try adding rootfstype=reiserfs to your kernel command line in grub/lilo. If that will let you boot you'll need to regenerate kernel images with mkinitcpio (or you can just re-install the kernel) _after_ editing /etc/mkinitcpio.conf and adding "reiserfs" to modules section.

sinister99 · 2007-09-09 01:21:05

I'm starting to get somewhere, but something odd is happening.

When I boot into the rescue system and chroot into my system, my boot drive is sde1. I verified my lilo.conf was correct and ran lilo and rebooted.

When I boot my system, sde1 is referencing a different drive (the on screen output has the wrong filesystem)

So my question is while I am chrooted, how do I put the correct drive in when it chanes when I boot my system?

erm67 · 2007-09-09 09:02:52

sinister99 wrote:

I'm starting to get somewhere, but something odd is happening.
When I boot into the rescue system and chroot into my system, my boot drive is sde1. I verified my lilo.conf was correct and ran lilo and rebooted.
When I boot my system, sde1 is referencing a different drive (the on screen output has the wrong filesystem)
So my question is while I am chrooted, how do I put the correct drive in when it chanes when I boot my system?

You can use in lilo.conf
append='root=/dev/sdX1'
But first you have to find out the real name of the root device or use Persistent block device naming (better)
BTW dev(8,1) is sda1

sinister99 · 2007-09-09 17:53:52

erm67 wrote:

sinister99 wrote:
I'm starting to get somewhere, but something odd is happening.
When I boot into the rescue system and chroot into my system, my boot drive is sde1. I verified my lilo.conf was correct and ran lilo and rebooted.
When I boot my system, sde1 is referencing a different drive (the on screen output has the wrong filesystem)
So my question is while I am chrooted, how do I put the correct drive in when it chanes when I boot my system?
You can use in lilo.conf
append='root=/dev/sdX1'
But first you have to find out the real name of the root device or use Persistent block device naming (better)
BTW dev(8,1) is sda1

That persistant naming was exactly what I needed. Thanks.

Arch Linux

#1 2007-09-08 21:55:50

{solved} kernel panic - cannot open root device

#2 2007-09-08 22:11:40

Re: {solved} kernel panic - cannot open root device

#3 2007-09-08 23:16:49

Re: {solved} kernel panic - cannot open root device

#4 2007-09-08 23:22:26

Re: {solved} kernel panic - cannot open root device

#5 2007-09-09 01:21:05

Re: {solved} kernel panic - cannot open root device

#6 2007-09-09 09:02:52

Re: {solved} kernel panic - cannot open root device

#7 2007-09-09 17:53:52

Re: {solved} kernel panic - cannot open root device

Board footer