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

OK perhaps I did not make myself clear. I have enabled ssh access , "reformatted" my data partition, c, to ext3 and now am adding additional drives and expanding. I assume that the process does not alter the partition i.e convert back to ext4 for the data partition. Which of the log files will tell me the partition information.

I believe that the Readynas NV+ V1 data partion is ext3 and I have no issue with expansion and filling these to the max!

janforman wrote:
But who...? I have IBM Enterprise San, Synology-Rack-NAS and everything seems like joke to me :D Thanks to full SSH access to Netgear products - I can fix it by myself :) - no problem... for this price it's not that bad.

i'll do what i should have done in the first place, roll my own MAS system using normal PC hardware. that way i not only have full control over it, but i can do so much more with it!

Hi...

I moved to ext3 couple of months back and this seemed to resolve my issues.

However I have now had a drive failure. On replacing the failed drive the unit will get stuck on 'RAID sync started on volume C.' What then happens is the light for 'no.2' bay starts flashing, even though it is No.1 bay that is out.

The GUI reports the volume as 'redundant' but only 3 of the 4 green lights are on the icon (?). After a restart of the unit *it does not mount my volume and refuses to* - so I have no access to any of my data.

To resolve this it is necessary to remove my new disk and restart the unit again. It then comes back saying 'unprotected' but I can at least access my data.

This unit is 100% stock apart from switching to ext3. I suggest somebody looks into whether using this causes issues for DR scenario. Seems to suggest from my experience this may interfere with this.

Netgear support told me they tested this problem on a unit in their offices and couldn't re produce the problem. Clearly this was lies!

Oh also my time machine stopped working when I went to ext3.

cync wrote:
...Netgear support told me they tested this on a unit in their offices and couldn't reproduce the problem. Clearly this was lies!

I understand that you are frustrated, but there is nothing in your post that supports a claim that they are lying to you.

cync wrote:
...To resolve this it is necessary to remove my new disk and restart the unit again. It then comes back saying 'unprotected' but I can at least access my data.

My suggestion is to (a) backup up your data while you are in this unprotected state. Then (b) delete the partitions on the new disk (on a PC), and then reinsert it while the NAS is running.

BTW, what model disk is the new one? Also, did you check with the vendor to see if there is a needed firmware update?

I asked the support guy and he said they had tested this on a unit they have (as I had asked him to). I guarantee you they have not because this will have an impact on 100% of their units. Sorry but this is likely an issue with kernel. IMO this is a faulty product.

I don't have 5 TB of space elsewhere so I am stuck running my NAS in degraded mode.

The new disk is exactly the same model as the old one. There's no firmware update. I am looking through the logs at the moment to see if i can find anything of interest.

cync wrote:
I asked the support guy and he said they had tested this on a unit they have (as I had asked him to). I guarantee you they have not because this will have an impact on 100% of their units.

So your assertion is that any disk replacement on any NV+ V2 will fail in this way? How many units have you tried this on??? Perhaps some other v2 owners who have tried replacing disks can comment.

If the not-clearly-identified problem is really that ext4 doesn't work well when the disk volume gets full, I agree that is likely systemic. Though I don't think that would be a kernel issue, just a limitation of ext4.

Anyway, I'd still delete the disk partitions on the new drive and re-insert it. I'd think you should also run vendor tools on it while it was in the PC.

I would also invest in drives for backup - speaking from personal experience, a RAID array is not enough to protect against data loss.

StephenB wrote:

cync wrote: I asked the support guy and he said they had tested this on a unit they have (as I had asked him to). I guarantee you they have not because this will have an impact on 100% of their units. So your assertion is that any disk replacement on any NV+ V2 will fail in this way? How many units have you tried this on??? Perhaps some other v2 owners who have tried replacing disks can comment. If the not-clearly-identified problem is really that ext4 doesn't work well when the disk volume gets full, I agree that is likely systemic. Though I don't think that would be a kernel issue, just a limitation of ext4. Anyway, I'd still delete the disk partitions on the new drive and re-insert it. I'd think you should also run vendor tools on it while it was in the PC. I would also invest in drives for backup - speaking from personal experience, a RAID array is not enough to protect against data loss.

It's not ext4 limitation, because can affect ext3 as well (when you touch journal with ext4 driver). if this is not a bug what it is?
This is problem with driver or journaling in it - not file format!

But if anyone have free time - he can try to disable journaling in ext4 (because I think that this can solve problems).

I installed the EnableRootSSH_1.0-arm.bin add-on through the web GUI, restarted the NAS, went to run the add-on so that I could change this to Ext3, but the add-on isn't there, only ReadyNAS photos.

Also, I received a notification : "Successfully enabled root SSH access. The root password is now the same as your admin password."

Did I miss something?

Snipe3000 wrote:

hauser wrote: Snipe3000 wrote: Hey guys, I started running into this stalling issue at about 85% and pretty much can't add anymore data to the device. Sounds like I'm going to have to remove all the data before I can fix it correct? I'm a bit new to this, but how do I convert the file format to ext3? Is that done within the web interface? Thanks for me i did the below to get it to work better for me (after removing/backing up data on the drives) 1) Update firmware to 5.3.7 2) in the webGUI under System -> Settings -> Performance untick "Enable disk write cache" 3) use enable root ssh addon http://www.readynas.com/?p=4203 4) ssh into nas and edit /etc/fstab (vi /etc/fstab) change: EXT4 to EXT3 for mountpoint /c and save file (:wq) 5) reboot 6) mkfs.ext3 -m 0 /dev/c/c 7) tune2fs -O ^dir_index /dev/c/c 8) reboot 9) copy files to nas effectivly that's what it summates to of all of what i've done to the device since getting it to get it to the point today where i could fill it untill it had ~30mb left free still have an issue with delays in starting to copy larger files to the drive when it's 85%+ full, but it let me fill the drive. Cool, It will be a little bit before I can try this, I have to get some new hard drives to backup the NAS (7 TB). What is dropping the journal? is that something I should do as well?

Ok, I was able to get into the NAS using PuTTY, but I'm not stuck at step #4, when I type 'vi /etc/fstab' I get a list, but I'm not sure how to change it from EXT4 to EXT3 for mountpoint /c and save file.

I completed the steps and know nothing about linux. I discovered that vi is actually the command for the editor so first you have to "understand" how the editor works Simply you can move about with the arrow keys to enter edit mode you have to press [esc] key. then you can edit. You have to revert to command mode to save the file. google "vi editor" to get pages which describe the editor. and that should get you through that is what I did. sorry if this does not help