LILO problems... 1

[LiquidBinary]

Scenerio: I have a dual boot box running win2k and slackware. Win2k is on the master disk, linux is located on the slave. I recently tried to re-size my linux partition from win2k with partition magic. There was a program crash, and now when ever I try to boot into linux, it does not recognize any of my user or root passwords. When I try shutdown -r now (ctrl-alt-del) it says it does not understand what a run-level is. LILO still works fine, I can boot into both OS's, it's just my linux partition is trashed. Any hope of salvation? I also have a second question. I was under the impression that LILO was installed on the MBR of the master disk. I recently disconnected the slave drive, set the approprate settings in setup, and attemped to boot into win2k. When LILO was supposed to show up, I got a series of 10000101001010100001001010100101 scrolling a loop. Does LILO some how need the slave (linux drive) to boot win2k? Mike L.G.
mlg400@blazemail.com

 

[MikeLacey]

Mike,

It sounds as if your primary hd is a bit sick..... (that's no news to you I'm sure)

Looks as if you have two problems:

1 - MBR not happy when slave is disconnected
2 - Linux installation appears corrupted.

WRT 1 - Have you considered running 'fdisk /mbr' (which will put a clean MBR on your primary hd) and then reinstalling LILO? Mike
michael.j.lacey@ntlworld.com
Email welcome if you're in a hurry or something -- but post in tek-tips as well please, and I will post my reply here as well.

 

[LiquidBinary]

Mike: I have thought about running that command, but I am not too sure how safe that is. Microsoft recommends doing that as a last resort. If I do run it, how will I re-install LILO? Is it possible to do it from Win2k? Mike L.G.
mlg400@blazemail.com

 

[MikeLacey]

I think it's safe enough to run fdisk /mbr I've had to do it a couple of times and it's caused me no trouble.

I wouldn't know about re-installing LILO, to be honest that wouldn't be my priority in your place. I would want to get the partition table in a good state (fdisk /mbr) and then start to repair/redo the Linux install. What am I missing? Mike
michael.j.lacey@ntlworld.com
Email welcome if you're in a hurry or something -- but post in tek-tips as well please, and I will post my reply here as well.