Can't boot reiser4

MartinZ · 2006-02-05 14:27:15

I killed some time trying to switch my system from ext3 to reiser4 following the Reiser4FShowto, but still can't boot my system this way.
So i decided to ask for some help :?

Here's what i did:
1.- I'm using kernel26archck 2.6.15.archck3-1, libaal 1.0.5-2 and reiser4progs 1.0.5-2
2.- I migrated fom grub to lilo, as suggested in the wiki
3.- I created a reiser4 partition. This is the structure of my system:

/dev/hda3              4806936   1987760   2574988  44% / (ext3)
/dev/hdb5              4032220   2061008   1807352  54% /var (ext3)
none                    111640         0    111640   0% /dev/shm
tmpfs                   111640        16    111624   1% /tmp
/dev/hda2                31109      9770     19733  34% /boot (ext2)
/dev/hdb3             33405652  21216864  10831296  67% /home (ext3)
/dev/hda4              9532908   2538580   6994328  27% /reiser4 (Reiser4)

4.- I copied everything but /home in the reiser4 partition (that is /boot, / and /var) with the following script:

# Copy the system
cp -a /bin /reiser4
cp -a /boot /reiser4
cp -a /etc /reiser4
cp -a /lib /reiser4
cp -a /opt /reiser4
cp -a /root /reiser4
cp -a /sbin /reiser4
cp -a /tmp /reiser4
cp -a /usr /reiser4
cp -a /var /reiser4

# Restore Backup
#cp -a /backup/home /reiser4 --> i don't want to touch /home until i'm sure about reiser4

#Mount points (check you fstab file)
mkdir /reiser4/mnt
mkdir /reiser4/mnt/cd
mkdir /reiser4/mnt/dvd
mkdir /reiser4/mnt/fl
mkdir /reiser4/mnt/usb
mkdir /reiser4/mnt/d

# Create system directories
mkdir /reiser4/sys
mkdir /reiser4/proc
mkdir /reiser4/dev

#Migrate Udev
mknod /reiser4/dev/console c 5 1
mknod -m 666 /reiser4/dev/null c 1 3
mknod -m 666 /reiser4/dev/zero c 1 5

5.- This is my /etc/lilo.conf:

#
# /etc/lilo.conf
#

boot=/dev/hda
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80

default=Windows
timeout=50
lba32
bitmap = /boot/arch-boot.bmp
bmp-table = 120p,173p,1,15,17
bmp-colors = 80,,0;255,,0
bmp-timer = 254p,432p,255,107,0
prompt

image=/boot/vmlinuz26archck
        label=Arch
        root=/dev/hda3
        append="video=vesafb:1024x768-24@56,ywrap,mtrr splash=verbose,theme:darch console=tty1"
        initrd=/boot/initramfs-2.6.15-archck.img
        read-only

image=/boot/vmlinuz26archck
        label=Arch4
        root=/dev/hda4
        append="video=vesafb:1024x768-24@56,ywrap,mtrr splash=verbose,theme:darch console=tty1"
        initrd=/boot/initramfs-2.6.15-archck.img
        read-only

other=/dev/hda1
        label=Windows

6.- This is /reiser/etc/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
tmpfs           /tmp            tmpfs   defaults                0       0

/dev/cdrom      /mnt/cd         iso9660 ro,user,noauto,unhide   0       0
/dev/dvd        /mnt/dvd        auto    ro,user,noauto,unhide   0       0
/dev/fd0        /mnt/fl         vfat    user,noauto             0       0
/dev/sda1       /mnt/usb        vfat    defaults,user,noauto,rw 0       0
/dev/hdb2       /mnt/d          vfat    defaults,user,noauto,rw 0       0

/dev/hdb1 swap swap defaults 0 0
/dev/hda4 / reiser4 defaults 0 1
/dev/hdb3 /home ext3 defaults 0 1

7.- And this is my /etc/mkinitrams.conf:

# Disable whole subsystems by setting to "1"
REMOVE_IDE=
REMOVE_SCSI=1
REMOVE_SATA=1
REMOVE_CDROM=1
REMOVE_USB=1
REMOVE_FW=1
REMOVE_RAID=1
REMOVE_DM=1
REMOVE_FS=

# Enable auto-detection of HOSTCONTROLlER and FILESYSTEMS (set to "1")
#   (NOTE: This is still experimental, so it is disabled by default)
AUTODETECT=1

# Add a theme to enable fbsplash
FBSPLASH_THEME=darch
# Resolution to use, 1024x768 will be used if left blank. Format is '1024x768'
FBSPLASH_RES=1024x768

# Custom DSDT support can be included if you include the FULL path to the DSDT file here
# If left empty, it will not be included. If unsure, leave empty.
DSDT=

# Define which modules are needed by adding "moduleX moduleY"
# If left empty, all modules are included if they are not disabled above
HOSTCONTROLLER_IDE="generic sis5513"
HOSTCONTROLLER_SCSI=
HOSTCONTROLLER_SATA=
HOSTCONTROLLER_USB=
FILESYSTEMS="ext3 reiser4"

# Number of seconds to wait for USB devices to settle
USB_TIMEOUT=5

# If you have an encrypted root filesystem, set it here (eg, /dev/hda4)
CRYPT_DEVICE=

# If you use software RAID for your root device then list all the devices
# that belong to your root array here.  If your root RAID device is
# something other than md0, then change the RAID_ROOT_ARRAY setting.
#    eg, RAID_ROOT_DEVICES="/dev/hda3 /dev/hdc3"
RAID_ROOT_ARRAY="md0"
RAID_ROOT_DEVICES=

# Define additional modules here
ADD_MODULE=
REMOVE_MODULE=

However, when i try to boot into the reiser4 partition i get a kernel panic, with the following lines preceding it:

VFS: can't find an ext2 filesystem on dev hda4
mount: Mounting /dev/root on /new_root failed: Invalid argument
pivot_root: pivot_root: No such file or directory
chroot: cannot execute /bin/sh: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

Sorry i didn't get the whole message, i just copied it by hand. Of course i may write everything if needed

Thanks in advance,
Martin

shadowhand · 2006-02-05 23:13:28

mkdir /reiser4/initrd

MartinZ · 2006-02-06 02:57:35

shadowhand wrote:

mkdir /reiser4/initrd

Thanks for the answer shadowhand! I don't really know how this directory may solve my problem, but I faithfully tried it. Unfortunelly it didn't work

iphitus · 2006-02-06 05:59:26

It cant mount your root filesystem, and thus, it cannot execute init. I will add more detailed error messages to the next release of mkinitramfs.

From what did you create your reiser4 partition? You may have created it from a liveCD with an out-dated reiser4.

iphitus

MartinZ · 2006-02-07 03:09:30

Nope. I actually made it from my Arch system and ran the script i already posted.
I used a self-build Archie (I guess is up-to-date, i made it about 2 months ago) just to be sure everything was fine when i found that the created system couldn't boot.

I still believe this problem is my fault. I'm sure i did something wrong, but can't find what. :?:

However, i switched /home and /var to reiser4 and runs like a charm, I'm pretty happy with this filesystem

Thanks for the reply iphitus, i think Arch community rocks.

pikass · 2006-02-12 09:28:35

I second this problem with archck. Custom build kernel works.

Back2Cali · 2006-04-23 15:13:42

I've got the exact same problem here. I've build a costum kernel and a initramfs by doing exactly what is mentioned at the wiki. But the system won't boot using the initramfs. When creating an initrd file the system works fine.
So is there anything new on this one? Is there a way to create a initramfs that will boot up using reiser4 (as built in Kernel Option).

Thanks!

Infinite · 2006-04-23 15:42:14

Works fine here , I have two reiser4 partitions 8)
I'm using the -beyond kernel (+archck and 2.6.17-1-3).

Back2Cali · 2006-04-23 16:21:10

Well, I'm also using the beyond patchset on my costum Kernel. I have converted all my partitions to reiser4 except /boot which is still ext3. But even if I create a full initramfs it gives me a Kernel panic. So maybe you could tell me what the problem is or what I may have done wrong?
Is there something I have to take care of when configuring the Kernel or what? I'm using a PKGBUILD to create the Kernel which I copied together from all the suggestions from the wiki. Works fine for me. The only thing is, that it creates an initrd instead of an initramfs when I'm installing the Kernel. So could this be the answer to my question?

iphitus · 2006-04-24 10:29:47

Yeah, it's a bug in initramfs.

it uses fsck to detect the partition type, however fsck does not recognise reiser4.

tpowa said there's issues with letting the kernel detect the filesystem, which means I'll probably just end up having the kernel try and mount it as a reiser4, and if that fails, then falling back onto the fsck detection for everyone else. Dirty, but should work until the new setup comes through.

James

MartinZ · 2006-04-24 22:56:34

So, you mean we have to wait until you fix the problem to boot from reiser4?

Arch Linux

#1 2006-02-05 14:27:15

Can't boot reiser4

#2 2006-02-05 23:13:28

Re: Can't boot reiser4

#3 2006-02-06 02:57:35

Re: Can't boot reiser4

#4 2006-02-06 05:59:26

Re: Can't boot reiser4

#5 2006-02-07 03:09:30

Re: Can't boot reiser4

#6 2006-02-12 09:28:35

Re: Can't boot reiser4

#7 2006-04-23 15:13:42

Re: Can't boot reiser4

#8 2006-04-23 15:42:14

Re: Can't boot reiser4

#9 2006-04-23 16:21:10

Re: Can't boot reiser4

#10 2006-04-24 10:29:47

Re: Can't boot reiser4

#11 2006-04-24 22:56:34

Re: Can't boot reiser4

Board footer