gnollo

Disk added succesfully. Checked the warranty for the Seagate disk that had read errors, expired in 2020! Interstingly, the disk is a 8TB, but Seagate states is a 6TB when I checked the warranty...

Very good point. I just shucked a 10TB WD elements and installed it as a replacement. Just run diagnostics and attached. tower-diagnostics-20260923-1828.zip.crdownload

And we are back. Disk disabled for read errors. Same disk! I have had enough and will buy another disk for now to see if it happens again with a new disk.

Notice [TOWER] - Data-Rebuild finished (0 errors)Duration: 1 day, 5 hours, 45 minutes, 18 seconds. Average speed: 74.7 MB/s

Data rebuild in progress

Last SMART test result: Completed without error

Ok so moving the disk from the previous slot in the Norco S500 caddi to a different norco S500 caddy, this one fed by a Sata cable from the motherboard (the other one comes from a 8 sata port card). Will check the disk Smart report next.

I had the same, with the same drive, twice, disabled because of read errors. I believe I actually moved it to a different slot to eliminate cabling issues. I was thinking of rebooting, moving a disk with no issues to a differnt empty slot and then rebuild the drive onto the slot that was occupied by the disk with no issues. Any objections? Also will run a smart test and share it before doing so. Any other suggestions welcome.

7 weeks later, 12 drives moved to XFS format, 68TB copied from drive to drive Removed drive 12 from the excluded list in Global Shares setting Turned Tunable (md_write_method) back to Auto in Settings>>Disk Settings Back in business, unless I have forgotten any other settings that need to be changed back? Thank you all for all your help and advice.

Ok so I followed the steps above and I am now ready to move the data over to disk 12 again, this time from disk 7. Couple of points 1) I was lucky that when I started the array again after switching the drives it recognised all the rfs disks as rfs, because clicking on the disk to change the mode from auto to rfs is no longer an option in this version of the OS 2) this time I had the option to format the drive to XFS, which was much faster than CLEAR process I had to use for the parity drive last week. Why did I not get the option to format the parity drive instead of clear?

sent 11.48M bytes received 308.27K bytes 18.43K bytes/sec total size is 9.11T speedup is 773,026.16 Check completed some time earlier today so pretty quick in comparison to the previous checsum attempt. TTerminal returned to the root@tower green command line. I will swap the disks, format the rfs one to xfs and start moving the next drive.

OK started the drive post move check using TTerminal with rsync -avhPX /mnt/disk4/ /mnt/disk12/ I can now see the files being listed one by one as it goes through Thank you all for your help.

No issues, first time that I get that message so I thought to share for those who have not upgraded to the latest version of unraid. Additional steps were listed on https://docs.unraid.net/go/convert-reiser-and-xfs I don't copy them all as I added the link above and the text is quite long.

Updated unraid to latest version, 7.2.3, and now I get a message about "Critical: Deprecated Filesystem The following array devices are using deprecated filesystems:" list of all my rfs drives Action Required: Migrate to a supported filesystem (XFS v5, BTRFS, or ZFS). View migration guide → Message on the guide is Any drives formatted in ReiserFS need to be migrated to another filesystem ASAP as they will not be usable in future releases of Unraid. Any drives formatted in older XFS versions need to be migrated before 2030. The only method recommended there is Via the WebGUI (Unraid 7.2+): Navigate to Main → Array Operation and stop the array Navigate to Settings → Global Share Settings. In the Emptying disk(s) area, select the disk(s) to empty and Apply. Note: this status will automatically be removed when the array is stopped. In Unraid 7.2.0, any data on this disk will be hidden from user shares until this status is removed. Starting with Unraid 7.2.1, the data remains available to user shares but new files will not be written to the disk until this status is removed. Navigate to Main → Array Operation and start the array On Main → Array Operation click Move (or wait until mover runs via its normal schedule) Mover will empty the disk, moving files to other array drives according to your Share settings. Note that files at the root of the drive are outside of any Shares and will not be moved. Check Tools → System Log for messages about any files that could not be moved due to being in use or a lack of free space

I have rebooted the server to clear all activities and restart the emby docker, as my family was rioting after one week of askimg me are we there yet? So I will restart the comparison on Sunday night to complete the check. I am going to go with -avhPX as I feel that the checksum comparison might be overkill, probably takes much longer than the command above. If you think I should have the checksum as part of the final comparison before I wipe the source drive, let me know your thoughts please.