January 28, 201115 yr Hello All, Just logged into unMenu and seeing one of my drives went down this afternoon. UnMenu is showing DSBL beside it instead og "OK" Log is showing this error: ATA_OP_STANDBYNOW1 ioctl error: -5 I powered down and checked the cables. NOThing loose (Though I didn't swap the sata cable out yet) I rebooted and still no change . I ran a short smart test and this is what i got: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 199 166 021 Pre-fail Always - 5025 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 516 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1539 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 37 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 6986 194 Temperature_Celsius 0x0022 123 115 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 Any ideas? is my disk bad? Should I run a new parity check? Sigh. Thanks!
January 29, 201115 yr Hello All, Just logged into unMenu and seeing one of my drives went down this afternoon. UnMenu is showing DSBL beside it instead og "OK" If a disk is disabled, a "write" to it failed. Log is showing this error: ATA_OP_STANDBYNOW1 ioctl error: -5 At that time, an attempt to control the drive failed. I powered down and checked the cables. NOThing loose (Though I didn't swap the sata cable out yet) I rebooted and still no change . How do you know there was no change? The array will not automatically put the drive back into service once a write to it failed. Can you get a smart report from the drive? I ran a short smart test and this is what i got: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 199 166 021 Pre-fail Always - 5025 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 516 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1539 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 37 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 6986 194 Temperature_Celsius 0x0022 123 115 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 It appears you can now communicate with the drive. It is probably not defective. It may have had (or still has) a loose cable. Any ideas? is my disk bad?No, probably not bad, but disabled. It does not have the correct contents (remember a write to it failed) so it must be re-constructed from parity and the other data drives. Should I run a new parity check? You cannot run a parity check if a drive is disabled. All drives must be working for that button to be present.Sigh. Thanks! To get the drive to be re-constructed you must Stop the array Un-assign the failed drive Start the array with it un-assigned (This will cause the array to forget its model/serial number) Stop the array once more Re-assign the failed disk back to its spot in the array Start the array once more. This time the contents of the drive will be re-constructed onto itself. When the re-construction is complete, your array will have parity protection once more (assuming it was just a loose cable). Until then, it is running in a degraded state simulating the contents of the failed drive. Joe L.
January 29, 201115 yr Author Looking good so far! Parity is rebuilding! Thanks Joe, you're a life saver!
January 29, 201115 yr Looking good so far! Parity is rebuilding!No, the disabled disk is being re-constructed from parity and the other data disks.
January 29, 201115 yr Author Doh! That's what i meant . Was rushing out the door to meet the lady friend . It's at 12.8%
Archived
This topic is now archived and is closed to further replies.