My Readynas Duo is now on its last legs, locking up and dropping off the Network for no apparant reason, however from my investigations I suspect it is also Kernal panic introduced by one of the later firmware upgrades. Third to last release, to be exact (at work at the moment, dont recall the Version).
It sounds more like a filling OS partition to me - which is easily fixed.
Open a new thread on your problem, and we can respond there (rather than hijacking this one). Please do report the firmware version.
Ok so after downgrading from 6.2.3-T1696 to 6.2.0 again the unit took a while to come back online and the screen is stuck on "Booting Upgrading Firmware" But while it's in this state I can access it over the network and all my backups are successfully backing up to it. It has stayed up for 2.5 days now woohoo. When I log into the unit it says device not ready and I don't get any info on the dashboard but I don't care at the moment as long as the unit stays on working.
Some notes to help you guys at Netgear figure this out. maybe these are coincidences, maybe not. maybe worth a try? apparently you have no other ideas how to recreate the problem.
1. I turned off readycloud and it started locking up after less than 2 hours. turned it back on. lasts at least 5 or 6. 2. I turned time machine on. It allowed me to back up my machine almost all the way before the NAS crashed. after I rebooted it from the crash it had to "rebuilding volume" 3. This morning, only the music share was dead. I was able to access the others for a minute or so, and then they all crashed...
were there instructions posted somewhere for how to downgrade back to 6.1.9 when the unit was able to perform the function for which it was designed?
Would you offer a replacement NAS that is not having this problem to exercise good customer service in exchange for sending in the failing unit for diagnostics/forensics? If, as you say, this is not affecting most users, this would not be a financial hardship for NetGear which takes in around 1.2 billion dollars a year. It would also allow you to evaluate these systems that you have mistakenly destroyed and learn from your mistakes so that this doesn't happen in the future. It would be the responsible thing to do. ReadyNAS marketing is directed at businesses; "ReadyNAS lets you do more with your business data than you ever thought you could afford." these failures are causing companies all over the world money every day in IT service calls and lost productivity.
Negative here too. Hangs completely with no response to ping, ssh or http. I've been following this issue/tread since update to 6.2.0, waiting for a fiix without involving in this tread. Now I'm here too, experiencing similar issues as the other ones. I'm running as plain setup as possible (SMB,FTP,SSH and HTTP(S). 4 x 2TB WD Reds, 2 volumes, 2 disks in a raid O and 2 in a JBOD) No backup-jobs, no scheduled disk jobs, no apps. Only a few shares. I DO use networkcard-bonding (ALB), but also tried to use only one connection without any effect regarding the lockup issue.
For me the most 'stable' versions since 6.1.x seems to be versions from 6.2.0 up to (and incuding) the fourth 6.2.3 beta. Then the NAS 'only' freezes once or twice every other day or so. Beta 5 and 6 makes it freeze within hours.
I'll send you my logs too if you think they may show anything you haven't already seen in all the othes one's logs...
We can update this remotely if you give us access (see my PM).
Alternatively if you have a spare disk (must not be from your array) you could power down, remove your disks (label order) and use the spare disk to update firmware the firmware.
I also tried the T1721 but still no go, locks up within a couple of hours, or less if I put some load on it. 😞
EDIT: Ok, so I tried switching out the WD Green I was using to test the firmware with since it's not on the list. Tried with a Samsung I had lying around but that resulted in the same lockup 30-40 min into a copy and 60-90 min when idle.
