Samsung Spinpoint F4EG HD204UI 2TB compatibility?

[ginopilotino]

Yeah, but can diskstation see if a drive is patched or not? Wasn't the flash completely invisible?

Even the patcher can't detect a patched drive.

[jeprira]

I did mine today.

I used the HP USB tool to make a bootable USB, I put the file on the stick.

I booted an old PC where I had plugged both HD204UI I own. The patch did one after the other and put up messages about the non-samsung drives and a 1T Samsung I also have saying "not applicable".

Put the disks back in my 209+II and it booted cleanly. No issues, no changes that I can see, firmware number unaltered.

I must say I didn't notice any issues before...

btw: I'm on the new 3.1

[cread]

DSM final 3.1 throws up an unexpected warning at first boot, automatically disabling write cache. I did the (invisible) Samsung update a few months ago or whatever. Any ideas? Just ignore? Was able to enable write cache again.

Oh and btw, one drive is still reading as "abnormal". Is this simply an old remnant?

Could this be just a precaution? I'm sure DSM does not know the FW version. I wish there were detailed release notes between the versions (e.g. 1553 vs 1594).

If it reads "in the past" in the SMART data tab, then it is normal. It stores a worst case on the Drive. Since no matter how good it gets later, there will always be a time where it did not pass. I would be nice if DSM handled this a bit different (e.g. a current fault = abnormal or faulted, and old fault would be "in_the_past" and green in the status (unless there is something new))

[jim_h]

I just put DSM3.1 on my new 411+ with new 2 F4s from 2010 12. I did not manually patch it. Is there anything I should watch out for?

Not really. Mine worked without a hitch.
You might want to run the full SMART test on both drives.

I ran the 'extended test' on both drives and it took at least 7hrs for each one. Both came back as 'Normal'. It was a little anti-climatic. I was hoping for more information from this extended test besides just 'Normal'.

[wpwood3]

I just put DSM3.1 on my new 411+ with new 2 F4s from 2010 12. I did not manually patch it. Is there anything I should watch out for?

Not really. Mine worked without a hitch.
You might want to run the full SMART test on both drives.

I ran the 'extended test' on both drives and it took at least 7hrs for each one. Both came back as 'Normal'. It was a little anti-climatic. I was hoping for more information from this extended test besides just 'Normal'.

Click on SMART Info to get the full results of the test.

[jim_h]

Click on SMART Info to get the full results of the test.

Thanks. Same as before. I guess that's a good thing.

[hifreak]

So we can just enable the writing cache again with no problems?

[rooin]

Well other than reading the horror stories, and hoping that doesn't happen to me I have nothing but good luck to report with these drives.

I have 2x HD204UI's dated 2010.10 each running in basic non-raid mode and I've had no issues of any kind on my DS211. I knew nothing of the firmware issue till today when I updated to 3.1 and it warned me of the cache issue.
They were in my Antique DS207 for 3 months before I upgraded last month to the DS211. I run 2 websites, I do regular network streaming of both Audio & Video, and I use the Download station nearly daily. No problems ever.
Both drives have over a TB of data on them each as well. Hibernation has been enabled as well haven't experienced any spin-up problems either. (On either device) I see 75-80MB/s data transfers on the 211. Didn't get squat out of the old 207 though. 12MB or so average. (was reason I updated)

[Ghostlink]

Spinup "worse" is down to 42 on my 2nd HD204UI on DX510 with DS3.1
Are you sure the that DSM 3.1 got the spinup patch?

[Pokkara]

Today I have just purchased a Synology DS211J and two Samsung HD204U drives. Both serial numbers on the drives are in the form of xxxxxxB1xxxxx.
Synology official HD compatibility list mentions that HD204UI disks with serials xxxxxxxZ7xxxxx, xxxxxxxZ8xxxxx,xxxxxxxZ9xxxxx,xxxxxxxZAxxxxx, or xxxxxxxZBxxxxx must be patched with Samsung F4EG.exe.
So I assume my disks don't require patching. Still, I am a little confused by Samsung S/N logic, as I would expect something like xxxxxxxZCxxxxx or xxxxxxxZDxxxxx...
Can anybody help and confirm that HD204UI drives with xxxxxxB1xxxxx serial numbers are now working properly with DS211J? And that no patch from Samsung or Synology (for the DS211J) are required?

[fhall1]

I upgraded from 3.1 beta to 3.1 yesterday and spinup seems fine (so far anyway).

[zr0hero]

So we can just enable the writing cache again with no problems?

Thats what I just did. I bought my drives on Nov 10, 2010 so I'm thinking mine are not "flashed" - speaking of which if you browse the download files for this drive model on Samsung's website, you don't even see a firmware patch listed. Ridiculous.

I just upgraded to 3.1 today, and ever since the reboot, CPU usage gas been at 100% - any idea why this is? I hear lots of HD churning...I was having no issues at all until I flashed DSM today

Should I go ahead and yank the drives and flash em? The only firmware I could find was on this page -> http://www.samsung.com/global/business/ ... msg_id=386

Please advise..

[zr0hero]

test

[drasar]

Spinup "worse" is down to 42 on my 2nd HD204UI on DX510 with DS3.1
Are you sure the that DSM 3.1 got the spinup patch?

A have 45 on my both HD204UI drives (DS211j, DSM 3.0 1374 -- with the spin-up patch). I can sometimes hear "bzzz" noise and the drive spins-up only on the second attempt

[mark]

I think you have to look at Spin up raw data and not at "spin up worst". However, I also have
the feeling that it is not functioning 100 percent when "listening" to the noise the harddisks
make.