stratigary

This is quite odd as it definitely showed as xfs on the main screen for the 2 weeks it was in operation. I take it this where the issues came from. I know reiserfs is old and not recommended for new drives, but is there a reason I should switch right now? Could I add the new drive to my array as xfs (or suggested file system) and then shrink the array to fill that disk and remove the reiserfs disk?

@trurl Thank you so very much for your help, everything has worked well so far and it seems like I was able to recover from this event. Quick question though if you don' t mind. After reinstalling the old 3TB disk, I planned on zeroing out the 6TB disk that had the filesystem error so that I could possibly reuse it in the future. So, I popped it into a USB dock to use with unassigned devices and preclear it again. Oddly, the disk showed up as being half full with all the files intact and the filesystem listed was reiserfs when it was originally xfs. Is there something odd going on here or did I do something wrong when I originally upgraded the 3TB disk (reisefs) to this 6TB disk (xfs)?

Ah, that makes sense!! To answer your other question, I am somewhat familiar with working with files on the server using MC and/or Krusader but not confident enough I think. Your first suggestion sounds like a workable plan for me. To clarify, is this how I should do it: Remove corrupted disk assignment in the GUI to no device Shut down server and replace disk with original disk Start server and make New Config (should I preserve all current assignments?) Let parity rebuild and check for any errors on disks Remove original disk assignment in the GUI to no device Shut down server and replace original disk with new larger disk Start server and rebuild new larger disk from parity. I really do appreciate all of your help. I've been searching everywhere for this specific issue but I can't seem to find much. If there is anything I need to change here I would be happy to hear it.

Ok, this seems like the way to go but (please bear with me) could you please help me with a step-by-step. I've been using this system for years without issue and I'm afraid of doing something in the wrong order and making it worse. Currently, my other 4 drives are fine and contain all the shares and data minus what I lost on the corrupted disk. I have a copy of the data that was lost on the corrupted disk on a separate, but smaller, disk that I just pulled. I also have another disk the same size as the corrupted one I could use as well. What order of steps should I take using New Config to get this corrupted disk back in working order and then copy over the files to it that were lost? Thank you for any help you can provide!

Ok, might have some good news but I could really use your advice on how to proceed. I just realized that this disk that is corrupted (6tb) is one that I just installed 20 days ago to replace/upgrade a previous drive (3tb) and I still have this drive that hasn't been touched. Using UFS explorer on my Windows machine I can see that all the data is still on the old drive. What are the steps I should take to bring the new 6tb drive into good standing and then how to move the files from the older 3tb drive onto the fixed 6tb drive. I do have another 6tb drive that is brand new if using that in some way would be easier. I really appreciate any help you can give me!

Yes, I did run xfs_repair without the -n and I get the same result, bad primary superblock and searches forever and never finds a secondary superblock just ........ forever. I have some slightly out of date backups that I can work with, but it will be a pain. I do have one spare drive on hand that's the same size as the corrupted one. Are there any hail mary options I can try before I have to reformat?

I did what was suggested on this website. I started in maintenance mode and then clicked on the disk on the main screen. In the Check Filesystem Status I ran it as -n. That is when it said there was a bad primary superblock and searched forever and never found a secondary superblock. What is the best way to go about rebuilding this drive to recover the data? I can get a hold of a new drive to put in its place tomorrow, would that be the best option to do and then just rebuild it from parity? server-diagnostics-20220312-2323.zip

Returned home today and noticed that my Unraid server had shut down for some reason. Upon rebooting I noticed that Disk 1 (20 days old) was listed as "unmountable: not mounted". When I ran the xfx_repair it said "bad primary superblock - bad primary number!!" and then searched but never found a secondary superblock. Should I even bother to try and rebuild this drive and, if so, how do I go about this. When I choose the "format" option in the GUI it makes it sound like it will clear out the drive and then update the parity to reflect that cleared drive and I lose all the data. Or should I just RMA the drive and rebuild on a new one?

Good call, after a reboot I was able to run a parity check with the suspect disk unassigned and am now getting speeds between 40-50 MB/sec. I think that's where it should be, correct? Should I let this parity check continue or stop and wait for my new disk to arrive and rebuild? Thank you so much for all your help!!

Pressed "Sync" again and then grabbed the syslog (attached) server-syslog-20161219-1556.zip

My apologies, I didn't quite understand what you meant at first..I get it now. I just tried what you suggested: cancelled rebuild, stopped array, unassigned disk, started array. However, the only option I have after that is to run a Parity-Sync and/or Data-rebuild and, when I press the "sync" button the screen refreshes and nothing happens.

Ok, so here is what is going on so far. I stopped the rebuild, stopped the array and then shut down. I then switched sata ports on that HD to see if it was the problem. After a reboot and attempted rebuild the max speed never exceeded 11 MB/sec and hovered around 2 MB/sec. I also noticed that my Win 10 VM (which worked before this issue) now wouldn't start because it had an "internal error: Did not find USB device 5a4:1700" I found out that this is my USB3 card which does show up but now has a different ID of 1b73:1100. When I disabled then re-enabled the card in the VM manager the VM started working again. My new drive is scheduled to be here Wednesday so I guess I'll find out then if this is a drive issue or a motherboard issue. Is there anything else I can try in the meantime to problem solve this?

Unfortunately I don't have one on hand (now i know better) but I did buy one yesterday and it should be here by tomorrow or Friday. Should I let the rebuild continue running or should I stop it and wait for the new drive?

I've attached current diagnostic logs. Except for a few short bursts of around 11MB/sec the speed always seems to hover around 2MB/sec. This seemed to be the problem a few days ago when I noticed the parity check was going to take forever as well. server-diagnostics-20161218-2213.zip

So, I finally started the rebuild of the drive and it's telling me that it is going to take over 100 days to rebuild this. Any idea what is going on here, because I'm sure it shouldn't take that long to rebuild. I figured it was just something that happens when you start and lowers quickly as time goes on but the estimate is not getting any shorter, in fact it's getting longer.