NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tim_hamblin
Jan 07, 2012Aspirant
Initial findings with new Duo V2
I've already sent a few posts about my initial experience with the new Duo V2, but thought it easier to put it into one feedback post...
I've previously used the ReadyNAS Duo (V1) for a few years, with a final hardware configuration with 1GB RAM and 2x Seagate 2TB HDDs (ST2000DL003)
So, back to the new Duo V2 (running arm 5.3.2), this was the RND2000-200EUS (diskless) model - I'm UK-based, but there doesn't appear to a UK SKU, but the EU model does include a UK and Euro power cables...
Hardware Compatibility List:
This doesn't appear to have the 2TB version of my previous Seagate HDDs, but does have the 1.5TB version, so I initially installed the two ST2000DL003 drives.
I later replaced these with Western Digital (WD20EARX) 2TB HDDs (see below why)...
GUI:
Loads much faster, bit more bling, simpler to navigate, etc...
However, having been used to Front View, it is a bit limited. I can understand this, as it probably targetted to the home-user more than the pro-sumer...
Performance:
Read/writes over the network greatly improved - 40-50MB/s... However, going back to the GUI - you can't adjust the MTU, and currently it is not set up for Jumbo Packets ('ping -f -l' can easily prove that), would this improve performance?
(Works great over wireless too - but didn't benchmark).
DNLA:
I guess still under development - if you modify a file (e.g mp3 ID tag), it will still broadcasts the original version. Going back to the GUI - there is no option to 'Rescan Media'... Hopefully resolved with new firmware.
ReadyNAS Remote:
Doesn't work with iOS devices (iPhone/iPad, etc) as yet. Hopefully resolved with new firmware.
Volume Scan (i_block errors):
Here's my main issue - which might be a problem with my particular Duo V2...
When I did a Restart with Volume Scan, I would get a notification email about 'Volume scan found and corrected errors'. These errors were all related to: Pass 1: Checking inodes, blocks, and sizes - Inode 26181655, i_blocks is 739472, should be 739480. Fix? yes (for about 4-10 different Inode/i_block references). This occured after heavy writes made to the Duo. Once the Volume Scan corrected these errors, subsequent restarts had no errors until a large amount of more data was copied to the Duo.
I initially thought this was due to the Seagte drives not being on the HCL, so went out and purchased two new WD drives (WD20EARX) that were on the HCL... I rebuilt the Duo (volume build takes about 7 hours!). However, as before - started to get the same i_block erros on restart/volume scan... I've just reinstalled the arm 5.3.2 firmware and kicked off a factory reset, so we'll see what happens next...
Summary:
Much improved performance,but still early days in terms of the firmware... Fustration at possible RMA for a brand new (week-old) Duo V2...
Can someone please shed more light on these Inode/i_blocks erros please (below is a last example prior to reinstalling the firmware)...?
***** File system check performed at Sat Jan 7 10:11:28 WET 2012 *****
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Inode 26181655, i_blocks is 739472, should be 739480. Fix? yes
Inode 26181996, i_blocks is 547568, should be 547576. Fix? yes
Inode 26182037, i_blocks is 671744, should be 671752. Fix? yes
Inode 26182083, i_blocks is 594160, should be 594168. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/c-c: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/c-c: 14538/30285824 files (1.0% non-contiguous), 79676625/484573184 blocks
I've previously used the ReadyNAS Duo (V1) for a few years, with a final hardware configuration with 1GB RAM and 2x Seagate 2TB HDDs (ST2000DL003)
So, back to the new Duo V2 (running arm 5.3.2), this was the RND2000-200EUS (diskless) model - I'm UK-based, but there doesn't appear to a UK SKU, but the EU model does include a UK and Euro power cables...
Hardware Compatibility List:
This doesn't appear to have the 2TB version of my previous Seagate HDDs, but does have the 1.5TB version, so I initially installed the two ST2000DL003 drives.
I later replaced these with Western Digital (WD20EARX) 2TB HDDs (see below why)...
GUI:
Loads much faster, bit more bling, simpler to navigate, etc...
However, having been used to Front View, it is a bit limited. I can understand this, as it probably targetted to the home-user more than the pro-sumer...
Performance:
Read/writes over the network greatly improved - 40-50MB/s... However, going back to the GUI - you can't adjust the MTU, and currently it is not set up for Jumbo Packets ('ping -f -l' can easily prove that), would this improve performance?
(Works great over wireless too - but didn't benchmark).
DNLA:
I guess still under development - if you modify a file (e.g mp3 ID tag), it will still broadcasts the original version. Going back to the GUI - there is no option to 'Rescan Media'... Hopefully resolved with new firmware.
ReadyNAS Remote:
Doesn't work with iOS devices (iPhone/iPad, etc) as yet. Hopefully resolved with new firmware.
Volume Scan (i_block errors):
Here's my main issue - which might be a problem with my particular Duo V2...
When I did a Restart with Volume Scan, I would get a notification email about 'Volume scan found and corrected errors'. These errors were all related to: Pass 1: Checking inodes, blocks, and sizes - Inode 26181655, i_blocks is 739472, should be 739480. Fix? yes (for about 4-10 different Inode/i_block references). This occured after heavy writes made to the Duo. Once the Volume Scan corrected these errors, subsequent restarts had no errors until a large amount of more data was copied to the Duo.
I initially thought this was due to the Seagte drives not being on the HCL, so went out and purchased two new WD drives (WD20EARX) that were on the HCL... I rebuilt the Duo (volume build takes about 7 hours!). However, as before - started to get the same i_block erros on restart/volume scan... I've just reinstalled the arm 5.3.2 firmware and kicked off a factory reset, so we'll see what happens next...
Summary:
Much improved performance,but still early days in terms of the firmware... Fustration at possible RMA for a brand new (week-old) Duo V2...
Can someone please shed more light on these Inode/i_blocks erros please (below is a last example prior to reinstalling the firmware)...?
***** File system check performed at Sat Jan 7 10:11:28 WET 2012 *****
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Inode 26181655, i_blocks is 739472, should be 739480. Fix? yes
Inode 26181996, i_blocks is 547568, should be 547576. Fix? yes
Inode 26182037, i_blocks is 671744, should be 671752. Fix? yes
Inode 26182083, i_blocks is 594160, should be 594168. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/c-c: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/c-c: 14538/30285824 files (1.0% non-contiguous), 79676625/484573184 blocks
26 Replies
Replies have been turned off for this discussion
- amidrocGuideDid tech support give you a reason? I am experiencing the same problems with my NV+ V2 running ARM 5.3.2 and two WD20EARX-00PASB0. I have a case opened up and waiting for a response.
- tim_hamblinAspirant
amidroc wrote: Did tech support give you a reason? I am experiencing the same problems with my NV+ V2 running ARM 5.3.2 and two WD20EARX-00PASB0. I have a case opened up and waiting for a response.
I ended up pushing back on the Support... They initially just closed the case for no reason... The Health Status is a bit confusing as all 'LEDs' show Green status. But Volume Scan finds and corrects errors (i_blocks related) after heavy writes made to the Duo V2... This is not just with WD HDDs, as I found this to be an issue with Seagate HDDs...
My other issue was the disappearing Add-ons... I've done some more testing - this might be related to a corrupt ARM 5.3.2 firmware from ReadyNAS website (which I have downloaded several times)...
Factory Defaults >> Add-ons available in Dashboard to install and configure
(Re)install 5.3.2 firmware downloaded from ReadyNAS website >> Add-ons disappear from Dashboard
Install 5.3.3[T8] beta firmware >> Add-ons available
Roll-back to 5.3.2 firmware from ReadyNAS website >> Add-ons disppear from Dashboard... - tim_hamblinAspirantWell finally received my replacement ReadyNAS Duo...
However, I've now lost complete faith in NetGear... They've shipped me a ReadyNAS Duo Version 1 (Sparc-based unit), not the new ARM-based ReadyNAS Duo Version 2... :evil: :evil: :evil:
New ticket raised #17703285 - Sunday_Afterno1AspirantNow that really sucks! I hope they send the replacement for the replacement overnight.
You probably know this already, but it bears repeating: don't, repeat, don't put your v2 disks in a v1 unless you want to lose your data! - yoh-dahGuide
tim_hamblin wrote: Well finally received my replacement ReadyNAS Duo...
However, I've now lost complete faith in NetGear... They've shipped me a ReadyNAS Duo Version 1 (Sparc-based unit), not the new ARM-based ReadyNAS Duo Version 2... :evil: :evil: :evil:
New ticket raised #17703285
I understand your frustration and apologize for the unnecessary problems you're going through. We're addressing this issue at our RMA center, so hopefully we won't run into the confusion in the future. - tim_hamblinAspirantWell I got a repy back from NetGear Support last night.... Support clearly don't read the ticket history (although I'm now on my thrid support ticket)...
"Thank you for choosing NETGEAR. My name is <first-name> and I will be your support engineer. Since we are doing this online, it may require a few e-mail exchanges before we can resolve the issue. We will do our best to help resolve your case in the least possible time.
I understand that you recently got a ReadyNAS Duo replaced with a ReadyNAS Duo version 2. Understandably you want the correct device sent to you.
You could have received the version 2 if we are out of stock of the version 1 of the Duo. I see that you're located in the UK. It would be best to contact them over the phone and have them check the warehouse. They can be reached at +44(0)8448 75 4000"
Alas, this is not the response I expected...
The faulty unit I shipped back for RMA was the new ReadyNAS Duo V2 (part number: RND2000-200EUS, serial number: 2UM11AEK0088D) - this is the latest ARM-based model. What I received back is the older ReadyNAS Duo (model number: RND2000-200WWB, serial number: 2102927J00C5F) - which is Sparc-based. These are not the same NAS units - if had put my original WD20EARX HDDs drives from my RND2000-200EUS into the replacement RND2000-200WWB I would have lost all my data. In light of the fact that NetGear are unable to provide the correct RMA unit, the only logical solution is for them to provide a new retail unit (especially as it was only one week old when I raised my original support ticket). I also believe that I should not have to pay any shipping costs in returning the incorrect RMA replacement back to NetGear....
I find it 'amusing' that it is now suggested for me to phone and check their warehouse stock - I am the customer!!! - PapaBear1Apprenticetim_hamblin - you say the model you received from Netgear as replacement on your RMA is part number RND2000-200WWB. The 200 would indicate a v2. Can you verify that you have the small fan on the rear and the front door says just ReadnNAS Duo.
Also, if you have a spare hard disk, power up the replacement and see what version of RAIDiator is on it.
I know that you feel as though since the unit was only a week old when it failed, you should receive a new unit, and that does in fact happen from time to time when no suitable refurbished unit is available, but the policy (like most companies) is to provide a refurbished unit as RMA replacement. When I got my first NVX, I could not get it to boot, and worked with the technician at Netgear. At one point, it appeared I had a bad chassis, and he was preparing an RMA, when I removed the memory module and reseated it and the unit booted just fine (and has been running fine for 18 months now). He was going to give me an RMA number, but said I should see if the vendor would replace it, for they would replace it with a brand new unit whereas Netgear would ship a refurbished unit. He also commented that I paid for a new unit and should get one.
Another thought, I believe you have had the unit less than 90 days and you get 90 days of free telephone support. Have you tried calling Netgear tech support and then get the case escalated? Although, I am sure you have steam coming out of your ears, just keep in mind that persistence over anger is far better. - mdgm-ntgrNETGEAR Employee Retired
PapaBear wrote: tim_hamblin - you say the model you received from Netgear as replacement on your RMA is part number RND2000-200WWB. The 200 would indicate a v2.
Unfortunately a number of v1 units were labelled RND2000-200 (Have a look at How to tell whether I have a Duo v1 or Duo v2 or NV+ v1 or NV+ v2), which is very confusing I know. The WWB is for refurbished.
Now this may have changed but as the Duo v2 is a pretty new product there would either be no refurbished units or a very limited supply of them. If NetGear has no refurb v2s they should replace with a new unit. - PapaBear1ApprenticeI was not sure about the 200, did know the WWB indicated a refurbished unit (which would be a little unusual this fast after the release of a new model) the fan is probably the dead cinch give away, as doors and trim and stickers could be swapped, but that fan difference would indicate a totally different chassis. I have sent a PM to a member who seems to have close contact with tech support.
All the more reason that the new Arm units should have had different model names. Given the pattern of the Ultra and Pro Series, something with a 2 for the 2 bay and 4 for the 4 bay. Would have been a lot less confusion and allowed for a 6 bay ARM based entry level unit as well. (I know I'm preaching to the choir here :? ). Tatooine 2,4,6 has a nice ring. - tim_hamblinAspirantDefinately the older ReadyNAS Duo - rear panel has a 60 mm fan, only USB 2.0 ports and recessed power socket. Also the chassis is black, not dark grey. The front lower edge below the door has ReadyNAS Duo on it, not ReadyNAS Duo V2. And the final clue is the 15 Sep 2010 date stamp on the brown refurb box...
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!