NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Spinpoint F4 HD204UI 2TB 5400 RPM working good so far
There was a recent deal at NewEgg on the SAMSUNG Spinpoint F4 HD204UI 2TB 5400 RPM 32MB drives, so I decided to risk it as opposed to the other WD & Seagate 2tb drives. I installed them, upgraded the ReadyNAS firmware then did a factory reset. Disk 4 took most of an evening to resync, but finally finished. So far it's been running fine as I've been copying data off my old NV+ on to the new Ultra 4.
The Ultra 4 is sitting in the bottom of my gun safe, so low heat is rather important to me and I thought a 5400 would be a better bet. So far I haven't seen any Temp1 above 140f or so and the HD's are usually at or under 100f, never seen one above 108f. I was worrried that the enclosed fireproof safe would end up retaining too much heat, but it's been 3 days now with no problems. When I have the safe open the drives are very quiet, not surprisingly closed you can't hear a thing at all.
Will try and post later when I see how they hold up.
The Ultra 4 is sitting in the bottom of my gun safe, so low heat is rather important to me and I thought a 5400 would be a better bet. So far I haven't seen any Temp1 above 140f or so and the HD's are usually at or under 100f, never seen one above 108f. I was worrried that the enclosed fireproof safe would end up retaining too much heat, but it's been 3 days now with no problems. When I have the safe open the drives are very quiet, not surprisingly closed you can't hear a thing at all.
Will try and post later when I see how they hold up.
160 Replies
Replies have been turned off for this discussion
- I didn't understand any of the ' airs' 'bug' post. Could someone translate it into laymans, i'm tired just got in from work.
Also where does the bug pop up? Does whatever nas one is using throw this up in a warning message?
mutley - I didn't understand his post as well until I went to the website he posted. I don't know what effect this would have on our ReadyNAS though.
http://sourceforge.net/apps/trac/smartm ... GBadBlocks
The issue is described as:
* Problem: If the system writes to this disk and smartctl -a (5.40) is used at the same time, write errors are reported and bad blocks appear on the disk.
and here is a little more info on it:
This was reported by a reader and could be reproduced in c't magazine lab on the following system:
Windows 7 x64 Ultimate
Core i3-560
Intel H55 chipset
SATA-AHCI-Driver: Intel Rapid Storage Technology (RST) 9.6
* It could also be reproduced under Linux (Fedora 14) if AHCI is enabled and the following commands are run in parallel:
# badblocks -svw -b 4096 /dev/sdd 4000000
# smartctl -a /dev/sdd
* It could not be reproduced if the Intel H55 chipset is set to IDE mode.
* It could also be reproduced on another system with an AMD chipset under Windows and drivers msahci.sys or amdsata.sys.
* It could not be reproduced on the same AMD system and amdsata.sys driver with the following other disks: - mattseattle
Ok, cheers for some more clarification there. Judging by your post, yeah I'm not sure of the ramifications on the Duo. I guess we'll have to wait and see.
Anyone else got any info?
mutley - The Soundforge report said the error occurs under Linux in ACHI mode. Anyone know if the ReadyNAS systems are configured for ACHI or IDE mode? I did a search, but nothing relevant popped up. If it's IDE mode, we should be okay.
- Has anyone actually had this happen on their ReadyNAS with these drives? I've been using 4 of these drives on my ReadyNAS Pro for several weeks now.
- It would be hard to tell if it happened or not - you'd need to MD5 check all the files on the NAS against known good ones.
- Airs but according to the report it mentions this - write errors are reported and bad blocks appear on the disk.
That would show up in the SMART display and/or Volume scan. - Matt, the page I linked does mention this:
The above suggests that the disk sometimes discards a pending 64 sector write command when a IDENTIFY DEVICE command is received. This data loss occurs silently. There is no error message in kernel log, SMART Error log, NCQ Command Error log page, or SATA Phy Event Counters log page.
Please note that the badblocks command reported "256 bad blocks" in the above test because the data read differs from the data written before. None of the tests resulted in actual bad (unreadable) blocks on the disk. Testing did not damage the disk itself. The problem is that new data already sent to the disk may not be written. Previously written data is not affected.
Btw, I'm in Seattle too, hi! :) - Airs...
How did you disable write caching?
I lived in Seattle for 10 years but moved to New Orleans 3 years ago.
-Matt - You can find it in Frontview under System -> Performance
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
