Disk with error : "Unmountable : Unsupported or no file system"

[Wanderer]

I added this new disk drive as a cache a couple months ago.

Everything seemed to be working fine with no errors detected from Unraid.

 

Then 2 things gave away flags about the drive condition:

 

1) (not really sure if it's related to a disk problem or a docker setting but) every new file created was given a unknown permission and I had to run the "New Permissions" tool every time whenever I needed to do any modifications on the files;

 

2) Since this morning, the drive became write-protected. I couldn't write on it but could clearly read all the content, no problem.

 

I then tried to reboot the server, and now the drive is giving me the "Unsupported or no file system" error and cannot be mounted.

 

Any help would be appreciated!

 

unraid-diagnostics-20240911-1323.zip

[JorgeB]

Sep 11 12:59:40 UNRAID kernel: BTRFS error (device sdg1): parent transid verify failed on logical 3487719686144 mirror 1 wanted 15272 found 15203
Sep 11 12:59:40 UNRAID kernel: BTRFS error (device sdg1): parent transid verify failed on logical 3487719686144 mirror 2 wanted 15272 found 15203

 

This error is fatal, it means some writes were lost, see here for some recovery options, btrfs restore is usually the best option for this.

[Wanderer]

10 hours ago, JorgeB said:

Sep 11 12:59:40 UNRAID kernel: BTRFS error (device sdg1): parent transid verify failed on logical 3487719686144 mirror 1 wanted 15272 found 15203
Sep 11 12:59:40 UNRAID kernel: BTRFS error (device sdg1): parent transid verify failed on logical 3487719686144 mirror 2 wanted 15272 found 15203

 

This error is fatal, it means some writes were lost, see here for some recovery options, btrfs restore is usually the best option for this.

 

Awesome! Thanks a lot! It worked!

 

I was able to create a temporary mount point and copying the whole disk manually for now.

 

So, what could have caused this? Would it be a faulty disk issue or just the btrfs filesystem that's not reliable?

 

 

[JorgeB]

Most commonly it's a device or controller firmware issue.