Re: Now won't boot (was: Re: Squeeze assembles one RAID array, at boot but not the other
On Mon, Jan 7, 2013 at 1:44 PM, Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> On Mon, 07 Jan 2013 11:20:45 -0700, Bob Proulx wrote:
>> Hendrik Boom wrote:
>>>
>>> Won't boot. Gets stick at the initramfs prompt after complaining
>>> that it can't run /sbin/init
>>>
>>> I look with ls, and discover that /sbin exists, bit is totally
>>> empty. that seems a good reason to be unable to run /sbin/init.
>>
>> Does seem to be a good reason. I can't remember what is in the bin
>> directories of an initrd bootstrapping image. Pretty sure there is at
>> least something in /sbin though. And noting that for the most part I
>> think you will be working out of a busybox shell which is used to
>> reduce the amount of file system storage space needed in that early
>> boot time environment.
>
> Would it really be complaining about missing /sbin/init on the initrd
> ramdisk, or about /sbin/init being missing on the real root partition,
> which could be caused by not having mounted it yet?
There isn't a "/sbin/init" in the initramfs. There's "/init", a shell script.
You've reached the point where the initramfs expects the root fs to
have been moved. It seems to have failed but I don't understand why
there's an empty "/sbin" rather than no "/sbin".
Reply to: