How many Samsung Hard drives have failed on you?
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
How many Samsung Hard drives have failed on you?
This poll is an attempt to calculate the SPCR statistical failure rate of Samsung. Rather than do a lot of hearsay and speculation, let's get some solid numbers generated so we can determine what the failure rate of SPCR's sampling size. Please also vote in the How Many Samsung Hard Drives have you owned poll?
thought these two threads could be interesting here:)
here about 5% of the disks reported had failed...
http://forums.silentpcreview.com/viewto ... highlight=
Here there are number of reported dead drives is larger, but the poll is not linked to any counting of drives.
http://forums.silentpcreview.com/viewto ... ght=#72831
here about 5% of the disks reported had failed...
http://forums.silentpcreview.com/viewto ... highlight=
Here there are number of reported dead drives is larger, but the poll is not linked to any counting of drives.
http://forums.silentpcreview.com/viewto ... ght=#72831
-
- *Lifetime Patron*
- Posts: 541
- Joined: Sun Jan 04, 2004 11:35 am
- Location: Chicago, Ill., USA
- Contact:
Same here, I'm abstaining from voting because I only got mine within the last month. It's had no problems, but it's barely been used.Jordan wrote:I have had 2 running perfectly fine but I've only had them about 6 months.
It might be more useful to also indicate how long the drive(s) has (have) been in use (regardless of failure).
<shrug>
Matt
The problem with measuring how much time it took to achieve failure is that it's difficult to get anything meaningful from that. Ultimately, all drives will fail, which is the basic principle behind RAID (Redundant Array of Independent Disks). Drives are more likely fail when pushed to temperature limits. Frequent spinning up and spinning down may increase the likelyhood of failure. Even the conditions in which they were stored prior to purchase can alter their failure rate.
Since this is a simple survey and not a research experiment, I'm not too worried about the time it took to fail. All I want is a number that is semi-meaningful, even if it's not statistically significant.
Right now at the time of this post (1:45AM EST), I've counted 2 drive failures out of a total of 27 drives owned. That's a failure rate of 7.4%. That's a bit high, but I suspect that the numbers may drop as more people vote, since it's still not statistically significant (If it was 28 drives owned, that failure rate would drop to 7.1%).
Since this is a simple survey and not a research experiment, I'm not too worried about the time it took to fail. All I want is a number that is semi-meaningful, even if it's not statistically significant.
Right now at the time of this post (1:45AM EST), I've counted 2 drive failures out of a total of 27 drives owned. That's a failure rate of 7.4%. That's a bit high, but I suspect that the numbers may drop as more people vote, since it's still not statistically significant (If it was 28 drives owned, that failure rate would drop to 7.1%).
I completely forgot, don't ask me how, but through my website (controlpc.co.uk) I have built over 10 PC's with Samsung drives. I Always use Samsung drives because they are quiet, pretty fast and run fairly cool (which esp helps in SFF PCs I build).
Out of all the drives and my own two I can't report a single failure or even hitch so far.
Out of all the drives and my own two I can't report a single failure or even hitch so far.
The only flaw with this poll is for folks who have had more than one Samsung drive. If I've owned 5 and had zero failures, I get one vote for "none". If I've had 5 drives and 1 failed, then I would mark "1", which makes it look like for my one vote, I had 100% failure, but really it was a 20% failure rate (1 out of 5).
But if you vote in the companion poll here (also link in the initial post above), then it's taken care of. This poll is how many have failed, the other is how many have you owned. People need to vote in both polls to give this any meaning whatsoever.AZBrandon wrote:The only flaw with this poll is for folks who have had more than one Samsung drive. If I've owned 5 and had zero failures, I get one vote for "none". If I've had 5 drives and 1 failed, then I would mark "1", which makes it look like for my one vote, I had 100% failure, but really it was a 20% failure rate (1 out of 5).
Dave
d-temp smart report:
Yay 202GB Samsungs!
Still I liked it and I'm going to go get it replaced with another one as soon as I've tried backing up as much as I can be bothered with.
Had it since late August. And it's the first drive that has crasched for me in ages. (last one was a bigfoot or seagate 1080MB...)
Been lucky I guess and not at all like the numerous RMA's my friends have done on any number of Maxtors, WDs and IBMs.
Code: Select all
-------------------------[Device information]-------------------------
Physical drive: 2
Compatiblity: ATA/ATAPI-7 minor version 001Eh
Model: SA]SUNW SP0802^ 0 0 0 0 0 0 0 0 0 0 0 0
Firmware revision: TU100-23
Serial number: 0653Z1VW706410
Disk capacity: 202.56 Gb (424803472 sectors)
Buffer size: 2048 Kb
Identify information CRC: FAILED
Still I liked it and I'm going to go get it replaced with another one as soon as I've tried backing up as much as I can be bothered with.
Had it since late August. And it's the first drive that has crasched for me in ages. (last one was a bigfoot or seagate 1080MB...)
Been lucky I guess and not at all like the numerous RMA's my friends have done on any number of Maxtors, WDs and IBMs.
Yes on every second or third boot or so.
And even if it boots ok it usually goes "corrupt" during the day. I was was also pondering if it might be the cables and was going to try with a new pair before I rma'd it as I was going by the shop for a cd-r pack anyway to do backup.
And after this tip I'll most surely try it Thanks.
I'll guess I'll do another post later to let you know how it turns out.
Is there any other things I should try if the cables turn out ok btw?
I guess i can try and put up another computer to check so it isn't the promise controller on the mb breaking down but I dont have another mb with uata support unfortunatly.
And even if it boots ok it usually goes "corrupt" during the day. I was was also pondering if it might be the cables and was going to try with a new pair before I rma'd it as I was going by the shop for a cd-r pack anyway to do backup.
And after this tip I'll most surely try it Thanks.
I'll guess I'll do another post later to let you know how it turns out.
Is there any other things I should try if the cables turn out ok btw?
I guess i can try and put up another computer to check so it isn't the promise controller on the mb breaking down but I dont have another mb with uata support unfortunatly.
By any chance You are using rounded cables?luggage wrote:Yes on every second or third boot or so.
And even if it boots ok it usually goes "corrupt" during the day. I was was also pondering if it might be the cables...
Well, You could download Samsung's or Hitachi's Feature Tool, and set the ATA speed down to ATA100 (UDMA-5). ATA133 is really stretching the spec.luggage wrote:Is there any other things I should try if the cables turn out ok btw?
Also, good thing to remember is that the master (only) device should be attached to the end connector. I once had some issues when using rounded cables, ATA133, mobile rack and the middle connector of the cable. I got some write errors, but changing the rack to the end connector solved them.
Please do report back if the new cable helps anything.
Cheers,
Jan
No I do the origami thingJan Kivar wrote:By any chance You are using rounded cables?
It seems to have helped. That is it works now - so far (remove 1 from the poll )Jan Kivar wrote:Well, You could download Samsung's or Hitachi's Feature Tool, and set the ATA speed down to ATA100 (UDMA-5). ATA133 is really stretching the spec.luggage wrote:Is there any other things I should try if the cables turn out ok btw?
Also, good thing to remember is that the master (only) device should be attached to the end connector. I once had some issues when using rounded cables, ATA133, mobile rack and the middle connector of the cable. I got some write errors, but changing the rack to the end connector solved them.
Please do report back if the new cable helps anything.
Cheers,
Jan
I suspect that what might have happened is that I slightly dislodged the caple from the plextor cdr-writer that sits on the same cable while cleaning heatsinks. And with vibrations and that I got some funky signals. Anyway the new cable gave a much "firmer" connection so I hope that wont happen again. (I did check the connection to the samsung earlier... but not as carefully the connection to the plextor )
The samsung (and cudaIV) is running UDMA-5 since the Promise100 can't handle more.
Having it on the Promise controller also makes it "invisble" to the Hutil unfortunatly. (lists as a scsi-controller for windows... )
I'll try the Hitachi Feature Tool and see if it can find my drives.
Don't feel like moving it over to the nomal IDE channels just to set the AAM as I cant hear it over my fans anyway.
That'll have to wait untill I migrate it over to a new quiter system in the future sometime.
Btw the store I bought it in and that got me the new cable today said they had had very little trouble with the Spinpoints they sold. Only four being returned from customers, and all of them found to be ok so they had not RMA'd anyone to samsung yet. (I dont know how many they had sold tho but they use the Spinpoints as default in the computers they sell and the shop is surviving so... )
[edit]the Hitachi Feature Tool managed to find all three of them Great!
I'd like to officially change my vote from zero to one. Tonight, one half of my RAID-1 array has died.
This would bump the failure rate back up to 4.9%, which is still damn good in my opinion. Except that Luggage voted a failure when that didn't happen. So I think we're still legitimately at 3.9%
Anyone else out there that hasn't voted yet?
This would bump the failure rate back up to 4.9%, which is still damn good in my opinion. Except that Luggage voted a failure when that didn't happen. So I think we're still legitimately at 3.9%
Anyone else out there that hasn't voted yet?
-
- Moderator
- Posts: 7681
- Joined: Mon Dec 09, 2002 7:11 pm
- Location: Maynard, MA, Eaarth
- Contact:
poll amendment
Hello:
I have used at least 10 Samsungs (mostly SATA's) and up until yesterday, none had given any trouble. Now, it seems that one (of a RAID 1 pair) has failed in a client's computer, though I'll confirm it tomorrow -- it may just have lost power or the data cable my have slipped out...
So, maybe my vote of "None" will get changed to "one"...
I have used at least 10 Samsungs (mostly SATA's) and up until yesterday, none had given any trouble. Now, it seems that one (of a RAID 1 pair) has failed in a client's computer, though I'll confirm it tomorrow -- it may just have lost power or the data cable my have slipped out...
So, maybe my vote of "None" will get changed to "one"...
I agree, I'm kinda shocked everyone else considers a 5% failure rate good. I think I've only had two HD's go on me in about 15 yrs -- that's probably a couple hundred drives -- MFM, RLL, SCSI and all the flavors of IDE...Viperoni wrote:In general, I rarely see HD's rarely go bad. Out of 100 computers, I honestly doubt 5 develop bad HD's within 6 months.
Dave