![]() However, I created a shared folder for storing data and mapped it on a Windows 8.1 VM in the QNAP TS-451 NAS (that is currently under evaluation). The Cloud Station and related packages were uninstalled as they simply refused to let the disks go to sleep. After prolonged usage, it was re-purposed slightly. In my original DS414j review, I had indicated its suitability as a backup NAS. However, the drives that were used for long term testing were never hot-swapped. The unit doesn't support hot-swap, but we tested it out and found that it worked. However, in the interest of full disclosure, I have to note that the unit had been used againt Synology's directions with reference to hot-swapping during the review process. The NAS, as per its intended usage scenario, had been only very lightly loaded in terms of network and disk traffic. This time around, the web UI was accessible, but I was presented with the dreaded message that there were no hard drives in the unit. Left with no other option, I powered down the unit with a long press of the front panel power button and restarted it. All four HDD lights were blinking furiously and the status light was glowing orange. I woke up last Saturday morning to incessant beeping from the recently commissioned Synology DS414j. On two occasions (once with a Seagate Barracuda 1 TB drive in a Netgear NV+ v2 and another time with a Samsung Spinpoint 1 TB drive in a QNAP TS-659 Pro II), the NAS UI complained about increasing reallocated sector counts on the drive and I promptly backed up the data and reinitialized the units with new drives. Even though I perform RAID rebuild as part of every NAS evaluation, I have never had the necessity to do one in the course of regular usage. ![]() After 4+ years of running multiple NAS units 24x7, I finally ended up in a situation that brought my data availability to a complete halt.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |