[Help] Folders disappeared until reboot, now files won't delete

[tallguyNJ]

F4-423 Version 5.1.406
TOS: 6.0.229-00147
(4) 12TB drives with one as a hot spare
(2) 512Gig M.2
TRAID

I have my Plex media in a shared folder. All of a sudden, while watching a video via Plex (running on a separate server), the entire media folder disappeared. All others shares folders were fine. I shutdown and rebooted the NAS and everything came back, but now, when I delete a file(s), they come back. It this is happening on all my shared folders and not just the one I had issues with.

Any thoughts on how to fix this and why it possibly happened in the first place?

Note: I noticed the Storage Pool is showing synchronizing, but it's taking forever.

[TMzethar]

The 5.1.406 you mentioned should be the TNAS PC version and not the TOS version.
It is recommended that you wait for the storage pool synchronization to finish and then see how is it going. Synchronization takes a lot of system resources and may make your Plex run slowly.

[tallguyNJ]

added TOS version above. I'm at 81.37%, so it may be done be done in the next 6 hours. I'll see what happens.

[tallguyNJ]

So the storage pool is now normal, but when I delete a file, it still comes back.
I went into TOS File manager with my admin account and tried to delete the file and I get an Operation Failed error.

On top of this, I can't copy files over from my PCs as it say the disk is write-protected. I even tried a test where I tried to create a new shared folder in the control panel, but nothing happened and the folder didn't create.

Update #2: Overnight a majority of my folders on the server completely disappeared. I did a reboot and they are back, but now the storage pool is doing another synchronizing started at 50%. This is going to take another 24+ hours to complete.

Anyone have any next steps?

[TMzethar]

Based on the system report you provided, we have identified that your 2-disk RAID0 Hyper Cache, specifically the sdzb SSD, is consistently reporting I/O errors. The issues you mentioned are likely related to this problem.
Could you please specify the type of Cache you are using? Depending on the situation, we may need to take different remedial actions.

[tallguyNJ]

Have (2) Samsung M.2 512Gig Model:MZVL2512HCJQ-00BH1

According to the Hyper Cache, I have them in Balance Mode Raid 0

Let me know the next steps.

Thank you

[TMzethar]

Although you are using an unnecessary RAID 0 mode, fortunately, you are using the balanced mode. In this mode, data is written simultaneously to both the SSD cache and the HDD volume, so the data is likely to be complete.
Your volume appears to be mounted in read-only mode. Under these circumstances, theoretically, you should be able to return to normal operation after disabling the SSD Hyper Cache.
However, the actual feasibility remains uncertain. It is strongly recommended that you back up essential data first if you want to try to disable the SSD Hyper Cache.

[tallguyNJ]

So, just to confirm, I should just delete the Hypercache drive? Since I have it in balanced mode, I should be fine, but still should backup my critical data to be safe. Once complete, the NAS should function normally.

If I want to recreate the HyperCache drive to help prevent this issue from coming back, should I set the two drive to Raid 1 vs Raid 0, or should I just have a single drive? I have more M.2 drives to replace the defective one.

Thank you

[TMlinda]

You can delete the hyper cache and replace the new SSD.
RAID1 is a protective array. If there is a faulty disk in the array, you can replace it and repair the array. RAID0 cannot do this.
If you want to replace the array, you need to delete the original RAID0 and recreate RAID1. Remember to back up the data before doing this.

[tallguyNJ]

I'm trying to delete the hyper cache, but keep getting an operation failed error. Any thoughts?

update: I had to do a hard shutdown the unit since it wouldn't shutdown on it's own. I then just opened it a removed the two M.2 drive. Rebooted and I'm working again without loosing my data. HyperCache is gone. Guess I got lucky.