Forum Discussion

Aspirant

Oct 10, 2023

Solved

BTRFS error ReadyNAS 314, OS6.10.8

I wonder whether anyone can help? 314, four Toshiba DT01ACA200 drives in X-RAID (I normally use Flex-RAID; I guess I just forgot to change over...), and working perfectly until recently. Now every ...

StephenB
Oct 13, 2023
Sandshark wrote:

Since a drive error is one potential cause,

It's hard to rule disks out, as I have seen them mis-behave in ways that don't affect the smart stats.

mfb9: If you want me to take a look, then send me a link to dropbox (or google drive, icloud, onedrive, ...) via a private message (PM). Please provide the full zip file. You send a PM using the envelope icon in the upper right of the forum page. Make sure the permissions allow anyone with the link to download

StephenB

Guru - Experienced User

Oct 12, 2023

mfb9 wrote:

If I post the full log, would someone be able to interpret it and tell me what I need to do?

I'm willing to take a look, just send me a link in a PM (you can't attach the log zip). Don't post it publicly.

Sometimes mods will also offer to take a look.

mfb9 wrote:

I feel uncomfortable about changing to flex-RAID while there are gremlins, but maybe it'd be OK if everything is backed up...?

Even rebooting the NAS could result in losing the volume, so I'd be careful now about changing things.

However, if ssh is not enabled, then it would be good to enable it. For some (unclear) reason the NAS won't let you enable when there is no mounted volume.

Sandshark
Sensei - Experienced User
Oct 12, 2023
The OS is putting the volume into read-only mode to prevent you from doing any more damage to the already unreliable volume. Take the hint and make sure everything is backed up before the volume becomes inaccessible.

I had a similar issue some years back, and nothing I did short of destroying and re-creating the volume had a lasting effect.
- mfb9
  Aspirant
  Oct 12, 2023
  Thanks very much. Yes, everything is backed up regularly, but it's still a worry! So the "damage" is likely to be what exactly? The drives seem reliable on the testing that the system does (although I recognise that a more in-depth test on drives taken out and interrogated individually can sometimes show problems that aren't picked up by the ReadyNAS system). Is it a volume structure problem? Because I thought the whole point of using BTRFS and copy-on-write as "Bit Rot Protection" was that volume errors were self-healing in a sense.
  
  So if I destroy and re-create the volumes and write back the backup that should do the job? Without hardware change?
  
  Thanks very much for your help.
  - StephenB
    Guru - Experienced User
    Oct 12, 2023
    mfb9 wrote:
    
    Yes, everything is backed up regularly, but it's still a worry! So the "damage" is likely to be what exactly?
    
    General possibilities:
    
    Disk errors
    
    File system metadata (folder structures, etc) have somehow gotten corrupted
    
    Metadata can become corrupted due to lost disk writes, Causes include
    
    system power-fail
    
    system crash
    
    ungraceful shutdown
    
    Some form of "bit-rot" also (memory corruption, perhaps due a bug, etc)
mfb9
Aspirant
Oct 12, 2023
Thanks very much. A link to eg Dropbox with the log, do you mean?

I confess I've never mastered ssh, but maybe now is the time to try to do so!
OK - I've enabled SSH and successfully managed to log in, so that will be useful in the future when I know what to do with it!

Thanks very much for your help.
Mark