Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
SATA disk disappears
34 views
Skip to first unread message
Wojciech Puchar
Jan 10, 2013, 7:23:23 PM1/10/13
to
got this on dell poweredge T110 server with 4 disks, including two 3TB
drives (ada2,ada3):
ahcich2: Timeout on slot 8 port 0
ahcich2: is 00000000 cs 1ffffe00 ss 1fffff00 rs 1fffff00 tfd 40 serr
00000000 cmd 0000c817
ahcich2: AHCI reset: device not ready after 31000ms (tfd = 00000080)
(ada2:ahcich2:0:0:0): lost device
GEOM_MIRROR: Request failed (error=6). ada2[WRITE(offset=2997587410944,
length=753664)]
GEOM_MIRROR: Device home1: provider ada2 disconnected.
(ada2:ahcich2:0:0:0): removing device entry
did camcontrol reset 2, rescan 2 and ada2 reappeared
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <WDC WD30EZRX-00DC0B0 80.00A80> ATA-9 SATA 3.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
started gmirror rebuild and it now works at full speed.
GEOM_MIRROR: Device home1: rebuilding provider ada2.
What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk
is fine.
I use latest FreeBSD-8
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hacke...@freebsd.org"
Warren Block
Jan 10, 2013, 10:55:29 PM1/10/13
to
On Fri, 11 Jan 2013, Wojciech Puchar wrote:
>
> got this on dell poweredge T110 server with 4 disks, including two 3TB drives
> (ada2,ada3):
>
> ahcich2: Timeout on slot 8 port 0
> ahcich2: is 00000000 cs 1ffffe00 ss 1fffff00 rs 1fffff00 tfd 40 serr 00000000
> cmd 0000c817
> ahcich2: AHCI reset: device not ready after 31000ms (tfd = 00000080)
> (ada2:ahcich2:0:0:0): lost device
> GEOM_MIRROR: Request failed (error=6). ada2[WRITE(offset=2997587410944,
> length=753664)]
> GEOM_MIRROR: Device home1: provider ada2 disconnected.
> (ada2:ahcich2:0:0:0): removing device entry
>
>
>
> did camcontrol reset 2, rescan 2 and ada2 reappeared
> ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
> ada2: <WDC WD30EZRX-00DC0B0 80.00A80> ATA-9 SATA 3.x device
> ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada2: Command Queueing enabled
> ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>
>
> started gmirror rebuild and it now works at full speed.
>
> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>
>
> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk is
> fine.
I had a new WD drive recently that had a write error. Reallocated
>
> got this on dell poweredge T110 server with 4 disks, including two 3TB drives
> (ada2,ada3):
>
> ahcich2: Timeout on slot 8 port 0
> ahcich2: is 00000000 cs 1ffffe00 ss 1fffff00 rs 1fffff00 tfd 40 serr 00000000
> cmd 0000c817
> ahcich2: AHCI reset: device not ready after 31000ms (tfd = 00000080)
> (ada2:ahcich2:0:0:0): lost device
> GEOM_MIRROR: Request failed (error=6). ada2[WRITE(offset=2997587410944,
> length=753664)]
> GEOM_MIRROR: Device home1: provider ada2 disconnected.
> (ada2:ahcich2:0:0:0): removing device entry
>
>
>
> did camcontrol reset 2, rescan 2 and ada2 reappeared
> ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
> ada2: <WDC WD30EZRX-00DC0B0 80.00A80> ATA-9 SATA 3.x device
> ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada2: Command Queueing enabled
> ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>
>
> started gmirror rebuild and it now works at full speed.
>
> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>
>
> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk is
> fine.
sector count did not go up, but it quickly failed the SMART self-test,
short or long. See smartctl(8) about the -t parameters.
Wojciech Puchar
Jan 11, 2013, 5:42:34 AM1/11/13
to
>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>>
>>
>> started gmirror rebuild and it now works at full speed.
>>
>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>>
>>
>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk
>> is fine.
>
> I had a new WD drive recently that had a write error. Reallocated sector
> count did not go up, but it quickly failed the SMART self-test, short or
> long. See smartctl(8) about the -t parameters.
>
this is WD "green" 3TB
>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>>
>>
>> started gmirror rebuild and it now works at full speed.
>>
>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>>
>>
>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk
>> is fine.
>
> I had a new WD drive recently that had a write error. Reallocated sector
> count did not go up, but it quickly failed the SMART self-test, short or
> long. See smartctl(8) about the -t parameters.
>
Warren Block
Jan 11, 2013, 4:47:03 PM1/11/13
to
On Fri, 11 Jan 2013, Wojciech Puchar wrote:
>>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
>>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>>>
>>>
>>> started gmirror rebuild and it now works at full speed.
>>>
>>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>>>
>>>
>>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk
>>> is fine.
>>
>> I had a new WD drive recently that had a write error. Reallocated sector
>> count did not go up, but it quickly failed the SMART self-test, short or
>> long. See smartctl(8) about the -t parameters.
>>
> this is WD "green" 3TB
1T Red here. The firmware is likely very similar.
>>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>>>
>>>
>>> started gmirror rebuild and it now works at full speed.
>>>
>>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>>>
>>>
>>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows disk
>>> is fine.
>>
>> I had a new WD drive recently that had a write error. Reallocated sector
>> count did not go up, but it quickly failed the SMART self-test, short or
>> long. See smartctl(8) about the -t parameters.
>>
> this is WD "green" 3TB
Christian Gusenbauer
Jan 12, 2013, 3:25:54 AM1/12/13
to
On Friday 11 January 2013 22:47:03 Warren Block wrote:
> On Fri, 11 Jan 2013, Wojciech Puchar wrote:
> >>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
> >>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
> >>>
> >>>
> >>> started gmirror rebuild and it now works at full speed.
> >>>
> >>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
> >>>
> >>>
> >>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows
> >>> disk is fine.
> >>
> >> I had a new WD drive recently that had a write error. Reallocated
> >> sector count did not go up, but it quickly failed the SMART self-test,
> >> short or long. See smartctl(8) about the -t parameters.
> >
> > this is WD "green" 3TB
>
> 1T Red here. The firmware is likely very similar.
The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not using
> On Fri, 11 Jan 2013, Wojciech Puchar wrote:
> >>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
> >>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
> >>>
> >>>
> >>> started gmirror rebuild and it now works at full speed.
> >>>
> >>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
> >>>
> >>>
> >>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows
> >>> disk is fine.
> >>
> >> I had a new WD drive recently that had a write error. Reallocated
> >> sector count did not go up, but it quickly failed the SMART self-test,
> >> short or long. See smartctl(8) about the -t parameters.
> >
> > this is WD "green" 3TB
>
> 1T Red here. The firmware is likely very similar.
GEOM. I had that problem two times within the last two weeks, but the smart
self tests can not find any errors/bad sectors.
Ciao,
Christian.
Warren Block
Jan 12, 2013, 1:07:17 PM1/12/13
to
On Sat, 12 Jan 2013, Christian Gusenbauer wrote:
> On Friday 11 January 2013 22:47:03 Warren Block wrote:
>> On Fri, 11 Jan 2013, Wojciech Puchar wrote:
>>>>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
>>>>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>>>>>
>>>>>
>>>>> started gmirror rebuild and it now works at full speed.
>>>>>
>>>>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>>>>>
>>>>>
>>>>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows
>>>>> disk is fine.
>>>>
>>>> I had a new WD drive recently that had a write error. Reallocated
>>>> sector count did not go up, but it quickly failed the SMART self-test,
>>>> short or long. See smartctl(8) about the -t parameters.
>>>
>>> this is WD "green" 3TB
>>
>> 1T Red here. The firmware is likely very similar.
>
> The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not using
> GEOM. I had that problem two times within the last two weeks, but the smart
> self tests can not find any errors/bad sectors.
Hmm. The green drives are supposed to go to sleep for power saving, and
> On Friday 11 January 2013 22:47:03 Warren Block wrote:
>> On Fri, 11 Jan 2013, Wojciech Puchar wrote:
>>>>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
>>>>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
>>>>>
>>>>>
>>>>> started gmirror rebuild and it now works at full speed.
>>>>>
>>>>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
>>>>>
>>>>>
>>>>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows
>>>>> disk is fine.
>>>>
>>>> I had a new WD drive recently that had a write error. Reallocated
>>>> sector count did not go up, but it quickly failed the SMART self-test,
>>>> short or long. See smartctl(8) about the -t parameters.
>>>
>>> this is WD "green" 3TB
>>
>> 1T Red here. The firmware is likely very similar.
>
> The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not using
> GEOM. I had that problem two times within the last two weeks, but the smart
> self tests can not find any errors/bad sectors.
then there's a multiple-second delay when they have to spin back up on
access. That should not be a problem for gmirror, but maybe it is.
sysutils/ataidle can turn on the spindown. Some drives do not accept
that command, or claim to accept it but ignore it. Worth a try, though.
Warren Block
Jan 12, 2013, 1:10:29 PM1/12/13
to
On Sat, 12 Jan 2013, Warren Block wrote:
> Hmm. The green drives are supposed to go to sleep for power saving, and then
> there's a multiple-second delay when they have to spin back up on access.
> That should not be a problem for gmirror, but maybe it is. sysutils/ataidle
> can turn on the spindown. Some drives do not accept that command, or claim
> to accept it but ignore it. Worth a try, though.
Make that: sysutils/ataidle can turn *off* the spindown.
> Hmm. The green drives are supposed to go to sleep for power saving, and then
> there's a multiple-second delay when they have to spin back up on access.
> That should not be a problem for gmirror, but maybe it is. sysutils/ataidle
> can turn on the spindown. Some drives do not accept that command, or claim
> to accept it but ignore it. Worth a try, though.
Adam Vande More
Jan 12, 2013, 1:22:51 PM1/12/13
to
On Sat, Jan 12, 2013 at 12:10 PM, Warren Block <wbl...@wonkity.com> wrote:
> On Sat, 12 Jan 2013, Warren Block wrote:
>
> Hmm. The green drives are supposed to go to sleep for power saving, and
>> then there's a multiple-second delay when they have to spin back up on
>> access. That should not be a problem for gmirror, but maybe it is.
>> sysutils/ataidle can turn on the spindown. Some drives do not accept that
>> command, or claim to accept it but ignore it. Worth a try, though.
>>
>
> Make that: sysutils/ataidle can turn *off* the spindown.
>
>
Maybe just bumping kern.cam.ada.default_timeout to 45 or something might
> On Sat, 12 Jan 2013, Warren Block wrote:
>
> Hmm. The green drives are supposed to go to sleep for power saving, and
>> then there's a multiple-second delay when they have to spin back up on
>> access. That should not be a problem for gmirror, but maybe it is.
>> sysutils/ataidle can turn on the spindown. Some drives do not accept that
>> command, or claim to accept it but ignore it. Worth a try, though.
>>
>
> Make that: sysutils/ataidle can turn *off* the spindown.
>
>
help while still allowing drive to function as designed.
--
Adam Vande More
Wojciech Puchar
Jan 13, 2013, 5:36:36 AM1/13/13
to
>> self tests can not find any errors/bad sectors.
>
>
> Hmm. The green drives are supposed to go to sleep for power saving, and then
> there's a multiple-second delay when they have to spin back up on access.
no it wasn't that.
> there's a multiple-second delay when they have to spin back up on access.
i did long test as you recommended and drive reported fault.
Gave it back for replacement. Thank you
Wojciech Puchar
Jan 13, 2013, 5:40:01 AM1/13/13
to
>>
>> 1T Red here. The firmware is likely very similar.
>
> The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not using
> GEOM. I had that problem two times within the last two weeks, but the smart
>> 1T Red here. The firmware is likely very similar.
>
> The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not using
> GEOM. I had that problem two times within the last two weeks, but the smart
> self tests can not find any errors/bad sectors.
smartctl -t long /dev/disk
found an error after few hours.
Christian Gusenbauer
Jan 13, 2013, 11:30:56 AM1/13/13
to
On Saturday 12 January 2013 19:07:17 Warren Block wrote:
> On Sat, 12 Jan 2013, Christian Gusenbauer wrote:
> > On Friday 11 January 2013 22:47:03 Warren Block wrote:
> >> On Fri, 11 Jan 2013, Wojciech Puchar wrote:
> >>>>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
> >>>>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
> >>>>>
> >>>>>
> >>>>> started gmirror rebuild and it now works at full speed.
> >>>>>
> >>>>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
> >>>>>
> >>>>>
> >>>>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows
> >>>>> disk is fine.
> >>>>
> >>>> I had a new WD drive recently that had a write error. Reallocated
> >>>> sector count did not go up, but it quickly failed the SMART self-test,
> >>>> short or long. See smartctl(8) about the -t parameters.
> >>>
> >>> this is WD "green" 3TB
> >>
> On Sat, 12 Jan 2013, Christian Gusenbauer wrote:
> > On Friday 11 January 2013 22:47:03 Warren Block wrote:
> >> On Fri, 11 Jan 2013, Wojciech Puchar wrote:
> >>>>> GEOM_MIRROR: Component ada2 (device home1) broken, skipping.
> >>>>> GEOM_MIRROR: Cannot add disk ada2 to home1 (error=22).
> >>>>>
> >>>>>
> >>>>> started gmirror rebuild and it now works at full speed.
> >>>>>
> >>>>> GEOM_MIRROR: Device home1: rebuilding provider ada2.
> >>>>>
> >>>>>
> >>>>> What kind of hardware failure may it be? smartctl -a /dev/ada2 shows
> >>>>> disk is fine.
> >>>>
> >>>> I had a new WD drive recently that had a write error. Reallocated
> >>>> sector count did not go up, but it quickly failed the SMART self-test,
> >>>> short or long. See smartctl(8) about the -t parameters.
> >>>
> >>> this is WD "green" 3TB
> >>
> >> 1T Red here. The firmware is likely very similar.
> >
> > The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not
> > using GEOM. I had that problem two times within the last two weeks, but
> > the smart self tests can not find any errors/bad sectors.
>
> >
> > The same here: brandnew WD 2T green, 9.1 stable, svn rev. 244773, not
> > using GEOM. I had that problem two times within the last two weeks, but
> > the smart self tests can not find any errors/bad sectors.
>
> Hmm. The green drives are supposed to go to sleep for power saving, and
> then there's a multiple-second delay when they have to spin back up on
> then there's a multiple-second delay when they have to spin back up on
> access. That should not be a problem for gmirror, but maybe it is.
> sysutils/ataidle can turn on the spindown. Some drives do not accept
> that command, or claim to accept it but ignore it. Worth a try, though.
I don't think it was the power saving spin down, because I was copying data
> sysutils/ataidle can turn on the spindown. Some drives do not accept
> that command, or claim to accept it but ignore it. Worth a try, though.
from/to the drive when it suddenly vanished. So the disk was busy at that
time. I'll give ataidle a chance - but it's hard to reproduce. I'm using the
drive for five days now without failure.
Thanks,
Christian.
0 new messages