Final Word on the Samsung HD204UI


KYThrill

Recommended Posts

well, it seems I have another option...

 

use the Samsungs in one of my NV+... seems infrant is up to date on their file systems... at least with their latest firmware release...

 

 

um... why is a hardware device (NV+) more up to date than a software device (unRAID)??? shouldn't it be the other way around?

although, I guess, just going by the date of the 5.0 beta posting, it may be that limetech is following the Duke Nukem Forever release schedule? hopefully that works out better for Limetect than it did for 3drealms ;) btw, slightly off topic... anyone know when DNF will be released... I was a huge fan of DN3 back in the day....

 

Unraid starts the partitions at 63 which is not aligned with the 4k sector drives.  There is work that needs to be done so that sector 63 can still be used in unraid but when new 4k discs are put in they are formatted and the partition starts at 64.  There is a lot of hoop jumping and checking that needs to be done for this to be implemented and not require the user to change a lot of stuff.

Link to comment
  • Replies 121
  • Created
  • Last Reply

Top Posters In This Topic

There is a lot of hoop jumping and checking that needs to be done for this to be implemented and not require the user to change a lot of stuff.

thats ok, I am starting fresh... so as long as it gets done now, it wont really effect me :)

 

 

Fair enough, but Lime-Tech has to make it work for everyone.  There has not been a lot of communication from Lime-Tech lately.

 

This change will hopefully make it into 5.0 (as we are seeing more and more drives with the 4K sector setup) but I am not sure if it will make it into a 4.5.x release.  My gut says it probably will but will probably be the last change to the 4.5.x series.  Every change after that will only be done to the 5.x releases.

Link to comment

FWIW, an F4 can work "well enough" depending on how you use the drive.  I didn't think to check the forum until after I'd picked mine up and decided to give it a shot anyway.  As long as the access is sequential, I don't see a performance hit.  And everything I do on most of my unRAID drives involves one-time writes of huge files and occasional reads.  (Storing and playing back HD video.)  I get 32-34megs/sec when writing large files to the drive which is the same I get with similar writes to any other drive.  If I try to read while writing, it bogs down but I can live with it.  Once I'm done filling up the drive, I won't be writing to it again.  I haven't run a parity check yet but I'm not too concerned with the speed of parity checks as long as it still finishes overnight.

 

So whether it will be adequate depends on how you use it.  I'm disappointed in this trend, tho.  unRAID will need to start detecting and handling these drives in software soon if everyone starts designing their new drives this way.  The F3 was my favorite 2tb drive because it just plain worked and didn't have any issues.  I'm tempted to track down some F3s and buy them while I can.  :)

Link to comment

Fair enough, but Lime-Tech has to make it work for everyone.  There has not been a lot of communication from Lime-Tech lately.

 

This change will hopefully make it into 5.0 (as we are seeing more and more drives with the 4K sector setup) but I am not sure if it will make it into a 4.5.x release.  My gut says it probably will but will probably be the last change to the 4.5.x series.  Every change after that will only be done to the 5.x releases.

 

It will need to be there sooner rather than later if the 1 January deadline comes to fruition. Its been decreed that all drive manufactured post 1 January should use the 4k cluster size. Its already hard enough as it is to get drives with the 512b cluster size.

Link to comment

As I understand it, the 'extra space' is invisible to the user.  Basically, advanced format drives are able to cram more data into the same physical platter surface area (4x as much, if I understand it correctly).

 

More or less correct.  I don't think the gain is 4x ... maybe closer to 4%.  Perhaps the 'wasted' space is reduced by 4x.

 

The gains come about because the overheads (sector gaps, sector headers, parity bits etc) are reduced. Changing sector size from 512B to 4kB means that there are 8x less sectors.  However, the improvement is not 8x because the sector headers have to be bigger.

Link to comment
  • 3 weeks later...

Yep I've just bought one of these in complete ignorance thinking it would work fine as long as it wasn't one of the 4k sector drives.  So what's the score exactly?  I understand the alignment issues, but is it a definite no-go or will it work?  I need to use this as my parity drive since it's larger than the other drives in the array.  Will there be some sort of patch to make these drives operate optimally? - updates can be kinda slow around here so I wondering if I should just send it bake for a refund now that I have the chance.  On the otherhand I do need the space now...

 

Thoughts and suggestions?

 

Matt.

Link to comment

So what's the score exactly?  I understand the alignment issues, but is it a definite no-go or will it work?  I need to use this as my parity drive since it's larger than the other drives in the array.  Will there be some sort of patch to make these drives operate optimally? - updates can be kinda slow around here so I wondering if I should just send it bake for a refund now that I have the chance.  On the otherhand I do need the space now...

 

Thoughts and suggestions?

 

From what others have reported it will be very slow as a parity drive and degrade the performance of your entire array. On top of the slow performance issues, it also reports temps that are impossible to achieve (below room temp). I would not and will not trust this Samsung drive. It would be best if you return it now.

 

There is no known or estimated arrival date of changes required in unRAID to make good use of the drive.

Link to comment

Although I would not buy an F4 drive for use in an unraid array right now, if I had one, I may consider using it. How much would it cost to return it? What kind of a deal did you get on it? Can you wait for a deal on something else? If you decide to keep it, I would not use it as a parity drive. I would only use it as a media drive, install it in your array, fill it up, and leave it alone. In that scenario it would be fine. I have three F3 drives and the temperatures they report are in line with the others in the array. I don't see that as reason alone to reject a drive. Reliability, low power and ease of warranty replacement are what I seek.

Link to comment

FYI I am now using 2 of those in my array since 3 weeks, not as parity though. Good performance, low temp and stability as far as I can tell, but of course we'll have to see if they stand the test of time.

Really not sure though where the issues were coming from for others, as those drives seem to offer perfect 512 sector compatibility.

Link to comment

FYI I am now using 2 of those in my array since 3 weeks, not as parity though. Good performance, low temp and stability as far as I can tell, but of course we'll have to see if they stand the test of time.

Really not sure though where the issues were coming from for others, as those drives seem to offer perfect 512 sector compatibility.

interesting - can you tell us anything about the performance? is is on par with your other disks?

Link to comment

Well that the thing - I didn't notice any difference with other recent disks, and they are much better than the old slow 300GB and 500GB they replaced - but that's not performance per se!

What's the best way to really test? Parity check speed for example didn't change vs when I had the old disks, which I think is good because it should mean they perform as good as the 2*203WI that were the only 2TB I had so far.

Link to comment

Well that the thing - I didn't notice any difference with other recent disks, and they are much better than the old slow 300GB and 500GB they replaced - but that's not performance per se!

What's the best way to really test? Parity check speed for example didn't change vs when I had the old disks, which I think is good because it should mean they perform as good as the 2*203WI that were the only 2TB I had so far.

 

If you added 2 new disks that should by all rights perform better than the disks they replaced, but you are getting the SAME parity check speeds then something may be not quite right.

 

If you have unmenu installed try the Disk Management and Disk Performance links in the upper left corner.

Link to comment

low temp and stability as far as I can tell, but of course we'll have to see if they stand the test of time.

 

You can not trust the temps that they report. At best you need to add an adjustment offset to what they do report, likely 5C - 10C. It has been confirmed that they report temps that are impossible to achieve (below room temps).

 

Also, if you replaced antiquated disks with brand new disks, your performance should have increased. If you're seeing the same performance, then something is wrong with the drives or the system or your observations. As prostuff1 said, you should try unMenu's Disk Management and Disk Performance links.

Link to comment

As prostuff1 said, you should try unMenu's Disk Management and Disk Performance links.

They too might report inconsistent results... (Disk Performance link in unMENU is based on what bwm-ng reports.  bwm-ng NEVER reports the same rate as unRAID's management console when doing a parity check.)

 

Remember, parity check speed is determined on the SLOWEST disk involved through the SLOWEST interface involved.  A brand new "fast" disk will do nothing to change the effective parity speed if it was not replacing the disk that was the slowest.

Link to comment

As prostuff1 said, you should try unMenu's Disk Management and Disk Performance links.

They too might report inconsistent results... (Disk Performance link in unMENU is based on what bwm-ng reports.  bwm-ng NEVER reports the same rate as unRAID's management console when doing a parity check.)

 

Remember, parity check speed is determined on the SLOWEST disk involved through the SLOWEST interface involved.  A brand new "fast" disk will do nothing to change the effective parity speed if it was not replacing the disk that was the slowest.

Exactly - I had only 1 disk going until 2TB, now I have 3 - 1 203, 2 204 - and speed is the same. My conclusion is that 204 is as fast as 203 on parity check...

 

As for the Disk Performance, well, it's an instant measure and depends on a lot of parameters, I'd rather use a Linux level test... Is there any?

Link to comment
  • 2 weeks later...

They are as safe as any HD can be. The main reason they are not recommended is due to their below average write speeds using unRaid. Their read speeds are generally not the issue.

 

In my experience, if you use another 2 TB as your parity (I use an f3) and a good cache drive (I use a 502hj) you will not even be able to tell a difference between an ears and a f4.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.