Re: BUSY BOX after boot attempt..
i just come across this problem 2 days ago. in my case, it is actually
the udev problem. check if there is any error saying udevd failed etc.
Even after successfully booting. i have problem with my eth0 not
working (renamed to eth1 by then new udev)..
to fix it, i do apt-get update then apt-get upgrade.
apt will take the rest. i think getting the new udevd working is what the new
kernel need to work..
On 9/10/08, Andrei Popescu <andreimpopescu@gmail.com> wrote:
> On Tue,09.Sep.08, 16:00:11, Jack Schneider wrote:
>>
>>
>> -- Hi, all
>>
>> I created my own problem. I think!
>> I have a dual boot Dell M60 laptop. Running Lenny, linux kernel
>> 2.6.26-1-686. I have/had a small primary (hda3) as /boot.
>> A larger logical (hda2) with / (hda5) and /home (hda6) + Swap (hda7).
>> hda1 is XP.
>> I used GRML 1.1 iso and gparted to "resize/move" /boot to 5X intial
>> size. because with kernel changes, I had low disk space errors. All
>> seemed to go well. No errors. When I rebooted back to lenny on hdd I
>> get the BusyBox prompt. I get the GRUB window OK. I see what looks like
>> errors as follows,
>> Mount: No such file or directory. (Three times)
>> Target filesystem doesn't have /sbin/init
>> No init found, Try parsing init= bootarg
>>
>> I don't know where to go next...
>
> I've had cases where changes in partitioning has changed the partition
> numbers. Boot your GRML and check what the correct numbers are. In case
> of any doubt use labels.
>
> Regards,
> Andrei
> --
> If you can't explain it simply, you don't understand it well enough.
> (Albert Einstein)
>
Reply to: