NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Volume Readonly after blackout
Although I have my Ultra 6 Plus connected to an UPS that is supposed to shut it down once a critical level of battery is reached, a few days ago while a blackout the NAS eventually was taken down abr...
Smaky wrote:
Once I went into the admin console, I noticed the Volume was in Read Only Mode. and when looking at the log I noticed some entries en the dmseg log stating:
BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727
md126 is the data volume, and those errors is why the volume is read-only.
The first thing to do is to back up your files.
The safest way is to switch to flexraid, destroy the volume, recreate it, and then switch back. You'll then need to recreate the shares, reload the data and reinstall the apps.
You could alternatively try btrfs check -repair - which is risky, so it is important to make the backup before you try it.
Thanks for your reply. I am now doing a full backup of the data. Fortunately so far it has been progresssing without issues. Once I am done, I'll try to repair first.
I noticed the btrfs check command (without repair) shows the volume is online. Can md126 volume be unmounted? Looking at the log, there are not too many btrfs errors and all of them related to single block:
[Mon Jun 1 00:16:19 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:19 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:19 2020] BTRFS: error (device md126) in balance_level:1912: errno=-5 IO failure [Mon Jun 1 00:16:19 2020] BTRFS info (device md126): forced readonly [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS: error (device md126) in balance_level:1912: errno=-5 IO failure [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS: error (device md126) in balance_level:1912: errno=-5 IO failure [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS: error (device md126) in balance_level:1912: errno=-5 IO failure [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS critical (device md126): corrupt leaf, bad key order: block=14964045447168, root=1, slot=727 [Mon Jun 1 00:16:20 2020] BTRFS: error (device md126) in balance_level:1912: errno=-5 IO failure
Smaky wrote:
I noticed the btrfs check command (without repair) shows the volume is online. Can md126 volume be unmounted?
You could try umount /data.
If that fails,then you'd need to boot up in tech support mode, chroot, and then run the command.
Has your NAS ever been vertically expanded (i.e., is there an md127 that is also part of the volume)?
Yes there is an md127 volume. Is there a log file where the current array structure is included so I can post it here?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
