Quote:
Originally Posted by serendipity7000
Well that was a bit of a disaster! I couldn’t work out how to install unetbootin so I followed some instructions for using dd. 100% sure I did everything correctly and selected the correct drive for usb (usb stick was definitely flashing during the process) but it cancelled after filling my main hard drive. I’m going to have a look at the usb thing another day! Only just got 5.1 installed and updated (legacy).
|
this is definitely one of the main concerns with using dd. i had meant to respond to your earlier question, but got busy. even when considering my response i had forgotten to add this warning because i have just become accustomed to using
lsblk before starting the dd write that it didn't occur to me.
even though i have written my live usb's with dd many times, a few months ago i wasn't paying as much attention and recycled a dd write command from ctrl + r and was in the middle of typing my password when i remembered to check the intended write disk. i was about to wipe out my timeshift backup drive instead of writing to the intended usb.
i can understand if you would be averse to trying dd again. in case you are interested, here is my process:
i run
to make sure all of my drives are listed in the same terminal session i intend to use for my dd write. then it is usually something like
Code:
sudo dd if=/path/to/linux.iso of=/dev/sdX status=progress && sync
the if is usually something like /home/user/Downloads/ubuntu18.04.iso (or ~/Downloads/ubuntu18.04.iso for a bit of a shortcut). i get the correct partition letter to replace sdX with from
lsblk. status=progress lets you know how the write is progressing. && sync runs sync as long as the write finishes correctly to make sure everything finishes writing before you unmount the usb.