Re: [ARMedslack] Initrd fails to mount rootfs
But wouldn't it be a better solution to use the standard kernel parameters for the uinitrd, too? from Documentation/kernel-parameters.txt: rootdelay=[KNL] Delay (in seconds) to pause before attempting to mount the root filesystem rootfstype= [KNL] Set root filesystem type rootwait[KNL] Wait (indefinitely) for root device to show up. Useful for devices that are detected asynchronously (e.g. USB and MMC devices). Yes it would. I'll patch the init script to accept both parameters. -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Initrd fails to mount rootfs
When I had a similar problem myself, I unpacked the kirkwood's initrd and put in the classic print statements into the init script to find out where it was broken. I've built my own kernel now (same version like 14.0 and based on your config). I've just added the needed drivers to the kernel (USB, SCSI disk, some filesystems) so I can boot without initrd and everything is ok now. Which modules did you add? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Initrd fails to mount rootfs
The fact that it worked with 13.37 doesn't really mean a lot, to be honest. 13.37 had a different version of busybox, a different version of udev, a different kernel; most likely containted a different set of modules. Yes, of course. Just wanted to make sure that everything else is ok and I already had it running with 13.37 some time ago. So I gave it a test run. When I had a similar problem myself, I unpacked the kirkwood's initrd and put in the classic print statements into the init script to find out where it was broken. I've built my own kernel now (same version like 14.0 and based on your config). I've just added the needed drivers to the kernel (USB, SCSI disk, some filesystems) so I can boot without initrd and everything is ok now. -- Thorsten Mühlfelder Salix OS: www.salixos.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Initrd fails to mount rootfs
Hi, I've reactivated my Seagate Dockstar, that was lying around in my cupboard for some month. I did the following: 1. reinstalled Doozans U-Boot to have a clean system to start 2. prepared an USB stick with sda1=boot, sda2=swap, sda3=rootfs 3. untared the Slackware ARM minirootfs to the correct places on the USB stick (slack-14.0-miniroot_27Sep12.tar.xz) 4. changed some U-Boot settings to match my USB stick (rootfs=sda3, ext4) But while booting the initrd system fails to mount the rootfs. You can find a complete log here: http://pastebin.com/XLyCFiGV IMHO the relevant part: mount: mounting /dev/sda3 on /mnt failed: Invalid argument ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead. You can try to fix it. Type 'exit' when things are done. /bin/sh: can't access tty; job control turned off You can see in the log that the partitions already appear about 5 seconds before the mount attempt and actually it is possible to mount the partition by hand: / # mount -o ro -t ext4 /dev/sda3 /mnt [ 755.989044] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) Any ideas? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Initrd fails to mount rootfs
On 30 November 2012 13:03, Thorsten Mühlfelder thenk...@salixos.org wrote: 4. changed some U-Boot settings to match my USB stick (rootfs=sda3, ext4) I am not familiar with that device but shouldn't you add rootwait ? ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Initrd fails to mount rootfs
But while booting the initrd system fails to mount the rootfs. You can find a complete log here: http://pastebin.com/XLyCFiGV You have four partitions not 3. What is on /dev/sda4? Is your /etc/fstab setup? You have a root shell there - can you share what you have done to investigate it? It may be obvious what's happened. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Initrd fails to mount rootfs
But while booting the initrd system fails to mount the rootfs. You can find a complete log here: http://pastebin.com/XLyCFiGV IMHO the relevant part: mount: mounting /dev/sda3 on /mnt failed: Invalid argument ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead. You can try to fix it. Type 'exit' when things are done. /bin/sh: can't access tty; job control turned off Same configuration with kernel and uinitrd from 13.37 (Linux 2.6.38.4-kirkwood) boots fine. -- Thorsten Mühlfelder Salix OS: www.salixos.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
