Jump to content

3TB drive errors when creating parity // WD30EZRX


Recommended Posts

Updated from a working 4.7 array to 5.0b10 on a friend's test server, with the intent to test out the new 3TB support.  New parity drive was detected fine as 3TB, and when starting the array, the option was given to upgrade parity from 2TB to 3TB.  When starting the upgrade process, it worked for a couple of minutes and errored out.  See attached syslog.

 

Tried swapping the parity from the MB SATA to one of the Supermicro AOC PCIE cards, but no joy either.  MB is an ASUS P5Q Deluxe.  Edit: drive is an WD30EZRX 3TB.

 

Any ideas?

 

Cheers,

 

-jj-

syslog-2011-08-06.zip

Link to comment

Updated from a working 4.7 array to 5.0b10 on a friend's test server, with the intent to test out the new 3TB support.  New parity drive was detected fine as 3TB, and when starting the array, the option was given to upgrade parity from 2TB to 3TB.  When starting the upgrade process, it worked for a couple of minutes and errored out.  See attached syslog.

 

Tried swapping the parity from the MB SATA to one of the Supermicro AOC PCIE cards, but no joy either.  MB is an ASUS P5Q Deluxe.  Edit: drive is an WD30EZRX 3TB.

 

Any ideas?

 

Cheers,

 

-jj-

 

Don't know.  I am not an expert in syslog reading, but here is where the problems start ...

 

Aug  6 15:52:27 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1807:find reserved error, why?
Aug  6 15:52:27 Tower kernel: sas: sas_to_ata_err: Saw error 2.  What to do?
Aug  6 15:52:27 Tower kernel: sas: sas_ata_task_done: SAS error 2
Aug  6 15:52:27 Tower kernel: ata20: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Aug  6 15:52:27 Tower kernel: ata20: status=0x01 { Error }
Aug  6 15:52:27 Tower kernel: ata20: error=0x04 { DriveStatusError }
Aug  6 15:52:40 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1807:find reserved error, why?
Aug  6 15:52:40 Tower kernel: sas: sas_to_ata_err: Saw error 2.  What to do?
Aug  6 15:52:40 Tower kernel: sas: sas_ata_task_done: SAS error 2
Aug  6 15:52:40 Tower kernel: ata20: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Aug  6 15:52:40 Tower kernel: ata20: status=0x01 { Error }
Aug  6 15:52:40 Tower kernel: ata20: error=0x04 { DriveStatusError }
Aug  6 15:52:50 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1807:find reserved error, why?
Aug  6 15:52:50 Tower kernel: sas: sas_to_ata_err: Saw error 2.  What to do?
Aug  6 15:52:50 Tower kernel: sas: sas_ata_task_done: SAS error 2
Aug  6 15:52:50 Tower kernel: ata20: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Aug  6 15:52:50 Tower kernel: ata20: status=0x01 { Error }
Aug  6 15:52:50 Tower kernel: ata20: error=0x04 { DriveStatusError }
Aug  6 15:52:59 Tower kernel: sas: sas_to_ata_err: Saw error 2.  What to do?
Aug  6 15:52:59 Tower kernel: sas: sas_ata_task_done: SAS error 2
Aug  6 15:52:59 Tower kernel: ata20: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Aug  6 15:52:59 Tower kernel: ata20: status=0x01 { Error }
Aug  6 15:52:59 Tower kernel: ata20: error=0x04 { DriveStatusError }
Aug  6 15:53:09 Tower kernel: sas: sas_to_ata_err: Saw error 2.  What to do?
Aug  6 15:53:09 Tower kernel: sas: sas_ata_task_done: SAS error 2
Aug  6 15:53:09 Tower kernel: ata20: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Aug  6 15:53:09 Tower kernel: ata20: status=0x01 { Error }
Aug  6 15:53:09 Tower kernel: ata20: error=0x04 { DriveStatusError }
Aug  6 15:53:18 Tower kernel: sas: sas_to_ata_err: Saw error 2.  What to do?
Aug  6 15:53:18 Tower kernel: sas: sas_ata_task_done: SAS error 2
Aug  6 15:53:18 Tower kernel: ata20: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Aug  6 15:53:18 Tower kernel: ata20: status=0x01 { Error }
Aug  6 15:53:18 Tower kernel: ata20: error=0x04 { DriveStatusError }
Aug  6 15:53:18 Tower kernel: sd 10:0:3:0: [sdq]  Result: hostbyte=0x00 driverbyte=0x08
Aug  6 15:53:18 Tower kernel: sd 10:0:3:0: [sdq]  Sense Key : 0xb [current] [descriptor]
Aug  6 15:53:18 Tower kernel: Descriptor sense data with sense descriptors (in hex):
Aug  6 15:53:18 Tower kernel:         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
Aug  6 15:53:18 Tower kernel:         00 00 00 4f 
Aug  6 15:53:18 Tower kernel: sd 10:0:3:0: [sdq]  ASC=0x0 ASCQ=0x0
Aug  6 15:53:18 Tower kernel: sd 10:0:3:0: [sdq] CDB: cdb[0]=0x2a: 2a 00 00 20 01 50 00 01 00 00
Aug  6 15:53:18 Tower kernel: end_request: I/O error, dev sdq, sector 2097488
Aug  6 15:53:18 Tower kernel: md: disk0 write error
Aug  6 15:53:18 Tower kernel: handle_stripe write error: 2097424/0, count: 1
Aug  6 15:53:18 Tower kernel: md: md_do_sync: got signal, exit...
Aug  6 15:53:18 Tower kernel: md: disk0 write error
Aug  6 15:53:18 Tower kernel: handle_stripe write error: 2097432/0, count: 1
Aug  6 15:53:18 Tower kernel: md: disk0 write error
Aug  6 15:53:18 Tower kernel: handle_stripe write error: 2097440/0, count: 1
Aug  6 15:53:18 Tower kernel: md: disk0 write error
Aug  6 15:53:18 Tower kernel: handle_stripe write error: 2097448/0, count: 1
Aug  6 15:53:18 Tower kernel: md: disk0 write error

 

I have several 3T drives, but none are WD.  In fact I have not heard of anyone here with anything other that Hitachi 3T drives, so it could be something to do with the drive (unlikely but possible).

 

Whenever you see strange disk behavior first steps are normally to run smart reports and check the cabling.  Have you done that?  Can you post a smart report?  That would be my first suggestion.

Link to comment

Hello there, thanks very much for the reply.  Have since updated one of my servers to 0.5b10 and same issue there.  Have tried multiple ports for the drive (Supermicro 24 disk case).

 

SMART report attached:-

 

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD30EZRX-00MMMB0
Serial Number:    WD-WCAWZ0944377
Firmware Version: 80.00A80
User Capacity:    3,000,592,982,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  7 20:35:16 2011 CEST
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:  (0x80)	Offline data collection activity
				was never started.
				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: 		 (50160) 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: 	       (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       -       0
 3 Spin_Up_Time            0x0027   227   182   021    Pre-fail  Always       -       5616
 4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       11
 5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
 7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
 9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       23
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       -       10
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       6
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       34
194 Temperature_Celsius     0x0022   111   111   000    Old_age   Always       -       41
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   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

 

Current running Joe's 3TB preclear beta script on it, to see on errors there.  Will report back.

 

Cheers,

 

-jj-

 

Link to comment
  • 2 weeks later...

Just as a further update here, the WD drives seemed to read ok, but would error out upon any writes attempted.

 

I bought 2 x Hitachi_HDS723030ALA640 3TB drives to test and these are working perfectly fine.

 

Assume some compatibility issues with the WD drives at present (using Supermicro RAID card, and motherboard SATA's).

 

I will keep the drives on the side in case further testing needed at some point.

 

Cheers,

 

-jj-

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...