HDD error ?

[pestijanos21]

Dear Support,

From yesterday I could reach my beautiful B3 server by web and refused all ssh connection.
(It is a totaly new device 2 weeks old .... )

After the restarting I have got the following error in the system log ( It works about 1-2 hours after cannot reach again) :

I think it can be a serious problem.

Help please!

Thank you in advance,
Best regards,

Jhonny

---------------------------
Nov 27 13:14:24 b3 kernel: [ 289.314668] ata1.00: exception Emask 0x0 SAct 0x3ff SErr 0x0 action 0x6
Nov 27 13:14:24 b3 kernel: [ 289.321252] ata1.00: edma_err_cause=02000084 pp_flags=00000003, dev error, EDMA self-disable
Nov 27 13:14:24 b3 kernel: [ 289.329745] ata1.00: failed command: READ FPDMA QUEUED
Nov 27 13:14:24 b3 kernel: [ 289.334892] ata1.00: cmd 60/00:00:98:f1:37/01:00:07:00:00/40 tag 0 ncq 131072 in
Nov 27 13:14:24 b3 kernel: [ 289.334899] res 41/40:00:e8:f1:37/00:00:07:00:00/40 Emask 0x409 (media error) <F>
Nov 27 13:14:24 b3 kernel: [ 289.350492] ata1.00: status: { DRDY ERR }
Nov 27 13:14:24 b3 kernel: [ 289.354482] ata1.00: error: { UNC }
Nov 27 13:14:24 b3 kernel: [ 289.357965] ata1.00: failed command: READ FPDMA QUEUED
Nov 27 13:14:24 b3 kernel: [ 289.363092] ata1.00: cmd 60/00:08:98:f2:37/01:00:07:00:00/40 tag 1 ncq 131072 in
Nov 27 13:14:24 b3 kernel: [ 289.363099] res 41/40:0c:98:f2:37/40:00:07:00:00/40 Emask 0x9 (media error)
Nov 27 13:14:24 b3 kernel: [ 289.378167] ata1.00: status: { DRDY ERR }
Nov 27 13:14:24 b3 kernel: [ 289.382155] ata1.00: error: { UNC }
Nov 27 13:14:24 b3 kernel: [ 289.385640] ata1.00: failed command: WRITE FPDMA QUEUED
Nov 27 13:14:24 b3 kernel: [ 289.390853] ata1.00: cmd 61/08:10:42:26:98/00:00:00:00:00/40 tag 2 ncq 4096 out
Nov 27 13:14:24 b3 kernel: [ 289.390860] res 41/40:0c:98:f2:37/40:00:07:00:00/40 Emask 0x9 (media error)
Nov 27 13:14:24 b3 kernel: [ 289.405842] ata1.00: status: { DRDY ERR }
Nov 27 13:14:24 b3 kernel: [ 289.409829] ata1.00: error: { UNC }
Nov 27 13:14:24 b3 kernel: [ 289.413305] ata1.00: failed command: WRITE FPDMA QUEUED
Nov 27 13:14:24 b3 kernel: [ 289.418529] ata1.00: cmd 61/08:18:4a:26:98/00:00:00:00:00/40 tag 3 ncq 4096 out
Nov 27 13:14:24 b3 kernel: [ 289.418536] res 41/40:0c:98:f2:37/40:00:07:00:00/40 Emask 0x9 (media error)
Nov 27 13:14:24 b3 kernel: [ 289.433593] ata1.00: status: { DRDY ERR }
Nov 27 13:14:24 b3 kernel: [ 289.437590] ata1.00: error: { UNC }
Nov 27 13:14:24 b3 kernel: [ 289.441065] ata1.00: failed command: WRITE FPDMA QUEUED
Nov 27 13:14:24 b3 kernel: [ 289.446289] ata1.00: cmd 61/08:20:52:26:98/00:00:00:00:00/40 tag 4 ncq 4096 out
Nov 27 13:14:24 b3 kernel: [ 289.446296] res 41/40:0c:98:f2:37/40:00:07:00:00/40 Emask 0x9 (media error)
Nov 27 13:14:24 b3 kernel: [ 289.461281] ata1.00: status: { DRDY ERR }
Nov 27 13:14:24 b3 kernel: [ 289.465281] ata1.00: error: { UNC }
Nov 27 13:14:24 b3 kernel: [ 289.468755] ata1.00: failed command: WRITE FPDMA QUEUED
Nov 27 13:14:24 b3 kernel: [ 289.473969] ata1.00: cmd 61/08:28:5a:26:98/00:00:00:00:00/40 tag 5 ncq 4096 out
Nov 27 13:14:24 b3 kernel: [ 289.473976] res 41/40:0c:98:f2:37/40:00:07:00:00/40 Emask 0x9 (media error)
Nov 27 13:14:24 b3 kernel: [ 289.488959] ata1.00: status: { DRDY ERR }
Nov 27 13:14:24 b3 kernel: [ 289.492946] ata1.00: error: { UNC }

[Ubi]

Could be a cable/controller issue, but could be something else too. AFAIK his generally does not point to a failed disk itself. Do you have any peripherals connected? (bubba storage, USB disk, whatever). If so, remove these if you can and see if the problem persists.
Oh and just to be sure, can you run this as root:

Code: Select all

cat /var/log/dmesg | grep 'ata[0-9]\+.[0-9][0-9]: ATA-'

You may want to check the health of your drive:

Code: Select all

apt-get install smartmontools
smartctl --all /dev/sda

It works about 1-2 hours after cannot reach again

Do you mean that every time it starts, it only works for max 2 hours and then dies?

[pestijanos21]

Hello,

Yes It means exactly, if I am using the device (copy, torrent ...) in 1-2 hours the B3 will stopp. Refuse the SSH connection and cannot see the web pages also.


You can see the smartctl logs:

Code: Select all

root@b3:/home/pesti# smartctl -a /dev/sda
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 WD10EARS-00MVWB0
Serial Number:    WD-WCAZA5866855
Firmware Version: 51.0AB51
User Capacity:    1,000,204,886,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:    Thu Dec  1 12:13:19 2011 CET
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:      ( 120) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                 (25080) 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:        ( 244) 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       -       38
  3 Spin_Up_Time            0x0027   253   253   021    Pre-fail  Always       -       1125
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       40
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   199   198   000    Old_age   Always       -       40
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       465
 10 Spin_Retry_Count        0x0032   100   253   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       -       38
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       30
193 Load_Cycle_Count        0x0032   186   186   000    Old_age   Always       -       42655
194 Temperature_Celsius     0x0022   114   104   000    Old_age   Always       -       36
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   001   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      -       2

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       80%       461         122311200
# 2  Extended offline    Completed: read failure       90%       461         122311200

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.

[Ubi]

can you please resubmit the smart data inside CODE blocks. This way it is rather unreadable
thanks

[Ubi]

but in the mean time it seems you have no bad blocks on the drive. My guess here is that the HDD cables are faulty or not inserted properly. As this is a new machine, would it be possible to re-insert the two cables into the HD and see if that improves? Such activity will not void your warranty.

[su_root]

Try to re-attach the cables as Ubi said. Could also be an IO controller failing or a software (kernel?) bug. Can you recall what you have updated and installed before this started?

Have you tried fsck, what does it say? Have you tried to restart udev? What HDD are you using and which kernel?

Just in case, try also to run memtest.

[Ubi]

yeah I was thinking of memtest. It's typically a memory issue if a machine dies after a specific time.
The old trick on PCs (if memtest gave no results) was to switch between linux and windows to verify, as windows starts occupying memory from the "other end" as linux (an d thus would crash at a much sooner or later timepoint).
But, as the presented errors are typical for a controller issue, and no file corruption was reported (which you'd expect from mem-corruption) I still put my money on the controller or the cable =)

[su_root]

But, as the presented errors are typical for a controller issue, and no file corruption was reported (which you'd expect from mem-corruption) I still put my money on the controller or the cable =)

Yes, I was thinking that it's odd that the starter of the thread did not complain about corrupted files. I had once a MoBo with faulty sata controller that corrupted pleeeeenty of data. I did not notice the corrupted data at once which made the journey very unpleasant.

But let's hope it is the cable, it is after all the easiest part to change

[su_root]

I did just find a very useful tool called inotifywatch, perhaps it helps you with your problem.

[pestijanos21]

Hello Guys,

Thank you.
I think will be better if I returned it where I buy, because it is under warranty. (without to open the box...)


Thank you for your efforts again.

Best regards,

Jhonny

[Ubi]

that's probably a wise idea.

[durin]

Hi,

I got this same problem last September. Until that my B3 worked almost for a full year before the problem started.

Unfortunately I haven't have time for this problem and my B3 has been unplugged since last September until now.

Did you find the reason for this problem or did Excito find the reason?

[durin]

Actualy it's not 100% same. My syslog shows

Apr 19 19:49:34 b3 kernel: [ 5054.636828] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
Apr 19 19:49:34 b3 kernel: [ 5054.643867] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 19 19:49:34 b3 kernel: [ 5054.649102] ata1.00: cmd 61/08:00:2a:47:98/00:00:00:00:00/40 tag 0 ncq 4096 out
Apr 19 19:49:34 b3 kernel: [ 5054.649109] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 19 19:49:34 b3 kernel: [ 5054.663746] ata1.00: status: { DRDY }
Apr 19 19:49:34 b3 kernel: [ 5054.667400] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 19 19:49:34 b3 kernel: [ 5054.672613] ata1.00: cmd 61/08:08:32:47:98/00:00:00:00:00/40 tag 1 ncq 4096 out
Apr 19 19:49:34 b3 kernel: [ 5054.672620] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 19 19:49:34 b3 kernel: [ 5054.687256] ata1.00: status: { DRDY }
Apr 19 19:49:34 b3 kernel: [ 5054.690910] ata1: hard resetting link
Apr 19 19:49:35 b3 kernel: [ 5056.036644] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
Apr 19 19:49:35 b3 kernel: [ 5056.116656] ata1.00: configured for UDMA/133
Apr 19 19:49:35 b3 kernel: [ 5056.120913] ata1.00: device reported invalid CHS sector 0
Apr 19 19:49:35 b3 kernel: [ 5056.126290] ata1.00: device reported invalid CHS sector 0
Apr 19 19:49:35 b3 kernel: [ 5056.131696] ata1: EH complete

[nobody]

interesting, the CHS invalid error generally only shows up with load-issues, not so much with defective hardware. May still be a hardware issue though, also because I can't really believe the B3 CPU can saturate the sata so much it brings forth these errors.