corrupted block on HD

Thread View: comp.sys.next.sysadmin

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Ludger Solbach Wed, 11 Nov 1992 19:51

#1291

Author: Ludger Solbach
Date: Wed, 11 Nov 1992 19:51

32 lines
1648 bytes

Each time I use "fsck" it reports an unreferenced File at Block
I=70905. Owner, size, modification time and mode of this file
are displayed, however, not the filename itself. I answer "y"
for correction, also on the following error report "BLKS MISSING
IN BITMAP". I run "fsck" again and type "reboot" afterwards. In
the following system panic it says: "(Cpu 0) vn_rele". After
another reboot command I get "INCORRECT BLOCK COUNT", again at
I=70905 plus "(1 should be 0) (corrected)".


     Now my questions:

- I thought SCSI drives would mask out corrupted blocks automa-
       tically. Why not here?

- How can I find out the name of the corrupted file?

- Is there a hard disk utility for NeXT like "Norton Utilities"
       for the Macintosh?

- How can I get rid of the problem?

Please help me! Send your answers to the e-mail address below.

          Ludger.

/********************************************************************/
/*  Ludger Solbach, AB Techn. Inf. VI, TU Hamburg-Harburg, Germany  */
/*                   Tel.: +49-40-7718-3357                         */
/*               e-mail: solbach@tu-harburg.dbp.de                  */
/********************************************************************/

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads