Ilgrank

Whoops :) Read your post too late. The sync completed after 14 hours.. but it did complete without errors. So, checking the help, indeed -F forced a Full Resync of the array.. well, I hope I had no Read error during the process.. Just out of curiosity.. since I do still have the original drives,parity and content files.. If you were me, would you just copy the old parity and content file over and do a re-sync? Thanks guys!

Sorry for the double post :/

Update: Seems to be doing a full parity? (how do I get for certain?) Since after 5 hours is at 50%..

Update: Seems to be doing a full parity? (how do I get for certain?) Since after 5 hours is at 50%..

whoops.. it was existing, but permissions were insufficient. Fixed that, I was prompted with Too many disks have UUID changed from the latest 'sync'. If this happens because you really replaced them, you can 'sync' anyway, using 'snapraid --force-uuid sync'. Instead, it's possible that you messed up the disk mount points, and you have to restore the mount points at the state of the latest sync. I re-run then with snapraid -E -F --force-uuid sync and now it is running.. fingers crossed since I don't...

whoops.. it was existing, but permissions were insufficient. Fixed that, I was prompted with Too many disks have UUID changed from the latest 'sync'. If this happens because you really replaced them, you can 'sync' anyway, using 'snapraid --force-uuid sync'. Instead, it's possible that you messed up the disk mount points, and you have to restore the mount points at the state of the latest sync. I re-run then with snapraid -E -F --force-uuid sync and now it seems to be running.. fingers crossed since...

yep, it is existing and it is empty

Thanks Leifi and David! @Leifi: I tried first your suggestion: snapraid sync -E -F but as you guessed, it is still complaining about the missing disk. Even adding a 'fake' disk as an empty directory in a non-snapraid disk fails tho: L:\>snapraid sync -E -F Self test... Error accessing 'disk' 'L:\W\' specification in 'L:/W/' at line 37 @David : Recalculating the entire parity is surely an option, but I would take it as a last resort.. Thanks!