is this device bad?
Todd Cohen
I just bought one of those huge seagate ST410800N hard drives off
off e-bay and I'm getting errors trying to make it useable. I've connected
it via an external enclosure to my AlphaStation 200. I'm using an active
terminator. dmesg reports the following on bootup:
da1 at sym0 bus 0 target 4 lun 0
da1: <SEAGATE ST410800N 7114> Fixed Direct Access SCSI-2 device
da1: 10.000MB/s transfers (10.000MHz, offset 8)
da1: Attempt to query device size failed: MEDIUM ERROR, Medium format
corrupted
and when I try the following commands I get these errors:
lizard# dd if=/dev/zero of=/dev/da1 bs=1k count=1
dd: /dev/da1: Input/output error
lizard# dd if=/dev/zero of=/dev/rda1 bs=1k count=1
dd: /dev/rda1: Input/output error
from dmesg:
(da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
(da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
(da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
(da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
(da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
(da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
(da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
(da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
Is this drive bad?
__________________________________________________________________________
ICMP: The protocol that goes PING! I like angles, but only to a degree.
cthread. cthread_fork(). Fork, thread, fork! Black holes suck.
http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars.
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Kenneth D. Merry
It might be, although when I've seen 'medium format corrupted' errors
before, they're sometimes fixable by low-level formatting the disk.
Try formatting the disk like this:
camcontrol format da1
Then try accessing the disk again. If that doesn't fix the problem, you
might have a bad disk.
Ken
--
Kenneth Merry
k...@kdm.org
J Wunsch
> It might be, although when I've seen 'medium format corrupted'
> errors before, they're sometimes fixable by low-level formatting the
> disk.
`Medium format corrupted' is normally issued if a previous `format
unit' operation had been aborted. Reformatting should help (unless
the `format unit' operation itself ends up in another error, of
course).
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Mike Squires
I have about 20 of the ST410800WD drives here, used with Adaptec, Symbios,
and DPT controllers.
I would do a low level format, using the controller's low level format
option (CTL-A during the boot process for Adaptec).
I've always done this with a new or used disk when connected for the
first time or to a different controller. This is in part superstitious
behaviour learned during the early days of PC SCSI when even Adaptec
controllers didn't use interchangeable low level formats.
The ST4100800 series has been very reliable for me - no failures, and they
clock at a respectable 5MB/sec for an old 5400 RPM drive.
MLS
Todd Cohen
AlphaStation. I ran the following as someone else suggested, it doesn't
report any errors.. but later in dmesg I get errors:
camcontrol format da1
da1 at sym0 bus 0 target 4 lun 0
da1: <SEAGATE ST410800N 7114> Fixed Direct Access SCSI-2 device
da1: 10.000MB/s transfers (10.000MHz, offset 8)
da1: Attempt to query device size failed: MEDIUM ERROR, Medium format
corrupted
(da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
(da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
(da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
(da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
(da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
(da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
-Todd
On Tue, 24 Apr 2001, Mike Squires wrote:
> > I just bought one of those huge seagate ST410800N hard drives off
>
> I have about 20 of the ST410800WD drives here, used with Adaptec, Symbios,
> and DPT controllers.
>
> I would do a low level format, using the controller's low level format
> option (CTL-A during the boot process for Adaptec).
>
> I've always done this with a new or used disk when connected for the
> first time or to a different controller. This is in part superstitious
> behaviour learned during the early days of PC SCSI when even Adaptec
> controllers didn't use interchangeable low level formats.
>
> The ST4100800 series has been very reliable for me - no failures, and they
> clock at a respectable 5MB/sec for an old 5400 RPM drive.
>
> MLS
>
__________________________________________________________________________
ICMP: The protocol that goes PING! I like angles, but only to a degree.
cthread. cthread_fork(). Fork, thread, fork! Black holes suck.
http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars.
Kenneth D. Merry
> Well, I don't know how to do a low level format on this machine.. it's an
> AlphaStation. I ran the following as someone else suggested, it doesn't
> report any errors.. but later in dmesg I get errors:
>
> camcontrol format da1
That is a low level format.
> da1 at sym0 bus 0 target 4 lun 0
> da1: <SEAGATE ST410800N 7114> Fixed Direct Access SCSI-2 device
> da1: 10.000MB/s transfers (10.000MHz, offset 8)
> da1: Attempt to query device size failed: MEDIUM ERROR, Medium format
> corrupted
> (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
> (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
> (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
> (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
> (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0
> (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1
If those errors popped up after the format (you might want to power cycle
as well), then you've probably got a bad drive.
Ken
--
Kenneth Merry
k...@kdm.org
To Unsubscribe: send mail to majo...@FreeBSD.org
Todd Cohen
format took about 2 seconds...
-Todd
__________________________________________________________________________
ICMP: The protocol that goes PING! I like angles, but only to a degree.
cthread. cthread_fork(). Fork, thread, fork! Black holes suck.
http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars.
Kenneth D. Merry
> Ok.. how long should that format take? it's a 9.x gig drive and that
> format took about 2 seconds...
It should have taken a lot longer than that.
Try this instead:
camcontrol format da1 -v -w
That will issue a non-immediate format command. It may be that your drive
doesn't like the immediate format command but isn't returning an error.
Ken
--
Kenneth Merry
k...@kdm.org
To Unsubscribe: send mail to majo...@FreeBSD.org
Todd Cohen
so.. then had the following error:
lizard# camcontrol format da1 -v -w
You are about to REMOVE ALL DATA from the following device:
pass1: <SEAGATE ST410800N 7114> Fixed Direct Access SCSI-2 device
pass1: Serial Number 00337771
pass1: 10.000MB/s transfers (10.000MHz, offset 8)
Are you SURE you want to do this? (yes/no) yes
Current format timeout is 10800 seconds
Enter new timeout in seconds or press
return to keep the current timeout [10800]
Formatting...camcontrol: error sending format command
CAM status is 0xb
lizard#
-Todd
On Tue, 24 Apr 2001, Kenneth D. Merry wrote:
> On Tue, Apr 24, 2001 at 12:24:50 -0400, Todd Cohen wrote:
> > Ok.. how long should that format take? it's a 9.x gig drive and that
> > format took about 2 seconds...
>
> It should have taken a lot longer than that.
>
> Try this instead:
>
> camcontrol format da1 -v -w
>
> That will issue a non-immediate format command. It may be that your drive
> doesn't like the immediate format command but isn't returning an error.
>
> Ken
> --
> Kenneth Merry
> k...@kdm.org
>
__________________________________________________________________________
ICMP: The protocol that goes PING! I like angles, but only to a degree.
cthread. cthread_fork(). Fork, thread, fork! Black holes suck.
http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars.
Kenneth D. Merry
> I ran that command... it sat at "Fromatting..." for about 20-30 minutes or
> so.. then had the following error:
>
> lizard# camcontrol format da1 -v -w
> You are about to REMOVE ALL DATA from the following device:
> pass1: <SEAGATE ST410800N 7114> Fixed Direct Access SCSI-2 device
> pass1: Serial Number 00337771
> pass1: 10.000MB/s transfers (10.000MHz, offset 8)
> Are you SURE you want to do this? (yes/no) yes
> Current format timeout is 10800 seconds
> Enter new timeout in seconds or press
> return to keep the current timeout [10800]
> Formatting...camcontrol: error sending format command
> CAM status is 0xb
> lizard#
That's a command timeout, but the timeout was set to 3 hours, not 20-30
minutes. Was there anything in the dmesg after camcontrol returned?
Ken
--
Kenneth Merry
k...@kdm.org
To Unsubscribe: send mail to majo...@FreeBSD.org
Todd Cohen
(da0:sym0:0:0:0): MEDIUM ERROR info:1f4e47 asc:11,0
(da0:sym0:0:0:0): Unrecovered read error
(da0:sym0:0:0:0): READ(06). CDB: 8 1f 60 10 10 0
(da0:sym0:0:0:0): MEDIUM ERROR info:1f6017 asc:11,0
(da0:sym0:0:0:0): Unrecovered read error
sym0:4:control msgout: 80 6.
-Todd
On Tue, 24 Apr 2001, Kenneth D. Merry wrote:
__________________________________________________________________________
ICMP: The protocol that goes PING! I like angles, but only to a degree.
cthread. cthread_fork(). Fork, thread, fork! Black holes suck.
http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars.
Kenneth D. Merry
On Tue, Apr 24, 2001 at 15:00:20 -0400, Todd Cohen wrote:
> On Tue, 24 Apr 2001, Kenneth D. Merry wrote:
> > On Tue, Apr 24, 2001 at 14:44:02 -0400, Todd Cohen wrote:
> > > I ran that command... it sat at "Fromatting..." for about 20-30 minutes or
> > > so.. then had the following error:
> > >
> > > lizard# camcontrol format da1 -v -w
> > > You are about to REMOVE ALL DATA from the following device:
> > > pass1: <SEAGATE ST410800N 7114> Fixed Direct Access SCSI-2 device
> > > pass1: Serial Number 00337771
> > > pass1: 10.000MB/s transfers (10.000MHz, offset 8)
> > > Are you SURE you want to do this? (yes/no) yes
> > > Current format timeout is 10800 seconds
> > > Enter new timeout in seconds or press
> > > return to keep the current timeout [10800]
> > > Formatting...camcontrol: error sending format command
> > > CAM status is 0xb
> > > lizard#
> >
> > That's a command timeout, but the timeout was set to 3 hours, not 20-30
> > minutes. Was there anything in the dmesg after camcontrol returned?
> >
> (da0:sym0:0:0:0): READ(06). CDB: 8 1f 4e 46 2 0
> (da0:sym0:0:0:0): MEDIUM ERROR info:1f4e47 asc:11,0
> (da0:sym0:0:0:0): Unrecovered read error
> (da0:sym0:0:0:0): READ(06). CDB: 8 1f 60 10 10 0
> (da0:sym0:0:0:0): MEDIUM ERROR info:1f6017 asc:11,0
> (da0:sym0:0:0:0): Unrecovered read error
> sym0:4:control msgout: 80 6.
Isn't the drive you're trying to talk to da1?
The last message is the one that might pertain to da1, but I'm not sure
what that means. You'll have to ask Gerard what that means, and then we
can perhaps figure out why the disk is timing out.
Another potential problem is the timeout length may be overflowing a 32-bit
integer.
IIRC, HZ on the alpha is 1000. The sym(4) driver uses the following to
calculate the timeout:
ccb->ccb_h.timeout_ch = timeout(sym_timeout, (caddr_t) ccb,
ccb->ccb_h.timeout*hz/1000);
So with a timeout of 10800 seconds, or 10,800,000 ms, multiplied by hz,
which is likely 1000 on the alpha, you would overflow a 32-bit integer.
So try a timeout of 4200 seconds instead, and see if that works. That's 70
minutes, but it might be enough for the format to complete.
If not, we'll have to adjust the above calculation to use 64-bit math so it
won't overflow.
Todd Cohen
loaner and it's not the greatest either :) I'll try a different timeout..
thanks.
-Todd
>
> Isn't the drive you're trying to talk to da1?
>
> The last message is the one that might pertain to da1, but I'm not sure
> what that means. You'll have to ask Gerard what that means, and then we
> can perhaps figure out why the disk is timing out.
>
> Another potential problem is the timeout length may be overflowing a 32-bit
> integer.
>
> IIRC, HZ on the alpha is 1000. The sym(4) driver uses the following to
> calculate the timeout:
>
> ccb->ccb_h.timeout_ch = timeout(sym_timeout, (caddr_t) ccb,
> ccb->ccb_h.timeout*hz/1000);
>
> So with a timeout of 10800 seconds, or 10,800,000 ms, multiplied by hz,
> which is likely 1000 on the alpha, you would overflow a 32-bit integer.
>
> So try a timeout of 4200 seconds instead, and see if that works. That's 70
> minutes, but it might be enough for the format to complete.
>
> If not, we'll have to adjust the above calculation to use 64-bit math so it
> won't overflow.
>
> Ken
> --
> Kenneth Merry
> k...@kdm.org
>
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-scsi" in the body of the message
>
__________________________________________________________________________
ICMP: The protocol that goes PING! I like angles, but only to a degree.
cthread. cthread_fork(). Fork, thread, fork! Black holes suck.
http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars.