Ok so, I just got the NAS and installed the 2 x 2TB Samsung Eco Green F4s Did the whole initialising and disk checking, however, its come back to me with a SMART error..... Untitled by Penderyn, on Flickr - is it RMA time for me!?
spin up time? was the HDD having difficulty spinning up? try it on your desktop to see if same SMART error is reported. and RMA on the bases of SMART error.
You could check the drive compatibility list for your product (Sorry if you already did this?) http://www.synology.com/support/hd.php?lang=enu The Synology forums are quite good for stuff like this. Is this your drive? http://forum.synology.com/enu/viewtopic.php?f=26&t=27905 Looks like you have some reading to do, 26 pages of stuff! Hope you get it sorted. Chunks
Those hard drives are on the list but you have to upgrade synology firmware to 3.1. You will need to use different older hard drive when doing this.
There is also a fault with the original firmware on these hard drives, check which version you have - you may need to flash an update. http://forums.whirlpool.net.au/archive/1597038 Chunks
Its a 'known issue' with these drives apparently! Though unfortunately I did not know about it and upgraded to 3.1 only after installing the disks. Now one of my desks permanently generates a smart failure error, though apparently there is no risk of data loss. Annoying!
The Samsung issue shouldn't be generating a SMART error, it is a quite write error that will occur. At any rate, they fixed it in all drives shipping from about 11/2010 on. If the drive is newer than that, it has the fixed firmware on it. That said, both my drives were newer than 11/2010 and I updated the firmware just to be sure.
Yes, the drives have fixed firmware according to the serial number. However, from what I can tell from the thread above, if you run them in the NAS with v3.0 installed then they generate the SMART error because of delayed spin up, and once this occurs there is no way to remove the smart error and run the test again.
Yeah I read in to it a bit more. *opens mouth, inserts foot* Seems like the SMART error is because of v3.0 as you said. Seems kind of asinine to me that it'll cause a SMART error, but I don't put anything past technology these days.
