Hi Thanks for reading. i started having i/o issues preventing sabnzbd and other programs writing to the array or cache. a reboot fixed these for about ten minutes but kept occuring, i tried cables and reboots etc and during this a disk (external) went offline and i had some trouble getting it back online which i did eventually. during this i through fault of my own created a pool between two caches then reverted but consequently wiped both drives aswell as the external as it was saying they had unmountable file systems. they are all remounted now and seemed to be working, until i started trying to rebuild everything (realised my appdata backup was deprecated so from scratch) and i still have these errors i cant even create a share as it fails each time disk checks also reveal file system errors on multople disks.

i am happy to start from scratch if needs be on an os level but i would rather not lose all my data. it is recoverable but consists of nearly 20tb.

i honestly dont know where to start either fixing or restarting and was told to head here and post my diagnostics.

thanks in advance for anyone willing to help

maynardserver-diagnostics-20230808-1131.zip

Replace cables for cache SSD, check filesystem on disk8 and post new diags after array start.

cache is nvme in m.2 slot find attached result of check filesystem and new diagnostic

 

disk 8 check.txt maynardserver-diagnostics-20230808-1245.zip

8 minutes ago, mark_s_maynard said:

cache is nvme in m.2 slot

Not that one, this one:

 

Aug  7 23:35:59 MaynardServer emhttpd: import 30 cache device: (sdi) PNY_CS900_240GB_SSD_PNY21142104090104EA6

 

i can do that later as i am not near the server but its not part of the array or cache its an unused seperate cache 

59 minutes ago, mark_s_maynard said:

but its not part of the array or cache its an unused seperate cache 

Not sure I follow, it's assigned to an Unraid pool, appdata has some files there, and it's the device that's is dropping offline, so it can cause issues with at least some containers.

that device shldnt be part of the pool im not sure how that happened and it only has 4.75 mb on it. i have removed it completely as i dont really have any need for it

But like mentioned there were appdata files there, make sure they are not needed, and that filesystem going read-only due to the device dropping would cause issues with at least the appdata share, other than that the only other issue present that I could see were the disk8 fs issue, that should be fixed after running xfs_repair.

 

 

due to deprecated plugin and not checking on my part the entire appdata folder was cleared out and have to start from scratch anyway. so providing im not overly concerned about the appdata folder if i remove the troublesome drive and start again and run xfs_repair you think i should be back up and running. also sorry to be a noob but how do i run xfs repair? is it gui or cmdline?

 

Yes, click the check filesystem link.

ok took me a while to figure out xfs repair but i ran it and running -n now doesnt spit any errors so im going to spin it up and fingers crossed it will all work fine now, thankyou for your help