B3 grinding noises - disk failing? URGENT!

[theWebalyst]

My B3 is normally silent but a few minutes ago I noticed a grinding noise that sounds like the disk. Its a bit like the sound of something loose rattling about most of the time (though obviously its not quite that!), though occaisionally I'm hearing the "zip zip" of a longer seek operation.

I tried the web interface which didn't respond at first. Then I got into a couple of pages (I think, maybe they are cached in FF) but now I am getting 500 errors from Apache after a long timeout.

So, probably a disk failure, although as this is a RAID setup does this mean both disks?

Any recommended actions? (I have a spare disk in a Bubba|2 handy).

Thanks

Mark

[DanielM]

I'd start taking backup of everything important...

(Actually I wouldn't, I already got backups of it, but I'd doublecheck for sure.)

/Daniel

[theWebalyst]

I'd start taking backup of everything important...

(Actually I wouldn't, I already got backups of it, but I'd doublecheck for sure.)

/Daniel

Thanks Daniel, but it is my backup

Mark

[86ivar]

For how long have this bubba been running?
Im a bit concerned abaout my bubba 2 that has been running continously 1,5 yrs. the disk never stops even no downloads. Anyone know the lifetime of such a disk? (2Tb Green)
Is there a option to make it "sleep" to save its lifetime?

[Eek]

Actually if it keeps spinning all the time,
the less likely it is to give problems.
Problems mostly arise from spinning up and down of the disks and sudden power outages.

[theWebalyst]

UPDATE...

Ok, the grinding has stopped and the web interface is working again.

Raid status is "normal", but the syslog is full of disk errors (see below). Is it normal for RAID to say all is well when clearly there was a problem? What does this mean for my drives? Should I run some diagnostics?

All advice appreciated. Here's the last bit of syslog (no errors after this, time currently 17:22):

Code: Select all

Jan 16 17:06:35 b3 kernel: [5377131.564975] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 16 17:06:35 b3 kernel: [5377131.571695] ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jan 16 17:06:35 b3 kernel: [5377131.580299] ata2.00: failed command: READ DMA EXT
Jan 16 17:06:35 b3 kernel: [5377131.585172] ata2.00: cmd 25/00:08:5a:00:a4/00:00:a3:00:00/e0 tag 0 dma 4096 in
Jan 16 17:06:35 b3 kernel: [5377131.585179] res 51/40:00:5a:00:a4/40:00:a3:00:00/e0 Emask 0x9 (media error)
Jan 16 17:06:35 b3 kernel: [5377131.600478] ata2.00: status: { DRDY ERR }
Jan 16 17:06:35 b3 kernel: [5377131.604638] ata2.00: error: { UNC }
Jan 16 17:06:35 b3 kernel: [5377131.608324] ata2: hard resetting link
Jan 16 17:06:38 b3 kernel: [5377134.874979] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
Jan 16 17:06:39 b3 kernel: [5377134.994960] ata2.00: configured for UDMA/33
Jan 16 17:06:39 b3 kernel: [5377134.999339] sd 1:0:0:0: [sdb] Unhandled sense code
Jan 16 17:06:39 b3 kernel: [5377135.004279] sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
Jan 16 17:06:39 b3 kernel: [5377135.010868] sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Jan 16 17:06:39 b3 kernel: [5377135.017488] Descriptor sense data with sense descriptors (in hex):
Jan 16 17:06:39 b3 kernel: [5377135.023821] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jan 16 17:06:39 b3 kernel: [5377135.030465] a3 a4 00 5a
Jan 16 17:06:39 b3 kernel: [5377135.033888] sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4
Jan 16 17:06:39 b3 kernel: [5377135.038693] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 a3 a4 00 5a 00 00 08 00
Jan 16 17:06:39 b3 kernel: [5377135.046099] end_request: I/O error, dev sdb, sector 2745434202
Jan 16 17:06:39 b3 kernel: [5377135.052080] md/raid1:md0: sdb1: rescheduling sector 2745434168
Jan 16 17:06:39 b3 kernel: [5377135.058101] ata2: EH complete
Jan 16 17:06:51 b3 snmpd[2102]: error on subcontainer 'ia_addr' insert (-1)
Jan 16 17:06:54 b3 Bubba: :Album[10076]: 0, Loop: is still running
Jan 16 17:06:54 b3 Bubba: :Album[10076]: 0, Loop time: time=1326733644 now=1326733614, t=30
Jan 16 17:07:06 b3 kernel: [5377162.869950] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 16 17:07:06 b3 kernel: [5377162.876579] ata2.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Jan 16 17:07:06 b3 kernel: [5377162.885542] ata2.00: failed command: READ DMA EXT
Jan 16 17:07:06 b3 kernel: [5377162.890769] ata2.00: cmd 25/00:08:5a:00:a4/00:00:a3:00:00/e0 tag 0 dma 4096 in
Jan 16 17:07:06 b3 kernel: [5377162.890777] res 51/40:00:5c:00:a4/40:00:a3:00:00/e0 Emask 0x9 (media error)
Jan 16 17:07:06 b3 kernel: [5377162.906041] ata2.00: status: { DRDY ERR }
Jan 16 17:07:06 b3 kernel: [5377162.910201] ata2.00: error: { UNC }
Jan 16 17:07:06 b3 kernel: [5377162.913888] ata2: hard resetting link
Jan 16 17:07:09 b3 kernel: [5377165.221807] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
Jan 16 17:07:09 b3 kernel: [5377165.321847] ata2.00: configured for UDMA/33
Jan 16 17:07:09 b3 kernel: [5377165.326221] ata2: EH complete
Jan 16 17:07:09 b3 kernel: [5377165.630477] md/raid1:md0: redirecting sector 2745434168 to other mirror: sdb1

[Ubi]

These errors sound a bit like that other thread. At that time we were expecting cable rather than HDD error, and in the end the unit was returned for warranty.

[Binkem]

Did you check your disk's SMART status? There is a howto on the forum somewhere.

[Ubi]

Binkem you also need to explain to him what to look for in the SMART readout, as the resulting jungle of numbers isn't exactly obvious for non-experts.

[theWebalyst]

Well I have done "smartctl -t long" tests on /dev/sda and /dev/sdb. I also captured the "smartctl -a" output for each drive beforehand so I could to a diff. These pre "-t long" outputs are different and neither contains an error, unlike the output after doing "-t long".

Is the test complete?
/dev/sdb completed without errors, at least I think it completed. The output contains the following:

"Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host."

Does this mean the "smartctl -t long" has not completed?

/dev/sda - read error
Anyway, /dev/sda has a similar message, but also did have an error. Here is the error line, and below it the complete smartctl status output for the drive.

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 50% 10447 1939442656

Code: Select all

smartctl 5.40 2010-07-12 r3124 [armv5tel-unknown-linux-gnueabi] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format) family
Device Model:     WDC WD20EARS-00S8B1
Serial Number:    WD-WCAVY4135034
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Tue Jan 17 13:24:52 2012 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x85) Offline data collection activity
                                        was aborted by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 117) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                 (39960) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 255) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x3031) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
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   161   141   021    Pre-fail  Always       -       8925
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       122
  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   086   086   000    Old_age   Always       -       10447
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       106
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       101
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       1138773
194 Temperature_Celsius     0x0022   101   097   000    Old_age   Always       -       51
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       11
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1
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      -       1

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       50%     10447         1939442656

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

What is the recommended action for this read error?

Thanks,

Mark