- cross-posted to:
- privacyguides@lemmy.one
- cross-posted to:
- privacyguides@lemmy.one
I am shocked by this - the quote in below is very concerning:
“However, in 2024, the situation changed: balenaEtcher started sharing the file name of the image and the model of the USB stick with the Balena company and possibly with third parties.”
Can’t see myself using this software anymore…
♬ Hello
ddmy old friend
I’ve comesudowith you again ♬… and the sign said the bytes of the distro are written to the SD card …. if they’re un-tar’d …
Hello cat or cp or pv… Or anything else that works with files
Huh this is news to me. Wonder why dd has been the defacto standard in guides everywhere for the past 15-20+ years
Thank you for pointing it out.
…and that’s how I met your
motherforkWow, I was not aware of that. I really liked balena. Thankfully, I haven’t been using it since installing Mint.
Just use
dd. It’s not that hard. You pass it 2 arguments:if=the file you want to flash, andof=the destination. If you’re feeling fancy, pass in somestatus=progress. And don’t forget to prepend it withsudo. That’s it.I just tried this the other day and was unable to boot from the USB. any chance you could shed some light on what i might have screwed up?
The command was:
dd if=fedora.iso of=/dev/sdc bs=4M status=progressThe USB stick was not mounted and the fedora image was verified. The command completed successfully but I couldn’t boot from it. When I used fedora writer to burn the same image to the same USB stick it booted no problem.
Edit: spelling
Don’t use Fedora myself, but it may not be a hybrid ISO that becomes bootable when written… so I looked and you are missing a flag
dd if=/path/to/image.iso of=/dev/sdX bs=8M status=progress oflag=direct
From https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/
I don’t think
oflags=directhas any influence on the result. Apparently that’s about disabling the page cache in the kernel, which can avoid a situation in which the system slows down due to buildup yet-to-write pages.Perhaps not. But the flag allows for direct I/O for data, bypassing buffers which can be overrun with certain size blocks, potentially causing dirty buffer depending on the machine being used. My understanding is that it’s “more reliable” for writing (especially on shitty USB Flash drives) and getting the exact ISO properly written.
But it could be useless all the same - I’m just pointing out that OPs command is not the one recommended by Fedora when writing their ISO. Also OP is less likely to pull the drive before buffers have flushed this way.
Oh yeah that’s where I was getting at, but I didn’t have time to write that out earlier. I agree that OP probably pulled out the usb stick before buffers were flushed. I imagine that direct I/O would mitigate this problem a lot because presumably whatever buffers still exist (there would some hardware buffers and I think Linux kernel I/O buffers) will be minimal compared to the potentially large amount of dirty pages one might accumulate using normal cached writes. So I imagine those buffers would be empty very shortly (less than one second maybe?) after dd finishes, whereas I’ve seen regular dd finish tens of seconds before my usb stick stopped blinking it’s LED. Still if you wait for that long the result will be the same.
Ah! Thank you! I knew it was something I screwed up!
You didn’t screw up, you beautifully proved why the CLI is never a simple solution.
deleted by creator
Did you make sure that the
ofis correct?lsblkto make sure.If your sure it wrote to the right drive i would make sure that you have a good download. Did you run your checksums?
I think fedora works with secureboot but you might want to disable it just to see if that is the issue. I believe you can reenable it after install.
Make sure to go into the bios and boot from external drive/usb.
Out of 15 years of using
ddi have never had a problem.I did verify with
lsblk, with a listing before and after plugging in the stick to be absolutely sure.I also did verify the checksum of the ISO.
I’ll double check SecureBoot, but as I mentioned, the same ISO written to the same stick with Fedora writer did boot in the same machine it wouldn’t boot from with the
ddversion.I know it’s something I did or didn’t do to make it work correctly, so this is not me trying to dunk on
dd, just trying to understand what I did wrong.
dd
Never understood why you would use anything else. It’s in coreutils!!!
There are people coming from Windows, which does not have
dd.J think the best solution for window$ ppl is Rufus?
“just” setting that up takes much longer than installing a small app to do it.
OK so keep using the small app that is reporting your usage activity
Or just dont use windows
Because GNU dd-rescue exists
It’s faster to drag and drop a downloaded ISO and choose the target from a dropdown, than do it on a command line. And get a progress bar. As much as command line is usually faster, it isn’t in this case.
Yes you can also get a progress bar on the command line but it’s more typing again, and realistically you need to look the option up every time if you use dd once every 3 months.
Lmao. Uses a computer, typing is too much. It took more typing to write your comment than to craft a tab-completed dd command, even if you had to call the help menu to refresh your available options, jus’ sayin’
I get it though, the general public are scared of the big bad 'puter magic and need GUIs.
Let me try: Lmao. Uses a computer, still does stuff the slower way because learning new things is too difficult.
To be serious, I am looking for the best solutions for my use cases, not adequate ones. Yes dd works perfectly fine and as you noted doesn’t take long to use anyway. But just because it’s fine doesn’t mean other approaches aren’t better.
A GUI tool can offer or take a list of download URLs for common distros so downloading isn’t a separate step, it can check if the target device is a flash drive and not a hard drive by mistake, it can automatically choose the optimal block size for the device, it can verify the process by reading it back from the device, can show you the current filesystem, label, and usage of the target device to confirm, it can handle flashing to multiple devices at the same time with separate and total progress bars.
If I wanted to do all that on the command line it’d be quite a lot of commands or a sizeable script to write. Or I can use a simple dd command and lose out on all of the above. Either way it’s a worse option. I will only use dd when a GUI tool isn’t installed, or when I’m on a system without a DE.
Tab complete? Just ^R that shit!
Shhh, that’s too advanced. Besides, CLI is outdated and slower than GUIs, this is just insane behavior /s
I honestly didn’t even need to specify tab-completed. It’s still less typing than their comment unless your paths are miles long.
Many won’t touch the command line.
I know, but just because someone doesn’t understand something or ignores it doesn’t mean it isn’t the best/simplest choice for 90% of cases.
It is indeed the best way, but somehow I am still anxious using this command, even after flashing countless USB drives 😅
I’ve made it a habit to type out the command without sudo at first, then when it yells at me about permissions I am reminded to go back and double-check.
I used it less than a week ago for a Mint install, worked fine.
If you actually read the post, you would have known, it does work, but there are some privacy concerns with it:
“However, in 2024, the situation changed: balenaEtcher started sharing the file name of the image and the model of the USB stick with the Balena company and possibly with third parties.”
I seriously DGAF who knows which Mint edition I installed or the brand of flash drive I used.
Ventoy is life!
did they ever clear up that random unexplained binaries issue?
From what I could gather, they’re taken from Fedora and OpenSUSE. They’re signed blobs for secure boot support.
I mean for privacy things it makes sense to avoid leaking anything. But I fail to understand where the danger is to have anonymous data that says a user installed “Ubuntu-24.04-wappity-whatever.iso” to “KINGSTON DATA TRAVELER 32GB” at some point.
If anything that seems like worthwhile analytics for the dev team to have access to.
Most software lets you opt out of sending anonymous analytics data though.
They could just ask. “Please allow us to know what you flash and on what device so we can improve the software” yes, no, tell me more, show me the data
Then I would have no problem using the SW, transparency is important to me
It is a trap for people not knowing and government may use it as excuse to activate executive
have they tried also tracking for errors, cause it fucks up every second image unlike rufus
Truth. Etcher is garbage. Rufus is king.
Not using Ventoy in 2025?
Ventoy uses several blobs without any instructions of compiling them yourself?
Balenaetcher has, for me at least, failed to write to USBs for the last 3 years or so that I’ve tried to use it - meanwhile random iso writers from flatpak have been more reliable for me. Very obnoxious that so many iso related sites recommend it. Rufus, kicks tons of ass, if for whatever reason you’re still on windows.
Also on most distros I’ve tried, the disk utility has some sort of right click or context menu that gets you a ‘restore disk image’ button that works great as well.
Flatpack? You are using Linux and you need “iso writers”? Is your dd broken, son?
😂 I also read this as Ron’s voice!
Nah as much as i love doing stuff via terminal, I am extra paranoid specifically about writing to the wrong device and losing data; I prefer as many confirmations as possible that I’m writing to the correct drive, and graphical installers tend to give me just a few more reassurances. A few examples would be stuff like
- a graphical representation of partitions (the general layout of a drive tends to offer an easy ‘fingerprint’ in my mind; like the pattern of partitions help me confirm I’m looking at, say, a Debian install USB compared to a single-partition general purpose storage disk)
- icons for different types of devices, like an SD card, USB, or hard disk icon
- confirmation dialogues summarizing what device is targeted, and what all will be performed
I’m also the kind of person who stares at a written email worrying about every last nuance of my phrasing, so 🤷♂️😂 definitely a me problem, I think!
This sounded like a techy Ron Swanson.
Are the scissors broken in your house, son?
At least one person got the reference!
Rufus is great! I worked with the maintainer to fix a bug in hardware they didn’t have and it was a very pleasant experience.
Why use a fancy GUI tool when good old
dddoes the trickBecause of the risk of accidentally wiping the main drive if you’re just copy pasting stuff
If that happens to you, that’s both a great reminder that mindlessly copy-pasting commands from the internet is a terrible idea, and a chance to practice your restore-from-backup routine! I see no downsides.
deleted by creator
cat is the tool of distinguished gentlemen
dd status=progresscan also tell you how far along the operation is.Dang, nice! I’ve been using dd for nearly 30 years and have never seen that. I actually used to used dcfldd because it had better progress reporting than dd (and supported repeated patterns for input). Thanks for sharing!
cp command works well too
for Windows
Friendship ended with Balena
Now Rufus is my new best friend

















