how to correct "dirty" blocks, and how to use fsck.

[dnixon]

When booting, an SGI Indigo repeats lots of error messages that say there are system files not available or not found. This appears to be due to "dirty" blocks and/or superblock.

I have tried using the command "fsck /dev/root" in single user mode but this fails to run. Should I be running this command from a different position, or should I use something else to correct the corruption?

 

[crimso]

you'll have better luck with fx -x using the exercise option. do a man on fx because the exe submenu is potentially dangerous. from the sounds of it you have problems that will require the most invasive and a reload of the os. you could start by trying fx -x dksc
and select the right cntlr and disk and go into the exe menu and issue seq (sequential) and then use rd-cmp instead of wr-cmp this will not destroy the data on the disk but will add any block it deems bad to the defect list. keep in mind any data on those bad blocks may be lost if fx can't put it somewhere else. likely resulting in a corrupt os. hope this helps.

 

[dnixon]

Hi crimso,

Thanks for that, but a ready installed disk was obtained and replaced the failing disk. A bit extreme maybe but it had the correct software and set up on it, and works.
cheers!