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...
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?
Smaky wrote:
Yes there is an md127 volume. Is there a log file where the current array structure is included so I can post it here?
mdstat.log
It's simplest to cut/paste it (using the </> control), as you can't attach a .zip or a .log file to your reply.
Here it is...
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md126 : active raid5 sda3[0] sdf3[5] sde3[4] sdd3[3] sdc3[6] sdb3[1] 19510844160 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU] md127 : active raid5 sda4[0] sdc4[3] sdb4[1] 3906743808 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] md1 : active raid10 sda2[0] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1] 1566720 blocks super 1.2 512K chunks 2 near-copies [6/6] [UUUUUU] md0 : active raid1 sda1[0] sdf1[5] sde1[4] sdd1[3] sdc1[6] sdb1[1] 4190208 blocks super 1.2 [6/6] [UUUUUU] unused devices: <none> /dev/md/0: Version : 1.2 Creation Time : Fri Jun 14 07:35:23 2019 Raid Level : raid1 Array Size : 4190208 (4.00 GiB 4.29 GB) Used Dev Size : 4190208 (4.00 GiB 4.29 GB) Raid Devices : 6 Total Devices : 6 Persistence : Superblock is persistent Update Time : Mon Jun 1 18:07:05 2020 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 0 Spare Devices : 0 Consistency Policy : unknown Name : 33eaa9b5:0 (local to host 33eaa9b5) UUID : cf8882a0:6c0dec12:faafde0f:fb3e15bf Events : 613 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 6 8 33 2 active sync /dev/sdc1 3 8 49 3 active sync /dev/sdd1 4 8 65 4 active sync /dev/sde1 5 8 81 5 active sync /dev/sdf1 /dev/md/1: Version : 1.2 Creation Time : Sun Jul 28 09:57:14 2019 Raid Level : raid10 Array Size : 1566720 (1530.00 MiB 1604.32 MB) Used Dev Size : 522240 (510.00 MiB 534.77 MB) Raid Devices : 6 Total Devices : 6 Persistence : Superblock is persistent Update Time : Sun Apr 26 02:05:12 2020 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 0 Spare Devices : 0 Layout : near=2 Chunk Size : 512K Consistency Policy : unknown Name : 33eaa9b5:1 (local to host 33eaa9b5) UUID : d7dc864b:638758b0:9fbc310a:05216ae3 Events : 19 Number Major Minor RaidDevice State 0 8 2 0 active sync set-A /dev/sda2 1 8 18 1 active sync set-B /dev/sdb2 2 8 34 2 active sync set-A /dev/sdc2 3 8 50 3 active sync set-B /dev/sdd2 4 8 66 4 active sync set-A /dev/sde2 5 8 82 5 active sync set-B /dev/sdf2 /dev/md/data-0: Version : 1.2 Creation Time : Fri Jun 14 07:35:43 2019 Raid Level : raid5 Array Size : 19510844160 (18606.99 GiB 19979.10 GB) Used Dev Size : 3902168832 (3721.40 GiB 3995.82 GB) Raid Devices : 6 Total Devices : 6 Persistence : Superblock is persistent Update Time : Mon Jun 1 00:16:06 2020 State : clean Active Devices : 6 Working Devices : 6 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Name : 33eaa9b5:data-0 (local to host 33eaa9b5) UUID : e19bef9c:b604ae69:54f48e23:1ba865b3 Events : 40766 Number Major Minor RaidDevice State 0 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 6 8 35 2 active sync /dev/sdc3 3 8 51 3 active sync /dev/sdd3 4 8 67 4 active sync /dev/sde3 5 8 83 5 active sync /dev/sdf3 /dev/md/data-1: Version : 1.2 Creation Time : Sat Jun 15 19:25:51 2019 Raid Level : raid5 Array Size : 3906743808 (3725.76 GiB 4000.51 GB) Used Dev Size : 1953371904 (1862.88 GiB 2000.25 GB) Raid Devices : 3 Total Devices : 3 Persistence : Superblock is persistent Update Time : Mon Jun 1 00:16:06 2020 State : clean Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Name : 33eaa9b5:data-1 (local to host 33eaa9b5) UUID : b6908885:8dae1868:ffe32319:10f422fa Events : 1688 Number Major Minor RaidDevice State 0 8 4 0 active sync /dev/sda4 1 8 20 1 active sync /dev/sdb4 3 8 36 2 active sync /dev/sdc4
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
