Re: 2.6.24-4 kernel not booting
I do not know what caused the issue.
i know that i can boot from linux dvd and go to rescue mode.
No network support.
i can do mounts and stuff. ---just do not know what the next step would be.
mjh
On Tue, Aug 5, 2008 at 6:36 PM, Michael Habashy <mjh2000@gmail.com> wrote:
> i appriciate your help.
> i am not new to linux but i am new to lvm and raid and recovery.
> if you give me some simple steps, i can follow.
> i would really like the help because my main ssystem is down.
> please provide step by step proceedure..to ensure that i get my system
> up and running.
> can you point me to a how-to or something ??
>
> mjh
>
>
> On Tue, Aug 5, 2008 at 6:27 PM, Andrew Sackville-West
> <andrew@farwestbilliards.com> wrote:
>> On Tue, Aug 05, 2008 at 06:09:10PM -0400, Michael Habashy wrote:
>>> can anyone help on this???
>>> I get into a busybox prompt and can not do much.
>>> Can i get a list of procedures on how to recover my system ???
>>> I am using lvm2 on top of raid. (raid1 for boot and raid5 for root and
>>> the rest of my system)
>>> I am able to but with the debian 4.0 dvd and get into rescue mode. I
>>> can then create a directory and mount my /dev/md0 device
>>>
>>> I can see all my files on the boot partition including my kernels
>>> ...all seems okay...just do not know where to go from here.
>>
>> can you boot into a previous kernel?
>>
>> when you are in the busybox shell, are you able to manually mount your
>> partitions?
>> I suspect not based on the messages below.
>>
>> if you have no previous kernel to boot from, you will likely have to
>> boot rescue media, chroot into the system and rebuild from
>> there.
>>
>> Without more info, I would suggest either
>>
>> dpkg-reconfigure linux-image-2.6.24blahblahblah
>>
>> don't do *all* your linux images because if your initramfs stuff is
>> broken, then all your initrds will get broken as a result.
>>
>>>
>>> thanks
>>> mjh
>>>
>>>
>>> On Thu, Apr 3, 2008 at 12:44 AM, Vikram Vincent <vincentvikram@gmail.com> wrote:
>>> > Hello,
>>> > I upgraded my system to the latest kernel along with all the other packages.
>>> > While installing I found that the "initrd" line in grub's menu.lst was not
>>> > being
>>> > created and so I had to manually add it.
>>
>> what specifically did you manually add? Perhaps you added the wrong
>> initrd? Not sure what happens in that situation, but I bet it looks
>> like what you're seeing.
>>
>> remember that you can edit your boot lines on the fly in grub...
>>
>>> > Upon booting I get the certain messages and then find myself in the
>>> > initramfs
>>> > prompt. I tried reinstalling the concerned packages but to no avail.
>>> >
>>> > Begin: Running /scripts/init-bottom ...
>>> > mount: Mounting /root/dev on /dev/.static/dev failed: No such file or
>>> > directory
>>> > Done.
>>> > mount: Mounting /sys on /root/sys failed: No such file or directory
>>> > mount: Mounting /proc on /root/proc failed: No such file or directory
>>> > Target filesystem doesn't have /sbin/init
>>> > No init found. Try passing init= bootarg.
>>> >
>>> > Busybox.... Built-in shell (ash)
>>> > /bin/sh: can't access tty: job control turned off
>>> > (initramfs) /* prompt */
>>
>> whatever other specific details you can provide will help.
>>
>> ls -l /boot
>>
>> and maybe a copy of grub's menu.lst
>>
>> would be good starting places.
>>
>>
>> A
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFImNPtaIeIEqwil4YRAg9tAJ4tIQX4XFyIivBJW5wxX5ZGW1g1PQCg5Jiy
>> IxrySjkA2MwFqZ2DwLKD/8o=
>> =CE58
>> -----END PGP SIGNATURE-----
>>
>>
>
Reply to: