Bad Month for Laptop Disks

Instead of writing new articles, I recently spent a lot of time fighting laptop hard disks going bad.

The first was a Seagate ST1000LM14 (apparently originally a Samsung design), a hybrid 1TB 5,400rpm disk with 8GB flash. The disk was installed in a Lenovo Z50-75 laptop and started failing after only about 7 or 8 months. The interesting thing is that the disk didn’t have bad sectors but rather CRC errors on the SATA interface during transfers.

The disk was set up for dual booting with Windows and Linux, each using close to 500GB. Linux (Ubuntu 14.04) could somewhat deal with the transfer errors by reducing the SATA transfer speed and retrying very hard. Windows 8.1 on the other hand wouldn’t even boot, couldn’t repair itself, and entirely failed to produce any kind of useful diagnostic. Boo.

After attaching the disk to a USB adapter, I was able to move the recovery partition off of it without problems, used the recovery partition to reinstall Windows on a new disk, and then copied the nearly 500GB Linux partition again without any problem whatsoever.

I have no idea what happened to this disk. It appears like a problem with failing electronics rather than bad media. The drive was replaced by a newer model, a Seagate ST1000LM15. Time will tell if that was a good idea.

Bad Apple #2

Only about three weeks later, my MacBook Pro refused to boot after being turned off for about a week. OS X would start booting and then the laptop simply turned itself off without indicating why. Boo again. This is a 2012 MacBook Pro with Apple-shipped 750GB 7,200rpm disk. The disk appears to be a Hitachi/HGST Travelstar 7K750.

Further probing revealed that the main HFS+ partition was in an inconsistent state and the root filesystem could not be mounted, which is what caused the machine to turn itself off.

The recovery partition could still be booted without a hitch, and the filesystem could be mounted in read-only mode. I immediately proceeded to copy everything off to an external disk. Copying about 700GB of data hit two bad sectors in unimportant Firefox cache files but otherwise went smoothly.

All attempts to repair the filesystem utterly failed. It appears that Disk Utility/fsck was stymied by a dreaded “I/O error”. Rebuilding the catalog multiple times made most of the files in the main partition vanish but failed to bring the filesystem to a usable state, even when no I/O errors were occurring.

So I zapped the partition and copied back the previously saved files. This went smoothly and after copying the 700GB back, the system is booting again. The disk is scheduled to be replaced with a Travelstar 7K1000, the only 7,200rpm large laptop drive I could find.

Again I have no idea what really happened. The system was shut down cleanly but a week later refused to boot up even once. It looks like a bad sector possibly developed in some critical area of the filesystem and completely tripped up the HFS fsck. Erasing the partition and rewriting all data probably gave the disk a chance to relocate any bad sectors. The disk seems to be fairly healthy overall and it looks like really bad luck that it stopped booting.

If only SSDs never failed… but alas, that is not the case. And from what I gather, SSDs tend to fail hard, while neither of my bad disks actually resulted in a data loss.

This entry was posted in PC hardware. Bookmark the permalink.

7 Responses to Bad Month for Laptop Disks

  1. Raúl Gutiérrez says:

    Does the SMART information contain any interesting bit for these disks? I always wondered if it’s a useful feature before or after disk crashes.

    And, have you tried HDD Regenerator with your disks? It is a piece of software which I also wonder if it is a fraud or it really helps.

  2. Trowa Barton says:

    There are plenty of reports that state HDD Regenerator is a fraud, writes bogus data, etc.

    BUT, I’ve actually used it, and for things with a few bad sectors, they’ve booted correctly after, things with massive failures, the file system is at least in a good enough state to recover the user’s files, or at least more likely to succeed. I’ve had pretty good results on drives coming from both macs and pcs, things that wouldn’t even mount in their respective OSes in a USB dock will hang in there long enough to proceed with recovery scans.

    That said, it could still be writing junk to the file system, and it just doesn’t matter because the user data is all I’m after.

  3. ender says:

    I’ve had bad experience with Seagate’s desktop SSHDs – replaced it 3 times in 3 months, then finally replaced it with a regular SSD and HDD, which has worked far better.

  4. Michal Necasek says:

    Do you know what model(s) those were? At any rate, I’d rather use a single device, and unfortunately I need a lot of disk space but this laptop isn’t worth a 1TB SSD. So it’s tough 🙂 I suppose I could just go for a regular disk if the next SSHD fails again.

  5. ender says:

    Sorry, don’t remember – whatever model was current in December 2013 (this was on my work computer).

  6. rasz_pl says:

    >reports that state HDD Regenerator is a fraud

    HDD Regenerator forces HDD firmware to remap bad sectors (by hammering at the slow sectors), it does work as long as
    -firmware doesnt run out of spare space
    -there are no bad sectors in the service area rendering whole drive unusable

    Good for couple of bad sectors, but has huge potential for turning still working but failing drive into a brick. Sometimes its better to manually locate problematic region (mhdd latency scan) and exclude it with empty hidden partition. <- This is what "factory refurbished" often entails, but on a lower level. Remapping sector numbers so the bad area is almost invisible, you can still spot it in HDTune graph as a jaggies instead of smooth line, or gaps of different speed in the middle of a drive.

  7. Michal Necasek says:

    So it’s not a fraud… but one’s mileage will vary.

    I remember seeing those spikes in a HDTune graph. I immediately thought “hmm, remapped sectors”.

Leave a Reply

Your email address will not be published. Required fields are marked *