Slackware 10.2 doesn't boot anymore

bmxer_br · 05-30-2006, 08:14 AM

Hello friends,

I am using Slackware 10.2, with kernel 2.6.16 in my laptop (HP DV4274nr). Everything was going well and i have not made changes since last boot. I turned off computer yesterday, and today Slackware doesn't boot anymore.

The system is automatically booting from lilo and the message stops after dots "Loading Linux-2.6 ............." . No more messages and loading.

Where do i start to discover the problem? Is there a parameter can i use at lilo to try starting Slackware?

Thanks!
Michel

onebuck · 05-30-2006, 09:08 AM

Quote:

Originally Posted by bmxer_br

Hello friends,

I am using Slackware 10.2, with kernel 2.6.16 in my laptop (HP DV4274nr). Everything was going well and i have not made changes since last boot. I turned off computer yesterday, and today Slackware doesn't boot anymore.

The system is automatically booting from lilo and the message stops after dots "Loading Linux-2.6 ............." . No more messages and loading.

Where do i start to discover the problem? Is there a parameter can i use at lilo to try starting Slackware?

Thanks!
Michel

Hi,

You could use the install cd1 to boot your system!

Once the cd1 is booted you can respond to the boot: with;

Code:

boot: root=/dev/hda1 noinitrd ro

You can change the device (/dev/hda1) to your set.

Once you have your system booted then confirm your lilo.conf is correct then you can write;

Code:

#lilo -v -t -b /dev/hda      #this will test lilo
#lilo -v -b /dev/hda         #this write to /dev/hda

If you are able to write the lilo then try a reboot.

If not, do you have the virus protection set in your BIOS?

Bruce Hill · 06-02-2006, 10:03 PM

I suggest you get your hard drive manufacturer's utility and test your drive.

You can boot that Slackware at the LiLO boot prompt with:

Code:

Linux-2.6 init 1 (to boot into single user mode for root to work)
Linux-2.6 init 3 (to launch into multi-user mode without starting the X11 session manager)

If you haven't changed anything, it could be hardware. Or something you've run/installed might have changed something.

The sound advice that gwsandvik gave you will work to boot your system.

Please post back what you've done and the results...

psethi2000 · 06-20-2006, 02:27 AM

[QUOTE=gwsandvik]Hi,

You could use the install cd1 to boot your system!

Once the cd1 is booted you can respond to the boot: with;

Code:

boot: root=/dev/hda1 noinitrd ro

Did you mean?

Code:

boot: bare.i root=/dev/hda1 noinitrd ro

onebuck · 06-20-2006, 09:32 AM

[QUOTE=psethi2000]

Quote:

Originally Posted by gwsandvik

Hi,

You could use the install cd1 to boot your system!

Once the cd1 is booted you can respond to the boot: with;

Code:

boot: root=/dev/hda1 noinitrd ro

Did you mean?

Code:

boot: bare.i root=/dev/hda1 noinitrd ro

Hi,

The default is bare.i.

psethi2000 · 06-21-2006, 02:48 AM

[QUOTE=gwsandvik]

Quote:

Originally Posted by psethi2000

Hi,

The default is bare.i.

If I don't say bare.i , I get an error saying "could not find kernel image: root=/dev/hda"

if I put bare.i in the begining of the statement it works fine.

Thanks,