ElliotJMD

That's a screenshot of the lost+found compute, from what I can tell 99% of it is music I was ripping before the original drive died and the rest of it is some blender assets

redmatter-diagnostics-20220810-0158.zip These are the latest. Interestingly, the emulated drive is actually now showing again and is accessible and appears to be working, it didn't work when I rebooted the server about an hour ago and I haven't changed anything since.

So I've tried running -L and I don't think I got anything out of it, it spent about a minute writing to the parity drive at 50MB/s then stopped and it told me there was an error and to run the command again, the second time it finished but doesn't appear to have actually done anything other than the XFS file system corrupt message being gone in the Main tab. Unless there's another step I need to do? Or is this something that I need to actually put in a new HDD for it to rebuild onto?

Never really thought about that but that makes perfect sense

Iirc, last time it was slightly under 1.5 days. It starts off at somewhere around 200MB/s and by the end slows down to less than half of that (no idea if the slowing down thing is normal)

Do you reckon I should run the -L parameter as a kind of last ditch attempt?

I'll also create some copies of some of the files that are the most important to me

I did the check but I haven't done the repair yet, I wasn't exactly sure how to do it even reading the docs although I did get an error message that sounds somewhat useful to somebody that understands it ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

Most of the data on the missing drive can be gotten again, I don't think there was any substantial data on the drive that was important. I mostly use it as a local repository of all my data. The rest of the array currently does not have any backup as I kept putting it off as I worked it out to take somewhere in excess of two years on my internet to backup all of my data, I do have a couple TBs of portable HDDs that I can copy super important info onto in the meantime if you believe it is worth it. If there is a chance of getting the data back it would be preferable even if it leaves me with a bunch of corrupted files, depending what is on the drive I would actually be perfectly contempt with only retrieving a table of contents. An additional, after a lot of effort with Amazon, I have a new HDD coming in two days so if this data is recovered then I won't be emulating the drive for very long.

redmatter-diagnostics-20220809-2104.zip That's the diagnostics after starting the array normally

Yes, I was fully aware I was running without protection. I have been missing the drive for approximately two weeks but I have only had the array online for a total of slightly less than two hours when I needed to access some files that I needed. Although you are correct with it not being necessarily a good idea, due to space and hardware constraints it is unfortunately the only possible way to go for me. I do not know what will happen if I try to write data to the array, as soon as I noticed the emulated disk missing I immediately stopped the array to prevent any further damage

Apologies, didn't realise there were two different check buttons. I ran the check filesystem one and this was the output of it, it's quite long so I've attached it as a text file Disk4 Check.txt

The check just finished this morning and it found no errors, there isn't a repair button on this page that I can find and the emulated drive still isn't showing up as storage in the array. I've attached some screenshots of the page again

Okay, thank you. I will start a check now

Thanks for the response, As I am currently without the drive do I still want to follow that and run a check even with it showing the emulated drive error?