PhilE wrote:I'm happy you're making progress - I've never played around with the PARTUUID system. Thanks for sharing your findings.
For the record, the "followkernel" parameter replaces the "ramfsaddr=-1", so you don't need both. Either use the two separate assignments as you had before, or the one initramfs command.
Yeah, I understood your other post. I had tried it with both, with either, trying anything... Thanks.
One thing I'm curious about... this particular card was originally written from the 12/24/2014 Raspbian release IMG. Is it normal to have 3-4 MB of unallocated space at the beginning of the card? I just opened it in gparted and noticed that the boot partition doesn't start at the beginning of the drive. Is this necessary?
Oh well, I'm going to install a fresh image and go from there.
Alright, I tried over and over again to get everything working in a variety of ways using the same old external 80GB Toshiba MK8025GAS hard drive (the enclosure has an adapter/controller named "Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI"). The hard drive was always recognized when I would boot using root=/dev/sda1, but it wasn't mounting early enough no matter what I tried (I even tried rootdelay=100 and boot_delay=100 in cmdline.txt based on another member's posts in the forum). When I would boot up to the microSD root (/dev/mmcblk0p2), I could see that the external hard drive would end up mounting a little too late for it to work (even with those delays). Finally, I tried a different newer external hard drive and that was successful. The newer drive mounted earlier, worked great and did not require any ridiculous tinkering with cmdline.txt.
Everything (initramfs, PARTUUID, UUID, and root on an external hard drive) works. Good stuff.
EDIT: Unfortunately, I was mistaken. Not everything is working. PARTUUID in cmdline.txt, UUID in fstab, and root on an external hard drive will work together, but as soon as I add initramfs to the mix the boot process fails.
- If I use PARTUUID=2EAF42A6-0615-44A9-BB63-E09F80A307FE in cmdline.txt with initramfs commented-out in config.txt, then booting completes successfully.
- If I use use root=/dev/sda1 in cmdline.txt with initramfs enabled in config.txt, then booting also completes successfully.
- If I use use root=/dev/sda1 in cmdline.txt with initramfs commented-out in config.txt, then booting also completes successfully.
- If I use PARTUUID=2EAF42A6-0615-44A9-BB63-E09F80A307FE in cmdline.txt with initramfs enabled in config.txt, then the same failure occurs which I posted about earlier in the thread (Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg.).
Maybe this https://bugs.debian.org/cgi-bin/bugrepo ... bug=762870
explains what I'm seeing?
apt-get install busybox
update-initramfs -u -k `uname -r` -v
NOW, it all works:
initramfs initrd.img-3.18.6-v7+ followkernel
Sorry for getting so far off-topic here. I would not be offended if my posts were moved elsewhere. Thanks again for taking a look.