I put 4 of the Samsung drives in my desktop using 4 unused SATA ports from the motherboard (P7P55D-E LX) and just spanned them (over 7TB non-raid). At least they will not go to waste. I'll wait for the Hitachi drives to be delivered and try the raid route again.
Screw it - I just ordered 20 2TB Hatachi drives from PC-PitStop. Now - what to do with these crappy Samsung drives. Maybe put them on a 3Ware 9500S I have laying around doing nothing and use 4 of them in my desktop.
OBTW: - I also need the SAS RAID controller to present SFF-8088 connectors out the back. I could live with SFF-8087 internals and use an adapter bracket from pc-pitstop to get the SFF8087 internals to SFF-8088 externals. What a nightmare - I really wish Samsung woud get their feces in order.
This is where the F4EG patch came from: http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386&page=1&faqType=QI&faqKeyword
This is where the otherone came from: http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=387&page=1&faqType=QI&faqKeyword
Here's what I get when I do an MD5 on the files I used:
G:\install\Samsung HDD stuff\089312HD240UI_JP>md5 HD240UI_JP.EXE
EEE0492525D836392551021BB744CDCB HD240UI_JP.EXE
G:\install\Samsung HDD stuff\621878F4EG>md5 F4EG.EXE
AD1930D9FE53A6C8E20C3F57936452D1 F4EG.EXE
I'm using the Adaptec 3085 that has 2 external SFF8088 SAS connectors. I would consider switching to another controller if it would solve the problem, but it would have to expose 2 SFF 8088 ports. I'm having a lot of trouble trusting these drives with my data.
When I applied this upgrade (FAQ 37) - F4EG.exe the software reported that the version number was now 1AQ10003. I ain't making this s..t up. It's for real. It is really strange that some people are reporting that the version number stays at 1AQ10001. Strange.
No they were 1AQ10001 before the upgrade. When I applied one of the other upgrades (089312HD240UI_JP) it said that it was ugrading to 1AQ10001. That didn't work either, so I applied the F4EG upgrade which raised the version to 1AQ10003. That didn't fix the problem either. I'm wondering if a...