213

When you accidental format the wrong /dev/sdX (en.meming.world)

submitted 23 hours ago by einfach_orangensaft@sh.itjust.works to c/programmer_humor@programming.dev

41 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] ulterno@programming.dev 0 points 16 hours ago

Mass deployment using a solution that is making you have to remove all other storage devices.
That sounds very frustrating and I wouldn't want to do that.

On the other hand, you're probably an expert on disconnecting and reconnecting SCSI cables by now.

[-] rtxn@lemmy.world 1 points 16 hours ago

There was no need to physically disconnect anything. We didn't actually use any SCSI devices, but Linux (and in turn, the Debian-based Clonezilla) uses the SCSI kernel driver for all ATA devices, so SATA SSDs also appeared as SCSI hosts and could be handled as such. If I had to manually unplug and reconnect hundreds of physical cables, I'd send my resignation directly to my boss' printer.

[-] ulterno@programming.dev 0 points 16 hours ago

So you somehow connected a networked drive as sda - is what I understand from that.

That would be interesting

[-] rtxn@lemmy.world 2 points 16 hours ago

No.

The local machine boots using PXE. Clonezilla itself is transferred from a TFTP server as a squashfs and loaded into memory. When that OS boots, it mounts a network share using CIFS that contains the image to be installed. All of the local SATA disks are named sda, sdb, etc. A script determines which SATA disk is the correct one (must be non-rotational, must be a specific size and type), deletes every SCSI device (which includes ATA devices too), then mounts only the chosen disk to make sure it's named sda.

Clonezilla will not allow an image cloned from a device named sda to be written to a device with a different name -- this is why I had to make sure that sda is always the correct SSD.