dieselpwr3d Posted July 31, 2015 Share Posted July 31, 2015 I'm at a complete loss now. I'm running a supermicro AOC-SAS2LP-MV8, connected to mainly sas drives, but I do have one new WD Red 2.5" 1tb drive that is connected as the parity drive. Ever since I've installed it, I build the array just fine, it works all day just fine and then when trying to run a parity automatically, I get errors and the drive drops out. I've run the long and short smart scans through the webgui with no errors reported, and cannot figure out why. I've attached the download from the hard drive, as well as the diagnostic zip file from unraid. When I encounter this error, I have never written anything new to the drives, I can re add the drive, run a parity check and it works just fine, until unraid again does an automatic parity check and I get the drive dropping due to errors. If someone wouldn't mind taking a look at the attachments and offering some suggestions, I would really appreciate it. Actually, I wasn't allowed to upload the .rtf file. So I've copied and pasted the contents here. smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: /1:0:3:0 Product: User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes Physical block size: 1903784304 bytes Lowest aligned LBA: 14896 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. tower-diagnostics-20150731-0006.zip Link to comment
trurl Posted July 31, 2015 Share Posted July 31, 2015 Post a screenshot of Main. The diagnostic doesn't have any smart for your data drives, and I don't know what to make of the IDs of the data drives. Are they SSDs or something? And the smart for your parity isn't any good either. It says it is a 600PB drive. What is your hardware? Please be detailed. Link to comment
dieselpwr3d Posted July 31, 2015 Author Share Posted July 31, 2015 Hardware is as follows: IBM xServe x3550 m3 with dual L5640s, 32gb ram, 2x 147gb 15k 6.0gbps SAS drives (IBM branded), 2x 900gb 10k 6.0 gbps SAS drives (no labels but supposedly WD), 1 WD 1tb Red drive. All drives are the 2.5" versions. I'm using the supermicro controller to connect to the sas backplane, and it is installed in the slot where the original M5015 was installed (front left side behind drives). Here is a screenshot of my main. I turned the server back on today, it recognized the WD red drive as a new drive and started a parity check. This will always pass, but no other ones will for some reason, even with no data written or accessed between. I don't know if the drive is dead, as I never had an issue with just the SAS drives connected to unraid. All of the smart tests that I've run on it in unraid have come back as good no errors. The controller sees it as a 1tb drive as well. As far as the drive identifications, I have no clue. They used to be part of a raid array (not counting the WD red drive), but I can't imagine that it would cause the drive ID to change. I could be completely wrong. I will post another diagnostic file and all the smart info for all the drives once the parity check finishes again - it will be another couple of hours. Link to comment
dieselpwr3d Posted August 1, 2015 Author Share Posted August 1, 2015 This is the info from my parity drive as it stands after completing the parity check earlier today. smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD10JFCX-68N6GN0 Serial Number: WD-WXK1EC4FN0N4 LU WWN Device Id: 5 0014ee 65af70a4d Firmware Version: 82.00A82 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Jul 31 21:55:00 2015 EDT 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (18720) 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: ( 209) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control 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 179 179 021 Pre-fail Always - 2041 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 9 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 100 100 000 Old_age Always - 132 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 - 9 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 104 194 Temperature_Celsius 0x0022 121 114 000 Old_age Always - 26 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 200 200 000 Old_age Offline - 0 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 Short offline Completed without error 00% 126 - # 2 Short offline Completed without error 00% 126 - # 3 Short offline Completed without error 00% 126 - # 4 Short offline Completed without error 00% 46 - # 5 Short offline Completed without error 00% 46 - # 6 Extended offline Completed without error 00% 45 - 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. I'll get this once the drive is readded to the array, and the parity check is done. Then later on, I get the read out in the first posting here. It only seems to be the WD drive. I never had an issue with the SAS drives. Link to comment
dieselpwr3d Posted August 1, 2015 Author Share Posted August 1, 2015 After posting that information last night, I checked the array this morning. I'm back to the original smart error saying it's a 600 PB drive, and the array is down. I've attached another diagnostic file. Could this be a controller issue or is my WD 1tb drive cooked? If you're needing more info, what do you need? tower-diagnostics-20150801-0904.zip Link to comment
Bungy Posted August 2, 2015 Share Posted August 2, 2015 Can you connect the m5015 again and see if you have the same issues? Link to comment
dieselpwr3d Posted August 4, 2015 Author Share Posted August 4, 2015 Sorry for the delayed reply, I've been trying to find a sitter these past two days. A process almost as frustrating as dealing with this issue, lol. I can try to hook back up the m5015, but I may have to redo the firmware on it. I had started to follow directions for flashing the m1015 cards without realizing it was not the right card. I would have to flash it back to it's original rom and bin files to do so. I'll try that a little later on today and report back. Thanks. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.