You are not logged in.
I used the guide on the wiki to transfer an existing Arch install over to Reiser4 and since then I get the good ol' "Cannot Find Root Device, Attempted to kill init" kernel panic. The new Reiser4 copy of the system is on a SATA drive a intel controller(what should be sdb2, according to the old copy), and the original copy is on the intel PATA controller (sda). The panic occurs right after it mounts the root partition read only and attempts to pass control to INIT.
My GRUB looks fine to me. By the way, grub still sits on the old copy of the system, on the PATA drive.
# (0) Arch LinuxR4
title Arch LinuxR4
root (hd1,1)
kernel /boot/vmlinuz26mm root=/dev/sdb2 ro rootfstype=reiser4
initrd /boot/kernel26mm.img
# (1) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26mm root=/dev/sda1 ro
initrd /boot/kernel26mm.img
Here is my fstab.
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,unhide 0 0
/dev/dvd /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/fd0 /mnt/fd0 vfat user,noauto 0 0
/dev/sdb2 / reiser4 defaults 0 1
/dev/sda3 swap swap defaults 0 0
/dev/sdb1 /media/disk-1 ntfs-3g defaults 0 1
And after talking to tomkx, I decided to try putting the reiser4 module into the initrd, but to no avail. The error reminds me a lot of the error everyone was getting with Intel chipsets and stock kernels when upgrading to 2.6.19+ from a lower kernel.
Last edited by GiGaHuRtZ (2007-03-31 02:21:24)
Offline
I assume, you compiled a new kernel with Reiser4 support before moving?
Offline
I used the kernel26mm package in the repositories, which has Reiser4 support.
Offline
Make sure you have the hook for Reiser4 in /etc/mkinitcpio.conf and recreate your kernel26mm.img.
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
Make sure you have the hook for Reiser4 in /etc/mkinitcpio.conf and recreate your kernel26mm.img.
Thanks for the suggestion, but I have already done that, no effect.
Offline
From mkinitcpio wiki page (filesystems HOOK):
This will detect the filesystem type at runtime, load the module and pass it to kinit. NOTE: it will NOT detect reiser4, it must be added to modules list.
http://wiki.archlinux.org/index.php/Mki … _the_HOOKS
Last edited by SiD (2007-04-04 09:58:14)
Offline
From mkinitcpio wiki page (filesystems HOOK):
This will detect the filesystem type at runtime, load the module and pass it to kinit. NOTE: it will NOT detect reiser4, it must be added to modules list.
Right, I've already done that. The kernel loads and mounts the root FS fine as read only, and then when it goes to pass control to init (right before it checks the disk, hence why the kernel mounts read only) it panics.
Last edited by GiGaHuRtZ (2007-04-04 17:27:08)
Offline
Sorry but I'm fresh out of ideas.
BTW, did you know that the creator of ReiserFS (Hanz Reiser) is being held for suspicion of murdering his wife and that the ReiserFS project is kinda in limbo?
That's one of the reasons the big guys like Suse are not using it for their root fs anymore and have switched over to ext3.
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
Yes I know that, but I don't think his sentencing will effect Reiser4 either way, it's open source, and there are more people at NameSys besides Hans, to continue the project.
Offline
since using ReiserFS I've had to rebuild the tree like 3 times, I don't ever remember having to do this with ext3.
Is there a way to convert back to ext3 without having to reformat the disk?
Offline
Unfortunately there isn't. You have to tar up your reiserfs partition to some other storage, reformat the partition to ext3 and untar.
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline