This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have an RN 214 that I could not write to any more.
I have seen other have simular issues on the forum. Need suggestion how to proseed.
The problem started earlier today.
I updated the ReadyNAS OS to version 6.8.1 just a few days ago. Not jsure if it is related.
I have enabled Bit-rot-protection on the share, I read that this may be a bad idea?
Log where the problem started:
Oct 10 06:01:23 nas32-2017 kernel: ------------[ cut here ]------------
Oct 10 06:01:23 nas32-2017 kernel: WARNING: CPU: 1 PID: 32658 at fs/btrfs/disk-io.c:541 btree_csum_one_bio+0x108/0x10c()
Oct 10 06:01:23 nas32-2017 kernel: Modules linked in: vpd(PO)
Oct 10 06:01:23 nas32-2017 kernel: CPU: 1 PID: 32658 Comm: kworker/u8:1 Tainted: P O 4.4.88.alpine.1 #1
Oct 10 06:01:23 nas32-2017 kernel: Hardware name: Annapurna Labs Alpine
Oct 10 06:01:23 nas32-2017 kernel: Workqueue: btrfs-worker btrfs_worker_helper
Oct 10 06:01:23 nas32-2017 kernel: [<c0015980>] (unwind_backtrace) from [<c0012388>] (show_stack+0x10/0x14)
Oct 10 06:01:23 nas32-2017 kernel: ------------[ cut here ]------------
Oct 10 06:01:23 nas32-2017 kernel: WARNING: CPU: 3 PID: 32525 at fs/btrfs/disk-io.c:541 btree_csum_one_bio+0x108/0x10c()
Oct 10 06:01:23 nas32-2017 kernel: Modules linked in: vpd(PO)
Oct 10 06:01:23 nas32-2017 kernel: [<c0012388>] (show_stack) from [<c039bcd0>] (dump_stack+0x94/0xa8)
Oct 10 06:01:23 nas32-2017 kernel: [<c039bcd0>] (dump_stack) from [<c0020074>] (warn_slowpath_common+0x84/0xb4)
Oct 10 06:01:23 nas32-2017 kernel: [<c0020074>] (warn_slowpath_common) from [<c0020140>] (warn_slowpath_null+0x1c/0x24)
Oct 10 06:01:23 nas32-2017 kernel: [<c0020140>] (warn_slowpath_null) from [<c02a82b4>] (btree_csum_one_bio+0x108/0x10c)
Oct 10 06:01:23 nas32-2017 kernel: [<c02a82b4>] (btree_csum_one_bio) from [<c02a7170>] (run_one_async_start+0x34/0x44)
Oct 10 06:01:23 nas32-2017 kernel: [<c02a7170>] (run_one_async_start) from [<c02e90fc>] (normal_work_helper+0x108/0x1f4)
Oct 10 06:01:23 nas32-2017 kernel: [<c02e90fc>] (normal_work_helper) from [<c0035338>] (process_one_work+0x134/0x344)
Oct 10 06:01:23 nas32-2017 kernel: [<c0035338>] (process_one_work) from [<c0035594>] (worker_thread+0x4c/0x4bc)
Oct 10 06:01:23 nas32-2017 kernel: [<c0035594>] (worker_thread) from [<c003a858>] (kthread+0xfc/0x114)
Oct 10 06:01:23 nas32-2017 kernel: [<c003a858>] (kthread) from [<c000f368>] (ret_from_fork+0x14/0x2c)
Oct 10 06:01:23 nas32-2017 kernel: ---[ end trace 5d7482ac13d21d10 ]---
Oct 10 06:01:23 nas32-2017 kernel: CPU: 3 PID: 32525 Comm: kworker/u8:6 Tainted: P O 4.4.88.alpine.1 #1
Oct 10 06:01:23 nas32-2017 kernel: Hardware name: Annapurna Labs Alpine
Oct 10 06:01:23 nas32-2017 kernel: Workqueue: btrfs-worker btrfs_worker_helper
Oct 10 06:01:23 nas32-2017 kernel: [<c0015980>] (unwind_backtrace) from [<c0012388>] (show_stack+0x10/0x14)
Oct 10 06:01:23 nas32-2017 kernel: [<c0012388>] (show_stack) from [<c039bcd0>] (dump_stack+0x94/0xa8)
Oct 10 06:01:23 nas32-2017 kernel: [<c039bcd0>] (dump_stack) from [<c0020074>] (warn_slowpath_common+0x84/0xb4)
Oct 10 06:01:23 nas32-2017 kernel: [<c0020074>] (warn_slowpath_common) from [<c0020140>] (warn_slowpath_null+0x1c/0x24)
Oct 10 06:01:23 nas32-2017 kernel: [<c0020140>] (warn_slowpath_null) from [<c02a82b4>] (btree_csum_one_bio+0x108/0x10c)
Oct 10 06:01:23 nas32-2017 kernel: [<c02a82b4>] (btree_csum_one_bio) from [<c02a7170>] (run_one_async_start+0x34/0x44)
Oct 10 06:01:23 nas32-2017 kernel: [<c02a7170>] (run_one_async_start) from [<c02e90fc>] (normal_work_helper+0x108/0x1f4)
Oct 10 06:01:23 nas32-2017 kernel: [<c02e90fc>] (normal_work_helper) from [<c0035338>] (process_one_work+0x134/0x344)
Oct 10 06:01:23 nas32-2017 kernel: [<c0035338>] (process_one_work) from [<c0035594>] (worker_thread+0x4c/0x4bc)
Oct 10 06:01:23 nas32-2017 kernel: [<c0035594>] (worker_thread) from [<c003a858>] (kthread+0xfc/0x114)
Oct 10 06:01:23 nas32-2017 kernel: [<c003a858>] (kthread) from [<c000f368>] (ret_from_fork+0x14/0x2c)
Oct 10 06:01:23 nas32-2017 kernel: ---[ end trace 5d7482ac13d21d11 ]---
....
Oct 10 06:01:24 nas32-2017 kernel: ------------[ cut here ]------------
Oct 10 06:01:24 nas32-2017 kernel: WARNING: CPU: 1 PID: 32660 at fs/btrfs/disk-io.c:541 btree_csum_one_bio+0x108/0x10c()
Oct 10 06:01:24 nas32-2017 kernel: Modules linked in: vpd(PO)
Oct 10 06:01:24 nas32-2017 kernel: CPU: 1 PID: 32660 Comm: kworker/u8:4 Tainted: P W O 4.4.88.alpine.1 #1
Oct 10 06:01:24 nas32-2017 kernel: Hardware name: Annapurna Labs Alpine
Oct 10 06:01:24 nas32-2017 kernel: Workqueue: btrfs-worker btrfs_worker_helper
Oct 10 06:01:24 nas32-2017 kernel: [<c0015980>] (unwind_backtrace) from [<c0012388>] (show_stack+0x10/0x14)
Oct 10 06:01:24 nas32-2017 kernel: [<c0012388>] (show_stack) from [<c039bcd0>] (dump_stack+0x94/0xa8)
Oct 10 06:01:24 nas32-2017 kernel: [<c039bcd0>] (dump_stack) from [<c0020074>] (warn_slowpath_common+0x84/0xb4)
Oct 10 06:01:24 nas32-2017 kernel: [<c0020074>] (warn_slowpath_common) from [<c0020140>] (warn_slowpath_null+0x1c/0x24)
Oct 10 06:01:24 nas32-2017 kernel: [<c0020140>] (warn_slowpath_null) from [<c02a82b4>] (btree_csum_one_bio+0x108/0x10c)
Oct 10 06:01:24 nas32-2017 kernel: [<c02a82b4>] (btree_csum_one_bio) from [<c02a7170>] (run_one_async_start+0x34/0x44)
Oct 10 06:01:24 nas32-2017 kernel: [<c02a7170>] (run_one_async_start) from [<c02e90fc>] (normal_work_helper+0x108/0x1f4)
Oct 10 06:01:24 nas32-2017 kernel: [<c02e90fc>] (normal_work_helper) from [<c0035338>] (process_one_work+0x134/0x344)
Oct 10 06:01:24 nas32-2017 kernel: [<c0035338>] (process_one_work) from [<c0035594>] (worker_thread+0x4c/0x4bc)
Oct 10 06:01:24 nas32-2017 kernel: [<c0035594>] (worker_thread) from [<c003a858>] (kthread+0xfc/0x114)
Oct 10 06:01:24 nas32-2017 kernel: [<c003a858>] (kthread) from [<c000f368>] (ret_from_fork+0x14/0x2c)
Oct 10 06:01:24 nas32-2017 kernel: ---[ end trace 5d7482ac13d21d36 ]---
Oct 10 06:01:47 nas32-2017 kernel: BTRFS error (device md127): bad tree block start 11065534089998688569 17840787259392
Oct 10 06:01:47 nas32-2017 kernel: BTRFS error (device md127): bad tree block start 11065534089998688569 17840787259392
Oct 10 06:01:47 nas32-2017 kernel: BTRFS warning (device md127): Skipping commit of aborted transaction.
Oct 10 06:01:47 nas32-2017 kernel: BTRFS: error (device md127) in cleanup_transaction:1856: errno=-5 IO failure
Oct 10 06:01:47 nas32-2017 kernel: BTRFS info (device md127): forced readonly
Oct 10 06:01:48 nas32-2017 kernel: BTRFS info (device md127): delayed_refs has NO entry
I have tried to reboot the device and the device is still readonly.
$ mount
udev on /dev type devtmpfs (rw,noatime,nodiratime,size=10240k,nr_inodes=187826,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,mode=600,ptmxmode=000)
/dev/md0 on / type ext4 (rw,noatime,nodiratime,data=ordered)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime,nodiratime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime,nodiratime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime,nodiratime,size=516372k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,noatime,nodiratime,freezer)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,noatime,nodiratime)
sunrpc on /proc/fs/nfsd type nfsd (rw,noatime,nodiratime)
mqueue on /dev/mqueue type mqueue (rw,noatime,nodiratime)
configfs on /sys/kernel/config type configfs (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,noatime,nodiratime)
/dev/md127 on /data type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=5,subvol=/)
/dev/md127 on /apps type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=5,subvol=/.apps)
/dev/md127 on /home type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=5,subvol=/home)
/dev/md127 on /run/nfs4/data/Data type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=268,subvol=/Data)
/dev/md127 on /run/nfs4/home type btrfs (ro,noatime,nodiratime,nodatasum,nospace_cache,clear_cache,subvolid=5,subvol=/home)
btrfs filesystem show:
# btrfs filesystem show
Label: '0e8aece8:data' uuid: 1749e135-07f2-4052-a14a-44e5b2d0d3fc
Total devices 1 FS bytes used 16.07TiB
devid 1 size 21.82TiB used 16.10TiB path /dev/md127
btrfs check:
# btrfs check -p /dev/md127
checksum verify failed on 17840787390464 found 7A43DE2D wanted 39312E37
checksum verify failed on 17840787390464 found 7A43DE2D wanted 39312E37
checksum verify failed on 17840787390464 found 2A8F23F6 wanted 38333831
checksum verify failed on 17840787390464 found 7A43DE2D wanted 39312E37
bytenr mismatch, want=17840787390464, have=3544948844530774573
Couldn't setup extent tree
ERROR: cannot open file system
It appears the issue you have described requires assistance from the engineers and/or higher tier who can remote in to the NAS and fix this from the backend.
Unfortunately, It shows on your records that the support warranty of your product is already expired. You may try contacting support center and avail a support contract. That should allow you to extend the support for your product so they can escalate your issue to L3 or patiently wait for anyone in the community who has the knowledge in the SSH commands and fixing some issues from the backend.
It appears the issue you have described requires assistance from the engineers and/or higher tier who can remote in to the NAS and fix this from the backend.
Unfortunately, It shows on your records that the support warranty of your product is already expired. You may try contacting support center and avail a support contract. That should allow you to extend the support for your product so they can escalate your issue to L3 or patiently wait for anyone in the community who has the knowledge in the SSH commands and fixing some issues from the backend.
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution.
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
For support contract I would recommend to contact our phone support department so they can discuss a type support contract and the price. Unfortunately there is no option and have not seen a forum post changing from btrfs to ext file system.
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution.
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
