[4449] in Hotline Meeting
More unhappiness in printserver land
daemon@ATHENA.MIT.EDU (David Krikorian)
Fri Apr 5 23:43:59 1991
Date: Fri, 5 Apr 91 23:43:39 -0500
From: David Krikorian <dkk@ATHENA.MIT.EDU>
To: hotline@ATHENA.MIT.EDU
Reply-To: dkk@mit.edu
M16-034-P has been logging hard errors tonight, too:
------------
Apr 5 04:40:26 m16-034-p vmunix: ra0g: hard error sn27856
------------
The additional problem with this one is that the bad block is an inode
block, and contains information about other inodes. As a result, a
whole bunch of files may end up in /site/lost+found/ when rqbads and
fsck are run:
------------
m16-034-p# /etc/icheck -b 27856 /dev/rra0g
/dev/rra0g:
27856 arg; frag 0 of 8, inode=5600, class=inodes 5600-5632
...
------------
I'd recommend running rqbads on this system soon (which will probably
show a bad block somewhere around number 76000 on ra0c) to try to
salvage the data from the bad block, then running fsck manually if it
doesn't succeed automatically during reboot. (Don't run fsck manually
until after rqbads has been run.)
I get the impression that all the original-equipment RD53s were
getting old, and were pushed to the limit by the recent power hit...
