This just happened and server is not able to spin up  (start)

 

I attached diagnostics file

 

server_a-diagnostics-20170211-1227.zip

I know I'm seeming impatient, but I have now tried just about everything i can think of that is on this server

 

One question, If i build a linux box can I use it to read the drives and get my data?

There's probably a filesystem problem on one or more of your disks, log doesn't show array start, so can't see which one, start in maintenance mode and check all xfs disks:

 

https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS

 

PS: there are a lot of call traces possibly SAS controller related, you should upgrade to latest unRAID.

Okay it had a disk error on MD1 however it seems to ave had a corruption problem on disk 3, I pulled the disk and checked it out thoroughly with WDdiag (I then ordered a replacement to have on hand) so after starting in maintenance mode it bagan a data rebuild, so i am letting that run its course.

 

I did run the xfs repair and it came up with this (SEE PIC):

 

And i haven't a clue what to do next

 

 

Rerun the xfs_repair adding the -L option.  Despite the warning the chance of any data loss seem to be minimal going from past experience.

It seems to be working, in order to run any of it (due to error on drive 3, I had to format that drive. I did the repair -L first and when the new parity scan is done (it did not keep parity) I will re-run standard repair/check and then upgrade to current version

 

i only lost 1.4TB of data and there is no way to no now what was on that particular disk, but I am sure I will find out down the road 

 

thanks for all the help, I will be replacing that drive when the new one comes in.

 

Thanks again,

Ice