superloopy1

, sorry that read wrongly. how can dual parity be better at protecting the array when parity check running in maintenance mode moreorless is the question.

what changes to make it 'less iikely' to drop a disk though when using dual parity?

thanks for replying. is this 'parity rebuild in maintenance mode' documented anywhere?

Nobody had to do this then?

Guys, i've reached a stage where i need to move a 12TB drive out of my array, hopefully without incident. I have read the manual and have a question. Is a there any way that the current dual parity can help me here or is it the case that once i remove the outgoing drive and a new parity sync gets underway that's it, i'm on my own so to speak. Can it be made to work in a similar manner to adding a drive when dual parity will protect me in the event of too many drives failing. I'm just a bit wary that i've been hammering the array recently and possibly this one more parity sync could be one too many. Ironically the outgoing drive is going towards extending a second array to accommodate a further backup of this array which currently only gets a backup of 50% of the contents. Am i over thinking this and should i just get on with it and sod the consequences?

i have this problem too ... but no solution??

'Remove the mover tuning plugin' ..... just wondering, having just had the same experience of moverNOT moving any data until plugin is removed, just why this is needed and i'm assuming I dont add the plugin back?

Ok, whats the concensus here about which tool is best suited to backing up VM's in their entirety. I'm just about to setup a couple of vms and dont really have the expertise to 'fiddle' in the event i bork them. Is there something along the lines of Appdata backup/restore?

Thanks. Had already tried a known good cable and also swapped between other arraydisks, still the same. So, i'm rebuilding to a new disk as i cant afford an unprotected array for much longer. Maybe time to add a second parity as the drives are now aging. I'll take a look at the old drive once this is complete. Cheers!!

As per the title. I've checked a few similar posts which always begin ..... diagnostics please. So here they are, attached. The disk is spinning no problems there, i have swapped out the sata cable without any luck but looking at the syslog it seems to have no problems on startup, being a clean mount? I do have a spare disk and most of the contents are now secured. Just looking not to have to switch it in and rebuild if possible. Thanks for any assistance ... tower-diagnostics-20240103-2045.zip

Thankyou for a speedy reply!

Can someone explain to me what happens when you have more than two cache assigned drives (one SSD named cache and one nvme drive named cache_nvme) and then run mover? Will it move both 'cache' drives contenst to the array sequentially? Or, has the nvme drive contents have to be manually moved? Apologies for a simplistic question, no doubt yet again, but i'm way behind with Unraid these days. having just added a nvme cache drive i now need to move 'stuff', just how exactly? Thanks!

Guys, I need help. I moved my appdata folder off my cache disk as it was failing. Installed a new ssd and moved apodat back and now both of my 'arr' dockers are failing to start with an error to do with 'malformed database' which seems to be pointing at database corruption?? What's the restore procedure, anyone able to help. Other dockers are just fine, enby plex etc.

Thanks again! Yes, its disabled. Much appreciated.

The file is 'mnt/cache/docker-xfs.img' and is freestanding .... so, its ok to just 'move' it ?