Lost Cache drive and now lost shares

[Overlandr]

So I have a unRAID server and I decided I wanted to put a cache in it so I put and Nvme and a SATA m.2 in which all worked. I transfered all my photos on to it. As the appdata, domains and system are on preferred they were stored on the cache, but I thought it was fine as I had redundancy (I didn't back it up...) Then I rebooted and the NVMe drive wasn't showing up so I just wiggled it in the mobo which picked it back up, but now unRAID has lost all of the shares and isn't showing files. Im guessing I can pull my photos off the HDDs as it isn't RAID, but is there an easier way of fixing this?

It is especially annoying as in the shares folder, everything was green and no warnings of data loss. 

Edited September 13, 2019 by Matt Dumbrill

[JorgeB]

1 hour ago, Matt Dumbrill said:

but I thought it was fine as I had redundancy (I didn't back it up...)

Redundancy is not a backup, also if the pool was created on v6.7.x it wasn't redundant because of a bug.

 

Please post the diagnostics: Tools -> Diagnostics

[Overlandr]

I should have backed it up, but unfortunately I haven't. Also that's a pretty mean bug. I cannot post diagnostics at this time, but is there some way to fix the the system without hooking the drives up to a separate PC. Thanks for the reply. 

[JorgeB]

Can't see what's the problem without the diags.

[Overlandr]

OK, I'm going to be at university for a while without the server, so I'm going to have to put this on the back burner for a while. Thank you for your help. I will come back to this thread in the future. 

[Overlandr]

On 9/13/2019 at 9:29 AM, johnnie.black said:

Can't see what's the problem without the diags.

Well I have just got back and as I boot up the NAS, all the files now show up for some reason which is good. No idea why that happened, but I will be backing up the config files and running diag to see if anything happened. Also try to find a way to fix that Cache redundancy issue.

[Overlandr]

Here are the diagnostics nas-diagnostics-20191019-1442.zip . Definitely looks like there is something wrong with the cache.

[JorgeB]

One of the devices dropped offline, since pool wasn't redundant you should recreate a new pool, then fix the redundancy problem as explained in the link above, also see here for better pool monitoring, in case that device drops again.