Commands like dd
are the best. Good ole greybeard-era spells with arcane syntax and the power to casually wipe out the whole universe (from their perspective ofc) if used haphazardly or not in respectful manner.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
What do you mean? Explicitly having to set if=
and of=
is way harder to screw up than mixing up the order of arguments for e.g. cp
.
I could swear the argument order to "ln" swaps every now and then!
Unless you forget what if and of mean. With cp
it's simply "cp what where". Never had problems remembering that.
Computer equivalent of vacuum decay in our universe...
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.
Yeah lsblk, lsscsi, fdsik -l , go have a coffee, come back later and hit enter on dd
Yeah lsblk, lsscsi, fdsik -l , go have a coffee, come back later and hit enter on dd
Then realize you typed the command wrong and panic when you don't get an error.
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
Always lsblk
before dd
. The order of /sdX might change from boot to boot. Only /nvme doesn't change.
First thing I do after loading the liveusb is write the "mylsblk" which does the much more sane thing of:
lsblk -o NAME,LABEL,PARTLABEL,UUID,SIZE,MOUNTPOINTS
Why is this?
It's a design thing. BIOS can know NVMe disks' location because they're directly mounted to PCIe. SATA isn't like this. Similar logic with the RAM slots.
--status=progress. So happy when they added this.
If only I could remember to set status=progress
...
I always end up using killall -USR1
from another terminal
I am become dd, the destroyer of disks
"/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... "
i always just
cat /dev/??? > /dev/null
to make sure the usb blinks
More like *screams into the void*
Me laughing with /dev/nvme0n1p1
well i mean, the original meme was referring to a usb device with an led...
That's a good way of doing it
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.
We seriously need a series of DD-Command 4 Dummies guides Also you guys have USB drives with lights ????
You all still have a LED inside USB flashdrive?
Yep! I just installed Void about ten minutes ago off a 2GB stick from the mid-2000s. Somehow, those little sticks just keep going!
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.
Remember kids, always lsblk before you dd
heh i do it hardcore, my USB has no light ;)
Reminds me of the DOS days of my youth.
fdisk does not stand for friendly disk.
Don't confuse if and of!
don't cross the streams
/dev/disk/by-id/xxx works for me. Never made a mistake.
Doesn't dd pick sda by default?
No