So I have been running unraid for almost a year now, my configuration is as follows

 

1 SATA Parity

4 SATA Capacity

1 NVME Cache

1 SATA Passthrough to a Windows machine.

 

I also have a windows VM with a pass-through Nvidia3070 that I use as a remote gaming computer for my living room, office and tablets.

 

Recently I started using Jellyfin and bought a second Nvidia3060 card to use as an encoding card for it.

 

When I installed it, after the boot one of my HDs, came with Unmountable: Wrong or no file system, didn't change anything in the configuration of the HDs.

 

I ran the XFS check and it came back with

 

Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... ................................................................(dots continue for like 1000 lines, removing them)...........................................................................................................................................................................found candidate secondary superblock... unable to verify superblock, continuing... ...................................................(dots continue for like 1000 lines, removing them)........................................................Sorry, could not find valid secondary superblock Exiting now.

 

Since it didn't come back with any possible fixes, I decided to remove the GPU and see if that helped, no dice, even after removing the GPU, still came back as Unmountable: Wrong or no file system.

 

I am honestly at a loss here, I read that I should not under any circumstance format the hard drive, but don't really know what else I could do to recover it, I have a lot of data in here and around 20 different dockers with a lot of configuration behind them.

 

Thanks!

Did you do the check from the webUI or the command line? Easy to get the command wrong. 

 

Attach Diagnostics to your NEXT post in this thread 

I did it from the WebUI, no shell involved here.

 

I attach my diagnostics file.

 

I appreciate the help, thanks!

server-diagnostics-20221223-1503.zip

Why do you have SSDs in the parity array? SSDs in the array cannot be trimmed, and write speed is limited by parity.

Not clear there is any connection or disk problem, but shutdown, check connections, reboot, and try again to check filesystem on disk2.

 

Have you done memtest recently?

First question: Those were the disks I had lying around, is the read speed also dictated by the parity drive?

 

I did a full disconnection of everything, replaced all the SATA cables with new ones and did a memtest.

 

All comes green, cables are just out of the box and I purposefully used a different port to connect the failing drive, did check after the reboot and still the same issue.

 

I wonder if the block data just got corrupted somehow, is there a way to shrink the array without losing any information? Then I could re-add the disk as a new disk later.

 

 

Try running xfs_repair directly on the device, this will invalidate parity, but it's just to make sure the md driver is not interfering.

 

xfs_repair -v /dev/sdb1

 

Note that if you rebooted since the diags check that disk2 is still sdb

Sorry for the late reply, I got sick and had to drop this for a while.

 

Couple of questions before I run the command directly if you don't mind.

 

If the parity gets invalidated does that mean I lose all my data?

 

Do I have to run this in maintenance mode?

 

Thanks for all the help, I really appreciate it!

2 hours ago, Unbugspray said:

If the parity gets invalidated does that mean I lose all my data?

It means parity will have to be rebuilt if parity is bypassed in this way. Parity contains none of your data

 

https://wiki.unraid.net/Manual/Overview#Parity-Protected_Array

 

Only the disk being repaired is affected.

2 hours ago, Unbugspray said:

Do I have to run this in maintenance mode?

yes