You are not logged in.
Hi, could someone kindly help this.
I got the kernel panic with larch5.3 building CD. I didn't get any error messages during the creating. The error message of starting system is in belowing words.
:: Initializing writable layer for union (overlay)
/init: 193: /tfs/system/usr/bin/lzop: not found
/init: 193: /tfs/system/bin/tar not found
:Setting up union file system
unionfs: error accessing lower directory '/tfs/overlay' (error -2)
unionfs: read_super: error while parsing options (err= -2)
:: End of live system set-up
:: Initramfs Completed - control passing to kinit
Kernel panic - not syncing: Attempted to kill init!
Offline
It looks like you are trying to use unionfs - this is not a good idea. Originally larch was based on unionfs, but I haven't tested it for ages and I guess it probably doesn't work. You need to use aufs. If you can't find enough info in the docs, post again.
larch: http://larch.berlios.de
Offline
Hi, gradgrind, Thanks a lot for your answer. Could you let me know which argument for larch to ceate aufs? Thanks.
Offline
You don't need a special argument, you just need to install aufs ( I assume you are trying to larchify an existing system? - if using mklarch aufs needs to be in the 'addepacks' file in the profile).
larch: http://larch.berlios.de
Offline
Hello,
supdaniel
I hope i can help you somehow.
Your post let became me a little bit frightend,
because it could have something to do with larch itself. Mmmh...
Why? Because of the missing tar.
But maybe i could help you a little bit.
As gradgrind mentioned aufs and lzop is needed.
I hope you use larchify otherwise my post is
pointless.
I don`t know how you get to the point,
where you use unionfs, but there is a way to clearify this.
Look at /lib/initcpio/mkinitcpio.conf
There has to be larch2_aufs in it, otherwise edit it.
But it should be the default. I never experienced something else
the last updates.
Greetings
Offline
Hi, paraflu Thanks a lot for your reply. My situation is / mount to /dev/sda3, /boot mount to /dev/sda1, /home mount to /dev/sda4 and swap mount to /dev/sda2. I installed larch5.3 in my home directory /home/supdaniel/larch. I just use simply command ./larchify / to build the livecd and I also added gparted, squashfs-tools, lzop, syslinux, cdrkit packages. Could you kindly let me know how can I create the exiting system correct that make me in trouble for a few days. Thanks.
Offline
You didn't mention aufs - you really must install that. Also larch-live is necessary (from the larch repository). If you are building a cd, you will also want eject. I think, then, './larchify /' should work.
larch: http://larch.berlios.de
Offline
Hi gradgrind, Thanks for your reply. Yes, I have added aufs, eject packages. But it seems still cannot work. Sorry for many troubles.
One think. When I create the iso file, it gives a warning message.
// Build without a profile? [y/N]: y
//
// **********************************************************
//
// ***** Creating live CD from system at ''
//
// This will delete EVERYTHING under ::: /.larch/cd :::
//
// I really mean it ... Are you sure you want to do this?
// **********************************************************
[y/N]: y
WARNING:
You seem to have installed a package containing modules
which aren't compatible with your kernel.
Please check that this won't cause problems.
Maybe you need the corresponding package
for your kernel?
chroot: cannot change root directory to pacman: No such file or directory
Package:
Continue? [y/N]: y
// Kernel version: 2.6.27-ARCH
// -> regenerating kernel dependencies
Using aufs
// copying cd-root to /.larch/cd
// copying kernel from /boot to /.larch/cd/boot/vmlinuz
// ... using vmlinuz26
// calling gen_larch_init to generate the initramfs
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
Offline
Well done, you've found a bug in larch!
But I'm not sure that it's what is causing your problem ...
Could you first look for the modules that are for the wrong kernel (in /lib/modules/ ...) and remove them. Or maybe you have more than one kernel installed? If you can remove them the larch error should not occur - it happens when it is trying to tell you which package supplies the wrong kernel module.
If you can't remove the problem module(s), you can perhaps fix larch (until I get around to updating it). I think you can change line 502 in larch/buildlive:
'chroot ${INSTLDIR}' -> 'chrootx' (without the quotation marks)
EDIT:
Sorry that's wrong, it should be:
'chroot ${INSTLDIR}' -> '${chrootx}' (without the quotation marks)
Last edited by gradgrind (2008-11-13 08:20:25)
larch: http://larch.berlios.de
Offline
Excellent! Thanks a lot. I will try this solution.:)
Offline
What's wrong with unionfs? (The official Arch install cd uses it btw)
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
What's wrong with unionfs? (The official Arch install cd uses it btw)
A few kernel versions back unionfs stopped working. At that point I switched all my attention to aufs. I don't know if unionfs will work with larch now, I haven't tried it. (I suppose if it's being used in the install CD it must work, at least to some extent). There is, however, one big advantage to aufs (in larch) - it allows relatively easy and efficient implementation of an overlay merge (used in session saving), using a feature not supported in unionfs.
larch: http://larch.berlios.de
Offline
Hi, aufs need update with new kernel 2.6.29
Offline