NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
aequus
May 30, 2018Aspirant
Volume Read Only - OS 6.9.3
Hi, after a reboot my volume is now read only. Disks are ok, everything is backuped what can i do to solve it?
dmesg shows:
21.497390] md126: detected capacity change from 0 to 10001279549440
[ 21.733817] BTRFS: device label 7c6e49a2:data devid 2 transid 2314880 /dev/md126
[ 22.163521] e1000e: eth0 NIC Link is Down
[ 22.231465] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.231468] 8021q: adding VLAN 0 to HW filter on device eth0
[ 25.777082] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 25.777430] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 85.293620] BTRFS info (device md126): checking UUID tree
[ 86.713928] traps: leafp2p[3685] general protection ip:7fa1a2ad0c04 sp:7fa1a0fe8bd8 error:0 in
libc-2.19.so[7fa1a2a3a000+1a1000]
[ 119.047893] BTRFS error (device md126): parent transid verify failed on 35255717134336 wanted 2
123812 found 2314881
[ 119.058391] BTRFS error (device md126): parent transid verify failed on 35255717134336 wanted 2
123812 found 2314881
[ 119.058396] BTRFS warning (device md126): Skipping commit of aborted transaction.
[ 119.058400] BTRFS: error (device md126) in cleanup_transaction:1864: errno=-5 IO failure
[ 119.058401] BTRFS info (device md126): forced readonly
[ 119.058407] BTRFS info (device md126): delayed_refs has NO entry
[ 119.058427] BTRFS warning (device md126): btrfs_uuid_scan_kthread failed -30
[ 125.956296] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 125.956303] NFSD: starting 90-second grace period (net ffffffff88f2f5c0)
[ 146.045372] nfsd: last server has exited, flushing export cache
[ 188.511468] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 188.511480] NFSD: starting 90-second grace period (net ffffffff88f2f5c0)
BR gerd
7 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
Clearly there's an issue with BTRFS in your log. Options are to
(a) use paid netgear support (my.netgear.com), and see if they can solve it short of a factory reset
(b) bite the bullet- do a factory reset, reconfigure, and restore data from your backup.
Any idea on what might have caused this? For instance, was there an unexpected power cut?
- aequusAspirant
There was no power cut. I did i simple reboot out of the gui because i had problems with the timemashine share. Rebiulding the device will take a week I habe 20TB data on it and it would mean a lost my installtion the second time in 2 years because of btfrs problems.
That is verry bad I would never gain buy an netgear device!
Whats about the repair options? I umount all btfrs mounts and tried the command:
btrfs check --repair /dev/md127
The command answered with "/dev/md126 busy or in use"
Trying btrfs check --repair /dev/md126, I get "/dev/md127 busy or in use"!
- StephenBGuru - Experienced User
aequus wrote:
Whats about the repair options? I umount all btfrs mounts and tried the command:
btrfs check --repair /dev/md127
The command answered with "/dev/md126 busy or in use"
Trying btrfs check --repair /dev/md126, I get "/dev/md127 busy or in use"!
I haven't used --repair, and it is considered a "dangerous" option in the btrfs wiki. I'd start w/o the --repair, and see what problems it finds.
Did you unmount /apps?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!