[SOLVED] I'm at a total loss, ISO will not go to USB

Sector11 · 2022-01-10 21:38:52

SOLVED: My OOPS!

Trying to burn the lithium ISO to a USB stick.

a17d0364d55352487f4d08d5dc1ad7f789931e911cb4cb2c82cb5255c1ed1d23
   $ sha256sum /media/10/ISOs/BL/lithium-3-amd64.hybrid.iso
a17d0364d55352487f4d08d5dc1ad7f789931e911cb4cb2c82cb5255c1ed1d23

YUP, it's good

dd if=<file> of=<device> bs=4M; sync

The USB stick was wiped and formatted Fat32 with gparted

 10 Jan 22 @ 18:31:19 ~
   $ sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11: 
lrwxrwxrwx 1 root root 9 Jan 10 18:15 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0 -> ../../sdb
 
 10 Jan 22 @ 18:34:48 /media/10/ISOs/BL
   $ dd if=lithium-3-amd64.hybrid.iso of=sdb bs=4M; sync
312+1 records in
312+1 records out
1309868032 bytes (1.3 GB, 1.2 GiB) copied, 8.39025 s, 156 MB/s
 
 10 Jan 22 @ 18:35:01 /media/10/ISOs/BL
   $

and the stick is empty!

cp lithium-3-amd64.hybrid.iso sdb

and the stick is empty!

Any help appreciated.

deleted0 · 2022-01-10 21:49:16

I think you need, of=/dev/sdb, as the path.

8bit

Sector11 · 2022-01-10 22:20:21

Did some checking and saw one sample with that so:

 10 Jan 22 @ 19:03:40 ~
   $ sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11: 
lrwxrwxrwx 1 root root 9 Jan 10 19:03 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0 -> ../../sdb
 
 10 Jan 22 @ 19:03:59 ~
   $ cd /media/10/ISOs/BL/
 
 10 Jan 22 @ 19:04:40 /media/10/ISOs/BL
   $ ls
lithium-3-amd64.hybrid.iso  lithium-3-amd64.hybrid.iso.sig  lithium-3.sha256sums.txt  sdb
 
 10 Jan 22 @ 19:04:45 /media/10/ISOs/BL
   $ dd if=lithium-3-amd64.hybrid.iso of=/dev/sdb bs=4M status=progress; sync
dd: failed to open '/dev/sdb': Permission denied
 
 10 Jan 22 @ 19:05:12 /media/10/ISOs/BL
   $ sudo dd if=lithium-3-amd64.hybrid.iso of=/dev/sdb bs=4M status=progress; sync
1207959552 bytes (1.2 GB, 1.1 GiB) copied, 7 s, 172 MB/s
312+1 records in
312+1 records out
1309868032 bytes (1.3 GB, 1.2 GiB) copied, 7.57966 s, 173 MB/s

Not good
Getting ready to toss the computer out a 2nd floor window.

PackRat · 2022-01-10 23:51:28

10 Jan 22 @ 19:04:40 /media/10/ISOs/BL
   $ ls
lithium-3-amd64.hybrid.iso  lithium-3-amd64.hybrid.iso.sig  lithium-3.sha256sums.txt  sdb

Why is sdb showing as a directory in they directory where you downloaded the ISOs?

You don't mount the thumb drive after formatting it fat32 in order to burn the iso with dd. Make sure it's not mounted.

Last edited by PackRat (2022-01-10 23:55:28)

Sector11 · 2022-01-10 23:55:43

OH!!! That sdb should not be there, deleted. but still the post above that,

PackRat · 2022-01-10 23:57:05

Getting ready to toss the computer out a 2nd floor window.

More likely the thumb drive may need to be tossed. How old is it? You have another, fairly new one, you can try?

Sector11 · 2022-01-11 00:07:57

No it's not old, I can copy files to is with thunar.

It had Siduction on it just the other day.

Sector11 · 2022-01-11 01:00:44

OK I have it. Do not know if it works but it's there.

/media/sector11/BUNSENLABS_LITHIUM/.disk
/media/sector11/BUNSENLABS_LITHIUM/boot
/media/sector11/BUNSENLABS_LITHIUM/debian
/media/sector11/BUNSENLABS_LITHIUM/dists
/media/sector11/BUNSENLABS_LITHIUM/EFI
/media/sector11/BUNSENLABS_LITHIUM/firmware
/media/sector11/BUNSENLABS_LITHIUM/install
/media/sector11/BUNSENLABS_LITHIUM/isolinux
/media/sector11/BUNSENLABS_LITHIUM/live
/media/sector11/BUNSENLABS_LITHIUM/pool
/media/sector11/BUNSENLABS_LITHIUM/tools
/media/sector11/BUNSENLABS_LITHIUM/autorun.inf
/media/sector11/BUNSENLABS_LITHIUM/bunsen_version
/media/sector11/BUNSENLABS_LITHIUM/efi.img
/media/sector11/BUNSENLABS_LITHIUM/g2ldr
/media/sector11/BUNSENLABS_LITHIUM/g2ldr.mbr
/media/sector11/BUNSENLABS_LITHIUM/md5sum.txt
/media/sector11/BUNSENLABS_LITHIUM/setup.exe
/media/sector11/BUNSENLABS_LITHIUM/win32-loader.ini

Needed to be root - I have never need to be root to burn an ISO.

 10 Jan 22 @ 21:31:40 ~
   $ cd /media/10/ISOs/BL/
 
 10 Jan 22 @ 21:31:54 /media/10/ISOs/BL
   $ ls
lithium-3-amd64.hybrid.iso	lithium-3.sha256sums.txt
lithium-3-amd64.hybrid.iso.sig
 
 10 Jan 22 @ 21:31:58 /media/10/ISOs/BL
   $ dd if=lithium-3-amd64.hybrid.iso of=/dev/sdb bs=4M status=progress; sync
dd: failed to open '/dev/sdb': Permission denied
 
 10 Jan 22 @ 21:32:14 /media/10/ISOs/BL
   $ sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11: 
lrwxrwxrwx 1 root root 9 Jan 10 21:31 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_4C532000030822116285-0:0 -> ../../sdb
 
 10 Jan 22 @ 21:32:30 /media/10/ISOs/BL
   $ dd if=lithium-3-amd64.hybrid.iso of=/dev/sdb bs=4M status=progress; sync
dd: failed to open '/dev/sdb': Permission denied
 
 10 Jan 22 @ 21:32:36 /media/10/ISOs/BL
   $ sudo su
root@debian:/media/10/ISOs/BL # dd if=lithium-3-amd64.hybrid.iso of=/dev/sdb bs=4M status=progress; sync                                      
312+1 records in
312+1 records out
1309868032 bytes (1.3 GB, 1.2 GiB) copied, 291.434 s, 4.5 MB/s
root@debian:/media/10/ISOs/BL #

johnraff · 2022-01-11 02:27:27

Sector11 wrote:

Needed to be root - I have never need to be root to burn an ISO.

I think that changed around Debian Stretch or so.

Sector11 · 2022-01-11 03:18:06

I still don't recall needing to be root with BL ...
{sigh}

Maybe it's my forgetter.

johnraff · 2022-01-11 07:08:11

I don't remember when it was, but I do remember suddenly needing to use sudo after an upgrade, quite a while ago.

unklar · 2022-01-11 09:06:57

Sector11 wrote:

The USB stick was wiped and formatted Fat32 with gparted

In principle, this is wrong.

The dd command destroys ALL data of the medium to which it is applied! So the FAT32 file system will be destroyed as well. That is why it is so dangerous and the user is always asked to look EXACTLY.

The dd command is used to write to a USB stick. With it one brings e.g. a hybrid ISO on the stick. Hybrid means, start ability.

ISO's have a RAW format, because of the data compression.
This format cannot be made visible with a file manager.
Only if I use the following procedure, I can see the content of the ISO with the file manager.

# mkdir /mnt/disk
# mount -o loop /media/S11/lithium-3-amd64.hybrid.iso /mnt/disk

leave

# umount /mnt/disk

Sector11 · 2022-01-11 12:28:15

johnraff wrote:

I don't remember when it was, but I do remember suddenly needing to use sudo after an upgrade, quite a while ago.

I did use sudo ... said it copied in 7.5 seconds .. but not there see earlier post, quoted for TLDR:

 10 Jan 22 @ 19:05:12 /media/10/ISOs/BL
   $ sudo dd if=lithium-3-amd64.hybrid.iso of=/dev/sdb bs=4M status=progress; sync
1207959552 bytes (1.2 GB, 1.1 GiB) copied, 7 s, 172 MB/s
312+1 records in
312+1 records out
1309868032 bytes (1.3 GB, 1.2 GiB) copied, 7.57966 s, 173 MB/s

OUCH: maybe it did:

 11 Jan 22 @ 09:26:21 ~
   $ c 173*7.57966
1311.28118

#1 2022-01-10 21:38:52

[SOLVED] I'm at a total loss, ISO will not go to USB

#2 2022-01-10 21:49:16

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#3 2022-01-10 22:20:21

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#4 2022-01-10 23:51:28

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#5 2022-01-10 23:55:43

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#6 2022-01-10 23:57:05

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#7 2022-01-11 00:07:57

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#8 2022-01-11 01:00:44

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#9 2022-01-11 02:27:27

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#10 2022-01-11 03:18:06

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#11 2022-01-11 07:08:11

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#12 2022-01-11 09:06:57

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

#13 2022-01-11 12:28:15

Re: [SOLVED] I'm at a total loss, ISO will not go to USB

Board footer