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