• muhyb@programming.dev
    26·
    8 hours ago

    Always lsblk before dd. The order of /sdX might change from boot to boot. Only /nvme doesn’t change.

  • ѕєχυαℓ ρσℓутσρє@lemmy.sdf.org
    19·
    8 hours ago

    This is the only reason why I still use GUI for making Linux USBs. Can’t trust my ADHD ass to write the correct drive name. Also, none of my USB drives have a light.

    Popsicle is pretty nice, it doesn’t let you choose the internal drives afaik.

  • waigl@lemmy.world
    53·
    11 hours ago

    IMHO, it was a mistake to make USB block storage use the same line of names also used for local hard disks. Sure, the block device drivers for USB mass storage internally hook into the SCSI subsystem to provide block level access, and that’s why the drives are called sd[something], but why should I as an end user have to care about that? A USB drive is very much not the same thing for me as a SCSI harddisk. A NVMe drive on the other hand, kinda sorta is, at least from a practical purpose point of view, yet NVMe drives get a completely different naming scheme.

    That aside, suggest you use lsblk before dd.

    • Redjard@lemmy.dbzer0.com
      1·
      2 hours ago

      At least sata is well on its way towards dying, so the problem will solve itself in some more years.
      My machines all have nvme exclusively now, only some servers are left using sata. And I would say the type of user at risk of fucking up a dd command (which 95% of the time should be a cp command) doesn’t deal with servers. Those are also not machines you plug thumb drives into commonly.

      In 5-10 years we will think of sda as the usb drive, and it’ll be a fun-fact that sda used to be the boot drive.

    • grue@lemmy.worldEnglish
      5·
      6 hours ago

      While we’re at it, can we also rename the hard drive block devices back to hd instead of sd again? SATA might use the SCSI subsystem, but SATA ain’t SCSI.

    • BCsven@lemmy.ca
      10·
      9 hours ago

      Yeah lsblk, lsscsi, fdsik -l , go have a coffee, come back later and hit enter on dd

    • naeap@sopuli.xyz
      8·
      10 hours ago

      I still made the mistake, when I sleep deprived switched if and of somehow
      My then girlfriend wasn’t exactly happy, that all here photos and music, which we just moved off old CDs, that couldn’t be read correctly anymore, and I spent quite some time to finally move them

      Obviously the old CDs and the backup image were thrown out/deleted just a few days earlier, because I proudly had saved the bulk of it - and being poor students having loads of storage for multiple backups wasn’t in reach.
      Backing them up again to fresh CDs was on the plan, but I quickly needed a live USB stick to restore my work laptop…

      Since then I’m always anxious, when working with dd. Still years later I triple check and already think through my backup restoration plan
      Which is a good thing in itself, but my heart rate spikes can’t be healthy

  • LostXOR@fedia.io
    38·
    11 hours ago

    “/dev/sdb? It’s sdb? With a B? Yep that’s the flash drive. Just type it in… of=/dev/sd what was the letter again? B? Alright, /dev/sdb. Double check with lsblk, yep that’s the small disk. Are my backups working properly? Alright here goes nothing… <enter>”

    • BCsven@lemmy.ca
      7·
      9 hours ago

      I buy them specifically with LED. It s helpful for data transfer, but also helpful for doing a flash of new OS to old nas hardware… You have to hold reset button in on nas until you see it start to read USB (by LED) then you know you can release the reset button.

    • Hellfire103@lemmy.caOPEnglish
      111·
      11 hours ago

      Yep! I just installed Void about ten minutes ago off a 2GB stick from the mid-2000s. Somehow, those little sticks just keep going!

      • ma1w4re@lemm.ee
        5·
        10 hours ago

        Same! I have a 4gb white SanDisk stick, from like 12-14 years ago and is still working 💀💀 it even died on me once, and started working again after a few days 😳😳

      • f4f4f4f4f4f4f4f4@sopuli.xyzEnglish
        2·
        8 hours ago

        Keep them around. I was playing with and testing some ~15 years old mobos for work, and they would not boot from any USB3.0 stick I tried. Same images on an 8GB USB2.0 stick booted with no problem.

        Name and shame: Biostar motherboard

      • kekmacska@lemmy.zipEnglish
        1·
        8 hours ago

        for an usb, it might work. For such an old hard drive, it won’t. Linux will refuse to boot

  • philluminati@lemmy.ml
    4·
    9 hours ago

    ls /dev > /tmp/before

    <insert usb>

    ls /dev > /tmp/after

    <repeat two more times>

    diff /tmp/before /tmp/after

    <sweating>
  • SaltyIceteaMaker@lemmy.ml
    4·
    11 hours ago

    worst case for me would be ereasing my ventoy drive.

    cause i for sure wont be partitioning any of my nvme drives. so the only mistake i can make is like type sda instead of sdb which would just be another usb drive🤷

    • Possibly linux@lemmy.zipEnglish
      1·
      9 hours ago

      I want a immutible Linux that restricts access to critical components. I wouldn’t mind running my desktop in a container.

      • iopq@lemmy.world
        1·
        8 hours ago

        NixOS store (app folder) is read only. You literally can’t mess with it. It doesn’t really need a container, most things are locked down already. Of course you could mess up your home folder, but that’s on you then