On Mon, Jan 19, 2015 at 6:13 PM, bitlord <bitlord0...@gmail.com> wrote: > On Mon, 19 Jan 2015 13:55:30 -0800 > Mark Knecht <markkne...@gmail.com> wrote: > >> Hi, >> There was an update to stable busybox this weekend choosing version >> 1.23.0 as the new stable version. Since this update, for NEW kernels >> only, I'm unable to assemble my RAID6 root device and therefore the >> kernel won't boot. Has anyone else had similar problems? I've looked >> around for recent posts, etc., but haven't found anything as of yet >> but the gatekeeper in the Gentoo Bugzilla environment won't let me >> file a bug report. >> >> At issue here is assembling the root RAID device. I build the >> initramfs into the kernel for exactly this sort of reason. Other than >> changing a few RAID UUIDs this setup hasn't changed in years. I masked >> 1.23.0, went back to 1.21.0 and that still works for new kernel so it >> appears to be a busybox issue. >> >> My configuration follows. initramfs.config is referenced in my >> kernel config file which then loads initramfs_init_new.sh to do the >> work. The failure is three messages: >> >> /init: line 16: mount: not found >> /init: line 17: mount: not found >> /init: line 18: mount: not found >> > > No RAID here (LUKS(LVM())), but I have custom initramfs, and I see this > problem after update + regenerating initramfs (with new binaries), which > in the end produce a kernel panic ... (I don't know much)) > Older images work fine, I did some "testing" (guessing), and adding > before all those mount ... lines > '/bin/busybox --install -s' > (Which should "install" all symlinks for supported tools?) > That generates a lot of other messages but I was able to boot my > system with new image. >
Hi bitlord, Thanks very much for the ideas. I suspect it's going to get me closer when I can work on this again this evening. I'm going quite slow as it would be really bad if something I do in this area ends up hurting the machine. One idea I had after reading your response was instead of doing the complete '--install -s' maybe I'd add just one line slink /bin/mount busybox 755 0 0 in the main setup file to get the mount command and see if that solves the problem. However your solution is likely better as when I fall into busybox I suspect I'd have everything busybox provides which would be more powerful. Maybe you can add a response to my bug report here? https://bugs.gentoo.org/show_bug.cgi?id=536988 The Jeroen guy who acts as gatekeeper is marking the bug report as invalid because no one else is reporting anything. I think that's pretty bogus so anything you can add would likely be helpful. None the less, thanks for the response. It's made me revisit how this works (at the 10000 foot level) which is good. Cheers, Mark
