cannondale0815

I haven't tried your script yet but wanted to thank you for contributing to the community! :)

Been running SnapRAID for many years and have had to occasionally replace a failing disk over the years. But in those cases it was always obvious, as the disk was completely dead. I am now getting periodic data errors and a message about failing blocks having been marked as bad. But no info which disk those failing blocks are related to. I'd like to replace that disk, but how can I find out which one it is? See below my latest output from a scrub: 100% completed, 1641092 MB accessed in 1:35 %, 0:00...

For as long as your OS (Windows 11) can see all disks as individual disks, it doesn't matter what enclosure you choose. But do not choose an enclosure that provides hardware RAID internally. If it does, make sure it can be turned off. The OS needs to see all disks individually, not as a single volume.

For as long as your OS (Windows 11) can see all disks as individual disks, it doesn't matter what enclosure you choose. But do not choose an enclosure that provides hardware RAID internally. If it does, make sure it can be turned off. The OS needs to see all disks individually, not as a single JBOD.

For as long as your OS (Windows 11) can see all disks as individual disks, it doesn't matter what enclosure you choose.

Whenever you change the size of your disks, you need to start replacing the partity drive(s) with larger ones first, then match the data drives thereafter. That has been my strategy in the past. So basically either option 1 or 2. Where do you see that an imbalance in drive sizes is discouraged? I don't think it is, for as long as your parity drives are at least as large as your largest data drive.

Whenever you change the size of your disks, you need to start replacing the partity drive(s) with larger ones first, then match the data drives thereafter. That has been my strategy in the past.

Answering my own question, I performed an rsync from the old drive to the new drive, then mounted the new drive under the mount point of the old drive, then a snapraid check, a diff and then a sync. Seems to have gone ok. sudo rsync -avxHAXW --numeric-ids --info=progress2 /mnt/Disk6/ /mnt/NEWDisk6/ > /tmp/d6_rsync.out Only thing that concerned me is that after the diff (before sync), I was told there were several thousand "restored" files. I assume that's because the disk was changed? 1020456 equal...