NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNas Pro6, os 6.3.5. Read-only volume.
Hello.
I have RND pro6 with 6.3.5 OS version.
Two weeks ago I've shutdown the device and powered it off.
now it's read-only.
can't switch to English, sorry.
here is part of the log
Sep 13 21:15:32 NAS kernel: md: md0 stopped.
Sep 13 21:15:32 NAS kernel: md: bind<sdb1>
Sep 13 21:15:32 NAS kernel: md: bind<sdc1>
Sep 13 21:15:32 NAS kernel: md: bind<sdd1>
Sep 13 21:15:32 NAS kernel: md: bind<sde1>
Sep 13 21:15:32 NAS kernel: md: bind<sdf1>
Sep 13 21:15:32 NAS kernel: md: bind<sda1>
Sep 13 21:15:32 NAS kernel: md/raid1:md0: active with 6 out of 6 mirrors
Sep 13 21:15:32 NAS kernel: md0: detected capacity change from 0 to 4290772992
Sep 13 21:15:32 NAS kernel: md0: unknown partition table
Sep 13 21:15:32 NAS kernel: md: md1 stopped.
Sep 13 21:15:32 NAS kernel: md: bind<sdb2>
Sep 13 21:15:32 NAS kernel: md: bind<sdc2>
Sep 13 21:15:32 NAS kernel: md: bind<sdd2>
Sep 13 21:15:32 NAS kernel: md: bind<sde2>
Sep 13 21:15:32 NAS kernel: md: bind<sdf2>
Sep 13 21:15:32 NAS kernel: md: bind<sda2>
Sep 13 21:15:32 NAS kernel: md/raid:md1: device sda2 operational as raid disk 0
Sep 13 21:15:32 NAS kernel: md/raid:md1: device sdf2 operational as raid disk 5
Sep 13 21:15:32 NAS kernel: md/raid:md1: device sde2 operational as raid disk 4
Sep 13 21:15:32 NAS kernel: md/raid:md1: device sdd2 operational as raid disk 3
Sep 13 21:15:32 NAS kernel: md/raid:md1: device sdc2 operational as raid disk 2
Sep 13 21:15:32 NAS kernel: md/raid:md1: device sdb2 operational as raid disk 1
Sep 13 21:15:32 NAS kernel: md/raid:md1: allocated 6440kB
Sep 13 21:15:32 NAS kernel: md/raid:md1: raid level 6 active with 6 out of 6 devices, algorithm 2
Sep 13 21:15:32 NAS kernel: RAID conf printout:
Sep 13 21:15:32 NAS kernel: --- level:6 rd:6 wd:6
Sep 13 21:15:32 NAS kernel: disk 0, o:1, dev:sda2
Sep 13 21:15:32 NAS kernel: disk 1, o:1, dev:sdb2
Sep 13 21:15:32 NAS kernel: disk 2, o:1, dev:sdc2
Sep 13 21:15:32 NAS kernel: disk 3, o:1, dev:sdd2
Sep 13 21:15:32 NAS kernel: disk 4, o:1, dev:sde2
Sep 13 21:15:32 NAS kernel: disk 5, o:1, dev:sdf2
Sep 13 21:15:32 NAS kernel: md1: detected capacity change from 0 to 2145124352
Sep 13 21:15:32 NAS kernel: md1: unknown partition table
Sep 13 21:15:32 NAS kernel: BTRFS: device label 33eae13b:root devid 1 transid 18415 /dev/md0
Sep 13 21:15:32 NAS kernel: WARNING! power/level is deprecated; use power/control instead
Sep 13 21:15:32 NAS systemd[1]: systemd 44 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP; debian)
Sep 13 21:15:32 NAS systemd[1]: Set hostname to <NAS>.
Sep 13 21:15:32 NAS systemd[1]: Cannot add dependency job for unit fvapp-btsync.service, ignoring: Unit fvapp-btsync.service failed to load: No such file ...or details.
Sep 13 21:15:32 NAS udevd[1147]: starting version 175
Sep 13 21:15:32 NAS systemd-journal[1132]: Journal started
Sep 13 21:15:32 NAS kernel: BTRFS (dev md0): parent transid verify failed on 241795072 wanted 8262 found 10310
Sep 13 21:15:32 NAS kernel: BTRFS (dev md0): parent transid verify failed on 241795072 wanted 8262 found 10310
Sep 13 21:15:33 NAS kernel: md: md127 stopped.
Sep 13 21:15:33 NAS kernel: md: bind<sdb3>
Sep 13 21:15:33 NAS kernel: md: bind<sdc3>
Sep 13 21:15:33 NAS kernel: md: bind<sdd3>
Sep 13 21:15:33 NAS kernel: md: bind<sde3>
Sep 13 21:15:33 NAS kernel: md: bind<sdf3>
Sep 13 21:15:33 NAS kernel: md: bind<sda3>
Sep 13 21:15:33 NAS kernel: md/raid:md127: device sda3 operational as raid disk 0
Sep 13 21:15:33 NAS kernel: md/raid:md127: device sdf3 operational as raid disk 5
Sep 13 21:15:33 NAS kernel: md/raid:md127: device sde3 operational as raid disk 4
Sep 13 21:15:33 NAS kernel: md/raid:md127: device sdd3 operational as raid disk 3
Sep 13 21:15:33 NAS kernel: md/raid:md127: device sdc3 operational as raid disk 2
Sep 13 21:15:33 NAS kernel: md/raid:md127: device sdb3 operational as raid disk 1
Sep 13 21:15:33 NAS kernel: md/raid:md127: allocated 6440kB
Sep 13 21:15:33 NAS kernel: md/raid:md127: raid level 5 active with 6 out of 6 devices, algorithm 2
Sep 13 21:15:33 NAS kernel: RAID conf printout:
Sep 13 21:15:33 NAS kernel: --- level:5 rd:6 wd:6
Sep 13 21:15:33 NAS kernel: disk 0, o:1, dev:sda3
Sep 13 21:15:33 NAS kernel: disk 1, o:1, dev:sdb3
Sep 13 21:15:33 NAS kernel: disk 2, o:1, dev:sdc3
Sep 13 21:15:33 NAS kernel: disk 3, o:1, dev:sdd3
Sep 13 21:15:33 NAS kernel: disk 4, o:1, dev:sde3
Sep 13 21:15:33 NAS kernel: disk 5, o:1, dev:sdf3
Sep 13 21:15:33 NAS kernel: md127: detected capacity change from 0 to 14978123694080
Sep 13 21:15:33 NAS start_raids[1121]: mdadm: /dev/md/data-0 has been started with 6 drives.
Sep 13 21:15:33 NAS kernel: md127: unknown partition table
Sep 13 21:15:33 NAS kernel: BTRFS: device label 33eae13b:data devid 1 transid 3116 /dev/md127
Sep 13 21:15:33 NAS kernel: Adding 2094844k swap on /dev/md1. Priority:-1 extents:1 across:2094844k
Sep 13 21:15:33 NAS kernel: BTRFS (dev md127): parent transid verify failed on 306741248 wanted 766 found 2814
Sep 13 21:15:33 NAS kernel: BTRFS (dev md127): parent transid verify failed on 306741248 wanted 766 found 2814
Sep 13 21:15:33 NAS kernel: BTRFS: Failed to read block groups: -5
Sep 13 21:15:33 NAS mount[1193]: mount: wrong fs type, bad option, bad superblock on /dev/md127,
Sep 13 21:15:33 NAS mount[1193]: missing codepage or helper program, or other error
Sep 13 21:15:33 NAS mount[1193]: In some cases useful info is found in syslog - try
Sep 13 21:15:33 NAS mount[1193]: dmesg | tail or so
Sep 13 21:15:33 NAS systemd[1]: data.mount mount process exited, code=exited status=32
Sep 13 21:15:33 NAS kernel: BTRFS: open_ctree failed
Sep 13 21:15:33 NAS systemd[1]: Job apps.mount/start failed with result 'dependency'.
Sep 13 21:15:33 NAS systemd[1]: Job home.mount/start failed with result 'dependency'.
Sep 13 21:15:33 NAS systemd[1]: Job local-fs.target/start failed with result 'dependency'.
Sep 13 21:15:33 NAS systemd[1]: Unit data.mount entered failed state.
Sep 13 21:15:33 NAS mdadm[2039]: NewArray event detected on md device /dev/md0
Sep 13 21:15:33 NAS mdadm[2039]: NewArray event detected on md device /dev/md1
Sep 13 21:15:33 NAS mdadm[2039]: NewArray event detected on md device /dev/md127
how can't I can data back?
thank you
Hello!
I've fixed 6.3.5 problem. with dataloss.
but now I've changed FS to really solid rock FS without dataloss, high fragmentation and other "features" - see here ;)
11 Replies
Replies have been turned off for this discussion
root@NAS:~# cat /proc/mdstat Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active raid5 sda3[0] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1] 14627073920 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU] md1 : active raid6 sda2[0] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1] 2094848 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU] md0 : active raid1 sda1[0] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] 4190208 blocks super 1.2 [6/6] [UUUUUU]Hello!
I've fixed 6.3.5 problem. with dataloss.
but now I've changed FS to really solid rock FS without dataloss, high fragmentation and other "features" - see here ;)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
