Cache disk corrupt several hours after upgrade

[RikStigter]

Hi,

 

After an upgrade to 6.12 my system worked fine, but several hours later my cache-disk

became unreachable and all dockers failed.

The cache-drive sits on a Crucial MX500 2TB, with latest firmware.

After extracting it and testing it, it appears that the file-system has gone. I reinserted it in the server. Diagnostics attached.

How to proceed from here? Should I erase the disk and rebuild the dockers (It's only three active dockers and they aren't to complex to reinstall)?

tower-diagnostics-20230616-0718.zip

[RikStigter]

Some additional info: 

• I had copied some files to the cache and after 3 hours these normally get moved to the array. I'm not sure whether that has had any impact to this problem, but 'gut feeling' says it might. My gut might be wrong.
• The system is a HP Microserver gen8 (I think you'll be able to see that from the diagnostics file, but nevertheless...)
  •  I had already planned some maintenance so I did that this mornbing while I was testing the drive. So it now has a new fan, all dust cleared out (althought t never ran hot, but that is what maintenance is for) and all connectors have been re-inserted. The cache drive is visible to the system, but unformatted.
  • The 'appsdata'-share is totally empty (ths is where the docker files would have resided)
• My second server (a HP Microsrver gen10) has no problems at all, but 'll check again after copying some fle to it's fle-system

[JorgeB]

If the log tree is the only problem this may help:

btrfs rescue zero-log /dev/sdf1

 

[RikStigter]

Hello JorgeB

 

Got back this:

parent transid verify failed on 531043008512 wanted 616473 found 616472
parent transid verify failed on 531043008512 wanted 616473 found 616472
Couldn't setup log root tree
Clearing log on /dev/sdf1, previous log_root 531043008512, level 0

 

After a reboot everything seems to be OK once again. Dockers are all back.

 

Many thanks!

 

Rik

 

 

[JorgeB]

Make sure backups are up to date, also that error is usually caused by a controller/firmware issue, since it's an MX500 make sure it's using the latest firmware:

 

https://forums.unraid.net/topic/134954-warning-crucial-mx500-ssds-world-of-pain-stay-away-from-these/?do=findComment&comment=1255816

 

[RikStigter]

Ah,  see there is a new version.  I thought I was on te latest. II'll update ASAP.

Thanx again!