ReadyNas 102 = Unusable frustrating junk! - now what?

Question

Firmware 6.10.4 hotfix 1 - RAID 1This unit has become a comedy of errors. It seems anything I try to do with it, it just gives errors.&nbsp;Yeah, it's end of life. But its not really that old and it used to work, but it seems the firmware upgrades over the years have been causing issue after issue, instead of making it better. Why should I suffer from NetGear's buggy firmware?&nbsp;The very basic task of copying files to it doesn't work. I have a nightly robocopy script that attempts to copy files from my laptop to the RN, but gives a Not Enough Space on the Disk error. There is plenty of space. The Share's Quota settings are unchecked. However, in attempt to set any value in hopes of getting the setting to stick, but my changes don't take. The "Size" label turns red...but no other information is provided:Ok, well let's hope that it showing as unchecked is correct...let's move on to the Volume's Quota setting. The Quota check box is checked...ok, let's uncheck it....&nbsp;Ha! Nice try you simple user...not going to let that happen!&nbsp;I'm not aware of or could find any other Quota related settings (i.e. at the user or group levels), so that's all I could attempt.&nbsp;I downloaded the logs and did a search for this error code...not found in any of the files.I searched for the term "Failed"....2,565 hits in 16 of the 79 log files...hmmm, not sure where to start there.I searched for the term "Error"....even more hits...9,968 hits in 20 of the 79 log files...hmmm, not sure where to start there either.This old thread I started never got resolved...the mods didn't know and said to contact support.&nbsp;&nbsp;Any ideas on where to start? I'd love for it to just do these two things as it should:Copy files to it up to full disk capacityPerform cloud backups to my business Dropbox account for extra redundancyIf I could get it to work, great. If not, I'll replace...with a NON-Netgear alternative as this has been extremely frustrating and I'd expect to be able at least copy files to a NAS device. IF I go that route, can I just plug my 2 - 3TB drives in RAID 1 config into another brand unit?&nbsp;Other Issues, just to show that there are problems all over the place:Can't change Snapshot Pruning value...get the same&nbsp;Code: 1014019994 errorCheck for Updates wouldn't work...couldn't resolve host name error... had to set DNS server, which somehow got erased or became a new setting after some upgrade???Can't get DropBox sync to work. Creating a new folder from the ReadyNas side creates the folder name as ReadyNas regardless of what you enter as the desired folder name. Ok, I'll use ReadyNas instead of Pictures...fine..but then the DropBox status goes back to Disabled for some reason...no error provided. Logs show&nbsp;Mar 03 21:32:47 ReadyNAS systemd[1]: Started Dropbox 2 client for ReadyNAS.
Mar 03 21:32:47 ReadyNAS ng-csd[5535]: terminate called after throwing an instance of 'Poco::FileException'
Mar 03 21:32:47 ReadyNAS ng-csd[5535]:   what():  File access error
Mar 03 21:32:47 ReadyNAS systemd[1]: dropbox.service: Main process exited, code=killed, status=6/ABRT
Mar 03 21:32:47 ReadyNAS systemd[1]: dropbox.service: Unit entered failed state.
Mar 03 21:32:47 ReadyNAS systemd[1]: dropbox.service: Failed with result 'signal'.
Mar 03 21:32:48 ReadyNAS systemd[1]: dropbox.service: Service hold-off time over, scheduling restart.
Mar 03 21:32:48 ReadyNAS systemd[1]: Stopped Dropbox 2 client for ReadyNAS.
Mar 03 21:32:48 ReadyNAS systemd[1]: dropbox.service: Start request repeated too quickly.
Mar 03 21:32:48 ReadyNAS systemd[1]: Failed to start Dropbox 2 client for ReadyNAS.
Mar 03 21:32:48 ReadyNAS systemd[1]: dropbox.service: Unit entered failed state.
Mar 03 21:32:48 ReadyNAS systemd[1]: dropbox.service: Failed with result 'start-limit-hit'.Heck, I can't even look at an old support ticket in NetGear's support portal...upon clicking on it I get this error...seriously!!!

mdgm · Answer

chadwixk&nbsp;wrote:I have a nightly robocopy script that attempts to copy files from my laptop to the RN, but gives a Not Enough Space on the Disk error. There is plenty of space.What does your btrfs.log look like, particularly the top part of it.chadwixk&nbsp;wrote:Any ideas on where to start? I'd love for it to just do these two things as it should:Copy files to it up to full disk capacityBTRFS loves free space. It's not a good idea to fill up any disk in any system regardless of brand or operating system used up to capacity. You are far more likely to encounter corner case problems with a full filesystem than one with plenty of free space. How full is your data volume?&nbsp;chadwixk&nbsp;wrote:If I could get it to work, great. If not, I'll replace...with a NON-Netgear alternative as this has been extremely frustrating and I'd expect to be able at least copy files to a NAS device. IF I go that route, can I just plug my 2 - 3TB drives in RAID 1 config into another brand unit?A different brand would need to format the disks, so you would need to backup your data first.

chadwixk · Answer

I didn't really mean I'd fill it to 100%, but I'd like the ability to fill it...i.e. not get errors that it is full when it isn't.&nbsp;I have about 600GB of free space. And I just freed up more by cleaning up old snapshots.&nbsp;Here's the top part of btrfs.logLabel: '2fe56952:data'  uuid: f3768221-8da7-44f9-8fe1-fc703e7af6fd
	Total devices 1 FS bytes used 2.14TiB
	devid    1 size 2.72TiB used 2.72TiB path /dev/md127

=== filesystem /data ===
Data, single: total=2.70TiB, used=2.13TiB
System, DUP: total=8.00MiB, used=352.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=10.50GiB, used=10.00GiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=512.00MiB, used=0.00BOk, that's what I thought....working on scouring up a bunch of old drives now to do so.&nbsp;

mdgm · Answer

chadwixk&nbsp;wrote:Here's the top part of btrfs.logLabel: '2fe56952:data'  uuid: f3768221-8da7-44f9-8fe1-fc703e7af6fd
	Total devices 1 FS bytes used 2.14TiB
	devid    1 size 2.72TiB used 2.72TiB path /dev/md127Note that third linesize 2.72TiB used 2.72TiBThat means that the space on the data volume is fully allocated.When you delete data if a chunk is emptied it is returned to unallocated space. It can take some time for this to happen. When you delete an old snapshot all the newer snapshots are updated recursively, I think which can take some time.&nbsp;Note to free up space by deleting snapshots, all snapshots that contain some deleted data must be deleted.&nbsp;So if you added a file on the 1st January and deleted it on the 1st March you'd need to delete all snapshots from and including the time on 1st January when the data was added onwards through to and including the time on 1st March when the data was deleted. If you don't do that then deleting that data doesn't free up space.If deleting all the snapshots that contain some data doesn't change the allocations being full then you could try a balance from SSH with some special parameters e.g. -dusage=1. Though it could fail due to not enough space in which case the workaround is to temporarily add some storage e.g. a USB disk so that a balance can be run and then when space is freed up to run commands to remove the USB disk from the data volume.&nbsp;chadwixk&nbsp;wrote:Data, single: total=2.70TiB, used=2.13TiBOk, that's what I thought....working on scouring up a bunch of old drives now to do so.So we have 2.70TiB allocated to data of which 2.13TiB is in use.chadwixk&nbsp;wrote:Metadata, DUP: total=10.50GiB, used=10.00GiB0.5GiB of that metadata allocation is reserved so the metadata is full. What's needed is to return some space from data to unallocated space so that it can be allocated to metadata.chadwixk&nbsp;wrote:Ok, that's what I thought....working on scouring up a bunch of old drives now to do so.What does your initrd.log look like?If you look further in btrfs.log do you see some of the deleted snapshots are still in purge?

chadwixk · Answer

I saw that line, but also right above it it shows that only 2.14TB is used, which also corresponded with what the web interface GUI showed...about 25% free space.&nbsp;Total devices 1 FS bytes used 2.14TiBAlso this seems to support that there is ~600GB of free space:Data, single: total=2.70TiB, used=2.13TiBThis seems to directly contradict each other? Why does this show it is full? :size 2.72TiB used 2.72TiBHere's the initrd.log[2015/08/27 01:19:39] Factory default initiated due to new disks (no RAID, no partitions)!
[2015/08/27 01:19:45] Defaulting to X-RAID2 mode, RAID level 1
[2015/08/27 01:20:17] Factory default initiated on ReadyNASOS 6.2.0 (ReadyNASOS).
[2015/08/30 07:20:21] Updated from ReadyNASOS 6.2.0 (ReadyNASOS) to 6.2.5 (ReadyNASOS).
[2015/12/02 09:50:47] Updated from ReadyNASOS 6.2.5 (ReadyNASOS) to 6.4.1 (ReadyNASOS).
[2016/11/29 20:25:15] Updated from ReadyNASOS 6.4.1 (ReadyNASOS) to 6.5.0 (RC3).
[2017/07/15 16:12:29 UTC] Updated from ReadyNASOS 6.5.0 (RC3) to 6.7.5 (ReadyNASOS).
[2018/11/15 21:22:23 UTC] Updated from ReadyNASOS 6.7.5 (ReadyNASOS) to 6.9.4 (ReadyNASOS).
[2019/02/05 06:55:49 UTC] Updated from ReadyNASOS 6.9.4 (ReadyNASOS) to 6.9.5 (ReadyNASOS).
[2019/12/03 10:12:14 UTC] Updated from ReadyNASOS 6.9.5 (ReadyNASOS) to 6.10.2 (ReadyNASOS).
[2021/03/04 03:57:07 UTC] Updated from ReadyNASOS 6.10.2 (ReadyNASOS) to 6.10.4 (ReadyNASOS).So after deleting multiple snapshots, and my son accidentally tripping the breaker that my NAS is on, restarting the NAS which is now reindexing, I am able to now Save config changes. Turning off the Volume Quota, adding Dropbox uploads and last night's robocopy backup script worked, without any disk full errors!&nbsp;So I considere this mostly solved. My only remaining issue is that I was having these errors when the disk seemed to be reporting that it had ~600GB of 2.7TB of free space, which is a decent amount of space. So I'm not convinced that it was truly full, and hence not sure of what the root problem was, and further, not convinced it won't happen again nor how to fix if it does. Time will tell I guess.&nbsp;Current btrfs.log:Label: '2fe56952:data'  uuid: f3768221-8da7-44f9-8fe1-fc703e7af6fd
	Total devices 1 FS bytes used 1.53TiB
	devid    1 size 2.72TiB used 2.72TiB path /dev/md127

=== filesystem /data ===
Data, single: total=2.70TiB, used=1.52TiB
System, DUP: total=8.00MiB, used=352.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=10.50GiB, used=3.00GiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=512.00MiB, used=0.00BIt still shows in this one line that it is full, so I don't think that means its full, but that it is fully reserved for use or somethingdevid    1 size 2.72TiB used 2.72TiB path /dev/md127It is now reporting only being a bit over 50% used:Data, single: total=2.70TiB, used=1.52TiBMetadata, DUP (not sure the diff between DUP and single), is lower, but originally, it still had 500MB of unused space, I'd think that would be plenty and there was 600GB of free space it could've pulled from if it needed more, and I'd hope the logic would be there to do so.&nbsp;

mdgm · Answer

The space is fully allocated. There's a difference between allocation and what is in use of the allocation. That 512MiB in metadata is in the GlobalReserve. The system had nowhere to store additional metadata and with the space on the volume fully allocated it couldn't allocate any more space to metadata. Now that you have metadata allocation available to use you can write to the volume again.&nbsp;You may wish to do a balance of the data volume. That will move data around so that chunks are emptied and returned to unallocated space.

Forum Discussion

ReadyNas 102 = Unusable frustrating junk! - now what?

9 Replies

Related Content

R7000P 5Ghz Unusable

Wifi Frustration

MR80: Satellites become unusable after time while main router is fine?

render wlan unusable

ReadyCLOUD mac desktop app still unusable

NETGEAR Academy

ProSupport for Business