RN204 resync after successful resync, any idea what's going on?

Question

Ok, i'm confused.&nbsp; Original set up of disks was 3x1TB and 1x500GB.&nbsp; One of the 1TB was not on the HCL, neither was the 500GB so to play fair, I have swapped these, one at a time of course, waiting for sync completion.&nbsp;The swap of the 1TB took about 24 hours to sync, then I swapped the 500GB for a 2TB drive. That took 34 hours but as soon as it finished, it then started resync again and now says it will take 5.5 days!&nbsp; Is this doing a balance or something?&nbsp; I'm struggling to comprehend 7 days to swap such relatively small disks and of the 9 days that i've had the unit, 7 of them so far have been in a fault state (one from a different case where access to the volumes were lost when the unit hung).&nbsp;I was already low on confidence with after the first major issue this but it's heading even more South now.&nbsp;(I have opened a support case)&nbsp;

djtaylor · Answer

Ok, I think i'm going to answer my own question here after scouring through the logs.&nbsp;I began with 3 x 1TB, 1x 0.5GB and the unit created:-1 RAID 5 volume: 4 x 0.5GB = 1.5TB1 RAID 5 volume: 3 x 0.5GB = 1.0TBTotal 2.5TB&nbsp;Next I replaced one of the 1TB so all that had to happen was to create matching partitions and resync.&nbsp;Then I swapped the 0.5 for a 2TB drive so in the first instance it created a 0.5TB partition and sync'd the volume that spanned 4 disks and completed.&nbsp; Then, it found the option of introducing an extra 0.5TB in order to reshape the array and it's the addition of an extra 0.5GB and reshape/resize that's the second resync that i'm seeing bourne out from the volume log below.&nbsp;btrfs is new to me (as is the RN204) so i'm just trying to understand its processes.&nbsp; A better message in the log on the console would be reshaping array rather than throw in another resync but that's just my opinion, it would at least have been more readily understandable that it wasn't the exact same degraded to redundant resync!&nbsp;My other question here though is the resync speed, "Sync speed: 2168 KB/sec", that seems ridiculously low?&nbsp; I'm not using the box for any other read/writes so I would have thought it could be going a lot faster.&nbsp; I have decuded that it's throttled from other log detail but still, this seems way under what it could do when not otherwise loaded.&nbsp; Comments?&nbsp;&nbsp;&nbsp;&nbsp; Mount point: /data&nbsp;&nbsp; &nbsp;Size: 2425866240KB (2313 GB)&nbsp;&nbsp; &nbsp;Available: 646797924KB (616 GB)&nbsp;&nbsp; &nbsp;Snapshot: 4947484KB (4831 MB)&nbsp;&nbsp; &nbsp;RAID Level: 5&nbsp;&nbsp; &nbsp;State: redundant&nbsp;&nbsp; &nbsp;Action: reshaping (adding RAID disks, changing RAID level)&nbsp;&nbsp; &nbsp;Percentage: 50.0%&nbsp;&nbsp; &nbsp;Sync speed: 2168 KB/sec&nbsp;&nbsp; &nbsp;Time to completion: 3735.2 minutes&nbsp;&nbsp; &nbsp;Flags 0xC8&nbsp;&nbsp; &nbsp;Type: btrfs&nbsp;&nbsp; &nbsp;RAIDs:&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;md126&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Size: 2901208704&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Level: 5&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Action: idle&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Members: 4&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;md127&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Size: 1952987648&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Level: 5&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Action: reshaping (adding RAID disks, changing RAID level)&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;Members: 4

djtaylor · Answer

Now looking at it via cat /proc/mdstat, 2MB/sec was a good one, it's usually nearer 930KB to 1MB/sec.

Ok, it's slow and i'm impatient but I understand what's going on so i'll just let it chunter away until it's a happy bunny again.

mdgm-ntgr · Answer

Regarding the speed. There is a known issue that is fixed in ReadyNASOS 6.5.0 Beta

The services you are running and also the apps you are running and how heavily you are using the NAS are factors too.

djtaylor · Answer

Yes, i'd noticed that in one of your other posts to someone else. After my near total data loss scare, the unit is currently backing up to a cloud provider (the only other task running) I think the X-RAID notion is neat but i've since ordered 3 more WD Red drives to swap out my 3 old drives, that'll bring all 4 drives up to new WD Reds. I don't see myself doing another storage space upgrade in any time in the future, it'll be faster to flatten the config and start again as I already have a local backup anyway. I realise that the reshape time shouldn't really matter but I kinda like completed processes and to swap out 3 more drives at the present rate would look like around 3 weeks. On the basis that firmware 6.5.0 is just around the corner and that i'd rather wait for my cloud backup to complete (that'll be a few days), i'll just schedule a flatten NAS day and clear it all, fresh firmware and start again. So basically, my original idea to buy a diskless unit and just throw some old spare drives at it as a cheap storage thing has totally turned on its head and become a chunky investment!

StephenB · Answer

djtaylor wrote:So basically, my original idea to buy a diskless unit and just throw some old spare drives at it as a cheap storage thing has totally turned on its head and become a chunky investment!
Using RAID on old disks often doesn't work out well.

Forum Discussion

RN204 resync after successful resync, any idea what's going on?

5 Replies

Related Content

Degraded Resync???

ReadyNAS 716X data- Two volumes after Resync

RN214 Festplatte FAILED während RESYNC

Resync gone wrong

Factory Reset - resync?

NETGEAR Academy

ProSupport for Business