Samsung Spinpoint F4EG HD204UI 2TB compatibility?

[tipsen]

Can anybody tell if the following is good or bad (and preferably also why):

NAS> fdisk -lu

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sda2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sda3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdb2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdb3 9437184 3907024064 1948793440+ fd Linux raid autodetect

/Tommy

[maxxfi]

Device Boot Start End Blocks Id System
/dev/sda1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sda2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sda3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdb2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdb3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Those '256' are a good sign that the drive is formatted with 4k-blocks.
IIRC it would be 63 with the older 512 bytes blocks.

[Vic Vega]

I get identical fdisk -lu results as tipsen in my setup.

Speed test with Xbench 1.3 on Mac connected via AFP in gigabit network (Dlink DIR-655)
Read 95 MB/s
Write 67 MB/s

Does this say that throughput does not suffer from the 4kb issue in this setup?

[lenh]

I'm also interested in these new 2Tb drives. Tipsen, can you confirm that they're OK with the 207+ ?

[tipsen]

I'm also interested in these new 2Tb drives. Tipsen, can you confirm that they're OK with the 207+ ?

Yes, they're still working fine with my setup - no problems whatsoever!

[tbar2112]

I am considering this for the DS410. Does anybody have experience with this setup?

It would now be great if Synology could record this drive into the compatibility list, this topic has lived for a month now

[Vic Vega]

My setup works fine as well. No problems.

[Klojum]

It would be nice if we got the final confirmation from Synology by now on these latest 2TB drives. I'm anxious to use them in a DS-209+. Reading here in this forum that they work in other Synology products is a positive start, and it -almost- gives me the go-ahead to purchase a 4TB-set of them, but... I'd like to know for sure.

Come'on, Synology. Tell us your verdict!

[tbar2112]

It would be nice if we got the final confirmation from Synology by now on these latest 2TB drives. I'm anxious to use them in a DS-209+. Reading here in this forum that they work in other Synology products is a positive start, and it -almost- gives me the go-ahead to purchase a 4TB-set of them, but... I'd like to know for sure.

Come'on, Synology. Tell us your verdict!

I decided to go for it without the whitelisting on Synology's part; I ordered 3 of these + the DS410 yesterday. I'll keep you posted! However, it's often the test of time that is the most inportant one...

[tarmsaft]

So, what you guys are telling me is that I can migrate my 5xSamsung HD103UJ (1TB) drives in Raid 5 on a DS509+ to the new HD204UI drives without any complications? Sweet.

I guess I need to replace one drive at a time, wait for it to sync before I do the next and then do an expand when all drives are switched.. I wonder how long that will take? Since I've used up all 4TB.

I got myself a serious problem when migrating.
Major inode/block size failure. The first volume crash appeared after the 4th (out of 5) disk had reached 100% in synchronization.

I do not know if it was due to the disks, the migration itself and/or something else but you can read about it at the end of this thread:
viewtopic.php?f=7&t=18410

[TDIP]

Another vote for the HD204UI drives. I've been running them in my DS1010+ (5.3TB RAID 6, 3.0-1337) for a couple weeks without issue. I'll note that the HD204UI hibernates fine (noted because the Synology drive list at http://www.synology.com/support/hd.php?lang=enu shows two prior Samsung models as "not recommended" because they failed to hibernate).

[Ghostlink]

Hi
I just got a DS1010+ with 5 204UI, running on Raid 6.
This is my first NAS and I'm a newbie so I dont know if I set up everything right.
Im on WinXP and I mounted the drive as a normal network storage.
Seems to be problems with the reed speed.
Can anyone help me look at these numbers and tell me what to do with settings or such?



Server> fdisk -lu

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sda2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sda3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdb2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdb3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdc2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdc3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Disk /dev/sdd: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sdd1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sdd2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sdd3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Disk /dev/sde: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sde1 256 4980735 2490240 fd Linux raid autodetect
Partition 1 does not end on cylinder boundary
/dev/sde2 4980736 9175039 2097152 fd Linux raid autodetect
Partition 2 does not end on cylinder boundary
/dev/sde3 9437184 3907024064 1948793440+ fd Linux raid autodetect

Disk /dev/synoboot: 128 MB, 128450560 bytes
255 heads, 63 sectors/track, 15 cylinders, total 250880 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/synoboot1 * 63 32129 16033+ 83 Linux
/dev/synoboot2 32130 224909 96390 83 Linux

[Klojum]

I decided to go for it without the whitelisting on Synology's part; I ordered 3 of these + the DS410 yesterday. I'll keep you posted! However, it's often the test of time that is the most inportant one...

I couldn't wait any longer as well, hehe. And the price was right, i thought: € 87,50 per drive.

Now using two 2TB Samsung HD204UI drives in a 209+ running in RAID-0, with 3,56TB available after format.
Finally just received the go-ahead after a lengthy full disk check of (2x8) 16 hours in total...

But... it's being filled with large files at this very moment, 45MB/s average using FTP.
All looks fine, sofar. Drive temps are 29 & 33°Celsius

[UPDATE]
Transfer speeds now up to 47-48MB on average, and occaisionally towards 90MB/s.
Drive temps are currently 31 & 35°Celsius during continues writes. I guess RAID-0 has reached its operating temperature.

[compet_pl]

There is a beginning of the REAL PROBLEM for Synology and 2TB Samsung HDD users on the European market right now.
The older HD203WI (it's at Synology list as compatible) is starting to be not available now. I think it's just the rest of the Samsung stock.

The only Samsung 2TB drive available is HD204UI right now.
So, If any Synology user wants to add or change any Samsung 2TB disk, he has no compatible (means tested by Synology) disk to buy.

So... Synology! Pls be hurry with your test!

[nikoazn]

I'm currently using two HD204UI drives on my 210j box for 100+ hours now. Everything works perfectly so far!.
Hibernation works. No issues with smart-info(low lcc count, no raw data error, no sector reallocation etc.).
Tested with UPS power supply, simulated power outage scenario, my 210j box went into safe mode and rebooted automatically after power has been restored. Temp reading on both hdd runs cooler than HD203WI, 43'C max/40'C avg. under high load.

Best 2tb HDD so far in the market.


Niko