I got my original F4-210 on June 6th and out of the box it had a problem where it would run for 15 - 20 mins then reboot itself after beeping. Amazon replaced it and the replacement has been working fine until about a week ago where it did it again. I cycled the power and then it worked again until last night.
Today I cycled the power but it still won't stay up for long before resetting. There are no problems reported when logging in to the UI, all 4 drives report good and I was tailing /var/log/dmesg when it reset the last time and nothing was logged it just dropped the connection and reset.
So I backed up my config and did a reset (config not OS). After reboot the LAN led shows it is connected but the unit is unresponsive to http or ping requests.
The original beep/reboot problem seems like this problem someone else reported: viewtopic.php?f=9&t=1142
F4-210 frozen
-
TMS
Re: F4-210 frozen
Hi, what type of hard drive do you use? You can refer to this link to check if the hard drive is healthy? viewtopic.php?f=75&t=1125
Re: F4-210 frozen
4 x brand new 2 TB WD Blues. I doubt its a hard drive issue since I had the same problem with another unit before. The bigger problem at this time is that I can't even get the unit to boot since doing a config reset.
Re: F4-210 frozen
I have just found that the unit will boot and allow me to access the web ui when there are no drives installed. If I add a drive to any of the 4 bays I can hear the drive power up but it will not boot. One time it did boot with a single drive in the 4th bay, however, it would not boot again with the drive in a different bay or after I placed it back in the 4th bay. It did boot after I removed it again.
Unless you believe that all 4 of my drives went bad at the exact same time I suspect it is either a hardware or a software issue with the unit.
I also just realized I haven't mentioned I was on version 4.1.32 when this started and did the automatic upgrade to 4.2.07 yesterday. It seemed to be a much shorter time between start up and beeping/resetting after the update.
Unless you believe that all 4 of my drives went bad at the exact same time I suspect it is either a hardware or a software issue with the unit.
I also just realized I haven't mentioned I was on version 4.1.32 when this started and did the automatic upgrade to 4.2.07 yesterday. It seemed to be a much shorter time between start up and beeping/resetting after the update.