sabarirjpm

The subsequent parity check completed with no errors. Thanks for all the help through out...

Event: Parity Check Tuning Subject: [TOWER] finished (187721164 errors) Description: Elapsed Time 22 hr, 18 min, 38 sec, Runtime 22 hr, 18 min, 38 sec, Increments 1, Average Speed 149.4MB/s Importance: normal This is what happened.. I did follow the second instruction where every disk was zeroed out and removed I don't remember seeing any errors in any of the drives. Have restarted the check again now and will let you know how it goes

@jorgeb Thanks for the reply. I do not understand. I have only one parity and followed the shrink array procedure by removing one disk at a time and every time I remove a drive I start the array saying that the parity is already valid. The parity should have remained valid as the zeroing of each of the drives would have written the same to the parity. After all the disks are removed from the array one by one, I did a parity check to check if everything is fine. That's when I noticed the above. So I assume that somewhere during the above process, I could have done something wrong. Correct me if I am wrong

Just to add, I shuffled the connectors when I removed the old drives and ordered them on the remaining drives

Ok now after repeating shrink array for 5 of my 2TB hard drives, removed them and ran the parity sync just to confirm that everything is fine and I see lot of sync errors that are corrected. The parity check is still in progress with another 10 hours pending with approximately 18 hours elapsed. Does that mean that somewhere while using the shrink array option I did something wrong? Attached are the diagnostics. Is my data safe? tower-diagnostics-20220821-0445.zip

I am consolidating the old 2 tbs to the newer 12 TBs. So atleast 5 of them will be removed. Will the disk be numbered disk2, disk 9, disk 10, disk 11?

Over the last week, did the following. 1. 4TB data is moved across using unbalance plugin. Was very slow but waited for it to complete. 2. Copied over the data from the 12 TB drive which was off the array to unRAID and added the 12 TB to the array. Again a time consuming process which involved the preclearing of the 12 TB drive. 3. Used the Clear an unRAID array data drive user script as mentioned in the shrink array procedure and cleared of one 2 TB drive. (Used the second option The "Clear Drive Then Remove Drive" Method) 4. Stopped the array after the dd command is completed (Could not see the progress in the UI. Had to ssh into tower and confirm that the dd command is no longer running.) 5. Unassigned the drive which was cleared 6. Made the unassigned drive as the cache drive. Started the array by confirming that the parity is valid Now I see that when the array is started, The numbering of the disks starts from Disk2(Disk1 was unassigned from the array and made as a cache). Is that expected? I haven't yet restarted the array yet. tower-diagnostics-20220815-0144.zip Attached are the diags. Please let me know if the steps followed are correct tower-diagnostics-20220815-0144.zip

Thanks much. Have the following to-dos. 1. Move the data from newly added 4TB on to other disks using Unbalance plugin and convert the filesystem to xfs 2. Copy over the data/ backups available in the temporary 12TB drive that I had off the array and move it to unRAID 3. Use shrink-array to consolidate few disks 4. Convert the rest to XFS 4. Use one of the left over 2TBs after the consolidation as a cache disk.. Will keep posted on the progress. Thanks all along for getting my array back on shape

Attached is the log after the Disk2 replacement with a 4TB. tower-diagnostics-20220805-1734.zip

Backing up the Disk 2 did not work as it threw continuous read errors and had to cancel. Proceeded without backup as it had mostly movies. Parity Swap, Disk 8 Rebuild done. It again had read errors while rebuilding Disk8. Swapped Disk2 with a 4TB drive and rebuilding is in progress. Attached are the logs after the rebuild of Disk8. Did I loose any data? tower-diagnostics-20220805-0617.zip

Will take the disk 2 backup. After the parity swap and rebuilding Disk8, while replacing the disk 2, I would like it to be in XFS how do I get it. According to the wiki, it will again be reiserfs. Eventually, would like every drive moved to xfs

Am using one of the 12TBs(formatted as NTFS and added to a Windows PC) that I have and moving the data over the network. Another 120 GB pending to be copied across for disk 8 which is emulated and another 2TB of disk2 to be backed up. Thought of completing the emulated drive, do a parity swap and then replace the data drive disk 2. Now I think I need to backup the disk 2 before doing a parity swap. Correct me if I am wrong

Started taking the backups of Disk 8 currently and while it is in progress, see read errors in Disk 2. Attached the diagnostics. With this now, I am worried what would happen during the parity swap. Any suggestions? tower-diagnostics-20220803-1549.zip

So you would like to backup the data in Disk 8 or in Disk 2 to begin with or both?

No got it as used drives. 3 Nos. SMART says healthy on this.

Yes. Can I just replace the data drive Disk 8 which is currently missing with this? I assume this would start parity swap. If this would work, would proceed based on your response

Please find attached the diagnostics. Also I am not building a new server. Going to upgrade my existing tower-diagnostics-20220802-1514.zip

@trurl Got two temporary 2 TB hard drives and unfortunately both of them were not healthy and the moment I popped those, I started receiving the smart errors and the missing disk went to the disabled state. Of the 3 * 12 TBs that I received, One of them is empty, can I just swap the older drive with the 12 TB? I am reading in the wiki that the parity swap will automatically happen when I pop in one of the 12TBs and the existing parity will then be converted to a data drive. Is it safer way to proceed? Assuming that it is possible, another question is how do I preclear the 12 TB(do I need to do this?) before I put it into use?

Hi Trurl. I now think that it is more complicated than I expected.. Received the hard drives just now. Will shortly test them first and I think I need assistance through out. Thanks for helping me out.

Just to reconfirm. I am planning to do the following 1. Setup a new system, get the trial of unRAID and setup 3 new drives 2. Copy over the data from the existing to the new setup over the network 3. Make a note of the drive assignments on the new server 4. Move the original flash with the license to the new setup, select new config tool and assign the drives according to the note on step 3 and make unraid aware of the new drive changes. Will the above steps work and help me in a successful migration? Assuming that another drive won't go down during the copy

How do I handle the license. Assuming that I take the newer build and the copy path

The server can be shutdown. I am planning to keep it shutdown till I receive the newer drives. Need to manage a temporary chassis and power supply for the newer build and am expecting it to be ready by early next week.

So you suggest a newer build and copy the data over? Will prioritize the failed, failing drives. Is that ok?

Disk 2 is reporting smart error and the report is attached. Disk 8 is currently in "not installed" state. This server is being used as a media server storage and mostly contains music, movies collected over years. When I ssh to the server and list the contents of /mnt/disk8 it shows the data. Am assuming that these are the ones which belong to disk 8 which is currently in "Not Installed" State tower-diagnostics-20220729-1724.zip

Diagnostics attached. I have no backups available currently. Should I use one of the 12TBs and take the backups of the failed, failing drives first? build 2 disk array and restore from the 12 TB back to the array or proceed with the step by step process? How do I identify which data is in which drive tower-diagnostics-20220729-1724.zip