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 bit the bullet last night and upgraded the firmware on all my drives. The most painful part was creating a bootable thumb drive. After that it was easy. I am super annoyed that Samsung did not update the firmware number for this major bug fix.
- Good guide soulseeker
Someone needed to do a guide like that for the team. I know info come from airs, but between the two, good stuff.
We can't always be frontier runners, someone has to do it.
I'll give this a go the weekend.
In fact I've just stuck it on a stickie on desktop. - ok, I finally did it (although I slept well last night but I could't stop thinking about it ;))
1. looked for an old usb-stick
2. used http://www.lowfps.com/creating-a-bootab ... humb-drive
3. copied the samsung file also on the stick - renamed it to patch.exe
4. shut down the nas
5. plugged the 1. drive on a sata-port, changed bios boot settings to usb, booted from stick
6. typed patch.exe, it found the disc automatically and patched it within seconds
7. did it again with the second disc
8. back in the nas - booting and waiting for my networkshare to come up
9. they appeared - now I'm listening to anathema (from my nice 2X2tb-share) and wonder if any files are damaged (I don't think so) but still feel annoyed about the waste of lifetime. at least it worked.
10. I also asked netgear-support if they could tell me if the box runs in ide or ahci - they haven't got any idea but on monday a 2. level support may tell me - deleted...airs beat me to it.
- Do we have any conclusion yet?
Do we need to update the patch definitely (if one has access to dos)?
What's the thinking so far?
I'm with you soulseeker on this waste of time. It's cost me a small fortune in dollars and time so far just to update my drives with latest radiator. But the other option was WD and again more bugging with LCC's.
mutley - The HD204UI was on the HCL for the Synology product line. At least till this bug cropped up then they removed it.
I'm doing a few more tests as I just had a file come up as NOT IDENTICAL so before I say for sure I'm going to do a few more tests.
Update:
I repeated the test 15 times with 2 different video files and some jpg's. Out of all the tests I had one MD5 test come back as NOT IDENTICAL. I can't replicate it so not sure what the cause was. - thanks mattseattlle
by the way - I really love my nas (and my data) but the waste of lifetime for bughunting really pisses me off :((. But it's my own fault, no hcl, no safety ... on the other hand no risk, no fun ;). airs wrote: Not sure if you'll be able to detect a file error that way. An MD5 comparison will tell you for sure though!
I downloaded the MD5 app for the Mac OS this morning. I just ran several tests of copying video and music files back and forth. While the copying was happening I loaded the SMART data for 4 of the Samsung drives happening. On other tests I did a combination of that as well as loading the iphone app that queries the SMART data as well. After doing an MD5 comparison it showed that all the files were identical in checksums.- Cheers airs
mutley Mutley wrote: Another question regarding patch procedure Once the computer booted, it dropped me at a C:\> command prompt and I just executed the Samsung exe.
If I'm attaching disk via dock/caddy to laptop with XP, would it still be 'C:\' or be whatever xp gives hard drive i.e. "J:\" and then "filename.exe"? So I'd have to change prefix from "C:\" to "J:\"?
Or it don't matter, patch will find it's way to Samsung hard drive?
mutley
It'll find the drive, just make sure its the only SATA/IDE device connected to be safe. As for C versus J, it should drop you to C.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
