Most active commenters

    ←back to thread

    138 points pabs3 | 21 comments | | HN request time: 1.009s | source | bottom
    Show context
    karlkloss ◴[] No.45897158[source]
    And when the AI bubble bursts, "refurbished" HDDs and GPUs will flood the market. Save your money now and be prepared.
    replies(4): >>45897441 #>>45897779 #>>45899005 #>>45905947 #
    1. Nux ◴[] No.45897779[source]
    GPUs yes, but there'll be no HDDs making it alive, they'll get destroyed to protect whatever rubbish they had on.
    replies(4): >>45898933 #>>45899550 #>>45902830 #>>45904076 #
    2. HugoTea ◴[] No.45898933[source]
    Depends how it goes down, if a company goes into insolvency all security policies are off the table and random hardware can get shifted into lot bidding.
    3. pmontra ◴[] No.45899550[source]
    HDD can be written multiple times with random data if data centers really have to protect what their former customers wrote on them. I never looked at those details in standard contracts.

    There is also encryption at rest.

    replies(6): >>45899888 #>>45900464 #>>45903887 #>>45905249 #>>45908119 #>>45908151 #
    4. teeray ◴[] No.45899888[source]
    > HDD can be written multiple times with random data

    Which costs more in compute than simply throwing the drive in a shredder

    replies(2): >>45903924 #>>45905280 #
    5. tencentshill ◴[] No.45900464[source]
    They have enough investor money they don't need to recoup it selling used drives. Straight to the shredder.
    6. archagon ◴[] No.45902830[source]
    I believe many enterprise drives have instant-erase functionality (presumably deleting an encryption key).
    replies(1): >>45905281 #
    7. jimwalsh ◴[] No.45903887[source]
    All the large datacenter/cloud companies do not let hard drives leave the building.
    8. walterbell ◴[] No.45903924{3}[source]
    What's the disposal method for shredded drives?
    replies(1): >>45904915 #
    9. bigbuppo ◴[] No.45904076[source]
    Nah, the liquidators aren't going to care about that. Those hard drives are going to be shipped out with all your wildest porn chat bot fantasies.
    replies(1): >>45904736 #
    10. maerF0x0 ◴[] No.45904736[source]
    "Shredded onsite" means by the next user when they format the drive and write contents to it /s
    11. faeyanpiraat ◴[] No.45904915{4}[source]
    Mount Doom
    12. SoftTalker ◴[] No.45905249[source]
    All you really need to do is write one pass of zeros on them. That will prevent anyone but a very dedicated adversary with expensive equipment from recovering any data, especially on TB scale drives.

    Can still take hours per drive though, which is why a lot of people skip it.

    replies(2): >>45905700 #>>45907777 #
    13. rwyinuse ◴[] No.45905280{3}[source]
    Not really, if we give the HDD some resale value. There's a market for used but functional hard drives.
    14. SoftTalker ◴[] No.45905281[source]
    If they were encrypted to begin with, yes. Many are not.
    replies(1): >>45907559 #
    15. edoceo ◴[] No.45905700{3}[source]
    I make a random 1MB chunk, then write that all over the drive, at overlapping offsets. I've been told that really clears it. On IDE-spinning-rust disks I trusted it, not sure if I should trust these modern SSD
    replies(1): >>45906905 #
    16. p1mrx ◴[] No.45906905{4}[source]
    Why rewrite the same 1MB chunk, instead of making new random chunks?

    Redundant data at least opens the possibility that the drive could deduplicate.

    replies(1): >>45908677 #
    17. archagon ◴[] No.45907559{3}[source]
    I was under the impression that these drives may be transparently encrypted by default. (Rollable encryption key in hardware, invisible to end-user.)
    18. krior ◴[] No.45907777{3}[source]
    Or encrypt it and just trash the encryption header.
    19. PeaceTed ◴[] No.45908119[source]
    When I used to do computer refurbishment, 'Boot and Nuke' was great for this. Load it up at boot, and write over the with random junk a few times.
    20. ComputerGuru ◴[] No.45908151[source]
    I wrote hddrand to write random data and optionally read it back to verify integrity. https://github.com/mqudsi/hddrand
    21. edoceo ◴[] No.45908677{5}[source]
    Cause making new random was taking too much time.