July 20, 201213 yr I recently purchased a new larger disk as part of an upgrade to my server. Before starting anything I ran a full parity check with no errors and pre-cleared the new disk. I then removed the old parity drive and began rebuilding parity on the new larger disk. I believe the parity rebuild finished. I remember my next step was to check parity to confirm that the upgrade completed successfully. However I didn't see the option available to me so I stopped the array. I'm pretty sure at this point disk2 showed an error (and may have been red). After several hours the array was still stuck trying to unmount all of the drives and I (perhaps foolishly) did a hard reset on the box. When I logged in I saw the parity is now orange and disk2 is showing up red and unformated (see pic). I've also included the SMART report for the drive in question as well as my current syslog. At this point I'm not sure what the best way to proceed is to recover. I can't say whether or not the drive redballed during the parity check or not. I do still have my old, in-tact parity drive. Nothing should have written to the array unless some plugin wrote a log (which would all be on the 'failed' drive). Any help would be greatly appreciated. smartctl --all /dev/sdd 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 === Model Family: SAMSUNG SpinPoint F2 EG series Device Model: SAMSUNG HD154UI Serial Number: S1XWJ1KZ214109 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Fri Jul 20 00:24:25 2012 UTC 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: ( 34) The self-test routine was interrupted by the host with a hard or soft reset. Total time to complete Offline data collection: (19947) 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: ( 35) minutes. SCT capabilities: (0x003f) 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 0x000f 100 099 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 071 071 011 Pre-fail Always - 9470 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 1638 5 Reallocated_Sector_Ct 0x0033 095 095 010 Pre-fail Always - 221 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 8 8 Seek_Time_Performance 0x0025 100 099 015 Pre-fail Offline - 13867 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 17789 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 3 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 14 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 347 13 Read_Soft_Error_Rate 0x000e 100 099 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 1 184 End-to-End_Error 0x0033 025 025 000 Pre-fail Always - 75 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 3 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 076 069 000 Old_age Always - 24 (Min/Max 24/24) 194 Temperature_Celsius 0x0022 075 067 000 Old_age Always - 25 (Min/Max 24/25) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 4206 196 Reallocated_Event_Count 0x0032 095 095 000 Old_age Always - 221 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 099 000 Old_age Always - 192 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 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 Interrupted (host reset) 20% 6695 - # 2 Short offline Interrupted (host reset) 20% 6678 - # 3 Short offline Aborted by host 30% 6678 - # 4 Short offline Interrupted (host reset) 20% 6678 - 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. log.zip
July 20, 201213 yr You can't downgrade parity from 3TB to 2TB without redoing the setup, which would invalidate your parity, making it impossible to data rebuild. The newer 5.0 versions have a "parity is valid" button, but i'm not sure how it would handle it in these situations. Your current parity didn't finish, it has a orange ball next to it. This is the same as "two drives failed", so you have data loss from my understanding. In theory assuming your running the latest 5.0 RC (I show B14 which I believe doesn't support this), you could run the new setup config, assign your old 2TB parity, assign your data drives the same way and then tell it parity is accurate. Then after the array starts, you stop array and unassign disk2, then replaced it with a new drive and start the array. I would think that this would rebuild it using the old 2TB parity. I really suggest NOT trying this until someone that has more knowledge can confirm this, it could result in you not being able to recover the data no matter what. Either way, the drive definitely needs replaced judging by that SMART result.
July 20, 201213 yr I've had a couple of instances like this, with multiple drives showing up as either unformatted or missing. A reboot solved these for me. That disk definitely needs to be replaced. In the worst case, you can go back to your original parity drive, but if the generation of parity on the new drive did complete successfully, you should be able to rebuild the drive from your new parity.
July 23, 201213 yr Author In theory assuming your running the latest 5.0 RC (I show B14 which I believe doesn't support this), you could run the new setup config, assign your old 2TB parity, assign your data drives the same way and then tell it parity is accurate. Then after the array starts, you stop array and unassign disk2, then replaced it with a new drive and start the array. I would think that this would rebuild it using the old 2TB parity. I really suggest NOT trying this until someone that has more knowledge can confirm this, it could result in you not being able to recover the data no matter what. This was my thought on how best to proceed. I'm guessing I should be able to update to the latest 5.0 RC to enable this procedure without screwing things up even more? Anyone have any other ideas or confirm that this is a 'safe' way before I give it a shot?
Archived
This topic is now archived and is closed to further replies.