A moment ago I unmounted my 1TB HDD with 400GB of content and I partition it into two different partitions, obviously keeping the space that was already occupied. I did because I don’t care if the content get corrupted, but after I did it everything is still working perfectly, when I thought everything would be corrupted.

I am possibly a complete ignorant on this subject, but due to the nature of the HDD and how it writes and reads data I expected it to corrupt everything, why didn’t it happen? On an SSD on the other hand I would not consider that possible because it is not even a mechanical part where the information is stored.

  • oleorun@real.lemmy.fan
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Awesome question.

    The operating system, or OS, really does not care about whether it is a hard drive or a solid state drive when moving around the partitions.

    Say your hard drives are pools. One is filled with molasses, and the other has water. The partitions are like the ropes in the pool. Perhaps you have no ropes. Maybe you have three, but two are so close to the wall, and each other, that only a small amount of stuff could occupy those lanes.

    That leaves you with one really large lane. That’s your data partition.

    Water or molasses, the ropes are the same.

    • xantoxis@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I kinda really want a description of the mental model that led to “HDD can’t do this but SSD can”.

      • Xirup@lemmy.dbzer0.comOP
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        As I said, I am not an expert on the subject, my mentality comes from the fact that my concept of partitions was that they were overwritten, like making a scratch on a DVD and the content could not be read because of that.