Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Want to burn an ISO to USB - how?
39 views
Skip to first unread message
Chris
Apr 22, 2021, 10:34:07 AM4/22/21
to
I must be missing something. I've searched for different options and
either they mention Disk Utility - which no longer has the ability - or
hdiutil - which I can't get to work - or there's Balena Etcher - which
continually creates corrupted USB sticks.
Surely there's an easy way to burn an (ubuntu) ISO to a USB stick? I
can't find it. Balena Etcher is the solution recommended by Ubuntu but
it never completes successfully. I've tried two sticks one of which is
new, and they both work fine via Windows tools.
Help!? What do others use, please?
Mark
Apr 22, 2021, 10:50:42 AM4/22/21
to
32GB SanDisk Cruzer with Linux (ElementaryOS* and PopOS) without a
problem. I think I was going to try Ubuntu as well but never got around
to it.
(*From my very limited usage, a very nice little distro)
--
Cheers ... Mark
Theo
Apr 22, 2021, 10:53:58 AM4/22/21
to
Chris <ithi...@gmail.com> wrote:
>
> I must be missing something. I've searched for different options and
> either they mention Disk Utility - which no longer has the ability - or
> hdiutil - which I can't get to work - or there's Balena Etcher - which
> continually creates corrupted USB sticks.
Be aware that an ISO needs to specifically support booting from a mass
>
> I must be missing something. I've searched for different options and
> either they mention Disk Utility - which no longer has the ability - or
> hdiutil - which I can't get to work - or there's Balena Etcher - which
> continually creates corrupted USB sticks.
storage drive (ie USB stick), which boot in a different way from a CD/DVD.
The Ubuntu ISO supports that, but others (eg some Windows) need extra work.
> Surely there's an easy way to burn an (ubuntu) ISO to a USB stick? I
> can't find it. Balena Etcher is the solution recommended by Ubuntu but
> it never completes successfully. I've tried two sticks one of which is
> new, and they both work fine via Windows tools.
more lightweight as it doesn't contain a full web browser(!).
https://gitlab.com/bztsrc/usbimager
You can also do it from Terminal:
$ diskutil list
- identify the drive number of your target stick (ie /dev/disk2 or
whatever). Don't get this wrong or you'll nuke your hard drive!
$ diskutil unmountDisk disk2
$ sudo dd if=ubuntu-20.04-desktop.iso of=/dev/rdisk2 bs=1m
- wait for it to finish (may be some minutes for a slow USB)
$ sync
Theo
nospam
Apr 22, 2021, 10:56:21 AM4/22/21
to
In article <s5s1gt$qqm$1...@dont-email.me>, Chris <ithi...@gmail.com>
wrote:
> I must be missing something. I've searched for different options and
> either they mention Disk Utility - which no longer has the ability - or
> hdiutil - which I can't get to work - or there's Balena Etcher - which
> continually creates corrupted USB sticks.
it shouldn't, but the real problem is that balena is electron garbage.
> Surely there's an easy way to burn an (ubuntu) ISO to a USB stick? I
> can't find it. Balena Etcher is the solution recommended by Ubuntu but
> it never completes successfully. I've tried two sticks one of which is
> new, and they both work fine via Windows tools.
>
> Help!? What do others use, please?
dd
it's included with every mac. no need for any additional tools.
wrote:
> I must be missing something. I've searched for different options and
> either they mention Disk Utility - which no longer has the ability - or
> hdiutil - which I can't get to work - or there's Balena Etcher - which
> continually creates corrupted USB sticks.
> Surely there's an easy way to burn an (ubuntu) ISO to a USB stick? I
> can't find it. Balena Etcher is the solution recommended by Ubuntu but
> it never completes successfully. I've tried two sticks one of which is
> new, and they both work fine via Windows tools.
>
> Help!? What do others use, please?
it's included with every mac. no need for any additional tools.
nospam
Apr 22, 2021, 11:01:26 AM4/22/21
to
In article <U5y*ao...@news.chiark.greenend.org.uk>, Theo
<theom...@chiark.greenend.org.uk> wrote:
> $ diskutil list
> - identify the drive number of your target stick (ie /dev/disk2 or
> whatever). Don't get this wrong or you'll nuke your hard drive!
>
> $ diskutil unmountDisk disk2
> $ sudo dd if=ubuntu-20.04-desktop.iso of=/dev/rdisk2 bs=1m
> - wait for it to finish (may be some minutes for a slow USB)
> $ sync
sync is not required.
> $ diskutil list
> - identify the drive number of your target stick (ie /dev/disk2 or
> whatever). Don't get this wrong or you'll nuke your hard drive!
>
> $ diskutil unmountDisk disk2
> $ sudo dd if=ubuntu-20.04-desktop.iso of=/dev/rdisk2 bs=1m
> - wait for it to finish (may be some minutes for a slow USB)
> $ sync
Chris
Apr 22, 2021, 2:44:19 PM4/22/21
to
dd is so slow...
Anyway I tried that and it failed again:
> sudo dd if=kubuntu-20.04.2.0-desktop-amd64.iso of=/dev/disk2 bs=1m
2520+1 records in
2520+1 records out
2643034112 bytes transferred in 3724.972502 secs (709545 bytes/sec)
A window pops saying that I have an recognised disk and whether to
initialize, ignore or eject.
Also tried usbimager and got a "permission denied" despite giving it
full disk access.
There's nothing wrong with the stick as I wrote an image to it fine in
Windows and it's also brand new.
Could it be a hardware issue? This is on a 2017 MBP with Catalina.
nospam
Apr 22, 2021, 2:59:26 PM4/22/21
to
In article <s5sg61$gg6$1...@dont-email.me>, Chris <ithi...@gmail.com>
wrote:
> Thanks. I would have thought there was a more elegant solution than dd.
> dd is so slow...
be sure to use /dev/rdisk# not /dev/disk#
it's *much* faster.
wrote:
> Thanks. I would have thought there was a more elegant solution than dd.
> dd is so slow...
it's *much* faster.
Chris
Apr 22, 2021, 3:00:14 PM4/22/21
to
be used with the Mac so I thought that might be the issue. Used a proper
Apple media dongle (with USB-A and -C plus VGA) and it does the same as
do other ports on the Mac.
What's going on here? Something's borked.
Bruce Horrocks
Apr 22, 2021, 4:18:55 PM4/22/21
to
On 22/04/2021 19:44, Chris wrote:
> On 22/04/2021 15:53, Theo wrote:
...
>>
>> You can also do it from Terminal:
>>
>> $ diskutil list
>> - identify the drive number of your target stick (ie /dev/disk2 or
>> whatever). Don't get this wrong or you'll nuke your hard drive!
>>
>> $ diskutil unmountDisk disk2
>> $ sudo dd if=ubuntu-20.04-desktop.iso of=/dev/rdisk2 bs=1m
>> - wait for it to finish (may be some minutes for a slow USB)
>> $ sync
>
> Thanks. I would have thought there was a more elegant solution than dd.
> dd is so slow...
bs=10m will make it run faster. You can also press ctrl-T while it's
>> You can also do it from Terminal:
>>
>> $ diskutil list
>> - identify the drive number of your target stick (ie /dev/disk2 or
>> whatever). Don't get this wrong or you'll nuke your hard drive!
>>
>> $ diskutil unmountDisk disk2
>> $ sudo dd if=ubuntu-20.04-desktop.iso of=/dev/rdisk2 bs=1m
>> - wait for it to finish (may be some minutes for a slow USB)
>> $ sync
>
> Thanks. I would have thought there was a more elegant solution than dd.
> dd is so slow...
running to see progress.
> Anyway I tried that and it failed again:
>> sudo dd if=kubuntu-20.04.2.0-desktop-amd64.iso of=/dev/disk2 bs=1m
> 2520+1 records in
> 2520+1 records out
> 2643034112 bytes transferred in 3724.972502 secs (709545 bytes/sec)
>
> A window pops saying that I have an recognised disk and whether to
> initialize, ignore or eject.
acid test?
> Also tried usbimager and got a "permission denied" despite giving it
> full disk access.
>
> There's nothing wrong with the stick as I wrote an image to it fine in
> Windows and it's also brand new.
>
> Could it be a hardware issue? This is on a 2017 MBP with Catalina.
boot a PC with it.
--
Bruce Horrocks
Surrey, England
(bruce at scorecrow dot com)
Theo
Apr 22, 2021, 5:10:42 PM4/22/21
to
Chris <ithi...@gmail.com> wrote:
> Thanks. I would have thought there was a more elegant solution than dd.
> dd is so slow...
At this kind of speed it's likely the write speed of your flash media. Some
> Thanks. I would have thought there was a more elegant solution than dd.
> dd is so slow...
drives, particularly if they're from a few years ago, are very slow.
> Anyway I tried that and it failed again:
> > sudo dd if=kubuntu-20.04.2.0-desktop-amd64.iso of=/dev/disk2 bs=1m
> 2520+1 records in
> 2520+1 records out
> 2643034112 bytes transferred in 3724.972502 secs (709545 bytes/sec)
% curl -v -s http://cdimage.ubuntu.com/kubuntu/releases/20.04.2/release/kubuntu-20.04.2.0-desktop-amd64.iso \
2>&1 | grep Length
< Content-Length: 2643034112
Sounds like it's written the correct length to me.
If you want to check:
% sudo dd if=/dev/rdisk2 bs=32768 count=80659 | shasum -a 256
should match the output of:
% curl https://cdimage.ubuntu.com/kubuntu/releases/20.04.2/release/SHA256SUMS
In case you were wondering, 80659*32768=2643034112 - it's the largest
power-of-2 I could factor out.
Theo
Chris
Apr 22, 2021, 5:43:30 PM4/22/21
to
Chris
Apr 22, 2021, 6:49:26 PM4/22/21
to
Alan B <alanrich...@nospamgmail.com.here> wrote:
> It’s an unrecognised file system as far macOS is concerned but it should
> still boot if you restart holding down the alt key and allow you to install
> kubuntu to another USB drive or whatever.
Wait, that message is normal? Most confusing!
That can't be right. If I take the stick that's been burned on windows I
can see the files just fine on the mac. What's the difference?
> still boot if you restart holding down the alt key and allow you to install
> kubuntu to another USB drive or whatever.
Wait, that message is normal? Most confusing!
That can't be right. If I take the stick that's been burned on windows I
can see the files just fine on the mac. What's the difference?
STALKING_TARGET_74
Apr 23, 2021, 10:41:45 PM4/23/21
to
Diesel: functionally illiterate fraud. Promotion is a wonderful thing
and consumer stupidity is even better. Can you stop begging for my attention?
What were you hoping for? Helping Jeff Relf and helping Gregory Hall isn't
the same thing. Nobody should knowingly help Jeff Relf do anything - except
for driving off a cliff, licking hot wires, or successfully decapitating
himself.
No one here has ever read my code, much less found a bug; still, in my
auxiliary brain, I'm thinking, "What if the program crashes", a secret
I share with you only now.
--
Get Rich Slow!!
https://duckduckgo.com/?q=steve+carroll+racist+swine
https://duckduckgo.com/?q=steve+carroll%3A+racist+swine
https://duckduckgo.com/?q=dustin+cook+the+functionally+illiterate+fraud
Steve Carroll the Racist Swine
Dustin the dude with the stuck floppy
Apr 24, 2021, 2:13:24 PM4/24/21
to
about him. It was FromTheRafters who stated that he and his hired winos
used to steal candy from toddlers all the time and it was free entertainment,
not even a slight concern. FromTheRafters is six seconds away from being
in Ian McCall's kill file. FromTheRafters's reverse compiled 3d printers
with the MaxCliqueDyn Maximum Clique algorithm to produce posts which are
not unlike those from my posts.
--
This Trick Gets Women Hot For You!!
<http://web.archive.org/web/20200911090505/https://www.usphonebook.com/dustin-
cook/UQjN2UTM5IzM1ADM0czNwMjMyYzR?Gremlin=&Diesel=>
Steve Carroll
Apr 24, 2021, 5:10:05 PM4/24/21
to
On Thursday, April 22, 2021 at 2:43:30 PM UTC-7, Chris wrote:
to Windows users. Primary interface is Pantheon, though. Choice is all
you require after dealing with ChromeOS. Are you being transparent on
purpose?
These losers get their jollies out of provoking angry responses to their
crap, which is the very definition of a troll. Several people keep replying
to Shadow. I can't denounce Bob Campbell for his animosity but I do not
fathom why he writes here other than to mess with Shadow. Bob Campbell
is pushing discussions as experienced in a moderated group and open groups
are not it. But when the stats were run, it turns out by _that_ criteria,
Shadow was far more "fanatical" than even I imagined.
-
This Trick Gets Women Hot For You!!
https://www.youtube.com/watch?v=0ZNxaaKD7-c
https://duckduckgo.com/?q=steve+carroll+racist+swine
Steve 'Racist Swine' Carroll
Chris
Apr 26, 2021, 4:18:54 AM4/26/21
to
I thought I sent this last week. Stuck in my outbox.
On 23/04/2021 08:21, Alan B wrote:
> On 22 Apr 2021 at 23:49:24 BST, "Chris" <ithi...@gmail.com> wrote:
> version), inserted a spare 32GB USB stick, unmounted the it via diskutil and
> wrote the iso to the stick. Note that I did not bother with the hdiutil
> conversion.
>
> sudo dd if=kubuntu-21.04-desktop-amd64.iso of=/dev/rdisk2 bs=4m
>
> After a few minutes the following message appeared:
>
> 701+1 records in
> 701+1 records out
> 2941128704 bytes transferred in 172.057264 secs (17093894 bytes/sec)
>
> But NO disk unreadable message!
Just tried it with kubuntu 21.04 and got the exact same as you including
no message.
> Diskutil list revealed:
>
> /dev/disk2 (external, physical):
> #: TYPE NAME SIZE IDENTIFIER
> 0: GUID_partition_scheme *32.0 GB disk2
> 1: Microsoft Basic Data 2.9 GB disk2s1
> 2: EFI ESP 5.1 MB disk2s2
> 3: Microsoft Basic Data 307.2 KB disk2s3
diskutil for k21.04:
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *30.8 GB disk2
1: Microsoft Basic Data 2.9 GB disk2s1
2: EFI ESP 5.1 MB disk2s2
3: Microsoft Basic Data 307.2 KB disk2s3
Repeated it with kubuntu 20.04 and still got the unreadable message.
diskutil for k20.04:
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *30.8 GB disk2
1: Apple_partition_map 4.1 KB disk2s1
2: Apple_HFS 4.1 MB disk2s2
So definitely something weird going on, despite it being bootable and
seemingly working as expected.
> The stick is bootable via restart + alt key. I wonder if the iso format has
> changed between kubuntu 20.04 and 21.04?
I thought they were always just iso9660. Google doesn't find anything
different.
> I seem to remember inspecting
> unreadable sticks in the past with diskutil and seeing fdisk formatted
> partitions on the stick which probably upset macOS although the stick was
> still bootable.
>
> As for creating it on Windows, maybe it depends on the tool you used and how
> it formats the installer stick?
I used rufus: https://rufus.ie/en/. I think it used MBR partitioning
scheme and FAT32.
On 23/04/2021 08:21, Alan B wrote:
> On 22 Apr 2021 at 23:49:24 BST, "Chris" <ithi...@gmail.com> wrote:
>
>> Alan B <alanrich...@nospamgmail.com.here> wrote:
>>>
>>> It’s an unrecognised file system as far macOS is concerned but it should
>>> still boot if you restart holding down the alt key and allow you to install
>>> kubuntu to another USB drive or whatever.
>>
>> Wait, that message is normal? Most confusing!
>>
>> That can't be right. If I take the stick that's been burned on windows I
>> can see the files just fine on the mac. What's the difference?
>
> This morning I downloaded kubuntu-21.04-desktop-amd64.iso (the latest official
>> Alan B <alanrich...@nospamgmail.com.here> wrote:
>>>
>>> It’s an unrecognised file system as far macOS is concerned but it should
>>> still boot if you restart holding down the alt key and allow you to install
>>> kubuntu to another USB drive or whatever.
>>
>> Wait, that message is normal? Most confusing!
>>
>> That can't be right. If I take the stick that's been burned on windows I
>> can see the files just fine on the mac. What's the difference?
>
> version), inserted a spare 32GB USB stick, unmounted the it via diskutil and
> wrote the iso to the stick. Note that I did not bother with the hdiutil
> conversion.
>
> sudo dd if=kubuntu-21.04-desktop-amd64.iso of=/dev/rdisk2 bs=4m
>
> After a few minutes the following message appeared:
>
> 701+1 records in
> 701+1 records out
> 2941128704 bytes transferred in 172.057264 secs (17093894 bytes/sec)
>
> But NO disk unreadable message!
Just tried it with kubuntu 21.04 and got the exact same as you including
no message.
> Diskutil list revealed:
>
> /dev/disk2 (external, physical):
> #: TYPE NAME SIZE IDENTIFIER
> 0: GUID_partition_scheme *32.0 GB disk2
> 1: Microsoft Basic Data 2.9 GB disk2s1
> 2: EFI ESP 5.1 MB disk2s2
> 3: Microsoft Basic Data 307.2 KB disk2s3
diskutil for k21.04:
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *30.8 GB disk2
1: Microsoft Basic Data 2.9 GB disk2s1
2: EFI ESP 5.1 MB disk2s2
3: Microsoft Basic Data 307.2 KB disk2s3
Repeated it with kubuntu 20.04 and still got the unreadable message.
diskutil for k20.04:
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *30.8 GB disk2
1: Apple_partition_map 4.1 KB disk2s1
2: Apple_HFS 4.1 MB disk2s2
So definitely something weird going on, despite it being bootable and
seemingly working as expected.
> The stick is bootable via restart + alt key. I wonder if the iso format has
> changed between kubuntu 20.04 and 21.04?
I thought they were always just iso9660. Google doesn't find anything
different.
> I seem to remember inspecting
> unreadable sticks in the past with diskutil and seeing fdisk formatted
> partitions on the stick which probably upset macOS although the stick was
> still bootable.
>
> As for creating it on Windows, maybe it depends on the tool you used and how
> it formats the installer stick?
I used rufus: https://rufus.ie/en/. I think it used MBR partitioning
scheme and FAT32.
Chris
Apr 27, 2021, 4:35:10 AM4/27/21
to
On 26/04/2021 09:27, Alan B wrote:
> Sorry I meant the actual contents of the .iso file might have been changed to
> make it more macOS compatible, e.g. Partition #2 EFI ESP's format and
> contents?
Checking with Windows - as it's the only thing that can see both sticks
- I see that the kubuntu 21 ISO simply has an 'efi' directory with a few
.efi files within it. The kubuntu 20 is the more usual linux folder and
file structure 'isolinux', 'grub', etc. It's odd - to me at least - that
the more usual one is the one that causes the error on the mac.
Anyway, I see that's not actually an error and I'll be aware of this in
future.
Thanks all!
> make it more macOS compatible, e.g. Partition #2 EFI ESP's format and
> contents?
Checking with Windows - as it's the only thing that can see both sticks
- I see that the kubuntu 21 ISO simply has an 'efi' directory with a few
.efi files within it. The kubuntu 20 is the more usual linux folder and
file structure 'isolinux', 'grub', etc. It's odd - to me at least - that
the more usual one is the one that causes the error on the mac.
Anyway, I see that's not actually an error and I'll be aware of this in
future.
Thanks all!
Theo
Apr 28, 2021, 5:47:52 AM4/28/21
to
that can be booted three ways:
ISO9660 with an El Torito partition suitable for booting from a CD/DVD
MBR format with a boot block suitable for booting on an older PC in BIOS
mode, or a newer PC with CSM (legacy BIOS) enabled
With an EFI partition suitable for booting on newer PCs in UEFI mode (like
Intel Macs)
In past times (eg Windows installers) you had to run a 'USB disc creator'
tool to convert an ISO with El Torito into a bootable USB image, which is
avoided by this careful construction. All this cunningness can trip up the
Mac, as you observed, as it can't read the parts intended for other booting
methods.
Theo
0 new messages