42
Lost partition table, can i trust the HDD again? (discuss.tchncs.de)
submitted 3 months ago by to c/linuxquestions@lemmy.zip
19 comments fedilink hide all child comments
 

Probably due to a power outage, I suddenly lost access to a connected USB HDD yesterday. According to parted, I get the message “unknown partition table,” and gdisk says the GPT is corrupted. Using testdisk, I was able to copy the files to another drive and restore the partition table and mount the HDD.

Is it possible that the partition table was damaged by the power outage, or does this point to a different problem? Can I safely store data on such an HDD again, or should I replace it?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 3 months ago (1 child)

It's good, the only downside is it's a smart tool which only gives you smart data Vs actual drive health

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 3 months ago* (last edited 3 months ago) (1 child)

    While it's true we don't really need those old tools anymore, unless one have ancient hardware. On Linux we can use badblocks to test the hard drive. This is from Arch Wiki:

    Modern HDDs and SSDs include firmware that will automatically detect, attempt to correct, and report errors. However, firmware becomes aware of a corrupted sector only upon an attempt to read or write to it. Badblocks may be used to test the entire device at once. It operates by sequentially attempting to read and optionally write to and read back every sector on a drive, and report errors. Consequently, the firmware will react to any detected failures in this process.

    So, for most cases SMART data is actually sufficient. And there is badblocks if you want to check the entire disk. However we don't have manufacturer tools like Windows has.

    A little warning about badblocks. Don't do a write test if you have important stuff on it because it will erase the disk.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 months ago (1 child)

    As a computer technician I have seen hundreds of times the drive and smart data didn't actually know what was going on and it took quality tools to alert the driver to what was happening to start work.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 months ago (1 child)

    If the drive's firmware is faulty, SMART data will be faulty too. But can you say the percentage is somewhat high from what you dealt with, a little statistics? What I saw is my personal experience and it's definitely wouldn't be accurate as yours. I only saw a drive died out of nowhere a handful of times which is not high if I make it into a percentage.Though if the drive itself is faulty, it won't take long for it to die too.

    The best I saw is a WD Caviar Black 500 GB drive from 2011 we use, still kicking. Took a backup because of its age a couple years ago but haven't died yet. The worst I saw was my friend's NVMe SSD that died in 3 months after he installed. Probably its firmware was also faulty because SMART didn't help that time.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 months ago (1 child)

    It's nothing to do with faulty firmware, it's that smart will only see 1 in 3 issues and as such is simply not good enough to use as actual diagnostics.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 months ago (1 child)

    I see. So, you're saying that occasionally checking smartctl (or having smartd as a daemon continuously), running badblocks time to time and maybe checking iostat not really enough? I mean, Linux is by far the most used OS on servers and datacenters, if these are not enough someone would write a proper tool I guess, don't you think?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 months ago (1 child)

    Not at all. It takes a huge amount of work to do so, and the benefit of using raid etc is redundancy so they can afford for things to fail. Smart mon tools is a great example, the software is great but it needs it's database to support that drives functions to work well and they can't and don't support everything.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 months ago (1 child)

    I see, they're solving the issue other way around then by using raid. Didn't know smartmontools work with a database, so it works kind of like an antivirus in a way. Interesting.

    By the way, again it's just my experience but I want to ask this. Have you noticed faulty disks are more common in NVMe SSDs than HDDs or I happen to noticed that because it's common in cheaper options and more expensive ones are actually worth the price?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •