Re: oops on reboot damaged filesystem

[Seth Mos <knuffie@xs4all.nl>]

At 08:41 20-8-2001 +1200, Godfrey Livingstone wrote:
>I have been trying to test out xfs for a while not but the system hard
>locked up on a regular basis until 2.4.9 which seems reasonably stable.
>I can get it to crash with a "make -j bzImage" but make -j 20 bzImage"
>does not crash.
>
>As a side note can anyone issue "make -j bzImage" or "make -j modules"
>and not crash their machine?

I have not encounterd it and I can still play Quake3 as well.

>smp dual celeron 433 with 512mb of ram

Abit dual celeron motherboard? Do you have the latest bios? A lot of people 
have reported problems with that motherboard before. Even NT4 can have a 
hard time operating. (I have a friend with such a motherboard)

>Anyway my problem is that when I shut down for a reboot I got an oops on
>reboot. Tried the rescue disk and when the rescue disk looked for
>installed partitions it found the damaged file system and crashed.
>
>How can I get the rescue disk to not look for partitions so that I can
>effect a repair?

AIEE!! Crap.

Start the installer just like you would installing the OS. I think you 
could switch to the second console with ctrl+alt+F2 and then repair the FS 
but I am not quite sure if you can do it from within the installer.

Another thing you could do is follow the link within the FAQ to the rescue 
boot disks section and download the XFS floppy boot disks. Maybe a last 
resort but that should always work.
http://oss.sgi.com/projects/xfs/faq.html#xfsbootdisks

>Godfrey Livingstone

Cheers

--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.