[ABANDON] My experiences writing an ISO to USB stick -- Help!

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
User avatar
austin.texas
Level 20
Level 20
Posts: 12003
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: My experiences writing an ISO to USB stick -- Help!

Post by austin.texas »

Give MultiSystem a try. It works great for me.
viewtopic.php?f=46&t=233094&start=40#p1238337

The only thing is that once you have created your Mint 18 USB drive with dd or with mintstick, you have a ISO9660 filesystem, which can prevent you from using the flash drive for other things. I know from experience that sometimes you need to clean up the first 64 sectors of the disk. You can't delete it by deleting partitions. You can delete all of your partitions, and it will still be there.
You can fix that with the dd command.
You can erase the boot area (including the partition table) by zeroing out the first 1MB of the drive, so that you have a fresh start.

Code: Select all

sudo dd if=/dev/zero of=/dev/sdb bs=1M count=10
That will destroy the partition table, as I mentioned. Gparted is the easiest way to create a new one - in spite of the fact that you are reticent to use Gparted... This is a flash drive anyway, not your hard drive.
Open GParted and locate the USB drive using the drop-down menu at the top right.
Unmount the USB drive - right click > Unmount
Create a new partition table: Device menu > Create Partition Table > msdos > APPLY
Close GParted.
Now you have a clean USB drive ready for MultiSystem to use.
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

There's also this: 'https://en.wikipedia.org/wiki/Unified_E ... _Interface' about UEFI. SMM is actually an extension to the I386 architecture and op codes. I've coded using SMM instructions ... So... THAT'S UEFI, eh? Now I understand, and yes AscLinux, I guess I do have EFI. My apologies for questioning it, but you see, the 'BIOS' (EFI actually) doesn't mention it, and its description in "USB Legacy" doesn't sound like EFI.
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

austin.texas wrote:Give MultiSystem a try. ... Gparted is the easiest way to create a new one - in spite of the fact that you are reticent to use Gparted... This is a flash drive anyway, not your hard drive.
Open GParted and locate the USB drive using the drop-down menu at the top right.
Unmount the USB drive - right click > Unmount
Create a new partition table: Device menu > Create Partition Table > msdos > APPLY
Close GParted.
Now you have a clean USB drive ready for MultiSystem to use.
Okay, you bet. If this works, I'm going to fly down there and buy you a beer. :o
User avatar
slipstick
Level 6
Level 6
Posts: 1071
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: My experiences writing an ISO to USB stick -- Help!

Post by slipstick »

This may be of interest to some - the latest (well, the latest available in the US) issue of Linux Format magazine, LX217, Nov. 2016, has an article:"Grub: Boot ISO's from USB" - describes how to put multiple ISO's on a single USB stick. I haven't had time to read the article yet, but there is a lot of command line stuff in there. I would think that issue is probablly still available at places like Barnes and Noble.
In theory, theory and practice are the same. In practice, they ain't.
User avatar
austin.texas
Level 20
Level 20
Posts: 12003
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: My experiences writing an ISO to USB stick -- Help!

Post by austin.texas »

slipstick wrote:This may be of interest to some - the latest (well, the latest available in the US) issue of Linux Format magazine, LX217, Nov. 2016, has an article:"Grub: Boot ISO's from USB" - describes how to put multiple ISO's on a single USB stick. I haven't had time to read the article yet, but there is a lot of command line stuff in there. I would think that issue is probablly still available at places like Barnes and Noble.
I wrote a tutorial on how to do that, a couple of years ago. :arrow:
https://community.linuxmint.com/tutorial/view/1846

It can get complicated. MultiSystem is easier.
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

Lots of errors, Austin

Code: Select all

#!/bin/bash
apt-add-repository 'deb http://liveusb.info/multisystem/depot all main'
wget -q -O - http://liveusb.info/multisystem/depot/multisystem.asc | sudo apt-key add -
apt-get update
apt-get install multisystem

Code: Select all

mark-Lenovo-V570 mark # ./install_multisystem.bash
No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
OK
Ign:1 http://packages.linuxmint.com sarah InRelease
Hit:2 http://packages.linuxmint.com sarah Release                                                                                                                       
Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]                                                                                             
Hit:5 http://archive.canonical.com/ubuntu xenial InRelease                                                         
Ign:6 http://liveusb.info/multisystem/depot all InRelease                                                               
Get:7 http://liveusb.info/multisystem/depot all Release [4,637 B]                                                       
Get:8 http://liveusb.info/multisystem/depot all Release.gpg [473 B]                                     
Get:9 http://liveusb.info/multisystem/depot all/main amd64 Packages [1,257 B]
Get:10 http://liveusb.info/multisystem/depot all/main i386 Packages [1,261 B]                      
Err:11 http://mirror.cs.pitt.edu/ubuntu/archive xenial InRelease                                                                                                        
  Could not connect to mirror.cs.pitt.edu:80 (136.142.23.206), connection timed out
Err:12 http://mirror.cs.pitt.edu/ubuntu/archive xenial-updates InRelease
  Unable to connect to mirror.cs.pitt.edu:http:
Err:13 http://mirror.cs.pitt.edu/ubuntu/archive xenial-backports InRelease
  Unable to connect to mirror.cs.pitt.edu:http:
Fetched 102 kB in 2min 0s (843 B/s)
Reading package lists... Done
W: http://liveusb.info/multisystem/depot/dists/all/Release.gpg: Signature by key 32027DE3D67157C45E69C0AE4E940D7FDD7FB8CC uses weak digest algorithm (SHA1)
W: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/dists/xenial/InRelease  Could not connect to mirror.cs.pitt.edu:80 (136.142.23.206), connection timed out
W: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/dists/xenial-updates/InRelease  Unable to connect to mirror.cs.pitt.edu:http:
W: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/dists/xenial-backports/InRelease  Unable to connect to mirror.cs.pitt.edu:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  gstreamer0.10-ffmpeg libhal1-flash libunshield0 unshield xplayer-plugins-extra
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  fatresize gtkdialog ipxe-qemu libaio1 libboost-random1.58.0 libboost-thread1.58.0 libcacard0 libfdt1 libiscsi2 librados2 librbd1 libspice-server1 libusbredirparser1
  libutempter0 libxdo3 libxen-4.6 libxenstore3.0 qemu qemu-block-extra qemu-kvm qemu-slof qemu-system qemu-system-arm qemu-system-common qemu-system-mips
  qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-utils seabios squashfs-tools xdotool xterm
Suggested packages:
  qemu-user-static samba vde2 openbios-ppc openhackware sgabios ovmf debootstrap xfonts-cyrillic
Recommended packages:
  cpu-checker qemu-user-binfmt sharutils
The following NEW packages will be installed:
  fatresize gtkdialog ipxe-qemu libaio1 libboost-random1.58.0 libboost-thread1.58.0 libcacard0 libfdt1 libiscsi2 librados2 librbd1 libspice-server1 libusbredirparser1
  libutempter0 libxdo3 libxen-4.6 libxenstore3.0 multisystem qemu qemu-block-extra qemu-kvm qemu-slof qemu-system qemu-system-arm qemu-system-common qemu-system-mips
  qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-utils seabios squashfs-tools xdotool xterm
0 upgraded, 36 newly installed, 0 to remove and 71 not upgraded.
Need to get 46.6 MB of archives.
After this operation, 268 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-block-extra amd64 1:2.5+dfsg-5ubuntu10.6 [32.8 kB]
Get:2 http://liveusb.info/multisystem/depot all/main amd64 gtkdialog amd64 2:0.8.3-2 [95.5 kB]                            
Get:3 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system-common amd64 1:2.5+dfsg-5ubuntu10.6 [281 kB]
Get:4 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system-arm amd64 1:2.5+dfsg-5ubuntu10.6 [4,120 kB]       
Get:5 http://liveusb.info/multisystem/depot all/main amd64 multisystem all 1.0365 [8,873 kB]                      
Get:6 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system-mips amd64 1:2.5+dfsg-5ubuntu10.6 [3,343 kB]                                             
Get:7 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system-ppc amd64 1:2.5+dfsg-5ubuntu10.6 [5,712 kB]                                              
Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system-sparc amd64 1:2.5+dfsg-5ubuntu10.6 [1,977 kB]                                            
Get:9 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system-x86 amd64 1:2.5+dfsg-5ubuntu10.6 [2,758 kB]                                              
Get:10 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system-misc amd64 1:2.5+dfsg-5ubuntu10.6 [6,164 kB]                                            
Get:11 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-system amd64 1:2.5+dfsg-5ubuntu10.6 [6,130 B]                                                  
Get:12 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 qemu-user amd64 1:2.5+dfsg-5ubuntu10.6 [6,201 kB]                                               
Get:13 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-utils amd64 1:2.5+dfsg-5ubuntu10.6 [578 kB]                                                    
Get:14 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 qemu amd64 1:2.5+dfsg-5ubuntu10.6 [83.0 kB]                                                     
Get:15 http://security.ubuntu.com/ubuntu xenial-security/main amd64 qemu-kvm amd64 1:2.5+dfsg-5ubuntu10.6 [7,168 B]                                                     
Err:16 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 libiscsi2 amd64 1.12.0-2                                                                              
  Could not connect to mirror.cs.pitt.edu:80 (136.142.23.206), connection timed out
Err:17 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 squashfs-tools amd64 1:4.3-3ubuntu2                                                                   
  Unable to connect to mirror.cs.pitt.edu:http:
Err:18 http://mirror.cs.pitt.edu/ubuntu/archive xenial/universe amd64 fatresize amd64 1.0.2-9                                                                           
  Unable to connect to mirror.cs.pitt.edu:http:
Err:19 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 libutempter0 amd64 1.1.6-3                                                                            
  Unable to connect to mirror.cs.pitt.edu:http:
Err:20 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 xterm amd64 322-1ubuntu1                                                                              
  Unable to connect to mirror.cs.pitt.edu:http:
Err:21 http://mirror.cs.pitt.edu/ubuntu/archive xenial/universe amd64 libxdo3 amd64 1:3.20150503.1-2                                                                    
  Unable to connect to mirror.cs.pitt.edu:http:
Err:22 http://mirror.cs.pitt.edu/ubuntu/archive xenial/universe amd64 xdotool amd64 1:3.20150503.1-2                                                                    
  Unable to connect to mirror.cs.pitt.edu:http:
Err:23 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 libaio1 amd64 0.3.110-2                                                                               
  Unable to connect to mirror.cs.pitt.edu:http:
Err:24 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 libcacard0 amd64 1:2.5.0-2                                                                            
  Unable to connect to mirror.cs.pitt.edu:http:
Err:25 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 libfdt1 amd64 1.4.0+dfsg-2                                                                            
  Unable to connect to mirror.cs.pitt.edu:http:
Err:26 http://security.ubuntu.com/ubuntu xenial-security/main amd64 libspice-server1 amd64 0.12.6-4ubuntu0.1                                                            
  Unable to connect to mirror.cs.pitt.edu:http:
Err:27 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main amd64 libusbredirparser1 amd64 0.7.1-1                                                                      
  Unable to connect to mirror.cs.pitt.edu:http:
Ign:28 http://security.ubuntu.com/ubuntu xenial-security/main amd64 libxenstore3.0 amd64 4.6.0-1ubuntu4.2                                                               
Ign:29 http://security.ubuntu.com/ubuntu xenial-security/main amd64 libxen-4.6 amd64 4.6.0-1ubuntu4.2                                                                   
Err:30 http://mirror.cs.pitt.edu/ubuntu/archive xenial-updates/main amd64 libboost-random1.58.0 amd64 1.58.0+dfsg-5ubuntu3.1                                            
  Unable to connect to mirror.cs.pitt.edu:http:
Err:31 http://mirror.cs.pitt.edu/ubuntu/archive xenial-updates/main amd64 libboost-thread1.58.0 amd64 1.58.0+dfsg-5ubuntu3.1                                            
  Unable to connect to mirror.cs.pitt.edu:http:
Err:32 http://mirror.cs.pitt.edu/ubuntu/archive xenial-updates/main amd64 librados2 amd64 10.2.2-0ubuntu0.16.04.2                                                       
  Unable to connect to mirror.cs.pitt.edu:http:
Err:33 http://mirror.cs.pitt.edu/ubuntu/archive xenial-updates/main amd64 librbd1 amd64 10.2.2-0ubuntu0.16.04.2                                                         
  Unable to connect to mirror.cs.pitt.edu:http:
Ign:34 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main i386 qemu-slof all 20151103+dfsg-1ubuntu1                                                                   
Ign:35 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main i386 seabios all 1.8.2-1ubuntu1                                                                             
Ign:36 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main i386 ipxe-qemu all 1.0.0+git-20150424.a25a16d-1ubuntu1                                                      
Err:34 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main i386 qemu-slof all 20151103+dfsg-1ubuntu1                                                                   
  Unable to connect to mirror.cs.pitt.edu:http:
Err:35 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main i386 seabios all 1.8.2-1ubuntu1                                                                             
  Unable to connect to mirror.cs.pitt.edu:http:
Err:36 http://mirror.cs.pitt.edu/ubuntu/archive xenial/main i386 ipxe-qemu all 1.0.0+git-20150424.a25a16d-1ubuntu1                                                      
  Unable to connect to mirror.cs.pitt.edu:http:
Get:26 http://security.ubuntu.com/ubuntu xenial-security/main amd64 libspice-server1 amd64 0.12.6-4ubuntu0.1 [338 kB]                                                   
Get:28 http://security.ubuntu.com/ubuntu xenial-security/main amd64 libxenstore3.0 amd64 4.6.0-1ubuntu4.2 [19.7 kB]                                                     
Get:29 http://security.ubuntu.com/ubuntu xenial-security/main amd64 libxen-4.6 amd64 4.6.0-1ubuntu4.2 [345 kB]                                                          
Fetched 40.9 MB in 2min 29s (273 kB/s)                                                                                                                                  
E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/libi/libiscsi/libiscsi2_1.12.0-2_amd64.deb  Could not connect to mirror.cs.pitt.edu:80 (136.142.23.206), connection timed out

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/s/squashfs-tools/squashfs-tools_4.3-3ubuntu2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/universe/f/fatresize/fatresize_1.0.2-9_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/libu/libutempter/libutempter0_1.1.6-3_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/x/xterm/xterm_322-1ubuntu1_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/universe/x/xdotool/libxdo3_3.20150503.1-2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/universe/x/xdotool/xdotool_3.20150503.1-2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/liba/libaio/libaio1_0.3.110-2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/libc/libcacard/libcacard0_2.5.0-2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/d/device-tree-compiler/libfdt1_1.4.0+dfsg-2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/u/usbredir/libusbredirparser1_0.7.1-1_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/b/boost1.58/libboost-random1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/b/boost1.58/libboost-thread1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/c/ceph/librados2_10.2.2-0ubuntu0.16.04.2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/c/ceph/librbd1_10.2.2-0ubuntu0.16.04.2_amd64.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/s/slof/qemu-slof_20151103+dfsg-1ubuntu1_all.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/s/seabios/seabios_1.8.2-1ubuntu1_all.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Failed to fetch http://mirror.cs.pitt.edu/ubuntu/archive/pool/main/i/ipxe/ipxe-qemu_1.0.0+git-20150424.a25a16d-1ubuntu1_all.deb  Unable to connect to mirror.cs.pitt.edu:http:

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
mark-Lenovo-V570 mark # 
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

I took the 'sudo' off of the end of the pipe -- didn't see it before. Ran it. Same result.

PS: Correction. Similar result -- all the 'Failed to fetch' statements at the end are the same.
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

austin.texas wrote: ... You can erase the boot area (including the partition table) by zeroing out the first 1MB of the drive, so that you have a fresh start.

Code: Select all

sudo dd if=/dev/zero of=/dev/sdb bs=1M count=10

Code: Select all

mark-Lenovo-V570 mark # dd if=/dev/zero of=/dev/sdb bs=1M count=10
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.0121764 s, 861 MB/s
mark-Lenovo-V570 mark # 
That will destroy the partition table, as I mentioned. Gparted is the easiest way to create a new one - in spite of the fact that you are reticent to use Gparted... This is a flash drive anyway, not your hard drive.
Open GParted and locate the USB drive using the drop-down menu at the top right.
Unmount the USB drive - right click > Unmount
It was no longer mounted !?!?!?!?!?!?!
Create a new partition table: Device menu > Create Partition Table > msdos > APPLY
I immediately got this from 'gparted'
Libparted Error wrote:Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

I rebooted, lauched 'gparted', and created the 'msdos' partition table, this time without complaint.

Now what? How can I finish getting MultiSystem?
User avatar
austin.texas
Level 20
Level 20
Posts: 12003
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: My experiences writing an ISO to USB stick -- Help!

Post by austin.texas »

You posted that you ran sudo apt-get install multisystem
Is it not in your Menu under Accessories?
If not, post the result of

Code: Select all

apt-cache policy multisystem
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

austin.texas wrote:You posted that you ran sudo apt-get install multisystem
Is it not in your Menu under Accessories?
If not, post the result of

Code: Select all

apt-cache policy multisystem
Hi Austin. Still up, eh?

I successfully installed 'multisystem' after I changed 'Software Sources' in 'Mint Update'. I figured that out all by myself! I'm learning (my head is expanding by the minute :) ).

Then I discovered I had to manually format the USB stick. I used 'mintstick' to format it fat32 file system. I just ran 'multisystem' and got this: "Erreur: MultiSystem n'accepte pas les espaces dans les label de disques." I'm pretty sure that says that spaces in the volume label is not acceptable -- it turns out that 'mintstick' automatically labeled the USB stick "USB Stick". I'm currently trying to figure this out:

Code: Select all

mark-Lenovo-V570 mark # mlabel /dev/sdb1
Mtools version 4.0.18, dated January 9th, 2013
Usage: mlabel [-vscVn] [-N serial] drive:
mark-Lenovo-V570 mark # 
I looked at the man page and it doesn't say what option '-vscVn' means.

Code: Select all

mlabel(1)                   General Commands Manual                  mlabel(1)

Name
       mlabel - make an MSDOS volume label

Note of warning
       This  manpage  has  been  automatically generated from mtools's texinfo
       documentation, and may not be entirely accurate or complete.   See  the
       end of this man page for details.

Description
       The mlabel command adds a volume label to a disk. Its syntax is:
       mlabel [-vcsn] [-N serial] drive:[new_label]

       Mlabel  displays  the current volume label, if present. If new_label is
       not given, and if neither the c nor the s options are set,  it  prompts
       the  user  for a new volume label.  To delete an existing volume label,
       press return at the prompt.

       The label is limited to 11 single-byte characters, e.g. Name1234567.

       Reasonable care is taken to create a valid MS-DOS volume label.  If  an
       invalid  label is specified, mlabel changes the label (and displays the
       new label if the verbose mode is set). Mlabel returns 0 on success or 1
       on failure.

       Mlabel supports the following options:

       c      Clears an existing label, without prompting the user

       s      Shows the existing label, without prompting the user.

       n      Assigns a new (random) serial number to the disk

       N serial
              Sets  the  supplied  serial  number. The serial number should be
              supplied as an 8 digit hexadecimal number, without spaces
Do you have any ideas? -- I assume that 'drive:' should be 'drive:USB_Stick', but I don't really know that, either. I'd try 'mlabel /dev/sdb1 drive:USB_Stick' but I'm a bit gun shy after so much struggle -- I don't want to screw up and trash my embedded hard disk.
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

I've tried these

Code: Select all

mark-Lenovo-V570 mark # mlabel -s /dev/sdb1
Mtools version 4.0.18, dated January 9th, 2013
Usage: mlabel [-vscVn] [-N serial] drive:
mark-Lenovo-V570 mark # mlabel -s drive:/dev/sdb1
Mtools version 4.0.18, dated January 9th, 2013
Usage: mlabel [-vscVn] [-N serial] drive:
mark-Lenovo-V570 mark # mlabel -s /dev/sdb1
Mtools version 4.0.18, dated January 9th, 2013
Usage: mlabel [-vscVn] [-N serial] drive:
mark-Lenovo-V570 mark # mlabel /dev/sdb1 -s
Mtools version 4.0.18, dated January 9th, 2013
Usage: mlabel [-vscVn] [-N serial] drive:
mark-Lenovo-V570 mark # mlabel /dev/sdb1
Mtools version 4.0.18, dated January 9th, 2013
Usage: mlabel [-vscVn] [-N serial] drive:
mark-Lenovo-V570 mark # 
I don't know how to run 'mlabel'. I tried '-s' because it's probably non-destructive.
User avatar
austin.texas
Level 20
Level 20
Posts: 12003
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: My experiences writing an ISO to USB stick -- Help!

Post by austin.texas »

Code: Select all

sudo tune2fs -L multisystem /dev/sdb1
Then, to check it:

Code: Select all

lsblk -f
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

austin.texas wrote:

Code: Select all

sudo tune2fs -L multisystem /dev/sdb1
Then, to check it:

Code: Select all

lsblk -f

Code: Select all

mark-Lenovo-V570 mark # tune2fs -L multisystem /dev/sdb1
tune2fs 1.42.13 (17-May-2015)
tune2fs: Bad magic number in super-block while trying to open /dev/sdb1
Couldn't find valid filesystem superblock.
mark-Lenovo-V570 mark # 
This is quite the all-day sucker, eh?
User avatar
austin.texas
Level 20
Level 20
Posts: 12003
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: My experiences writing an ISO to USB stick -- Help!

Post by austin.texas »

What is the result of

Code: Select all

lsblk -f
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

austin.texas wrote:What is the result of

Code: Select all

lsblk -f

Code: Select all

mark-Lenovo-V570 mark # lsblk -f
NAME                FSTYPE      LABEL     UUID                                   MOUNTPOINT
sda                                                                              
├─sda1              vfat                  28C3-6073                              /boot/efi
├─sda2              ext2                  0d0ef13c-228d-4fcb-a65a-a6c7f3d50924   /boot
└─sda3              LVM2_member           pPm7IY-YCw2-YR0j-Qisa-kR1D-PonV-IW3Wdp 
  ├─mint--vg-root   ext4                  bbc20518-3767-4011-9b5b-5eaf72fc426e   /
  └─mint--vg-swap_1 swap                  08536d11-38b9-46db-8f76-c0bd95cf05a6   [SWAP]
sdb                                                                              
└─sdb1              vfat        USB Stick 829D-8363                              /media/mark/USB Stick
sr0                                                                              
mark-Lenovo-V570 mark # 
I couldn't discover the way to run 'mlabel' (see above 'viewtopic.php?f=46&t=233094&p=1238612#p1238600' & 'viewtopic.php?f=46&t=233094&p=1238612#p1238603').
User avatar
austin.texas
Level 20
Level 20
Posts: 12003
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: My experiences writing an ISO to USB stick -- Help!

Post by austin.texas »

You were right in using mtools.
First, run this command:

Code: Select all

sudo echo mtools_skip_check=1 >> ~/.mtoolsrc
Then:

Code: Select all

sudo mlabel -i /dev/sdb1 ::multisystem
Then post the result of

Code: Select all

lsblk -f
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
markfilipak
Level 6
Level 6
Posts: 1174
Joined: Sun Mar 10, 2013 8:08 pm
Location: Mansfield, Ohio

Re: My experiences writing an ISO to USB stick -- Help!

Post by markfilipak »

I discovered I could change the USB stick's label with 'gparted', so I did. 'multisystem' then ran, I selected the Mint 18 ISO and set the application off (can't remember what the button said), a terminal-style window opened (sudo), I put in my password and something about missing operand flashed and it closed.

This is all too much. I'm giving up. Sorry to take up so much of your time, Austin. Thanks, and best wishes to you, but I just can't take it any more.
Locked

Return to “Installation & Boot”