Arch Linux

arew264

Member

From: Friendswood, Texas, US

Registered: 2006-07-01

Posts: 394

Website

Changing Root Filesystem Causes Much Pain

I've just gone through a massive repartitioning, with the net result being this:
/:
     was: /dev/sda2 reiserfs
     is: /dev/sda4 ext3

/home:
     was: /dev/sda3 reiserfs
     is: /dev/sda3 ext3

/boot:
    was and still is: /dev/sda1 ext2

I can boot from the Arch installation disk using root=/dev/sda4, so that's all good.
The problem is getting my existing installation to boot. Even if I edit the boot entry in GRUB so that instead of "root=/dev/sda2", I have "root=/dev/sda4", the boot fails with:

init: Cannot open root device sda4(8,4)
init: init not found!
kernel panic - not syncing: Attempted to kill init!

Do I need to regenerate my initrd.img or something? I can't using the Arch install disk because it doesn't seem to support ext2...

arew264

Member

From: Friendswood, Texas, US

Registered: 2006-07-01

Posts: 394

Website

Re: Changing Root Filesystem Causes Much Pain

THANK YOU DEVELOPERS!!!

I just booted the fallback image, and that had all the drivers I need for booting to work. I'll be regenerating my initrd as soon as I figure out what to change.

bender02

Member

From: UK

Registered: 2007-02-04

Posts: 1,328

Re: Changing Root Filesystem Causes Much Pain

You probably don't need to change anything, just regenerate. It's because the 'autodetect' hook that you probably have in the HOOKS array in mkinitcpio.conf causes only modules that are needed to be included in the initramfs. Last time you regenerated, it was reiserfs module; when you regenerate now, it should include ext3 automatically.

arew264

Member

From: Friendswood, Texas, US

Registered: 2006-07-01

Posts: 394

Website

Re: Changing Root Filesystem Causes Much Pain

Yep, that was the case. I regenerated and rebooted and now everything's back to normal, and I'm off of ReiserFS.