RN214
5 Topics
Issue with old user permissions and NFS
I recently migrated my RN214 to expose NFS shares instead of SMB (no Windows PCs anymore). Turned out that there was a UID collision, user "volker" was auto-assigned UID 100 which I didn't care too much back then. Now, with NFS, UID 100 reflects to systemd-network on my local PC and the system would not let me change attributes, rsync was throwing erros similar to sync: [generator] failed to set permissions on "/media/rn214-Media/somefile": Operation not permitted (1) . So I created a new user "volker" on the RN214 (changing the existing UID was not possible) with UID 1000 which is the same on the local PC after first renaming the existing user volker to "volker_old". This new "volker" can read and write to files owned by "volker_old", copy them around and even delete them, but he can't get ownership of the existing file nor change permissions. Now I have numerous files owned by "volker_old" that I want to transfer to "volker". So I figured running find /data/Media -user volker_old -exec chown volker:users {} \; in a shell on the RN214 would be an elegant solution to this, since find /data/Media -user volker_old returned plenty of hits. However, I get chown: changing ownership of '/data/Media/somefile': Operation not permitted errors, even as admin user belonging to the admin group. sudo does not exist and for su - I don't know the root password - if there is any. Sure, I could just delete all the offending files and copy them over from a backup again, but this is about 5TB of data and will take an eternity. Is there any way to resolve this ownership issue efficiently? Any help highly appreciated.Solved600Views0likes7CommentsRN214 btrfs corruption forced readonly
Hi 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 Any suggestions? Thanks /bSolved4.4KViews0likes6CommentsREADYNAS 214 and Dropbox Sync
Hello, I've a NAS RN214, used to store big media files (videos, audio). I synced with Dropbox all the medias in the NAS (4 TB). The dropbox cloud service is set in "push only". Dropbox should copy all the new files (or the modiefied ones). Every time I restart the NAS, Dropbox starts uploading all the files!! :-( I tried different setup without solve the issue. It a big issue because, with my home-line, I need 150-200 days to upload everything! I can't understand what else to do. Any ideas?4.4KViews0likes8CommentsApache2 not starting, admin page is offline, shares and SSH are still available
Over the weekend I set up PHP, MySQL, and phpmyadmin and moved my web-based database to the NAS. Everything worked except the htaccess. I got that working Monday and tested it all out with great pride. Then I rebooted (to replace the UPS) and when it came back up, I could not access my subdirectories in the www share online. I received an email from the NAS saying that there were errors in the PHP install. I went to try to uninstall it, and I got an error that it couldn't be uninstalled. Then all the web pages were down including the admin page. Port 7082 (phpmyadmin) isn't responding either. I used SSH to log in. I tried to restart apache, but it failed saying: apache2[4034]: [error] server reached MaxClients setting, consider raising the MaxClients setting I can still access the shares through the network, I can access them through https://readycloud.netgear.com/ as well as my iphone app. I just can't get to the admin page or the www share set up for HTML access. RAIDar says everything is up and healthy. The admin page shows the "ReadyNas Admin is offline" page. Firmware is 6.6.1 - but before this happened it said that was the most current (although I see it's not). What am I missing? How can I correct this?Solved2.7KViews0likes3CommentsRN214 Won't Boot even after Factory Reset
Never had a problem till now. I had to move my ReadyNas to another location. Powered down, moved it, turned it back on and it's stuck on "Booting... 67%" After much internet searching, I tried diiferent options in the boot menu -- OS Reinstall, and even Factory Default (I do have everything backed up), but with both options and multiple attempts, it still stalls out while Booting, somewhere between 60-57%.The power button blinks blue, all 4 disk lights are lit up, and the ACT light is flashing steady. I left it trying to boot overnight, no progress. Was looking into the USB Recovery tool, but couldn't figure it out. Also I use a Mac and can't open exe files. I'm not sure the firmware. I haven't updated it in probably 6 months. I use this device primarily with PLEX. I would have thought a Factory Reset would do the trick. I'm just trying to get the thing back up and running. Any help is greatly appreciated!Solved6.3KViews0likes14Comments