Ok, I've been really working the RPM problem, and have solved everything up
to one
point... the new error message that I started getting, about the disk being
full.
I've done some experiments, and somehow, not only did the rpm database get
corrupted,
but the filesystem has become corrupted.  I can create files, write to them,
etc.,
but I cannot create new directories.  I've never seen anything like that.
I've
tried rebooting, thinking it was some kind of transient error, and fsck has
detected
errors on the disk... repeatedly.  Every time I've rebooted, even if I
reboot, login
just as root and as the first thing I do I tell it to reboot again, I get
fsck 
reporting errors on the disk.  Fsck should have repaired them; it didn't.
I've
also started getting other errors that are alarming me.  This one just
popped up
on the console, and I'm scratching my head.

Unable to handle kernel paging request at virtual address c9fcda18
current->tss.cr3 = 03238000, %cr3 = 03238000
*pde = 00000000
Ooops: 0000
CPU:     0
EIP:     0010:[<c013131c>]
EFLAGS:  00010206
eax: c3cfae58   ebx: c9fcda00   ecx: 00000024   edx: c3c00000
esi: c323b002   edi: c323b00c   ebp: c9fcda18   esp: c3245dcc
ds: 0018   es: 0018   ss: 0018
Process nice (pid: 1263, process nr: 46, stackpage=c3245000)
Stack: c323b00c 00000001 c3cfae58 c323b002 2f62eee7 0000000a c012c2b4
c1fcdc80
       c3245e14 c3245e14 c012c513 c1fcdc80 c3245e14 00000001 00000020
c323b000
       00000000 c323b000 c323b002 0000000a 2f62eee7 c012c6a6 c323b000
c1fcdc80
Call Trace: [<c012c2b4>] [<c012c513>] [<c012c6a6>] [<c012b877>] [<c012b737>]
[<c012c55f>] [<c012c0ec>]
        [<c0108d1b>] [<c0108d08>]
Code:  8b 6d 00 8b 74 24 18 39 73 48 75 58 8b 74 24 24 39 73 0c 75

Ok, I recognize SOME of what it's saying.... eax, ebx, ecx, and edx are
Intel Registers (hey, I remember that from my assembly programming days!)
CPU 0, well, it IS CPU 0, since I have a uniprocessor system.  But some of
the rest is totally foreign to me, unless it's almost a DBX style dump...
which I've never found particularly useful.  

Looks like Linus is going to have to be rebuilt from scratch...

So, my question is, does anyone know of a different/better tool to use to
check disks
and/or repair disks than fsck?  I'm losing some confidence in it, since it
is not able
to repair the disk during boot.  Unless this sounds like I have a disk going
bad to folks?

TIA
Bill Ward



R/William Ward


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to