trurl

Maybe diagnostics will tell us when we get them.

Parity looks OK now, but it looks like there may be some corruption on emulated disk4 even though it is mounted. And maybe a connection problem with disk2, which might be the cause. Check connection on disk2 then post new diagnostics before restarting the rebuild.

Diagnostics is downloaded to your computer as a single ZIP file. If it appears to you as a lot of individual files, it is bacause your computer automatically unzipped that single ZIP file. We want that complete, single ZIP file. Nobody is going to download all those individual attachments. Please look for that single diagnostics ZIP file wherever your browser saves downloads, and attach to your NEXT post in this thread.

Post new diagnostics

How long have you let them dry?

Doesn't look like you had run Mover yet.

I think you somehow got diagnostics before it had finished booting. Post new diagnostics.

Apr 6 11:09:27 Tower emhttpd: skipping invalid cfg pool name: ._cacheThis makes me wonder if your Mac added some of those annoying hidden files to your flash drive. Speaking of flash, lots of FSCK files there, so there has been some corruption. Do you have a current flash backup? Might be a good idea to do memtest just in case.

Since that isn't an assigned disk not sure how relevant it is to other problems. Obviously it can't be used for anything. All array data disks mounted. Nothing assigned as parity. Cache, user shares, docker.img, libvirt.img all mounted.

👍

These are the 3rd of my 3-2-1 backup. 1st is working files on PC, 2nd is nightly backups to Unraid. 3rd is external backup from Unraid to drives that are leftover from upsizing drives in my Main server. I have 4 of these in rotation and the important files will completely fit on 2TB, personal files, photos, music. My backup server is just for the unimportant media files, etc. My backup server is made of parts including drives leftover from upgrading my main server. My unimportant media files probably total about 20TB.

My offsite is just external drives that are stored offsite.

Post a screenshot of those settings

So it wasn't a clean reboot. Attach Diagnostics ZIP to your NEXT post in this thread. Setup syslog server

Do you have an attached keyboard and monitor?

Even less time if it fails.

I only power up my backup server to do backups, and those aren't important so I do them whenever. The important backups go offsite. Self-test only shows progress every 10%, so don't think it is stuck if you don't see progress frequently. It won't take as long as the full preread, clear, postread you just did. Maybe more like just the clear portion.

Always remember to get diagnostics before rebooting

For future reference, no reason to do any of that from the terminal.

Technically you can move while syncing parity, but it will slow down parity rebuild and slow down mover since it would have to seek to the place it needs to read/write for the move, and seek to the place it needs to write parity. So, just let if finish parity sync. If you lost system share and it had to be recreated that would be the most likely reason for all dockers to be gone. As long as you have appdata, they can be easily reinstalled and work just as before by using Previous Apps on the Apps page since the executable code stored in docker.img will just be downloaded again.

Yes I know, but it already had files on the array. "Only", won't move anything, since there is no Mover action because no Secondary

Your Docker/VM related shares - appdata, domains, system - have some files on the array. Possibly some of those files were on the now gone disks. Ideally, those Docker/VM related shares would have all files on cache or other fast pool, with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. Go to Settings and disable Docker and VM Manager. Set appdata, domains, system shares to Primary:cache; Secondary:array; Mover action:array->cache. Go to Array Operation and run Mover. Wait for it to complete, post new diagnostics.

Run another extended self-test when preclear is finished.

Click on the drive in Unassigned Devices (for example, mine is listed as dev2), then, under Attributes, your can see whether the Pending Sectors are now Reallocated Sectors. Under Self-Test, you can do a SMART extended self-test, and Download a SMART report. If you want to preview these features while waiting for the preclear to finish, it works the same for all your drives, such as in the array. But, if a disk is spundown, you will have to spinup to get it to read the Attributes.

Reboot shouldn't be necessary, but sometimes it seems to help to restart the array to get the shares "refreshed".