i've recently purchased one of the Netgear ReadyNAS NV+ V2 units and have become very unhappy with it. it started out ok and could copy files to it at good rate, now that the unit is over 80% full i've been coming accross the smbd stall on IO Wait issue that seems to plague this unit :(after coming to these fourms i found that there are many other users with the same issues and none of the solutions they have had for them posted around converting to EXT3 has made the copy issues any better for me.i have linked the other topics i could find with same issues that have been plagueing me so far. i have logged a support case (20047616) with netgear but their "remote access policy" is very bad and i can't agree to it. viewtopic.php?f=21&t=63992 viewtopic.php?f=21&t=64739 viewtopic.php?f=21&t=67310 viewtopic.php?f=21&t=66731

Converting to EXT3 helps, does it? And what do you do if you already have all your disks in EXT3???!!!Netgear have never impressed me on quality nor performance, but the Sw engineering quality control really hits the bottom. Have they ever heard of version control? Have in gods name can an old bug pass through to a subsequent release - albeit a Beta???!!!This was the final blow for me- getting in to my car to go and by a Synology or Qnap - whatever bet never again Netgear and Readynas!

Converting to EXT3 will help. Again thank you NETGEAR for quality control.You need to download your data because it will be wiped (from what I've been told). Yes, you need to give them root OR add drives to get below 80%.. I did both ...

I'm looking into this issue, from the logs I see that you converted to ext3 yourself, and you're still running into the issue, right? I'm chasing down a few things, could you confirm, are you storing a large amount of small files on the device (checked volume stat, if my math is correct, average of 3.5MB per file)?Are you only using CIFS/SMB to copy files to the NAS?

Skywarp wrote:I'm looking into this issue, from the logs I see that you converted to ext3 yourself, and you're still running into the issue, right? I'm chasing down a few things, could you confirm, are you storing a large amount of small files on the device (checked volume stat, if my math is correct, average of 3.5MB per file)?Are you only using CIFS/SMB to copy files to the NAS?I have same problems... converting volume to ext3 solve everything. This problem is related only to filesystem itself not to anything else.This is propably kernel bug, somewhere at journaling code. I found it on Synology and QNAP forums and people are very angry because of this.There's nothing in logs only IOWaits raises to 100% after any write is performed and system is not responsive for some seconds/speed drops to 10MB/s or lower.Maybe disabling journaling in ext4 can help, but I don't trust this filesystem for now.I saw this problem when volume is aprox. 85% full and I have a lot small files on it.When you format ext3 volume you can switch to ext4 driver and in that situation everything goes wrong.Journal must be recreated while you are going back to ext3 - if not, ext3 have same problems as ext4 (100% IOWaits).Perfomace with nearly full volume on ext3 is ~50MB/s write ~80MB/s read - not bad for ARM platform.

Skywarp wrote:I'm looking into this issue, from the logs I see that you converted to ext3 yourself, and you're still running into the issue, right? I'm chasing down a few things, could you confirm, are you storing a large amount of small files on the device (checked volume stat, if my math is correct, average of 3.5MB per file)?Are you only using CIFS/SMB to copy files to the NAS?yeah i converted to ext3 myself "mkfs.ext3 -m 0 /dev/c/c" and still have the issue, last night i upgraded to 5.3.7 as it adds an option in the web GUI to disable write caching and am trying to fill drive again past 80% and hopefully to 99% but am not very hopefull.yeah im fairly sure most of my files are farily small, only a few larger files. im only using CIFS/SMB to copy via the lan, im using rsync for some remote backup from another site to here.have been trying to figgure out if NCQ is enabled on the device as `cat /sys/block/sda/device/queue_depth` results "31" (suggesting it's on) and trying to set it to "1" results in error.also trying to figgure out why/how to stop the segate drives "chirping" as they load/unload the heads periodaccly as after ~1month my Load Cycle Count is over 10k for each drive as reported in smart.EDIT:Currently with firmware 5.3.7 and write cache turned off via the GUI i've managed to copy about 180gb more to the drive with some acceptable speed but after that mark im getting about 1minute of IO Wait before starting to copy a file and then more IO Wait during copying the file to the drive. the test set of data have files between 1gb to 3gb files. currently at about 875GB free space reported.

NV+ V2 stalling when 80%+ full (20047616)

197 Replies

Replies have been turned off for this discussion

Tokfan

Aspirant

May 31, 2013

hauser wrote:
janforman wrote:
Tokfan wrote:
I sent my NAS back to the store and just got my money back lol.

So I have this version installed... but with ext3. I don't have problems before and don't have any now.

But what is great
a) fixed power-on (i must unplug power sometimes before)
b) fixed power scheduler (don't work sometimes)
c) kernel is newer (maybe some patches are here) Linux version 2.6.31.8.duov2 Thu Apr 18 18:24:47 HKT 2013

Anyone can confirm that problems are gone under ext4?

with 5.3.8-T20 it still crashed before 100% full, Best I got was <10gb free before it crashed which was still unacceptable.

from what I understand 5.3.8-T20 == 5.3.8 final

I had 4x2Tb in xraid2 i.e. 5,4Tb free space and it didn't let me use the "last" 724Gb...
Now I'm looking at the new RN104, any1 know if it has the same shitty problem?

mdgm-ntgr
NETGEAR Employee Retired
May 31, 2013
The 104 has double the RAM, uses a newer kernel and the BTRFS filesystem versus the EXT4 filesystem the NV+ v2 uses. The 104 has a newer CPU but it is still an ARM one. I would recommend looking at the 314 which has a dual-core Intel Atom CPU
ihartley
Tutor
Jun 01, 2013
Are these kernel patches something new, or something that has been around for ages but never rolled up in an update??
davexyz
Aspirant
Jun 07, 2013
Well over six months for this fix

Anyway updated to 5.3.8 whilst in ext3
Transfered 8TB to a backup device (4 and a half days)
Factory default
Copy back 8Tb another 4 and a half days
and it worked

at the moment 176Gb free on device

What a waste of 9 days of my life for this transfer and the fact that the device should have worked in the first place. then it takes over six months to get a fix!!

I have another 3 of these devices still to update currently in ext3 but I will save that for another time I need the device which I transfered data to for storing data.

janforman

Aspirant

Jun 08, 2013

davexyz wrote:
Well over six months for this fix

Anyway updated to 5.3.8 whilst in ext3
Transfered 8TB to a backup device (4 and a half days)
Factory default
Copy back 8Tb another 4 and a half days
and it worked

at the moment 176Gb free on device

What a waste of 9 days of my life for this transfer and the fact that the device should have worked in the first place. then it takes over six months to get a fix!!

I have another 3 of these devices still to update currently in ext3 but I will save that for another time I need the device which I transfered data to for storing data.

davexyz wrote:
Well over six months for this fix Anyway updated to 5.3.8 whilst in ext3 Transfered 8TB to a backup device (4 and a half days) Factory default Copy back 8Tb another 4 and a half days and it worked at the moment 176Gb free on device What a waste of 9 days of my life for this transfer and the fact that the device should have worked in the first place. then it takes over six months to get a fix!! I have another 3 of these devices still to update currently in ext3 but I will save that for another time I need the device which I transfered data to for storing data.

You can go from ext3 to ext4 without data loss because it's forward compatible (not backward).

davexyz
Aspirant
Jun 08, 2013
What are the commands for this?

I assume I would ssh into the box

I have no linux so if you could post the commands as you did for setting up in ext3. I followed that
Thanks
janforman
Aspirant
Jun 08, 2013
davexyz wrote:
What are the commands for this?

I assume I would ssh into the box

I have no linux so if you could post the commands as you did for setting up in ext3. I followed that
Thanks

You must use SSH access and replace ext3 back in /etc/fstab to ext4

then run this from prompt
tune2fs -O extents,uninit_bg,dir_index /dev/c/c
reboot now.

run filesystem check while you rebooting NAS (again)from web frontend.
davexyz
Aspirant
Jun 09, 2013
OK I have updated fstb

entered tune2fs ...
rebooted

entered the fsck... {Enter}

and it has come back with

"WARNING the file system is mounted if you continue you ***WILL*** cause ***SEVERE*** filesystem damage

Proceed y/n"

At this point I stopped to get further advice.

Is It safe to proceed?

davexyz wrote:
What are the commands for this? I assume I would ssh into the box I have no linux so if you could post the commands as you did for setting up in ext3. I followed that Thanks

janforman

Aspirant

Jun 10, 2013

davexyz wrote:
OK I have updated fstb

entered tune2fs ...
rebooted

entered the fsck... {Enter}

and it has come back with

"WARNING the file system is mounted if you continue you ***WILL*** cause ***SEVERE*** filesystem damage

Proceed y/n"

At this point I stopped to get further advice.

Is It safe to proceed?

davexyz wrote:
OK I have updated fstb entered tune2fs ... rebooted entered the fsck... {Enter} and it has come back with "WARNING the file system is mounted if you continue you *WILL* cause *SEVERE* filesystem damage Proceed y/n" At this point I stopped to get further advice. Is It safe to proceed?

No - my mistake, please check filesystem by Readynas frontend option while rebooting or shutdown.

davexyz
Aspirant
Jun 10, 2013
Good job I checked

Reboot with volume check
Volume check completed, 7 hours later (8.1TB)

Downloaded logs from unit looked at mounts.log

gives "/dev/c/c on /c type ext4"

So at long last the unit is in the state it should have been in upon release.

Thanks Jan

1) for the initial solution to format in ext3 which allowed full use and 2)for a time and data storage saving solution for ext4 useage without a factory reset.

now for the other units

By the way if usb drives are attached it will move these up one ie USB_HDD_1 becomes USB_HDD_2 so unplug before you do this

or if your usb name has changed , unplug, ssh into box, edit storage.conf which is in /etc/frontview/usb

remove all settings and save file,plug usb drive back in

Forum Discussion

NV+ V2 stalling when 80%+ full (20047616)

197 Replies

Related Content

Stalls from WAC730

Firmware update stalls for EX3700

Nighthawk AC1750 setup stalls at routerlogin

RN214 File transfers stall

ReadyNAS RN214 check root fs - booting 47% - stalled

NETGEAR Academy

ProSupport for Business