Iván Filpo <[EMAIL PROTECTED]> wrote [with attributions corrected]:
> I'm getting insted of 40 a lot of 01's u think is probably the same ?. I'm
> booting hda5, that's the root. the other partition has win2k installed so
i
> think that if i set in the lilo.conf to boot /dev/hda it will return an
>
Joey Hess [EMAIL PROTECTED]; on behalf of; Joey Hess
[EMAIL PROTECTED]
> Seneca Cunningham wrote:
> > I have just been rearranging all my partitions, and now it looks like
the
> > most recent change is messing my system. A shortened version of the
first
> > couple post-post lines is:
> >
> > L
Seneca Cunningham wrote:
> I have just been rearranging all my partitions, and now it looks like the
> most recent change is messing my system. A shortened version of the first
> couple post-post lines is:
>
> L 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
>40 40 40 40
I managed to get the system to boot with my old potato rescue disk.
It seems that lilo was looking for the MBR or something similar in the wrong
location. Without putting out any error messages, when I had last run lilo
before the problem, it put the boot device to /dev/hda5, an extended
partition
hi seneca
you've got a problem...
you need to fix your lilo.conf file..
but cant fix it since it wont boot ???
- get tom's rootboot, or linux-bbc or other stand alone
boot media
- it'd be best/easiest to boot into single user mode
with root=/dev/hda3 ( your current / )
- fix /etc/lilo.co
I have just been rearranging all my partitions, and now it looks like the
most recent change is messing my system. A shortened version of the first
couple post-post lines is:
L 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 4
6 matches
Mail list logo
