Just to clarify, although the Raidar finds the NAS and shows it on the list (but with a 'blue' dot) along with the v1 (which of course is all green) so I can't open the v2's dashboard.
Just to clarify, although the Raidar finds the NAS and shows it on the list (but with a 'blue' dot( along with the v1 (which of course is all green) so I can't open the v2's dashboard.
Understood. But is it giving any other status (indicating a corrupt OS, failed drives, etc)? You can hover the mouse over the various icons, that often gives a bit more info.
FWIW, an alternative way to open the dashboard is to browse to https://nas-ip-address/admin (using the real IP address of course). But that won't work either if the NAS isn't detecting the disks (since the NAS boots from the disks).
I didn't realize that the NAS currently isn't finding disks. Obviously we need to sort that out first (in particular if it is a problem with the chassis, the power, or one or more disks).
Correct, first things first and that's enough for me for tonight so I'll check in again after I've tried another disk. Just to confirm, you can't see any compatibility problems with my Reds, can you?
Thanks for joining the discussion, RayDee. @StephenB may confirm or deny, but I don't believe the Readynas Duo v2 has the ability to change the JumboFrames setting from the Web interface unlike the v1. From what I have read you have to get into the codes to alter it. It doesn't allow alteration of the MTU either which is something else I have researched. Thanks again!
The DuoV2 was clearly designed for a less sophisticated home user, so does not have those settings.
I'm actually wondering if the problem isn't that the drives are only operating at SATA1 speed, which may be related to the odd start-up issue you're seeing. Maybe try plugging in a USB3 device and test speed to it.
FYI, I just fired up my DuoV2 and I get an average read speed of 65.5MB/sec on a 400MB file. That's about half of what a Pro2 gives me, but should be plenty fast enough for streaming HD content.
The DuoV2 was clearly designed for a less sophisticated home user, so does not have those settings.
I'm actually wondering if the problem isn't that the drives are only operating at SATA1 speed, which may be related to the odd start-up issue you're seeing.
He was measuring 1-2 MB/s write speeds before he had the boot problem. Even if there were a jumbo frame problem, jumbo frames wouldn't result in that much of a speed drop. I'm not seeing how SATA1 backplane speeds would account for those initial speed tests either.
Though of course the start-up issue is odd, and we don't know the cause. A failing backplane is certainly possible.
Just in case I do something stupid, could I ask an incredibly basic question please? If I remove the new Red drives from the bays of the v2 and insert one of the old Green drives from the v1 should the NAS just start and read the drive as if it wrote to the drive itself? That Green drive also has HD video on it so it would be a good test if I could just swap one over. That Green drive has an equal mirrored drive in the v1. Are the drive holders interchangeable between the v1 and v2 - the v1 has a push button release while the v2 has a push down lever. Might be safer to just unscrew the drive and put it on the v2 holder to try it out, what do you think?
If I remove the new Red drives from the bays of the v2 and insert one of the old Green drives from the v1 should the NAS just start and read the drive as if it wrote to the drive itself?
No. The v2 will re-format the green drive if you do that (at least one that is working properly).
Have you made on progress with the v2 boot problem?
Afraid not, booting the unit has been hit and miss since I got it. The initial formatting of the brand new Red drives went well and carried out all the transfer of data from my v1 using Rsync no problem, although I know there was one time it wouldn't start the drives but I got it started eventually. After it was all transferred and I tried my first 1080p video was when I found the speed problem with the NTV550, I was shattered as this is the purpose of this particular NAS and I have been very happy with the reliability of my long term v1. The power plug seemed lose in the socket and if I touched it power would stop to the unit. Eventually the plug arced and started melting the plastic surround of the plug which was when I pulled it for good, purchasing a new power supply which didn't solve the booting problem and now I can't get the discs to start at all - I'll keep trying, although it's bed time for me!
That bad power connector may be current limiting the power, which could affect the secondary voltage regulation of the NAS. I've repaired one that was in that condition, and it was just a solder joint that came loose. I re-soldered it and then re-enforced the connector to board interface with some epoxy (which is risky, as it makes future connector replacement much more difficult).
If the connector is broken, it might be difficult to find one that fits perfectly. Bypassing it could be an option, either connecting the supply wires directly or using a "pigtail".
The original Duo design, with the recessed power connector and 90° connector on the supply, was far superior in keeping the connection from being bumped, which can lead to this problem. While it appears they abandoned the recess so they could use a bigger fan, I'm not sure why they went to a straight connector.
Not many on the market here in Australia, and as I am only using it as a basic media server I was trying to minimize costs while increasing capacity. Theory was sound based on my prolonged success with the v1. I'm going to test it with the 500Gb drive it came with and that might confirm if it is a power interface problem or not. I have a good friend who is an electrician so I might have to call in a favour haha! I don't give up easily!!
You're reading my mind @Sandshark, I have a friend who is an electrician so we might rip the back off it and check out the solder joints. He did suggest this himself as a cause but suggested replacing the power brick as a first step. Thanks for reinforcing the idea.
Allllrighty, so the 500Gb drive didn't start either so it's not the drives. Tomorrow I'm off to my local repairman who is going to check out the power socket connection for me.
Oddly, I just had something happen on my OS4.2.31 machine -- a Pro2 -- that sounds similar. On mine, it comes up with "no disks" with two drives installed, but boots with just either one in either slot. I've determined that the internal 12V regulator circuit is not producing sufficient current, even with a 10A external supply. And, unfortunately, it's not the connector, either. So, I wish you the best that it is something simple to fix.
Hey guys, I'm back on the case after having the v2 checked out by my local repairman who gave the internals a clean bill of health and ran it for a week, turning off and on, without it missing a beat. When I got it home, I plugged all the network and ups cables in before turning the unit and guess what......? the hard disks didn't fire up like before I took it to him! I replicated the conditions that the repairman would have been testing the unit by with no external cables plugged in and it started perfectly. After an elimination test I have isolated the problem to the ups monitor cable to the v1 as causing the hard disks not to start - does this make any sense to anybody! If I plug the cable in after it starts there is no problem, but if it is plugged in when the unit is started the drives don't start!!
After an elimination test I have isolated the problem to the ups monitor cable to the v1 as causing the hard disks not to start - does this make any sense to anybody!
What model UPS is the UPS monitor cable connected to?
I'm a bit confused by the "to the v1" bit in your post.
I have 2 x ReadyNas - a ReadyNas Duo v1 and a v2. I have been using the v1 for many years with excellent reliability so bought a second hand v2 for it's increased hard disk capacity and improved performance (the v2 is the one with the network speed issue). The UPS is monitored via a usb cable directly into the v2 while the v1 is monitoring the UPS via a usb cable into the v2 which is all going fine - green lights on both devices in Raidar. When the cable from the v1 into the v2 is plugged in, the v2 doesn't start but when it isn't connected it does start - weird! Plugging it in after the v2 starts gets all green lights on Raidar for both devices.
The UPS is monitored via a usb cable directly into the v2 while the v1 is monitoring the UPS via a usb cable into the v2 which is all going fine - green lights on both devices in Raidar. When the cable from the v1 into the v2 is plugged in, the v2 doesn't start but when it isn't connected it does start - weird! Plugging it in after the v2 starts gets all green lights on Raidar for both devices.
I'm not surprised it misbehaves on boot. It's weird that the USB cable connection between the v1 and v2 works at all.
What you are supposed to do with most ReadyNAS is to monitor the UPS status over ethernet (enabling network monitoring on the NAS connected to the UPS, and setting up that monitoring on the other NAS). You need to also protect the network connection between them (easy if the two NAS are connected to the same router or switch).
But as far as I can see from the manual, the network monitoring feature isn't exposed in the v2. It could be there anyway - the v2 manual doesn't have many screenshots. It's also possible it's automatically turned on - so if you don't see it in the v2 dashboard, you could try using setting up the v1 to monitor the v2 over ethernet on the v1 anyway, and see if also works. If it doesn't, I'd probably just get a second UPS.
Seriously, you're kidding me!! I feel like such a doofus.......but happy if this may be causing some of my issues! I assumed that because the ups uses a usb cable to provide info to the NAS, you used the same to the second one! Can't wait to see what happens when that cable is pulled - fingers crossed that it has had something to do with the ethernet issue too....... but doubtful! You're right though, all green lights on the v1. FYI, I had all the ups monitoring setting correct on both the v1 and the v2 which explains why it was working - except it was monitoring via the network, not the usb haha!!
FYI, I had all the ups monitoring setting correct on both the v1 and the v2 which explains why it was working - except it was monitoring via the network, not the usb haha!!
Yeah, that does explain it.
It is important to make sure the switch(es) or router to which the two NAS are connected are also protected by the UPS (though they don't need to monitor it). Otherwise the network connection drops when the power fails, so the v2 won't get a shutdown message when the UPS battery drains.
Note if the NAS are both connected to the same switch, you don't need to protect the router - just the switch.
GOOD NEWS! Now that I have the power issue all sorted and set up with a new power supply I thought I would tackle the network issue again. First thing I tried was plugging the NAS into a different switch with a longer cable and BINGO, speed increased to greater than the v1 which is how it is meant to be. Next was to plug that longer cable into the original switch and it was still perfect which means that despite trying two different cables before the power supply problem and different ports on the original switch, both those patch cables must have been faulty! What a pain, but so happy now as I have two working ReadyNAS, both with redundant drives and UPS protection to a new power supply.
So very thankfull for the help and advice of @StephenB & @Sandshark, apologies for wasting you time on what eventually was such a simple fix despite the power issue distraction. I'm now going through my box of cables and testing them on the NAS, throwing out any that don't work to avoid wasting time in future. Thanks again, and hopefully my experience can assist someone in the future.
