am I the only one?
19h 33m ago by lemmy.zip/u/overcast in linux@lemmy.ml
hi, in the past I’ve got a pretty weird issue while I was getting ready to make a switch: every USB that I tried failed to boot
turns out, the “safer” way to get it out from the PC (the eject function) messed up its file system
it was long ago, but the other day I made another bootable USB and it happened again, I thought it was just a bug that would be eventually fixed it happens both for Linux Live ISOs and Windows Install Media
am I the only one?
What are you using to flash the drive, what OS, what DE, what machine are you on and what are you trying to boot on?
am I the only one?
Maybe not but this is for sure the first time that I read about an problem like that. Also never experienced it myself.
@overcast yes, the only one.
If you want to be sure, go in a terminal and type umount /media/<stick> ( I do not know your path) and wait a bit. maybe mount it again there with mount /media/<stick> and have a look, if there is an error of a possible damaged filesystem.
After the files have copied I always run sync to be sure then I umount
Yes, this exactly.
What are you using? Try Rufus if you aren't using it to make the bootable media. Its my go to on Windows. Literally the GOAT.
Fedora Media Writer is the best
dd is but I'll allow a gui app.
I've found that depending on what distro/OS it is certain methods of burning the ISO don't work correctly, no clue why. Windows needs their official tool, so because of that i use a vm to burn it. I've also had linux distros that couldn't boot when dropping it onto a ventoy drive, and would only work when directly burning it with dd, so it might have something to do with what ISO you're trying to burn and how you're burning it.
full ass browser and telemetry for a simple disk imager.. balena ether shouldn't be recommended