SEO

Hi,

I've just upgraded to the testing debian distrubution after using woody
for a little while.

I changed the sources list to testing, did apt-get update and apt-get -t
testing dist-upgrade

After a little bit of screwing around, it managed to upgrade everything,
except now when I reboot, I get the message:

"Verifying DMA Pool Data...

LI"

Looks like it got stuck just as it was starting LILO or something.

Does anyone know what I should do?

Brett.

On Thu, 2 Dec 2004, Brett wrote:

> I changed the sources list to testing, did apt-get update and apt-get -t
> testing dist-upgrade

#apt-get update
#apt-get dist-upgrade

> Looks like it got stuck just as it was starting LILO or something.
>
> Does anyone know what I should do?

At this point in time, read this:

HOWTO install Sarge with the net-installer-rc2
http://www.linuxquestions.org/questi...hreadid=261506

good luck

does he really need to resort to re-installing?
i don't think his system is screwed, it looks like it doesn't even get
to the kernel...

things to try:
- boot to a Live CD, re-install LILO or better install Grub
- if it gets to the kernel but hangs before initrd, try compiling your
own kernel, maybe some options were bad for your system in the upgraded
version.




Luigidigi wrote:
> On Thu, 2 Dec 2004, Brett wrote:
>
>
>>I changed the sources list to testing, did apt-get update and apt-get -t
>>testing dist-upgrade
>
>
> #apt-get update
> #apt-get dist-upgrade
>
>
>>Looks like it got stuck just as it was starting LILO or something.
>>
>>Does anyone know what I should do?
>
>
> At this point in time, read this:
>
> HOWTO install Sarge with the net-installer-rc2
> http://www.linuxquestions.org/questi...hreadid=261506
>
> good luck

On Thu, 2 Dec 2004 13:50:09 +1100, Brett
<noreply@hotmail.com> wrote:
> Hi,
>
> I've just upgraded to the testing debian distrubution after using woody
> for a little while.
>
> I changed the sources list to testing, did apt-get update and apt-get -t
> testing dist-upgrade
>
> After a little bit of screwing around, it managed to upgrade everything,
> except now when I reboot, I get the message:
>
> "Verifying DMA Pool Data...
>
> LI"
>
> Looks like it got stuck just as it was starting LILO or something.
>
> Does anyone know what I should do?
>
Run /sbin/lilo.

--
"At a scheduled time, the robot would pull the flush lever and scream as
it got sucked down the drain." --Kibo

OK, I've got a rescue disk, can someone help with some exact
instructions on how I can run lilo after booting with the rescue disks?

Brett.

"Bill Marcum" <bmarcum@iglou.com.urgent> wrote in message
news:9si382-otg.ln1@don.localnet...
> On Thu, 2 Dec 2004 13:50:09 +1100, Brett
> <noreply@hotmail.com> wrote:
>> Hi,
>>
>> I've just upgraded to the testing debian distrubution after using
>> woody
>> for a little while.
>>
>> I changed the sources list to testing, did apt-get update and
>> apt-get -t
>> testing dist-upgrade
>>
>> After a little bit of screwing around, it managed to upgrade
>> everything,
>> except now when I reboot, I get the message:
>>
>> "Verifying DMA Pool Data...
>>
>> LI"
>>
>> Looks like it got stuck just as it was starting LILO or something.
>>
>> Does anyone know what I should do?
>>
> Run /sbin/lilo.
>
> --
> "At a scheduled time, the robot would pull the flush lever and scream
> as
> it got sucked down the drain." --Kibo

OK, some progress.
From a Lnx-bbc boot CD, i've tried:

linux root=/dev/hda1

which seems to begin the boot process. I recognise some of the things
that it does during booting (setting the time, smb mounts etc), but I'm
getting *a lot* of errors like:

modprobe: modprobe: Cant open dependencies file
lib/modules/2.4.19-xfs/modules.dep (No such file or directory)

After this, I get the message:

INIT: no more processes left in this run level.

And the machine doesn't do anything else.

Please help!

Brett.

"Brett" <noreply@hotmail.com> wrote in message
news:41afaeed$0$8114$afc38c87@news.optusnet.com.au ...
> OK, I've got a rescue disk, can someone help with some exact
> instructions on how I can run lilo after booting with the rescue
> disks?
>
> Brett.
>
> "Bill Marcum" <bmarcum@iglou.com.urgent> wrote in message
> news:9si382-otg.ln1@don.localnet...
>> On Thu, 2 Dec 2004 13:50:09 +1100, Brett
>> <noreply@hotmail.com> wrote:
>>> Hi,
>>>
>>> I've just upgraded to the testing debian distrubution after using
>>> woody
>>> for a little while.
>>>
>>> I changed the sources list to testing, did apt-get update and
>>> apt-get -t
>>> testing dist-upgrade
>>>
>>> After a little bit of screwing around, it managed to upgrade
>>> everything,
>>> except now when I reboot, I get the message:
>>>
>>> "Verifying DMA Pool Data...
>>>
>>> LI"
>>>
>>> Looks like it got stuck just as it was starting LILO or something.
>>>
>>> Does anyone know what I should do?
>>>
>> Run /sbin/lilo.
>>
>> --
>> "At a scheduled time, the robot would pull the flush lever and scream
>> as
>> it got sucked down the drain." --Kibo
>
>

Brett wrote:
> OK, some progress.
> From a Lnx-bbc boot CD, i've tried:
>
> linux root=/dev/hda1

instead of using the rescue disk to boot to your harddrive, just boot it
to its own linux environment. If the setup on your harddrive is messed
up it's going to be a waste of time booting to it, right? If you boot
to the CD's linux, it will be entirely based on the CD, with the
filesystem in RAM. Your harddrive won't even be mounted.

Then, once this is done, you are in a stable linux environment with a
nice command prompt. Then you can do things like mount the harddrive
and look at the files to make sure everything is in place.

Ex:

# mkdir /mnt/hda1
# mount /dev/hda1 /mnt/hda1
# cd /mnt/hda1
# ls

This will let you see if everything is okay. Oh, before you mount it
you might want to try

# fsck /dev/hda1

This will check the disk to make sure there are no errors. If you want
to get into your harddrive's root, you can use chroot:

# chroot /mnt/hda1

Now it's as if you booted to your harddrive. You can use apt-get or
whatever you want. Check your lilo configuration:

# cat /etc/lilo.conf

If it's okay, re-run LILO to fix your boot sector.

# /sbin/lilo

Although I suggest using Grub instead, because it lets you change the
boot parameters on the fly, so it's easier to experiment with.


Steve

Brett schrob:
>> [top-quoting repaired]
>> Run /sbin/lilo.
> OK, I've got a rescue disk, can someone help with some exact
> instructions on how I can run lilo after booting with the rescue disks?

[boot from rescue disk]
mount /dev/hda1 /somewhere
chroot /somewhere
lilo

HTH,
Jan