Date: Tue, 7 Oct 1997 15:06:34 +0000 (GMT) From: Adam David <adam@veda.is> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: fixing bad SCSI sectors? Message-ID: <199710071506.PAA00374@ubiq.veda.is> In-Reply-To: <19971007083916.RV43899@uriah.heep.sax.de> from J Wunsch at "Oct 7, 97 08:39:16 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > How do I start fixing this disk? > > By formatting it... This has been most weird. I figured out eventually that the device list was a menu of devices to choose from, and did a "Verify" from the BT445C BIOS. As soon as it hit sector 0x2a0 (deduced from previous context), it bailed out with "Verify Failed !". The disk is now up and running again... after a thorough massage, taking about 6 hours of repeated assaults. This is roughly what it took: 1. SCSI BIOS Verify --> Failed early 2. Switch off the power and wait for 30 seconds 3. SCSI BIOS Verify --> Failed late 4. Repeat 3 or more times from 1. --> Succeeded 5. fsck --> Failed late, bt0 not taking commands (same sector broke each time) 6. Repeat 3 or more times from 2. omitting Verify on final pass --> Succeeded I've no idea whether anything was remapped, the SCSI BIOS utility only reports success or failure. > Alas, dd(1) doesn't lseek on raw devices when using "seek=". ... and/or "skip="... but I guess it should do? Anyway, it turned out this time to be a hardware (not a media) problem by the looks of it. It was the wrong phase of the moon for this controller at an age of 3 years. I hope this doesn't happen every month. Does anyone know why the BT44x controllers are prone to this kind of lockup, and whether anything can be done about it? -- Adam David <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710071506.PAA00374>