NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Shares goes read-only after a while after upgrade to 6.8.0
Hi, After upgrading to 6.8.0 I have a strange behavior. After every boot, everything is fine for some time (up to half an hour) and then file system goes read only. After boot: root@NasSeb...
This morning I gave up: didn't see any possible solution as the more I looked the it seemed the raid itself became corrupt (not read/write error in the smart data of the disks)
=> I just did a factory default and am downloading my last backup
As I feared, scrub didn't solve the problem and desmg raise lots of errors
[ 52.671108] BTRFS critical (device md127): corrupt leaf, slot offset bad: blo ck=863109120, root=1, slot=159 [ 55.351256] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 55.370366] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 55.917422] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 55.990251] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 63.156939] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 63.170322] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 63.195064] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 63.195291] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 63.490218] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 63.490426] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 64.986349] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 64.986675] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 64.987037] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 64.987405] BTRFS error (device md127): bad tree block start 566935740547 384 36864 [ 65.370875] BTRFS critical (device md127): corrupt leaf, slot offset bad: blo ck=863109120, root=1, slot=159 [ 65.370895] BTRFS: error (device md127) in __btrfs_free_extent:6968: errno=-5 IO failure [ 65.370897] BTRFS info (device md127): forced readonly [ 65.370901] BTRFS: error (device md127) in btrfs_run_delayed_refs:2956: errno =-5 IO failure [ 65.371117] BTRFS error (device md127): pending csums is 360448
But all was ok until upgrade :(
Is there any mean to repair this ?
Hello Keligh,
It does appear that after firmware upgrade the NAS will for some reason will automatically go to read only mode. I have not seen similar concern/issue raised on support. When the NAS goes to read only mode do you need to reboot the NAS to work again and in turn goes to a cycle is this correct? May we ask for the complete logs of the NAS, you may use file sharing website like wikisend and just PM the download link.
Regards,
Marty_M
NETGEAR Community TeamThis morning I gave up: didn't see any possible solution as the more I looked the it seemed the raid itself became corrupt (not read/write error in the smart data of the disks)
=> I just did a factory default and am downloading my last backup
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
