Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ST3000DM001

en.wikipedia.org

Post reply on HN
Print view View original

71–80 of 259 posts

Re: ST3000DM001

#71

Post by choeger »

Lammy wrote: post #61
3np wrote: post #55

Earlier quoted context omitted.

Or they managed to fill it with hardware without having to coordinate an intricate conspiracy involving supply chain and manufacturers across the globe.

> coordinate an intricate conspiracy Nobody is alleging that but you. Personally I don't think either "surveillance system needs a way to store what is collected" or "high-volume customers have economic leverage to demand confidentiality" are particularly intricate concepts.

The Snowden effect has worn off, it seems. Nowadays the NSA is back to being able to pull the most extreme stunts and everyone who thinks it is even remotely possible is called a crazy conspiracy theorist.

Re: ST3000DM001

#72

Post by Yizahi »

I had two of them, both failed over few years of super light use in a cooled case (with dedicated HDD fans). No Seagates for me after that.

Re: ST3000DM001

#73

Post by myrandomcomment »

vincnetas wrote: post #54
grp000 wrote: post #44

Earlier quoted context omitted.

I'm not familiar with data center tools or terminology. What is a tazer in this context?

Read same and could not believe that author is calling them selves "good customer" and meantime also intentionally failing hard drives with teaser. Some mental gymnastics there ;)

It is an amusing story from a completely different time and place in IT. Today people would just loudly and publicly complain on Twitter and other social media to embarrass the vendor into sorting it. Sharing a story, not speaking to the nature or the correctness of the solution. I have worked on both sides. Once when I was on the vendor side a very large customer returned a very expensive switch as RMA. A set of 16 ports stopped working. The cause in the end, the customer had gotten an SFP stuck and tried to rip it out, pulling the cage from its solder joints on the board. 3 switches in 2 months. We smiled, swapped all of them and then the sales team had a chat with the customer to help resolve the issue (their 3rd party SFP with a crappy designed latch). Is what it is.

Re: ST3000DM001

#74

Post by formerly_proven »

I still have one of these and it has always been loosing a little bit of data here and there for the last seven or eight years. Maybe even from day one and it just took me some time to notice. You can write a bunch of data to it, check it, and it will be fine, but after a few months there are probably a few hundred or thousand new unreadable sectors. Oddly consistent.

Re: ST3000DM001

#75

Post by Y_Y »

grp000 wrote: post #44
myrandomcomment wrote: post #24

Back in the mid 90s I was working in IT at a midsized company. We used Compaq desktops (this is the Pentium Pro timeframe). The HD in the system where quantum fireball (IIRC). They failed at an amazing rate all in the first 3 months (30%). We called Compaq at one point and said, look we want replacement drives for all of our remaining systems. After much back and forth (stupid on their part as we had 1000+ machines o…

I'm not familiar with data center tools or terminology. What is a tazer in this context?

Sibling comments have answered this correctly, but I like to imagine it was there as a threat to the Compaq visitors, like one might leave a loaded gun in a visible spot to facilitate negotiation.

Re: ST3000DM001

#77

Post by neilv »

Other infamous drives: Sun used the Quantum 105S for the main drive in SPARCstations, and that drive turned out to have a stiction problem (would stop spinning up). At a workstation ISV that was primarily Sun for its own workstations, on the rare occasion we had to power off large numbers of workstations, always at least one machine wouldn't come back. I vaguely recall slapping a drive, or dropping it and its caddy a short distance onto a desk, in the best tradition of "percussive maintenance".

I also personally bought at least one Quantum 105S, and then later "nobody every got fired for buying IBM" personally bought an IBM Deathstar drive. https://en.wikipedia.org/wiki/Deskstar#IBM_Deskstar_75GXP_fa...

Given my luck managing to find the worst lemon drives, for my subsequent home server, you can be sure that I intentionally used RAID mirroring of two different brands of drive. (Yes, it turned out that one make&model ran hot, while the other ran cool, and the hot one died.)

Re: ST3000DM001

#79

Post by Y_Y »

denton-scratch wrote: post #52
geocrasher wrote: post #8

Earlier quoted context omitted.

I worked at a small web hosting company back then, and we used a bunch of IBM Deathstar's. They certainly lived up to their name! I disassembled one just to see what went wrong, and I found the cause (of that drive's failure, at least). Here's a list of terms for reference: http://data-recovery-tips.co.uk/wp-content/uploads/2013/09/h... At some point, the bearing that serves as the pivot that the actuator arm and act…

Back in the day, my employer sold "disk cartridges", which were 24"diameter magnetic-coated aluminium disks in a plastic case. Head crashes were fairly common,, and made a horrible noise. We'd open the case of a crashed cartridge, extract the platter, and hang it on the wall; the crash would produce a rather spectacular sunburst pattern in the magnetic coating.

Cool! Does anyone have a picture of this?

I always thought hard disk platters looked especially cool compared to other storage media like floppies or CDs or flash stuff.

Re: ST3000DM001

#80

Post by lostlogin »

dstick wrote: post #66
theospears wrote: post #53

I was responsible for maintaining some large glusterfs clusters built on top of these drives, and they certainly added excitement to the experience. 1) At one point we were experiencing disk failures often enough that we wrote a cronjob to detect drive failures via smartctl and automatically send an email to our hosting company requesting them replace the drive. This saved engineering time, and more importantly reduc…

These things always happen in the weekend don't they? When I managed a large network of servers, it seems that all the outages happened during parties and/or the weekend.

Issues seem to happen as you implement the long desired upgrade/fix/repair too. Things hold on for years then crap out right at the final moment.
Post reply on HN