theone Posted June 24, 2015 Share Posted June 24, 2015 Hi, I have 1 sector pending on one of my WD20EARS drives. I tried: * Stopped array * Removed the drive from array * Started array * Rebuilt drive After data rebuilt drive still has 1 pending sector. I am planning on buying 2 new 5/6TB drives to expand my array which is 99% full. one drive will be for parity and the 2nd for data. How should I proceed with the swap considering I have the pending sector still there? Link to comment
itimpi Posted June 24, 2015 Share Posted June 24, 2015 When you get the 6TB drives, then I would suggest they are first tested using the pre-clear.sh script. That will take some days with a 6TB drive but does give you confidence that they can be added to the array safely. One suggestion at this point is to do a swap-disable process where you simultaneously upgrade parity to a larger disk, and use the parity disk in the array. The one being replaced at this point being the 2TB drive with the pending sector that does not want to go away, When that completes OK you can work on clearing the pending sector without risk to your data and until it does you still have the existing disk to fall back on if any recovery action is needed. At this point you would be in a position to add the new 6TB disk to the array for additional space. You now want to work on the 2TB disk and try to clear the pending sector. You could put it through some pre-clear cycles to see if that helps. You could also run the manufacturers diagnostic software against it. If the Pending sector cannot be cleared then you do not want to use it in the array. While you are at it check the other SMART attributes look OK. Link to comment
MrLondon Posted June 24, 2015 Share Posted June 24, 2015 I had on one drive 102 pending sectors and after running preclear these 102 pending sectors are gone. Link to comment
theone Posted June 24, 2015 Author Share Posted June 24, 2015 One suggestion at this point is to do a swap-disable process where you simultaneously upgrade parity to a larger disk, and use the parity disk in the array. How is this achieved? Link to comment
itimpi Posted June 24, 2015 Share Posted June 24, 2015 One suggestion at this point is to do a swap-disable process where you simultaneously upgrade parity to a larger disk, and use the parity disk in the array. How is this achieved? It is covered here in the wiki. Link to comment
theone Posted June 24, 2015 Author Share Posted June 24, 2015 I see that the first part of the swap-disable is to change the parity drive and run a parity sync. Won't the pending sector create an issue with the parity sync? Could it cause data loss due to the pending sector? My current parity can compensate for the read error (pending sector). What does it mean if in my current configuration I run a parity CHECK and no errors are reported? Link to comment
itimpi Posted June 24, 2015 Share Posted June 24, 2015 I see that the first part of the swap-disable is to change the parity drive and run a parity sync. Won't the pending sector create an issue with the parity sync? Could it cause data loss due to the pending sector? My current parity can compensate for the read error (pending sector). What does it mean if in my current configuration I run a parity CHECK and no errors are reported? I think you are looking at the wrong sequence of steps. The swap-disable is not the first option in that section - and you will see that it does NOT start with a parity sync, and involves swapping both disks at the same time. The sequence of steps it shows is: 1. Stop the array. 2. Power down the unit. 3. Replace the parity hard disk with a new bigger one. 4. Replace the failed hard disk with you old parity disk. 5. Power up the unit. 6. Start the array. Link to comment
theone Posted June 24, 2015 Author Share Posted June 24, 2015 I see that the first part of the swap-disable is to change the parity drive and run a parity sync. Won't the pending sector create an issue with the parity sync? Could it cause data loss due to the pending sector? My current parity can compensate for the read error (pending sector). What does it mean if in my current configuration I run a parity CHECK and no errors are reported? I think you are looking at the wrong sequence of steps. The swap-isable is the third option in that section - and you will see that it does NOT start with a parity sync, and involves swapping both disks at the same time. The sequence of steps it shows is: 1. Stop the array. 2. Power down the unit. 3. Replace the parity hard disk with a new bigger one. 4. Replace the failed hard disk with you old parity disk. 5. Power up the unit. 6. Start the array. Can anyone confirm that the swap-disable works without problems on unRAID 6? Will the array automatically detect the old Parity disk as a data disk and then proceed to do the swap-disable process? I assume what happens is: * Parity is copied from old Parity disk to new Parity disk * Data, which was located on discarded old data disk, is reconstructed on old Parity disk. Correct? Link to comment
limetech Posted June 24, 2015 Share Posted June 24, 2015 I see that the first part of the swap-disable is to change the parity drive and run a parity sync. Won't the pending sector create an issue with the parity sync? Could it cause data loss due to the pending sector? My current parity can compensate for the read error (pending sector). What does it mean if in my current configuration I run a parity CHECK and no errors are reported? I think you are looking at the wrong sequence of steps. The swap-isable is the third option in that section - and you will see that it does NOT start with a parity sync, and involves swapping both disks at the same time. The sequence of steps it shows is: 1. Stop the array. 2. Power down the unit. 3. Replace the parity hard disk with a new bigger one. 4. Replace the failed hard disk with you old parity disk. 5. Power up the unit. 6. Start the array. Can anyone confirm that the swap-disable works without problems on unRAID 6? Will the array automatically detect the old Parity disk as a data disk and then proceed to do the swap-disable process? I assume what happens is: * Parity is copied from old Parity disk to new Parity disk * Data, which was located on discarded old data disk, is reconstructed on old Parity disk. Correct? "Should Work"tm Link to comment
theone Posted September 2, 2015 Author Share Posted September 2, 2015 Because the drive was not RED I had to do some additional steps as described in the Wiki to make it RED: NOTE: Swap-disable (copy) button will not appear if your drive is not red. Scenario: One data drive (2TB) in slot 5 is having issue with read/write but not yet RED, Replacement drive is 3TB while current parity drive is only 2TB in slot 1. The steps are as below 1. Identify drive serial number from UNRAID GUI 2. Shutdown and Power off Unraid server 3. Replace parity drive (2TB) with new 3TB drive in Slot 1 4. Remove faulty 2TB drive in slot 5 and replace with the old 2TB parity drive just removed from step above 5. Power on Unraid Server From the GUI (5.0.5) 1. UnRaid GUI will show 2 Drives red 2. Select the original parity drive (2TB) as parity 3. Select the "faulty" drive in slot 5 and select No-Disk 4. Start the array - GUI will show red stated No-Disk 5. Stop the array 6. Select the newly install 3TB drive from parity drop down in slot 1 to become the new parity drive 7. Select the old parity drive 2TB to be the new replacement for faulty drive in slot 5 8. Copy button will appear instead of start Array. 9. Click Copy to start Swap Disable function where the old parity (2TB) will copy over to the new parity drive (3TB) The server has completed the parity copy and is back online rebuilding the data on the previous parity drive from the newer and larger parity drive. Nice feature Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.