I have been playing around with a semi-functional RD5200 running OS6.9.5 (yes, a ReadyData configured as a ReadyNAS). The problem it has can make the drives not visible at boot. When that happened, I was surprised that the OS on the flash had updated itself to 6.10.0, as visible on the monitor screen and also in the UI once I got it to recognize a drive. I re-imaged it to 6.9.5 and tried it again, first with the Ethernet disconnected (no update) and then with it connected (it updated). Is this something new? I can see why there could be a desire to insure newly installed units have the most recent firmware. But booting with no drives is a troubleshooting tool we often recommend, and having the flash firmware updated in the middle of troubleshooting another problem is a recipe for disaster.
Do we need to start telling folks to pull the Ethernet cable before booting with no drives and then insert it after the NAS has had time to boot? When I did that, it didn't update the flash. Or is this something unique because I have a chassis that identifies itself as an RD5200? If it weren't for the warnings about going back to 6.9.x from 6.10.0 and the fact I'm not convinced 6.10.0 is really stable, I'd just try it on another NAS.
Do we need to start telling folks to pull the Ethernet cable before booting with no drives and then insert it after the NAS has had time to boot? .
@JohnCM_S : I agree with Sandshark that we need to understand when the NAS will update it's flash while diskless, and how to prevent that.
Can you provide some guidance on this? Otherwise we'll need to tell folks to pull the ethernet cables and reinsert them after - which is annoying to say the least. Also if the NAS doesn't have an LCD panel, it will be hard to know when it's safe to reinsert the cable.
The system needs a volume to perform a firmware update so a diskless system updating itself is not normal. Also, the system will notify you if there is an update available but not just upgrade.
The system needs a volume to perform a firmware update so a diskless system updating itself is not normal. Also, the system will notify you if there is an update available but not just upgrade.
I am not sure what caused his RD5200 to just update without any disks. I checked this with L3 and said that it is really not normal and they cannot really explain how that happened. They said that the RD5200 with an OS6 firmware is a hack and unsupported. They do not know if the hack allowed the system to "see" a volume and update the firmware without any drives installed.
It's definately not accessing any disk when it does this. But, there is a unused section of the USB that it might be doing something with. I cloned the 256M USB boot drive from a RN4200V2 to the 512MB one from the RD5200. But it still comes up not showing any drives when the problem occurs, which makes me think that's not it.
FYI, it did the same thing on an RN4200V2. I can only guess it's due to the flash drive being a USB device, and thus a "disk".
I was testing the bays, and one row didn't work -- had a loose cable. So, it booted as a diskless system. After I fixed it and re-booted, it updated the volume to 6.10.1, though I had installed 6.9.5.
