HP3000-L Archives

April 2013, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dan Barnes <[log in to unmask]>
Reply To:
Dan Barnes <[log in to unmask]>
Date:
Fri, 12 Apr 2013 15:23:34 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
Hi Gang,

I have a test system (989/450, mpe/ix 7.0 pp2) that I have discovered a bad drive on (9gb in a HAJE Jamaica Enclosure).  In doing regular preventive maintenance (fscheck, dump-to-disk testing) on restart after a ctrl-b tc, I have a single disk within a mounted volume set that has given me a repair source error.  In preparation for replacing the disk with all the required rebuilding of everything, one of our team members working on this found they got a disk read error trying to do a backup.  In doing a variety fo other things, the system ended up totally hung, including the console.

I figured while doing a reboot I would use ODE and then DISKUTIL in the hopes that a read test of the drive would force it to spare out the bad sector(s) and could then reboot and do the much simpler procedure for replacing a mirrored disk if it still complained.

Unfortunately, though it found the bad sector(s) on the first pass, when I ran it a second time to insure it was now clean, I am still getting the read error in the same location.

Is there anything else I can do to force the bad sectors to get flagged and swapped out ?

TIA,
Dan

Dan Barnes ..:.. LCI-Lawinger Consulting
106 Central Avenue, Suite A ..:.. Osseo, MN, 55369-1243
Tel: 763-390-8320 ..:.. Fax: 763-425-5483 ..:.. Cell: 612-240-2136 ..:.. Pager: 952-394-0132
[log in to unmask] ..:.. [log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2