Samba going down frequently

Hi

I have a MyBookLive 1 TB and a WDTV Live Plus. Recently I started experiencing problems when playing videos in WDTV stored in MyBookLive. The playback stops frequently and I had to restart MyBookLive every time.

Then I noticed that Samba started to go down and I could play videos accessing through Twonky without problems. I accesed the device through ssh and using dmesg noticed that /dev/md1 partition had some errors.

I unmounted /dev/md1 and run fsck, leaving the partition clean and restarted.

Now md1 seems to be ok, but I found another intriguing error message using dmesg:

ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0310)
ata2.00: configured for UDMA/133
ata2.00: device reported invalid CHS sector 0
ata2: EH complete
sata-dwc 4bffd1800.sata: sata_dwc_isr intr with no active qc qc=(null)
sata-dwc 4bffd1800.sata: RX DMA PENDINGING
sata-dwc 4bffd1800.sata: dma_dwc_xfer_setup: dma channel unavailable
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: failed command: READ DMA EXT
ata2.00: cmd 25/00:80:80:05:95/00:00:28:00:00/e0 tag 0 dma 65536 in
         res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
ata2.00: status: { DRDY }

I also found this:

EXT4-fs (sda4): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda4): mounted filesystem with ordered data mode
eth0: no IPv6 routers present
Adding 500608k swap on /dev/sda3.  Priority:-1 extents:1 across:500608k
svc: failed to register lockdv1 RPC service (errno 97).
md: md0 stopped.
md: cannot remove active disk sda1 from md1 …
md: cannot remove active disk sda2 from md1 …

I cannot run fsck on sda4 because the device is always busy and cannot be unmounted without -f option. But even with -f, fsck sees it as mounted and complains. It doesn’t look safe to run fsck without a clean unmount, so I didn’t.

My firmware is updated, by the way.

Any ideas we’ll be truly apreciated.

Thanks in advance.

I search those ATA errors on Google.

Now, of course, in the context of an MBL, they might mean something else, but every indication is that your hardware is failing.

I’d back the drive up NOW and contact WD.

Yes, I did the same and seems you’re right.

But the strage thing is that Twonky seems to work without problems when samba is down.

So I run smartctl and I got this:

(Sorry, this is a lot of text but there are no attachments…)

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD10EARS-00MVWB0
Serial Number:    WD-WMAZA5776017
Firmware Version: 51.0AB51
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sun Aug 12 11:10:44 2012 ART
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:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:          (19080) 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:      ( 187) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x3035)    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       -       52
  3 Spin_Up_Time            0x0027   171   169   021    Pre-fail  Always       -       6425
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       2400
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   194   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   092   092   000    Old_age   Always       -       6349
 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       -       56
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       46
193 Load_Cycle_Count        0x0032   175   175   000    Old_age   Always       -       76112
194 Temperature_Celsius     0x0022   100   079   000    Old_age   Always       -       50
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       10
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       7
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      -       8

SMART Error Log Version: 1
ATA Error Count: 30 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It “wraps” after 49.710 days.

Error 30 occurred at disk power-on lifetime: 4169 hours (173 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  – – – – – – –
  40 51 80 a0 a0 02 e0  Error: UNC 128 sectors at LBA = 0x0002a0a0 = 172192

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  – – – – – – – –  ----------------  --------------------
  c8 00 80 80 a0 02 e0 08  13d+18:43:46.588  READ DMA
  ec 00 00 00 00 00 a0 08  13d+18:43:46.573  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  13d+18:43:46.573  SET FEATURES [Set transfer mode]

Error 29 occurred at disk power-on lifetime: 4169 hours (173 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  – – – – – – –
  01 51 80 00 a0 02 e0  Error: AMNF 128 sectors at LBA = 0x0002a000 = 172032

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  – – – – – – – –  ----------------  --------------------
  c8 00 80 00 a0 02 e0 08  13d+18:42:21.354  READ DMA
  c8 00 40 20 71 31 e0 08  13d+18:42:17.302  READ DMA
  e5 00 00 00 00 00 40 08  13d+18:42:17.292  CHECK POWER MODE
  c8 00 80 00 ea 01 e0 08  13d+18:42:08.055  READ DMA
  c8 00 80 80 e9 01 e0 08  13d+18:42:04.689  READ DMA

Error 28 occurred at disk power-on lifetime: 4169 hours (173 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  – – – – – – –
  40 51 40 28 71 31 e0  Error: UNC 64 sectors at LBA = 0x00317128 = 3240232

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  – – – – – – – –  ----------------  --------------------
  c8 00 40 20 71 31 e0 08  13d+18:42:17.302  READ DMA
  e5 00 00 00 00 00 40 08  13d+18:42:17.292  CHECK POWER MODE
  c8 00 80 00 ea 01 e0 08  13d+18:42:08.055  READ DMA
  c8 00 80 80 e9 01 e0 08  13d+18:42:04.689  READ DMA

Error 27 occurred at disk power-on lifetime: 4169 hours (173 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  – – – – – – –
  40 51 80 28 ea 01 e0  Error: UNC 128 sectors at LBA = 0x0001ea28 = 125480

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  – – – – – – – –  ----------------  --------------------
  c8 00 80 00 ea 01 e0 08  13d+18:42:08.055  READ DMA
  c8 00 80 80 e9 01 e0 08  13d+18:42:04.689  READ DMA
  ec 00 00 00 00 00 a0 08  13d+18:42:04.665  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  13d+18:42:04.664  SET FEATURES [Set transfer mode]

Error 26 occurred at disk power-on lifetime: 4169 hours (173 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  – – – – – – –
  01 51 80 88 e9 01 e0  Error: AMNF 128 sectors at LBA = 0x0001e988 = 125320

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  – – – – – – – –  ----------------  --------------------
  c8 00 80 80 e9 01 e0 08  13d+18:42:04.689  READ DMA
  ec 00 00 00 00 00 a0 08  13d+18:42:04.665  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08  13d+18:42:04.664  SET FEATURES [Set transfer mode]

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       90%      6333         54134560

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.

There is something wrong with the hardware. Now I wonder if it can be saved or not.

I guess I’ll have to contact WD.

Thanks.