superloopy1

did this ever get answered and is it a possibility at all?

I'm expanding the system by adding a larger drive to replace a smaller one having ran a parity check to ensure all data is ok. If the expansion process fails and the disk is being emulated how do i proceed. The original data disk is at this stage outside of the array but fully functional.

So, how do i get the original 14TB drives data back onto the array without losing it? Is it a case of mounting it externally and purchasing another drive for the array which then takes a move of the data, if so that seems a very long winded fix?

Thanks. so, data is intact on smaller, outgoing disk as to be expected. but if you just wanted to put it, and the contents, back into the system then how do you get the data back in sync? wont reinserting the disk just prompt to overwrite?

.... during a drive expansion ( i've removed a 14TB drive and am replacing with an 18TB) there is a problem? I still have the original 14TB drive. Is it simply a matter of switching it back in and restarting? Should the drive expansion be running in maintenance mode to avoid any detrimental activity should the expansion go belly up? Jsut sitting here watching it slowly restore over some 2.5 days!!

That 'other' parity was done in maintenance mode, thanks. Update ... just to say that I did do exactly that AND it logged 23 errors from switching over parity disks i suppose. Still running the 'old'parity recheck as i write so absolutely nothing gained and fours days of electricity wasted ! That did the trick, i'll not forget it, ta v.much!

I always knew there'd be a fix, thanks! So, new config, maintain all slots then the tick box. I'll let you know ...

Yet again, issues with parity. I've reached a point where advice is needed. Scenario .... upgrading my single 16TB parity drive to a larger 18TB drive. Simple eh. So, I ran a full parity check, all clear, on the existing drive. Unplugged old parity from existing cables and inserted larger drive. All went well, allocated new drive as parity and restarted in maintenance mode safe in the knowledge that my old 16TB drive could serve me well in case of problems. Parity sync running for hours then lost connection at around the 15hours to go stage. Nothing. Hooked up monitor, all dead. Fearing the worst I powered off and on and everything back as it was so away I went again. Same routine, maintenance mode and same thing happened although a little later in the sync process. So, I gave up and put it all back together with the old 16TB parity thinking I could ust switch and go. BUT ... I can reallocate the drive to parity but can't see any way to avoid having to resync and therefore losing parity on the old disk. That's not how I thought it worked. Can't see anywhere to say 'trust existing parity'. Am I missing something? What's the way forward without wiping out my trusted parity drive? Any advice would be appreciated. Thanks!

, 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?