Great! Now I mount the new Disk 9?

You assign the new disk 9 and start the array to begin rebuild. "mount" has a different and specific meaning.

Note that emulated disk9 has a lost+found share on it. Those are folders and files that repair couldn't figure out.

On 6/26/2026 at 12:00 PM, trurl said:

When you eventually rebuild disk9 you will get those same lost+found. ...

Linux 'file' command can try to identify what kind of data is in a particular lost+found file so you can try to open it in an appropriate application to see if you know what it is.

Done. Estimated rebuild finish in 15 hours.

Rebuild is complete.

Everything looks ok. I'll have to go through all of the lost+found files.

Attached another diagnostics, just in case

mrplex-diagnostics-20260701-1110.zip

Edited July 1Jul 1 by mrichards

Looks good, rebuild finished without any errors or warnings logged.

Thanks so much for the help, @JorgeB and @trurl !

I have 3 other drives that are very close to dying, so will work on moving the files off of those before this happens, again.

45 minutes ago, mrichards said:

work on moving the files off of those

Probably safer to rebuild to new disks.

Is there a high risk of losing data by moving versus rebuilding to a new drive?

Was hoping to hold off on buying more new drives for a couple of months, because I have to set up a better backup system.

With the 2 new drives, I'm at around 50% capacity.

Edited Thursday at 08:57 PM4 days by mrichards

4 hours ago, mrichards said:

risk of losing data by moving

Copy is faster and safer than move. Move is Copy from source to destination, then delete from source. Delete is a write operation, so that would be additional writing to suspect disk even though it is just updating the filesystem to mark the deleted blocks available instead of overwriting all the data. Also all writes update parity.

You can exclude the bad disk from user shares so there won't be duplicates, then when all files have been copied elsewhere, you can New Config to remove the disk and rebuild parity.

ah. ok. I misinterpreted. That's what I'm doing. I've already excluded the bad drives from user shares, and am copying the files from those drives.

27 minutes ago, mrichards said:

I misinterpreted.

Not sure what you misinterpreted.

8 hours ago, trurl said:

Probably safer to rebuild to new disks.

This is true, since the bad disk isn't involved at all in rebuilding to a new disk. It is replaced.

Less true if multiple disks are known to be bad, since all other disks must be reliably read to reliably rebuild a disk.

One of your disks had a lot more reallocated than is safe, and I suspect those had been increasing. Not clear if other disks are of concern or not.

That would be disk 8 with 12,000+ reallocated sectors.

Followed by disk 3 with only 12 reallocated sectors.

Disk 6 doesn't have any reallocated sectors, but has 88 current pending sectors.

Disk3 is probably OK then for now.