Re: I boot and get: L40 40 40 40 40...
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.conf
...
boot=/dev/hda
...
# take linear
# linear
lba32
...
root=/dev/hda3
...
- while its up and running: ( make a boot floppy )
dd if=/boot/vmlinuz of=/dev/fd0 bs=1024
rdev /dev/fd0 /dev/hda3
sync
- save this floppy... it will save you one day
or use lilo or mkbootdisk to make a boot floppy
re-run lilo again and you should be fine
c ya
alvin
On Mon, 28 Jan 2002, 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 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
>
> These lines continue not to the point of ad nauseum, but to the point of
> infinity. I can boot into my DOS partition with a boot disk, but I can't use
> the boot disk that I make earlier for my kernel (a custom compilation of
> 2.4.16), the partitions have been changed.
>
> I can't alter the settings on my boot floppy as the system with the problem
> is the only linux system that I have any access to.
>
> My system is a combination of potato, woody, and sid, that is mostly woody.
> The original partitions were somewhere along the lines of:
>
> /dev/hda1 FAT16 1000M
> /dev/hda3 Linux ext2 800M
> /dev/hda2 Linux swap 200M
>
> The altered partitions are something like:
>
> /dev/hda1 FAT16 100M
> /dev/hda2 Linux ext2 900M (this is /usr)
> /dev/hda5 Linux ext2 200M (this is /)
> /dev/hda6 Linux ext2 200M
> /dev/hda7 Linux ext2 200M
> /dev/hda8 Linux ext2 200M
> /dev/hda4 Linux swap 100M
>
> The problem did not happen after partitioning, or shifting the files from
> the old hda3 to the newer hda2, 5-8. It happened after I relocated files
> from what would now be /usr/usr to /usr.
>
> I had had some problems with this process earlier on, all being corrected
> within minutes.
>
> To my very untrained eye, it looks like some crucial file was corrupted in
> that final move (why is it _always_ the last change that kills the system).
>
> Do you know of any way to fix this without reinstalling the entire system?
> The only way I can do any installation is by floppy.
>
> Thanks for any help,
>
> Seneca
> seneca@slemish.com
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: