thedroid

I would like to replace and existing drive with a larger unit but also change the drive from Reiser to XFS. I have moved all the data from the existing drive to another location My question is can I 1. stop the array 2. replace the drive with the new one 3. set file system of the drive to XFS 4. restart the array 5. format unmountable drive and have the array work without requiring a parity rebuild or will I have to skip step 2 (keeping the original drive in place) continue with 3-5 6. stop the array 7. replace the drive 8. Assign the new drive 8. restart the array to do a parity rebuild.

Done when drive was unattached from the array list. In any event I am back up and running, thanks to yourself and itimpi. Had to do a rebuild. Lost the data on the one drive, but thankfully it was not much and I had a backup of most of it. The rebuild is currently about 75% through but all appears to be well so far. Thanks again for the assistance. Ill chaulk it down to a learning experience.

Don't think so, but not impossible.

Upon further review looks like I screwed up and the emulated drive is actually showing up as empty, and I have already formatted the actual physical drive so it looks like that data is lost. Not a real issue in this case, because the drive did not have very much data on it to begin with. Lesson learned. What is the best way to move forward with getting the array back in order without loosing the data on the other drives. Currently I have stopped the emulated array to be on the safe side.

Thanks. Will review link

Diags attached mediaserver-diagnostics-20220607-0945.zip

The *emulated* drive is functioning and the array starts ok in "Array unprotected" mode. Where i run in to problems is trying to add back that actual physical drive so that I can rebuild the array back to it.

Yesterday a drive mysteriously dropped from my 21 disk array and the array is now running in emulation mode. I brought the array down. Did a smart test extended on the drive which reported no errors. Did a "destructive" through test on the drive by writing/reading/verifiying the entire drive and no errors were found. Tried to add the drive back to the array to do a rebuild, but unraid refuses to add the drive back. I can add it to the slot, but it always reports an unmountable drive error. Any suggestions?

smartctl below and syslog attached. Thanks for your help smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Black family Device Model: WDC WD1001FALS-00E8B0 Serial Number: WD-WMATV2378672 Firmware Version: 05.00K05 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: Sun Oct 23 04:04:57 2011 Local time zone must be set--see zic m 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (18600) 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: ( 214) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) 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 199 199 051 Pre-fail Always - 20429 3 Spin_Up_Time 0x0027 253 229 021 Pre-fail Always - 1008 4 Start_Stop_Count 0x0032 091 091 000 Old_age Always - 9320 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 4 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 9947 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 994 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 49 193 Load_Cycle_Count 0x0032 197 197 000 Old_age Always - 9270 194 Temperature_Celsius 0x0022 110 096 000 Old_age Always - 40 196 Reallocated_Event_Count 0x0032 196 196 000 Old_age Always - 4 197 Current_Pending_Sector 0x0032 199 199 000 Old_age Always - 163 198 Offline_Uncorrectable 0x0030 200 199 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1591 200 Multi_Zone_Error_Rate 0x0008 200 137 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 Conveyance offline Completed without error 00% 5628 - 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. txt.zip

The syslog reports "controller in dubious state, performing PRT_RST" and "device reported invalid CHS sector" along with various other related messages. The parity would not have been valid, I dont think. Heres the rundown of exactly what happened. 1. UPS died causing the unraid server to power off improperly 2. Upon powering back up, unraid started a parity check. 3. 20% completed in the usual amount of time, but the system took 4 days to reach 21%. After an additional week it was still on 21% and the web interface was unresponsive. 4. Tried to power down using POWERDOWN from command prompt, it when through most of the motions, but did not actually power down, after a day I pulled the plug. 5. Powered back up, checked the syslog found the error mentioned above. 6. Shutdown the system. 7. Installed the "bad" drive in another box, mounted as readonly to see if I had any problems reading the drive. It seemed to work ok. 8. Reinstalled the "bad" drive, swapping its position on a different cable, controller and power with another drive in the array 9. The problem followed the drive, parity rebuild seemed to halt this time at 6%.

I was in the middle of a parity rebuild when a drive flaked out. I can replaced the drive, but I dont think that I can trust the parity information. The flakey drive works well enough so that I can copy some/most of the info off using another machine. My question is what happens to the information on the good drives when I put in a replacement and rebuild the array with the possibly bad parity information.