___________________________________________________________
This e-mail is intended for the addressee only
and may contain privileged and/or confidential information
___________________________________________________________
Thanks using the installer worked all appears to be well.
Yes the board is an Abit BP6 and I have the latest bios and I have
patched the bios with the latest hpt366 rom.
The hard drives are not on the hpt366 in any case. System is not
overclocked.
The computer was rock solid under 2.2.19 (patched) uptime of 4 months
at one stage.
How do you save an oops and kdb output, does issuing DEBUG=1 when in kdb
save the output or is that unnecessary?
Is the output from the kbd bt command needed?
I have checked the FAQ and and searched Google and have not been able to
find the answer to these questions sorry.
Godfrey
-----Original Message-----
From: Seth Mos [mailto:knuffie@xxxxxxxxx]
Sent: Monday, 20 August 2001 09:16
To: Godfrey Livingstone; linux-xfs@xxxxxxxxxxx
Subject: Re: oops on reboot damaged filesystem
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.
_____________________________________________
A J Park
Intellectual Property Lawyers and Consultants
Patent and Trade Mark Attorneys
New Zealand
www.ajpark.com
_____________________________________________
|