I colori dei dischi

Cosa significano i codici di colore dei dischi fissi? È una pratica usata da Western Digital per indicare la destinazione d’uso prevista per un disco.

Da What do different WD Hard Drive colors mean?

  • WD Blue HDD: è un supporto di archiviazione generico, affidabile e a basso consumo.
  • WD Red HDD: è prodotto per sistemi NAS e RAID.
  • WD Green HDD: consuma meno energia ed è simile ai dischi rigidi della serie blu. L’edizione verde non è popolare al giorno d’oggi.
  • WD Black HDD: è un disco rigido ad alte prestazioni ed è progettato per applicazioni di gioco e creazione di contenuti di fascia alta.
  • WD Purple HDD: è un dispositivo di archiviazione per sistemi di sorveglianza.
  • WD Gold HDD: è una versione premium dei dischi rigidi WD ed è progettato per i centri dati e altre applicazioni simili.

Tradotto con www.DeepL.com/Translator (versione gratuita)

Data rotting on magnetic hard drives

According to https://mastodon.uno/@octo/108051239339031165

…it would be good practice to rewrite the data on HDDs every few years because magnetism tends to weaken over time…

Flash memories (SSD, microSD…), on the other hand, simply need to be powered up from time to time, because they store bits as electrical charges in cells that act more or less as capacitors.
The data should not be rewritten, indeed rewriting any data on a flash memory consumes the cells.

Translated with deepl.com

While the fading of data on flash media which are not powered for a long time is a issue I know about, knowing that data also fades from magnetic disks is new to me.

So I searched for “refresh hard disk“, soon finding How to refresh stored data with Linux and Windows. The instruction on this page has a potentially dangerous error and it doesn’t explain how and why data rots on a magnetic hard drive.

Hard Disk Drives use magnetic storage and, over time, lose their magnetic orientation. Long exposure to wet or humid conditions might also affect the hardware and lead to degradation. (See Data degradation – Wikipedia and What Is Digital Decay & Data Degredation?)

On akcp.com there are good, concise suggestions. on Hard Drive Long-term storage temperatures

When a hard drive is used as long-term data storage, it will usually fare better than SSD drives (as we will examine in the SSD section). When turned off, a hard drive could be safely stored between -40°C (-40°F) and 70°C (158°F), but it will vary between models. Western Digital recommends that a standard consumer drive’s storage temperature be between 12°C (53.6°F) and 33°C (91.4°F). You would also need to choose a storage location that isn’t humid, or in direct sunlight.

After storing a hard drive at a higher or lower temperature, you should allow the drive enough time (at least 2-3 hours but longer if there are bigger differences) to heat up to room temperature before you attempt to use it. If the ambient temperature is not highly fluctuating around the drive (higher or lower than 15-20 degrees), as magnetic storage it will most likely keep your data safe and readable even many years later after it has been turned off.

Other than the environmental conditions around the drive, you would not need to worry about the data retention of a hard drive. It is permanent magnetic storage and no need to be turned on to “refresh the stored data”. Therefore, it is still recommended that you use hard drives for off-site or external data storage of your backups – they are still more cost-effective and reliable for this application.

So, as long as you keep your backup hard drive unplugged, safely stored in a dry place with a fairly constant mild temperature you can safely assume that the data will be safe for several years. I have successfully recovered data from my 42Mb SCSI drive of my first Amiga that were stored in a humid garage. Because I was lucky enough to have access to a far more recent machine with Ultra SCSI, plus I had the right cable to plug to actually connect to the drive. Because my old Amiga can’t be connected to the network, a capability that nowadays we take for granted.

Because after having correctly stored the media, when the time comes to recover data on magnetic hard drives the next main problem is how to read it. More specifically having the hardware to read the media.

Everyone has a 5¼” floppy drive, hasn’t you? Or a 3½” floppy? Commodore 64 and original PC extensively used the first, Amiga, Atari ST and later PC the latter.

A couple of years ago I could easily find an USB 3½” floppy reader on my favourite store. They don’t have them anymore. Having working hardware to read the media is as important as conserving uncorrupted media:

Long-term preservation of magnetic media is affected by two major factors; its intrinsic instability and the likelihood of the hardware obsolescence. The equipment used to access magnetic media today will almost certainly have been superseded in the next decades. For all practical purposes the records will be unusable, even media in good condition. The main prospect for long-term retention of the information held on magnetic media seems to be in regular copying or data migration, thus maintaining a good quality signal that can be read using available equipment. Copying can either be to fresh tape or disk, or to some other machine-readable format. Once copied to an uncompressed digital format the information can be copied without loss of quality.

from Preserving magnetic media on National Archive of Australia

So the mantra is “make backups, make backups, make backups”. On recent hardware and media.

Now let’s return to the page on bikegremlin. Simply put:

Never, ever run badblocks that way

You shall not use the “-f” switch, which force the program to run even with a mounted drive. Especially on a mounted media. You shall unmount it instead of ejecting, and only after that you can run badblock that way.

The man page (manual) of badblocks clearly states:

   -f     Normally, badblocks will refuse to do a read/write or a non-destructive  test
          on  a  device  which  is mounted, since either can cause the system to poten‐
          tially crash and/or damage the file system even if it is  mounted  read-only.
          This can be overridden using the -f flag, but should almost never be used ---
          if you think you're smarter than the badblocks program, you almost  certainly
          aren't.   The  only  time  when  this  option  might be safe to use is if the
          /etc/mtab file is incorrect, and the device really isn't mounted.

So unless your name is Theodore T’so I warmly suggest you not to use the -f flag.

It is way more sane to copy that data elsewhere. Or using the media for a new backup.

Run macOS on QEMU/KVM. With OpenCore + Big Sur + Monterey support now! Only commercial (paid) support is available now to avoid spammy issues. No Mac system is required.

From https://github.com/kholia/OSX-KVM

I’ll try it because Sosumi which uses snap has some issues when dealing with some part of data linked in another partition (don’t ask me why I did it)

Update: Try this instead https://www.linuxuprising.com/2021/03/install-macos-big-sur-or-catalina-in.html and https://github.com/sickcodes/Docker-OSX