I have the Synology ds411slim NAS, no problems thus far.
I added a NEW WD Black 500GB drive (exactly the same as one that's already running in the NAS), and configured it, adding a volume on the new standalone drive (No RAID)... after disk checking (which takes hours), the NAS locks me out, and drops off the network.
I have to physically pull the power plug (it won't shut down when I press the power button) to restart it.
Upon restart it tells me the new volume on the new disk has crashed. I delete it.
I've repeated this several times, exact same behavior each time. I loaded the HDD to my desktop to look at it, and it had several small partitions on it (presumably from the multiple times I've added the volume), so I formatted it to nothing, tried again. Same behavior.
This is very annoying, and I can't figure out why the NAS is being uncooperative with loading this volume/HDD. I don't believe it has anything to do with the drive, since I am running the exact same drive in it already.
SMART reports the drive is fine. the NAS lists it as 'not initialized' when it goes in clean at first, 'initialized' once it's building the volume... and 'crashed' once I reboot it after it freezes out at the end of the disk check process.
This person is doing the EXACT SAME PROCEDURE AS ME, but his is working apparently (slightly different model NAS)
The HDDs I'm using have the same firmware, were manufactured according to the label, at the same time, and the NAS OS identifies their serials as the exact same (indeed, I'm beginning to wonder if that could produce a problem).
I've emailed Synology support; but apparently this isn't a very common issue - I can't find information on it anywhere.
I'm wondering if it's HDD related, but it's confusing since the drive is formattable and functions fine when I test it on my desktop. (I formatted it to NTFS, wrote/read some data, then reformatted it to blank, and tried it on the NAS again).
Actually no - after 2 weeks of technical support emails back and forth (and I eventually had to give them web access to the NAS so they could poke around in it), they gave up and gave me an RMA for a new one.
It wasted hours of my time, and I never figured out (nor did Synology conclude) what was wrong with the NAS, even after they analyzed the Kernel, and it was wiped several times, etc.
I still don't really know what the cause was - in either case they were unable to resolve it and were amenable to replacing it so I was unable to investigate it further...