So a couple days ago I encountered fs corruption on my cache drive.  Restarted the array in maintenance mode, ran xfs_repair, got things going again.  Didn't think too much of it because the smart report on the drive appeared good.  Today I wake up an my dockers aren't running, looked like something similar happened, so I stopped the array rebooted and was welcomed back with the "Unsupported partition layout" error on my cache drive. 

 

Looks to me like there's simply no partitions on that drive anymore:

 

At the moment, I've got another drive standing by in the machine ready to be a new cache drive, but my question for the group is, is there anything I can do to recover what was on the cache drive?  I'd made the mistake of not installing the CA Backup Appdata plugin, so otherwise I think I'll have to go reconfigure all my dockers

 

Any help would be appreciated.  Array is sitting in maintenance Mode at the moment and I haven't done anything to the offending Cache drive.

unraid-smart-20191209-0925.zip unraid-diagnostics-20191209-1520.zip

Edited December 9, 20196 yr by stanger89

That error would imply something changed in the MBR or the partition layout making it a non standard parition, that should never happen in normal use, but if that's the only problem it should still mount with the UD plugin.

Firstly, thanks so much for the quick reply.

 

I installed the UD plugin, and when I stop the array, remove the Intel/sdh from the cache slot, it shows up in the UD section, but does not appear to be mountable:

Looks like the partition disappeared, so probably data it not recoverable, at least not easily.

Yeah, that was kind of my fear, was kind of hoping I was missing something.

Unfortunately yes, I missed that in the fdisk screenshot because it looked to me like you were cutting that part.

2 hours ago, stanger89 said:

I think I'll have to go reconfigure all my dockers

Your appdata is gone of course, but your docker templates are on flash. After you get cache and docker service going again you should be able to install your dockers just as they were (with no existing appdata of course) by using the Previous Apps feature on the Apps page.

Yeah I did that last time, since the FS corruption wiped out the docker.img file, but it's all the configuration in the dockers that's going to suck to reconfigure.

Well I had pretty good luck with Raise Data Recovery.  I actually think it's pretty much all there, just need to sort out the folder structure.  That said my most important dockers I found and restored the configs for.  Still sorting out a few others.  Actually looks like I got the rest too.

 

Anyway, got another SSD on the way to setup the cache to be a btrfs pool, and I need to sort out setting up the CA backup so this doesn't happen again.

Edited December 9, 20196 yr by stanger89

3 hours ago, stanger89 said:

it's all the configuration in the dockers that's going to suck to reconfigure.

I don't understand this part. Are you talking about settings within each specific application, or are you talking about the settings for each container on the Docker page? The settings for each container on the Docker page is exactly what the Previous Apps feature is about.

Yeah, I meant all the settings within each application, you're right of course reinstalling the dockers are easy since the templates are all saved.  I've used that a few times.