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.
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.
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."
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 😎 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
this is the worst thing I have ever owned! it genuinely is. This is a total joke now.
Initially I had the 80% full issue. Support said it isn't an issue. So I have moved to ext3, resolved the issue.
I am now stuck on 3 disks because it is shite (won't re-build the array - doesn't even give me a decent reason! And on restart the volume disappears..). All my disks are perfect - I've tested them independently at length.
Now I have tried updating the firmware. What has happened is the unit is stuck on 'installing addons'. It won't get any further.
I have tried an os- reinstall but this does not fix the issue.
So now I cannot even use my unit! 🙂 Fantastic stuff. Anyone looking to buy one of these (or by extension *any* readynas) I would strongly recommend you avoid it. My experience has been horrendous.
All I have done is change the file system to ext3 - this unit has had nothing else changed on it at all - apart from enabling root access.
the unit isn't duff. the software is. they can't have tested this can they!
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
I was able to edit it, but now its all messed up, and I dont know how to reset it to start over. Does anyone know how to do that?
When I enter in Step #6 mkfs.ext3 -m 0 /dev/c/c I get: Could not stat /dev/c/c --- No such file or directory The device apparently does not exist; did you specify it correctly?
** I did a factory reset and started over. That seems to have fixed the problem. I finished the steps for EXT4 to EXT3, and I'm only starting out with 2 drives in there for now. There seems to be a recovery going on right now that's going to take 8 hours. Is this normal? Both drives are empty.
I'm at 80% again, and its doing the same thing as before where it stops working, this is after the EXT3 conversion. I also can't do volume scans anymore. The only way to shut down the device when it starts freezing is to pull the power plug. I thought the EXT3 fix was suppose to resolve this?
***** File system check performed at Wed Mar 6 09:48:00 PST 2013 ***** fsck from util-linux-ng 2.17.2 /dev/mapper/c-c: recovering journal /dev/mapper/c-c contains a file system with errors, check forced. Warning... fsck.ext3 for device /dev/mapper/c-c exited with signal 9.
I'm not able to access my data anymore and I can't access the configuration web portal. Has this happen to anyone?
I am having a nightmare getting Netgear support to acknowledge this problem. They keep insisting that what I have is a one-off problem. Every time I point them to these forums they go silent and I dont hear from them for days?!!! From what I've read downgrading to EXT3 doesn't actually seem to help? I've read about users having problems expanding the array and users that STILL get stuck at 80% full disk space. It is going to be a huge hassle for me to wipe my units and restore all the data. It looks a though QNAP have released a firmware patch for this bug so why haven't Netgear?!
This is a NAS, its primary purpose is to store data, therefore if you can't write data to it all you have is an expensive 'Netgear' branded paper weight. It is infuriating and their support staff are patronising and unhelpful. I'll keep updating my post at viewtopic.php?f=21&t=69560 with anything I find out.
IMHO 'proper' technical support should not be so hard on the user while providing so little benefit. Who are the NTGR engineers that can make changes to the firmware and why don't they read the forum, arguably the best source of feedback from the people that use the product they are supporting?
IMHO 'proper' technical support should not be so hard on the user while providing so little benefit. Who are the NTGR engineers that can make changes to the firmware and why don't they read the forum, arguably the best source of feedback from the people that use the product they are supporting?
I don't disagree.
Though from a practical perspective, robclark41 needs to get help for his specific problem. Requesting escalation to L3 is one strategy that might get him there faster.
I didn't want to sound like I was disagreeing with the suggestion to escalate and agree it is a valid course of action. Unfortunately I let my frustration color my words. It would seem a solution may be out there but there does not appear to be enough communication between the user base and NTGR to lead us to believe they are aware of or are working on the solution.
Hi All, Sorry for the late response - I have been in contact with L3 at Netgear who I have finally managed to convince that they have a serious problem with these units. They have given me a firmware patch to test but unfortunately it hasnt made any difference. At least they are working on it now...
Funny after no reply on my open case about this issue for 3 months I finally also got a software patch
I questioned what does it do before I installed the reply was "As far as could get this from Engineering, this changes a few runtime variables to limit searching for space to write to on the disk, this should make it much more responsive when writing when full.
But according to them it should solve the hanging when trying to write when getting closer to full in certain situations. "
i've had my case open for about 3.5 months now and still haven't got any help from netgear.
level 2 wont advance the case to level 3 level 3 won't talk to me unless i agree to the dodgy "remote access policy" (i don't agree to the terms of it) customer services response so far: "We really want to work with you to resolve the issue however, at this stage, we still need to do further technical troubleshooting to find out exactly what the issue is."
at least you guys seem to have gotten a little further with your cases?
I questioned what does it do before I installed the reply was "As far as could get this from Engineering, this changes a few runtime variables to limit searching for space to write to on the disk, this should make it much more responsive when writing when full.
Hauser, I am also having a nightmare with Netgear support. It is unbelievably bad. The last patch they gave me to fix the problem did not work. They have now said 'accept our remote access policy or we will close the case'. I find their level 2 support guys rude, arrogant and unhelpful. Unless I give them unrestricted access to my unit and all my personal data they will not help me. It is a terrible way to do business, if only there was somewhere official we could complain about this and force a solution out of them. I have conceeded to letting the L3 guys remote onto my PC but said I wanted to be there when they did it so I could see what was going on. This apparently is not aloud, they prefer to snoop, steal and mess with all your data in the privacy of their own offices in their own time. What annoys me the most is that they will not try and reproduce the issue in a test lab. It is very simple and easy to reproduce but they will not do it. This make me furious, with one fell swoop it would tell them that this is a general issue and not restricted to a few cases. I'm at my wits end... what to do with these idiots?!
