Drive upgrade / fs / format concerns

[youngnapoleon]

Hey guys, I'm running the latest stable version of unraid & earlier in the week upgraded my 8tb parity to 18tb. This took awhile, but I ran into no problems. A day after that wrapped up, I swapped out/upgraded a 4tb data drive for that previous 8tb one. I followed the same (I thought) cautious process as I did for the parity. I swapped the drives, went into maintenance mode, then clicked sync after selecting the replacement drive in the appropriate slot. 8tb data build was a lot quicker than 18tb parity build lol.

 

Then I stopped array & started in normal mode, but the new drive, despite no errors etc in the sync & no problem with any of the previous drives, said it was unmountable, no fs (though it registers in the gui as xfs, lsblk confirmed no fs via terminal). I was SO close to just ticking the format box & going for it, then was like... Omg did I just nearly clear 4tb of data that parity would then take as gospel & I can't rebuild? I don't see what other option I have though, is it just horribly worded/explained in the gui? I am currently running through another sync & it's rebuilding from parity again in maintenance mode in the meantime. Maybe after this it will just work? 

 

Can anyone clarify if something is going wrong with the sync, or if I'm actually expected to 'format' & that it doesn't actually purge the drive of data? 

 

Thanks as always, gang

 

(also I'm writing this on my phone, so apologies for less than stellar formatting/everything.) 

Edited August 8 by youngnapoleon

[JorgeB]

Please post the diagnostics.
 

[youngnapoleon]

1 hour ago, JorgeB said:

Please post the diagnostics.
 

I have, for better or worse reboot since the original maintenance mode sync was complete, should I wait for the current one to finish before posting diag? 

 

(edit: I've uploaded current diagnostics, but will redo them once the latest sync is finished. Any advice on whether to get new ones right after, or should I start the array proper first?) 

illmatic-diagnostics-20240808-2357.zip

Edited August 8 by youngnapoleon

[JorgeB]

Check filesystem on disk4 and post the output of running it without -n

[youngnapoleon]

6 hours ago, JorgeB said:

Check filesystem on disk4 and post the output of running it without -n

I can do that, though I worry it will take my system offline for a whole extra day... So, to confirm & out of curiosity:

A) my original post doesn't show expected behaviour after a maintenance mode sync? 

B) even though the the array runs fine while emulated, & the sync presumably builds the disk from scratch, you're concerned it's a recurring xfs error? 

[trurl]

Just in case you have some other idea. FORMAT is definitely NOT what you want to do unless you don't want that data.

 

Filesystem check is what you need to do, and it often won't take a lot of time to complete.

 

So

7 hours ago, JorgeB said:

Check filesystem on disk4 and post the output of running it without -n

 

Be sure to do the check using the webUI and not the command line. Easy to get the command wrong.

 

Possibly the filesystem was already unmountable before you did the rebuild and you didn't notice. Rebuilding unmountable will always result in unmountable. We usually recommend filesystem check and repair before rebuild.

 

Also, I never do rebuild or sync in maintenance mode. You should be able to continue to use your server during rebuilds in normal mode, though performance will be impacted so large transfers should be avoided.

 

Sounds like you may still have the original 4TB disk with its contents. You could see if it will mount as an Unassigned Device so that could give another option for recovery.

[youngnapoleon]

Thanks for the explanations. It's still got a few hours to go for the current sync, can try the file system check soon. I forgot to mention in my original post I'd kicked one off yesterday, but when it was taking over an hour with no verbosity for me to understand, I became disheartened & stopped it. I do still have the original disk, so if that can still be loaded as unassigned, I guess a full actual format with the array running would be fine. Guess it'll be another nervous day at work constantly checking the Web gui lol. 

 

Thank you both, will update soon! 

[trurl]

31 minutes ago, youngnapoleon said:

forgot to mention in my original post I'd kicked one off yesterday, but when it was taking over an hour with no verbosity for me to understand

Did you do it from the webUI?

 

1 hour ago, trurl said:

Be sure to do the check using the webUI and not the command line. Easy to get the command wrong.

 

[youngnapoleon]

Indeed I did, all I did was remove the -n & kick it off. 

[youngnapoleon]

Here's the latest log if it's of any interest, but I think I'll call it a day. The fs check took around two hours & completed - with a ridiculously long log full of errors. Still at work, but judging by used space, it lost a lot of stuff. But it's all running, I'll run some more diags & keep an eye on things, see if I can get data off the previous drive, etc... & try to swap this out asap because I'm now untrusting haha. 

 

Thanks for your help guys, I'm open to any other advice

illmatic-diagnostics-20240809-1439.zip

[trurl]

2 hours ago, youngnapoleon said:

log full of error

 

17 hours ago, JorgeB said:

post the output

 

[youngnapoleon]

Yeah... I am keenly aware... I'm just kinda tryna work my around it & maybe understand where I went wrong/if it's something I did. But given the original disk still lives, I don't think I've actually lost anything, so I'm just counting my blessings