Ubuntu Forums Archive Viewer

Howto make USB boot drives

Archived thread 1958073 from Tutorials. Markdown source: Tutorials/thread_1958073_Howto_make_USB_boot_drives.md

Original URL About this archive
#1

[SIZE=5]This thread follows the development of the tool mkusb[/SIZE]

  • You get an overview in this first post.
  • You can skip to the end of the thread to read about current problems, tweaks and solutions.

[SIZE=4]There are two improvements in mkusb version 12.5.6 [/SIZE]

  • [FONT=Courier New]mkusb-tow[/FONT] 'TO Windows' is a new tool to make a Windows installer boot drive ported from mkusb-plug to mkusb-dus. It works well with most current Windows iso files, including those with a file, install.wim, that expands to more than 4 GiB. So two partitions are created, one with FAT32 to boot from and one with NTFS where the main content of the iso file is extracted. The old mkusb method, that works well in 32-bit systems (but not when install.wim exceeds 4 GiB) is still available.
  • When running in an installed system booted in UEFI mode mkusb-dus selects method silently for persistent live drives. This is made because it is nowadays common to run Ubuntu in this way, and we still want to make drives that boot both in UEFI mode and BIOS mode. Earlier there were warnings, that compressed files were extracted instead of running commands because the grub tool to create a BIOS bootloader (grub-pc) is not compatible with grub for UEFI (grub-efi).

[SIZE=4]You may notice some improvements in mkusb version 12.5.7 [/SIZE]

  • Sparky Linux is recognized as a working host operating system by mkusb (alongside Ubuntu and the Ubuntu family flavours and Debian).
  • [FONT=Courier New]watch-flush[/FONT] is imported from mkusb-plug to mkusb-dus in order to show what is happening while the system i flushing the buffers (during writing to a USB drive or memory card).

The programs [FONT=Courier New]watch-flush[/FONT] and [FONT=Courier New]mkusb-tow[/FONT] are moved from the mkusb-plug package to the mkusb-common package. This may cause a hiccup when upgrading from a previous version. You can fix it with the following commands


sudo apt update
**sudo apt -f install**        # this is the crucial command line with -f, --fix-broken
sudo apt install mkusb

[COLOR="#606060"]Please notice that you need other commands when you want to install mkusb the first time:

sudo add-apt-repository universe  # this line only for standard Ubuntu live
sudo add-apt-repository ppa:mkusb/ppa          # stable PPA for regular usage
# sudo add-apt-repository ppa:mkusb/unstable   # PPA for development and testing; remove the # in front of the command to use it
sudo apt update
sudo apt install mkusb

sudo apt install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

[/COLOR] [SIZE=4]mkusb-plug is a new and very reliable tool to create a USB boot drive[/SIZE]

When you intend to create a USB boot drive, you should use a tool that is as reliable as possible. It should help you identify the target drive (avoid overwriting data in another drive) and it should create a working bootable drive.

  • Standard mkusb version 12 alias mkusb-dus has served us well for years, and is still the main 'mkusb choice' for the current versions of Ubuntu (and the community flavours Kubuntu, Lubuntu ... Xubuntu) including 18.04.x LTS.
  • Now there is a new version, mkusb-plug, that is even safer. It can create 'plain' cloned USB boot drives of most Linux distros, and also persistent live drives of Ubuntu 19.10 and newer versions. It uses a plug-in method to make the identification of the target drive very safe, and you are welcome to start using it.

With version 2.4.1, now upgraded to version 2.4.4, there is a desktop file 'mkusb-plug.desktop', so you can start mkusb-plug

  • like any other graphical program
  • but also from a terminal window according to the help text

 $ mkusb-plug -h
 Tool to create boot drive, typically a live USB drive
 Usage:    mkusb-plug [source file]
 Examples:
           mkusb-plug linux.iso           # make live drive
           mkusb-plug linux.img           # clone image file
           mkusb-plug ubuntu-19.10+.iso   # make persistent live
           mkusb-plug debian-10+.iso      # make persistent live
           mkusb-plug -v                  # version
           mkusb-plug -h                  # help

The terminal window will serve as console for the program.

'Like any other graphical program' means

  • via the menu or other way to access programs graphical desktop programs (depending on the desktop environment)

. select 'Open with ...' . expand 'System Tools' and select mkusb-plug

  • via right-clicking on an iso file
  • The next time you can expect the desktop environment to remember your choice, so that it will be easier to select mkusb-plug.

**Read more and install mkusb-plug from this link**

[hr][/hr] [SIZE=5]Quick start manual and mkusb[/SIZE] [IMG]https://help.ubuntu.com/community/mkusb/artwork?action=AttachFile&do=get&target=mkusb24.png[/IMG]

The fastest way to start making USB boot drives is to install the *mkusb PPA*, install and update the mkusb package like all the other program packages. See this link https://launchpad.net/~mkusb/+archive/ubuntu/ppa

If you run standard Ubuntu live, you need an extra instruction to get the repository Universe. (Kubuntu, Lubuntu ... Xubuntu have the repository Universe activated automatically.)

Text after the # character is not used by the shell interpreter, it is a comment for the human eye.

sudo add-apt-repository universe  # this line only for standard Ubuntu live
sudo add-apt-repository ppa:mkusb/ppa          # stable PPA for regular usage
# sudo add-apt-repository ppa:mkusb/unstable   # PPA for development and testing; remove the # in front of the command to use it
sudo apt update
sudo apt install mkusb

sudo apt install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You can download the quick start manual(s) at this link http://phillw.net/isos/linux-tools/mkusb/

[[img]https://help.ubuntu.com/community/mkusb/pictures?action=AttachFile&do=get&target=16-mkusb-quick-start-manual.png[/img]](http://phillw.net/isos/linux-tools/mkusb/mkUSB-quick-start-manual-11.pdf) [[img]https://help.ubuntu.com/community/mkusb?action=AttachFile&do=get&target=mkusb-quick-start-manual-22.png[/img]](http://phillw.net/isos/linux-tools/mkusb/mkUSB-quick-start-manual-22.pdf)

*Alternative:* You find alternate links at Quick start (if http://phillw.net/isos/linux-tools/mkusb/ is temporarity down).

If you want to try the current version of *mkusb*, get it via the PPA.

There are more details (text and screenshot pictures) at the wiki page https://help.ubuntu.com/community/mkusb

[SIZE=4]Warning about overwriting the target device[/SIZE]

mkusb will 'use the whole device', actually only the head end (size of the iso file), but the rest of the device is not available. mkusb simply clones the ISO 9660 file system with its content from the iso file. This ISO 9660 file system works from CD/DVD disks, and also from USB drives. After using a USB pendrive like this, you make a new partition table and file system, if you want to use it for another purpose.

[SIZE=4]Help selecting the correct target device[/SIZE]

The crucial task of mkusb was and is to help selecting the correct device and avoid overwriting other devices.

[HR][/HR] [SIZE=4]Doing the same thing many times[/SIZE]

For the first time I had been helping to test a new Ubuntu version (Lubuntu 12.04 LTS). After a while I wanted to make itsimpler and safer to transfer the code to the USB pendrive. I have been happy using [FONT=courier new]unetbootin[/FONT], because of its high success rate. I also tested Ubuntu's startup disk creator [FONT=courier new]usb-creator-gtk[/FONT], which has the advantage that you reach Ubuntu's first screen, that is skipped by unetbootin. Both tools work with my computers and can be used to create persistent live systems.

[HR][/HR] [SIZE=4]dd image of iso file to USB device safely[/SIZE]

But I also read somewhere that it should be possible to boot from a direct image of the iso file. So I tried it with [SIZE=3][FONT=courier new]dd[/FONT][/SIZE], the disk destroyer ;-) And it works, the computer boots from a USB device (pendrive, stick, flash drive, but also disk or SSD) just like it were from a CD drive. Also like a CD, it will be mounted read-only, so it cannot carry persistence.

Since [SIZE=3][FONT=courier new]dd[/FONT][/SIZE] is a bit risky, I made a shell-script, so that you get advice from a help text window and have to run dd manually only once, but with support from the script to avoid writing to any internal drive. The first time you must select the correct USB device, if more than one are connected. So it is safer and also much more convenient (but not 100%).

The next daily build will automatically select the correct USB device (when it is inserted into the computer). So for the next daily builds it is safe and very convenient.

I cloned an [FONT=courier new]ubuntu-desktop-amd64.iso[/FONT] this way, and the USB pendrive works in both UEFI and CSM (BIOS) modes.

[SIZE=4]Shell script[/SIZE]

The shell-script has been updated and improved and will be updated again when necessary. It is now convenient to use also for one-off creations of USB boot devices from iso files and compressed image files and also to wipe the drives if necessary after the cloning. The shellscript can monitor the data transfer with [FONT=courier new]pv[/FONT], and suggests that you install it, if not available. Notice that pv shows Mibibytes and dd shows Megabytes.

*Here is the shell-script for anyone to use or improve.*

Download [FONT=courier new]mkusb[/FONT] from the following link

http://phillw.net/isos/linux-tools/mkusb [URL="http://phillw.net/isos/one-button-installer/scripts/"] [/URL]There are also previous versions for users that like simple scripts.

Use the current [FONT=courier new]md5sum.txt.asc[/FONT] file to check that the md5sum matches before you start using mkusb!

Verify that this signed md5sum file is correct with the following commands


[COLOR=#0000ff]gpg --keyserver hkp://pgp.mit.edu --recv-keys EB0FC2C8
gpg --verify md5sum.txt.asc
[/COLOR]

The output should be something like


[COLOR=#0000ff]gpg --keyserver hkp://pgp.mit.edu --recv-keys EB0FC2C8[/COLOR]
... 
gpg: key EB0FC2C8: public key "Nio Sudden Wiklund (sudodus) <address@mailserver.com>" imported (or not changed the second time ...)
...
[COLOR=#0000ff]gpg --verify md5sum.txt.asc[/COLOR]
gpg: Signature made Sat Aug  2 12:09:06 2014 CEST using RSA key ID EB0FC2C8
gpg: Good signature from "Nio Sudden Wiklund (sudodus) <mail address>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 0303 EA77 E34C 52F2 2958  47C6 BD43 C742 EB0F C2C8

The warning "This key is not certified with a trusted signature! There is no indication that the signature belongs to the owner." means that there is no chain of trusted keys between your computer's keyring and the key, that was used to sign the md5sums (the key of sudodus). Check that the result matches, when you verify it: The md5sums and the signature of your output of these commands should match. Then there is reason to trust that nobody else has written the mkusb script file and its md5sum. The date of the signature will change at updates, and the text might be translated to your local language, but it should be clear that it is a

'Good signature from "Nio Sudden Wiklund (sudodus)"'.

[hr][/hr] [SIZE=4]mkusb-nox[/SIZE]

*mkusb-nox* is supplied via the PPA. It works in text screens, 'No X', and can do 'everything' that mkusb version 9 can do (but without eye candy). The improved recognition of operating systems in iso files and devices is ported is ported from version 9.

https://help.ubuntu.com/community/mkusb/v7

sudo add-apt-repository ppa:mkusb/ppa  # and press Enter to accept it
sudo apt-get update
sudo apt-get install mkusb-nox

[SIZE=4]mkusb-bas[/SIZE]

A very basic version of mkusb is made for old and/or very small operating systems (suitable for very old computers and as portable systems). *mkusb-bas* is tweaked to run in TinyCore and Wary Puppy. See this link

mkusb version 7.4.x - mkusb-bas

[SIZE=4]mkusb minimal shellscript - mkusb-min[/SIZE]

*mkusb-min* is simple, the shellscript is very small compared to the other versions, yet it serves the purpose to wrap a safety belt around 'dd'.

Small and flexible

  • *mkusb-min* needs no extra packages (but makes the user experience nicer, if you install pv). It runs in text screens, terminal windows, via ssh and other network connections.
  • *mkusb-min* works in many different linux distros. It needs bash, some standard tools and features, that are present in almost all current linux distros (2017).

There are more details, for example how to download *mkusb-min* and how to use it, at the following link,

help.ubuntu.com/community/mkusb/min

[hr][/hr] [SIZE=4]Wipe the CD file system[/SIZE]

I should add, that if you want to re-use a USB drive that has been used like this, you should wipe it with dd (overwrite with zeros), otherwise grub-install doesn't want to write into the mbr area, because it recognizes the CD file system, iso9660. (You need *not* wipe it before cloning.)

You can use the shell-script also for this task and wipe the whole drive, 'wipe-whole-device', but often it is enough to wipe the first megabyte of the drive, 'wipe-1'.

$ [COLOR=#0000ff]sudo -H mkusb wipe[/COLOR]

It is *very important* that you wipe your intended target drive and nothing else. It will be completely wiped, not even PhotoRec can do anything after that operation. But there are other (and better) tools to wipe an entire HDD or SSD for example *hdparm* or *DBAN*.

And after that you can use *gparted* to make a new partition table (for example MBR) and suitable partition(s) for example FAT32 with boot and lba flags.

[SIZE=4]mkusb 10.2 introduces a 'wipe menu' with several useful options[/SIZE]

  • s "Standard: create MSDOS partition table with FAT32 partition"
  • b "Big drive: create GUID partition table with NTFS partition"
  • g "General: use 'gparted' to make partition table and partition(s)"
  • a "Advanced: create GUID partition table (skeleton for installing an OS)"
  • f "wipe the First megabyte (mibibyte)"
  • w "wipe the Whole device - consider other options except for special cases"

[SIZE=4]Several iso files can be cloned to working USB pendrives[/SIZE]

ISO files that can be be cloned to working USB boot drives are called hybrid iso files.

There are mkusb PPAs for {Ubuntu, Kubuntu, Lubuntu, Xubuntu ...} {12.04 LTS, 14.04 LTS, 14.10, 15.04} alias {precise, trusty, utopic, vivid}. * mkusb* can make working USB installers also from the Ubuntu mini.iso. See this link.

[COLOR=#800080]New:[/COLOR] You find working mini.iso files for 12.04 LTS (32-bits pae (and non-pae in a subdirectory)) at this link - precise-updates.

Arch Bento Bodhi Clonezilla (mkusb-nox) Debian Jessie Fedora (uses simpler black & white menus because zenity lacks support for html) (live only) Knoppix (needed treatment with isohybrid) Linux Mint LXLE Mageia (live only) openSUSE (live only) ToriOS Webconverger

while some other iso files did not work (although they make good CD boot disks). It is often possible to convert such an iso file to a hybrid iso with the following command

isohybrid downloaded-file.iso

It converts the iso in-place (the file is overwritten), so make a copy before you run *isohybrid* if you want to keep the original file untouched. See the following link

http://gparted-forum.surf4.info/viewtopic.php?pid=30798#p30798

[SIZE=4]Complete install to USB[/SIZE]

I also installed Lubuntu to a 16 GB USB pendrive, a complete install, like to a HDD. It was a little tricky with the swap partition, so now I know, why people advice, that you should disconnect the internal drive before doing it. This pendrive is truly portable, and probably better than a persistent live system. *Please* avoid proprietary drivers, if you want portability! There are several compressed image files, that were made from such installed systems, and they can be installed with mkusb. See the following links,

help.ubuntu.com/community/Installation/UEFI-and-BIOS

AskUbuntu: Boot Ubuntu from external drive

[SIZE=4]Booting USB drives with grub2 and iso files 'grub-n-iso' [/SIZE]

64-bit versions work only in 64-bit computers. 32-bit versions work in 32-bit and 64-bit computer (with BIOS, but not with UEFI, unless you use the methods described in the following paragraph).

The 'grub-n-iso' method uses grub2 to boot from an iso file, so once you have such a USB pendrive, you can boot most Intel and AMD computers that can run a 32-bit system (except very old non-PAE systems, systems with too low RAM, and systems with non-compatible hardware). The 'grub-n-iso' method can be used to create multi-boot USB pendrives by selecting iso file to boot from in the grub menu.

You can use the shell-script *mkusb* also for this task, to clone a compressed image from a file [FONT=courier new]file.img.gz[/FONT] to a USB drive. You can download such files from http://phillw.net/isos/linux-tools/uefi-n-bios/

[SIZE=4]mkusb can make persistent live drives[/SIZE]

A modified 'grub-n-iso' method is used, when mkusb creates persistent live drives. See details at mkusb/persistent

[SIZE=4]One pendrive for all PC (Intel/AMD) computers - Ubuntu 64-bit and Lubuntu 32-bit[/SIZE]

The following four systems are downloaded as compressed image files and installed via *mkusb*

  1. One pendrive for all PC (Intel/AMD) computers - Ubuntu 64-bit and Lubuntu 32-bit

There are methods now to make 32-bit Ubuntu family operating systems boot in UEFI mode via grub and iso files, 'grub-n-iso'. This makes it possible to make a USB pendrive with persistence, that is very portable between different computers :smile:

  1. A smaller and simpler pendrive for all PC (Intel/AMD) computers - 'grub-n-iso' - Lubuntu 32-bit
  1. Multiboot pendrive system for all PC (Intel/AMD) computers
  1. Make persistent live drives with casper-rw and home-rw partitions *New 2018-04-30:* a shellscript developed within the 'grub-n-iso' method, mk-persistent-live_with_home-rw.

-o-

The system with compressed image files makes it easy for a beginner to install, but it is rather inflexible. So I made a shell-script, that does the main part of the work with the help of a couple of files for the configuration of the booting system. See this link

Build your own single boot or multiboot pendrive for all PC (Intel/AMD) computers

[hr][/hr] [SIZE=4]References to tutorials and tips how to make USB boot drives[/SIZE]

Ubuntu help page - FromUSBStick Ubuntu help page - mkusb Ubuntu wiki page - Win32DiskImager/iso2usb Ubuntu wiki page - Win32DiskImager/compressed-image_2_USB-or-SD Ubuntu help page - UEFI-and-BIOS

#2

I added details *how to wipe the CD file system*, if you want to use the USB drive with a normal file system again.

#3

bump

#4

The shell-script is updated 2013-06-09 (June 9) and much improved compared to the original version. It is now convenient to use also for one-off creations of USB boot devices. There are also some hints about the usage. See the opening post (the first post).

#5

Elfy said: bump

attaching the picture of locked threads (except two of them). Were they locked because of age? I don't think there is anything unethical in them.

#6

[COLOR=#800080]*Temporary edit*:

The startup disk creator version [FONT=courier new]usb-creator-gtk[/FONT] is buggy in Lubuntu 13.04, and it is being debugged right now. Please install two[/COLOR][COLOR=#800080][COLOR=#800080] additional[/COLOR] packages, that help it work, either directly or via a PPA!

[/COLOR]``` [COLOR=#800080]sudo apt-get install [/COLOR][COLOR=#800080][COLOR=#800080]usb-creator-gtk [/COLOR][/COLOR][COLOR=#800080][COLOR=#800080]python-gudev gir1.2-gudev-1.0[/COLOR][/COLOR]

or

sudo add-apt-repository ppa:jmarsden/lubuntu sudo apt-get update sudo apt-get install usb-creator-gtk


[COLOR=#800080]It is improved in current updated/upgraded development installations of Lubuntu 13.10 (saucy-proposed December 18 2013)) and can create persistent USB drives, but it crashes when trying to erase a disk. There is project to rewrite it for 14.04 LTS[/COLOR]. If you still have problems with usb-creator-gtk, as a temporary workaround, you can try using **[FONT=courier new]usb-creator-kde[/FONT]** or one of the other tools instead. [/COLOR][See this bug report (and comments #15 and #16)]("https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1165200/")[COLOR=#800080] and [this bug report about the current debugging]("https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/915626").
[/COLOR]
-o-

A dd image of **[FONT=courier new]ubuntu-13.04-desktop-amd64.iso[/FONT]** creates a USB pendrive that works in both UEFI and CSM (BIOS) modes.

64-bit versions work only in 64-bit computers. 32-bit versions work in 32-bit and 64-bit computer with BIOS, but not with UEFI.

-o-

The ['grub-n-iso']("https://help.ubuntu.com/community/grub-n-iso") method uses grub2 to boot from an iso file, so once you have such a USB pendrive, you can boot most Intel and AMD computers with a 32-bit system (except very old non-PAE systems, UEFI systems, systems with too low RAM, and systems with non-compatible hardware). The  'grub-n-iso' method can be used to create multi-boot USB pendrives. You can also start from this [link to Pendrivelinux]("http://www.pendrivelinux.com/install-grub2-on-usb-from-ubuntu-linux/") and modify the USB drive to suit what you need.
#7

The shell-script is updated 2013-06-15 (June 15) and improved compared to the previous version. It is now convenient to use also for one-off creations of USB boot devices from iso files and compressed image files and also to wipe the drives if necessary after the cloning.

A typical dialogue looks like this the first time you run the script (and the label of the iso file does not match that on the USB drive). Either the general usage text

$ mkusb
Usage:
---- Make a USB install device from 'file.iso' -------
[COLOR=#0000ff]sudo /home/olle/bin/mkusb file.iso[/COLOR]
---- Make a USB install device from 'file.img.gz' ----
[COLOR=#0000ff]sudo /home/olle/bin/mkusb file.img.gz[/COLOR]
---- Make a USB install device from 'file.img.xz' ----
[COLOR=#0000ff]sudo /home/olle/bin/mkusb file.img.xz[/COLOR]
---- Wipe the USB device (may take long time) --------
[COLOR=#0000ff]sudo /home/olle/bin/mkusb wipe-all[/COLOR]
---- Wipe the first megabyte (MibiByte) -[COLOR=#0000cd]-------------
[/COLOR][COLOR=#0000ff]sudo /home/olle/bin/mkusb wipe-1[/COLOR]
---- Version -----------------------------------------
[COLOR=#0000ff]/home/olle/bin/mkusb -v[/COLOR]
$ 

or the specific usage text to help you cut and paste to get 'sudo and the path' easily, and then run the whole script to get the advice how to run the dd command line.


$ mkusb saucy-desktop-i386.iso
Usage:
[COLOR=#0000ff]sudo /home/sudodus/bin/mkusb saucy-desktop-i386.iso
[/COLOR]$ 

*Edit*: There are more details in the first post (the tutorial) while these following posts are 'only' comments about updates.

#8

You can make a working USB install drive with the dd cloning method with mini.iso version 13.04. I learned this from innn at the Ubuntu Forums. See this link.

#9

*Bugfix*: To avoid problems, when a bad partition table is found on some of the drives [FONT=courier new][B] parted -l[/B][/FONT] was changed to [FONT=courier new]parted -ls[/FONT]

when used in the shell-script. See [FONT=courier new]man parted [/FONT] -o-

A compressed copy of the shell-script file is attached to the first post.

The size and md5sum of the script file are listed. This makes it possible to check that the file was copied or downloaded correctly.

#10

There is also[URL="https://launchpad.net/gdiskdump"]

[SIZE=4]gdiskdump[/SIZE] [/URL]

which is a GUI for diskdump (dd), a clone and imaging tool for mass storage devices (hard disk drives, SSD, USB pendrives ...).

This is an open source Graphical User Interface for the Unix Command dd. You can easily select the Input- and Outputstream, so you can clone or image your Harddrive or Partition.

Wikipedia: "dd is a common Unix program whose primary purpose is the low-level copying and conversion of raw data." The version 0.8 .deb Package is working on Ubuntu 9.10+ (x86 and amd64) and other Debian like Distros.

The link to [gdiskdump was added at the end of post #1]

#11

The shell-script is updated 2013-09-05 (Sept 5) and much improved compared to the previous version. See the opening post (the first post).

  1. The script is updated to manage the changes of the iso file in version 13.10, so that the next daily build will automatically select the correct USB device.
  1. The data transfer can be monitored with [SIZE=4][FONT=courier new]pv[/FONT][/SIZE]. If not installed, the user gets a tip to install [FONT=courier new]pv[/FONT], but the old style is there for users who do not want the extra verbosity with [FONT=courier new]pv[/FONT] (if pv is not installed).
  1. There is also the previous version with a minor but important fix to partly manage the new iso format of 13.10 (the version from June 23 plus a minor fix). While I'm happy with the new version and recommend it, you are given the opportunity to have this old version (with the fix), if you prefer the simpler way it works and looks. It can also be used, if you have tweaked your own version of [FONT=courier new]mkusb[/FONT] (patch the update into your version)

[COLOR=#0000ff]diff mkusb2 mkusb-old-plus-minor-fix[/COLOR]
72c72,73
<  target="$(blkid | grep "$label" |sed s/.:.*// |grep "/dev/sd")"
---
>  #target="$(blkid | grep "$label" |sed s/.:.*// |grep "/dev/sd")"
>  target="$(blkid | grep "$label" |cut -b -8 |grep "/dev/sd")"
  1. The code windows in the opening post are also updated for typical input and output when using [FONT=courier new]mkusb[/FONT].
  1. There is a brief introduction to the One Button Installer

There is a wiki page at https://help.ubuntu.com/community/OBI, and files to download are available at http://phillw.net/isos/one-button-installer/. There is also a tutorial thread here, One Button Installer, 'OBI'.

#12

The new version 4 is available now, but several instructions in post #1 are still describing version 3. Version 4 is more automatic. You need not copy and paste the command line. This example shows how to select the target device with (+/-) or the number of the list item. Go ahead with (g) or quit with (q). (Toggle 'USB-only' with (u) if you want to write to a drive that is not a USB drive.)

[COLOR=#0000ff]sudo mkusb saucy-desktop-i386.iso[/COLOR]
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: warning: /tmp/tmp.Jbu6YwpDsR seems to be mounted read-only.
Lubuntu 13.10 "Saucy Salamander" - Beta i386 _found_ in iso-file
Lubuntu 13.10 "Saucy Salamander" - Beta i386 _not_ in USB device
Do you want to make a new one? (y/n)
y
[COLOR=#ff0000]***  WARNING: the device will be completely overwritten      ***
     Use the info in the xterm window (less /tmp/help-mkusb.txt)
***  quit with (q)                                           ***[/COLOR]
***  Unmount the device if mounted  ****************************
 
Model: ATA SAMSUNG HD322HJ (scsi)    Disk /dev/sda: 320GB    
Model: ATA OCZ-AGILITY3 (scsi)    Disk /dev/sdb: 60.0GB    
Model: ATA WDC WD10EARS-00Y (scsi)    Disk /dev/sdc: 1000GB    
Model: SanDisk Cruzer Blade (scsi)    Disk /dev/sdd: 4005MB    
Model: SanDisk Extreme (scsi)    Disk /dev/sde: 32.0GB    
Model: JetFlash Transcend 16GB (scsi)    Disk /dev/sdf: 15.8GB    
Live drive: /dev/sdb
USB drive:  /dev/sdd: 4004 MB, 4004511744 bytes
USB drive:  /dev/sde: 32.0 GB, 32017047552 bytes
USB drive:  /dev/sdf: 15.8 GB, 15812526080 bytes
 
[COLOR=#ff0000]---> 1: install to SanDisk Cruzer Blade (scsi) Disk /dev/sdd: 4005MB[/COLOR]
     2: install to SanDisk Extreme (scsi) Disk /dev/sde: 32.0GB
     3: install to JetFlash Transcend 16GB (scsi) Disk /dev/sdf: 15.8GB
Select another device with (+/-) or the number of the list item.
Go ahead with (g) or quit with (q). Toggle USB-only with (u).
2
     1: install to SanDisk Cruzer Blade (scsi) Disk /dev/sdd: 4005MB
[COLOR=#ff0000]---> 2: install to SanDisk Extreme (scsi) Disk /dev/sde: 32.0GB[/COLOR]
     3: install to JetFlash Transcend 16GB (scsi) Disk /dev/sdf: 15.8GB
Select another device with (+/-) or the number of the list item.
Go ahead with (g) or quit with (q). Toggle USB-only with (u).
g
2: source: saucy-desktop-i386.iso
   target: SanDisk Extreme (scsi) Disk /dev/sde: 32.0GB 
Do you really want to wipe and install to this device? (y/n)

'Do you really want to wipe and install to this device? (y/n)' is the last warning. If you answer y (and press the Enter key), the source file will be cloned to the target device.

[COLOR=#696969]This interface is borrowed from the One Button Installer, version 0.6 and 0.7.

[/COLOR]Version 4 works well not only in graphical desktops with terminal windows, but also in text screens (for example in a server). It can manage img.xz files (compressed with xz with ~20% better compression than gzip).

#13

[SIZE=4]Try to convert to a hybrid iso file[/SIZE]

ISO files that can be be cloned to working USB boot drives are called hybrid iso files. I tested and could make working USB boot drives from

  • ubuntu flavours 12.04+ (Kubuntu, Lubuntu, Ubuntu, Xubuntu, ... , desktop, alternate and server work, but not mini.iso)
  • mini.iso version 13.04. See this link.
  • linux mint 13+
  • clonezilla
  • debian stable
  • webconverger

while some other iso files did not work (although they make good CD boot disks). I could convert such an iso file to a hybrid iso (another person's 12.04 LTS re-spin using my own 12.04 LTS system) with the following command

isohybrid downloaded-file.iso

It converts the iso in-place (the file is overwritten), so make a copy before you run *isohybrid* if you want to keep the original file untouched. See the following link

http://gparted-forum.surf4.info/viewtopic.php?pid=30798#p30798

#14

sudo usb-creator-gtk

opens startup disk creator's GUI

#15

Yes, the 'command line names' usb-creator-gtk and usb-creator-kde correspond to the 'menu name' Startup Disk Creator (which is translated to the language used) and there is a detailed description of that tool at the wiki page

https://help.ubuntu.com/community/Installation/FromUSBStick#Install_and_run_usb-creator

[COLOR=#800080]*Temporary edit*: [/COLOR][COLOR=#800080][FONT=courier new]usb-creator-gtk[/FONT] is buggy in Lubuntu 13.04 and 13.10, and is being debugged. There is project to rewrite it for 14.04 LTS. [/COLOR][COLOR=#800080]If you still have problems with usb-creator-gtk, as a temporary workaround, you can try using [FONT=courier new]usb-creator-kde[/FONT] or [FONT=courier new]unetbootin[/FONT] or one of the other tools instead. See details at post #4[/COLOR][COLOR=#800080] [/COLOR]

#16

[I][B]mkusb version 5 is uploaded in a compressed tar file, a tarball. [/B][/I] New in version 5: In response to a user request [FONT=courier new]mkusb[/FONT] will install [FONT=courier new]pv[/FONT] automatically (if not already installed), when the user answers yes; the default in no (y/N).

There is only one *attached file* at post #1 and it contains the new version 5 of [FONT=courier new]mkusb[/FONT] and also previous versions for users that like simple scripts. Extract the script from the compressed file with *one* of these commands (or file-roller).


tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]-old-plus-minor-fix[/COLOR] > mkusb
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]3[/COLOR] > mkusb
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]4 [/COLOR]> mkusb
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]5[/COLOR] > mkusb

I use the file name [FONT=courier new]mkusb[/FONT], put it into my [FONT=courier new]~/bin[/FONT] directory and make it executable.

[COLOR=#0000ff]chmod ugo+x mkusb[/COLOR]

The current size and md5sum are listed in the next code box. Check that the file is correct before you start using it!


[COLOR=#0000ff]wc -c mkusb;md5sum mkusb  # from mkusb5.gz[/COLOR]
11692 mkusb
ab435d9606f30ee0ec0f1a46b849dbc1  mkusb

[COLOR=#0000ff]wc -c mkusb;md5sum mkusb  # from mkusb4.gz[/COLOR]
11373 mkusb
6ce8db8c1981e905800dfbb1f500176a  mkusb

[COLOR=#0000ff]wc -c mkusb;md5sum mkusb  # from mkusb3.gz[/COLOR]
6119 mkusb
ef16e65a7996cc0b5142fca81d9f9c83  mkusb

[COLOR=#0000ff]wc -c mkusb-old-plus-minor-fix; md5sum mkusb-old-plus-minor-fix[/COLOR]
4916 mkusb-old-plus-minor-fix
5fb04df7cdccaf915fac6978c6f6b6f4  mkusb-old-plus-minor-fix

Use the new version 5, or stay with an earlier version for example version 3 with more direct interaction in the terminal window.

#17

[SIZE=4][SIZE=4]Quick start manual and mkusb[/SIZE]

[/SIZE]The fastest way to start making USB boot drives is to download the *quick start manual* and the shell-script [FONT=courier new]mkusb[/FONT] and check the md5sums.

#18

Thank you for the tutorial, I was just looking for that!

#19

You are welcome, I hope it works well for you :-)

#20

[SIZE=4]A tool that helps boot some computers from [other] USB boot drives - Chainloader[/SIZE]

The *chainloader* is useful for middle-aged computers, for example computers without a CD/DVD drive, where it can be hard to boot from a USB drive, or when you want to run from a fast USB 3 drive that is unwilling to boot.

What is new, why a new tool? Isn't it enough to be able to use *mkusb* or the other tools?

The answer is in this link to the tutorial Howto help USB boot drives

#21

[I][B]mkusb version 6 is uploaded in a compressed tar file, a tarball. [/B][/I] Version 6 contains a bugfix. All calls with sudo in the code are removed, which makes mkusb work in systems that lack the sudo command (but where it is possible to run as the user root).

There is only one *attached file* at post #1 and it contains the new version 6 of [FONT=courier new]mkusb[/FONT] and also previous versions. Extract the script from the compressed file with *one* of these commands (or file-roller).


tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]-old-plus-minor-fix[/COLOR] > mkusb
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]3[/COLOR] > mkusb
...
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]6[/COLOR] > mkusb

I use the file name [FONT=courier new]mkusb[/FONT], put it into my [FONT=courier new]~/bin[/FONT] directory and make it executable.

[COLOR=#0000ff]chmod ugo+x mkusb[/COLOR]

The current size and md5sum are listed in the next code box. Check that the file is correct before you start using it!


[COLOR=#0000ff]wc -c mkusb;md5sum mkusb  # from mkusb6
[/COLOR]11677 mkusb
8c0f0a3cc52a0267036a4a7c78f4a8f6  mkusb[COLOR=#0000ff]
[/COLOR]
#22

The reason that usb-creator-gtk doesn't work may be because the iso file is not on a local file system. When I selected an iso file on an sshfs mounted filesystem, it refused to create the disk, displaying an error message indicating "Installation failed". Once I moved the .iso file to the local file system it worked without any issues.

This is on xubuntu 13.10

#23

ager-wick said: The reason that usb-creator-gtk doesn't work may be because the iso file is not on a local file system.

When I selected an iso file on an sshfs mounted filesystem, it refused to create the disk, displaying an error message indicating "Installation failed". Once I moved the .iso file to the local file system it worked without any issues.

This is on xubuntu 13.10

Interesting! It is worth looking into this problem. What OS (version and flavour of Ubuntu) were you running?

#24

Thanks for sharing this observation, *ager-wick*.

#25

[I][B]mkusb version 7.1 is uploaded in a compressed tar file, a tarball. [/B][/I] Version 7.1 contains a bugfix for unusual cases. The identification of the 'livedrive', the drive from which the current operating system is started did not work with all versions of Ubuntu when 'trying Ubuntu' or running a live session booted from from an install CD/DVD/USB drive. It is fixed to work for a few more cases. It is tested when booted from *CD*, and *USB* drives made via *cloning* the ISO file, *grub-n-iso, unetbootin, usb-creator-gtk*.

*Please let me know if you find another version or instance where it does not work!* For example, there are several other tools to make live drives, and there may be problems with some of them.

There is only one *attached file* at post #1 and it contains the new version 7.1 of [FONT=courier new]mkusb[/FONT] and also previous versions. Extract the script from the compressed file with *one* of these commands (or file-roller).


tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]-old-plus-minor-fix[/COLOR] > mkusb
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]3[/COLOR] > mkusb
...
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]71[/COLOR] > mkusb

I use the file name [FONT=courier new]mkusb[/FONT], put it into my [FONT=courier new]~/bin[/FONT] directory and make it executable.

[COLOR=#0000ff]chmod ugo+x mkusb[/COLOR]

The current size and md5sum are listed in the next code box. Check that the file is correct before you start using it!


[COLOR=#0000ff]wc -c mkusb;md5sum mkusb  # from mkusb71
[/COLOR]12450 mkusb
f1fe8feb917d12576d8785a70ad1a17f  mkusb
#26

Good stuff guys, thanks.

#27

Thank you :-)

#28

[I][B]mkusb version 7.4 is uploaded in a compressed tar file, a tarball. [/B][/I] Version 7.4 contains several minor improvements after version 7.1


# 2014-03-06  sudodus  fix to recognize debian iso file and work from CD
# 2014-03-06  sudodus  mkusb version 7.2
# 2014-03-09  sudodus  second parameter 'all' to start seeing all drives
#                      usbonly=false
# 2014-03-09  sudodus  mkusb version 7.3
# 2014-03-13  sudodus  switch for help window
# 2014-03-14  sudodus  writing "Done" after installation (for xterm -hold) 
# 2014-03-14  sudodus  mkusb version 7.4

There is only one *attached file* at post #1 and it contains the new version 7.4 of [FONT=courier new]mkusb[/FONT] and also previous versions. Extract the script from the compressed file with *one* of these commands (or file-roller).


tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]-old-plus-minor-fix[/COLOR] > mkusb
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]3[/COLOR] > mkusb
...
tar -xvOf mkusb-ball.tar.gz mkusb[COLOR=#0000ff]74[/COLOR] > mkusb

I use the file name [FONT=courier new]mkusb[/FONT], put it into my [FONT=courier new]~/bin[/FONT] directory and make it executable.

[COLOR=#0000ff]chmod ugo+x mkusb[/COLOR]

The current size and md5sum are listed in the next code box. Check that the file is correct before you start using it!


[COLOR=#0000ff]wc -c mkusb;md5sum mkusb  # from mkusb74
[/COLOR]13998 mkusb
d02976734e6be3e173910b9e6ac636c2  mkusb
#29

Thank you

#30

You are welcome :-) I'm glad that mkusb is useful for you.

#31

You can make them using unetbootin...its a freeware and the best one could get....... Download it fron here...: http://unetbootin.sourceforge.net :P

#32

Navneet_Kumar said: You can make them using unetbootin...its a freeware and the best one could get.......

Download it fron here...: http://unetbootin.sourceforge.net :P

Yes, Unetbootin is a good tool. There is a detailed description how to use it at

Paul Sutton's Unetbootin how to

and you can get a general overview about USB boot drives at this link

https://help.ubuntu.com/community/Installation/FromUSBStick

#33

[SIZE=4][SIZE=4]Quick start manual and mkusb [/SIZE][/SIZE]- modified links because Ubuntu One will be closed

The fastest way to start making USB boot drives is to download the *quick start manual* and the shell-script [FONT=courier new]mkusb[/FONT] and check the md5sums.

See this link http://phillw.net/isos/linux-tools/mkusb/

#34

Just got lubuntu 14.04 running nicely in persistence mode on a 4 GB and a 8 GB usb stick.

startup disk creator ran fine on ubuntu 12.04. Fire up unity and open the top applet on the launcher and start typing st... and select the icon.

I got 3 failures with 14.10 startup disk creator, First two times the usb booted to command line initramfs instead of desktop.

Last time, erasing the usb with startup disk creator caused python errors. Yes I made a launchpad bug copy/paste the many error lines.

sudo gparted and formatted the usb to F32. Do NOT use a volume label. My experience startup disk creator usb's don't like that. I erased the volume label with startup disk creator's erase option.

I'm interested in running Firefox, no history, with flashplugin installed. Lubuntu is a smaller image to fit in memory than unity (!) with not nearly so much bloatware.

Final result running Firefox just about like from a hard drive - and without the hard disk partitions mounted.

Now it's been some time (years) since I've run lubunto so I've got a bit of learning to do. So far so good.

Now it's faster to create the usb bootable by following the ubuntu hybrid iso directions with the primitive (!) linux command dd (watch out!) however creating a persistence capability is much easier for me with ubuntu's startup disk creator.

#35

jerrylamos said: Just got lubuntu 14.04 running nicely in persistence mode on a 4 GB and a 8 GB usb stick.

startup disk creator ran fine on ubuntu 12.04. Fire up unity and open the top applet on the launcher and start typing st... and select the icon.

I got 3 failures with 14.10 startup disk creator, First two times the usb booted to command line initramfs instead of desktop.

Last time, erasing the usb with startup disk creator caused python errors. Yes I made a launchpad bug copy/paste the many error lines.

I have been quite successful running the Startup Disk Creator (usb-creator-gtk) in 12.04 LTS, 13.10 and 14.04 LTS except erasing. I have not yet tried it in 14.10, but I can easily imagine it needs debugging to work there. In my experience usb-creator-kde is more reliable, but it pulls in a lot of kde packages (unless you are already running Kubuntu).

sudo gparted and formatted the usb to F32. Do NOT use a volume label. My experience startup disk creator usb's don't like that. I erased the volume label with startup disk creator's erase option.

I'm interested in running Firefox, no history, with flashplugin installed. Lubuntu is a smaller image to fit in memory than unity (!) with not nearly so much bloatware.

Final result running Firefox just about like from a hard drive - and without the hard disk partitions mounted.

Are you happy with the setting in Firefox 'Save no history'? Or would you prefer a read-only system with flashplugin installed?

Now it's been some time (years) since I've run lubunto so I've got a bit of learning to do. So far so good.

Now it's faster to create the usb bootable by following the ubuntu hybrid iso directions with the primitive (!) linux command dd (watch out!) however creating a persistence capability is much easier for me with ubuntu's startup disk creator.

Yes it is faster to use *dd* directly, but also more risky. It does what you tell it to do without questions, so a simple typing error or misunderstood order of devices can wipe important data. This is why I made *mkusb*, to make it safer to use dd. But it is for live sessions without persistence (with the read-only iso-9660 file system). When I want a persistent live system I use either the Startup Disk Creator or Unetbootin, but I often make a full installed system in a USB 3 pendrive, which I like better than a persistent live system.

#36

Hi!

  • How I can make the checksum (MD5, SHA1, SHA256 etc) in my Pen Drive with the mkusb? In other words, make the .ISO image checksum recorded in Pen Drive.
  • Another thing, I run the "sudo mkusb wipe-whole-device" command to clear the Pen Drive, but this command completely erases everything, even the partition and the partition table. Is there any way to delete only the contents of the Pen Drive without touching on partitions and stuff?
#37

Welcome to the Ubuntu Forums *renanrischiotto1 *:-)

*mkusb* does not run any checksum tests. But since it is a 'command line' or 'terminal window' program, it is straightforward to run those tests directly, for example

md5sum installer-file.iso

and check that it matches the value listed at

https://help.ubuntu.com/community/UbuntuHashes

-o-

  • If you plan to use mkusb, you need *not* erase the pendrive, because the installation will overwrite the previous content including the bootloader and partition table.
  • If you have used an installer made with mkusb, you may have problems to use *gparted* to create something new on the drive. This is why you should wipe the first megabyte. Then gparted will be happy and can install a new partition table and after that partitions and file systems.
  • If you want to erase all files on a drive (pendrive or HDD or SSD), you can use many tools, command line tools like *rm*, or simply do it with a file browser. But the content of the files can probably be recovered with for example *PhotoRec*.

-If you want to wipe (overwrite) all information on a drive (pendrive or HDD or SSD) for security reasons, you can use mkusb to 'wipe the whole drive'. But as I wrote in the first post of this thread, there are better tools for it (at least for hard disk drives), for example *hdparm* and *DBAN*.

#38

Thanks for answering!! :)

I had recorded a image .ISO on my Pen Drive with the mkusb. After, I run the "wipe-whole-device", after the procedure done, the Pen Drive no more was mounted in Ubuntu, then I opened the GParted and I saw no partition table or anything. So I created a new partition table "msdos" and I formated to FAT32 (primary partition), and I let 4MB of unallocated space for the eraseblock of Pen Drive. Actually I do not know the eraseblock of my Pen Drive (SanDisk Cruzer Blade 4GB), but it seems that 4MB is usually the eraseblock most used in Pen Drives. I did not know which was necessary run the "wipe-1" for better management using GParted. Anyway, would not have done any of this if I knew it was not necessary to delete the data from Pen Drive to a new recording =P

Did I do something wrong?

#39

No, I think nothing was wrong, only more complicated than necessary. I think gparted leaves 1 MB free space before the first partition starts as the default setting. That would work too as well as 4 MB.

Is the pendrive working like it should now?

#40

I have not tested it yet but I think that are perfect :)

*Sorry if my english is bad, I'm brazilian, I do my best which help of Google Tradutor =P

#41

The Pen Drive worked fine =)

So... a GUI for this program would be a good =)

#42

I'm glad you could make a pendrive that worked for you renanrischiotto1 :-)

I know and agree, that a GUI would make mkusb more attractive and more useful for people who are not used to the command line interface (terminal window). I have considered it, even discussed it with some people. When I have enough time, I'll try to do it.

#43

Nice =)

-------------------

You said this:

[COLOR=#000000]"If you have used an installer made with mkusb, you may have problems to use [/COLOR][I]gparted to create something new on the drive. This is why you should wipe the first megabyte. Then gparted will be happy and can install a new partition table and after that partitions and file systems." [/I] So, if I do not need use GParted after, it's best to use the "wipe-whole-device" or not? I do not understand the difference between "wipe-1" and "wipe-whole-device".

Another thing: If I run "wipe-whole-device", I need to create the partition table, partition and file system in the Pen Drive?

#44

For me, a USB pendrive is a temporary device, that I use for several things, and I use gparted to re-partition when I want to do that.

Using mkusb to make an install USB drive from an iso file makes the pendrive read-only because the ISO file system is read-only. So *to use the pendrive for example to store files to carry from one computer to another one, it must be re-partitioned. In this case gparted might have problems. Such problems are solved by wiping the first megabyte.*

It might be the same problem if you want to use Unetbootin or the Startup Disk Creator. Then you should make a FAT32 file system with gparted. If problems, wipe the first megabyte and try again with gparted.

But if you use mkusb to install another iso file to try another linux distro or version or flavour of Ubuntu, you need not wipe it. mkusb will overwrite the partition table anyway.

-o-

Wiping the whole drive is done in order to remove all information, so that some other person cannot recover it.

#45

Thanks man :)

#46

So.... :D

Would not cause the mkusb not remove the partition table of the Pen Drive and all within the Pen Drive? I say this because an unallocated space is recommended to leave for the erase block of Pen Drive (I learned this on the Ubuntu forum BR '-'), and possibly FAT32 partition (which is the standard of Pen Drive's).

#47

I'm not sure I understand what you mean.

The idea with mkusb is to make it safe to clone/flash an iso file or a compressed image file to a pendrive (each byte is copied exactly). The program dd is doing the job behind the curtain. This method does not allow for saving or skipping some space to be unallocated.

On the other hand, gparted will automatically leave the first megabyte unallocated (except the first 512 bytes, where it puts the bootloader and the partition table).

-o-

If you want to use your pendrive for storage at the same time as it is an installer, you should use another method, which uses a read/write file system, for example FAT32. In such cases Unetbootin or the Startup Disk Creator might be better alternatives.

#48

Great post, but personally i have never had a problem using dd to make a bootbale usb. It has probably worked better than unetbootin and the ubuntu startup disk creator has for me in the past. I guess you just have to make sure you use it correctly maybe? I came across this tutorial which i use when ever i want to make a bootable usb drive www.ivegotavirus.com/how-to-quickest-way-to-make-a-bootable-linux-usb-drive. Its worked for me every time with every sort of distro.

#49

Thanks for the feedback and the link :-)

> I guess you just have to make sure you use it correctly maybe?

This is the crucial point. If you make a small mistake with dd, it might reverse the process and overwrite what you wanted to save, or the output might be directed to a drive where you keep valuable files. I certainly agree, that dd is a marvelous tool, but without tight control, it can go bärsärk (berserk). This is why I made *mkusb*, at first only for myself, later on I uploaded it with this tutorial to help others use it in a safer way.

Cloning an iso file to a mass storage device, typically a USB drive, makes a boot drive provided it is a hybrid iso file, post-processed with *isohybrid*. See ``` man isohybrid


This is very reliable, and it is a particularly good for new releases, when the standard tools like Unetbootin might not be ready (if the configuration of the booting has been changed since the previous release).
#50

[SIZE=4]Release candidate *mkusb8-rc* with menus[/SIZE]

[s]I'm soon getting ready to upload[/s] I have uploaded a release candidate of the *mkusb* tool to install iso files and compressed image files to mass storage devices (typically but not only USB drives). It is only a bash script, and has been running in crude text mode, but people want eye candy, so I've made menus with *dialog* (big brother of whiptail), and also improved the identification of devices slightly (replaced calling *parted -ls* with a home-made bash function). It is still text mode, so runs in text screens and terminal windows.

See the attached pictures, which illustrate *the crucial part of mkusb, how to help selecting the correct device* and avoid overwriting other devices.

*Edit*: The file mkusb8-rc is uploaded to

http://phillw.net/isos/linux-tools/mkusb/

Check it with the corresponding signed md5sum file.

-rwxr-xr-x. 1 nio nio  22877 18 jul 06.46 mkusb8-rc
-rw-rw-r--. 1 nio nio    581 18 jul 11.27 mkusb8-rc.md5.asc

The quick start manual and the opening post in this thread are still valid, except the illustrations, that will be updated later on with screenshots of the menus.

Please give me feedback about this release candidate: help me find bugs and suggest improvements!

#51

I have started writing a wiki page for mkusb

https://help.ubuntu.com/community/mkusb

where there is a brief description plus several screendumps (pictures as well as text screen dumps) from *mkusb8-rc*

#52

The file *mkusb8-rc2* is uploaded to

http://phillw.net/isos/linux-tools/mkusb/

Check it with the corresponding signed md5sum file.

-rwxr-xr-x. 1 nio nio 33407 21 jul 21.34 mkusb8-rc2
-rw-rw-r--. 1 nio nio   582 21 jul 21.37 mkusb8-rc2.md5.asc

There is a menu system to select the input file in this release candidate; the input file alias the source in the cloning process

' source file --> target drive'

but it is still possible to enter the input file as a parameter. So the command

sudo path/mkusb8-rc2

will start a menu system where you can select the input file and then the target drive, while either of

sudo path/mkusb8-rc2 file.iso
sudo path/mkusb8-rc2 file.img
sudo path/mkusb8-rc2 file.img.gz
sudo path/mkusb8-rc2 file.img.xz
sudo path/mkusb8-rc2 wipe-1

will skip to selecting the target drive directly.

The quick start manual and the opening post in this thread are still valid, except the illustrations, that will be updated later on with screenshots of the menus. See also the wiki page for mkusb https://help.ubuntu.com/community/mkusb where there is a brief description plus several updated screendumps including the new menus.

Please give me feedback about this release candidate: help me find bugs and suggest improvements!

#53

[SIZE=4]mkusb version 8[/SIZE]

After testing the release candidates, the new version of *mkusb* is released. The intention is that the menus should make it useful for a larger group of people.

*mkusb* version 8 with *menus* is uploaded to http://phillw.net/isos/linux-tools/mkusb/

and there is a more detailed description with many screenshots at https://help.ubuntu.com/community/mkusb

Edit: The quick start manual is updated to mkusb version 8, while the the old quick start manual describes the last version without menus, 7.4.

#54

Thanks!

Tried both mkusb8-rc2 and the newer dated mkusb with today's Lubuntu 64.

Clean as a whistle. Now I just booted the USB images and haven't tried to do an install yet.

BTW, I usually crank up gparted and format the USB to FAT32, then label example Lubuntu64. Sometimes the USB needs a partition table first.

For whatever reason over the years Ubuntu Startup Disk Creator has given me lots of grief as has brasero and unetbootin. I've even had to warily resort to command line dd, talk about playing with fire.

Thanks lots!

#55

You are welcome *jerrylamos* :-)

#56

[SIZE=4]mksub version 8.3[/SIZE]

I have uploaded *mkusb* version 8.3 to [[COLOR=#000000]phillw[/COLOR]]("http://ubuntuforums.org/member.php?u=824544")'s server http://phillw.net/isos/linux-tools/mkusb/

I think it is ready to be used by several more people now, and a good alternative to the Startup Disk Creator and Unetbootin in order to create USB boot drives. It is fast and reliable, and I hope it will be easy to use.

There are menus using 'dialog' which makes the text mode experience quite nice. And there are flie selectors using 'zenity', which makes it even more user friendly in graphical desktop environments. mkusb works in text mode as well as in graphical mode, locally as well as remotely via ssh.

You find more details at this wiki page https://help.ubuntu.com/community/mkusb

#57

Thank you so much!!! :p

#58

dunn2 said: Thank you so much!!! :p

I'm glad it worked for you :-)

-o-

[SIZE=4]mkusb version 8.4[/SIZE]

However, I found a bug that depends on the current date (now that it is a one-digit date (August 2). It made mkusb fail to find target devices. I squashed the bug and uploaded version 8.4 which has no bug that I know of now ;-)

See http://phillw.net/isos/linux-tools/mkusb/

and https://help.ubuntu.com/community/mkusb

#59

[SIZE=4]mkusb version 8.5[/SIZE]

The new version 8.5 has a feature to make it safer. The last warning screen has [COLOR=#ff0000]red[/COLOR] background. See the attached picture and the following links

http://phillw.net/isos/linux-tools/mkusb/

https://help.ubuntu.com/community/mkusb

*Edit*:

Version 8.5.1: cosmetic bugfix for compressed image files in order to show the progress display (LANG=C for pv display).

Version 8.5.2: Improvements and bugfixes

  • improved check if the same iso, for updating the (daily) iso image during iso testing http://iso.qa.ubuntu.com/
  • improved final dialogue, more logical, also cosmetic improvements
  • double quotes around the file name in the command string makes it work with some special characters, e.g. space and parenthesis. The following command works, but I recommend normal characters and no spaces.
sudo ./mkusb "quote file name (1) with special characters.iso"
#60

thanks!=d>=d>=d>=d>

#61

[SIZE=4]mkusb version 8.5 - improvements and bug-fixes[/SIZE][B]

Final warning with red background See this link and PPA, mkusb logo & icon, desktop file in version 8.5[/B] [IMG]https://help.ubuntu.com/community/mkusb/artwork?action=AttachFile&do=get&target=mkusb24.png[/IMG]

  • mkcmd_runcmd debugged in version 8.5.1 (LANG=C), for the progress display pv (cosmetic bugfix for compressed image files)
  • improvements and bugfixes in version 8.5.2
  • improved check if the same iso, for updating iso image at iso testing
  • improved final dialogue, more logical, also cosmetic improvements
  • double quotes around the file name in the command string makes it work with some special characters, e.g. space and parenthesis.

  • improvements and bugfixes in version 8.5.3
  • logo and icons developed and uploaded for mkusb
  • function zenitytest: usage test of zenity which also serves as splash in graphics mode
  • mkusb24.png stored in-file (in mkusb itself) encoded with base64
  • sudo -H mkusb recommended (due to graphics) but sudo mkusb works (and better via ssh -X)
  • final warning with zenity window
  • desktop file for easy access via menus in graphical desktop environments
  • manual page, you find it with man mkusb
  • mkusb.desktop using green xterm login and xterm console with correct dialog colours
  • PPA introduced

  • improvements and bugfixes in version 8.5.4
  • bugfix to restore red warning screen in text mode
  • some minor tweaks for the packaging of the PPA

The fastest way to start making USB boot drives is to install the mkusb PPA, install and update the mkusb package like all the other program packages. See this link https://launchpad.net/~mkusb/+archive/ubuntu/ppa

sudo add-apt-repository ppa:mkusb/ppa  # and press Enter to accept it
sudo apt-get update
sudo apt-get install mkusb

You can download the quick start manual and check the md5sums at this link http://phillw.net/isos/linux-tools/mkusb/

#62

[SIZE=4]mkusb version 9[/SIZE]

New: You can test mkusb version 9 with pure graphical menus and info texts including red warning menus via ppa:mkusb/unstable

See the link https://help.ubuntu.com/community/mkusb with details at /v9 [IMG]https://help.ubuntu.com/community/mkusb/artwork?action=AttachFile&do=get&target=mkusb24.png[/IMG]

File selection and the other dialogues use zenity (so this version works only in a graphical environment)

*mkusb-nox* is supplied via the PPA. It works in text screens, 'No X'.

#63

sudo add-apt-repository ppa:mkusb/ppa # and press Enter to accept it sudo apt-get update sudo apt-get install mkusb

after sudo apt-get install mkusb

I see :

Reading package lists... Done Building dependency tree Reading state information... Done [COLOR=#ff0000]E: Unable to locate package mkusb[/COLOR] ubuntu@ubuntu:/$

Then

ubuntu@ubuntu:/$ sudo -H mkusb [COLOR=#ff0000]sudo: mkusb: command not found[/COLOR] ubuntu@ubuntu:/$

[COLOR=#00ff00][SIZE=3]Help me, plz[/SIZE][/COLOR]

#64

sudo add-apt-repository ppa:mkusb/ppa # and press Enter to accept it sudo apt-get update sudo apt-get install mkusb

after sudo apt-get install mkusb

I see :

Reading package lists... Done Building dependency tree Reading state information... Done [COLOR=#ff0000]E: Unable to locate package mkusb[/COLOR] ubuntu@ubuntu:/$

Then

ubuntu@ubuntu:/$ sudo -H mkusb [COLOR=#ff0000]sudo: mkusb: command not found[/COLOR] ubuntu@ubuntu:/$

[COLOR=#00ff00][SIZE=3]Help me, plz[/SIZE][/COLOR]

Hi Sara,

In order to help you, I start by asking a few questions.

  1. Were the two first commands successful? What could you tell from the output of them? Was there some kind of error or warning text?
  1. Maybe there was a temporary error due to the internet or a server. Try again with the same three command lines :-)
  1. Please tell me which operating system you are using: Which version and flavour of Ubuntu, 12.04 LTS, 14.04 LTS, 14.10, standard Ubuntu, Kubuntu, Lubuntu, Xubuntu ... ? Or some special version?

-o-

*Edit:* I saw in another thread started by you, that you try installing ubuntu-*13.10*-desktop-i386. That version has passed end of life. I have not made a PPA entry for that version, which may explain why you cannot install mkusb.

Please install a version that is supported! See this link

Forums Staff recommendations on EOL Ubuntu releases, in particular 10.04 desktop.

#65

sudodus said: [SIZE=4]mkusb version 9[/SIZE]

New: You can test mkusb version 9 with pure graphical menus and info texts including red warning menus via ppa:mkusb/unstable

See the link https://help.ubuntu.com/community/mkusb with details at /v9 [IMG]https://help.ubuntu.com/community/mkusb/artwork?action=AttachFile&do=get&target=mkusb24.png[/IMG]

File selection and the other dialogues use zenity (so this version works only in a graphical environment)

*mkusb-nox* is supplied via the PPA. It works in text screens, 'No X'.

Now it is also possible to install mkusb version 9 with a script from http://phillw.net/isos/linux-tools/mkusb/, see this link

https://help.ubuntu.com/community/mkusb/v9#from_phillw.net

This makes it simple to test* in linux distros, which do not use Ubuntu PPAs, because the script downloads, checks and installs mkusb using only standard commands. It even checks itself and that the md5sum file was signed with a good signature by sudodos (me). The script can also remove what it installed. [HR][/HR]*) test, not use, because version 9 is still being developed and may fail in systems, where it is not tested; mkusb is tested (and tweaked to work) in

[COLOR=#006400]{Ubuntu, Kubuntu, Lubuntu, Xubuntu} {12.04 LTS, 14.04 LTS, 14.10} with PPAs for these versions (precise, trusty, utopic) Bento Bodhi Debian Wheezy (and 9w)[/COLOR] Fedora 20 (uses simpler black & white menus because zenity lacks support for html )[COLOR=#ff8c00] [/COLOR][COLOR=#006400]Knoppix 7.4 (needed treatment with isohybrid) Linux Mint LXLE 12.04.3 LXLE 12.04.4 revisited 32-bits (needed treatment with isohybrid) Mageia 4.1 Gnome Live and installed[/COLOR] (needs a legacy desktop file) openSUSE 13.1 (uses simpler black & white menus because zenity lacks support for html)[COLOR=#ff8c00] [/COLOR][COLOR=#006400]ToriOS alpha [/COLOR] [HR][/HR]**) In Fedora 20 and openSUSE 13.1, Zenity lacks the option --html, which is used in many dialogue windows by mkusb 9.

#66

sudodus said: Hi Sara,

In order to help you, I start by asking a few questions.

  1. Were the two first commands successful? What could you tell from the output of them? Was there some kind of error or warning text?
  1. Maybe there was a temporary error due to the internet or a server. Try again with the same three command lines :-)
  1. Please tell me which operating system you are using: Which version and flavour of Ubuntu, 12.04 LTS, 14.04 LTS, 14.10, standard Ubuntu, Kubuntu, Lubuntu, Xubuntu ... ? Or some special version?

-o-

*Edit:* I saw in another thread started by you, that you try installing ubuntu-*13.10*-desktop-i386. That version has passed end of life. I have not made a PPA entry for that version, which may explain why you cannot install mkusb.

Please install a version that is supported! See this link

Forums Staff recommendations on EOL Ubuntu releases, in particular 10.04 desktop.

1- OK

[COLOR=#0000ff]ubuntu@ubuntu:~$ sudo add-apt-repository ppa:mkusb/ppa[/COLOR]

More info: https://launchpad.net/~mkusb/+archive/ubuntu/ppa

Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keyring `/tmp/tmpb3dyvt/secring.gpg' created
gpg: keyring `/tmp/tmpb3dyvt/pubring.gpg' created
gpg: requesting key 54B8C8AC from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpb3dyvt/trustdb.gpg: trustdb created
gpg: key 54B8C8AC: public key "Launchpad PPA for MKUSB" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
[COLOR=#0000ff]ubuntu@ubuntu:~$  sudo apt-get update[/COLOR]
Ign cdrom://Ubuntu 13.10 _Saucy Salamander_ - Release i386 (20131016.1) saucy InRelease
Ign cdrom://Ubuntu 13.10 _Saucy Salamander_ - Release i386 (20131016.1) saucy/main Translation-en_US
Ign cdrom://Ubuntu 13.10 _Saucy Salamander_ - Release i386 (20131016.1) saucy/main Translation-en
Ign cdrom://Ubuntu 13.10 _Saucy Salamander_ - Release i386 (20131016.1) saucy/restricted Translation-en_US
Ign cdrom://Ubuntu 13.10 _Saucy Salamander_ - Release i386 (20131016.1) saucy/restricted Translation-en
Ign [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy InRelease                                  
Ign [http://ppa.launchpad.net](http://ppa.launchpad.net) saucy InRelease                                   
Ign [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy-updates InRelease                       
Ign [http://ppa.launchpad.net](http://ppa.launchpad.net) saucy Release.gpg 
Ign [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security InRelease
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy Release.gpg
Ign [http://ppa.launchpad.net](http://ppa.launchpad.net) saucy Release     
Hit [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security Release.gpg
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy-updates Release.gpg
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy Release    
Hit [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security Release                 
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy-updates Release                   
Hit [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security/main i386 Packages     
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy/main i386 Packages               
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy/restricted i386 Packages         
Hit [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security/restricted i386 Packages
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy/main Translation-en
Hit [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security/main Translation-en
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy/restricted Translation-en
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy-updates/main i386 Packages
Hit [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy-updates/restricted i386 Packages
Hit [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security/restricted Translation-en
Err [http://ppa.launchpad.net](http://ppa.launchpad.net) saucy/main i386 Packages                
[COLOR=#ff0000]  404  Not Found[/COLOR]
Ign [http://ppa.launchpad.net](http://ppa.launchpad.net) saucy/main Translation-en_US            
Ign [http://ppa.launchpad.net](http://ppa.launchpad.net) saucy/main Translation-en               
Ign [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy/main Translation-en_US
Ign [http://archive.ubuntu.com](http://archive.ubuntu.com) saucy/restricted Translation-en_US
Ign [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security/main Translation-en_US
Ign [http://security.ubuntu.com](http://security.ubuntu.com) saucy-security/restricted Translation-en_US
W: Failed to fetch [http://ppa.launchpad.net/mkusb/ppa/ubuntu/dists/saucy/main/binary-i386/Packages](http://ppa.launchpad.net/mkusb/ppa/ubuntu/dists/saucy/main/binary-i386/Packages)  404  Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.

[COLOR=#0000ff]ubuntu@ubuntu:~$ sudo apt-get install mkusb[/COLOR]
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package mkusb
ubuntu@ubuntu:~$ 

sudodus said:

  1. Please tell me which operating system you are using: Which version and flavour of Ubuntu, 12.04 LTS, 14.04 LTS, 14.10, standard Ubuntu, Kubuntu, Lubuntu, Xubuntu ... ? Or some special version?

[SIZE=3][COLOR=#008000]ubuntu-13.10-desktop-i386.iso [/COLOR][COLOR=#800080]----------------[/COLOR][COLOR=#008000] live(cd)[/COLOR][/SIZE]

#67

The version 13.10 of Ubuntu has passed end of life, and is no longer supported. You cannot expect that it is possible to upgrade and install programs into it.

There is no mkusb PPA version for 13.10. And even worse, there are security risks, because there are no security updates. So please download and try without installing a current version of the Ubuntu family operating systems: Lubuntu, Xubuntu, standard Ubuntu, Ubuntu Gnome and Kubuntu of *versions 12.04 LTS, 14.04.1 LTS*.

There are '1 1/2' exceptions:

  • Lubuntu 12.04 had no LTS (long time support), so it has passed end of life. Try Lubuntu 14.04.1 instead, or LXLE 12.04, which both promise support until April 2017.
  • Xubuntu 12.04 has LTS (long time support) only until April 2015, a very short time. Try Xubuntu14.04.1 instead, which promises support until April 2017.

See these links.

Forums Staff recommendations on EOL Ubuntu releases, in particular 10.04 desktop. [URL="http://ubuntuforums.org/showthread.php?t=2230389"] Try Ubuntu (Kubuntu, Lubuntu, Xubuntu, ...) before installing it[/URL]

#68

[SIZE=4]mkusb-nox[/SIZE][I][B]

mkusb-nox[/B][/I] 'No X' with a crude text based interface has been tested in several distros including Arch linux. It is very simple and straight-forward to use. See the attached files for more details.

More details can be found at https://help.ubuntu.com/community/mkusb/v7

See also this quick start manual for mkusb-nox -o-

If you want more eye-candy, use *mkusb version 9*.

#69

[SIZE=4]mkusb version 9[/SIZE]

is moved to the main (and stable) PPA, and is available via the following command lines

sudo add-apt-repository ppa:mkusb/ppa  # and press Enter
sudo apt-get update
sudo apt-get install mkusb

See the detailed description at https://help.ubuntu.com/community/mkusb

The quick start manual is updated too. See the following link

[URL="http://phillw.net/isos/linux-tools/mkusb/mkUSB-quick-start-manual.pdf"]http://phillw.net/isos/linux-tools/mkusb/mkUSB-quick-start-manual.pdf [/URL]

#70

[SIZE=4]mkusb-bas[/SIZE]

A very basic version of mkusb is made for old and/or very small operating systems (suitable for very old computers and as portable systems). *mkusb-bas* is tweaked to run in TinyCore and Wary Puppy. See this link

https://help.ubuntu.com/community/mkusb/v7#mkusb_version_7.4.x_-_mkusb-bas

#71

[SIZE=4]mkusb version 9.1[/SIZE]

When you reach the window of the first screenshot - Warning and overview, you may think that something will be selected automatically, so you dare not continue with the OK button.

It must be clear, that it is only a warning and overview, you should select drive at the next window.

So I wrote "*Select drive in the next window*" on the button (instead of "OK"). See the attached screenshot!

-o-

The updated mkusb version 9.1 is available now from http://phillw.net/isos/linux-tools/mkusb/ It is also available via *ppa:mkusb/unstable*

#72

[SIZE=4]mkusb and Win32DiskImager[/SIZE]

Now that 14.10 'Utopic Unicorn' is released and has problems with the Startup Disk Creator and Unetbootin, mkusb and Win32DiskImager can be handy tools. Due to their different way to work, they are not affected by the following bug.

[TABLE] [TR] [TD="bgcolor: #CCFF99"][Current issue at the release of Ubuntu 14.10 "Utopic Unicorn"] There are problems with the Startup Disk Creator alias usb-creator and Unetbootin, if you try to create a 14.10 boot drive from a previous version of Ubuntu. See this link to the release notes https://wiki.ubuntu.com/UtopicUnicorn/ReleaseNotes#Boot.2C_installation_and_post-install and https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1325801[/TD] [/TR] [/TABLE]

Until these problems are solved other tools work, for example *mkusb* in linux and *Win32DiskImager* in Windows described in the following links

https://help.ubuntu.com/community/mkusb and

https://wiki.ubuntu.com/Win32DiskImager/iso2usb (a brand new wiki page)

[URL="https://wiki.ubuntu.com/Win32DiskImager/iso2usb"] [/URL]

#73

Update:

Unetbootin works from Ubuntu 12.04.5 and 14.04.1 (can make a working USB boot drive for Ubuntu 14.10), so you can make persistent boot drives using Unetbootin.

But the bug is still there in Startup Disk Creator (tested Nov 1 2014 in 12.04.5 and 14.04.1), if you try to create a 14.10 boot drive.

#74

There are mkusb PPAs ('ppa' and 'unstable') for *Vivid* (Ubuntu 15.04) now. I tested it in a Lubuntu Vivid i386 live session, and it works as it should.

#75

[SIZE=4]mkusb version 9.1.2 and mkusb-nox version 7.5.5 [/SIZE] are uploaded to the [COLOR=#006400]stable[/COLOR] PPA

sudo add-apt-repository ppa:mkusb/[COLOR=#008000]ppa[/COLOR]  # and press Enter
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

[SIZE=4]mkusb version 9.1.3 and mkusb-nox version 7.5.6[/SIZE] are uploaded to the [COLOR=#0000ff]unstable[/COLOR] PPA

sudo add-apt-repository ppa:mkusb/[COLOR=#0000ff]unstable[/COLOR]  # and press Enter
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

[HR][/HR]Several minor improvements and bugfixes are included in these versions. There are also *two packages* now, one for *mkusb* and a separate small one for *mkusb-nox*

#76

[SIZE=4]mkusb version 9.1.4 and mkusb-nox version 7.5.7[/SIZE]

The final text for *wipe-whole-device* is improved:

"Done, but you should also check for the line 'dd: writing '$target': No space left on device', which means that the whole device is wiped. (Look in the terminal window) "

To wipe-whole-device with mkusb is a very special task, that is not recommended except in very special situations. Other tools are better for HDD and SSD devices. mkusb can be a good alternative for USB pendrives to remove private information completely, to make it impossible to recover that information with tools like PhotoRec.

Run this option from the command line

sudo -H mkusb wipe-whole-device

or

sudo mkusb-nox wipe-whole-device
#77

tx it was very helpful..

#78

You are welcome [[COLOR=#000000]Jamsheed_Nabi[/COLOR]]("http://ubuntuforums.org/member.php?u=1959291")

I'm glad it works well for you :-)

#79

[SIZE=4]Ubuntu 12.04 *mini.iso* works also when copied/cloned/flashed by mkusb to USB.[/SIZE]

There are mkusb PPAs for {Ubuntu, Kubuntu, Lubuntu, Xubuntu ...} {12.04 LTS, 14.04 LTS, 14.10, 15.04} alias {precise, trusty, utopic, vivid}. mkusb can make working USB installers also from the Ubuntu mini.iso. See this link.

[COLOR=#800080]New:[/COLOR] You find working mini.iso files for 12.04 LTS (32-bits pae (and non-pae in a subdirectory)) at this link - precise-updates.

#80

[SIZE=4]man mkusb[/SIZE]

The manual page ``` man mkusb

EXAMPLES Make a USB install device from ISO or image file sudo -H mkusb sudo -H mkusb file.iso sudo mkusb-nox file.iso sudo -H mkusb "quote file name (1) with special characters.iso" sudo -H mkusb "path/file.iso" sudo -H mkusb file.img sudo -H mkusb file.img.gz sudo -H mkusb file.img.xz

Install from 'file.img.xz', show all mass storage devices sudo -H mkusb file.img.xz all

Wipe the USB device (may take long time) sudo -H mkusb wipe-whole-device

Wipe the first megabyte (MibiByte), show only USB devices sudo -H mkusb wipe-1

Wipe the first megabyte, show all mass storage devices sudo -H mkusb wipe-1 all

Help and Version mkusb -h mkusb -v


Notice that you need quotes, when you specify the path to the source file as a command line parameter

sudo -H mkusb "path/file.iso"

and

sudo mkusb-nox "path/file.iso"

#81

[SIZE=4]One pendrive for all PC (Intel/AMD) computers[/SIZE]

*mkusb* in linux (or *Win32 Disk Imager* in Windows) can install [URL="http://ubuntuforums.org/showthread.php?t=2259682"] One pendrive for all PC (Intel/AMD) computers[/URL]

from the compressed image file

http://phillw.net/isos/one-button-in...u32-4GB.img.xz

#82

[SIZE=4]New quick start manual for mkusb-nox[/SIZE][I][B]

mkusb-nox[/B][/I] 'No X' with a crude text based interface has been tested in several distros including Arch linux, Debian Wheezy and Debian Jessie. It is very simple and straight-forward to use.

More details can be found at the following links

[URL="https://help.ubuntu.com/community/mkusb/v7"]https://help.ubuntu.com/community/mkusb/v7 [/URL]https://help.ubuntu.com/community/mkusb/v9#from_phillw.net

There is a new version of the quick start manual for mkusb-nox

#83

[SIZE=4]mkusb version 9.1.5 and mkusb-nox version 7.5.8[/SIZE]

There is a bug-fix and a new feature in this new version pair of mkusb/mkusb-nox. (mkusb-bas is not changed.)

  • bug-fix: source=${source##*/} ... to manage path in the parameter (broken by "cd to source file's directory" in 9.1.3)
  • new feature: Clone a device (typically a CD drive or USB drive)
  • new version of the built-in manual
[FONT=courier new]
sudo -H mkusb /dev/sr0    # example of CD drive
man mkusb                 # built-in manual[/FONT]

[HR][/HR]Released in the unstable PPA

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
#84

After looking this tutorial I'm a little bit confused. I was looking for info on how to dual-boot an iBook G4 (394 MB of RAM) with Lubuntu and, since I'm running on OS X when I see this of downloading a PPA file (package) I immediately think of linux (Ubuntu in particular).

Is this mkusb package can be run (adapted to) my laptop?

I guess that since I'm able to run commands from the Terminal and the core of your system (script) is the 'dd' command it's doable here too, am I correct on this?

PS. I already downloaded and checked the MD5SUM of an appropriate mini.iso file and it's standing quietly at the desktop.

Thanks for any info on this! Hope the thread isn't dormant yet...

EDIT: Coming to this thread from https://help.ubuntu.com/community/Installation/MinimalCD#A32-bit_PowerPC.2A.2A

#85

@ benny74402

I know very little about Mac computers. Has your ibook a PowerPC or Intel CPU? You need different versions of the Ubuntu mini or Lubuntu depending on the computer architechture. Furthermore, it is gradually getting harder to run current Ubuntu based systems in ageing PowerPC computers. A text based Ubuntu mini system and maybe Lubuntu should install and work with less than 512 MB RAM. See this link (which is focused on Intel architechture) https://wiki.ubuntu.com/Lubuntu/AdvancedMethods

I suggest that you *start an own thread* at our Ubuntu Forums to get relevant help from people who run Lubuntu in the same kind of Mac computer as yours. A good descriptive title helps interested people find it.

-o-

*mkusb* runs in linux. It uses bash (it is a bash script, that uses some standard linux tools which are available in the main linux distros). So if you already run linux in your Mac computer or another computer, mkusb can be expected to work.

But it does not work in Windows and is not tested in Mac OS (probably does not work). There are some special tools for installing into Mac computers depending on the hardware, and what systems you have already. *Unetbootin* is an alternative. There are a couple of links about installing into Mac

(in the following general link: https://help.ubuntu.com/community/Installation/FromUSBStick#Creating_a_bootable_Ubuntu_USB_flash_drive_from_Mac_OSX)

See How to install Ubuntu on MacBook using USB flash drive and [URL="http://ubuntuforums.org/showthread.php?t=2174630"]this Ubuntu Forum thread by Quackers [/URL]

#86

*mkusb* and *mkusb-nox* are tested and work in Lubuntu *15.04*. I expect them to work in standard Ubuntu and all the flavours Kubuntu, Lubuntu, Xubuntu, Ubuntu Gnome, Ubuntu Mate, Ubuntu Studio, Mythbuntu ... of the currently supported versions 12.04 LTS, 14.04 LTS, 14.10 and *15.04*.

#87

[SIZE=4]mkusb version 9.1.6

[/SIZE]The icons are located according to

http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html#install_icons

which should make it easier to make it work in various linux distros.

#88

These systems are downloaded as compressed image files and installed via *mkusb*

One pendrive for all PC (Intel/AMD) computers - Ubuntu 64-bit and Lubuntu 32-bit

There are methods now to make 32-bit Ubuntu family operating systems boot in UEFI mode via grub and iso files, 'grub-n-iso'. This makes it possible to make a USB pendrive with persistence, that is very portable between different computers :-)

A smaller and simpler pendrive for all PC (Intel/AMD) computers - 'grub-n-iso' - Lubuntu 32-bit

Multiboot pendrive system for all PC (Intel/AMD) computers

-o-

The system with compressed image files makes it easy for a beginner to install, but it is rather inflexible. So I made a shell-script, that does the main part of the work with the help of a couple of files for the configuration of the booting system. See this link

Build your own single boot or multiboot pendrive for all PC (Intel/AMD) computers

#89

[SIZE=4]mkusb 9.2 and mkusb-nox 7.5.9[/SIZE]

This version tries to unmount only usb drives when usbonly and does not try to unmount drives in fstab. In other words, it avoids unmounting partitions in drives, when not necessary for testing which is a suitable target drive.

It is a rather big change of sensitive parts in the shell-script code, so it will be tested for a while (and is uploaded to the unstable PPA and to phillw.net). See this link

https://help.ubuntu.com/community/mkusb/v9#Installation

#90

I have prepared a new version of the shell-script *mk-grub-n-iso* and a new shell-script *links2check*. This will offer a new possibility to make a multiboot pendrive with the same properties as described earlier in this thread: they work in (almost) all PC computers. With and without UEFI independent of 32-bit/64-bit! The systems works in old computers too (they must be powerful enough to run with Lubuntu).

You will be able to *manage the daily built iso files* of the Ubuntu family flavours, to install and update them incrementally directly in the pendrive, which saves time and effort. So it should be a convenient tool for all you iso-testers as well as for those of you who want to *try the bleeding edge version in real hardware* and not only in virtual machines.

As usual, it is a convenient option to download a compressed image file and install it with *mkusb*. Using *mk-grub-n-iso* will give you more flexibility. The choice is yours.

See the following posts (in the thread One pendrive for all PC (Intel/AMD) computers)

Build your own single boot or multiboot pendrive for all PC (Intel/AMD) computers

Create or download a portable system with a small footprint with a potential for isotesting

Manage the daily built iso files of your choice

#91

In order to help beginners to avoid mistakes I write this warning: *mkusb* will overwrite the the USB pendrive that you are using. Previous file systems, directories and files will not be available. After using the pendrive for this purpose (boot a live linux system and/or install a linux system), you can make a new partition table and file system and use the pendrive for storage and transfer of files again.

[SIZE=4]Warning about overwriting the target device[/SIZE]

mkusb will 'use the whole device', actually only the head end (size of the iso file), but the rest of the device is not available. mkusb simply clones the ISO 9660 file system with its content from the iso file. This ISO 9660 file system works from CD/DVD disks, and also from USB drives. After using a USB pendrive like this, you make a new partition table and file system, if you want to use it for another purpose.

[SIZE=4]Help selecting the correct target device[/SIZE]

The crucial task of mkusb was and is to help selecting the correct device and avoid overwriting other devices.

#92

[SIZE=4]mkusb 9.2.1 and mkusb-nox 7.5.9[/SIZE]

Two minor tweaks were made

  • removed 2 lines (<img class ...) from arrow= for a new html renderer in zenity 3.16.2
  • changed the identification of livedrive=$(df |grep /$|cut -c 5-8)

and after testing 9.2 for a month it is ready for the stable PPA, ppa:mkusb/ppa

#93

Two things to mention if I may. I am from Canada and so we are bilingual country. I speak and write mostly english and I just wanted to post two screenshots with constructuve comments.

The first screenshot asks for a password through terminal. Why does it not use policy tool kit like other programs?

The second screenshot shows opening screen and in all my training I see Font violation with CAPITAL letters about warning (circled in green). Also colour *red* is used more or less when describing procedure to remove malware from MS Windows...so it jumps out at me so to speak and I get apprehensive to use it.

Just kind suggestion .. we know it works well and we know it is experimental and we know there are risks but is not just one warning *font* enough?

#94

Thanks for the feedback, ventrical :-)

  1. The password terminal is like this in order to be as general as possible in order to work with one bash script file for several linux distros with as few tweaks (if statements to activate special code for a particular distro). There might be better methods, but that is the reason. (I'm using sudo -H to avoid problems with root ownership in the home directory.)
  1. There is a balance between more or less warnings. A couple of weeks ago was the latest time I had a message from a concerned user, that there are too few warnings. There was a beginner who overwrote his files - he had expected them to survive alongside the image of the iso file. I could change 'WARNING' to 'Warning', which is not yelling, but I have had so much feedback telling me to have big warning signs (yes plural) :-P

I'll think about it once more ...

#95

sudodus said: Thanks for the feedback, ventrical :-)

  1. The password terminal is like this in order to be as general as possible in order to work with one bash script file for several linux distros with as few tweaks (if statements to activate special code for a particular distro). There might be better methods, but that is the reason. (I'm using sudo -H to avoid problems with root ownership in the home directory.)
  1. There is a balance between more or less warnings. A couple of weeks ago was the latest time I had a message from a concerned user, that there are too few warnings. There was a beginner who overwrote his files - he had expected them to survive alongside the image of the iso file. I could change 'WARNING' to 'Warning', which is not yelling, but I have had so much feedback telling me to have big warning signs (yes plural) :-P

I'll think about it once more ...

Ok ... sudo -H , fair enough. Understood.

2.I can see from your explanation that others may need these warning texts. I am not critiquing your method. Sometimes style and ambiance can reflect that a developer has more confidence in their program... ummm what I am trying to say is perhaps a gentler warning as the script reaches it's STOP state waiting for input, ie;

'Please make sure the target drive is the USB drive.' <continue>(y/n)

Regards..

#96

Yes, I see your point, and I use English as a foreign language - so it is wise to listen to you, who use English as a native language. I have some time during this weekend to think about it and try to change to look and feel of the warning texts.

#97

sudodus said: Yes, I see your point, and I use English as a foreign language - so it is wise to listen to you, who use English as a native language. I have some time during this weekend to think about it and try to change to look and feel of the warning texts.

Yes. You got it right . "look and feel". Although not all that important to the core, it is important to the instructional development aspect.

Thank you for your considerations.

Regards..

#98

[SIZE=4]ToriOS beta compressed image file[/SIZE]

ToriOS can be installed with mkusb, for example into a pendrive of at least 8 GB from the following compressed image file. It can also be installed into an internal drive, but notice that it will overwrite all previous content of the drive. *This method is very simple and straight-forward*, but cannot create dual boot systems in the same drive. However, with two drives you get a dual boot system (and one drive can be external).

dd_ToriOS-LubuCore-pae-OEM_precise_7.8GB.img.xz

You can also use the corresponding tarball with ToriOS (the same beta version) updated from the repositories yesterday (July 30, 2015).

ToriOS-pae-OEM_prec_use-by-OBI-in-trusty.tar.xz

This tarball was made with zmktbl in the One Button Installer, OBI, version 3.1, and it can be installed with the same version of the OBI. *The OBI can install systems alongside existing operating systems and create dual-boot and multi-boot systems.*

-o-

ToriOS is installed in OEM mode, and should work well in old and middle-aged computers. It is a 32-bit system and the installation method works in BIOS mode. Use another linux distro and other installation method to install in UEFI mode (for example a 64-bit version of an Ubuntu flavour and mkusb).

Both of these images (the tarball and the compressed image file) are made from an OEM system, where Lubuntu Core was installed in order to help the system for final installation (ubiquity) render the graphical user interface correctly. However, you should *focus on ToriOS*. (Do not use the Lubuntu session, because it has passed end of life and receives no security updates).

#99

@ ventrical,

What about the attached screenshots of mkusb windows? (Legacy is the fallback when zenity is not compiled with webkit, so there is no rendering of html).

  1. Do you suggest further changes to some of these four windows?
  1. Is there any more window, where you think that the text should be changed?

-o-

I intend to move this dialogue to the thread where it belongs, Howto make USB boot drives

Edit: added attachment 'Final Checkpoint' with orange background.

#100

mkusb is prepared to start installing the operating system <osname>

may be better put ->

mkusb is ready to restore/copy the image file <osname>

but it seems no one else is having problems with your language or themes.

Regards..

Welcome and Warning , Final Warning... etc.. could it be better put if you used <notice> instead.. ie;

Welcome and Notice/Disclaimer, Final Notice/Disclaimer.

Regards.

The background painted red in screenshot three is hard on the eyes. Is there another, more smoother colour you could use?

Regards.

For example .. the screenshots in this previous post represent a theme that are much more unobtrusive and although the content is almost the same it is easier to understand.

http://ubuntuforums.org/showthread.php?t=1958073&page=5&p=13076377#post13076377

Regards..

#101

mkusb is prepared to start installing the operating system <osname>

may be better put ->

mkusb is ready to restore/copy the image file <osname>

but it seems no one else is having problems with your language or themes.

Regards..

I'll check it.

Edit: I replaced prepared with ready

Welcome and Warning , Final Warning... etc.. could it be better put if you used <notice> instead.. ie;

Welcome and Notice/Disclaimer, Final Notice/Disclaimer.

Regards.

I'll check that too, where I find the string warning (case insensitive search).

What about Final Checkpoint?

Edit: I replace warning with notice and checkpoint

The background painted red in screenshot three is hard on the eyes. Is there another, more smoother colour you could use?

Regards.

The idea is that the users should wake up and not only continue to click, to make them stop and check a final time. But maybe a [COLOR="#FF8C00"]pale orange[/COLOR] would work, even it is not as strong signal as [COLOR="#FF0000"]red[/COLOR]. But I don't think [COLOR="#0000CD"]blue[/COLOR] will work in this case.

#102

ventrical said: For example .. the screenshots in this previous post represent a theme that are much more unobtrusive and although the content is almost the same it is easier to understand.

http://ubuntuforums.org/showthread.php?t=1958073&page=5&p=13076377#post13076377

Regards..

Those are text mode menus made with *dialog*. I like the dialog style too, but there was feedback, that it looks ancient, and that I had to make a modern graphical style interface to make people even consider using mkusb. *zenity* is available for the same purpose as dialog, and I converted the system to use zenity.

The blue colour is nice, but cannot be used as a warning signal (in my opinion).

#103

I have edited the text (replaced 'Warning' etc) and the background colour for the 'Final Checkpoint' is [COLOR="#FF8C00"]orange[/COLOR]. I don't know if you like it better, but it is an attempt to make it easier on the eyes (less contrast), yet stop the user from clicking automatically without checking. See the attached file (also linked to the previous post with the other screenshots for a quick comparison).

@ ventrical and anybody who has an opinion about it:

Please give feedback about the background colour of the 'Final Checkpoint' :-) And when we have converged to a colour that works, I'll upload mkusb for you in order to read carefully all possible window texts.

#104

sudodus said: I'll check it.

Edit: I replaced prepared with ready

I'll check that too, where I find the string warning (case insensitive search).

What about Final Checkpoint?

Edit: I replace warning with notice and [B]checkpoint

[/B] Because of the way you have the core module of your script set up - Final Checkpoint will work. Others may use Final Step , but, because of the possibility of overwriting an hdd unintentionally, *checkpoint* works. At least as I see it from my own chair. My point is that it is assumed on the greater percentage that most users who are using and experimenting with mkusb already know the pitfalls. For those that do not , the content is such that the pitfalls are self explanatory. Final Caution is another example that can be used. Using the word *warning* multiple times is redundant and does not reflect confidence in the script.

Regards..

#105

sudodus said: I have edited the text (replaced 'Warning' etc) and the background colour for the 'Final Checkpoint' is [COLOR=#FF8C00]orange[/COLOR]. I don't know if you like it better, but it is an attempt to make it easier on the eyes (less contrast), yet stop the user from clicking automatically without checking. See the attached file (also linked to the previous post with the other screenshots for a quick comparison).

@ ventrical and anybody who has an opinion about it:

Please give feedback about the background colour of the 'Final Checkpoint' :-) And when we have converged to a colour that works, I'll upload mkusb for you in order to read carefully all possible window texts.

Yes.. this is very good !![COLOR=#ffd700] [/COLOR][COLOR=#ffd700][/COLOR][COLOR=#ffa500][/COLOR][COLOR=#daa520]Uh but perhaps this may be smoother [/COLOR][COLOR=#000000]as long as it does not create a conflict with your header border colour.

The screenshot you have put up reflects a 'look and feel' of more confidence in the program.

Regards..

[/COLOR]

#106

sudodus said: [COLOR=#FF8C00][/COLOR]

@ ventrical and anybody who has an opinion about it:

Yes, Please wait and see if others have input. There is probably a larger group that might reflect 'if it ain't broke-don't fix it' ! :)

regards..

#107

Just another thing. Please see the screen capture. The *black* background behind the text <Final checkpoint> sort of throws off the harmony of colours that you have established in your GUI. I hope I am not nit-picking :))

edit: Just leave it :) It's fine.

#108

I see what you mean. I made the text on the line with 'Final Checkpoint' black instead of red.

  1. I makes the following line, 'please check again' stand out better.
  1. And I think it makes the inverse video of 'Final Checkpoint' less disturbing - yet attracting the eye ;-)

Edit:

  1. I think you like it better with only bold text Final Checkpoint as in the second attachment.
  1. Now also two blue backgrounds
  1. And a screenshot with orange background and no red text (bold blue text in the final line). Is that what you want?

I put it as the first one, far left, next to the other orange screenshots.

#109

sudodus said: I see what you mean. I made the text on the line with 'Final Checkpoint' black instead of red.

  1. I makes the following line, 'please check again' stand out better.
  1. And I think it makes the inverse video of 'Final Checkpoint' less disturbing - yet attracting the eye ;-)

Edit:

  1. I think you like it better with only bold text Final Checkpoint as in the second attachment.

Ok.. great ! We are on the same page!:)

Now that I have you this far I must go a little further. It is the *red* colour of the last line about the target device. I would like to suggest an experiment. See how you use the light-cyan-blue colour to indicate the <target> device in the dialogue box? Then would it not only be logical to use the same <indicator> colour for the target final notice?

The reason I suggest this is purely only my personal opinion. I had worked for a Austrian firm that dealt with malware and malware removal. One on my duties was to help edit the English content. Also there was a section on malware removal and so most of the times there was a lot of *red* coloured script giving directions on what to do in the event there was an instance of <malware> being detected or a direction of how to remove a particular malware .

In Linux and Ubuntu we do not have to deal with malware as we do with Microsoft Windows Operating Systems. Also my line of thinking goes this way - that new converts from Windows to Linux/Ubuntu might consider such a *red* coloured dialogue box as a sort of malware alert. Since your program is not malware I do not see the reason of why to use the colour *red* as an indicator. I am just saying it may cause an unecessary apprehension in some users of the program. Perhaps it is only me because of my work with anti-malware and it is just maybe the way I see it. But I think I have a good argument logically with colour theme as people will be able to associate the two colours as meaning the same indicators which direct towards the target device. So the actual target device is a smooth cyan blue and such should be the colour of the final notice. Just my opinion.

Regards..

#110

I'll put two blue screenshots into my previous post,

Edit:

and a screenshot with orange background and no red text (bold blue text in the final line). Is that what you want?

The first one, next to the other orange screenshots.

#111

sudodus said: I'll put two blue screenshots into my previous post,

Edit:

and a screenshot with orange background and no red text (bold blue text in the final line). Is that what you want?

The first one, next to the other orange screenshots.

It's not a matter of what I want .. :) .. just what I suggested. It looks a lot more professional - do you not agree?

#112

sudodus said: I'll put two blue screenshots into my previous post,

Edit:

and a screenshot with orange background and no red text (bold blue text in the final line). Is that what you want?

The first one, next to the other orange screenshots.

The red text on light blue has a very good ambiance. In fact it is equal or better than screenshot #1.

#113

This one - very professional look and feel. Also more comprehensive with colour scheme.

Regards..

#114

mkusb is included in ToriOS (that is an ultra-light distro based on Ubuntu 12.04 LTS and jwm). So I asked the ToriOS developers and got this reply via mail.

Hi Nio, I can understand not liking the red, if it is an app you use many times a day. Is this colour determined by HTML in the file? If so, I'd suggest adding something like mkusb -w #ffffff Then for the user they can just change the colour if they don't like it. You can use getopts to easily make options for bash scripts Then just set a variable $warningcolor or whatever. Just an idea...

Personally I think the WARNING should not be easy on the eyes. It SHOULD be jarring and make the user think about it... do I really want to dd this specific drive? The default should be red. It is universally understood as stop/warning/danger.

But, to support your user base, adding a simple option for colour... or maybe adding a config file would be great! I like supporting everything a user could want to do (if I can).

I think it is a good idea to make it easy to configure mkusb's background colour for the 'final checkpoint'. I'll figure a good way to do it. Maybe it can be self-contained (editing the mkusb shellscript file), because the file size should not be changed.

#115

@ ventrical and other people who might be interested in testing the bleeding edge version of mkusb.

I made a tool for a self-contained editor in mkusb (it edits the mkusb shellscript file). The editor is accessed via the help menu. This way the end user can tweak the background colours of the final checkpoints (separate for standard installations and iso-testing). The background for iso-testing should be nicer for the eyes, because it is intended to be used often and by experienced users. See the attached files.

Do you want to try it? This version, mkusb 9.2.2 is uploaded to http://phillw.net/isos/linux-tools/mkusb/.

You must install it via *wget* because it has not reached the unstable PPA yet, I'm waiting for some feedback from you before uploading it to the PPA. The method to get it is described at the following Ubuntu help page

mkusb/v9#from_phillw.net

wget http://phillw.net/isos/linux-tools/mkusb/mkusb-installer

and run it from a terminal window with

bash mkusb-installer
...
[sudo] password:
...
Install via ppa or **wget**, uninstall or quit? (p/w/u/Q) **w**
...

  • Enter your password (installed systems typically require password, but not live systems)
  • Enter w (for wget) and the shell-script will download, check and install mkusb plus some small iso files for testing.
  • Repeat the command bash mkusb-installer if some file was not downloaded correctly.
#116

ventrical said: This one - very professional look and feel. Also more comprehensive with colour scheme.

Regards..

@ ventrical,

Thanks a lot for helping with the language content as well as the style of the text, and also for 'forcing me' to improve the colour scheme :KS

I can see a real improvement when i compare this version (9.2.2) with the previous version.

@ Israel Dahl,

Thanks for the tip to make the background colours of the final checkpoints easy to configure (for the end users) :-)

[HR][/HR] *Edit:* We can also see the results in these links

Compare The old Welcome and warning and A gentler Welcome window

and scroll to view the screenshots at Improved look and feel of mkusb 9.2.2

#117

i already have the ISO image on a 32GB USB memory stick. i'd like to use the remainder of the device for a file system. what is the best way for that?

#118

If you have the image as an image file, you can boot via grub 2 for example according to the following link.

One pendrive for all PC (Intel/AMD) computers - single boot, dual boot, multi boot

You boot from a FAT32 partition and can keep the iso file(s) in an ext partition. You decide if you wish to have a casper-rw partition for persistence or make the FAT32 partition large in order to access it from Windows and store/transfer files. Or you can have a separate large data partition with the file system you prefer.

Edit the partition table with *gparted* to fit your preferences :-)

-o-

Otherwise, if you have copied/cloned/flashed the iso file with its ISO 9660 file system to the pendrive, you must start from the beginning and create a new partition table, because the ISO 9660 file system (including the corresponding partition table) is read only. I have tried but not been able to store anything in the drive space 'behind' such a cloned image.

Pendrives are temporary devices for me - I use them for many purposes, create new partition tables and overwrite the previous content.

#119

[SIZE=4]mkusb version 9.2.3[/SIZE]

There is a small but important change in the version 9.2.3. The background colours that you edit via the help menu are saved in the file /root/.mkusb instead of in-line in the shellscript file. It makes your custom colours survive updates of *mkusb*. Please tell me if you want the file saved in your home directory, even when it is owned by root! That would make your custom colours survive installing new versions of the operating system, if you keep your home directory.

Example: final_check_body_bg is [COLOR="#daa125"]orange[/COLOR] and iso_test_body_bg is [COLOR="#649748"]green[/COLOR]

$ [COLOR="#0000FF"]cat /root/.mkusb[/COLOR]
final_check_body_bg=#daa125
iso_test_body_bg=#649748

while the standard values are [COLOR="#cc0000"]red[/COLOR] and [COLOR="#3580ca"]blue[/COLOR]

$ [COLOR="#0000FF"]grep -m2 -e body_bg $(which mkusb)[/COLOR]
final_check_body_bg='#cc0000'
iso_test_body_bg='#3580ca'
#120

i dd'd the image to the USB memory stick. it boots up OK. i just want to know how to make a data partition on the remaining space. the partition tools don't show anything on the device so i don't know at what sector to start the new partition at.

#121

Till skaparen :-)

I have not managed to do that. I think that when you clone a system (directly via dd or via a GUI tool like mkusb or Disks), you get the ISO 9660 file system, and I think it also somehow includes the head of the drive. Anyway, I have not been able to access the remaining space of a drive with a cloned copy of an ISO file. Sorry about that :-( I would be as happy as you, if someone can show how to do it :-P

If you want to use the whole drive, and use the first part of it to run a live or persistent live system, I suggest that you try a system that boots via grub2 and an iso file (or a multiboot system with several iso files). See this link (posts #6 and most of the following posts). Such a system is easy to edit with *gparted*. Most things work except moving the head of the boot partition - then you have to reinstall grub. So if you want a big FAT32 partition for access from Windows, it is also possible. The first partition (with the file system FAT32) is the boot partition, if you make the pendrive according to that link.

#122

[SIZE=4]mkusb 10.0.1 with a modified grub-n-iso installer added to create persistent live USB drives[/SIZE]

The bleeding edge version 'mkusb 10.0.1' can make persistent live systems for the Ubuntu family of linux. But I would say that the main purpose of mkusb is still to copy/clone/flash iso files and other compressed image files (which does not create persistent live systems).

ToriOS, an ultra-light community re-spin from Ubuntu 12.04 LTS, can even boot persistent live in UEFI mode. The only hickup I have seen is that the mouse does not work in UEFI mode, while it works when booted in BIOS mode. The built-in touchpad works. I do not get this hickup with Ubuntu, at least not with newer Ubuntu flavours (14.04 LTS and newer). It does not mean, that we can or should install ToriOS (32-bit) in UEFI mode, just a statement: ToriOS non-pae can work in UEFI mode :-)

A portable pendrive with ToriOS live and persistent live can run in 'everything' from very old computers without PAE to the new computers with UEFI.

I uploaded this bleeding edge version of mkusb to Phill's server, but not yet to the unstable ppa. And the wiki page mkusb/v9#from_phillw.net needs updating ... with basic facts as well as making a sub-page for version 10 and appropriate links.

I updated the installer, so that you can get it rather easily:

Download the shell-script file 'mkusb-installer' directly with

wget http://phillw.net/isos/linux-tools/mkusb/mkusb-installer

and run

bash mkusb-installer
...
[sudo] password:
...
Install via ppa or wget, uninstall or quit? (p/w/u/Q) w
...
  • Enter your password (installed systems typically require password, but not live systems)
  • Enter w (for wget) and the shell-script will download, check and install mkusb plus some small iso files for testing.
  • Repeat the command bash mkusb-installer if some file was not downloaded correctly.

I would be happy if you can try it and give me some feedback

#123

[SIZE=4]Installing a persistent live Lubuntu with mkusb 10.0.1[/SIZE]

The following screendumps illustrate how to make a persistent live USB pendrive with an Ubuntu flavour with mkusb 10.

Text screen dump of the 'mkusb console':


The mkusb console displays output from the engine behind the zenity curtain
main: usbonly=true
main: liveonly=true
No imput file specified yet
main: source=''
ubuntu
imagefile=/isodevice/lubuntu-14.04.2-desktop-i386.iso
Booted from: /dev/sda
/dev/sda is busy; cannot be unmounted. Close any program that is using
this device if you want to select and use it as a target for mkusb (maybe
change directory if a terminal window is using the partition)!
ans=2
select_device: /isodevice/lubuntu-14.04.2-desktop-i386 /isodevice/lubuntu-14.04.2-desktop-i386.iso /dev/sdb
mount: block device /isodevice/lubuntu-14.04.2-desktop-i386.iso is write-protected, mounting read-only
 Lubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
'/isodevice/lubuntu-14.04.2-desktop-i386.iso' is identified as the source ISO file

MODEL            NAME   FSTYPE  LABEL         MOUNTPOINT   SIZE
ExtremePro       sdb                                     119.2G
                 &#9500;&#9472;sdb1 vfat    ToriOS-daily              59.3G
                 &#9500;&#9472;sdb2 iso9660 torios-live                645M
                 &#9492;&#9472;sdb3 ext4    live-rw                   59.3G

Using the file '/usr/share/mkusb/grub.cfg'
Using the file '/usr/share/mkusb/usb-pack_efi.tar.gz'
Wipe the first megabyte (mibibyte) to get a clean boot area
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.250326 s, 4.2 MB/s

mkfs.fat 3.0.26 (2014-03-07)
mke2fs 1.42.9 (4-Feb-2014)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
5210112 inodes, 20814336 blocks
1040716 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
636 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done   

mount: block device /isodevice/lubuntu-14.04.2-desktop-i386.iso is write-protected, mounting read-only
fatlabel: warning - lowercase labels might not work properly with DOS or Windows
tune2fs 1.42.9 (4-Feb-2014)
tune2fs 1.42.9 (4-Feb-2014)
---------------------------------------------------------------------------
source=/isodevice/lubuntu-14.04.2-desktop-i386.iso
---------------------------------------------------------------------------
UEFI Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
BIOS Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
Copying files ...
./
./boot/
./boot/grub/
./boot/memtest/
./boot/memtest/memtest86+-5.01.bin
./boot/memtest/memtest.bin
./EFI/
./EFI/BOOT/
./EFI/BOOT/bootx64.efi
./EFI/BOOT/bootia32.efi
< /isodevice/lubuntu-14.04.2-desktop-i386.iso pv | dd of=/dev/sdb2 bs=4096
 703MB 0:00:04 [ 142MB/s] [============================================>] 100%            
179968+0 records in
179968+0 records out
737148928 bytes (737 MB) copied, 5.24744 s, 140 MB/s
Syncing the target device ...
MODEL            NAME   FSTYPE  LABEL                    MOUNTPOINT   SIZE
ExtremePro       sdb                                                119.2G
                 &#9500;&#9472;sdb1 vfat    lub1404232                           39.1G
                 &#9500;&#9472;sdb2 iso9660 Lubuntu 14.04.2 LTS i386              712M
                 &#9492;&#9472;sdb3 ext4    casper-rw                            79.4G
Done :-)
The target device is ready to use.
'/isodevice/lubuntu-14.04.2-desktop-i386.iso' was installed

See the attached pictures: The first four pictures illustrate the process to install the system, and the fifth picture shows the installed system running and the output from ``` sudo lsblk -fm

df -h

*Edit:* At this stage mkusb 10 is available via the unstable PPA and phillw.net. See a brief description with more links at mkusb#mkusb_version_10

#124

sudodus said: [SIZE=4]mkusb 10.0.1 with a modified grub-n-iso installer added to create persistent live USB drives[/SIZE]

The bleeding edge version 'mkusb 10.0.1' can make persistent live systems for the Ubuntu family of linux. But I would say that the main purpose of mkusb is still to copy/clone/flash iso files and other compressed image files (which does not create persistent live systems).

ToriOS, an ultra-light community re-spin from Ubuntu 12.04 LTS, can even boot persistent live in UEFI mode. The only hickup I have seen is that the mouse does not work in UEFI mode, while it works when booted in BIOS mode. The built-in touchpad works. I do not get this hickup with Ubuntu, at least not with newer Ubuntu flavours (14.04 LTS and newer). It does not mean, that we can or should install ToriOS (32-bit) in UEFI mode, just a statement: ToriOS non-pae can work in UEFI mode :-)

A portable pendrive with ToriOS live and persistent live can run in 'everything' from very old computers without PAE to the new computers with UEFI.

I uploaded this bleeding edge version of mkusb to Phill's server, but not yet to the unstable ppa. And the wiki page mkusb/v9#from_phillw.net needs updating ... with basic facts as well as making a sub-page for version 10 and appropriate links.

I updated the installer, so that you can get it rather easily:

I would be happy if you can try it and give me some feedback

I'll check it out in a while.


ventrical@ventrical-luntiy-betatest:~$ wget http://phillw.net/isos/linux-tools/mkusb/mkusb-installer
--2015-08-13 10:08:47--  http://phillw.net/isos/linux-tools/mkusb/mkusb-installer
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4528 (4.4K) [text/plain]
Saving to: ‘mkusb-installer’

mkusb-installer     100%[=====================>]   4.42K  --.-KB/s   in 0.01s  

2015-08-13 10:08:47 (379 KB/s) - ‘mkusb-installer’ saved [4528/4528]

ventrical@ventrical-luntiy-betatest:~$ bash mkusb-installer
Current directory:  /home/ventrical
HOME directory:     /home/ventrical
Desktop directory:  /home/ventrical/Desktop
pv needs the 'universe' repository
/usr/bin/wget
file=mk_install-and-test-mkusb.bash
--2015-08-13 10:09:55--  http://phillw.net/isos/linux-tools/mkusb/mk_install-and-test-mkusb.bash
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10394 (10K) [text/plain]
Saving to: ‘mk_install-and-test-mkusb.bash’

mk_install-and-test 100%[=====================>]  10.15K  --.-KB/s   in 0.04s  

2015-08-13 10:09:56 (290 KB/s) - ‘mk_install-and-test-mkusb.bash’ saved [10394/10394]

/usr/bin/sudo
gksudo not installed
Debian Jessie needs gksudo for the desktop file
[sudo] password for ventrical: 
/dev/sda1       74700960 14159216  56724016  20% /
Running with elevated (root alias superuser) permissions
Current directory:  /home/ventrical
User: root
+--------------------------------------------------------------------+
|  Testing only, 'unstable': Install and Test MKUSB in this computer |
+--------------------------------------------------------------------+
You may need to add the repo manually to

/etc/apt/sources.list

Add the line(s), for example if you run trusty,
mkusb is the same for all versions,
but not universe, where you find pv

deb http://ppa.launchpad.net/mkusb/unstable/ubuntu trusty main
deb http://archive.ubuntu.com/ubuntu trusty universe
----------------------------------------------------------------------
Current directory:  /home/ventrical
ubuntu
Install via ppa or wget, uninstall or quit? (p/w/u/Q) w
--2015-08-13 10:11:43--  http://phillw.net/isos/linux-tools/mkusb/md5sum.txt.asc
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2405 (2.3K) [text/plain]
Saving to: ‘md5sum.txt.asc’

md5sum.txt.asc      100%[=====================>]   2.35K  --.-KB/s   in 0.006s 

2015-08-13 10:11:43 (420 KB/s) - ‘md5sum.txt.asc’ saved [2405/2405]

md5sum.txt.asc does not check its own md5sum. But you can
check that it is has a good signature.
-------------------------------------------------------------------------------
gpg: directory `/home/ventrical/.gnupg' created
gpg: new configuration file `/home/ventrical/.gnupg/gpg.conf' created
gpg: WARNING: options in `/home/ventrical/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/home/ventrical/.gnupg/secring.gpg' created
gpg: keyring `/home/ventrical/.gnupg/pubring.gpg' created
gpg: /home/ventrical/.gnupg/trustdb.gpg: trustdb created
gpg: error reading key: public key not found
gpg: requesting key EB0FC2C8 from hkp server pgp.mit.edu
gpg: key EB0FC2C8: public key "Nio Sudden Wiklund (sudodus) <nio.wiklund@gmail.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
-------------------------------------------------------------------------------
gpg: Signature made Wed 12 Aug 2015 12:05:59 PM EDT using RSA key ID EB0FC2C8
gpg: Good signature from "Nio Sudden Wiklund (sudodus) <nio.wiklund@gmail.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 0303 EA77 E34C 52F2 2958  47C6 BD43 C742 EB0F C2C8
-------------------------------------------------------------------------------
mkusb-installer: md5sum OK
mk_install-and-test-mkusb.bash: md5sum OK
--2015-08-13 10:11:44--  http://phillw.net/isos/linux-tools/mkusb/test-images/mini.iso
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 32505856 (31M) [application/octet-stream]
Saving to: ‘mini.iso’

mini.iso            100%[=====================>]  31.00M   259KB/s   in 2m 8s  

2015-08-13 10:13:53 (248 KB/s) - ‘mini.iso’ saved [32505856/32505856]

mini.iso: md5sum OK
--2015-08-13 10:13:53--  http://phillw.net/isos/linux-tools/mkusb/test-images/TinyCore-5.4.iso
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14680064 (14M) [application/octet-stream]
Saving to: ‘TinyCore-5.4.iso’

TinyCore-5.4.iso    100%[=====================>]  14.00M   257KB/s   in 58s    

2015-08-13 10:14:51 (248 KB/s) - ‘TinyCore-5.4.iso’ saved [14680064/14680064]

TinyCore-5.4.iso: md5sum OK
--2015-08-13 10:14:51--  http://phillw.net/isos/linux-tools/mkusb/mkusb_sdir/grub.cfg
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 619 [text/plain]
Saving to: ‘grub.cfg’

grub.cfg            100%[=====================>]     619  --.-KB/s   in 0s     

2015-08-13 10:14:57 (193 MB/s) - ‘grub.cfg’ saved [619/619]

grub.cfg: md5sum OK
--2015-08-13 10:14:57--  http://phillw.net/isos/linux-tools/mkusb/mkusb_sdir/maybe-problems.txt
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1865 (1.8K) [text/plain]
Saving to: ‘maybe-problems.txt’

maybe-problems.txt  100%[=====================>]   1.82K  --.-KB/s   in 0.002s 

2015-08-13 10:14:58 (1.11 MB/s) - ‘maybe-problems.txt’ saved [1865/1865]

maybe-problems.txt: md5sum OK
--2015-08-13 10:14:58--  http://phillw.net/isos/linux-tools/mkusb/mkusb_sdir/usb-pack_efi.tar.gz
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 687655 (672K) [application/x-gzip]
Saving to: ‘usb-pack_efi.tar.gz’

usb-pack_efi.tar.gz 100%[=====================>] 671.54K  79.5KB/s   in 8.7s   

2015-08-13 10:15:07 (76.8 KB/s) - ‘usb-pack_efi.tar.gz’ saved [687655/687655]

usb-pack_efi.tar.gz: md5sum OK
--2015-08-13 10:15:07--  http://phillw.net/isos/linux-tools/mkusb/mkusb
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 92468 (90K) [text/plain]
Saving to: ‘mkusb’

mkusb               100%[=====================>]  90.30K  22.5KB/s   in 4.0s   

2015-08-13 10:15:14 (22.5 KB/s) - ‘mkusb’ saved [92468/92468]

mkusb: md5sum OK
--2015-08-13 10:15:14--  http://phillw.net/isos/linux-tools/mkusb/mkusb-nox
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 25921 (25K) [text/plain]
Saving to: ‘mkusb-nox’

mkusb-nox           100%[=====================>]  25.31K  26.6KB/s   in 1.0s   

2015-08-13 10:15:17 (26.6 KB/s) - ‘mkusb-nox’ saved [25921/25921]

mkusb-nox: md5sum OK
Install if necessary the help packages pv xterm zenity wmctrl
pv and wmctrl need the 'universe' repository
Reading package lists... Done
Building dependency tree       
Reading state information... Done
xterm is already the newest version.
zenity is already the newest version.
The following packages were automatically installed and are no longer required:
  linux-headers-3.19.0-10 linux-headers-3.19.0-10-generic
  linux-headers-3.19.0-15 linux-headers-3.19.0-15-generic
  linux-headers-3.19.0-16 linux-headers-3.19.0-16-generic
  linux-headers-3.19.0-22 linux-headers-3.19.0-22-generic
  linux-image-3.19.0-10-generic linux-image-3.19.0-15-generic
  linux-image-3.19.0-16-generic linux-image-3.19.0-22-generic
  linux-image-extra-3.19.0-10-generic linux-image-extra-3.19.0-15-generic
  linux-image-extra-3.19.0-16-generic linux-image-extra-3.19.0-22-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  pv wmctrl
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 68.5 kB of archives.
After this operation, 251 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ca.archive.ubuntu.com/ubuntu/ wily/universe pv amd64 1.6.0-1 [46.8 kB]
Get:2 http://ca.archive.ubuntu.com/ubuntu/ wily/universe wmctrl amd64 1.07-7 [21.8 kB]
Fetched 68.5 kB in 12s (5,377 B/s)                                             
Selecting previously unselected package pv.
(Reading database ... 327162 files and directories currently installed.)
Preparing to unpack .../archives/pv_1.6.0-1_amd64.deb ...
Unpacking pv (1.6.0-1) ...
Selecting previously unselected package wmctrl.
Preparing to unpack .../wmctrl_1.07-7_amd64.deb ...
Unpacking wmctrl (1.07-7) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up pv (1.6.0-1) ...
Setting up wmctrl (1.07-7) ...
--2015-08-13 10:16:15--  http://phillw.net/isos/linux-tools/mkusb/mkusb.desktop
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 499 [text/plain]
Saving to: ‘mkusb.desktop’

mkusb.desktop       100%[=====================>]     499  --.-KB/s   in 0s     

2015-08-13 10:16:15 (113 MB/s) - ‘mkusb.desktop’ saved [499/499]

mkusb.desktop: md5sum OK
--2015-08-13 10:16:16--  http://phillw.net/isos/linux-tools/mkusb/mkusb.svg
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7841 (7.7K) [image/svg+xml]
Saving to: ‘mkusb.svg’

mkusb.svg           100%[=====================>]   7.66K  --.-KB/s   in 0.03s  

2015-08-13 10:16:16 (300 KB/s) - ‘mkusb.svg’ saved [7841/7841]

mkusb.svg: md5sum OK
--2015-08-13 10:16:16--  http://phillw.net/isos/linux-tools/mkusb/mkusb.svg
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7841 (7.7K) [image/svg+xml]
Saving to: ‘mkusb.svg’

mkusb.svg           100%[=====================>]   7.66K  --.-KB/s   in 0.03s  

2015-08-13 10:16:18 (301 KB/s) - ‘mkusb.svg’ saved [7841/7841]

mkusb.svg: md5sum OK
--2015-08-13 10:16:18--  http://phillw.net/isos/linux-tools/mkusb/mkusb.png
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3219 (3.1K) [image/png]
Saving to: ‘mkusb.png’

mkusb.png           100%[=====================>]   3.14K  --.-KB/s   in 0.007s 

2015-08-13 10:16:19 (421 KB/s) - ‘mkusb.png’ saved [3219/3219]

mkusb.png: md5sum OK
--2015-08-13 10:16:19--  http://phillw.net/isos/linux-tools/mkusb/mkusb.8.gz
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2622 (2.6K) [application/x-gzip]
Saving to: ‘mkusb.8.gz’

mkusb.8.gz          100%[=====================>]   2.56K  --.-KB/s   in 0.005s 

2015-08-13 10:16:20 (476 KB/s) - ‘mkusb.8.gz’ saved [2622/2622]

mkusb.8.gz: md5sum OK

Done, test with the following small ISO files in
the directory /home/ventrical
'mini.iso' and 'TinyCore-5.4.iso'

ventrical@ventrical-luntiy-betatest:~$ 
#125

ok... preliminary test seems well..

#126

Will boot USB stick in BIOS mode but my UEFI machine does not detect installed .iso (or USB stick for that matter) when I use F11 menu.

Regards..

#127

Ok .. all is well .. had to use persistence toggle...

#128

Hi ventrical,

You installed the standard way, cloning with dd, which creates a live only image. No pendrive made from Ubuntu 12.04.1 LTS with that method works in UEFI mode. It does not have the configuration to boot that way.

And no alternate iso, server iso or mini.iso works in UEFI mode. Furthermore, alternate ISOs cannot run live at all. They have only a debian installer. I'm glad that you tried, it made that problem visible. You are good at making problems visible, which makes you a good tester :KS

-o-

But if you install the modified grub-n-iso way in a host system with version 14.04 LTS or newer, you will create a persistent live pendrive also from Ubuntu 12.04.1 LTS *desktop* iso, and it should run in UEFI. Select persistent in the main menu and continue according to post #121, or do it from a terminal window.

Double-click on 'Live only selected' and you get 'Persistent selected', or if you start with the command line

sudo -H mkusb ubuntu-12.04.1-desktop-i386.iso p   # p for persistent
#129

ventrical said: Ok .. all is well .. had to use persistence toggle...

This attempt with Mythbuntu looks successful :-) I can't wait for the result, when you try to boot it.

#130

Just absolutely a beautiful piece of work in progress.! That's pretty smart script. I do not have zenity (no colour scheme) but I can read between the lines no prob. It is using USB 2.0 a little faster also.

Simply put - it is booting into UEFI menu on newer Mother board with high degree of reliability. Providing the two options (persistence and live) in GRUB is a real bonus.:)

Regards..

edit: btw .. I am using wily ubuntu-desktop amd64 install to work your new version of mkusb so it is working good on development version.

#131

I'm glad it works well for you to make a persistent live pendrive :-) It is always important that someone else is testing the software, because I do not find everything that can go wrong, and I do not know what can be misunderstood.

Unfortunely the developers forgot to compile zenity with webkit for an update in wily some weeks ago, which makes the zenity windows ugly. I have reported it as a bug and hope it will be fixed before the release.

#132

Tried on some non-UEFI BIOS machines and it is having problems. On one amdx2/6000 processor it will not boot into either and currently I can only get these results on another machine.


mythbuntu@mythbuntu:~$ df -hFilesystem      Size  Used Avail Use% Mounted on
/cow            1.8G   43M  1.7G   3% /
udev            990M  4.0K  990M   1% /dev
tmpfs           201M  1.3M  199M   1% /run
/dev/sdb2       969M  969M     0 100% /cdrom
/dev/loop0      873M  873M     0 100% /rofs
none            4.0K     0  4.0K   0% /sys/fs/cgroup
tmpfs          1001M  204K 1001M   1% /tmp
none            5.0M     0  5.0M   0% /run/lock
none           1001M  208K 1001M   1% /run/shm
none            100M  8.0K  100M   1% /run/user
mythbuntu@mythbuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID:    Ubuntu
Description:    Ubuntu Trusty Tahr (development branch)
Release:    14.04
Codename:    trusty
mythbuntu@mythbuntu:~$ 

mythbuntu@mythbuntu:~$ inxi -Fxz
System:    Host: mythbuntu Kernel: 3.13.0-19-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: Xfce 4.11.4 (Gtk 2.24.22) Distro: Ubuntu 14.04 trusty
Machine:   Mobo: ASUSTeK model: P5B-E version: Rev 1.xx Bios: American Megatrends version: 1807 date: 04/15/2009
CPU:       Dual core Intel Core2 Duo CPU E8400 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 16020.1 
           Clock Speeds: 1: 4005.016 MHz 2: 4005.016 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0 
           X.Org: 1.15.0 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1440x900@59.9hz 
           GLX Renderer: Gallium 0.4 on NVA8 GLX Version: 3.0 Mesa 10.1.0 Direct Rendering: Yes
Audio:     Card-1: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 
           Card-2: NVIDIA High Definition Audio Controller driver: snd_hda_intel bus-ID: 01:00.1 
           Sound: Advanced Linux Sound Architecture ver: k3.13.0-19-generic
Network:   Card: Qualcomm Atheros Attansic L1 Gigabit Ethernet driver: atl1 ver: 2.1.3 bus-ID: 03:00.0
           IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 84.0GB (-) 1: id: /dev/sda model: Hitachi_HDS72168 size: 80.0GB temp: 39C 
           2: id: /dev/sdb model: Name n/a size: 4.0GB temp: 0C 
Partition: ID: / size: 1.8G used: 117M (7%) fs: overlayfs ID: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 37.5C mobo: 35.0C gpu: 34.0 
           Fan Speeds (in rpm): cpu: 4272 psu: 0 sys-1: 0 sys-2: 0 
Info:      Processes: 161 Uptime: 20 min Memory: 441.2/2001.4MB Runlevel: 2 Gcc sys: 4.8.2 
           Client: Shell (bash 4.3.0) inxi: 1.9.17 
mythbuntu@mythbuntu:~$ 


This will not work:


sudo lsblk -fm

Do I have to install a package from repo?

#133

I have a machine from 2008 with an M2N-VM DVI mobo from ASUS and the processor

AMD Athlon(tm) 64 X2 Dual Core Processor 4400+

which might be similar. I'll test if it works there to boot (from a persistent live pendrive made with mkusb 10).

-o-

I thought that *lsblk* comes with all Ubuntu flavours. It is part of the package util-linux.

#134

sudodus said: I have a machine from 2008 with an M2N-VM DVI mobo from ASUS and the processor

AMD Athlon(tm) 64 X2 Dual Core Processor 4400+

which might be similar. I'll test if it works there to boot (from a persistent live pendrive made with mkusb 10).

-o-

I thought that *lsblk* comes with all Ubuntu flavours. It is part of the package util-linux.

The version of mythubuntu 14.04 I am using is like the first alpha:) so it is very unstable. I plan to restore a more current image of 15.10 and then use that for testing. Also it could be hardware problem on my end. I will check this later.

lsblk not working may be due to unstable ubuntu version.

#135

I just downloaded ubuntu-12.04.1-desktop-i386.iso and made a persistent live pendrive.

*1. In my Toshiba with Intel i5*

I can boot in BIOS and UEFI mode from this persistent live pendrive. I get the same hickup as with ToriOS: the mouse does not work, but the touchpad works with UEFI. I think it is the mouse driver, that works only in BIOS mode for some reason. The kernel is older than the computer and mouse (my Toshiba with UEFI was bought in April 2013).

uname -a
Linux ubuntu 3.2.0-29-generic-pae #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 i686 i686 i386 GNU/Linux

*2. In my computer that was delivered with Ubuntu 7.10 (Gutsy) from GGS data in Gothenburg*

I bought that computer just before Hardy was released. It has an M2N-VM DVI mobo from ASUS and the processor AMD Athlon(tm) 64 X2 Dual Core Processor 4400+

I get the same problem as you with *lsblk -fm*, and I think I know the problem. It is looking for a floppy during a very long time. This happens with some distros and versions in some computers. It is possible to blacklist the floppy and get rid of the problem. A temporary solution, that solves the problem for me is

sudo lsblk -fm /dev/sd?
#136

Ok.. I tried a different USB port and it booted just fine.

I am still using freshly made 14.04 mythubuntu spin.


mythbuntu@mythbuntu:~$ sudo lsblk -fm /dev/sd?
NAME    FSTYPE  LABEL           MOUNTPOINT NAME      SIZE OWNER GROUP MODE
sda                                        sda       3.7G root  disk  brw-rw----
&#9500;&#9472;sda1  vfat    trusty64                   &#9500;&#9472;sda1    959M root  disk  brw-rw----
&#9500;&#9472;sda2  iso9660 Mythbuntu 14.04 LTS amd64
                                /cdrom     &#9500;&#9472;sda2    979M root  disk  brw-rw----
&#9492;&#9472;sda3  ext4    casper-rw                  &#9492;&#9472;sda3    1.8G root  disk  brw-rw----
sdb                                        sdb     465.8G root  disk  brw-rw----
&#9500;&#9472;sdb1  ext4                               &#9500;&#9472;sdb1  119.9G root  disk  brw-rw----
&#9500;&#9472;sdb2                                     &#9500;&#9472;sdb2      1K root  disk  brw-rw----
&#9500;&#9472;sdb5  swap                    [SWAP]     &#9500;&#9472;sdb5    2.2G root  disk  brw-rw----
&#9500;&#9472;sdb6  ext4                               &#9500;&#9472;sdb6  116.6G root  disk  brw-rw----
&#9500;&#9472;sdb7  swap                    [SWAP]     &#9500;&#9472;sdb7    696M root  disk  brw-rw----
&#9500;&#9472;sdb8  ext4                               &#9500;&#9472;sdb8   64.1G root  disk  brw-rw----
&#9500;&#9472;sdb9  swap                    [SWAP]     &#9500;&#9472;sdb9    759M root  disk  brw-rw----
&#9500;&#9472;sdb10 swap                    [SWAP]     &#9500;&#9472;sdb10   766M root  disk  brw-rw----
&#9500;&#9472;sdb11 ext4                               &#9500;&#9472;sdb11   110G root  disk  brw-rw----
&#9492;&#9472;sdb12 btrfs                              &#9492;&#9472;sdb12  50.8G root  disk  brw-rw----
mythbuntu@mythbuntu:~$ inxi -Fxz
System:    Host: mythbuntu Kernel: 3.13.0-19-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: Xfce 4.11.4 (Gtk 2.24.22) Distro: Ubuntu 14.04 trusty
Machine:   Mobo: ASUSTeK model: M2N-MX SE version: Rev x.xx Bios: American Megatrends version: 0308 date: 07/10/2007
CPU:       Dual core AMD Athlon 64 X2 6000+ (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 svm) bmips: 12054.6 
           Clock Speeds: 1: 3013.643 MHz 2: 3013.643 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 02:00.0 
           X.Org: 1.15.0 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1440x900@59.9hz 
           GLX Renderer: Gallium 0.4 on NVA8 GLX Version: 3.0 Mesa 10.1.0 Direct Rendering: Yes
Audio:     Card-1: NVIDIA MCP61 High Definition Audio driver: snd_hda_intel bus-ID: 00:05.0 
           Card-2: NVIDIA High Definition Audio Controller driver: snd_hda_intel bus-ID: 02:00.1 
           Sound: Advanced Linux Sound Architecture ver: k3.13.0-19-generic
Network:   Card-1: NVIDIA MCP61 Ethernet driver: forcedeth port: d480 bus-ID: 00:07.0
           IF: eth2 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-2: Qualcomm Atheros AR5212/AR5213 Wireless Network Adapter driver: ath5k bus-ID: 01:07.0
           IF: wlan0 state: down mac: <filter>
Drives:    HDD Total Size: 504.1GB (-) 1: id: /dev/sdb model: ST3500418AS size: 500.1GB temp: 25C 
           2: id: /dev/sda model: Name n/a size: 4.0GB temp: 0C 
Partition: ID: / size: 1.8G used: 102M (6%) fs: overlayfs ID: swap-1 size: 0.80GB used: 0.00GB (0%) fs: swap 
           ID: swap-2 size: 2.36GB used: 0.00GB (0%) fs: swap ID: swap-3 size: 0.73GB used: 0.00GB (0%) fs: swap 
           ID: swap-4 size: 0.80GB used: 0.00GB (0%) fs: swap 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 34.0C mobo: 31.0C gpu: 33.0 
           Fan Speeds (in rpm): cpu: 3629 sys-1: 4623 
Info:      Processes: 156 Uptime: 6 min Memory: 327.0/993.8MB Runlevel: 2 Gcc sys: 4.8.2 
           Client: Shell (bash 4.3.0) inxi: 1.9.17 
mythbuntu@mythbuntu:~$ 
#137

Yes, it seems to have persistence, because the size of /cow mounted on / matches the size of casper-rw

df -h:

/cow            1.8G   43M  1.7G   3% /

sudo lsblk -fm /dev/sd?:

&#9492;&#9472;sda3  ext4    casper-rw                  &#9492;&#9472;sda3    1.8G root  disk  brw-rw----

I guess that you have changed or added something (for example created a file in a terminal window) and checked that it survives a reboot.

#138

This method with grub 2 works also in HP computers that often refuse to boot from USB via grub, in other words from installed linux systems. I have found that a boot flag on the boot partition helps (even though it is not supposed to be necessary). And I don't think it confuses the other computers that boot happily from USB via grub without a boot flag.

#139

sudodus said: Yes, it seems to have persistence, because the size of /cow mounted on / matches the size of casper-rw

df -h:

/cow            1.8G   43M  1.7G   3% /

sudo lsblk -fm /dev/sd?:

&#9492;&#9472;sda3  ext4    casper-rw                  &#9492;&#9472;sda3    1.8G root  disk  brw-rw----

I guess that you have changed or added something (for example created a file in a terminal window) and checked that it survives a reboot.

Yes .. bookmarks in Chrome and installed inxi.

#140

sudodus said: This method with grub 2 works also in HP computers that often refuse to boot from USB via grub, ...

That's where Plop on CD or Floppy has come in handy, although there are still yet some that are even stubborn enough where Plop will not even boot them.

#141

ventrical said: This method with grub 2 works also in HP computers that often refuse to boot from USB via grub, ...

That's where Plop on CD or Floppy has come in handy, although there are still yet some that are even stubborn enough where Plop will not even boot them.

I think it is worthwhile to increase the percentage of computers that work with mkusb. But you are right. We will always need more than one method in order to convince even the the most stubborn computers to boot ;-)

#142

[SIZE=4]Fine-tuning in mkusb 10.0.2[/SIZE]

Several improvements were made and some bugs were fixed in mkusb version 10.

  • The output to the user (into the 'mkusb console') is improved, and some bugs with the text in zenity windows are fixed.
  • A screllbar is added to the mkusb console window.
  • mkusb is checking now, that it is called via *sudo -H* (to avoids writing files owned by root into the user's home directory tree).
  • There is a new function that probes the source ISO file to check if it is likely to work to create a persistent live drive from it (Ubuntu based distros), or at least possible to create a system that can use the whole drive to storage of data (Debian based distros).
  • The [sudo] password is entered via a zenity dialogue window instead of into the previous small xterm window.
  • mkusb starts in the user's home directory, but can remember the previously used source file (including its path).
  • The last list in mkhelp (Help -- Help text) is improved:
lsblk -o NAME,MODEL,FSTYPE,LABEL,MOUNTPOINT,SIZE,NAME

This version is tested in installed systems as well as in live and persistent live systems and works best in version 14.04 LTS and newer. (It works in 12.04 LTS too, but cannot create persistent live systems that boot in UEFI mode.)

*mkusb* version 10.0.2 is available only via phillw.net. See a brief description with more links at mkusb#mkusb_version_10

[hr][/hr] *Edit:* Added output, a text screen dump of the console window from an installation of Ubuntu MATE to a persistent live system, and two graphical screenshot pictures

The mkusb console displays output from the engine behind the zenity curtain.
[sudo] password for sudodus: 
Current directory=/home/sudodus
main: usbonly=true
main: liveonly=true
No imput file specified yet
main: source=''
ubuntu
select_source: imagefile=/mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso
imagefile=/mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso
Booted from: /dev/sda
ans=1
mount: blockenhet /mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso är skrivskyddad, monterar som endast läsbar
[COLOR="#006400"]** Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS i386 **[/COLOR]
'/mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso' is identified as the source ISO file

MODEL            NAME   FSTYPE  LABEL                    MOUNTPOINT   SIZE
ExtremePro       sdd                                                119,2G
                 &#9500;&#9472;sdd1 vfat    xub1404132                          100,6G
                 &#9500;&#9472;sdd2 iso9660 Xubuntu 14.04.1 LTS i386              925M
                 &#9492;&#9472;sdd3 ext4    casper-rw                            17,8G

Using the file '/usr/share/mkusb/grub.cfg'
Using the file '/usr/share/mkusb/usb-pack_efi.tar.gz'
Wipe the first megabyte (mibibyte) to get a clean boot area
1024+0 poster in
1024+0 poster ut
1048576 byte (1,0 MB) kopierade, 0,291924 s, 3,6 MB/s

mkfs.fat 3.0.26 (2014-03-07)
mke2fs 1.42.9 (4-Feb-2014)
Filsystemsetikett=
OS-typ: Linux
Blockstorlek=4096 (log=2)
Fragmentstorlek=4096 (log=2)
Kliv=0 block, remsvidd=0 block
5423104 inoder, 21679616 block
1083980 block (5.00%) reserverade för superanvändaren
Första datablock=0
Maximalt antal filsystemsblock=4294967296
662 blockgrupper
32768 block per grupp, 32768 fragment per grupp
8192 inoder per grupp
Superblockkopior lagrade på block: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000

Allokerar grupptabeller: klar                            
Skriver inodstabeller: klar                            
Skapar journal (32768 block): klar
Skriver superblock och filsystemsbokföringsinformation: klar   

mount: blockenhet /mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso är skrivskyddad, monterar som endast läsbar
fatlabel: warning - lowercase labels might not work properly with DOS or Windows
tune2fs 1.42.9 (4-Feb-2014)
tune2fs 1.42.9 (4-Feb-2014)
---------------------------------------------------------------------------
source=/mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso
---------------------------------------------------------------------------
UEFI Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
BIOS Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
Copying files ...
./
./boot/
./boot/grub/
./boot/memtest/
./boot/memtest/memtest86+-5.01.bin
./boot/memtest/memtest.bin
./EFI/
./EFI/BOOT/
./EFI/BOOT/bootx64.efi
./EFI/BOOT/bootia32.efi
< /mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso pv | dd of=/dev/sdd2 bs=4096
1,05GB 0:00:28 [37,3MB/s] [============================================>] 100%            
275536+0 poster in
275536+0 poster ut
1128595456 byte (1,1 GB) kopierade, 39,7362 s, 28,4 MB/s
Syncing the target device ...
MODEL            NAME   FSTYPE  LABEL      MOUNTPOINT   SIZE
ExtremePro       sdd                                  119,2G
                 &#9500;&#9472;sdd1 vfat    umt1404232             35,5G
                 &#9500;&#9472;sdd2 iso9660 MATE_14042              1,1G
                 &#9492;&#9472;sdd3 ext4    casper-rw              82,7G
Done :-)
The target device is ready to use.
'/mnt/multimed-2/CD/ubuntu/14.04/ubuntu-mate-14.04.2-LTS-desktop-i386.iso' was installed
#143

9.2.1 can't write to USB.


$ sudo -H mkusb
ubuntu
imagefile=/tmp/mini.iso
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: block device /tmp/mini.iso is write-protected, mounting read-only
disk_name_type=mini
Ubuntu 15.04. _found_ in iso-file
Ubuntu 15.04. _not_ in any possible target drive
Booted from: /dev/sda
/dev/sdb is busy; in fstab
ans=q

The /dev/sdb is not mounted.


$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda6        28G   23G  3.4G  88% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            4.0G   12K  4.0G   1% /dev
tmpfs           810M  1.3M  809M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            4.0G  8.0M  4.0G   1% /run/shm
none            100M   56K  100M   1% /run/user
cgmfs           100K     0  100K   0% /run/cgmanager/fs
/dev/sda7        92G   53G   35G  61% /home

What is the problem with that fstab? How to fix it?

#144

Welcome to the Ubuntu Forums :-)

There may be a bug. I suggesst that you try with mkusb version 9.2.3 version from the unstable PPA.

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

# if you want mkusb-nox
sudo apt-get install mkusb-nox

# or if you want both mkusb and mkusb-nox
sudo apt-get install mkusb mkusb-nox

Version 9.2.3 is tested quite a lot now, and I think it is time to transfer it to the main PPA.

If the newer version fails too, please help me debug the problem. You can start by posting the content of your fstab file, the output of

cat /etc/fstab

-o-

*Edit*: fstab is a list of partitions, that are 'mounted' and 'swapped on', used for the root partition and swap. There may also be a home partition and some data partition that is mounted via fstab. Maybe you have a partition defined but not mounted now or more likely a swap partition active in /dev/sdb. In that case it should not be used by mkusb. If that is not the case, there might be a bug, and it helps debugging to know the content of fstab.

#145

The following links are updated. They describe how to get and use mkusb 10.

mkusb#mkusb_version_10

mkusb#Persistent_live_systems

The main improvement compared to mkusb 9 is the possibility to select between cloning a live only system and creating a persistent live system.

#146

[SIZE=4]Fine-tuning in mkusb 10.0.3[/SIZE]

The help script mkusb-st2 is improved. The new version is uploaded and available via the unstable PPA and phillw.net

  • *zenity's* warnings are discarded
  • The login in live sessions is made smooth
#147

sudodus said: [SIZE=4]Fine-tuning in mkusb 10.0.3[/SIZE]

The help script mkusb-st2 is improved. The new version is uploaded and available via the unstable PPA and phillw.net

  • *zenity's* warnings are discarded
  • The login in live sessions is made smooth

Nicely done sudodus! Very straight forward GUI, and the first USB tool that I have used that would work for Arch. Another Keeper for Tools in my Arsenal! Glad I finally got around to giving it a go. Kind Regards

#148

Thanks runrickus :-)

Yes, I spent some time to make mkusb work in different linux distros, both as target and host OS. See this link

#149

Thanks to you! Been reading up on that page, Going to see how much this little beauty can do this weekend!:D I also added the the unstable ppa to keep up with your changes.(updates & upgrades) Regards

#150

[SIZE=4]Updated quick start manual for mkusb includes the new features of version 10[/SIZE]

You can download the quick start manual and check the md5sums at this link http://phillw.net/isos/linux-tools/mkusb/

Please refresh the browser it you do not get the manual for mkusb version 10

#151

[SIZE=4]Bug-fixes for Wily Werewolf and ToriOS in mkusb 10.0.4[/SIZE]

The new version is uploaded and available via the unstable PPA and phillw.net.

!. fixes to make it work to create persistent live systems in Wily Werewolf

target --> targ1 to avoid confusion in live systems sync after creating partitions (in 'grub_n_iso') clean the target's partitions because old content may survive: wipe first megabyte of boot and casper-rw partitions

  1. fixes to make it work to create persistent live systems in ToriOS

mkusb needs grub-pc to install 'persistent live' which is checked and the user is prompted to install it, if necessary.

#152

[SIZE=4]Bugfix for Vivid Vervet and general tweaks in mkusb 10.0.5[/SIZE]

  1. grub_n_iso: sync,sleep,lsblk,blkid,df commands added to make the FAT partition mount and check it in a live session of 15.04 (to make persistent live drives in a reliable way)
  1. blkid --> blkid /dev/[f]d?? and lsblk --> lsblk /dev/[f]d? to avoid delay because of searching for floppy

The new version is uploaded and available via the unstable PPA and phillw.net. I think it will soon be ready for the stable PPA, ppa:mkusb/ppa.

#153

It works very well on ver3.USB persistent-live uefi so far.

#154

It is important that when we declare our assumptions and document our work that the argument is clear and succinct- ie;

Persistent selected(toggle live only or persistent live)

It expects the user to fill in the spaces.

Would be more clear if:

Persistent live selected(toggle live only or persistent live)

Regards..

#155

ventrical said: It is important that when we declare our assumptions and document our work that the argument is clear and succinct- ie;

Persistent selected(toggle live only or persistent live)

It expects the user to fill in the spaces.

Would be more clear if:

Persistent live selected(toggle live only or persistent live)

Regards.. +1 Nicely Put.;)

#156

runrickus said: It is important that when we declare our assumptions and document our work that the argument is clear and succinct- ie;

Persistent selected(toggle live only or persistent live)

It expects the user to fill in the spaces.

Would be more clear if:

Persistent live selected(toggle live only or persistent live)

Regards.. +1 Nicely Put.;)

Thanks, these little things can be quite important to make a new user confident or not :-)

I'll change it, but I'll wait with uploading a modified version. Maybe you will find more things to change during this weekend.

#157

sudodus said: Thanks, these little things can be quite important to make a new user confident or not :-)

Those of us with a lot of experience understand mnemonics or truncated arguments quite easily. New users are not so familiar. Thank you for considering this. My comments do not reflect on the core operation of your program which is excellently written. I am just commenting from an instructional development point of view.

I'll change it, but I'll wait with uploading a modified version. Maybe you will find more things to change during this weekend.

I have the ppa installed. Labour Day weekend upon us in the west so there may be slow testing :)

Regards..

#158

ventrical said: Thank you for considering this. My comments do not reflect on the core operation of your program which is excellently written. I am just commenting from an instructional development point of view.

Good point ventrical I could see the possibility of my post coming across a little harsh or critical. I hope it was not taken in that fashion. I always know my intentions are never meant ill, but that said I can see wording might raise a different view. I Too think your program is wonderfully written(coded) and very greatful for your useful efforts and personal time. Thanks & Kind Regards

#159

No worries :-)

I'm asking for feedback in order to improve mkusb. This is what I want: improving the text is important. Your tests are also very useful, because you might try something, that I haven't tested - and you might find a bug.

#160

[SIZE=4]mkusb version 10.0.6 tested and uploaded. The module to create persistent live drives is ready for regular use[/SIZE]

runrickus said: It is important that when we declare our assumptions and document our work that the argument is clear and succinct- ie;

Persistent selected(toggle live only or persistent live)

It expects the user to fill in the spaces.

Would be more clear if:

Persistent live selected(toggle live only or persistent live)

Regards.. +1 Nicely Put.;)

Thanks, these little things can be quite important to make a new user confident or not :-)

I have changed it now, and made a slightly modified version: only this change (Persistent selected --> Persistent live selected) plus some comment in the head of the script and the version number.

After more own testing and your testing, *ventrical* and *runrickus*, I have uploaded the new version, mkusb 10.0.6, to the stable and the unstable PPAs. This means that mkusb's module to create persistent live drives is ready for regular use.

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
# if you want mkusb-nox
sudo apt-get install mkusb-nox
# or if you want both mkusb and mkusb-nox
sudo apt-get install mkusb mkusb-nox

See the following link for more details.

help.ubuntu.com/community/mkusb/gui

#161

runrickus said: Good point ventrical I could see the possibility of my post coming across a little harsh or critical. I hope it was not taken in that fashion.

I always know my intentions are never meant ill, but that said I can see wording might raise a different view. I Too think your program is wonderfully written(coded) and very greatful for your useful efforts and personal time. Thanks & Kind Regards

You have done no bad ! :) It's just me. I used to beta test Mamutu and A-squared antimalware for emsisoft (long ago)and help edit their HTML English help files (they are Austrian company)... so maybe I am just naturally pernickity ,<sp> about English reading comprehension.:)

Regards..

#162

sudodus said: No worries :-)

I'm asking for feedback in order to improve mkusb. This is what I want: improving the text is important. Your tests are also very useful, because you might try something, that I haven't tested - and you might find a bug.

Beautiful!. If I am a noob that is exactly what I am looking for. I do not have to grit my teeth wondering what is going to happen next.

Thanks and ..

Regards..

#163

@ventrical +1 Being [COLOR=#000000]naturally pernickity is what I like the most about your threads.(Takes the guess work out of guessing meanings) Plus you keep me on my toes when I try to take the short way out in helping others. Thanks my friend and Regards[/COLOR]

#164

runrickus said: @ventrical +1

[COLOR=#000000]....I try to take the short way out in helping others. [/COLOR]

Thanks . I needed to hear that. Actually it is one of my failings... hopefully that I can work on..

Regards..

#165

[SIZE=4]mkusb version 10.1.1 has a clean[er] GUI interface[/SIZE]

I have been told, that the 'mkusb console', which is a terminal window, can scare many users from mkusb. I had time, so I made an attempt to modify mkusb to look more like a standard GUI program. Have a look at mkusb version 10.1.1 :-)

*1. Running mkusb from the desktop file (via a menu or file browser)*

There are old and new dialogue windows and new progress windows. At the very end, the user will get a window with what was printed to 'mkusb console' before, but is now redirected to '~/mkusb.log'. See the attached files.

*- Is it a good idea to show ~/mkusb.log like that, or should it be optional (to be selected from a menu instead of having to look at it)?*

*2. Running mkusb from the command line*

It uses the terminal window as the 'mkusb console' like before, but there are also progress windows.

**. Get this version from the unstable PPA*

mkusb 10.1.1 is available from ppa:mkusb/unstable via the following command lines,

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

if you want mkusb-nox

sudo apt-get install mkusb-nox

or if you want both mkusb and mkusb-nox

sudo apt-get install mkusb mkusb-nox

that will install the bleeding edge version of mkusb and/or mkusb-nox (testing new features and bug-fixes).

#166

All I can say is Nice, very Nice. Along with your attachments (the Pictures) should be clear to the majority. By the way I have not had any errors as of yet.(Numerous installs) Thanks sudodus

#167

Thanks runrickus :-)

I'm glad that mkusb is useful for you.

#168

[SIZE=4]mkusb 10.2 has a 'wipe menu' with several useful options[/SIZE]

mkusb is available for testing from phillw.net

  1. Some convenient alternatives are added to wiping

  • s "Standard: create MSDOS partition table with FAT32 partition"
  • b "Big drive: create GUID partition table with NTFS partition"
  • g "General: use 'gparted' to make partition table and partition(s)"
  • a "Advanced: create GUID partition table (skeleton for installing an OS)"
  • f "wipe the First megabyte (mibibyte)"
  • w "wipe the Whole device - consider other options except for special cases"
  1. Command line token 'wipe' short-cut to the wipe menu
sudo -H mkusb wipe
  1. The manual *man mkusb* is updated

Screenshots

#169

Zenity's option to render html works again in Wily. Bug #1478386 is fixed.

This bug was fixed in the package zenity - 3.16.3-1ubuntu3

--------------- zenity (3.16.3-1ubuntu3) wily; urgency=medium

* debian/control.in: build-depends on gnome-common

-- Sebastien Bacher <seb128@ubuntu.com> Thu, 01 Oct 2015 17:04:38 +0200 Changed in zenity (Ubuntu): status: Fix Committed &#8594; Fix Released

This means that mkusb looks good again in Wily (it need not use the workaround 'mkusb-legacy') :-)

#170

[SIZE=4]mkusb 10.3 makes a persistent live system with a GPT partition table and a partition with the NTFS file system for data sharing with Windows.[/SIZE]

You can install it from ppa:mkusb/unstable and from phillw.net. See the following link for more details.

help.ubuntu.com/community/mkusb/gui

As before, mkusb can clone an ISO file to a live-only system but also create a persistent live system that can boot 32-bit and 64-bit Ubuntu family operating systems in BIOS and UEFI mode (but not in secure boot).

Test results with mk-grub-n-iso-s which is built into mkusb version 10

This new version of mkusb makes a GPT partition table and a partition with the NTFS file system for data sharing with Windows. This improves the exchange of data with [computers running] Windows, and it makes it possible to use with huge disks (more than 2 GB).

The following code windows illustrate the partition table.

[hr][/hr] Seen from the system where it is created with mkusb

$ [COLOR="#0000FF"]sudo parted -s /dev/sdd print[/COLOR]
Model: SanDisk ExtremePro (scsi)
Disk /dev/sdd: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Flags
 2      1049kB  2097kB  1049kB               primary  bios_grub
 3      2097kB  66.1MB  64.0MB  fat32        primary  boot
 4      66.1MB  967MB   901MB                primary
 5      967MB   73.4GB  72.4GB  ext4         primary
[COLOR="#B22222"] 1      73.4GB  128GB   54.6GB  ntfs         primary  msftdata[/COLOR]

$ [COLOR="#0000FF"]sudo lsblk -fm /dev/sdd[/COLOR]
NAME   FSTYPE  LABEL              MOUNTPOINT                NAME     SIZE OWNER GROUP MODE
sdd                                                         sdd    119.2G root  disk  brw-rw----
&#9500;&#9472;[COLOR="#B22222"]sdd1 ntfs    usbdata            /media/usbdata            |-sdd1  50.9G root  disk  brw-rw----[/COLOR]
&#9500;&#9472;sdd2                                                      |-sdd2     1M root  disk  brw-rw----
&#9500;&#9472;sdd3 vfat    lubwily32                                    |-sdd3    61M root  disk  brw-rw----
&#9500;&#9472;sdd4 iso9660 Lubuntu 15.10 i386 /media/Lubuntu 15.10 i386 |-sdd4   859M root  disk  brw-rw----
&#9492;&#9472;sdd5 ext4    casper-rw          /media/casper-rw          `-sdd5  67.5G root  disk  brw-rw----

Seen from itself running a persistent live session

lubuntu@lubuntu:~$ [COLOR="#0000FF"]sudo df -h[/COLOR]
Filesystem      Size  Used Avail Use% Mounted on
udev            931M     0  931M   0% /dev
tmpfs           189M  5.3M  184M   3% /run
/dev/sdf4       812M  812M     0 100% /cdrom
/dev/loop0      707M  707M     0 100% /rofs
[COLOR="#B22222"]/cow             67G   77M   63G   1% /[/COLOR]
tmpfs           944M     0  944M   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           944M     0  944M   0% /sys/fs/cgroup
tmpfs           944M  4.0K  944M   1% /tmp
tmpfs           189M  4.0K  189M   1% /run/user/999
[COLOR="#B22222"]/dev/sdf5        67G   77M   63G   1% /media/lubuntu/casper-rw[/COLOR]
/dev/sdf1        51G   88M   51G   1% /media/lubuntu/usbdata

lubuntu@lubuntu:~$ [COLOR="#0000FF"]sudo parted -s /dev/sdf print[/COLOR]
Model: SanDisk ExtremePro (scsi)
Disk /dev/sdf: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 2      1049kB  2097kB  1049kB               primary  bios_grub
 3      2097kB  66.1MB  64.0MB  fat32        primary  boot, esp
 4      66.1MB  967MB   901MB                primary
 5      967MB   73.4GB  72.4GB  ext2         primary
 1      73.4GB  128GB   54.6GB  ntfs         primary  msftdata

lubuntu@lubuntu:~$ [COLOR="#0000FF"]sudo lsblk -fm /dev/sdf[/COLOR]
NAME   FSTYPE  LABEL              UUID                                 MOUNTPOINT               NAME     SIZE OWNER GROUP MODE
sdf                                                                                             sdf    119.2G root  disk  brw-rw----
&#9500;&#9472;sdf1 ntfs    usbdata            1EC82C0A133468EA                     /media/lubuntu/usbdata   &#9500;&#9472;sdf1  50.9G root  disk  brw-rw----
&#9500;&#9472;sdf2                                                                                          &#9500;&#9472;sdf2     1M root  disk  brw-rw----
&#9500;&#9472;sdf3 vfat    lubwily32          1D8E-0F38                                                     &#9500;&#9472;sdf3    61M root  disk  brw-rw----
&#9500;&#9472;sdf4 iso9660 Lubuntu 15.10 i386 2015-10-03-17-30-41-00               /cdrom                   &#9500;&#9472;sdf4   859M root  disk  brw-rw----
&#9492;&#9472;sdf5 ext4    casper-rw          8c2b0f82-3cbe-459e-84de-fed1d750cd88 /media/lubuntu/casper-rw &#9492;&#9472;sdf5  67.5G root  disk  brw-rw---

Seen from Windows:

The usbdata partition is automatically mounted by Windows.

The last partition 'on the drive surface' is *the first partition in the partition table*, and that is what counts for Windows to see it. This trick makes it possible to have the system partitions of the persistent live system near 'the head end of the drive surface', which is an advantage particularly with huge disks. With the GPT partition table this system should work even with a huge USB disk, (exceeding 2 GB).

[hr][/hr] *This version needs testing*. Maybe some bug should be squashed before it can be moved to the stable PPA, ppa:mkusb/ppa. So you are very welcome to test it :-)

#171

[SIZE=4]mkusb 10.3 tested with a 4 TB hard disk drive[/SIZE]

I verified that mkusb can create a persistent live system that uses a 4 TB hard disk drive with a huge usbdata partition with NTFS ( > 3 TB ).

It works like it should with a new 'external box' with eSATA and USB 3. See the attached picture and the following code box with the mkusb console output, mkusb.log. In this extreme example, 184 Gibibytes are allocated for persistence, and 174 Gibibytes are actually available for files (program packages, tweaks and personal data files). The size of the usbdata partition is 3.5 Tibibytes.

(An older box with eSATA and USB 2 could manage more than 2 TB only via eSATA. The persistent live system could boot also via USB, but the huge usbdata partition with NTFS was not available.)


The mkusb console window displays,
or the file ~/mkusb.log contains:
output from the engine behind the zenity curtain.
---------------------------------------------------------------------------
start [mkusb 10.3] @ 2015-10-08 04:13:45 PM
---------------------------------------------------------------------------
Current directory=/home/lubuntu
main: usbonly=true
main: liveonly=true
No input file specified yet
main: source=''
TERM=unknown
ubuntu
---------------------------------------------------------------------------
menu_shell:
select_source: imagefile=/home/lubuntu/Hämtningar/ubuntu-wily-desktop-amd64.iso
---------------------------------------------------------------------------
menu_shell:
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/lubuntu/Hämtningar/ubuntu-wily-desktop-amd64.iso
Booted from: /dev/sdg
/dev/sdg is busy; cannot be unmounted. Close any program that is using
this device if you want to select and use it as a target for mkusb (maybe
change directory if a terminal window is using the partition)!
ans=u
/dev/sdg is busy; cannot be unmounted. Close any program that is using
this device if you want to select and use it as a target for mkusb (maybe
change directory if a terminal window is using the partition)!
ans=2
mount: /dev/loop1 is write-protected, mounting read-only
**Ubuntu 15.10 "Wily Werewolf" - Alpha amd64**
'/home/lubuntu/Hämtningar/ubuntu-wily-desktop-amd64.iso' is identified as the source ISO file
<pre>
MODEL            NAME FSTYPE LABEL MOUNTPOINT  SIZE
[COLOR="#B22222"]WDC WD40EFRX-68W sdb                           3.7T[/COLOR]
</pre>
Using the file '/usr/share/mkusb/grub.cfg'
Using the file '/usr/share/mkusb/usb-pack_efi.tar.gz'
Clean for a GUID partition table
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries.

Command (? for help): This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): 
Command (? for help): 
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
Wipe the first megabyte (mibibyte) to get a clean boot area
1024+0 poster in
1024+0 poster ut
1048576 byte (1.0 MB) kopierade, 0.0359203 s, 29.2 MB/s
---------------------------------------------------------------------------
Selected percentage of remaining space for persistence = 5
---------------------------------------------------------------------------
 
preparing /dev/sdb3  ------------------------------------------------
1024+0 poster in
1024+0 poster ut
1048576 byte (1.0 MB) kopierade, 0.0409623 s, 25.6 MB/s
mkfs.fat 3.0.28 (2015-05-16)
/dev/sdb3 has 255 heads and 63 sectors per track,
hidden sectors 0x1000;
logical sector size is 512,
using 0xf8 media descriptor, with 124928 sectors;
drive number 0x80;
filesystem has 2 32-bit FATs and 1 sector per cluster.
FAT size is 961 sectors, and provides 122974 clusters.
There are 32 reserved sectors.
Volume ID is 6d04e803, no volume label.
 
preparing /dev/sdb1  ------------------------------------------------
1024+0 poster in
1024+0 poster ut
1048576 byte (1.0 MB) kopierade, 0.0390653 s, 26.8 MB/s
Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
Creating root directory (mft record 5)
Creating $MFT (mft record 0)
Creating $MFTMirr (mft record 1)
Creating $LogFile (mft record 2)
Creating $AttrDef (mft record 4)
Creating $Bitmap (mft record 6)
Creating $Boot (mft record 7)
Creating backup boot sector.
Creating $Volume (mft record 3)
Creating $BadClus (mft record 8)
Creating $Secure (mft record 9)
Creating $UpCase (mft record 0xa)
Creating $Extend (mft record 11)
Creating system file (mft record 0xc)
Creating system file (mft record 0xd)
Creating system file (mft record 0xe)
Creating system file (mft record 0xf)
Creating $Quota (mft record 24)
Creating $ObjId (mft record 25)
Creating $Reparse (mft record 26)
Syncing root directory index record.
Syncing $Bitmap.
Syncing $MFT.
Updating $MFTMirr.
Syncing device.
mkntfs completed successfully. Have a nice day.
preparing /dev/sdb5  ------------------------------------------------
1024+0 poster in
1024+0 poster ut
1048576 byte (1.0 MB) kopierade, 0.0385398 s, 27.2 MB/s
mke2fs 1.42.12 (29-Aug-2014)
Skapar ett filsystem med 48820992 4 k-block och 12206080 inoder
Filsystems-UUID: bd3cb6a8-fac7-48d1-9566-2c40ac3e1423
Superblockkopior lagrade på block: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872

Allokerar grupptabeller:    0/1490         klar                            
Skriver inodstabeller:    0/1490         klar                            
Skapar journal (32768 block): klar
Skriver superblock och filsystemsbokföringsinformation:    0/1490  26/1490         klar

mount: /dev/loop1 is write-protected, mounting read-only
tune2fs 1.42.12 (29-Aug-2014)
---------------------------------------------------------------------------
source=/home/lubuntu/Hämtningar/ubuntu-wily-desktop-amd64.iso
---------------------------------------------------------------------------
mount /dev/sdb3 /tmp/tmp.WRMqyweanq
/dev/sdb3          61M    512    61M   1% /tmp/tmp.WRMqyweanq
UEFI Bootloader:  Installerar för i386-pc-plattformar.
Installation avslutad. Inga fel rapporterades.
BIOS Bootloader:  Installerar för i386-pc-plattformar.
Installation avslutad. Inga fel rapporterades.
./
./boot/
./boot/grub/
./boot/memtest/
./boot/memtest/memtest86+-5.01.bin
./boot/memtest/memtest.bin
./EFI/
./EFI/BOOT/
./EFI/BOOT/bootx64.efi
./EFI/BOOT/bootia32.efi
---------------------------------------------------------------------------
do_n_show:
&lt; "/home/lubuntu/Hämtningar/ubuntu-wily-desktop-amd64.iso" pv -n | dd of=/dev/sdb4 bs=4096
 
( < "/home/lubuntu/Hämtningar/ubuntu-wily-desktop-amd64.iso" pv -n | dd of=/dev/sdb4 bs=4096 && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 )
Please wait for sync (flushing file system buffers to the device)
until 'Done' is written ...
'pv %'; 'dd final output'
2
5
8
10
13
16
18
21
24
26
29
32
34
37
40
42
45
48
50
53
56
58
61
64
67
69
72
75
77
80
83
85
88
91
93
96
99
100
307200+0 poster in
307200+0 poster ut
1258291200 byte (1.3 GB) kopierade, 37.8401 s, 33.3 MB/s
Done
do_n_show: Work done
---------------------------------------------------------------------------
Syncing the target device ...
<pre>
parted -s "/dev/sdb" print
Modell: ATA WDC WD40EFRX-68W (scsi)
[COLOR="#B22222"]Disk /dev/sdb: 4001GB[/COLOR]
Sektorstorlek (logisk/fysisk): 512B/4096B
Partitionstabell: [COLOR="#B22222"]gpt[/COLOR]
Disk Flags: 

Nummer  Början  ****    Storlek  Filsystem  Namn     Flaggor
 2      1049kB  2097kB  1049kB              primary  bios_grub
 3      2097kB  66.1MB  64.0MB   fat32      primary  startbar, esp
 4      66.1MB  1374MB  1308MB              primary
 5      1374MB  201GB   200GB    ext2       primary
[COLOR="#B22222"] 1      201GB   4001GB  3799GB   ntfs       primary  msftdata[/COLOR]

lsblk -o MODEL,NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE "/dev/sdb"
MODEL            NAME   FSTYPE  LABEL              MOUNTPOINT   SIZE
WDC WD40EFRX-68W sdb                                            3.7T
[COLOR="#B22222"]                 &#9500;&#9472;sdb1 ntfs    usbdata                         3.5T[/COLOR]
                 &#9500;&#9472;sdb2                                           1M
                 &#9500;&#9472;sdb3 vfat    ubuwily64                        61M
                 &#9500;&#9472;sdb4 iso9660 Ubuntu 15.10 amd64              1.2G
                 &#9492;&#9472;sdb5 ext4    casper-rw                     186.2G
</pre>
Done :-)
The target device is ready to use.
'/home/lubuntu/Hämtningar/ubuntu-wily-desktop-amd64.iso' was installed
Cleanup after mkusb finished :-)
Zenity error log-file 'zerrlog'=/tmp/tmp.2cxDS9uk7w
Cleanup after mkusb finished :-)
---------------------------------------------------------------------------
Total time used [by mkusb] = 244 s; 00:04:04
#172

Hola. . Thanks for a detailed one. . But recentlyi I have installed 15.04 with the help of unetbootin from my ubuntu 12.04. And now am using wiley without any problems except the known freeze then force quit problems. . Can you please enlighten me what could be my priority problem if I installed via unetbootin. .

#173

Hola wasp52dex,

Welcome to the Ubuntu Forums :-)

  1. Unetbootin is not up to date in the Ubuntu repositories. It is best to install it from the developer's PPA. See this link

FromUSBStick#Unetbootin

  1. If the pendrive works (boots successfully into a live system with Ubuntu or an Ubuntu flavour: Kubuntu, Lubuntu, ... Xubuntu), you need not worry. If there are problems to quit (I guess you mean from the live system with Ubuntu) it is a problem between the computer hardware and the drivers of Ubuntu - not a problem of Unetbootin.

I'm testing Wily too, and for me it helps to flush the buffers with the command ``` sync


Is this answering your questions?
#174

Below are the three main screens of mkusb 10.3-1 unstable. I am currently testing so I have no reports atm.

Edit:

If you look at the second image you will see the text:

Ready to update ISO image: Source: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" -Alpha amd64

found in the iso file and found in /dev/sdb Name: usb-09c_1000 Dev:/dev:/sdb Size: 3995MB ---------------------------------------------------------

The second line DOES NOT indicate the SOURCE drive. The particular USB drive in question already had xenial xerus on it (A defunct gnome previous .iso which was not booting). If it *IS* indicating that the source drive is represented then it is making the declaration that the .iso file is in /sdb/ and not from /Downloads where I originally chose the daily/current.iso file. Not to have this included could be very confusing to some.

And also in the first line you should use 'restore' instead of 'update' because most testers who have switch over from using SDC to 'disk' utility method use that 'restore' option as this is the current convention for development version. Although the program itself appears to be stable I would not release it until the declarative statements are corrected.

  1. Include the correct source where the .iso is being restored from.
  2. Replace 'update' with 'restore' as it is the current development convention.

Regards..

#175

I see your points, ventrical, and I agree in one case ;-)

  1. I can add the source file into the text (I did not think it is necessary, but if it can help, it is good.)
  1. But I don't think *restore* is a good word. On the contrary, I think restore is used in a confusing way in gnome-disks.

I think like this: You restore something, that was there before. If you make an image of a drive (for example a backup), and later on copy it back from the backup copy, then you restore it. (Backup <---> Restore)

But in the case of iso-testing, you download or zsync to get a new daily iso file. This iso file is to replace the old one in the pendrive. I would say it is installed or updated, because it is the first time the new daily iso file will be put there. The prefix *re* means again - that it was there before.

Would you be happy if I exchange the last line according to the example in your attached blue picture (#2)?

from

'Install to the device /dev/sdb'

to

'Update the device /dev/sdb'

or to remove all doubt

'Write the data in the iso file to the device /dev/sdb'

or

'Copy/clone from the source iso-file to the device /dev/sdb'

-o-

By the way, have you tested to make a *persistent* live drive?

#176

@ ventrical

What about the attached pictures #1 - 'orig', #2 - 'copy/clone'? *look at the text*, the background colour is my personal tweak ;-)

*Edit:* I added the pictures #3 - copy-clone-flash-burn-restore-ToriOS.png and #4 - copy-clone-flash-burn-restore-Lubuntu.png

There are two modifications

  1. The source file's path is displayed (I also tested with a really long name)
  1. 'Copy/clone/flash/burn/restore' from the source iso-file to the device. I hope this will make you and everybody else happy: pick whichever word you prefer for the process :-)

*Edit 2:* I added the picture #5 - flash-burn-restore-Lubuntu.png.

  1. 'Flash/burn/restore' from the source iso-file to the device
  1. '-- automatic identification' is added after the 'double positive'
#177

sudodus said:

  1. But I don't think *restore* is a good word. On the contrary, I think restore is used in a confusing way in gnome-disks.

I think like this: You restore something, that was there before. If you make an image of a drive (for example a backup), and later on copy it back from the backup copy, then you restore it. (Backup <---> Restore)

But in the case of iso-testing, you download or zsync to get a new daily iso file. This iso file is to replace the old one in the pendrive. I would say it is installed or updated, because it is the first time the new daily iso file will be put there. The prefix *re* means again - that it was there before.

I would originally agree with you about using the 'restore' term as I thought the same way at first but even though it is being 'installed' it is really being 'restored' also TO the USB device because it cannot be booted in a live operating system unless it is with a virtual machine.

My complaint is this - that for the last few cycles since the breakage of SDC we have been using gnome-disks utility which uses the conventional term 'restore' so when we use /mkusb/ utility we again have to make adjustments on the fly to a newer convention term.

So the scenario is this - I am a tester. Period. I first use a tool called SDC. I find several different ways to get it working even when it is broke. Then it finally becomes unreliable in most any situation. I am then presented with an alternative method (using gnome-disks utility) and I am *instructed* to use the *restore* option to install a new .ISO file to USB Flash Disk. I use this option for 2 years and then I am presented with a non-ubuntu script tool from a :ppa that uses the term *install*. Now I know that this is splitting hairs but it is important for person who , lets say, test .ISOs everyday. We just want a straight, clear , cut and dry method to install a bootable .ISO file to a USB stick. Of course we are dealing with several different persons here internationally so we all have a slightly different slant as to how we would interpret the diference between /restore/ and /install/.

So really .. if you decide to use /install/ then it is just something we will have to get used to.

Regards..

#178

sudodus said: ********

Would you be happy if I exchange the last line according to the example in your attached blue picture (#2)?

from

'Install to the device /dev/sdb' ****

It is really not necessary to do so. One of the English definitions of *restore* is 'to bring it to it's original condition'. I think also is why it is used it gnome-disks. Otherwise we could just COPY or MOVE the .ISO file to the USB stick , but, we know this will not work. /Restore/ is a process that correctly configures a donwloaded .ISO file onto a target device so as it will be bootable and functional when a machine is started. We are not actually /installing/ the ISO file to the target device - however .. I respect your disagreement on this.

Regards..

#179

sudodus said: @ ventrical

What about the attached pictures #1 - 'orig', #2 - 'copy/clone'? *look at the text*, the background colour is my personal tweak ;-)

Neither give the source directory.

ie; Source: /sda?/Downloads/myisofile.iso

..so when I am working mkusb I am waiting to verify the source and I am expecting the source directory and file to be echoed back at me as I am moving on to the next screen in the GUI. it is ok for more advanced user because they might find it 'safe to assume' all the argument but for new or intermediate users , they might find it not in the right logical order because you are using a 'double positive' and that 'double-positive' leads one to preclude that the .ISO is being replicated from something already existing on the USB disk.

I recall that you used to have this source option of echo /dev/directory/.iso did you not?

Regards..

#180

Hi again ventrical,

I have uploaded two more screenshots of the 'iso-testing window' with modified text to post #174. so that you can switch easily between the various versions and compare them. I hope that we are converging to something that both of us think is good enough :-)

-o-

By the way, have you tested to make a persistent live drive? This is changed from before, I hope and think it is an improvement:

In the latest version 10.3, at

ppa:mkusb/unstable

I make a GUID partition table and an NTFS partition for exchange with Windows. It is logically the first partition (otherwise Windows does not see it), but physically the last partition, so the things involved in booting is before it. These things manage to boot in UEFI as well as in BIOS mode. It builds on a method developed by Andre Rodovalho. So I think mkusb is a good tool to make USB boot drives with Ubuntu and Ubuntu based distros. The GUID partition table makes it able to work also with huge ( > 2 TB ) USB hard disk drives.

mkusb can be used to wipe and or create new partition tables and file systems after a pendrive has been used for booting/installing and if a pendrive's file system is damaged, or if it is getting close to gridlocking. See this link Pendrive lifetime

#181

Yes ..#3 and #4 are excellent examples.

ok .. and then there is this double positive:

found in the iso file and found in /dev/sdb

ok.. I finally understand what you mean! However .. I offer only my opinion at this stage. I personally feel that this declaration is already 'assumed' in English speaking languages and I would think even a novice would already understand this but the way it is currently worded can be confusing at first. So .. to keep a long story short :) .. this is too much information! It sort of makes one stop in the middle of the flow. Most testers already know that they are wiping their usb drives and that all info will be gone and unrecoverable .. etc.. so .. there is a saying in America that 'less is more' :)

Regards..

#182

*Edit:* I added the pictures #3 - copy-clone-flash-burn-restore-

Choose one! We know we cannot physically copy an ISO to a USB and have it work...uhhh mmm 'flash-burn-restore' works good. I understand that and I think it is a more used common vernacular with NA testers. copy-clone is more 'windowish' I think. :) lol

btw .. have not tested other options as of yet.

Regards..

#183

What I am describing is the automatic identification of the target drive. Do you think that the whole text line should be removed? Or do you mean that there is one too many 'found', so that this is better: 'found in the iso file and in /dev/sdb'

-o-

I think burn is windowish, as much as copy and clone. Anyway you would be happy with 'flash/burn/restore' :-)

-o-

$ which less
/usr/bin/less

:-P

#184

.iso replicated in /dev/sdb

Replicate = exact copy, (to which, would _*infer*_ it being in both source and destination).

:)

#185

Thanks for the tip mikodo :-)

In this case there are different versions of the same *ubuntu version and flavour - typically two consecutive daily iso files, and the user = iso-tester is to overwrite yesterday's version with today's version. So they are not identical [yet] - but the identifying tags are the same, which is used for automatic identification of the target drive.

Yes, I could use *replicate* instead of copy/clone/flash/burn/restore.

#186

I have uploaded a fifth screenshot of the 'iso-testing window' with modified text to post #174. so that you can switch easily between the various versions and compare them. I hope that this is close to what can be used :-)

#187

mikodo said: .iso replicated in /dev/sdb

Replicate = exact copy, (to which, would _*infer*_ it being in both source and destination).

:)

No. And why? Because if it is an exact copy then we can simply use the COPY command from the pulldown menu which , of course, will not create a bootable USB disk ! Replicate would add to confusion. Regards..

#188

sudodus said: What I am describing is the automatic identification of the target drive. Do you think that the whole text line should be removed? Or do you mean that there is one too many 'found', so that this is better: 'found in the iso file and in /dev/sdb'

-o-

I think burn is windowish, as much as copy and clone. Anyway you would be happy with 'flash/burn/restore' :-)

-o-

$ which less
/usr/bin/less

:-P No .. do not remove. Now with '--automatic identification' insert it all makes perfect sense and ties it all together.

  1. Flash/burn/restore = flash/burn/restore :) No need for capitals at this point :) lol

regards..

#189

#5

That looks good to go from my perspective. I live in Centre of Automotive Capital of the World which is upper midwest of NA.. but of course I do not speak for everybody... just what I see and hear in these parts. Someone from London, Rotterdam, Berlin, Dubai, Tokyo or Hong Kong may see it totally different.

Regards..

#190

ventrical said: No .. do not remove. Now with '--automatic identification' insert it all makes perfect sense and ties it all together.

  1. Flash/burn/restore = flash/burn/restore :) No need for capitals at this point :) lol

regards..

OK, with the minor edit F -->f to get 'flash/burn/restore' I can finish polishing the iso-testing window of mkusb.

Thanks ventrical :-)

*Edit:* attached screenshot 'flash-burn-restore-Lubuntu-check.png'

#191

In my Very humble and modest opinion, Works for me. Thanks sudodus

#192

sudodus said: OK, with the minor edit F -->f to get 'flash/burn/restore' I can finish polishing the iso-testing window of mkusb.

Thanks ventrical :-)

*Edit:* attached screenshot 'flash-burn-restore-Lubuntu-check.png'

Excellent! THANK YOU!!

Regards..

#193

runrickus said: In my Very humble and modest opinion, Works for me.

Thanks sudodus +1 :)

#194

Thanks for your positive feedback runrickus and ventrical :-)

#195

Okay. I understand.

On top it says,

Ready to update ISO image

Why not keep the terms on the page the same?

Update the source-iso file to the device /dev/sdd ?

Or,

Write the new source-iso file to the device /dev/sdd ?

Keeps it cleaner.

#196

@ ventrical and runrickus,

The discussion is open again - as you hinted in post #187, ventrical, '.. but of course I do not speak for everybody...'

@ mikodo,

The modified version is not yet uploaded. I'm listening to your advice.

Are you still talking about the same window (as the attached screenshot in post #188), or are you extending the discussion to nearby windows? I realize that the terminology is not the same in the Window after that window, so if you are not extending the discussion, you are inspiring me to do it.

1.

What about the following 'final line'?

Update the source-iso file to the device /dev/sdd ? Write the new source-iso file to the device /dev/sdd ?

or (in order to be quite clear about what is going to happen)

Update (flash/burn/restore) from the new source-iso file to the device /dev/sdd ? Update (flash/burn/restore/clone) from the new source-iso file to the device /dev/sdd ? Re-clone (flash/burn/restore) from the new source-iso file to the device /dev/sdd ?

2.

What about the next window 'Work done'. It is not modified [yet(?)].

... device is re-cloned :-)

See the attached 'Work done orig' screenshot in this post (and for comparison the 'flash/burn/restore' screenshot).

It could be modified to

... device is updated :-)

#197

I apologize, sudodus. I have been working the last while and just saw your response. It's 03:15 here. I'm not in a clear and restful state of mind now to make good decisions.

But, I do think is important to do a few things.

  1. Be consistent within a window with the terminology, when it appropriate to do so.
  2. Use one term, not .../.../.... Pick one that is commonly used in GUI for English. Like "Write" to Disk, that sort of thing.
  3. If terms on the page cannot be the same or between pages because the "actions", are different, use a descriptive term for each. Just try to pick the commonly used terms. Try to think of what people would expect. I would recommend that, using consistency in naming conventions is generally what is expected, when appropriate.

Now, I've shouted my mouth off, when my mind is nearly asleep. :)

Edit:

I looked and yes I was referring to #188 attachment.

To what I like and to answer your explicit questions, here is what I like.

Question 1.

The image on top says:

Ready to update ISO image

then I would choose

Update the source-iso file to the device /dev/sdd ?

Question 2. Next page I would stick with the same convention and choose:

... device is updated.

It's for people using a gui. So, appearance and presentation is important. As in, what Gnome-develops would choose for those users.

That may not necessarily be what the people using the cli would call it but, they would understand and "know" what is being done on cli anyway.

#198

+1

Yes.. ie; just choose 'restore' and not flash/burn/restore. The currently used convention used in development version testing at ubuntuforums when using 'disks' is restore .. so all of us testers know that. You save yourself a lot of pressure by leaning on what is used in current development testing and so multiple choice is not necessary and that is up to end user to learn the current convention and if they do not like it or choose otherwise then that is their free choice to do so. Keep it simple ! :)

Regards..

#199

I think update can be used in such cases for copying as well as flashing/burning/restoring. And I don't like restore, because it means something else for me.

I would like to use *update* consistently, keep it in the title bar, change to it in the last line (replacing flash/burn/restore) and in the next window (replacing device is re-cloned)[B][I]

Edit:[/I][/B] What do you think of the following 'matching pair' of windows? See the attached screenshots :-)

#200

'Update' doesn't work for me .. but that's just me:)

Regards..

#201

The word *update* is not used the 'first' time a certain distro, flavour, version is 'flashed/burned/restored' into a pendrive.

*Update* is used only when another (typically the next) daily file of the same distro, flavour, version is 'flashed/burned/restored' into that pendrive. This is when the automatic identification works, and it is intended for iso-testing.

-o-

The number of clicks *and* the risk to overwrite the wrong drive are reduced during iso-testing.

#202

sudodus said: The word *update* is not used the 'first' time a certain distro, flavour, version is 'flashed/burned/restored' into a pendrive.

*Update* is used only when another (typically the next) daily file of the same distro, flavour, version is 'flashed/burned/restored' into that pendrive. This is when the automatic identification works, and it is intended for iso-testing.

Ahhh.. I see. :) Good work.

Regards..

#203

Don't know for sure, but with all the text changes made here, maybe add a manual. If there is one sorry, I have never needed to check. And I agree with ventrical [B]Good Work!! [/B]&#8203;Best regards

#204

Yes, there is a manual, and help/wiki page too.

mkUSB-quick-start-manual.pdf

mkusb help page

The quick start manual is fairly up to date, but may need some minor fixes after we have finished this testing and discussion :-)

#205

[COLOR=#000000]The quick start manual is fairly up to date, but may need some minor fixes after we have finished this testing and discussion [/COLOR]:smile:

Ah Ha! There she blows.:D Ask and Ye Shall Recive. (No Offense meant)

#206

runrickus said: Ah Ha! There she blows.:D

Ask and Ye Shall Recive. (No Offense meant)

None taken:)

Your friend. Captain Ahab :)

#207

Sudodus

Very craftily written! Nice work. It remembered from the last time where I store my .ISOs in pic #1. or perhaps that is default?

Regards..

#208

ventrical said: None taken:)

Your friend. Captain Ahab :) Whoosh! It is so hard staying Politically Correct these days. Did not want to start another Mutiny on the [FONT=arial] [/FONT]Pequod.:D Sorry off topic

#209

I have only seen the last 5 windows. I don't know if this will be consistent with the others.

Thumbnails found in Ventrical's Post #205:

&#8230;............................................................................................................................

2.

The selected Source was found:

/home/ventrical/Downloads/xenial-desktop-amd64.iso

It has not been installed to a device.

To use it, you must select a new target device, in the next window.

Notice: The target device will be completely overwritten.

Help selecting the target device is, available in the Starter -- Help menu

Please close any applications accessing your target device.

This will ensure that mkusb has exclusive access to it.

&#8230;......................................................................................................................................

3.

The selected iso-file will be installed to your target device.

Installing /home/vertricle/Downloads/Xenial-desktop-amd64.iso to /dev/usb &#8230; &#8230; Done

The device is now unmounted and can be safely unplugged.

Name: usb-090c_1000 Dev: /dev/sdb Size 3995MB

#210

ventrical said: Sudodus

Very craftily written! Nice work. It remembered from the last time where I store my .ISOs in pic #1. or perhaps that is default?

Regards..

Yes, it remembers :-)

cat /usr/share/mkusb/selected
#211

You are right, these windows need modifications as much as the iso-testing window. What about the following text?

mikodo said: I have only seen the last 5 windows. I don't know if this will be consistent with the others.

Thumbnails found in Ventrical's Post #205:

  1. *Notice and overview*

The selected Source was found:

/home/ventrical/Downloads/xenial-desktop-amd64.iso

It has not been installed to a device.

To use it, you must select a new target device, in the next window.

Notice: The target device will be completely overwritten.

Help selecting the target device is, available in the Starter -- Help menu

Please close any applications accessing your target device.

This will ensure that mkusb has exclusive access to it.

The system tag: [COLOR="#2252a0"]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64[/COLOR]

was found in the iso-file [COLOR="#2252a0"]/home/ventrical/Downloads/xenial-desktop-amd64.iso[/COLOR]

To use this system, you must select a target device in the next window. [COLOR="#FF0000"]Notice: The target device will be completely overwritten.[/COLOR]

Help selecting the target device is available in the Starter -- Help menu

[COLOR="#FF0000"]Please close any other applications accessing your target device.[/COLOR] This will ensure that mkusb has exclusive access to it. (Example: A terminal window can prevent unmounting the target device.)

Name: ... ...

Booted from /dev/sda

[Quit] [Select target device in the next window]

  1. *Work done with /dev/sdb*

The selected iso-file will be installed to your target device.

Installing /home/vertricle/Downloads/Xenial-desktop-amd64.iso to /dev/usb … … Done

The device is now unmounted and can be safely unplugged.

Name: usb-090c_1000 Dev: /dev/sdb Size 3995MB

The system: [COLOR="#2252a0"]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64[/color]

in the selected iso-file will be installed to your target device.

[TABLE="class: cms_table"][tr] [td="bgcolor: #b4df02"] Installing /home/vertrical/Downloads/Xenial-desktop-amd64.iso to /dev/usb … … Done [/td][/tr][/table]

The device is unmounted and can be safely unplugged now. [COLOR="#2252a0"]Name: usb-090c_1000 Dev: /dev/sdb Size 3995MB[/color]

[Exit from mkusb] [OK]

#212

Hi. I'll see what I can suggest.

I am going to make notes in the edit.> sudodus said:

*The user already knows, what they have selected from the previous window.

See the previous Window, "Select Source File", (which should be Capitalized as I have).

So, we just tell them mkusb has found it:

[s]The system tag: Found:[/s] [COLOR=#2252a0]

[/COLOR] Found: [COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64.iso[/COLOR]

[s]was found in the iso-file Found: [COLOR=#2252a0]/home/ventrical/Downloads/xenial-desktop-amd64.iso[/COLOR]..[/s]

*Then, simply tell the user, what to do. (They know they want to use that system).

They will see, if they have chosen correctly or not.

[B]Select a target device in the next window: [/B] [s]To use this system, you must select a target device in the next window.[/s] [COLOR=#FF0000]Notice: The target device will be completely overwritten.[/COLOR]

Help selecting the target device is available in the Starter -- Help menu

[COLOR=#FF0000]Please close any other applications accessing your target device.[/COLOR] This will ensure that mkusb has exclusive access to it. (Example: A terminal window can prevent unmounting the target device.)

*I like the example. It reinforces the importance of closing all applications accessing the device. If mksub cannot access the device, this will give the user a "clue", that they still must close, "something" still accessing the device.

Name: ... ...

Booted from /dev/sda .. [Quit] [Select target device in the next window]

*Now again, the user knows what they have selected. Just tell them that mkusb is using it.

[B]Installing: Ubuntu-MATE 16.04 LTS "Xenial Xerus: - Alhpa amd64.iso to /dev/usb ... ... Done [/B] [s]The system: [COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 [/COLOR][COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64[/COLOR] in the selected iso-file will be installed to your target device.[/s] [TABLE="class: cms_table"] [TR] [TD="bgcolor: #b4df02"][s]Installing /home/vertrical/Downloads/Xenial-desktop-amd64.iso to /dev/usb … … Done[/s][/TD] [/TR] [/TABLE]

The device is now unmounted and can be safely unplugged. [s]now.[/s] *I just moved (now) to where it should be. [COLOR=#2252a0]Name: usb-090c_1000 Dev: /dev/sdb Size 3995MB[/COLOR]

[Exit from mkusb] [OK]

#213

Hi. I'll see what I can suggest.

I am going to make notes in the quote.> sudodus said:

*The users already know, what they have selected from the previous window.

See, the previous window, "Select Source File", (which should be "Capitalized").

So, we just tell the users, mkusb has found it:

[s]The system tag: Found:[/s] [COLOR=#2252a0]

[/COLOR] Found: [COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64.iso[/COLOR]

[s]was found in the iso-file Found: [COLOR=#2252a0]/home/ventrical/Downloads/xenial-desktop-amd64.iso[/COLOR]..[/s]

*Then simply, tell the users what to do. (They know, they want to use that system. They can see, if they have chosen correctly or not).

[B]Select a target device in the next window: [/B] [s]To use this system, you must select a target device in the next window.[/s] [COLOR=#FF0000]Notice: The target device will be completely overwritten.[/COLOR]

Help selecting the target device is available in the Starter -- Help menu

[COLOR=#FF0000]Please close any other applications accessing your target device.[/COLOR] This will ensure that mkusb has exclusive access to it. (Example: A terminal window can prevent unmounting the target device.)

*I like the example. It reinforces the importance of closing all applications accessing the device. If mksub cannot access the device, this will give the users a "clue", they must still close, "something" accessing the device.

Name: ... ...

Booted from /dev/sda .. [Quit] [Select target device in the next window]

*Now again, the users know, what they have selected. Just tell them mkusb, is using it.

*- See # at bottom -*

[B]Installing: Ubuntu-MATE 16.04 LTS "Xenial Xerus: - Alhpa amd64.iso to /dev/usb ... ... Done [/B] [s]The system: [COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 [/COLOR][COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64[/COLOR] in the selected iso-file will be installed to your target device.[/s] [TABLE="class: cms_table"] [TR] [TD="bgcolor: #b4df02"][s]Installing /home/vertrical/Downloads/Xenial-desktop-amd64.iso to /dev/usb … … Done[/s][/TD] [/TR] [/TABLE]

The device is now unmounted and can be safely unplugged. [s]now.[/s] *I just moved (now) to where it should be. [COLOR=#2252a0]Name: usb-090c_1000 Dev: /dev/sdb Size 3995MB[/COLOR]

[Exit from mkusb] [OK]

I am sure you are trying to give the users all the information they need to make informed decisions. Probably, you want mkusb continually including redundant information to the users, for this reason. I think for the most part, a lot of the information you have been giving them is already known to them from, the actions they have decided upon in earlier decisions. I think a better way is supposing, the users have made their decisions based on what is displayed earlier. Then, on each successive page use simple, commonly used explanations with each. Redundancy of information, can make the pages look less polished. (That is why I got involved. I wanted to try to help with that).

With that said, You COULD make one more page here, asking them to confirm their choices before, mkusb writes to the target device. That is a commonly accepted practice. It would add one more page but, makes the users review their decisions before, it is to late to reverse them. Something similar to what, is clearly needed in Ubiquity before, a new partitioning table is, written over what is on the device.

Something like:

"You have chosen, "Blank" "Blank" Blank"! This action cannot be undone. Are you sure you want mkusb to do this? (You write what is appropriate and what you are comfortable with mkusb asking).

#214

Oh and sudodus. One last thing.

Since mkusb is both a cli and gui application, it is time to think about how it is named, as an app with a gui. All the gui's that I can think of now, have at least one Capital letter in the first of their name.

rysnc > Grsync;  duplicity > Deja-Dup

I don't know what is the solution but, I assume you would like this available in operating systems. They are going to expect a capital in the name.

If there is such a naming convention used, I guess I haven&#8217;t seen it. Then .... disregard.

#215

I'm open for a discussion:

The executable program file of most GUI programs are called by names with lower case letters, for example gparted, evince, gedit, synaptic, firefox, unetbootin. But often they are written in GUIs or texts with one or more uppercase letters, Gparted ... UnetBootIn, or they have a different name that is even translated to the locale's language. For example evince is called 'Dokumentvisare' in Swedish. It does not work to type Dokumentvisare in a terminal window.

$ Dokumentvisare
Dokumentvisare: kommandot hittades inte

(Dokumentvisare: command not found)

We have mkusb, mkusb-nox and mkusb-bas. Only mkusb has a GUI. It could be written mkUSB or MaKeUSB in menus etc, but I think it is confusing and prefer to use the name of the executable program file.

#216

sudodus said: I'm open for a discussion:

We have mkusb, mkusb-nox and mkusb-bas. Only mkusb has a GUI. It could be written mkUSB or MaKeUSB in menus etc, but I think it is confusing and prefer to use the name of the executable program file.

I had thought of MKusb.

MakeUsb

Mk-Usb

MAKE-USB

I think I like

MKusb

Tomorrow, I'll probably prefer something else. Doesn't matter what I like.

#217

mikodo said: Hi. I'll see what I can suggest.

I am going to make notes in the quote.

*The users already know, what they have selected from the previous window.

See, the previous window, "Select Source File", (which should be "Capitalized").

So, we just tell the users, mkusb has found it:

[s]The system tag: Found:[/s] [COLOR=#2252a0]

[/COLOR] Found: [COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64.iso[/COLOR]

[s]was found in the iso-file Found: [COLOR=#2252a0]/home/ventrical/Downloads/xenial-desktop-amd64.iso[/COLOR]..[/s]

*Then simply, tell the users what to do. (They know, they want to use that system. They can see, if they have chosen correctly or not).

[B]Select a target device in the next window: [/B] [s]To use this system, you must select a target device in the next window.[/s] [COLOR=#FF0000]Notice: The target device will be completely overwritten.[/COLOR]

Help selecting the target device is available in the Starter -- Help menu

[COLOR=#FF0000]Please close any other applications accessing your target device.[/COLOR] This will ensure that mkusb has exclusive access to it. (Example: A terminal window can prevent unmounting the target device.)

*I like the example. It reinforces the importance of closing all applications accessing the device. If mksub cannot access the device, this will give the users a "clue", they must still close, "something" accessing the device.

Name: ... ...

Booted from /dev/sda .. [Quit] [Select target device in the next window]

*Now again, the users know, what they have selected. Just tell them mkusb, is using it.

*- See # at bottom -*

[B]Installing: Ubuntu-MATE 16.04 LTS "Xenial Xerus: - Alhpa amd64.iso to /dev/usb ... ... Done [/B] [s]The system: [COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 [/COLOR][COLOR=#2252a0]Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64[/COLOR] in the selected iso-file will be installed to your target device.[/s] [TABLE="class: cms_table"] [TR] [TD="bgcolor: #b4df02"][s]Installing /home/vertrical/Downloads/Xenial-desktop-amd64.iso to /dev/usb … … Done[/s][/TD] [/TR] [/TABLE]

The device is now unmounted and can be safely unplugged. [s]now.[/s] *I just moved (now) to where it should be. [COLOR=#2252a0]Name: usb-090c_1000 Dev: /dev/sdb Size 3995MB[/COLOR]

[Exit from mkusb] [OK]

I am sure you are trying to give the users all the information they need to make informed decisions. Probably, you want mkusb continually including redundant information to the users, for this reason. I think for the most part, a lot of the information you have been giving them is already known to them from, the actions they have decided upon in earlier decisions. I think a better way is supposing, the users have made their decisions based on what is displayed earlier. Then, on each successive page use simple, commonly used explanations with each. Redundancy of information, can make the pages look less polished. (That is why I got involved. I wanted to try to help with that).

With that said, You COULD make one more page here, asking them to confirm their choices before, mkusb writes to the target device. That is a commonly accepted practice. It would add one more page but, makes the users review their decisions before, it is to late to reverse them. Something similar to what, is clearly needed in Ubiquity before, a new partitioning table is, written over what is on the device.

Something like:

"You have chosen, "Blank" "Blank" Blank"! This action cannot be undone. Are you sure you want mkusb to do this? (You write what is appropriate and what you are comfortable with mkusb asking).

Thanks for you contribution, I really appreciate it :-)

*I will take a longer look at this and try to improve mkusb along your guidelines.*

If you try mkusb, not only look at these screenshots, you will find a window here, asking them to confirm their choices, the *Final checkpoint*. It has a corresponding window for iso-testing (the blue one).

*Edit:* If the iso file contains the mini.iso the information in the source tag is not enough to identify what is going to be installed. See the third attached screenshot. The same is true for some non-ubuntu distros, that can also be installed with mkusb. Some iso files have names, that do no tell much about the system it contains. This is why I want to show both the source tag and the name of the iso-file.

#218

Oh, I apologize. I see you have the ending covered.

#219

mikodo said: Oh, I apologize. I see you have the ending covered.

You are very welcome to *test* using mkusb to create a live only USB pendrive and a persistent live pendrive (not only look at the screenshots). I think that you will find things to improve :-)

#220

I hope to use MKusb (lol) and cli, with my next computer. I could test it now with PLOP but, it is time for me to attend to other things presently.

My best regards.

#221

Real life has the highest priority. Whenever you have time, you are welcome to try/use mkusb and mkusb-nox alias MKusb and cli :-)

#222

@ mikodo, ventrical and runrickus

Please look at the attached screenshots and tell me what you think about them :-)

#223

You had me at mkusb!:D Those look real nice(to me) and good text for information. Many Thanks for your contributions sudodus

#224

sudodus said: *Edit:* If the iso file contains the mini.iso the information in the source tag is not enough to identify what is going to be installed. See the third attached screenshot. The same is true for some non-ubuntu distros, that can also be installed with mkusb. Some iso files have names, that do no tell much about the system it contains. This is why I want to show both the source tag and the name of the iso-file.

All right. I understand.

sudodus said: @ mikodo, ventrical and runrickus

Please look at the attached screenshots and tell me what you think about them :-)

*Screen Shot #1*

All I would suggest is to Capitalize "o"verview. That's not a deal breaker, one way or the other. Everything else I like.

Like: Notice and Overview

..................................................................................................

Screen Shot #2

Again, with the Capitals:

Like: Select device - Final checkpoint

Is it appropriate to say: (I know I am going against my previously given advice but, it is hard for me as a novice to follow. So, for other novices too, could you repeat what is said in Screen Shots #1 + #3 as in: Add in the, "System tag Ubuntu 14.04?

mkusb is ready to start installing System tag Ubuntu 14.04 The operating system /media/multimed-2/test/mkmkusb/mini ............................................ Why 2 mkmk? To the target device SanDisk_Cruzer_Blade /dev/sdd 4005MB .......................................... I added "device" (I think it gives continuity with other windows, that say that).

The rest looks good for the this window.

....................................................................................................

Screen Shot #3

I like it all!

....................................................................................................

*I would drop the, "The" system tag in all the windows, and make it to read: System tag Ubuntu 14.04

#225

I think we are converging soon (to texts that all of us who are discussing now can agree about) :-)

I will try to fix these items today.

#226

sudodus said: @ mikodo, ventrical and runrickus

Please look at the attached screenshots and tell me what you think about them :-)

It's just fine.

#227

@ mikodo, ventrical and runrickus

Please look at the attached screenshots and tell me what you think about them. I think we can be satisfied as they are now :-)

-o-

@ everybody

It would be good if you can test that this version of mkusb (10.3.1) can *create a persistent live drive*, and that the persistent live drive really works *in your computer*. You get it from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
#228

sudodus said: @ mikodo, ventrical and runrickus

Please look at the attached screenshots and tell me what you think about them. I think we can be satisfied as they are now :-)

-o-

@ everybody

It would be good if you can test that this version of mkusb (10.3.1) can *create a persistent live drive*, and that the persistent live drive really works *in your computer*. You get it from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

First bug I get. It sort of froze up and then continued on - and completed. When I chose 'report problem' it just disappeared.

Created on:


ventrical@ventrical-luntiy-betatest:~$ inxi -Fxz
System:    Host: ventrical-luntiy-betatest Kernel: 4.2.0-17-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: Unity 7.3.2 (Gtk 3.16.7-0ubuntu3)
           Distro: Ubuntu 15.10 wily
Machine:   Mobo: ASUSTeK model: P5B-E v: Rev 1.xx
           Bios: American Megatrends v: 1807 date: 04/15/2009
CPU:       Dual core Intel Core2 Duo E8400 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11980
           clock speeds: max: 2995 MHz 1: 2995 MHz 2: 2995 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
           Display Server: X.Org 1.17.2 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1440x900@59.89hz
           GLX Renderer: GeForce 210/PCIe/SSE2
           GLX Version: 3.3.0 NVIDIA 304.128 Direct Rendering: Yes
Audio:     Card-1 Intel 82801H (ICH8 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.2.0-17-generic
Network:   Card: Qualcomm Atheros Attansic L1 Gigabit Ethernet
           driver: atl1 v: 2.1.3 bus-ID: 03:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 84.0GB (52.5% used)
           ID-1: /dev/sda model: Hitachi_HDS72168 size: 80.0GB
           ID-2: /dev/sdb model: Name n/a size: 4.0GB
Partition: ID-1: / size: 72G used: 40G (58%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 2.15GB used: 0.01GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 34.5C mobo: 35.0C gpu: 0.0:35C
           Fan Speeds (in rpm): cpu: 4272 psu: 0 sys-1: 0 sys-2: 0
Info:      Processes: 184 Uptime: 26 min Memory: 850.3/2000.1MB
           Init: systemd runlevel: 5 Gcc sys: 5.2.1
           Client: Shell (bash 4.3.421) inxi: 2.2.16 
ventrical@ventrical-luntiy-betatest:~$ 
#229

I created persistent live using Ubuntu-Mate daily xenial desktop. Here is machine #1 It is a little bit slower than usual.


ubuntu-mate@ubuntu-mate:~$ inxi -Fxz
System:    Host: ubuntu-mate Kernel: 4.2.0-16-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: MATE 1.10.2 (Gtk 3.16.7-0ubuntu5)
           Distro: Ubuntu 16.04 xenial
Machine:   Mobo: MSI model: B85-G41 PC Mate(MS-7850) v: 1.0
           Bios: American Megatrends v: V2.8 date: 07/17/2014
CPU:       Dual core Intel Pentium G3240 (-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 12399
           clock speeds: max: 3100 MHz 1: 2044 MHz 2: 1408 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.17.2 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1440x900@59.89hz
           GLX Renderer: Mesa DRI Intel Haswell Desktop
           GLX Version: 3.0 Mesa 11.0.4 Direct Rendering: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.2.0-16-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 124.0GB (3.2% used)
           ID-1: /dev/sda model: Samsung_SSD_840 size: 120.0GB
           ID-2: /dev/sdb model: Name n/a size: 4.0GB
Partition: ID-1: / size: 1.3G used: 56M (5%) fs: overlay dev: N/A
           ID-2: swap-1 size: 4.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 154 Uptime: 7 min Memory: 509.1/7846.7MB
           Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.3.421) inxi: 2.2.28 
ubuntu-mate@ubuntu-mate:~$ 
#230

Test #2

Same persistent drive booted on this machine.




ubuntu-mate@ubuntu-mate:~$ inxi -Fxz
System:    Host: ubuntu-mate Kernel: 4.2.0-16-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: MATE 1.10.2 (Gtk 3.16.7-0ubuntu5)
           Distro: Ubuntu 16.04 xenial
Machine:   Mobo: ASUSTeK model: P5B-E v: Rev 1.xx
           Bios: American Megatrends v: 1807 date: 04/15/2009
CPU:       Dual core Intel Core2 Duo E8400 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11980
           clock speeds: max: 2995 MHz 1: 2995 MHz 2: 2995 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
           Display Server: X.Org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1440x900@59.89hz
           GLX Renderer: Gallium 0.4 on NVA8
           GLX Version: 3.0 Mesa 11.0.4 Direct Rendering: Yes
Audio:     Card-1 Intel 82801H (ICH8 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.2.0-16-generic
Network:   Card: Qualcomm Atheros Attansic L1 Gigabit Ethernet
           driver: atl1 v: 2.1.3 bus-ID: 03:00.0
           IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 84.0GB (2.5% used)
           ID-1: /dev/sda model: Hitachi_HDS72168 size: 80.0GB
           ID-2: /dev/sdb model: Name n/a size: 4.0GB
Partition: ID-1: / size: 1.3G used: 62M (6%) fs: overlay dev: N/A
           ID-2: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 184 Uptime: 3 min Memory: 502.0/2000.1MB
           Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.3.421) inxi: 2.2.28 
ubuntu-mate@ubuntu-mate:~$ 
#231

Test #3.

Same persistent drive booted on this machine.


ubuntu-mate@ubuntu-mate:~$ inxi -Fxz
System:    Host: ubuntu-mate Kernel: 4.2.0-16-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: MATE 1.10.2 (Gtk 3.16.7-0ubuntu5)
           Distro: Ubuntu 16.04 xenial
Machine:   Mobo: ASUSTeK model: P5LD2 v: Rev 1.xx
           Bios: American Megatrends v: 0901 date: 12/15/2005
CPU:       Dual core Intel Pentium D (-MCP-) cache: 2048 KB
           flags: (lm nx sse sse2 sse3) bmips: 15325
           clock speeds: max: 3831 MHz 1: 3831 MHz 2: 3831 MHz
Graphics:  Card: NVIDIA GF119 [GeForce GT 610] bus-ID: 04:00.0
           Display Server: X.Org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1440x900@59.89hz
           GLX Renderer: Gallium 0.4 on NVD9
           GLX Version: 3.0 Mesa 11.0.4 Direct Rendering: Yes
Audio:     Card-1 Intel NM10/ICH7 Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA GF119 HDMI Audio Controller
           driver: snd_hda_intel bus-ID: 04:00.1
           Sound: Advanced Linux Sound Architecture v: k4.2.0-16-generic
Network:   Card: Marvell 88E8053 PCI-E Gigabit Ethernet Controller
           driver: sky2 v: 1.30 port: c800 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 164.0GB (1.3% used)
           ID-1: /dev/sda model: Maxtor_6Y160M0 size: 160.0GB
           ID-2: /dev/sdb model: Name n/a size: 4.0GB
Partition: ID-1: / size: 1.3G used: 77M (7%) fs: overlay dev: N/A
           ID-2: swap-1 size: 2.13GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 174 Uptime: 3 min Memory: 502.2/2000.5MB
           Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.3.421) inxi: 2.2.28 
ubuntu-mate@ubuntu-mate:~$ 
#232

Test #3 DE Screenshot.

#233

Test#4. Booted same drive on this machine.


ubuntu-mate Kernel: 4.2.0-16-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: MATE 1.10.2 (Gtk 3.16.7-0ubuntu5)
           Distro: Ubuntu 16.04 xenial
Machine:   System: eMachines product: EL1352 v: P01-A1
           Mobo: eMachines model: EL1352
           Bios: American Megatrends v: P01-A1 date: 01/28/2010
CPU:       Dual core AMD Athlon II X2 250 (-MCP-) cache: 2048 KB
           flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 12055
           clock speeds: max: 3013 MHz 1: 3013 MHz 2: 3013 MHz
Graphics:  Card: NVIDIA C61 [GeForce 6150SE nForce 430] bus-ID: 00:0d.0
           Display Server: X.Org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           GLX Renderer: Gallium 0.4 on NV4C
           GLX Version: 2.1 Mesa 11.0.4 Direct Rendering: Yes
Audio:     Card NVIDIA MCP61 High Definition Audio
           driver: snd_hda_intel bus-ID: 00:05.0
           Sound: Advanced Linux Sound Architecture v: k4.2.0-16-generic
Network:   Card: NVIDIA MCP61 Ethernet
           driver: forcedeth port: e480 bus-ID: 00:07.0
           IF: enp0s7 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 504.1GB (0.6% used)
           ID-1: /dev/sda model: Hitachi_HDS72105 size: 500.1GB
           ID-2: /dev/sdd model: Name n/a size: 4.0GB
Partition: ID-1: / size: 1.3G used: 80M (7%) fs: overlay dev: N/A
           ID-2: swap-1 size: 2.95GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 187 Uptime: 3 min Memory: 449.2/2756.3MB
           Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.3.421) inxi: 2.2.28 
ubuntu-mate@ubuntu-mate:~$ 

#234

Test#5. Booted persistent on this laptop.



ubuntu-mate@ubuntu-mate:~$ inxi -Fxz
System:    Host: ubuntu-mate Kernel: 4.2.0-16-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: MATE 1.10.2 (Gtk 3.16.7-0ubuntu5)
           Distro: Ubuntu 16.04 xenial
Machine:   System: LENOVO product: 64634YU v: ThinkPad T61
           Mobo: LENOVO model: 64634YU
           Bios: LENOVO v: 7LETD0WW (2.30 ) date: 02/27/2012
CPU:       Dual core Intel Core2 Duo T7300 (-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7980
           clock speeds: max: 2001 MHz 1: 2000 MHz 2: 800 MHz
Graphics:  Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
           bus-ID: 00:02.0
           Display Server: X.Org 1.17.2 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1280x800@60.00hz
           GLX Renderer: Mesa DRI Intel 965GM
           GLX Version: 2.1 Mesa 11.0.4 Direct Rendering: Yes
Audio:     Card Intel 82801H (ICH8 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.2.0-16-generic
Network:   Card-1: Intel 82566MM Gigabit Network Connection
           driver: e1000e v: 3.2.5-k port: 1840 bus-ID: 00:19.0
           IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection
           driver: iwl4965 v: in-tree: bus-ID: 03:00.0
           IF: wls3 state: down mac: <filter>
Drives:    HDD Total Size: 84.0GB (2.5% used)
           ID-1: /dev/sda model: ST980817AS size: 80.0GB
           ID-2: /dev/sdb model: Name n/a size: 4.0GB
Partition: ID-1: / size: 1.3G used: 85M (8%) fs: overlay dev: N/A
           ID-2: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 186 Uptime: 3 min Memory: 509.0/1959.5MB
           Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.3.421) inxi: 2.2.28 
ubuntu-mate@ubuntu-mate:~$ 

mate desktop current probably not best to use for testing mkusb for persistent work.

regards..

#235

ventrical said: Test#5. Booted persistent on this laptop.

mate desktop current probably not best to use for testing mkusb for persistent work.

regards.. I also would agree that Mate is not a good persistent Test case.

#236

Test#6. Ok... work much faster here on <this machine> using same persistent drive.


ubuntu-mate@ubuntu-mate:~$ inxi -Fxz
System:    Host: ubuntu-mate Kernel: 4.2.0-16-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: MATE 1.10.2 (Gtk 3.16.7-0ubuntu5)
           Distro: Ubuntu 16.04 xenial
Machine:   Mobo: ASUSTeK model: M2N-MX SE v: Rev x.xx
           Bios: American Megatrends v: 0308 date: 07/10/2007
CPU:       Dual core AMD Athlon 64 X2 6000+ (-MCP-) cache: 2048 KB
           flags: (lm nx sse sse2 sse3 svm) bmips: 12053
           clock speeds: max: 3013 MHz 1: 3013 MHz 2: 3013 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 02:00.0
           Display Server: X.Org 1.17.2 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1440x900@59.89hz
           GLX Renderer: Gallium 0.4 on NVA8
           GLX Version: 3.0 Mesa 11.0.4 Direct Rendering: Yes
Audio:     Card-1 NVIDIA MCP61 High Definition Audio
           driver: snd_hda_intel bus-ID: 00:05.0
           Card-2 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 02:00.1
           Sound: Advanced Linux Sound Architecture v: k4.2.0-16-generic
Network:   Card-1: NVIDIA MCP61 Ethernet
           driver: forcedeth port: d480 bus-ID: 00:07.0
           IF: enp0s7 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-2: Qualcomm Atheros AR5212/5213/2414 Wireless Network Adapter
           driver: ath5k bus-ID: 01:07.0
           IF: wlp1s7 state: down mac: <filter>
Drives:    HDD Total Size: 504.1GB (0.9% used)
           ID-1: /dev/sda model: ST3500418AS size: 500.1GB
           ID-2: /dev/sdb model: Name n/a size: 4.0GB
Partition: ID-1: / size: 1.3G used: 83M (8%) fs: overlay dev: N/A
           ID-2: swap-1 size: 0.73GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
           ID-3: swap-2 size: 0.80GB used: 0.00GB (0%) fs: swap dev: /dev/sda10
           ID-4: swap-3 size: 2.36GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
           ID-5: swap-4 size: 0.80GB used: 0.00GB (0%) fs: swap dev: /dev/sda9
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 176 Uptime: 2 min Memory: 356.3/3952.5MB
           Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.3.421) inxi: 2.2.28 
ubuntu-mate@ubuntu-mate:~$ 
#237

runrickus said: I also would agree that Mate is not a good persistent Test case.

I am just using Mate because some of the machines are lower end machines and 1unity or gnome-shell will not always work .. but .. I will try some tests with unity and gnome shell. Mate will work on older nVidia adapters without evoking the dreaded llvmpipe :)

regards..

#238

Ok! But yes nvidia seems to be a little smother on older devices. On two intel lappys there is a lot of short freezes with a [COLOR=#000000]persistent install. Just sharing is all.[/COLOR]

#239

runrickus said: Ok! But yes nvidia seems to be a little smother on older devices.

On two intel lappys there is a lot of short freezes with a [COLOR=#000000]persistent install. Just sharing is all.[/COLOR]

Oh yes . I know :) Thanks for sharing.

I am going to try gnome-shell xenial now on ver3 USB persist.

Regards

#240

Zenity bug will not allow apport to call ff so I can get bug number. This activity started after todays mkusb update /unstable

#241

I made a new persistent drive on a ver3USB using xenial gnome-desktop. I chose 100%. Please see screenshots.

#242

ventrical said: First bug I get. It sort of froze up and then continued on - and completed. When I chose 'report problem' it just disappeared.

Created on:


ventrical@ventrical-luntiy-betatest:~$ inxi -Fxz
System:    Host: ventrical-luntiy-betatest Kernel: 4.2.0-17-generic x86_64 (64 bit gcc: 5.2.1)
           Desktop: Unity 7.3.2 (Gtk 3.16.7-0ubuntu3)
           Distro: Ubuntu 15.10 wily
Machine:   Mobo: ASUSTeK model: P5B-E v: Rev 1.xx
           Bios: American Megatrends v: 1807 date: 04/15/2009
CPU:       Dual core Intel Core2 Duo E8400 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11980
           clock speeds: max: 2995 MHz 1: 2995 MHz 2: 2995 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
           Display Server: X.Org 1.17.2 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1440x900@59.89hz
           GLX Renderer: GeForce 210/PCIe/SSE2
           GLX Version: 3.3.0 NVIDIA 304.128 Direct Rendering: Yes
Audio:     Card-1 Intel 82801H (ICH8 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.2.0-17-generic
Network:   Card: Qualcomm Atheros Attansic L1 Gigabit Ethernet
           driver: atl1 v: 2.1.3 bus-ID: 03:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 84.0GB (52.5% used)
           ID-1: /dev/sda model: Hitachi_HDS72168 size: 80.0GB
           ID-2: /dev/sdb model: Name n/a size: 4.0GB
Partition: ID-1: / size: 72G used: 40G (58%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 2.15GB used: 0.01GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 34.5C mobo: 35.0C gpu: 0.0:35C
           Fan Speeds (in rpm): cpu: 4272 psu: 0 sys-1: 0 sys-2: 0
Info:      Processes: 184 Uptime: 26 min Memory: 850.3/2000.1MB
           Init: systemd runlevel: 5 Gcc sys: 5.2.1
           Client: Shell (bash 4.3.421) inxi: 2.2.16 
ventrical@ventrical-luntiy-betatest:~$ 

Please describe this bug in words for me :-)

Could it be, that the computer is slow (so it was working, but not showing any progress for a while, for example while flushing the buffers to disk (the sync command)? Or is it a bug that you can repeat?

#243

ventrical said: Zenity bug will not allow apport to call ff so I can get bug number.

This activity started after todays mkusb update /unstable

Please describe this bug in words for me :-)

At what task/window did zenity crash?

I'll try to repeat it in my computer.

#244

ventrical said: I made a new persistent drive on a ver3USB using xenial gnome-desktop. I chose 100%.

Please see screenshots.

I can check if I also get complaints about bad alignment, when I select 100% in an 8 GB pendrive.

#245

sudodus said: Please describe this bug in words for me :-)

Could it be, that the computer is slow (so it was working, but not showing any progress for a while, for example while flushing the buffers to disk (the sync command)? Or is it a bug that you can repeat?

Please see screenshot in this post: http://ubuntuforums.org/showthread.php?t=1958073&page=24&p=13390270#post13390270

I cannot repeat it because I had already sent the bug report, but , as I said, apport did not call firefox to allow me to login to launchpad.

Regards..

#246

sudodus said: I can check if I also get complaints about bad alignment, when I select 100% in an 8 GB pendrive.

And that leaves no swapspace and I think that may explain problem there.. What % do you choose?

#247

sudodus said: Please describe this bug in words for me :-)

At what task/window did zenity crash?

I'll try to repeat it in my computer.

My misunderstanding. It was *apport* that called the bug (as per screenshot in previous posts). I had not even started mkusb. It just came up after I logged on to wily-ubuntu-desktop where I have mkusb hard installed/unstable.

#248

But a persistent live system is normally not getting any swap space (unless it can borrow some swap partition from another drive).

The problem might be, that I have not accounted for the case with 100% for persistence.

At first I used the FAT32 partition for both grub and data sharing with Windows. So it was not zero, when I selected 100% of the remaining space for persistence. Then I made this system with GPT and an NTFS partition. And I think it gets into problems, when it tries to create an NTFS partition without any drive space :-P

I think I can fix that either by not creating it if the drive space is below a certain value (for example 300 MB), or by allocating at least that drive space for it.

What do you think would be better?

#249

Ok.. here are last two apport logs:


ERROR: apport (pid 23917) Fri Nov 13 09:38:30 2015: called for pid 23910, signal 11, core limit 0
ERROR: apport (pid 23917) Fri Nov 13 09:38:30 2015: executable: /usr/bin/zenity (command line "zenity --text-info --html --filename=/dev/stdin --ok-label=OK --title=mkusb\ 10.3.1\ -\ Notice\ and\ overview --width=640 --height=560 --cancel-label=Quit --ok-label=Select\ target\ device\ in\ the\ next\ window")
ERROR: apport (pid 23917) Fri Nov 13 09:38:30 2015: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 23917) Fri Nov 13 09:38:35 2015: wrote report /var/crash/_usr_bin_zenity.0.crash

and


ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: called for pid 285, signal 6, core limit 0
ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: executable: /lib/systemd/systemd-udevd (command line "/lib/systemd/systemd-udevd")
ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: Ignoring systemd watchdog restart

but I think second report is not related.

regards..

#250

sudodus said: But a persistent live system is normally not getting any swap space (unless it can borrow some swap partition from another drive).

The problem might be, that I have not accounted for the case with 100% for persistence.

At first I used the FAT32 partition for both grub and data sharing with Windows. So it was not zero, when I selected 100% of the remaining space for persistence. Then I made this system with GPT and an NTFS partition. And I think it gets into problems, when it tries to create an NTFS partition without any drive space :-P

I think I can fix that either by not creating it if the drive space is below a certain value (for example 300 MB), or by allocating at least that drive space for it.

What do you think would be better?

I'll just use 50% and see what happens because on the 4GB USB I used for Mate I chose about 30 pecent and I noticed I had 2GB swapspace.

However.. It is working a bit better with gnome-shell.

#251

Zenity bug seems to be gone. It could have been a kernel issue. I don't know..

#252

ventrical said: Ok.. here are last two apport logs:


ERROR: apport (pid 23917) Fri Nov 13 09:38:30 2015: called for pid 23910, signal 11, core limit 0
ERROR: apport (pid 23917) Fri Nov 13 09:38:30 2015: executable: /usr/bin/zenity (command line "zenity --text-info --html --filename=/dev/stdin --ok-label=OK --title=mkusb\ 10.3.1\ -\ Notice\ and\ overview --width=640 --height=560 --cancel-label=Quit --ok-label=Select\ target\ device\ in\ the\ next\ window")
ERROR: apport (pid 23917) Fri Nov 13 09:38:30 2015: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 23917) Fri Nov 13 09:38:35 2015: wrote report /var/crash/_usr_bin_zenity.0.crash

and


ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: called for pid 285, signal 6, core limit 0
ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: executable: /lib/systemd/systemd-udevd (command line "/lib/systemd/systemd-udevd")
ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 3695) Tue Nov 10 15:18:13 2015: Ignoring systemd watchdog restart

but I think second report is not related.

regards..

So you had problems with the 'Notice and overview window'

That makes me confused. How come? Is it possible to repeat?

Which version is it - Xenial?

I'll try it in the same version.

#253

ventrical said: But a persistent live system is normally not getting any swap space (unless it can borrow some swap partition from another drive).

The problem might be, that I have not accounted for the case with 100% for persistence.

At first I used the FAT32 partition for both grub and data sharing with Windows. So it was not zero, when I selected 100% of the remaining space for persistence. Then I made this system with GPT and an NTFS partition. And I think it gets into problems, when it tries to create an NTFS partition without any drive space :-P

I think I can fix that either by not creating it if the drive space is below a certain value (for example 300 MB), or by allocating at least that drive space for it.

What do you think would be better?

I'll just use 50% and see what happens because on the 4GB USB I used for Mate I chose about 30 pecent and I noticed I had 2GB swapspace.

However.. It is working a bit better with gnome-shell.

I've tested, and it created a 512 b partition, not enough for the NTFS overhead, far less to align things :-D

And it is the reason I thought. I can fix that either by not creating it if the drive space is below a certain value (for example 300 MB), or by allocating at least that drive space for it.

What do you think would be better? - I'm inclined to 'not create it if the drive space is below a certain value'

#254

ventrical said: Zenity bug seems to be gone. It could have been a kernel issue. I don't know..

Just a thought here but are you overclocking your CPU? I have seen similar errors when I do that! And I also leave about 300MB in front of the USB.

#255

ventrical said: Zenity bug seems to be gone. It could have been a kernel issue. I don't know..

OK - let's not worry about it.

#256

runrickus said: Just a thought here but are you overclocking your CPU?

I have seen similar errors when I do that! And I also leave about 300MB in front of the USB.

No I don't overclock - I've had bad experiences with it :-P

Do you agree that I should have a limit of 300 MB for the NTFS file system?

#257

Well lets wait for ventrical to finish, But I do not run into the problems that are reported here with that set-up.

#258

ventrical said: I'll just use 50% and see what happens because on the 4GB USB I used for Mate I chose about 30 pecent and I noticed I had [COLOR="#FF0000"]2GB swapspace[/COLOR].

However.. It is working a bit better with gnome-shell.

When you say swapspace, do you mean the casper-rw overlay partition?

It should be possible to select 100%, and I intend to skip the NTFS partition at 100%. If given a percentage, that is translated to less than 300 MB, it can be given the average of the translated value and 300 MB (so slightly above 150 MB).

$ sudo parted -ls
...
Modell: SanDisk Cruzer Blade (scsi)
Disk /dev/sdd: 4005MB
Sektorstorlek (logisk/fysisk): 512B/512B
Partitionstabell: gpt

Nummer  Början  ****    Storlek  Filsystem  Namn     Flaggor
 2      1049kB  2097kB  1049kB              primary  bios_grub
[COLOR="#0000CD"] 3      2097kB  66,1MB  64,0MB   ntfs       primary  msftdata[/COLOR]
 4      66,1MB  148MB   81,8MB              primary
 5      148MB   4004MB  3857MB   ext4       primary
[COLOR="#FF0000"] 1      4004MB  4004MB  512B                primary  msftdata[/COLOR]


$ df -h
Filsystem      Storlek Använt Ledigt Anv% Monterat på
/dev/sdb5          52G    26G    24G  53% /
udev              2,0G    12K   2,0G   1% /dev
tmpfs             404M   1,2M   402M   1% /run
none              5,0M      0   5,0M   0% /run/lock
none              2,0G   1,2M   2,0G   1% /run/shm
cgroup            2,0G      0   2,0G   0% /sys/fs/cgroup
/dev/sdc7         841G   467G   331G  59% /media/multimed-2
[COLOR="#0000CD"]/dev/sdd3          61M   2,5M    59M   5% /mnt[/COLOR]
$ sudo lsblk -fm /dev/sdd
NAME   FSTYPE  LABEL MOUNTPOINT NAME     SIZE OWNER GROUP MODE
sdd                             sdd      3,7G root  disk  brw-rw----
[COLOR="#FF0000"]&#9500;&#9472;sdd1                          &#9500;&#9472;sdd1   512B root  disk  brw-rw----[/COLOR]
&#9500;&#9472;sdd2                          &#9500;&#9472;sdd2     1M root  disk  brw-rw----
&#9500;&#9472;sdd3 ntfs          /mnt       &#9500;&#9472;sdd3    61M root  disk  brw-rw----
&#9500;&#9472;sdd4 iso9660 CDROM            &#9500;&#9472;sdd4    78M root  disk  brw-rw----
&#9492;&#9472;sdd5 ext4    -rw              &#9492;&#9472;sdd5   3,6G root  disk  brw-rw----

Partition [COLOR="#FF0000"]#1[/COLOR] is the one that received [COLOR="#FF0000"]'0%'[/COLOR].

I formatted partition [COLOR="#0000CD"]#3 to NTFS[/COLOR] to see if it works with 61 MB, and it does, so 150 MB would be OK as the minimum value.

#259

runrickus said: Well lets wait for ventrical to finish,

But I do not run into the problems that are reported here with that set-up.

+1 :-)

#260

Ok here is one with 100% allocated to the installed OS

sudo parted -lsModel: ATA WDC WD5000AAKS-0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 


Number  Start   End    Size    Type      File system     Flags
 1      1049kB  268MB  267MB   primary   ext2            boot
 2      268MB   494GB  494GB   primary   ext4
 3      494GB   500GB  6264MB  extended                  lba
 5      494GB   500GB  6263MB  logical   linux-swap(v1)




Model: ATA WDC WD5000AADS-0 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 


Number  Start   End    Size    Type      File system  Flags
 1      1049kB  334GB  334GB   primary   ext4         boot
 2      334GB   500GB  166GB   extended
 6      334GB   497GB  163GB   logical   ext4
 5      497GB   500GB  3219MB  logical




Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.
Model: SanDisk Cruzer U (scsi)
Disk /dev/sdh: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 


[me@Arch ~]$ 


I have a customer here be back in about an 1 hour.

#261

sudodus said: So you had problems with the 'Notice and overview window'

That makes me confused. How come? Is it possible to repeat?

Which version is it - Xenial?

I'll try it in the same version.

Wily. When I updated mkusb I also got the 4.2.n.18 kernel and other so as I say it might have been new kernel. I rolled back to 4.2.n.17 and it worked ok .. no errors .. then back to 4.2.n.18 and no errors.

#262

sudodus said: When you say swapspace, do you mean the casper-rw overlay partition?

It happened so fast... but below is the layout of the 4GB USB persistent drive with xenial ubuntu-mate desktop on it.

#263

runrickus said: Just a thought here but are you overclocking your CPU?

I have seen similar errors when I do that! And I also leave about 300MB in front of the USB.

On that particular PC I have overclocked it to very high values but it is back to it's normal clock.. brb! :) Edit: Called away for a few moments... but yes .. I have had strange things during overclocks but it was at it's normal clock this time around.

Regards..

#264

Yes, maybe the new kernel or something else that came with the update. I guess it would be hard for me to repeat it.

-o-

I'm working with the logic and computation statements to fix the bug at 100% for persistence.

0 for NTFS -- no attempt to install NTFS

[s]> 0 and < 128 MB -- average between 'calculated value from the percentage' and 128 MB, for example 32 MB --> (32 + 128)/2 = 80 MB NTFS partition size

= 128 MB -- keep the value for NTFS partition size[/s]

*Edit:* mkusb version 10.3.2 contains a bugfix for this problem.

  • It works in my tests at 100% of the remaining space for persistence: There will be a spaceholder (only one sector, 512 bytes), and I have eleminated operations that fail.
  • It works also with high values for persistence, 95% - 99%: The casper-rw partition is given at least 300 MB drive space, and if there is enough space for usbdata with NTFS, it will get 60 MB or more.
#265

sudodus said: @ mikodo, ventrical and runrickus

Please look at the attached screenshots and tell me what you think about them. I think we can be satisfied as they are now

I think each of those windows clearly state what is needed for the user to know. I don't see any glaring deficits for usability. That is of primary importance.

As I have written earlier, I believe there is still room for polishing the presentation of the windows and possibly more consistency between all the windows throughout the process. You can choose to do that later if you wish.

I see you are moving on to more important things.

Good Luck.

#266

ventrical said: It happened so fast... but below is the layout of the 4GB USB persistent drive with xenial ubuntu-mate desktop on it.

I refer to your screenshot from 'Disks' or similar.

The *BIOS-Boot* partition has a *bios_grub* flag, and is intended for grub, when booting via BIOS. It is correct. The problem was with the NTFS partition, which has the logical number 1, necessary for Windows to see it, but it is located at the end of the drive, which is important, because the partitions involved in booting must not be too far back in the drive (if the drive is more than 137 GB, there is a limit, often referred to by *oldfred*, maybe there are other limits too).

#267

mikodo said: I think each of those windows clearly state what is needed for the user to know. I don't see any glaring deficits for usability. That is of primary importance.

As I have written earlier, I believe there is still room for polishing the presentation of the windows and possibly more consistency between all the windows throughout the process. You can choose to do that later if you wish.

I see you are moving on to more important things.

Good Luck.

Thank you,

And will continue to listen to your advice :-)

#268

Here is screenshot of well working xenial gnome-desktop persistent boot with approximately 4GB of swapspace... so it is most likely using the swapspace from the ssd.

#269

Most likely yes. You can find out for sure with this command

swapon -s
#270

[SIZE=4]mkusb version 10.3.2[/SIZE]

I have modified the logic and calculations of partition #1, the usbdata partition with NTFS.

  • It works in my tests at 100% of the remaining space for persistence: There will be a spaceholder (only one sector, 512 bytes), and I have eleminated operations that fail.
  • It works also with high values for persistence, 95% - 99%: The casper-rw partition is given at least 300 MB drive space, and if there is enough space for usbdata with NTFS, it will get 60 MB or more.

I might have introduced some other bug, so please test that this version, mkusb 10.3.2, can *create a persistent live drive*, and that the persistent live drive really works *in your computer*. You get/update it from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
#271

sudodus said: Most likely yes. You can find out for sure with this command

swapon -s

I'll try that later....ummm

regards..

#272

sudodus said: Most likely yes. You can find out for sure with this command

swapon -s

Thanks..


ubuntu-gnome@ubuntu-gnome:~$ swapon -s
Filename                Type        Size    Used    Priority
/dev/sda5                                  partition    4050940    0    -1
ubuntu-gnome@ubuntu-gnome:~$ 

so it is using swap partition from ssd drive.

#273

sudodus said: [SIZE=4]mkusb version 10.3.2[/SIZE]

I have modified the logic and calculations of partition #1, the usbdata partition with NTFS.

  • It works in my tests at 100% of the remaining space for persistence: There will be a spaceholder (only one sector, 512 bytes), and I have eleminated operations that fail.
  • It works also with high values for persistence, 95% - 99%: The casper-rw partition is given at least 300 MB drive space, and if there is enough space for usbdata with NTFS, it will get 60 MB or more.

I might have introduced some other bug, so please test that this version, mkusb 10.3.2, can *create a persistent live drive*, and that the persistent live drive really works *in your computer*. You get/update it from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

Actually my persistent drives are working beautifully as they are :) ubuntu-gnome desktop works exceptionally well but that is not to say that the progressive daily/current zsyncs will will work perfectly throughout the cycle.

Regards..

#274

ventrical said: Actually my persistent drives are working beautifully as they are :) ubuntu-gnome desktop works exceptionally well but that is not to say that the progressive daily/current zsyncs will will work perfectly throughout the cycle.

Regards..

I think it is better to zsync the daily iso file and put a new image of it onto the pendrive, than to update/upgrade a persistent live drive and gradually add more to the casper-rw partition.

I certainly agree that we must expect hiccups with the daily iso file during the development cycle.

-o-

You seem happy with the persistent live drives. Does that mean that you have found no more bug, and that you have finished this testing and debugging session?

#275

sudodus said: I think it is better to zsync the daily iso file and put a new image of it onto the pendrive, than to update/upgrade a persistent live drive and gradually add more to the casper-rw partition.

I did not mean it that way. I know that would not work. I mean about complete daily/currents.

I certainly agree that we must expect hiccups with the daily iso file during the development cycle.

-o-

Yes.. this way.

You seem happy with the persistent live drives. Does that mean that you have found no more bug, and that you have finished this testing and debugging session?

Absolutely not finished. Other works lays on the side :) I try to test mkusb when I can. Don't let me hold you back from putting 10.3.1 up as stable release.

Regards..

#276

But you found a bug in 10.3.1, and it is fixed in 10.3.2. I would like to skip 10.3.1 and use 10.3.2 as the new version of the stable release. I continue testing it myself, and I have not yet found any new bug, but I think it needs some more testing.

#277

+1! :)

#278

[SIZE=4]mkusb version 10.3.3[/SIZE]

During testing with an old 1 GB pendrive, I found and fixed a couple of minor bugs, that affect making persistent live drives.

  1. mkusb did not finish correctly, when there is too small space ( < 200 MB ) for persistence.
  2. there was confusion with the variables storing the pid of child processes, and those processes could be left running.

I might have introduced some other bug, so please test that this version, mkusb 10.3.3, can *create a persistent live drive*, and that the persistent live drive really works *in your computer*. You get/update it from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
#279

I created persistent live USB by mkusb 10.3 of xubuntu-15.10-desktop-amd64.iso. It worked a couple of times, but now starting a persistent session freezes on boot during the graphical animation. Why is this? Non-persistent session boots fine. How to recover the presistent boot?

#280

I guess that something has happened to the data on the casper-rw partition.

You could boot live-only and try to repair the file system on the casper-rw partition

sudo e2fsck -f /dev/sdx5

where x is the drive letter for the drive with your persistent live system.

If that does not help, I think you should

  1. Try to save any personal files stored in the casper-rw partition.
  1. Clear the file system in the casper-rw partition. Maybe it is enough to remove all files, maybe you need to create a new file system. mkusb creates an ext4 file system without journaling (which is good for pendrives to reduce wear), but if you have an SSD or HDD, you should [re-]activate journaling. It is also possible to create an ext2 file system (which lacks journaling).

*Edit:* Persistent live systems as well as installed systems in USB drives are sensitive to data loss or corruption, if the shutdown procedure is not complete before unplugging.

#281

The repair command found some things to fix, but fixing them didn't make the boot work. Thereafter removing all files in the casper-rw filesystem worked. BTW I have GPT in the flash drive.

#282

Yes, mkusb uses GPT for the persistent live drives. This makes it work with huge external hard disk drives, greater than 2 TB, where you can make a big NTFS partition to store data and share it with Windows computers. And GPT should be more stable than the MSDOS partition table.

I'm glad you made it work again :-)

[hr][/hr] [SIZE=4]1. Backup[/SIZE]

It might be a good idea to *backup the files in the casper-rw partition*.

For example, assuming Xubuntu 14.04.3 LTS (change 'Xubuntu' to fit *your* persistent live system)

where x is the drive letter of the persistent live drive (and the persistence is stored in the 5th partition )

  • *boot 'live-only'*, unmount the casper-rw partition /dev/sdx5,
sudo umount /dev/sdx5
  • check/repair the file system in the casper-rw partition
sudo e2fsck -f /dev/sdx5
  • mount the casper-rw partition
sudo mount /dev/sdx5 /mnt
  • make a tarball of the content and store the tarball in the NTFS partition (backup).
cd /mnt
sudo tar -cvzf /media/xubuntu/usbdata/casper-rw-1.tar.gz .

The final space and dot are important parts of the command.

Do not simply copy the files to that partition, because NTFS cannot preserve the permisisons of ext file systems. (If you want to copy or rsync the files, the target file system should also be an ext file system.)

[hr][/hr] [SIZE=4]2. Restore[/SIZE]

When you *restore from the tarball backup* (assuming the automatic mount works)

  • *boot 'live-only'*
  • change directory to the casper-rw partition, remove the current (and maybe partly bad) files, then extract from the tarball

cd /media/xubuntu/casper-rw
# Check that you have really changed directory to where you want! Avoid removing files from the wrong directory!
pwd
df .
ls
sudo rm -r *
sudo tar -xvzf /media/xubuntu/usbdata/casper-rw-1.tar.gz

*- reboot 'persistent live' and fix ownership for easy access to the mounted partitions*

sudo chown root:$USER /media/xubuntu/

[hr][/hr] [SIZE=4]3. Copy the tarball to another drive[/SIZE]

Finally, to be sure the backup survives, you should *copy the tarball to another drive*, that you keep somewhere else, so that both backup copies are not lost. If you use the pendrive regularly, you should make backup copies of the casper-rw partition regularly too, maybe once a week or twice a month.

[hr][/hr] [SIZE=4]4. Automation[/SIZE]

See post #283 with shell-scripts that do the job automatically.

#283

^^ As a mere mortal, I am enamored by this wizardry.

Should this trouble shooting & repair and backup commands be in here or here. Or, have I missed what is there already.

I will need to have my hand-held when I start playing with this. Maybe less hand-holding will need to be done if, there are these kind of instructions.

Back to my life.

Kind Regards.

#284

mikodo said: ^^ As a mere mortal, I am enamored by this wizardry.

Should this trouble shooting & repair and backup commands be in here or here. Or, have I missed what is there already.

I will need to have my hand-held when I start playing with this. Maybe less hand-holding will need to be done if, there are these kind of instructions.

Back to my life.

Kind Regards.

I see what you mean, and you are right :-)

These commands should be possible to automate in a couple of shell-scripts with more or less 'eye-candy'. For example, those shell-scripts can be put into the same partition as the boot files. Then it would be rather convenient for the user to perform backup and restore. Copying the tarball to another drive should be easy enough to do without any extra tool.

I have started thinking of making those shell-scripts, but it will take some time until they are ready. I thought that those manual command lines are better than nothing, because I have found that it can be important to start by checking/repairing the file system, not only make a tarball.

#285

[SIZE=4]mkusb version 10.3.4[/SIZE]

As promised, I have made shell-scripts to make it easy to backup and restore the overlayed persistent data of the persistent live system created by mkusb. These shell-scripts are written to

/dev/sdx1 mounted at /media/xubuntu/usbdata and /dev/sdx3 which can be mounted at /mnt.

These scripts work in linux operating systems based on Ubuntu. In some versions, they are not executable, but can be run as parameter to bash. *Boot into the live-only mode* and run the scripts according to the following examples. (The scripts will complain if you try to use it in persistent mode.)

[SIZE=3]Backup example[/SIZE]


cd /media/xubuntu/usbdata
ls -l
[COLOR="#0000cc"]bash backup[/COLOR]

[SIZE=3]Restore example[/SIZE]


cd /media/xubuntu/usbdata
ls -l
[COLOR="#0000cc"]bash restore[/COLOR]

The name of the tarball file (containing the backup) is updated automatically to create versions. Remove old versions manually!

1-casper-rw.tar.gz 2-casper-rw.tar.gz 3-casper-rw.tar.gz ...

[SIZE=3]Copy the tarball to another drive[/SIZE]

Finally, to be sure the backup survives, you should copy the tarball to another drive, that you keep somewhere else, so that both backup copies are not lost. If you use the pendrive regularly, you should make backup copies of the casper-rw partition regularly too, maybe once a week or twice a month.

[SIZE=3]Select another directory/file[/SIZE]

It is also possible to select another directory where to write/read the tarball. In that case, you add a parameter to the command line, for example


[COLOR="#0000cc"]bash backup /media/xubuntu/backup[/COLOR]  # target directory in another drive, a 'backup' drive

[COLOR="#0000cc"]bash restore /media/xubuntu/backup/1-casper-rw.tar.gz[/COLOR]  # source tarball in another drive, a 'backup' drive

[hr][/hr] The commands under the hood of backup and restore are described in post #280.

I might have introduced some other bug, so please test that this version, mkusb 10.3.4, can *create a persistent live drive*, and that the persistent live drive really works *in your computer*. You get/update it from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
#286

[SIZE=4]mkusb version 10.3.5[/SIZE]

This version is released with the intention to avoid problems with grub and booting in installed UEFI systems.

*- no change in BIOS mode*

*- change in UEFI mode*

grub-pc is not installed because it interferes with the installed system's grub-efi packages.

*This affects making persistent live drives in UEFI mode*. mkusb can not make drives that boot i BIOS mode. There are some error outputs, but it can make drives that boot in UEFI mode, both from 64-bit and 32-bit iso files.

*- final comment*

This is a temporary fix, and a better solution should be found. At least, it should be possible to create persistent live 64-bit systems that boot in both UEFI and BIOS mode. It is less important to create 32-bit systems that boot in UEFI mode.

*Edit:*

You get/update it from the stable and unstable PPA via the following commands

stable:

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb

unstable:

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
#287

[SIZE=4]mkusb version 10.4[/SIZE]

Making live-only pendrives works as usual and is not affected by these changes.

This version is released to solve problems with grub and booting in installed UEFI systems, when making persistent live systems. *grub-pc* is not installed into an installed system in UEFI mode, but it is installed into BIOS systems and live UEFI systems. A good solution in order to create flexible persistent live pendrives is to run mkusb in a persistent live pendrive.

old persistent live system + ISO file[COLOR="#0000CD"] [COLOR="#709900"]---- [IMG]https://help.ubuntu.com/community/mkusb/artwork?action=AttachFile&do=get&target=mkusb24.png[/IMG] --->[/COLOR] [/COLOR] new persistent live system

The method to make persistent live drives is modified to use

  • either data from the source ISO file (new), which works with amd64 (64-bit) systems based on Ubuntu,
  • or data from usb-pack_efi.tar.gz to boot (old), which is the method described in the following links.

One pendrive for all PC (Intel/AMD) computers - single-boot dual-boot multi-boot How to Create a EFI/UEFI GRUB2 Multiboot USB drive to boot ISO images

In both cases the persistent live system boots via *grub 2*.

There is a simple menu to select boot method, but the selection is overridden automatically, when only one of the methods works,

  • in installed systems in UEFI mode,
  • with i386 (32-bit) ISO files.

See the attached screenshot.

*- final comment*

This resolves the problem that caused the temporary fix in version 10.3.5.

[hr][/hr] You get/update this new version 10.4 from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

It is tested but needs more testing before uploading to the stable PPA 'ppa:mkusb/ppa'. You are welcome to participate in the testing :-)

#288

sudodus said: [SIZE=4]mkusb version 10.4[/SIZE]

Making live-only pendrives works as usual and is not affected by these changes.

This version is released to solve problems with grub and booting in installed UEFI systems, when making persistent live systems. *grub-pc* is not installed into an installed system in UEFI mode, but it is installed into BIOS systems and live UEFI systems. A good solution in order to create flexible persistent live pendrives is to run mkusb in a persistent live pendrive.

:-)

I need a clarification here. Do you mean that there was an acutal *bug* with mkusb itself running in an already installed UEFI mode system or are you referring to the actual installation of the ISO to USB in UEFI mode?

Regards..

#289

mkusb console will not allow for copy 'n paste, so it is hard to put up what has happened there. Is there a log file for that ?

Usng 10.4.1

#290

There is bug when you try to highlight 'find target....' and click ok and it will come up with error. But when you double-click 'find target ...' it will not error.

There is bug in both persistent BIOS and persistent UEFI modes where mouse arrow is big black X. I am testing ubuntu-mate zenial ISO using mkusb 10.4.1. The black "X" does not appear in "live mode' on either BIOS of UEFI mode.

Regards..

There is bug when you try to highlight 'find target....' and click ok and it will come up with error. But when you double-click 'find target ...' it will not error. This bug fixed on restart.

#291

There is zenity apport error bug right after login and when you send it, it sends in the background so there is no idea of where the report is going or what it is pulling from my logs. I have problems with this.

#292

Here is zenity log.

#293

ventrical said: [SIZE=4]mkusb version 10.4[/SIZE]

Making live-only pendrives works as usual and is not affected by these changes.

This version is released to solve problems with grub and booting in installed UEFI systems, when making persistent live systems. *grub-pc* is not installed into an installed system in UEFI mode, but it is installed into BIOS systems and live UEFI systems. A good solution in order to create flexible persistent live pendrives is to run mkusb in a persistent live pendrive.

:-)

I need a clarification here. Do you mean that there was an acutal *bug* with mkusb itself running in an already installed UEFI mode system or are you referring to the actual installation of the ISO to USB in UEFI mode?

Regards..

The "bug* is that mkusb wants to install the package grub-pc into the operating system (if it is not already there). This is OK in BIOS mode and in live (and persistent live) sessions. But not in systems that are installed in UEFI mode, because in this particular case it will kick out some other grub-related packages (grub-efi... etc). And I think that cannot be accepted.

mkusb needs the program *grub-install* from the package grub-pc to create persistent live systems with data from usb-pack_efi.tar.gz to boot, the 'old' way. But I added the 'new' way in version 10.4, to grab the grub files necessary for booting from the iso file itself. It works with amd64 iso files, but i386 iso files lack these files.

Is this explaining what you want to know?

#294

ventrical said: mkusb console will not allow for copy 'n paste, so it is hard to put up what has happened there. Is there a log file for that ?

Usng 10.4.1

Yes ~/mkusb.log

#295

sudodus said: The "bug* is that mkusb wants to install the package grub-pc into the operating system (if it is not already there). This is OK in BIOS mode and in live (and persistent live) sessions. But not in systems that are installed in UEFI mode, because in this particular case it will kick out some other grub-related packages (grub-efi... etc). And I think that cannot be accepted.

mkusb needs the program *grub-install* from the package grub-pc to create persistent live systems with data from usb-pack_efi.tar.gz to boot, the 'old' way. But I added the 'new' way in version 10.4, to grab the grub files necessary for booting from the iso file itself. It works with amd64 iso files, but i386 iso files lack these files.

Is this explaining what you want to know?

Yes.. I know this bug.

Thanks!

#296

sudodus said: Yes ~/mkusb.log

What directory? Can't find it. Even nautilus search wont find. I think nautilus is busted also.

#297

ventrical said: What directory? Can't find it. Even nautilus search wont find. I think nautilus is busted also.

:)

#298

ventrical said: There is zenity apport error bug right after login and when you send it, it sends in the background so there is no idea of where the report is going or what it is pulling from my logs. I have problems with this.

Maybe you have better control, if you run mkusb from a terminal window (instead of from a menu or Unity's dash or a desktop icon)

sudo -H mkusb

and you can make a complete bug report.

ventrical said: Here is zenity log.

There are several warnings and error messages from zenity and they depend on the version of Ubuntu. Maybe this one is more severe than the usual ones.

I tried to reproduce the bug in xenial i386 - persistent live, but it works as it should. It is not quite up to date, I'll grab the current daily iso and try again.

#299

sudodus said: Maybe you have better control, if you run mkusb from a terminal window (instead of from a menu or Unity's dash or a desktop icon)

sudo -H mkusb

and you can make a complete bug report.

There are several warnings and error messages from zenity and they depend on the version of Ubuntu. Maybe this one is more severe than the usual ones.

I tried to reproduce the bug in xenial i386 - persistent live, but it works as it should. It is not quite up to date, I'll grab the current daily iso and try again.

I'm was using wily in this case , fully updated.

#300

sammiev said: :)

Nope! it's not there . Even with 'show hidden files' on.

#301

ventrical said: What directory? Can't find it. Even nautilus search wont find. I think nautilus is busted also.

Tilde is short for the home directory alias $HOME, so it should be in your home directory.

~/mkusb.log
# or
$HOME/mkusb.log

-o-

By the way in my version of persistent live xenial system I have the following iso file (booting grub-n-iso)

lubuntu-xenial-desktop-i386.iso dated Nov 24,

and it does not suffer from the bugs that are affecting you. I'd better save it instead of overwriting in order to have a working xenial system ;-)

I have not been able to reproduce your bug with zenity, and not with 'find target ...' - marking and pressing Enter works, not only double-clicking.

And I can mark and paste with middle-click from a zenity text-info window to an editor. I think that is a bug of the underlying infrastructure (maybe your desktop environment) of the current version of xenial.

#302

sudodus said: Maybe you have better control, if you run mkusb from a terminal window (instead of from a menu or Unity's dash or a desktop icon)

sudo -H mkusb

and you can make a complete bug report.

There are several warnings and error messages from zenity and they depend on the version of Ubuntu. Maybe this one is more severe than the usual ones.

I tried to reproduce the bug in xenial i386 - persistent live, but it works as it should. It is not quite up to date, I'll grab the current daily iso and try again.

Very well..


[sudo] password for ventrical: 
---------------------------------------------------------------------------
start [mkusb 10.4] @ 2015-11-30 01:11:51 AM
---------------------------------------------------------------------------
Current directory=/home/ventrical
main: usbonly=true
main: liveonly=true
No input file specified yet
main: source=''
TERM=xterm-256color
ubuntu
---------------------------------------------------------------------------
menu_shell:
select_source: imagefile=/home/ventrical/Downloads/xenial-desktop-amd64.iso
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/ventrical/Downloads/xenial-desktop-amd64.iso
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /dev/loop0 is write-protected, mounting read-only
disk_name_type=desktop
Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 _found_ in iso-file
Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 _not_ in any possible target drive
Booted from: /dev/sda
ans=
---------------------------------------------------------------------------
menu_shell:
---------------------------------------------------------------------------
menu_shell:
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/ventrical/Downloads/xenial-desktop-amd64.iso
Booted from: /dev/sda
ans=1
mount: /dev/loop0 is write-protected, mounting read-only
 Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
mount: /dev/loop0 is write-protected, mounting read-only
'/home/ventrical/Downloads/xenial-desktop-amd64.iso' is identified as the source ISO file
<pre>
MODEL            NAME   FSTYPE  LABEL                       MOUNTPOINT  SIZE
                 sdb                                                    3.7G
                 &#9500;&#9472;sdb1                                                 512B
                 &#9500;&#9472;sdb2                                                   1M
                 &#9500;&#9472;sdb3 vfat    xenial64                                122M
                 &#9500;&#9472;sdb4 iso9660 Ubuntu-MATE 16.04 LTS amd64             1.2G
                 &#9492;&#9472;sdb5 ext4    casper-rw                               2.4G
</pre>
Using the file '/usr/share/mkusb/grub.cfg'
Using the file '/usr/share/mkusb/usb-pack_efi.tar.gz'
Clean for a GUID partition table
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): 
Command (? for help): 
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
Wipe the first megabyte (mibibyte) to get a clean boot area
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.376843 s, 2.8 MB/s
---------------------------------------------------------------------------
Selected percentage of remaining space for persistence = 100
---------------------------------------------------------------------------
 
preparing /dev/sdb3  ------------------------------------------------
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 1.03334 s, 1.0 MB/s
umount: /dev/sdb3: not mounted
mkfs.fat 3.0.28 (2015-05-16)
/dev/sdb3 has 123 heads and 62 sectors per track,
hidden sectors 0x1000;
logical sector size is 512,
using 0xf8 media descriptor, with 249856 sectors;
drive number 0x80;
filesystem has 2 32-bit FATs and 1 sector per cluster.
FAT size is 1922 sectors, and provides 245980 clusters.
There are 32 reserved sectors.
Volume ID is 9681a1eb, no volume label.
 
preparing /dev/sdb1  ------------------------------------------------
No space for NTFS partition /dev/sdb1, only placeholder
preparing /dev/sdb5  ------------------------------------------------
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.181953 s, 5.8 MB/s
umount: /dev/sdb5: not mounted
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 638715 4k blocks and 159680 inodes
Filesystem UUID: 6975c94c-d6e4-4772-9e9a-f39a0a0d2d3a
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

mount: /home/ventrical/Downloads/xenial-desktop-amd64.iso is already mounted
fatlabel: warning - lowercase labels might not work properly with DOS or Windows
tune2fs 1.42.12 (29-Aug-2014)
---------------------------------------------------------------------------
source=/home/ventrical/Downloads/xenial-desktop-amd64.iso
---------------------------------------------------------------------------
mount /dev/sdb3 /tmp/tmp.PqYzOdOVSf
mount: /dev/sdb1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
/dev/sdb3       121M   512  121M   1% /tmp/tmp.PqYzOdOVSf
UEFI Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
BIOS Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
using usb-pack_efi.tar.gz
./
./boot/
./boot/grub/
./boot/memtest/
./boot/memtest/memtest86+-5.01.bin
./boot/memtest/memtest.bin
./EFI/
./EFI/BOOT/
./EFI/BOOT/bootx64.efi
./EFI/BOOT/bootia32.efi
---------------------------------------------------------------------------
do_n_show:
&lt; "/home/ventrical/Downloads/xenial-desktop-amd64.iso" pv -n | dd of=/dev/sdb4 bs=4096
 
( < "/home/ventrical/Downloads/xenial-desktop-amd64.iso" pv -n | dd of=/dev/sdb4 bs=4096 && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 )
Please wait for sync (flushing file system buffers to the device)
until 'Done' is written ...
'pv %'; 'dd final output'
4
9
14
19
23
28
31
31
31
32
32
32
32
32
33
33
33
33
33
33
33
33
33
33
33
34
34
34
34
34
34
34
34
34
34
34
34
34
34
35
35
35
35
35
35
35
35
35
36
36
36
36
36
37
37
37
38
38
38
38
39
39
39
40
40
40
41
41
41
42
42
42
43
43
43
44
44
44
45
45
45
46
46
46
47
47
47
48
48
48
49
49
49
50
50
50
51
51
52
52
52
53
53
53
54
54
54
55
55
55
56
56
56
57
57
58
58
58
59
59
59
60
60
60
61
61
61
62
62
62
63
63
63
64
64
65
65
65
66
66
66
67
67
67
68
68
68
69
69
70
70
70
71
71
71
72
72
72
73
73
73
74
74
74
75
75
76
76
76
77
77
77
78
78
78
79
79
79
80
80
81
81
81
82
82
82
83
83
83
84
84
84
85
85
85
86
86
87
87
87
88
88
88
89
89
89
90
90
90
91
91
91
92
92
93
93
93
94
94
94
95
95
95
96
96
96
97
97
98
98
98
99
99
99
100
300144+0 records in
300144+0 records out
1229389824 bytes (1.2 GB) copied, 291.296 s, 4.2 MB/s
Done
do_n_show: Work done
---------------------------------------------------------------------------
Syncing the target device ...
<pre>
parted -s "/dev/sdb" print
Model:   (scsi)
Disk /dev/sdb: 3995MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 2      1049kB  2097kB  1049kB               primary  bios_grub
 3      2097kB  130MB   128MB   fat32        primary  boot, esp
 4      130MB   1379MB  1249MB               primary
 5      1379MB  3995MB  2616MB  ext2         primary
 1      3995MB  3995MB  512B                 primary  msftdata

lsblk -o MODEL,NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE "/dev/sdb"
MODEL            NAME   FSTYPE  LABEL                       MOUNTPOINT  SIZE
                 sdb                                                    3.7G
                 &#9500;&#9472;sdb1                                                 512B
                 &#9500;&#9472;sdb2                                                   1M
                 &#9500;&#9472;sdb3 vfat    xenial64                                122M
                 &#9500;&#9472;sdb4 iso9660 Ubuntu-MATE 16.04 LTS amd64             1.2G
                 &#9492;&#9472;sdb5 ext4    casper-rw                               2.4G
</pre>
Done :-)
The target device is ready to use.
'/home/ventrical/Downloads/xenial-desktop-amd64.iso' was installed
Cleanup after mkusb finished :-)
Zenity error log-file 'zerrlog'=/tmp/tmp.46FRqI2rCz
Cleanup after mkusb finished :-)
---------------------------------------------------------------------------
Total time used [by mkusb] = 570 s; 00:09:30
ventrical@ventrical-luntiy-betatest:~$ 

but I still think not being able to copy 'n paste mkusb console report is a bug. If not , then why not just use the terminal option and forget about the console? It then does not make sense to have the 'console' part of the GUI.Also it is important to reboot after updating.

Regards..

#303

ventrical said: Nope! it's not there . Even with 'show hidden files' on.

It should go there when mkusb is run from the menu/dash/desktop icon. If mkusb is run from a terminal window,

sudo -H mkusb

the corresponding output goes into the terminal window, it becomes 'the mkusb console', and there will be no ~/mkusb.log file.

#304

ventrical said: I'm was using wily in this case , fully updated.

I have a *Wily* system installed in UEFI mode in my Toshiba. I'll update/dist-upgrade it to be fully up to date and try mkusb there. It worked two days ago, but maybe it was not fully updated.

*Edit:* after updating, I can still cut-n-paste from the zenity text-info window "mkusb console output loggged to '~/mkusb.log'". I can not reproduce the bug at 'Install ==> find target'.

#305

ventrical said: Very well..


[sudo] password for ventrical: 
---------------------------------------------------------------------------
start [mkusb 10.4] @ 2015-11-30 01:11:51 AM
---------------------------------------------------------------------------
Current directory=/home/ventrical
main: usbonly=true
main: liveonly=true
No input file specified yet
main: source=''
TERM=xterm-256color
ubuntu
---------------------------------------------------------------------------
menu_shell:
select_source: imagefile=/home/ventrical/Downloads/xenial-desktop-amd64.iso
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/ventrical/Downloads/xenial-desktop-amd64.iso
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /dev/loop0 is write-protected, mounting read-only
disk_name_type=desktop
Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 _found_ in iso-file
Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 _not_ in any possible target drive
Booted from: /dev/sda
ans=
---------------------------------------------------------------------------
menu_shell:
---------------------------------------------------------------------------
menu_shell:
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/ventrical/Downloads/xenial-desktop-amd64.iso
Booted from: /dev/sda
ans=1
mount: /dev/loop0 is write-protected, mounting read-only
 Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
mount: /dev/loop0 is write-protected, mounting read-only
'/home/ventrical/Downloads/xenial-desktop-amd64.iso' is identified as the source ISO file
<pre>
MODEL            NAME   FSTYPE  LABEL                       MOUNTPOINT  SIZE
                 sdb                                                    3.7G
                 &#9500;&#9472;sdb1                                                 512B
                 &#9500;&#9472;sdb2                                                   1M
                 &#9500;&#9472;sdb3 vfat    xenial64                                122M
                 &#9500;&#9472;sdb4 iso9660 Ubuntu-MATE 16.04 LTS amd64             1.2G
                 &#9492;&#9472;sdb5 ext4    casper-rw                               2.4G
</pre>
Using the file '/usr/share/mkusb/grub.cfg'
Using the file '/usr/share/mkusb/usb-pack_efi.tar.gz'
Clean for a GUID partition table
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): 
Command (? for help): 
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
Wipe the first megabyte (mibibyte) to get a clean boot area
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.376843 s, 2.8 MB/s
---------------------------------------------------------------------------
Selected percentage of remaining space for persistence = 100
---------------------------------------------------------------------------
 
preparing /dev/sdb3  ------------------------------------------------
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 1.03334 s, 1.0 MB/s
umount: /dev/sdb3: not mounted
mkfs.fat 3.0.28 (2015-05-16)
/dev/sdb3 has 123 heads and 62 sectors per track,
hidden sectors 0x1000;
logical sector size is 512,
using 0xf8 media descriptor, with 249856 sectors;
drive number 0x80;
filesystem has 2 32-bit FATs and 1 sector per cluster.
FAT size is 1922 sectors, and provides 245980 clusters.
There are 32 reserved sectors.
Volume ID is 9681a1eb, no volume label.
 
preparing /dev/sdb1  ------------------------------------------------
No space for NTFS partition /dev/sdb1, only placeholder
preparing /dev/sdb5  ------------------------------------------------
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.181953 s, 5.8 MB/s
umount: /dev/sdb5: not mounted
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 638715 4k blocks and 159680 inodes
Filesystem UUID: 6975c94c-d6e4-4772-9e9a-f39a0a0d2d3a
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

mount: /home/ventrical/Downloads/xenial-desktop-amd64.iso is already mounted
fatlabel: warning - lowercase labels might not work properly with DOS or Windows
tune2fs 1.42.12 (29-Aug-2014)
---------------------------------------------------------------------------
source=/home/ventrical/Downloads/xenial-desktop-amd64.iso
---------------------------------------------------------------------------
mount /dev/sdb3 /tmp/tmp.PqYzOdOVSf
mount: /dev/sdb1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
/dev/sdb3       121M   512  121M   1% /tmp/tmp.PqYzOdOVSf
UEFI Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
BIOS Bootloader:  Installing for i386-pc platform.
Installation finished. No error reported.
using usb-pack_efi.tar.gz
./
./boot/
./boot/grub/
./boot/memtest/
./boot/memtest/memtest86+-5.01.bin
./boot/memtest/memtest.bin
./EFI/
./EFI/BOOT/
./EFI/BOOT/bootx64.efi
./EFI/BOOT/bootia32.efi
---------------------------------------------------------------------------
do_n_show:
&lt; "/home/ventrical/Downloads/xenial-desktop-amd64.iso" pv -n | dd of=/dev/sdb4 bs=4096
 
( < "/home/ventrical/Downloads/xenial-desktop-amd64.iso" pv -n | dd of=/dev/sdb4 bs=4096 && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 )
Please wait for sync (flushing file system buffers to the device)
until 'Done' is written ...
'pv %'; 'dd final output'
4
9
14
19
23
28
31
31
31
32
32
32
32
32
33
33
33
33
33
33
33
33
33
33
33
34
34
34
34
34
34
34
34
34
34
34
34
34
34
35
35
35
35
35
35
35
35
35
36
36
36
36
36
37
37
37
38
38
38
38
39
39
39
40
40
40
41
41
41
42
42
42
43
43
43
44
44
44
45
45
45
46
46
46
47
47
47
48
48
48
49
49
49
50
50
50
51
51
52
52
52
53
53
53
54
54
54
55
55
55
56
56
56
57
57
58
58
58
59
59
59
60
60
60
61
61
61
62
62
62
63
63
63
64
64
65
65
65
66
66
66
67
67
67
68
68
68the corresponding output goes into the terminal window, it becomes 'the mkusb console', and there will be no ~/mkusb.log file.
69
69
70
70
70
71
71
71
72
72
72
73
73
73
74
74
74
75
75
76
76
76
77
77
77
78
78
78
79
79
79
80
80
81
81
81
82
82
82
83
83
83
84
84
84
85
85
85
86
86
87
87
87
88
88
88
89
89
89
90
90
90
91
91
91
92
92
93
93
93
94
94
94
95
95
95
96
96
96
97
97
98
98
98
99
99
99
100
300144+0 records in
300144+0 records out
1229389824 bytes (1.2 GB) copied, 291.296 s, 4.2 MB/s
Done
do_n_show: Work done
---------------------------------------------------------------------------
Syncing the target device ...
<pre>
parted -s "/dev/sdb" print
Model:   (scsi)
Disk /dev/sdb: 3995MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 2      1049kB  2097kB  1049kB               primary  bios_grub
 3      2097kB  130MB   128MB   fat32        primary  boot, esp
 4      130MB   1379MB  1249MB               primary
 5      1379MB  3995MB  2616MB  ext2         primary
 1      3995MB  3995MB  512B                 primary  msftdata

lsblk -o MODEL,NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE "/dev/sdb"
MODEL            NAME   FSTYPE  LABEL                       MOUNTPOINT  SIZE
                 sdb                                                    3.7G
                 &#9500;&#9472;sdb1                                                 512B
                 &#9500;&#9472;sdb2                                                   1M
                 &#9500;&#9472;sdb3 vfat    xenial64                                122M
                 &#9500;&#9472;sdb4 iso9660 Ubuntu-MATE 16.04 LTS amd64             1.2G
                 &#9492;&#9472;sdb5 ext4    casper-rw                               2.4G
</pre>
Done :-)
The target device is ready to use.
'/home/ventrical/Downloads/xenial-desktop-amd64.iso' was installed
Cleanup after mkusb finished :-)
Zenity error log-file 'zerrlog'=/tmp/tmp.46FRqI2rCz
Cleanup after mkusb finished :-)
---------------------------------------------------------------------------
Total time used [by mkusb] = 570 s; 00:09:30
ventrical@ventrical-luntiy-betatest:~$ 

but I still think not being able to copy 'n paste mkusb console report is a bug. If not , then why not just use the terminal option and forget about the console? It then does not make sense to have the 'console' part of the GUI.Also it is important to reboot after updating.

Regards..

I agree. But I can copy 'n paste mkusb console report from the zenity text-info window.

I just tried with my persistent live system now booted with the current lubuntu xenial iso i386 file. It works too. Maybe your system is borked because of a mismatch due to updates/upgrades of the developing system. A live system or a fresh installation might work properly for you.

#306

sudodus said:

By the way in my version of persistent live xenial system I have the following iso file (booting grub-n-iso)

lubuntu-xenial-desktop-i386.iso dated Nov 24,

and it does not suffer from the bugs that are affecting you. I'd better save it instead of overwriting in order to have a working xenial system ;-)

Sigh... my UEFI persistent USB drives are working just fine. I think you misunderstood me.

Regards..

#307

Just checked another install (trusty) and the mkusb.log is not there either.

#308

Yes, I think so too. Our replies are 'overlapping'. Anyway, this is what I have done right now:

  1. *Standard Ubuntu Wily amd64 installed in UEFI mode*

I updated/dist-upgraded it to be up to date today. I rebooted and tested mkusb. I can not reproduce the bugs you have.

  1. *Lubuntu Xenial i386 persistent live with the current daily iso file (today)*

I rebooted and tested mkusb. I can not reproduce the bugs you have.

Exactly what system are you testing now?

  • Is it *Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64* ?
  • Is it installed in UEFI mode?

In that case I can download, install and test it.

#309

ventrical said: Just checked another install (trusty) and the mkusb.log is not there either.

It seems that you are provoking a bug, that I have not been aware of.

  • What Trusty system is it, flavour, version, installed or live?
  • How do you start mkusb?

-o-

*Edit:* I think it is night at your place now. See you tomorrow (your tomorrow) :-)

  1. I can download Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64, install it in UEFI mode and start testing it in UEFI mode:

MATE works too: I have ~/mkusb.log, I can cut-n-paste from the zenity text-info window "mkusb console output loggged to '~/mkusb.log'". I can not reproduce the bug at 'Install ==> find target'.

  1. I have several Trusty iso files already - and I have tested mkusb with Lubuntu Trusty, recently mainly 14.04.3, both amd64 and i386.

Maybe because I have not yet had any tea this morning, but I don't understand. You still have problems, now even in Trusty, and either I just don't get what the problem is, or all these versions of Ubuntu are working one way in your computers and another way in my computers.

#310

Let's take a back step :)

  1. You asked us to test mkusb 10.4.1. I already have two separate machines with unstable ppa. When I update/upgrade those machines, mkusb gets updated/upgraded also.
  1. mkusb is working just fine in creating persistive drives in UEFI mode . Yep, I can boot them in UEFI mode.:)

Of course, as you suggested, just use:

  1. Bugs: On the one update/upgrade of mkusb to 10.4.1 when I rebooted I got <system error> with Zenity (as I have uploaded screenshot in previous posts). This bug has only happened recently and it is annoying *bug* and it is just too easy to say the I need to re-install a fresh install. Also the mkusb console and not being able to copy n paste from there. So the bugs I am reporting are *cosmetic* bugs. The zenity bug is gone after second reboot.

sudo -H mkusb

and all is well.

When I have time I will try to emulate bug.

Thank you ! :)

Ok .. question. I want to reinstall mkusb .. so I have to purge and remove :ppa.

  1. Are there problems with purging mkusb from system?
  2. What are simple terminal commands to do so.?

#note#

Yes .. it was 2:00am in morning my time I think :)

Regards..

#311

sudodus said: It seems that you are provoking a bug, that I have not been aware of.

Maybe because I have not yet had any tea this morning, but I don't understand. You still have problems, now even in Trusty, and either I just don't get what the problem is, or all these versions of Ubuntu are working one way in your computers and another way in my computers.

Ok.. I double checked and the *Trusty* install is actually a vivid install. So this is a management problem at my end. My apologies.

I left you a message about purging/reinstalling mkusb. I would like to try this and also I will put mkusb on stable system.

Me. Having tea now! :) Can't do nothing without tea :)

Regards..

#312

ventrical said: Let's take a back step :)

:-)>

:-)>

Of course, as you suggested, just use:

  1. You asked us to test mkusb 10.4.1. I already have two separate machines with unstable ppa. When I update/upgrade those machines, mkusb gets updated/upgraded also.
  2. mkusb is working just fine in creating persistive drives in UEFI mode . Yep, I can boot them in UEFI mode.:)
  3. Bugs: On the one update/upgrade of mkusb to 10.4.1 when I rebooted I got <system error> with Zenity (as I have uploaded screenshot in previous posts). This bug has only happened recently and it is annoying *bug* and it is just too easy to say the I need to re-install a fresh install. Also the mkusb console and not being able to copy n paste from there. So the bugs I am reporting are *cosmetic* bugs. The zenity bug is gone after second reboot.

sudo -H mkusb

and all is well.

Agreed - cosmetic, but it is possible for me to copy-n-paste from the zenity window (showing ~/mkusb.log). I wonder why you have problems with it.>

When I have time I will try to emulate bug.

Thank you ! :)

Ok .. question. I want to reinstall mkusb .. so I have to purge and remove :ppa.

  1. Are there problems with purging mkusb from system?
  2. What are simple terminal commands to do so.?

#note#

Yes .. it was 2:00am in morning my time I think :)

Regards..

*Answer:* No problems, it should work with

sudo apt-get remove mkusb

or if you have also mkusb-nox

sudo apt-get remove mkusb mkusb-nox

but I think files created by mkusb when you run it will remain, for example ~/mkusb.log.

[hr][/hr] By the way, I open a terminal window and change directory to where I have the iso files and run this command. I think it is more convenient than via all the menus, there are enough zenity windows for me ;-)


[SIZE=3]sudo -H mkusb file.iso **[COLOR="#0000cc"]p[/COLOR]**  # to make a **[COLOR="#0000cc"]p[/COLOR]**ersistent live drive from 'file.iso'[/SIZE]
#313

[SIZE=4]A compressed image file with a persistent live system of Lubuntu 14.04.3 LTS (32-bit) and mkusb version 10.4[/SIZE]

Installed Ubuntu based systems in UEFI mode can use mkusb to create 'any' system by cloning, where the installed system depends only on the contents of the iso file or compressed image file. But the method to create persistent live systems is limited to UEFI mode (with and without secure boot).

In order to provide an alternative that works in BIOS mode, this compressed image file was created. It contains a persistent live system of *Lubuntu 14.04.3 LTS i386* (32-bit) and *mkusb version 10.4*. And this system is a very good booter in 32-bit as well as 64-bit PC (Intel/AMD) computers in BIOS mode and UEFI mode. But it does not work with secure boot. So this way it is possible to create a persistent live system that boots in BIOS mode (with 32-bit as well as 64-bit PCs) from a computer running in UEFI mode.

This compressed image file can be downloaded from this link: dd_lubu-14.04.3-desktop-i386_one-pendrive_7.8GB.img.xz and has the following md5sum

d001805e78369dba97f1183e5d31da6b  dd_lubu-14.04.3-desktop-i386_one-pendrive_7.8GB.img.xz

See this link to post #49 in the thread 'One pendrive for all PC (Intel/AMD) computers - single-boot dual-boot multi-boot' for more details.

#314

[SIZE=4]mkusb version 10.4.2[/SIZE]

  1. This version is released to solve problems with certain fstab configurations (the content of the file /etc/fstab). grep -m1 is used in the calculation of infstb in order to get only one line. This decides which drives are found in fstab and considered busy, not available as target devices for mkusb.
  1. The linux manual 'man mkusb' is updated.

[hr][/hr] You get/update this new version 10.4.2 from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

It is tested but needs more testing before uploading to the stable PPA 'ppa:mkusb/ppa'. You are welcome to participate in the testing :-)

#315

[SIZE=4]mkusb version 10.4.3[/SIZE]

This version is released to fix a couple of minor issues.

  1. It is now possible to select any file-name '*' for the source file, but later on there is a warning and a tip, "There should be an extension, and the extension should be written with lower-case letters, 'File.iso' or 'file.img' or 'File.img.gz' or 'file.img.xz'". See the attached screenshots.
  1. Another LANG="$curlang" when exiting from select-device fixes an issue when using non-standard characters in file names, for example Swedish letters åäö.

[hr][/hr] You get/update this new version 10.4.3 from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

It is tested but needs more testing before uploading to the stable PPA 'ppa:mkusb/ppa'. You are welcome to participate in the testing :-)

#316

I'm in... :)

#317

sammiev said: I'm in... :)

Thanks :-)

#318

[SIZE=4]mkusb version 10.4.4[/SIZE]

mkusb can select block device as input via the menu (before it could do it only via the command line)

if test -f "$imagefile" || test -b "$imagefile"

and s[dr]? in

--file-filter={*.i[sm][og]*,*.iso,*.img,*.img.?z,s[dr]?,*}

to make it easier to find mass storage devices /dev/sda, /dev/sdb ... and optical devices /dev/sr0, /dev/sr1 ...

See the attached screenshot.

This makes it easier and safer to clone devices. mkusb helps by wrapping 'a safety belt around dd'.

[hr][/hr] You get/update this new version 10.4.4 from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

It is tested but needs more testing before uploading to the stable PPA 'ppa:mkusb/ppa'. You are welcome to participate in the testing :-)

#319

OK had the update today to the latest unstable from yesterday installation.

Will play with it tonight.

Thanks

#320

Everything I tested worked great today.

Will do a few more tomorrow.

Is there anyone thing or two you want tested?

#321

sammiev said: Everything I tested worked great today.

Will do a few more tomorrow.

Is there anyone thing or two you want tested?

Thanks sammiev :-)

I guess you have tested some basic stuff and 'the latest and greatest'. Please tell me details about what you have tested!

-o-

  1. If you have suitable hardware, please test the three methods described to make persistent live drives at

mkusb/persistent

  1. and please test the backup and restore system described at

Backup and restore of persistent overlay data

#322

sudodus said: Thanks sammiev :-)

I guess you have tested some basic stuff and 'the latest and greatest'. Please tell me details about what you have tested!

-o-

  1. If you have suitable hardware, please test the three methods described to make persistent live drives at

mkusb/persistent

  1. and please test the backup and restore system described at

Backup and restore of persistent overlay data

Sorry to get back to this sooner. Was away all day.

I tested 1. which you posted the day before with most of the other options MSKUSB offers.

Will work on 2. tomorrow.

Everything tested on my side worked as expected. :)

#323

I'm looking forward to your final results, *sammiev* :-)

#324

Everything worked perfect until the restore and then again it does say successful.

Please check out the last few lines.

Many Thanks

sam@sam-G-L650:~$ cd /media/sam/usbdata
sam@sam-G-L650:/media/sam/usbdata$ ls -l
total 12
-rwxrwxrwx 1 sam sam 3582 Dec 15 08:31 backup
-rwxrwxrwx 1 sam sam 4555 Dec 15 08:31 restore
sam@sam-G-L650:/media/sam/usbdata$ bash backup
[sudo] password for sam: 
Do you want to back up to '/media/sam/usbdata'? y
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
casper-rw: 657/89760 files (1.5% non-contiguous), 26140/358656 blocks
ls: cannot access *-casper-rw.tar.gz: No such file or directory
./
./upper/
./upper/home/
./upper/home/ubuntu-gnome/
./upper/home/ubuntu-gnome/.gnupg/
./upper/home/ubuntu-gnome/.gnupg/secring.gpg
./upper/home/ubuntu-gnome/.gnupg/pubring.gpg
./upper/home/ubuntu-gnome/.gnupg/trustdb.gpg
./upper/home/ubuntu-gnome/.gnupg/gpg.conf
./upper/home/ubuntu-gnome/.gconf/
./upper/home/ubuntu-gnome/Public/
./upper/home/ubuntu-gnome/.ICEauthority
./upper/home/ubuntu-gnome/Downloads/
./upper/home/ubuntu-gnome/Pictures/
./upper/home/ubuntu-gnome/.local/
./upper/home/ubuntu-gnome/.local/share/
./upper/home/ubuntu-gnome/.local/share/evolution/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/system/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/system/tasks.ics
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/system/
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/system/calendar.ics
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/system/
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/system/contacts.db
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/system/photos/
./upper/home/ubuntu-gnome/.local/share/evolution/mail/
./upper/home/ubuntu-gnome/.local/share/evolution/mail/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/system/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/system/journal.ics
./upper/home/ubuntu-gnome/.local/share/gsettings-data-convert
./upper/home/ubuntu-gnome/.local/share/folks/
./upper/home/ubuntu-gnome/.local/share/folks/relationships.ini
./upper/home/ubuntu-gnome/.local/share/icc/
./upper/home/ubuntu-gnome/.local/share/icc/edid-958165f37ed2ae28b87c75c9c3b6f1e5.icc
./upper/home/ubuntu-gnome/.local/share/gnome-shell/
./upper/home/ubuntu-gnome/.local/share/telepathy/
./upper/home/ubuntu-gnome/.local/share/telepathy/mission-control/
./upper/home/ubuntu-gnome/.local/share/telepathy/mission-control/accounts-goa.cfg
./upper/home/ubuntu-gnome/.local/share/telepathy/mission-control/accounts.cfg
./upper/home/ubuntu-gnome/.local/share/zeitgeist/
./upper/home/ubuntu-gnome/.local/share/zeitgeist/activity.sqlite
./upper/home/ubuntu-gnome/.local/share/zeitgeist/activity.sqlite-shm
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/position.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/termlist.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/iamchert
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/record.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/postlist.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/position.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/termlist.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/postlist.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/position.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/record.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/termlist.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/postlist.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/flintlock
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/record.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/activity.sqlite-wal
./upper/home/ubuntu-gnome/.local/share/sounds/
./upper/home/ubuntu-gnome/.local/share/gnome-settings-daemon/
./upper/home/ubuntu-gnome/.local/share/gnome-settings-daemon/input-sources-converted
./upper/home/ubuntu-gnome/.local/share/applications/
./upper/home/ubuntu-gnome/.local/share/.converted-launchers
./upper/home/ubuntu-gnome/.local/share/keyrings/
./upper/home/ubuntu-gnome/.local/share/tracker/
./upper/home/ubuntu-gnome/.local/share/tracker/data/
./upper/home/ubuntu-gnome/.local/share/tracker/data/tracker-store.ontology.journal
./upper/home/ubuntu-gnome/.local/share/tracker/data/tracker-store.journal
./upper/home/ubuntu-gnome/.local/share/gvfs-metadata/
./upper/home/ubuntu-gnome/.local/share/gvfs-metadata/home
./upper/home/ubuntu-gnome/.local/share/gvfs-metadata/home-99cc27f4.log
./upper/home/ubuntu-gnome/.local/share/session_migration-gnome
./upper/home/ubuntu-gnome/.bashrc
./upper/home/ubuntu-gnome/Videos/
./upper/home/ubuntu-gnome/.profile
./upper/home/ubuntu-gnome/Music/
./upper/home/ubuntu-gnome/Documents/
./upper/home/ubuntu-gnome/.bash_logout
./upper/home/ubuntu-gnome/Desktop/
./upper/home/ubuntu-gnome/Desktop/ubiquity.desktop
./upper/home/ubuntu-gnome/Templates/
./upper/home/ubuntu-gnome/.cache/
./upper/home/ubuntu-gnome/.cache/evolution/
./upper/home/ubuntu-gnome/.cache/evolution/tasks/
./upper/home/ubuntu-gnome/.cache/evolution/tasks/trash/
./upper/home/ubuntu-gnome/.cache/evolution/calendar/
./upper/home/ubuntu-gnome/.cache/evolution/calendar/trash/
./upper/home/ubuntu-gnome/.cache/evolution/addressbook/
./upper/home/ubuntu-gnome/.cache/evolution/addressbook/trash/
./upper/home/ubuntu-gnome/.cache/evolution/sources/
./upper/home/ubuntu-gnome/.cache/evolution/sources/trash/
./upper/home/ubuntu-gnome/.cache/evolution/mail/
./upper/home/ubuntu-gnome/.cache/evolution/mail/trash/
./upper/home/ubuntu-gnome/.cache/evolution/memos/
./upper/home/ubuntu-gnome/.cache/evolution/memos/trash/
./upper/home/ubuntu-gnome/.cache/folks/
./upper/home/ubuntu-gnome/.cache/folks/avatars/
./upper/home/ubuntu-gnome/.cache/upstart/
./upper/home/ubuntu-gnome/.cache/upstart/gnome-keyring-gpg.log
./upper/home/ubuntu-gnome/.cache/upstart/gnome-settings-daemon.log
./upper/home/ubuntu-gnome/.cache/upstart/dbus.log
./upper/home/ubuntu-gnome/.cache/upstart/gnome-session-GNOME.log
./upper/home/ubuntu-gnome/.cache/upstart/at-spi2-registryd.log
./upper/home/ubuntu-gnome/.cache/upstart/gnome-keyring-ssh.log
./upper/home/ubuntu-gnome/.cache/upstart/dbus-session
./upper/home/ubuntu-gnome/.cache/upstart/update-notifier-release.log
./upper/home/ubuntu-gnome/.cache/upstart/im-config.log
./upper/home/ubuntu-gnome/.cache/upstart/ssh-agent.log
./upper/home/ubuntu-gnome/.cache/event-sound-cache.tdb.ce1ba8862842a0a1529b230b567019ec.x86_64-pc-linux-gnu
./upper/home/ubuntu-gnome/.cache/fontconfig/
./upper/home/ubuntu-gnome/.cache/fontconfig/cabbd14511b9e8a55e92af97fb3a0461-le64.cache-4
./upper/home/ubuntu-gnome/.cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-le64.cache-4
./upper/home/ubuntu-gnome/.cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-4
./upper/home/ubuntu-gnome/.cache/fontconfig/CACHEDIR.TAG
./upper/home/ubuntu-gnome/.cache/motd.legal-displayed
./upper/home/ubuntu-gnome/.cache/logrotate/
./upper/home/ubuntu-gnome/.cache/logrotate/status
./upper/home/ubuntu-gnome/.cache/tracker/
./upper/home/ubuntu-gnome/.cache/tracker/meta.db
./upper/home/ubuntu-gnome/.cache/tracker/no-need-mtime-check.txt
./upper/home/ubuntu-gnome/.cache/tracker/db-version.txt
./upper/home/ubuntu-gnome/.cache/tracker/miner-applications-locale.txt
./upper/home/ubuntu-gnome/.cache/tracker/first-index.txt
./upper/home/ubuntu-gnome/.cache/tracker/last-crawl.txt
./upper/home/ubuntu-gnome/.cache/tracker/meta.db-wal
./upper/home/ubuntu-gnome/.cache/tracker/meta.db-shm
./upper/home/ubuntu-gnome/.cache/tracker/ontologies.gvdb
./upper/home/ubuntu-gnome/.cache/tracker/db-locale.txt
./upper/home/ubuntu-gnome/.cache/gdm/
./upper/home/ubuntu-gnome/.cache/gdm/session.log
./upper/home/ubuntu-gnome/.cache/ibus/
./upper/home/ubuntu-gnome/.cache/ibus/bus/
./upper/home/ubuntu-gnome/.cache/ibus/bus/registry
./upper/home/ubuntu-gnome/.cache/gstreamer-1.0/
./upper/home/ubuntu-gnome/.cache/gstreamer-1.0/registry.x86_64.bin
./upper/home/ubuntu-gnome/.config/
./upper/home/ubuntu-gnome/.config/evolution/
./upper/home/ubuntu-gnome/.config/evolution/sources/
./upper/home/ubuntu-gnome/.config/update-notifier/
./upper/home/ubuntu-gnome/.config/user-dirs.locale
./upper/home/ubuntu-gnome/.config/gtk-3.0/
./upper/home/ubuntu-gnome/.config/gtk-3.0/bookmarks
./upper/home/ubuntu-gnome/.config/upstart/
./upper/home/ubuntu-gnome/.config/dconf/
./upper/home/ubuntu-gnome/.config/dconf/user
./upper/home/ubuntu-gnome/.config/libaccounts-glib/
./upper/home/ubuntu-gnome/.config/libaccounts-glib/accounts.db
./upper/home/ubuntu-gnome/.config/gnome-session/
./upper/home/ubuntu-gnome/.config/gnome-session/saved-session/
./upper/home/ubuntu-gnome/.config/nautilus/
./upper/home/ubuntu-gnome/.config/tracker/
./upper/home/ubuntu-gnome/.config/pulse/
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-default-sink
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-stream-volumes.tdb
./upper/home/ubuntu-gnome/.config/pulse/cookie
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-device-volumes.tdb
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-card-database.tdb
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-default-source
./upper/home/ubuntu-gnome/.config/goa-1.0/
./upper/home/ubuntu-gnome/.config/ibus/
./upper/home/ubuntu-gnome/.config/ibus/bus/
./upper/home/ubuntu-gnome/.config/ibus/bus/ce1ba8862842a0a1529b230b567019ec-unix-0
./upper/home/ubuntu-gnome/.config/user-dirs.dirs
./upper/home/ubuntu-gnome/.ssh/
./upper/cdrom/
./upper/etc/
./upper/etc/shadow
./upper/etc/pam.d/
./upper/etc/pam.d/login
./upper/etc/login.defs
./upper/etc/udev/
./upper/etc/udev/rules.d/
./upper/etc/udev/rules.d/70-persistent-net.rules
./upper/etc/group
./upper/etc/mtab
./upper/etc/shadow-
./upper/etc/gshadow
./upper/etc/mtab.fuselock
./upper/etc/ssl/
./upper/etc/ssl/private/
./upper/etc/ssl/private/ssl-cert-snakeoil.key
./upper/etc/ssl/certs/
./upper/etc/ssl/certs/8af41246
./upper/etc/ssl/certs/ssl-cert-snakeoil.pem
./upper/etc/hosts
./upper/etc/init/
./upper/etc/init/ureadahead-other.conf
./upper/etc/init/tty4.conf
./upper/etc/init/tty1.conf
./upper/etc/init/ureadahead.conf
./upper/etc/init/tty6.conf
./upper/etc/init/tty5.conf
./upper/etc/init/hwclock-save.conf
./upper/etc/init/tty2.conf
./upper/etc/init/tty3.conf
./upper/etc/passwd
./upper/etc/sudoers.d/
./upper/etc/sudoers.d/casper
./upper/etc/default/
./upper/etc/default/locale
./upper/etc/nologin
./upper/etc/xdg/
./upper/etc/xdg/autostart/
./upper/etc/xdg/autostart/screen-reader-profile.desktop
./upper/etc/.pwd.lock
./upper/etc/locale.gen
./upper/etc/network/
./upper/etc/network/interfaces
./upper/etc/group-
./upper/etc/cups/
./upper/etc/cups/ssl/
./upper/etc/cups/ppd/
./upper/etc/gshadow-
./upper/etc/gdm/
./upper/etc/gdm/custom.conf
./upper/etc/apt/
./upper/etc/apt/sources.list~
./upper/etc/apt/sources.list
./upper/etc/apt/apt.conf.d/
./upper/etc/apt/apt.conf.d/00aptitude
./upper/etc/passwd-
./upper/etc/fstab
./upper/etc/hostname
./upper/etc/casper.conf
./upper/media/
./upper/media/ubuntu-gnome/
./upper/media/ubuntu-gnome/usbdata/
./upper/media/ubuntu-gnome/casper-rw/
./upper/media/cdrom
./upper/tmp/
./upper/tmp/debconf.THX2rP/
./upper/tmp/debconf.THX2rP/config.dat
./upper/tmp/debconf.THX2rP/passwords.dat
./upper/tmp/debconf.THX2rP/config.dat-old
./upper/tmp/debconf.THX2rP/debconf.conf
./upper/var/
./upper/var/log/
./upper/var/log/wtmp
./upper/var/log/udev
./upper/var/log/upstart/
./upper/var/log/upstart/thermald.log
./upper/var/log/upstart/procps-virtual-filesystems.log
./upper/var/log/upstart/container-detect.log
./upper/var/log/upstart/cryptdisks.log
./upper/var/log/upstart/systemd-logind.log
./upper/var/log/upstart/cups.log
./upper/var/log/upstart/procps-static-network-up.log
./upper/var/log/upstart/alsa-state.log
./upper/var/log/upstart/alsa-restore.log
./upper/var/log/upstart/whoopsie.log
./upper/var/log/upstart/network-manager.log
./upper/var/log/upstart/modemmanager.log
./upper/var/log/upstart/console-setup.log
./upper/var/log/Xorg.0.log
./upper/var/log/kern.log
./upper/var/log/faillog
./upper/var/log/dmesg
./upper/var/log/auth.log
./upper/var/log/cups/
./upper/var/log/cups/access_log
./upper/var/log/cups/error_log
./upper/var/log/cups/page_log
./upper/var/log/syslog
./upper/var/log/gdm/
./upper/var/log/gdm/:0-slave.log
./upper/var/log/gdm/:0.log
./upper/var/log/casper.log
./upper/var/log/dmesg.0
./upper/var/log/boot.log
./upper/var/log/lastlog
./upper/var/log/unattended-upgrades/
./upper/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
./upper/var/lib/
./upper/var/lib/NetworkManager/
./upper/var/lib/NetworkManager/timestamps
./upper/var/lib/NetworkManager/dhclient-d6967d6c-12d4-40bf-a159-9601bd5ea2fe-eth0.lease
./upper/var/lib/NetworkManager/NetworkManager.state
./upper/var/lib/update-notifier/
./upper/var/lib/update-notifier/fsck-at-reboot
./upper/var/lib/update-notifier/updates-available
./upper/var/lib/colord/
./upper/var/lib/colord/storage.db
./upper/var/lib/colord/mapping.db
./upper/var/lib/plymouth/
./upper/var/lib/plymouth/boot-duration
./upper/var/lib/xkb/
./upper/var/lib/xkb/server-34CEB476A3CB596DA76FD7010A029F76732EF824.xkm
./upper/var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
./upper/var/lib/udisks2/
./upper/var/lib/udisks2/mounted-fs
./upper/var/lib/rfkill/
./upper/var/lib/rfkill/saved-state
./upper/var/lib/urandom/
./upper/var/lib/urandom/random-seed
./upper/var/lib/belocs/
./upper/var/lib/belocs/locales.dep
./upper/var/lib/belocs/hashfile.old
./upper/var/lib/belocs/hashfile
./upper/var/lib/belocs/list
./upper/var/lib/belocs/hashfile.new
./upper/var/lib/dpkg/
./upper/var/lib/dpkg/lock
./upper/var/lib/dpkg/diversions-old
./upper/var/lib/dpkg/diversions
./upper/var/lib/locales/
./upper/var/lib/locales/supported.d/
./upper/var/lib/locales/supported.d/local
./upper/var/lib/AccountsService/
./upper/var/lib/AccountsService/users/
./upper/var/lib/AccountsService/users/ubuntu-gnome
./upper/var/lib/dbus/
./upper/var/lib/dbus/machine-id
./upper/var/lib/alsa/
./upper/var/lib/alsa/asound.state.lock
./upper/var/lib/alsa/asound.state
./upper/var/lib/apt/
./upper/var/lib/apt/cdroms.list
./upper/var/lib/apt/lists/
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_universe_binary-amd64_Packages
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_restricted_binary-amd64_Packages
./upper/var/lib/apt/lists/lock
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_main_binary-amd64_Packages
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_multiverse_binary-amd64_Packages
./upper/var/lib/apt/lists/partial/
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_Release
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_Release.gpg
./upper/var/lib/polkit-1/
./upper/var/lib/polkit-1/localauthority/
./upper/var/lib/polkit-1/localauthority/10-vendor.d/
./upper/var/lib/polkit-1/localauthority/10-vendor.d/10-live-cd.pkla
./upper/var/lib/polkit-1/localauthority/50-local.d/
./upper/var/lib/polkit-1/localauthority/50-local.d/disable-hibernate.pkla
./upper/var/lib/ubuntu-release-upgrader/
./upper/var/lib/ubuntu-release-upgrader/release-upgrade-available
./upper/var/tmp/
./upper/var/spool/
./upper/var/spool/cups/
./upper/var/spool/cups/tmp/
./upper/var/cache/
./upper/var/cache/debconf/
./upper/var/cache/debconf/templates.dat
./upper/var/cache/debconf/config.dat
./upper/var/cache/debconf/passwords.dat
./upper/var/cache/debconf/config.dat-old
./upper/var/cache/fontconfig/
./upper/var/cache/fontconfig/cabbd14511b9e8a55e92af97fb3a0461-le64.cache-4
./upper/var/cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-le64.cache-4
./upper/var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-4
./upper/var/cache/cups/
./upper/var/cache/cups/rss/
./upper/var/cache/cups/job.cache
./upper/var/cache/apt/
./upper/var/cache/apt/archives/
./upper/var/cache/apt/archives/lock
./upper/var/cache/apt/pkgcache.bin
./upper/var/cache/apt/srcpkgcache.bin
./upper/boot/
./upper/boot/grub/
./upper/boot/grub/grubenv
./upper/rofs/
./upper/usr/
./upper/usr/lib/
./upper/usr/lib/python3/
./upper/usr/lib/python3/dist-packages/
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/__pycache__/
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/__pycache__/add_license_key_plugin.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/defer/
./upper/usr/lib/python3/dist-packages/defer/__pycache__/
./upper/usr/lib/python3/dist-packages/defer/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/defer/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/defer/__pycache__/version.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/config.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/logger.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/networking.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/lock.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/pkcompat.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/enums.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/policykit1.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/errors.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/progress.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/core.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/loop.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/worker.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/MetaRelease.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/__pycache__/
./upper/usr/lib/python3/dist-packages/UpdateManager/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/
./upper/usr/lib/python3/dist-packages/__pycache__/apport_python_hook.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/pkg_resources.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/lsb_release.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/language_support_pkgs.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/
./upper/usr/lib/python3/dist-packages/gi/repository/
./upper/usr/lib/python3/dist-packages/gi/repository/__pycache__/
./upper/usr/lib/python3/dist-packages/gi/repository/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/
./upper/usr/lib/python3/dist-packages/gi/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_option.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/module.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_constants.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/types.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_propertyhelper.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/importer.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/docstring.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_signalhelper.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/GObject.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/GLib.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/Gio.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_expat_introspect_parser.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/lowlevel.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/proxies.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/service.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/types.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/glib.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/bus.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_compat.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/connection.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_dbus.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/exceptions.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_version.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/decorators.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/mainloop/
./upper/usr/lib/python3/dist-packages/dbus/mainloop/__pycache__/
./upper/usr/lib/python3/dist-packages/dbus/mainloop/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/mainloop/__pycache__/glib.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/sourceslist.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/distro.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/distinfo.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/
./upper/usr/lib/python3/dist-packages/apt/__pycache__/
./upper/usr/lib/python3/dist-packages/apt/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/cdrom.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/debfile.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/cache.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/package.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/auth.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/progress/
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/text.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/base.cpython-34.pyc
./upper/usr/lib/update-notifier/
./upper/usr/lib/update-notifier/apt-check
./upper/usr/lib/update-notifier/apt-check.distrib
./upper/usr/lib/locale/
./upper/usr/lib/locale/locale-archive
./upper/usr/lib/python3.4/
./upper/usr/lib/python3.4/xml/
./upper/usr/lib/python3.4/xml/parsers/
./upper/usr/lib/python3.4/xml/parsers/__pycache__/
./upper/usr/lib/python3.4/xml/parsers/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/xml/parsers/__pycache__/expat.cpython-34.pyc
./upper/usr/lib/python3.4/xml/etree/
./upper/usr/lib/python3.4/xml/etree/__pycache__/
./upper/usr/lib/python3.4/xml/etree/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/xml/etree/__pycache__/ElementPath.cpython-34.pyc
./upper/usr/lib/python3.4/xml/etree/__pycache__/ElementTree.cpython-34.pyc
./upper/usr/lib/python3.4/xml/__pycache__/
./upper/usr/lib/python3.4/xml/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/collections/
./upper/usr/lib/python3.4/collections/__pycache__/
./upper/usr/lib/python3.4/collections/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/collections/__pycache__/abc.cpython-34.pyc
./upper/usr/lib/python3.4/ctypes/
./upper/usr/lib/python3.4/ctypes/__pycache__/
./upper/usr/lib/python3.4/ctypes/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/ctypes/__pycache__/_endian.cpython-34.pyc
./upper/usr/lib/python3.4/ctypes/__pycache__/util.cpython-34.pyc
./upper/usr/lib/python3.4/plat-x86_64-linux-gnu/
./upper/usr/lib/python3.4/plat-x86_64-linux-gnu/__pycache__/
./upper/usr/lib/python3.4/plat-x86_64-linux-gnu/__pycache__/_sysconfigdata_m.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/
./upper/usr/lib/python3.4/__pycache__/_sysconfigdata.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/heapq.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/textwrap.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/pkgutil.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_weakrefset.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/lzma.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/string.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_collections_abc.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/symbol.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/linecache.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/locale.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/io.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/operator.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/hashlib.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sre_parse.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tempfile.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/threading.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/quopri.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/stat.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/shutil.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/inspect.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sitecustomize.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/platform.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/struct.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_bootlocale.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/types.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/reprlib.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sysconfig.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/uuid.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/gettext.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/pickle.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/functools.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/re.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/fnmatch.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/codecs.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/contextlib.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/posixpath.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/__future__.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tokenize.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/opcode.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/site.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/ast.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/keyword.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/shlex.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/base64.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/selectors.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/copyreg.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/socket.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/dis.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/queue.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/bisect.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/os.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/random.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/gzip.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/subprocess.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/warnings.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/bz2.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/traceback.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/configparser.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/weakref.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/netrc.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/imp.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/copy.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sre_constants.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/token.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/datetime.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/enum.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/genericpath.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tty.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/calendar.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_sitebuiltins.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/abc.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/ssl.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/optparse.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_compat_pickle.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tarfile.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/uu.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/glob.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/zipfile.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sre_compile.cpython-34.pyc
./upper/usr/lib/python3.4/http/
./upper/usr/lib/python3.4/http/__pycache__/
./upper/usr/lib/python3.4/http/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/http/__pycache__/client.cpython-34.pyc
./upper/usr/lib/python3.4/email/
./upper/usr/lib/python3.4/email/__pycache__/
./upper/usr/lib/python3.4/email/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/header.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/_policybase.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/parser.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/_encoded_words.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/iterators.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/base64mime.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/errors.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/quoprimime.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/_parseaddr.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/charset.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/feedparser.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/message.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/encoders.cpython-34.pyc
./upper/usr/lib/python3.4/importlib/
./upper/usr/lib/python3.4/importlib/__pycache__/
./upper/usr/lib/python3.4/importlib/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/importlib/__pycache__/util.cpython-34.pyc
./upper/usr/lib/python3.4/importlib/__pycache__/machinery.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/
./upper/usr/lib/python3.4/encodings/__pycache__/
./upper/usr/lib/python3.4/encodings/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/aliases.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/latin_1.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/ascii.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/utf_8.cpython-34.pyc
./upper/usr/lib/python3.4/logging/
./upper/usr/lib/python3.4/logging/__pycache__/
./upper/usr/lib/python3.4/logging/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/logging/__pycache__/handlers.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/
./upper/usr/lib/python3.4/urllib/__pycache__/
./upper/usr/lib/python3.4/urllib/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/request.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/response.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/parse.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/error.cpython-34.pyc
./upper/usr/lib/ubuntu-release-upgrader/
./upper/usr/lib/ubuntu-release-upgrader/check-new-release-gtk
./upper/usr/lib/ubuntu-release-upgrader/check-new-release
./upper/usr/lib/ubuntu-release-upgrader/check-new-release.distrib
./upper/usr/lib/ubuntu-release-upgrader/check-new-release-gtk.distrib
./upper/usr/sbin/
./upper/usr/sbin/update-initramfs.distrib
./upper/usr/sbin/anacron.distrib
./upper/usr/sbin/anacron
./upper/usr/sbin/update-initramfs
./upper/usr/share/
./upper/usr/share/gnome-shell/
./upper/usr/share/gnome-shell/js/
./upper/usr/share/gnome-shell/js/gdm/
./upper/usr/share/gnome-shell/js/gdm/loginDialog.js
./upper/usr/share/glib-2.0/
./upper/usr/share/glib-2.0/schemas/
./upper/usr/share/glib-2.0/schemas/casper.gschema.override
./upper/usr/share/glib-2.0/schemas/gschemas.compiled
./upper/usr/share/applications/
./upper/usr/share/applications/ubiquity.desktop
./lost+found/
./work/
./work/work/
./format
Backup to '/media/sam/usbdata/1-casper-rw.tar.gz' successful
sam@sam-G-L650:/media/sam/usbdata$ ls -l
total 27224
-rwxrwxrwx 1 sam sam 27861369 Dec 17 19:58 1-casper-rw.tar.gz
-rwxrwxrwx 1 sam sam     3582 Dec 15 08:31 backup
-rwxrwxrwx 1 sam sam     4555 Dec 15 08:31 restore
sam@sam-G-L650:/media/sam/usbdata$ bash restore
umount: /dev/sdb5: not mounted
Do you want to restore from '/media/sam/usbdata'? y
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
casper-rw: 657/89760 files (1.5% non-contiguous), 26140/358656 blocks
-----------------------------------------------------------------
Restore from '/media/sam/usbdata/1-casper-rw.tar.gz'
-----------------------------------------------------------------
current directory: /mnt
Filesystem     1K-blocks  Used Available Use% Mounted on
/dev/sdb5        1412048 81984   1241952   7% /mnt
/dev/sdb5: LABEL="casper-rw" TYPE="ext4" PARTLABEL="primary" PARTUUID="1156c214-665e-4f7d-92b2-9e6844a4c6d4"
ls: format	lost+found  upper  work
-----------------------------------------------------------------
Is this the correct directory to restore? (y/n) y
./
./upper/
./upper/home/
./upper/home/ubuntu-gnome/
./upper/home/ubuntu-gnome/.gnupg/
./upper/home/ubuntu-gnome/.gnupg/secring.gpg
./upper/home/ubuntu-gnome/.gnupg/pubring.gpg
./upper/home/ubuntu-gnome/.gnupg/trustdb.gpg
./upper/home/ubuntu-gnome/.gnupg/gpg.conf
./upper/home/ubuntu-gnome/.gconf/
./upper/home/ubuntu-gnome/Public/
./upper/home/ubuntu-gnome/.ICEauthority
./upper/home/ubuntu-gnome/Downloads/
./upper/home/ubuntu-gnome/Pictures/
./upper/home/ubuntu-gnome/.local/
./upper/home/ubuntu-gnome/.local/share/
./upper/home/ubuntu-gnome/.local/share/evolution/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/system/
./upper/home/ubuntu-gnome/.local/share/evolution/tasks/system/tasks.ics
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/system/
./upper/home/ubuntu-gnome/.local/share/evolution/calendar/system/calendar.ics
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/system/
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/system/contacts.db
./upper/home/ubuntu-gnome/.local/share/evolution/addressbook/system/photos/
./upper/home/ubuntu-gnome/.local/share/evolution/mail/
./upper/home/ubuntu-gnome/.local/share/evolution/mail/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/trash/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/system/
./upper/home/ubuntu-gnome/.local/share/evolution/memos/system/journal.ics
./upper/home/ubuntu-gnome/.local/share/gsettings-data-convert
./upper/home/ubuntu-gnome/.local/share/folks/
./upper/home/ubuntu-gnome/.local/share/folks/relationships.ini
./upper/home/ubuntu-gnome/.local/share/icc/
./upper/home/ubuntu-gnome/.local/share/icc/edid-958165f37ed2ae28b87c75c9c3b6f1e5.icc
./upper/home/ubuntu-gnome/.local/share/gnome-shell/
./upper/home/ubuntu-gnome/.local/share/telepathy/
./upper/home/ubuntu-gnome/.local/share/telepathy/mission-control/
./upper/home/ubuntu-gnome/.local/share/telepathy/mission-control/accounts-goa.cfg
./upper/home/ubuntu-gnome/.local/share/telepathy/mission-control/accounts.cfg
./upper/home/ubuntu-gnome/.local/share/zeitgeist/
./upper/home/ubuntu-gnome/.local/share/zeitgeist/activity.sqlite
./upper/home/ubuntu-gnome/.local/share/zeitgeist/activity.sqlite-shm
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/position.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/termlist.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/iamchert
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/record.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/postlist.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/position.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/termlist.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/postlist.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/position.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/record.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/termlist.baseA
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/postlist.baseB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/flintlock
./upper/home/ubuntu-gnome/.local/share/zeitgeist/fts.index/record.DB
./upper/home/ubuntu-gnome/.local/share/zeitgeist/activity.sqlite-wal
./upper/home/ubuntu-gnome/.local/share/sounds/
./upper/home/ubuntu-gnome/.local/share/gnome-settings-daemon/
./upper/home/ubuntu-gnome/.local/share/gnome-settings-daemon/input-sources-converted
./upper/home/ubuntu-gnome/.local/share/applications/
./upper/home/ubuntu-gnome/.local/share/.converted-launchers
./upper/home/ubuntu-gnome/.local/share/keyrings/
./upper/home/ubuntu-gnome/.local/share/tracker/
./upper/home/ubuntu-gnome/.local/share/tracker/data/
./upper/home/ubuntu-gnome/.local/share/tracker/data/tracker-store.ontology.journal
./upper/home/ubuntu-gnome/.local/share/tracker/data/tracker-store.journal
./upper/home/ubuntu-gnome/.local/share/gvfs-metadata/
./upper/home/ubuntu-gnome/.local/share/gvfs-metadata/home
./upper/home/ubuntu-gnome/.local/share/gvfs-metadata/home-99cc27f4.log
./upper/home/ubuntu-gnome/.local/share/session_migration-gnome
./upper/home/ubuntu-gnome/.bashrc
./upper/home/ubuntu-gnome/Videos/
./upper/home/ubuntu-gnome/.profile
./upper/home/ubuntu-gnome/Music/
./upper/home/ubuntu-gnome/Documents/
./upper/home/ubuntu-gnome/.bash_logout
./upper/home/ubuntu-gnome/Desktop/
./upper/home/ubuntu-gnome/Desktop/ubiquity.desktop
./upper/home/ubuntu-gnome/Templates/
./upper/home/ubuntu-gnome/.cache/
./upper/home/ubuntu-gnome/.cache/evolution/
./upper/home/ubuntu-gnome/.cache/evolution/tasks/
./upper/home/ubuntu-gnome/.cache/evolution/tasks/trash/
./upper/home/ubuntu-gnome/.cache/evolution/calendar/
./upper/home/ubuntu-gnome/.cache/evolution/calendar/trash/
./upper/home/ubuntu-gnome/.cache/evolution/addressbook/
./upper/home/ubuntu-gnome/.cache/evolution/addressbook/trash/
./upper/home/ubuntu-gnome/.cache/evolution/sources/
./upper/home/ubuntu-gnome/.cache/evolution/sources/trash/
./upper/home/ubuntu-gnome/.cache/evolution/mail/
./upper/home/ubuntu-gnome/.cache/evolution/mail/trash/
./upper/home/ubuntu-gnome/.cache/evolution/memos/
./upper/home/ubuntu-gnome/.cache/evolution/memos/trash/
./upper/home/ubuntu-gnome/.cache/folks/
./upper/home/ubuntu-gnome/.cache/folks/avatars/
./upper/home/ubuntu-gnome/.cache/upstart/
./upper/home/ubuntu-gnome/.cache/upstart/gnome-keyring-gpg.log
./upper/home/ubuntu-gnome/.cache/upstart/gnome-settings-daemon.log
./upper/home/ubuntu-gnome/.cache/upstart/dbus.log
./upper/home/ubuntu-gnome/.cache/upstart/gnome-session-GNOME.log
./upper/home/ubuntu-gnome/.cache/upstart/at-spi2-registryd.log
./upper/home/ubuntu-gnome/.cache/upstart/gnome-keyring-ssh.log
./upper/home/ubuntu-gnome/.cache/upstart/dbus-session
./upper/home/ubuntu-gnome/.cache/upstart/update-notifier-release.log
./upper/home/ubuntu-gnome/.cache/upstart/im-config.log
./upper/home/ubuntu-gnome/.cache/upstart/ssh-agent.log
./upper/home/ubuntu-gnome/.cache/event-sound-cache.tdb.ce1ba8862842a0a1529b230b567019ec.x86_64-pc-linux-gnu
./upper/home/ubuntu-gnome/.cache/fontconfig/
./upper/home/ubuntu-gnome/.cache/fontconfig/cabbd14511b9e8a55e92af97fb3a0461-le64.cache-4
./upper/home/ubuntu-gnome/.cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-le64.cache-4
./upper/home/ubuntu-gnome/.cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-4
./upper/home/ubuntu-gnome/.cache/fontconfig/CACHEDIR.TAG
./upper/home/ubuntu-gnome/.cache/motd.legal-displayed
./upper/home/ubuntu-gnome/.cache/logrotate/
./upper/home/ubuntu-gnome/.cache/logrotate/status
./upper/home/ubuntu-gnome/.cache/tracker/
./upper/home/ubuntu-gnome/.cache/tracker/meta.db
./upper/home/ubuntu-gnome/.cache/tracker/no-need-mtime-check.txt
./upper/home/ubuntu-gnome/.cache/tracker/db-version.txt
./upper/home/ubuntu-gnome/.cache/tracker/miner-applications-locale.txt
./upper/home/ubuntu-gnome/.cache/tracker/first-index.txt
./upper/home/ubuntu-gnome/.cache/tracker/last-crawl.txt
./upper/home/ubuntu-gnome/.cache/tracker/meta.db-wal
./upper/home/ubuntu-gnome/.cache/tracker/meta.db-shm
./upper/home/ubuntu-gnome/.cache/tracker/ontologies.gvdb
./upper/home/ubuntu-gnome/.cache/tracker/db-locale.txt
./upper/home/ubuntu-gnome/.cache/gdm/
./upper/home/ubuntu-gnome/.cache/gdm/session.log
./upper/home/ubuntu-gnome/.cache/ibus/
./upper/home/ubuntu-gnome/.cache/ibus/bus/
./upper/home/ubuntu-gnome/.cache/ibus/bus/registry
./upper/home/ubuntu-gnome/.cache/gstreamer-1.0/
./upper/home/ubuntu-gnome/.cache/gstreamer-1.0/registry.x86_64.bin
./upper/home/ubuntu-gnome/.config/
./upper/home/ubuntu-gnome/.config/evolution/
./upper/home/ubuntu-gnome/.config/evolution/sources/
./upper/home/ubuntu-gnome/.config/update-notifier/
./upper/home/ubuntu-gnome/.config/user-dirs.locale
./upper/home/ubuntu-gnome/.config/gtk-3.0/
./upper/home/ubuntu-gnome/.config/gtk-3.0/bookmarks
./upper/home/ubuntu-gnome/.config/upstart/
./upper/home/ubuntu-gnome/.config/dconf/
./upper/home/ubuntu-gnome/.config/dconf/user
./upper/home/ubuntu-gnome/.config/libaccounts-glib/
./upper/home/ubuntu-gnome/.config/libaccounts-glib/accounts.db
./upper/home/ubuntu-gnome/.config/gnome-session/
./upper/home/ubuntu-gnome/.config/gnome-session/saved-session/
./upper/home/ubuntu-gnome/.config/nautilus/
./upper/home/ubuntu-gnome/.config/tracker/
./upper/home/ubuntu-gnome/.config/pulse/
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-default-sink
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-stream-volumes.tdb
./upper/home/ubuntu-gnome/.config/pulse/cookie
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-device-volumes.tdb
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-card-database.tdb
./upper/home/ubuntu-gnome/.config/pulse/ce1ba8862842a0a1529b230b567019ec-default-source
./upper/home/ubuntu-gnome/.config/goa-1.0/
./upper/home/ubuntu-gnome/.config/ibus/
./upper/home/ubuntu-gnome/.config/ibus/bus/
./upper/home/ubuntu-gnome/.config/ibus/bus/ce1ba8862842a0a1529b230b567019ec-unix-0
./upper/home/ubuntu-gnome/.config/user-dirs.dirs
./upper/home/ubuntu-gnome/.ssh/
./upper/cdrom/
./upper/etc/
./upper/etc/shadow
./upper/etc/pam.d/
./upper/etc/pam.d/login
./upper/etc/login.defs
./upper/etc/udev/
./upper/etc/udev/rules.d/
./upper/etc/udev/rules.d/70-persistent-net.rules
./upper/etc/group
./upper/etc/mtab
./upper/etc/shadow-
./upper/etc/gshadow
./upper/etc/mtab.fuselock
./upper/etc/ssl/
./upper/etc/ssl/private/
./upper/etc/ssl/private/ssl-cert-snakeoil.key
./upper/etc/ssl/certs/
./upper/etc/ssl/certs/8af41246
./upper/etc/ssl/certs/ssl-cert-snakeoil.pem
./upper/etc/hosts
./upper/etc/init/
./upper/etc/init/ureadahead-other.conf
./upper/etc/init/tty4.conf
./upper/etc/init/tty1.conf
./upper/etc/init/ureadahead.conf
./upper/etc/init/tty6.conf
./upper/etc/init/tty5.conf
./upper/etc/init/hwclock-save.conf
./upper/etc/init/tty2.conf
./upper/etc/init/tty3.conf
./upper/etc/passwd
./upper/etc/sudoers.d/
./upper/etc/sudoers.d/casper
./upper/etc/default/
./upper/etc/default/locale
./upper/etc/nologin
./upper/etc/xdg/
./upper/etc/xdg/autostart/
./upper/etc/xdg/autostart/screen-reader-profile.desktop
./upper/etc/.pwd.lock
./upper/etc/locale.gen
./upper/etc/network/
./upper/etc/network/interfaces
./upper/etc/group-
./upper/etc/cups/
./upper/etc/cups/ssl/
./upper/etc/cups/ppd/
./upper/etc/gshadow-
./upper/etc/gdm/
./upper/etc/gdm/custom.conf
./upper/etc/apt/
./upper/etc/apt/sources.list~
./upper/etc/apt/sources.list
./upper/etc/apt/apt.conf.d/
./upper/etc/apt/apt.conf.d/00aptitude
./upper/etc/passwd-
./upper/etc/fstab
./upper/etc/hostname
./upper/etc/casper.conf
./upper/media/
./upper/media/ubuntu-gnome/
./upper/media/ubuntu-gnome/usbdata/
./upper/media/ubuntu-gnome/casper-rw/
./upper/media/cdrom
./upper/tmp/
./upper/tmp/debconf.THX2rP/
./upper/tmp/debconf.THX2rP/config.dat
./upper/tmp/debconf.THX2rP/passwords.dat
./upper/tmp/debconf.THX2rP/config.dat-old
./upper/tmp/debconf.THX2rP/debconf.conf
./upper/var/
./upper/var/log/
./upper/var/log/wtmp
./upper/var/log/udev
./upper/var/log/upstart/
./upper/var/log/upstart/thermald.log
./upper/var/log/upstart/procps-virtual-filesystems.log
./upper/var/log/upstart/container-detect.log
./upper/var/log/upstart/cryptdisks.log
./upper/var/log/upstart/systemd-logind.log
./upper/var/log/upstart/cups.log
./upper/var/log/upstart/procps-static-network-up.log
./upper/var/log/upstart/alsa-state.log
./upper/var/log/upstart/alsa-restore.log
./upper/var/log/upstart/whoopsie.log
./upper/var/log/upstart/network-manager.log
./upper/var/log/upstart/modemmanager.log
./upper/var/log/upstart/console-setup.log
./upper/var/log/Xorg.0.log
./upper/var/log/kern.log
./upper/var/log/faillog
./upper/var/log/dmesg
./upper/var/log/auth.log
./upper/var/log/cups/
./upper/var/log/cups/access_log
./upper/var/log/cups/error_log
./upper/var/log/cups/page_log
./upper/var/log/syslog
./upper/var/log/gdm/
./upper/var/log/gdm/:0-slave.log
./upper/var/log/gdm/:0.log
./upper/var/log/casper.log
./upper/var/log/dmesg.0
./upper/var/log/boot.log
./upper/var/log/lastlog
./upper/var/log/unattended-upgrades/
./upper/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
./upper/var/lib/
./upper/var/lib/NetworkManager/
./upper/var/lib/NetworkManager/timestamps
./upper/var/lib/NetworkManager/dhclient-d6967d6c-12d4-40bf-a159-9601bd5ea2fe-eth0.lease
./upper/var/lib/NetworkManager/NetworkManager.state
./upper/var/lib/update-notifier/
./upper/var/lib/update-notifier/fsck-at-reboot
./upper/var/lib/update-notifier/updates-available
./upper/var/lib/colord/
./upper/var/lib/colord/storage.db
./upper/var/lib/colord/mapping.db
./upper/var/lib/plymouth/
./upper/var/lib/plymouth/boot-duration
./upper/var/lib/xkb/
./upper/var/lib/xkb/server-34CEB476A3CB596DA76FD7010A029F76732EF824.xkm
./upper/var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
./upper/var/lib/udisks2/
./upper/var/lib/udisks2/mounted-fs
./upper/var/lib/rfkill/
./upper/var/lib/rfkill/saved-state
./upper/var/lib/urandom/
./upper/var/lib/urandom/random-seed
./upper/var/lib/belocs/
./upper/var/lib/belocs/locales.dep
./upper/var/lib/belocs/hashfile.old
./upper/var/lib/belocs/hashfile
./upper/var/lib/belocs/list
./upper/var/lib/belocs/hashfile.new
./upper/var/lib/dpkg/
./upper/var/lib/dpkg/lock
./upper/var/lib/dpkg/diversions-old
./upper/var/lib/dpkg/diversions
./upper/var/lib/locales/
./upper/var/lib/locales/supported.d/
./upper/var/lib/locales/supported.d/local
./upper/var/lib/AccountsService/
./upper/var/lib/AccountsService/users/
./upper/var/lib/AccountsService/users/ubuntu-gnome
./upper/var/lib/dbus/
./upper/var/lib/dbus/machine-id
./upper/var/lib/alsa/
./upper/var/lib/alsa/asound.state.lock
./upper/var/lib/alsa/asound.state
./upper/var/lib/apt/
./upper/var/lib/apt/cdroms.list
./upper/var/lib/apt/lists/
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_universe_binary-amd64_Packages
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_restricted_binary-amd64_Packages
./upper/var/lib/apt/lists/lock
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_main_binary-amd64_Packages
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_multiverse_binary-amd64_Packages
./upper/var/lib/apt/lists/partial/
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_Release
./upper/var/lib/apt/lists/Ubuntu-GNOME%2014.04.3%20LTS%20%5fTrusty%20Tahr%5f%20-%20Beta%20amd64%20(20150805)_dists_trusty_Release.gpg
./upper/var/lib/polkit-1/
./upper/var/lib/polkit-1/localauthority/
./upper/var/lib/polkit-1/localauthority/10-vendor.d/
./upper/var/lib/polkit-1/localauthority/10-vendor.d/10-live-cd.pkla
./upper/var/lib/polkit-1/localauthority/50-local.d/
./upper/var/lib/polkit-1/localauthority/50-local.d/disable-hibernate.pkla
./upper/var/lib/ubuntu-release-upgrader/
./upper/var/lib/ubuntu-release-upgrader/release-upgrade-available
./upper/var/tmp/
./upper/var/spool/
./upper/var/spool/cups/
./upper/var/spool/cups/tmp/
./upper/var/cache/
./upper/var/cache/debconf/
./upper/var/cache/debconf/templates.dat
./upper/var/cache/debconf/config.dat
./upper/var/cache/debconf/passwords.dat
./upper/var/cache/debconf/config.dat-old
./upper/var/cache/fontconfig/
./upper/var/cache/fontconfig/cabbd14511b9e8a55e92af97fb3a0461-le64.cache-4
./upper/var/cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-le64.cache-4
./upper/var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-4
./upper/var/cache/cups/
./upper/var/cache/cups/rss/
./upper/var/cache/cups/job.cache
./upper/var/cache/apt/
./upper/var/cache/apt/archives/
./upper/var/cache/apt/archives/lock
./upper/var/cache/apt/pkgcache.bin
./upper/var/cache/apt/srcpkgcache.bin
./upper/boot/
./upper/boot/grub/
./upper/boot/grub/grubenv
./upper/rofs/
./upper/usr/
./upper/usr/lib/
./upper/usr/lib/python3/
./upper/usr/lib/python3/dist-packages/
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/__pycache__/
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/softwarecenter_aptd_plugins/__pycache__/add_license_key_plugin.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/defer/
./upper/usr/lib/python3/dist-packages/defer/__pycache__/
./upper/usr/lib/python3/dist-packages/defer/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/defer/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/defer/__pycache__/version.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/config.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/logger.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/networking.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/lock.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/pkcompat.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/enums.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/policykit1.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/errors.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/progress.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/core.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/loop.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptdaemon/__pycache__/worker.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/MetaRelease.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/Core/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/UpdateManager/__pycache__/
./upper/usr/lib/python3/dist-packages/UpdateManager/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/
./upper/usr/lib/python3/dist-packages/__pycache__/apport_python_hook.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/pkg_resources.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/lsb_release.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/__pycache__/language_support_pkgs.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/
./upper/usr/lib/python3/dist-packages/gi/repository/
./upper/usr/lib/python3/dist-packages/gi/repository/__pycache__/
./upper/usr/lib/python3/dist-packages/gi/repository/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/
./upper/usr/lib/python3/dist-packages/gi/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_option.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/module.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_constants.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/types.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_propertyhelper.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/importer.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/docstring.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/__pycache__/_signalhelper.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/GObject.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/GLib.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/gi/overrides/__pycache__/Gio.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_expat_introspect_parser.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/lowlevel.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/proxies.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/service.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/types.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/glib.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/bus.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_compat.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/connection.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_dbus.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/exceptions.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/_version.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/__pycache__/decorators.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/mainloop/
./upper/usr/lib/python3/dist-packages/dbus/mainloop/__pycache__/
./upper/usr/lib/python3/dist-packages/dbus/mainloop/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/dbus/mainloop/__pycache__/glib.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/sourceslist.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/distro.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/aptsources/__pycache__/distinfo.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/
./upper/usr/lib/python3/dist-packages/apt/__pycache__/
./upper/usr/lib/python3/dist-packages/apt/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/cdrom.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/debfile.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/cache.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/package.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/__pycache__/auth.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/progress/
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/text.cpython-34.pyc
./upper/usr/lib/python3/dist-packages/apt/progress/__pycache__/base.cpython-34.pyc
./upper/usr/lib/update-notifier/
./upper/usr/lib/update-notifier/apt-check
./upper/usr/lib/update-notifier/apt-check.distrib
./upper/usr/lib/locale/
./upper/usr/lib/locale/locale-archive
./upper/usr/lib/python3.4/
./upper/usr/lib/python3.4/xml/
./upper/usr/lib/python3.4/xml/parsers/
./upper/usr/lib/python3.4/xml/parsers/__pycache__/
./upper/usr/lib/python3.4/xml/parsers/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/xml/parsers/__pycache__/expat.cpython-34.pyc
./upper/usr/lib/python3.4/xml/etree/
./upper/usr/lib/python3.4/xml/etree/__pycache__/
./upper/usr/lib/python3.4/xml/etree/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/xml/etree/__pycache__/ElementPath.cpython-34.pyc
./upper/usr/lib/python3.4/xml/etree/__pycache__/ElementTree.cpython-34.pyc
./upper/usr/lib/python3.4/xml/__pycache__/
./upper/usr/lib/python3.4/xml/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/collections/
./upper/usr/lib/python3.4/collections/__pycache__/
./upper/usr/lib/python3.4/collections/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/collections/__pycache__/abc.cpython-34.pyc
./upper/usr/lib/python3.4/ctypes/
./upper/usr/lib/python3.4/ctypes/__pycache__/
./upper/usr/lib/python3.4/ctypes/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/ctypes/__pycache__/_endian.cpython-34.pyc
./upper/usr/lib/python3.4/ctypes/__pycache__/util.cpython-34.pyc
./upper/usr/lib/python3.4/plat-x86_64-linux-gnu/
./upper/usr/lib/python3.4/plat-x86_64-linux-gnu/__pycache__/
./upper/usr/lib/python3.4/plat-x86_64-linux-gnu/__pycache__/_sysconfigdata_m.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/
./upper/usr/lib/python3.4/__pycache__/_sysconfigdata.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/heapq.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/textwrap.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/pkgutil.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_weakrefset.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/lzma.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/string.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_collections_abc.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/symbol.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/linecache.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/locale.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/io.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/operator.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/hashlib.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sre_parse.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tempfile.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/threading.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/quopri.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/stat.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/shutil.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/inspect.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sitecustomize.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/platform.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/struct.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_bootlocale.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/types.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/reprlib.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sysconfig.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/uuid.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/gettext.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/pickle.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/functools.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/re.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/fnmatch.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/codecs.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/contextlib.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/posixpath.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/__future__.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tokenize.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/opcode.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/site.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/ast.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/keyword.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/shlex.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/base64.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/selectors.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/copyreg.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/socket.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/dis.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/queue.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/bisect.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/os.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/random.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/gzip.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/subprocess.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/warnings.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/bz2.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/traceback.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/configparser.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/weakref.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/netrc.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/imp.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/copy.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sre_constants.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/token.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/datetime.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/enum.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/genericpath.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tty.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/calendar.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_sitebuiltins.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/abc.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/ssl.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/optparse.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/_compat_pickle.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/tarfile.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/uu.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/glob.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/zipfile.cpython-34.pyc
./upper/usr/lib/python3.4/__pycache__/sre_compile.cpython-34.pyc
./upper/usr/lib/python3.4/http/
./upper/usr/lib/python3.4/http/__pycache__/
./upper/usr/lib/python3.4/http/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/http/__pycache__/client.cpython-34.pyc
./upper/usr/lib/python3.4/email/
./upper/usr/lib/python3.4/email/__pycache__/
./upper/usr/lib/python3.4/email/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/utils.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/header.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/_policybase.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/parser.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/_encoded_words.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/iterators.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/base64mime.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/errors.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/quoprimime.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/_parseaddr.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/charset.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/feedparser.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/message.cpython-34.pyc
./upper/usr/lib/python3.4/email/__pycache__/encoders.cpython-34.pyc
./upper/usr/lib/python3.4/importlib/
./upper/usr/lib/python3.4/importlib/__pycache__/
./upper/usr/lib/python3.4/importlib/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/importlib/__pycache__/util.cpython-34.pyc
./upper/usr/lib/python3.4/importlib/__pycache__/machinery.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/
./upper/usr/lib/python3.4/encodings/__pycache__/
./upper/usr/lib/python3.4/encodings/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/aliases.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/latin_1.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/ascii.cpython-34.pyc
./upper/usr/lib/python3.4/encodings/__pycache__/utf_8.cpython-34.pyc
./upper/usr/lib/python3.4/logging/
./upper/usr/lib/python3.4/logging/__pycache__/
./upper/usr/lib/python3.4/logging/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/logging/__pycache__/handlers.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/
./upper/usr/lib/python3.4/urllib/__pycache__/
./upper/usr/lib/python3.4/urllib/__pycache__/__init__.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/request.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/response.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/parse.cpython-34.pyc
./upper/usr/lib/python3.4/urllib/__pycache__/error.cpython-34.pyc
./upper/usr/lib/ubuntu-release-upgrader/
./upper/usr/lib/ubuntu-release-upgrader/check-new-release-gtk
./upper/usr/lib/ubuntu-release-upgrader/check-new-release
./upper/usr/lib/ubuntu-release-upgrader/check-new-release.distrib
./upper/usr/lib/ubuntu-release-upgrader/check-new-release-gtk.distrib
./upper/usr/sbin/
./upper/usr/sbin/update-initramfs.distrib
./upper/usr/sbin/anacron.distrib
./upper/usr/sbin/anacron
./upper/usr/sbin/update-initramfs
./upper/usr/share/
./upper/usr/share/gnome-shell/
./upper/usr/share/gnome-shell/js/
./upper/usr/share/gnome-shell/js/gdm/
./upper/usr/share/gnome-shell/js/gdm/loginDialog.js
./upper/usr/share/glib-2.0/
./upper/usr/share/glib-2.0/schemas/
./upper/usr/share/glib-2.0/schemas/casper.gschema.override
./upper/usr/share/glib-2.0/schemas/gschemas.compiled
./upper/usr/share/applications/
./upper/usr/share/applications/ubiquity.desktop
./lost+found/
./work/
./work/work/
./format
Restore from '/media/sam/usbdata/1-casper-rw.tar.gz' successful
chown: cannot access ‘/mnt/upper/media/sam’: No such file or directory
sam@sam-G-L650:/media/sam/usbdata$ 
#325

Looking at the prompt

sam@sam-G-L650:~$

indicates that you are doing this backup and restore from your installed system, not running a live-only system. I did not intend to run them from the installed system, so they might or might not work.

So my question is: What happens, when you reboot into the restored system? Does it work as it should?

If it works as it should, maybe it is only a minor bug, but at least, there should be some statement about the error output.

If not, you have found a big bug. Something must be changed - both the instructions and some check-point in the scripts for backup and restore, to avoid running them from an installed system, or even better, to make them work also when running from an installed system.

#326

Ok I tried it live and everything was fine, no data was lost, no errors.

Had to find which device had the live version on it, that was why it was ran from the installed system. :)

#327

Thanks for all the testing mkusb sammiev,

Now we know that the backup and restore scripts work also from the installed system :-) I'll try to figure out a way to inform the users of the error output in case they run the backup and restore from another drive, for example an installed system like you did.

#328

+1 :)

#329

[SIZE=4]mkusb version 10.4.5[/SIZE]

This is a bug-fix version

  1. minor bug-fix: cleaning when quitting from get_percent
  1. shell-script 'restore' skips chown when running from other system (not the persistent drive's 'own' live-only boot option)

[hr][/hr] You get/update this new version 10.4.5 from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

These fixes are minor, and should need no extra testing :-)

If no bug is found within the next few days, I intend to upload this version to the stable ppa too, ppa:mkusb/ppa

[hr][/hr] *Edit:*

mkusb version 10.4.5 is copied to the stable PPA now. You can get this version of mkusb and the corresponding mkusb-nox via the following commands

sudo add-apt-repository ppa:mkusb/ppa  # and press Enter
sudo apt-get update
sudo apt-get install mkusb mkusb-nox
#330

Strangely, running "whipe the Whole device" i.e.

< /dev/zero pv -n -s 8011120640 | dd bs=4096 of=/dev/sdc

[COLOR=#000000][FONT=sans-serif]in my case [/FONT][/COLOR]with mkusb 10.4.1 made my computer very slow until it was finished; even top command could not show its interface in terminal.

#331

I think it depends on the computer hardware. In some cases this writing operation will keep the computer busy.

Was the wiping finished correctly, so that the whole device was wiped?

-o-

By the way, I would recommend that you upgrade to the current version, mkusb 10.4.5. I don't think it will make a difference for wiping the whole device, but some other tasks will work better.

#332

Yes, I think so. Thanks for the advice.

#333

I ran persistent session and changed some settings in[FONT=arial] [COLOR=#111111]/etc/defaults/grub like http://askubuntu.com/a/395431/21005 to disable graphics acceleration. But when I ran ``` sudo update-grub

#334

Hi Jarno,

  1. You can add a boot option temporarily during booting at the grub menu by pressing the 'e' key and navigate to the 'linux line' and add the boot option to make it look like the [COLOR="#0000CD"]blue line[/COLOR] below.

-o-

  1. You can make a boot option persistent like this: A persistent live session does not boot like an installed system. Its grub.cfg cannot be managed via 'sudo update-grub'. Instead you should edit it directly. Add the boot option(s) at the end of the lines that starts with 'linux', alongside 'persistent', in your case 'nouveau.noaccel=1'.

Identify the partition with grub.cfg:

sudo lsblk -fm

Assume the live drive is /dev/sdx (typically /dev/sdb or /dev/sdc) and the label of partition 3 can be for example 'lubtrusty32' or 'xubxenial64'. Mount the partition and use the editor *nano*

sudo mount /dev/sdx3 /mnt
sudo nano /mnt/boot/grub/grub.cfg

Change

linux ($root) ... quiet splash persistent -- persistent

to

[COLOR="#0000CD"]linux ($root) ... quiet splash persistent nouveau.noaccel=1 -- persistent nouveau.noaccel=1[/COLOR]

-o-

  1. Persistent live systems can install program packages and upgrade program packages with an important exception: The kernel from the iso file will be used and it cannot be upgraded. If you want a newer kernel, you must start from a new iso file. This is a general limitation of persistent live systems, it affects systems made by mkusb and also persistent live systems made with other tools. *If you want a system that is completely 'upgradable', you should use an installed system, which is also possible in a USB pendrive*. See this link

Try Ubuntu (Kubuntu, Lubuntu, Xubuntu, ...) before installing it

#335

I pressed 'e' key and changed the line to contain the two "nouveau.noaccel=1" items, continued by Ctrl-x, but then Mythbuntu asks me username and password: I put mythbuntu as username and empty string as password (which is accepted as login info), but it always comes back to the login screen. This does not happen, if I do not change the linux parameters.

#336

I have not tried with Mythbuntu, but I have tried persistent live systems with Lubuntu 14.04.2 and Xenial Xerus (daily build) and they work with the boot option, that you tried.

I don't know why your computer goes back to the login screen. Maybe that boot option is no good for your computer. Maybe there was a typing error. Have you tried another boot option? Or maybe it works best without any extra boot option, only what comes with the persistent live system.

Why did you try to disable graphics acceleration with "nouveau.noaccel=1" according to the link in post #331?

#337

I didn't first notice the first [COLOR=#0000CD][FONT=Ubuntu Mono]nouveau.noaccel=1[/FONT][/COLOR] and only used the latter one. Why do you need to add it twice? Then I could start the session without manual login. However, it started to require manual login at some boot time and first I could login successfully, but now it does not work even with the same options. Only without adding such boot options, it succeeds to boot without manual login. If I choose non-persistent session, I can add [COLOR=#0000CD][FONT=Ubuntu Mono]nouveau.noaccel=1 [/FONT][/COLOR]before -- and boot, but should I add it also after --?

Because the operation with e.g. Youtube was slower than what I expected, say 1 frame per second in 144p resolution, and pretty much freezed computer, I wanted to test, if it would work better without the acceleration option.

#338

The boot options before -- are active in the live session. The boot options after -- are ported to the installed system (if you install a system from your live session).

Maybe something else that you have installed or tweaked has made your system sensitive to the boot options. I think you will not get the best help to solve your problem in this thread.

To get more and better help with Mythbuntu and playing video, I suggest that you *start an own thread* in the Mythbuntu or multimedia subforum. Make a good title, that describes your problem, and describe your computer and your system with many details. It makes it easier for the people who try to help to find your thread and to give relevant help :-)

My experience is that Lubuntu is the best Ubuntu flavour for playing video in old computers, because it has the lightest desktop environment. And it is very important to also consider your hardware, particularly the graphics card and the CPU.

#339

[SIZE=4]mkusb version 10.4.6[/SIZE]

This is a minor bug-fix version. The window to enter password in mkusb is updated like this:

After a bad password the title bar is changed

'mkusb - password' --> 'password: try again!'

[hr][/hr] You get/update this new version 10.4.6 from the unstable PPA via the following commands

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

This fix is minor, and should need no extra testing :-)

#340

+1 for all your hard work! :)

#341

[SIZE=4]mkusb version 10.5[/SIZE]

Finally mkusb can create a persistent live drive from a Debian Jessie iso file! The first method developed from 'grub-n-iso' works in this version of mkusb. The second method, 'Using data from the source iso file', works only with 64-bit iso files based on Ubuntu.

The third method, 'Compressed image file with a persistent live system', provides a work-around for computers in UEFI mode to use the first 'method developed from grub-n-iso' in the next step. A new compressed iso file of the third method contains mkusb 10.5 from the unstable PPA, 'bleeding edge'.

dd_lubu-14.04.3-desktop-i386_one-pendrive_mkusb10.5-bleeding-edge_7.8GB.img.xz

The following files are tested and work

[B]debian-live-8.0.0-i386-gnome-desktop.iso debian-live-8.2.0-amd64-gnome-desktop.iso[/B]

Three tweaks are built into mkusb (only for Debian) according to the following link. Thanks *hhh at #!* :-)

[ [SOLVED] Debian jessie persistent live USB](http://crunchbang.org/forums/viewtopic.php?pid=438311)

  1. An ext4 partition with the label persistence (not live-rw)

/dev/sdx5

  1. The boot option persistence (at the end of the linux line)
  1. A configuration file in the ext4 partition:
echo / union | tee persistence.conf

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

This fix needs some extra testing :-)

#342

mkusb version 10.5 can create a persistent live drive from a Debian Jessie iso file as described in the previous post.

The method Compressed image file with a persistent live system provides a work-around for computers in UEFI mode to use the 'method developed from grub-n-iso' in the next step. The following new compressed iso file contains mkusb 10.5

dd_lubu-14.04.3-desktop-i386_one-pendrive_mkusb10.5-bleeding-edge_7.8GB.img.xz

mkusb used the iso file debian-live-8.2.0-amd64-gnome-desktop.iso to create the persistent live system illustrated by the attached screenshot.

#343

[SIZE=4]mkusb version 10.5.1[/SIZE]

A new version of ToriOS is developed (in beta phase). It is built on Debian Jessie. *mkusb* is modified to make persistent live drives also from this version of ToriOS.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

This fix needs some extra testing to check that Debian Jessie itself and the original version of ToriOS (built on Ubuntu Precise) are still working:-)

[hr][/hr] *Edit: * mkusb version 10.5.1 is uploaded to the stable PPA now, ppa:mkusb/ppa

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#344

[SIZE=4]Compressed cloned image of an Ubuntu system with encrypted disk in UEFI mode[/SIZE]

*Warning:* the *dd* command is very powerful but also very dangerous. It is nick-named 'disk destroyer' because it does what you tell it to do without questions, even if you tell it to overwrite a disk that contains for example the family pictures.

Making a compressed cloned image with *dd|gzip*


sudo -s
dd if=/dev/sdx bs=4096 | gzip > dd-file.img.gz
sync
exit  # from superuser privileges

should work with any kind of partition table (except if there are bad sectors on the drive).

Recovering with *zcat|dd*


sudo -s
< dd-file.img.gz zcat | dd of=/dev/sdy bs=4096
sync
exit  # from superuser privileges

or *safer with mkusb*

sudo -H mkusb dd-file.img.gz

should work directly if an MSDOS partition table, and should work after fixing with *gdisk* if a GUID partition table, GPT. (There are repair commands in gdisk's 'recovery & transformation' menu and 'experts' menu.) Ubuntu is installed with GPT in UEFI mode.

Remember that you must recover to a drive with exactly the same size or larger, and the blocking (sector size) should be the same. Otherwise you should make a fresh installation and transfer your personal files separately.

-o-

The first command sequence 'writes only to a file', which should not be too risky. But you must check that you specify the input file [SIZE=3]if=/dev/sdx[/SIZE] (not the output file of=/dev/sdx, and the keys for [SIZE=3]i[/SIZE] and [SIZE=3]o[/SIZE] are neighbours on many keyboards).

*It is very important to double-check that the drive letter y is correct for the target drive*, otherwise you might destroy the family pictures. So instead of the second command sequence, you can use mkusb to wrap a safely belt around dd. It helps you to select the correct target drive.

Expanding a very big file with *gzip* will confuse the progress view, but the expansion itself works well. (The compression is more efficient and the progress view will work correctly with *xz*, but the compression is *very slow*. This is why I use gzip in this post.)

An alternative is to use no compression at all, to create a plain dd image file dd-file.img

sudo dd if=/dev/sdx bs=4096 of=dd-file.img
sync
sudo -H mkusb dd-file.img

[hr][/hr] *Testing that it works in UEFI mode*

I grabbed a [COLOR="#cc0000"]60GB[/COLOR] SSD that had been used via USB 3, so it was not trimmed. I put it inside a laptop (as an internal SATA drive), installed a fresh Ubuntu Xenial system with encrypted disk and made a compressed image (with dd|gzip). There was almost no compression. Zeroising (wiping) 'inside' by overwriting all unused space was not efficient. Then I wiped the whole drive (using mkusb), and after that installed a fresh Ubuntu Xenial system with encrypted disk in UEFI mode. It was compressed rather well from 60GB to 6.3GiB (6.74GB) by dd|gzip,

$ ls -lh /media/usbdata/dd-file.img.gz 
-rw------- 1 sudodus sudodus 6,3G feb 22 05:19 /media/usbdata/dd-file.img.gz

I expanded this compressed Ubuntu Xenial system with mkusb into a [COLOR="#cc0000"]320GB[/COLOR] HDD and repaired with gdisk (to get a backup partition table at the tail end of the drive), and it works. I can login via the passphrase and password and run the system.

tester@tester-SATELLITE-PRO-C850-19W:~$ [COLOR="#0000FF"]sudo lsblk -fm[/COLOR]
[sudo] password for tester: 
NAME                    FSTYPE      LABEL UUID                                   MOUNTPOINT NAME                    SIZE OWNER GROUP MODE
sda                                                                                         sda                   298,1G root  disk  brw-rw----
&#9500;&#9472;sda1                  vfat              6567-A0CC                              /boot/efi  &#9500;&#9472;sda1                  512M root  disk  brw-rw----
&#9500;&#9472;sda2                  ext2              e243db09-f9bb-46f3-b403-217552ce5923   /boot      &#9500;&#9472;sda2                  244M root  disk  brw-rw----
&#9492;&#9472;sda3                  crypto_LUKS       cd0aab8d-d5fc-46d4-8dfc-fb6426da4e3e              &#9492;&#9472;sda3                 55,2G root  disk  brw-rw----
  &#9492;&#9472;sda3_crypt          LVM2_member       4N5N66-boVS-YeCH-bYrR-Sufm-0mxP-mo5K5t              &#9492;&#9472;sda3_crypt         55,2G root  disk  brw-rw----
    &#9500;&#9472;ubuntu--vg-root   ext4              92461b8b-1c26-45a8-9253-1612b2c47589   /              &#9500;&#9472;ubuntu--vg-root  51,3G root  disk  brw-rw----
    &#9492;&#9472;ubuntu--vg-swap_1 swap              39818eea-088c-4af1-af0d-98ea4244deb2   [SWAP]         &#9492;&#9472;ubuntu--vg-swap_1
                                                                                                                    3,9G root  disk  brw-rw----
sr0                                                                                         sr0                    1024M root  cdrom brw-rw----

tester@tester-SATELLITE-PRO-C850-19W:~$ [COLOR="#0000FF"]sudo parted -ls[/COLOR]
Model: ATA ST320LT007-9ZV14 (scsi)
Disk /dev/sda: [COLOR="#cc0000"]320GB[/COLOR]
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  538MB   537MB   fat32        EFI System Partition  boot, esp
 2      538MB   794MB   256MB   ext2
 3      794MB   [COLOR="#cc0000"]60.0GB[/COLOR]  59.2GB


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ubuntu--vg-root: 55.0GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  55.0GB  55.0GB  ext4


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ubuntu--vg-swap_1: 4169MB
Sector size (logical/physical): 512B/4096B320GB
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system     Flags
 1      0.00B  4169MB  4169MB  linux-swap(v1)


Error: /dev/mapper/sda3_crypt: unrecognised disk label
Model: Linux device-mapper (crypt) (dm)
Disk /dev/mapper/sda3_crypt: 59.2GB
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags: 

[hr][/hr] It is probably easier to make a fresh installation. I think it is a better idea to use some kind of *backup of your personal files* instead of cloning or making a compressed image of the whole system with encrypted disk, particularly with a system, that has been used for a while and does not compress well.

#345

Hi, I don't know where to ask this. In Ubuntu Development Version, here or where?

In the future (not now), I want to do some testing for Xubuntu-next. I am reading on the Xubuntu-devel mailing list and today saw the call for: Subject: Xenial Upgrade Testing week, (I understand on bare-metal testing would be preferred over done in vm but, not necessary).

Example: Would using mkusb install be suitable for QA Testing/Tracker. For running this: http://iso.qa.ubuntu.com/qatracker/milestones/351/builds/113407/testcases/1310/results

Does anyone use installs in usb by mkusb, mkusb-nox for testing of installs for anything besides testing the app itself?

Thank you.

#346

Hi mikodo,

I have been using *mkusb* for years (starting with a simple text only script) for iso-testing. I suggest that you make live-only USB boot drives, they boot like DVD disks. I think it will be a simple and straightforward method. Keep a directory with scripts for the i386 and amd64 iso files and zsync them

zsync http://cdimage.ubuntu.com/xubuntu/daily-live/current/xenial-desktop-i386.iso.zsync
zsync http://cdimage.ubuntu.com/xubuntu/daily-live/current/xenial-desktop-amd64.iso.zsync

If you use one pendrive for each version (i386/amd64), there will be automatic identification and very easy and safe selection of target drive. After a while you might prefer the command line version *mkusb-nox*

If you make persistent live drives, cruft may accumulate (saved in the casper-rw file), and things may work differently compared to a clean live-only system. The boot will also be different.

-o-

An alternative is to run a live-only grub-n-iso system, see post #6 and the following posts in this link. Most things will be like they were cloned with mkusb, but there will obviously be no syslinux boot.

-o-

*Edit:* Testing *Upgrade* is different. I have not done it, but reading the testcase quickly, I get the idea, that you must *start from an installed system*, not from a live drive.

#347

[QUOTE=mikodo;13447019 _Does anyone use installs in usb by mkusb, mkusb-nox for testing of installs for anything besides testing the app itself?_

Thank you. I do all the time, one of my main tools for this and creating persistent live drives..Great Tool for my needs:D

#348

Thank you, folks!

My interest in using mkusb (besides enjoying watching its' development here), is for testing.

You've answered my questions. I am going to share your responses in #xubuntu-devel where I had asked about using it for testing and for using in specifically for (Xenial Upgrade Testing week). There may be others on that channel who saw my questions and may be interested in your responses.

#349

Enjoy the *Xenial Upgrade Testing Week* :-)

#350

Got your msg about testing script and decided to use mkusb 10.5.1 so I do not get the difference. So my point being is that using the 'wipe' menu it did not affect the FAT 32 format.

Regards..

#351

..and..

#352

Yes, the options in mkusb's wipe menu work. But we need something for 'restoring to a data storage drive' in the Ubuntu Startup Disk Creator too, because that is the tool that comes with Ubuntu.

#353

[SIZE=4]mkusb version 10.6[/SIZE]

The new version 10.6 mkusb lets you select the partition table, GPT or MSDOS, for the target drive, when making a persistent live drive. Normally GPT is recommended, but many HP computers need an MSDOS partition table to boot directly from USB. This is selected in a new menu window. See the attached screenshot.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

[FONT=Courier New]+ [/FONT]This new version works well with the current versions and flavours of Ubuntu including Xenial Xerus to be released as 16.04 LTS. [FONT=Courier New]+ [/FONT]This new version works well with Debian Jessie. [FONT=Courier New]- [/FONT]Persistent live ToriOS is still unable to boot middle-aged HP computers, but a live-only ToriOS pendrive works. [FONT=Courier New]- [/FONT]There seems to be a [let us hope temporary] problem with mkusb's zenity windows when using the proprietary nvidia 304 driver in Xenial Xerus. [hr][/hr] [COLOR="#484848"]mkusb version 10.5.1 is still uploaded at the stable PPA, ppa:mkusb/ppa

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#354

[SIZE=4]mkusb version 10.6.1[/SIZE]

The new version 10.6.1 adds fixes for Xubuntu 16.04 LTS, where there were problems with mounting and unmounting partitions, when creating a persistent live drive. You may also want to stop cluttering the desktop in Xubuntu and maybe also other Ubuntu flavours and re-spins or other linux distros.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] [COLOR="#484848"]mkusb version 10.5.1 is still uploaded at the stable PPA, ppa:mkusb/ppa

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#355

[SIZE=4]mkusb version 10.6.2[/SIZE]

The new version 10.6.2 adds a fix for mkusb and mkusb-nox.

xz --robot --list

At some instance, the standard list format of *xz* was changed which broke the progress view. The option --robot provides robust calculation of uncompressed size, and will probably remain stable.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] [COLOR="#484848"]mkusb version 10.5.1 is still uploaded at the stable PPA, ppa:mkusb/ppa, but I hope to upgrade it soon.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#356

[SIZE=4]mkusb version 10.6.3 and mkusb-nox version 7.5.9.4[/SIZE]

There is a minor fix for mkusb and a new feature for mkusb-nox, restore

sudo mkusb-nox restore

creates a standard storage device with an MSDOS partition table and a partition with a FAT32 file system. This is a convenient method to convert a cloned USB boot drive back to a storage drive. The manual page is updated to help you find this new feature, as well as the help text. This is a simplified version of mkusb's wipe menu.

$ [COLOR="#0000FF"]mkusb-nox[/COLOR]
Usage:
---- Make a USB install device from ISO or image file ---------------
sudo mkusb-nox file.iso
sudo mkusb-nox "quote file name (1) with special characters.iso"
sudo mkusb-nox file.img
sudo mkusb-nox file.img.gz
sudo mkusb-nox file.img.xz
---- Install from 'file.img.xz', show all mass storage devices
sudo mkusb-nox file.img.xz all
---- Clone a device (typically a CD drive or USB drive) -------------
sudo mkusb-nox /dev/sr0    # example of CD drive
---- Wipe the USB device (may take long time) -----------------------
sudo mkusb-nox wipe-whole-device
---- Wipe the first megabyte (MibiByte), show only USB devices ------
sudo mkusb-nox wipe-1
---- Wipe the first megabyte, show all mass storage devices ---------
sudo mkusb-nox wipe-1 all
[B][COLOR="#0000FF"]---- Restore to a storage device with FAT32 file system -------------
sudo mkusb-nox restore[/COLOR][/B]
---- Help and Version -----------------------------------------------
./mkusb-nox -h
./mkusb-nox -v

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 10.6.3 is uploaded now at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#357

[SIZE=4]mkusb ready for Yakkety Yak[/SIZE]

If you are testing Ubuntu Yakkety or one of the flavours (Kubuntu, Lubuntu ... Xubuntu), you can

  1. Use mkusb from an earlier version to create a live or persistent live pendrive with Yakkety Yak
  1. Install mkusb in Yakkety Yak.

There is a PPA for Yakkety now. Everything is ready at Launchpad,

sudo add-apt-repository ppa:mkusb/ppa

works now :-)

[hr][/hr] You can also get mkusb via the *wget* method according to this link: mkusb/gui#from_phillw.net and get the unstable version (now 10.6.3). Not much has happened since the release of Xenial, so it is no surprise that mkusb works.

-o-

Download the shell-script file mkusb-installer with the browser or do it directly from a terminal window with

wget http://phillw.net/isos/linux-tools/mkusb/mkusb-installer

and run it from a terminal window with

bash mkusb-installer
...
[sudo] password:
...
Install via ppa or wget, uninstall or quit? (p/w/u/Q) w
...
  1. Enter your password (installed systems typically require password, but not live systems)
  1. Enter w (for wget) and the shell-script will download, check and install mkusb plus some small iso files for testing.
  1. Repeat the command *bash mkusb-installer* if some file was not downloaded correctly.
#358

[SIZE=3]ppa:mkusb/ppa and ppa:mkusb/unstable work in yakkety now :-)[/SIZE]

#359

Yes!! I finally got it built for Arch also. So far so good sudodus. Just keeps getting better. Kind Regards

#360

That's nice, runrickus :-)

#361

[SIZE=4]mkusb version 10.6.4 and mkusb-nox version 7.5.9.5[/SIZE]

There is a new feature and a minor bug-fix for mkusb and mkusb-nox.

  • The small shellscript *gpt-fix* is used to fix the GUID partition table after cloning because the target drive size is almost always different from that of the source (origin of the compressed image file). This is now a function, gpt_fix, in mkusb and mkusb-nox. This way to fix the GPT eliminates the risk to forget about it and also makes it more convenient.
  • Thanks *yman* for finding a bug with the path to the source file :-). It was fixed by adding double quotes around the variable for the source file. Now mkusb and mkusb-nox can use a path with spaces and some other special characters. It worked with the filename before - now it is extended to the directory part of the path.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 10.6.3 is still uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#362

[SIZE=4]mkusb version 10.6.6 and mkusb-nox version 7.5.9.7[/SIZE]

This is a bug-fix version for mkusb and mkusb-nox.

  • The function *gpt_zap* is used to zap (wipe) old GPT structures (partition table and backup partition table) before the cloning starts.Then *gpt_fix* should work correctly (without confusion), when it is run after the cloning.
  • The logic to invoke *gpt_fix* is improved. It turned out that parted parted is acting differently in Trusty and Xenial, when it sees errors. The new logic is not using parted, but takes advantage of the more predictable state due to gpt_zap. It is still experimental, and needs more testing before it will be uploaded to the stable PPA.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 10.6.3 is still uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#363

[SIZE=4]mkusb version 10.6.6 and mkusb-nox version 7.5.9.7 at the stable PPA[/SIZE]

After testing mkusb version 10.6.6 and mkusb-nox version 7.5.9.7 are uploaded at the stable PPA, ppa:mkusb/ppa.

sudo add-apt-repository universe  # this line is necessary for standard Ubuntu (but not for the flavours kubuntu, lubuntu ... xubuntu)

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#364

Hi sudodus et al,

I went through this whole section: https://help.ubuntu.com/community/mkusb/pictures

I must compliment you on how nice the newer message dialogues are being presented, with the newer coloring that has been done to display, (and the bits on how to change for user/vendor as wished), the nicer HTML look, the improved and expanded features, on and on. The presentation of mkusub on display in these pages showing the older versions to the newer displays, really shows how much it has been improved.

Addendum. I forgot to mention the explanations attached to each window is very helpful in explaining the features on display in the windows. Newer users can easily see what each function means by reading the explanation. Very thoughtful.

Very, very nice!

#365

I'm glad you like it, mikodo :-)

#366

[SIZE=4]Updated system to install [Ubuntu flavours of] Xenial 32-bit alias 16.04 LTS[/SIZE]

This is a compressed image file of an installed Ubuntu mini system with text user interface. It is a good start for installing various flavours of Ubuntu or your own custom system by selecting which program packages to install. It is made to be installed with *mkusb*, but can be installed with other cloning tools too, for example *mkusb-nox* in text mode or {*7-zip* & Win32 Disk Imager} in Windows. This 32-bit system in meant to run in BIOS mode.

This system has been made up to date June 28, 2016. Features of the corresponding 64-bit UEFI-and-BIOS systems have been added: htop, a menu to select text mode font size, and the 'tasksel' menu for all the options of the Ubuntu Server.

The 'intel' text in the file name indicates that the system contains the package 'xserver-xorg-video-intel', which makes the system work will some old Intel graphics chips.

dd_Xenial-32-txt_2016-06-28_intel_7.8GB.img.xz

with the following md5sum:

01cc17a80dfbf7f5e484a56164ebbc8d  dd_Xenial-32-txt_2016-06-28_intel_7.8GB.img.xz

[hr][/hr] user: guru password: changeme

[hr][/hr] There is a corresponding tarball to be installed with the One Button Installer

Xenial-32-txt_2016-06-28_intel.tar.xz

*Edit:* Two bugs were discovered. Workarounds 'fix' them in the system of a compressed image file and a tarball dated 2016-06-29.

#367

sudodus said: [SIZE=4]Updated system to install [Ubuntu flavours of] Xenial 32-bit alias 16.04 LTS[/SIZE]

This is a compressed image file of an installed Ubuntu mini system with text user interface. It is a good start for installing various flavours of Ubuntu or your own custom system by selecting which program packages to install. It is made to be installed with *mkusb*, but can be installed with other cloning tools too, for example *mkusb-nox* in text mode or {*7-zip* & Win32 Disk Imager} in Windows. This 32-bit system in meant to run in BIOS mode.

This system has been made up to date June 28, 2016. Features of the corresponding 64-bit UEFI-and-BIOS systems have been added: htop, a menu to select text mode font size, and the 'tasksel' menu for all the options of the Ubuntu Server.

The 'intel' text in the file name indicates that the system contains the package 'xserver-xorg-video-intel', which makes the system work will some old Intel graphics chips.

dd_Xenial-32-txt_2016-06-28_intel_7.8GB.img.xz

with the following md5sum:

01cc17a80dfbf7f5e484a56164ebbc8d  dd_Xenial-32-txt_2016-06-28_intel_7.8GB.img.xz

[HR][/HR] user: guru password: changeme

[HR][/HR] There is a corresponding tarball to be installed with the One Button Installer

Xenial-32-txt_2016-06-28_intel.tar.xz Thanks sudodus!I will test this out for the next couple of days.:) Any hints for the password:confused: Just Kidding:D Cheers

#368

Hi runrickus,

Try either the compressed image file or the tarball (or both if you have time enough). It is more straight-forward to install from the compressed image file. The tarball is more flexible. You can make a single, dual or multi-boot system, and it will work with an MSDOS as well as a GUID partition table (at the advanced OBI level).

#369

sudodus said: Hi runrickus,

Try either the compressed image file or the tarball (or both if you have time enough). It is more straight-forward to install from the compressed image file. The tarball is more flexible. You can make a single, dual or multi-boot system, and it will work with an MSDOS as well as a GUID partition table (at the advanced OBI level).

Yep! I will do both and with various options and packages. Regards

#370

I have tested the system in dd_Xenial-32-txt_2016-06-28_intel_7.8GB.img.xz in some different computers.

*It works well in my 64-bit computers (from 2008 - 2016). *

*It works but with some problems in my 32-bit computers*:

an IBM Thinkpad T42 with Pentium M processor and a Dell Dimension 4600 with a Pentium 4 processor.

- The font is selected and unselected during boot, + but can be selected again via the text-mode-menus.

- The simple graphical user interface via Fluxbox and xinit cannot be started (via startx). + The more advanced graphical user interface 'Lubuntu Core' works as expected, and if Fluxbox is installed, it can be selected at the log in screen.

#371

sudodus said: I have tested the system in dd_Xenial-32-txt_2016-06-28_intel_7.8GB.img.xz in some different computers.

*It works well in my 64-bit computers (from 2008 - 2016). *

*It works but with some problems in my 32-bit computers*:

an IBM Thinkpad T42 with Pentium M processor and a Dell Dimension 4600 with a Pentium 4 processor.

- The font is selected and unselected during boot, + but can be selected again via the text-mode-menus.

- The simple graphical user interface via Fluxbox and xinit cannot be started (via startx). + The more advanced graphical user interface 'Lubuntu Core' works as expected, and if Fluxbox is installed, it can be selected at the log in screen. Here is my test bed

System: Acer product: Aspire M3300
           Mobo: Acer model: FRS780M
           Bios: American Megatrends v: P03-B0 date: 11/16/2009

Everything works as Advertised...Have not installed any video drivers due to I want to test it on an Acer lappy also. I have no bugs to report as yet...but still testing. I see you added this "Fluxbox and xinit cannot be started (via startx)." Nice job sudodus!

#372

After your test *runrickus*, I am confident to upload workarounds to 'fix' the bugs I discovered in the system. of a compressed image file and a tarball dated 2016-06-29.

+ The *font size* is set in the shellscript text-mode-menu.

+ The problem with *startx* is solved by providing a system with *Fluxbox et.al. already installed*. Then it can be started via startx also in 32-bit computers, and provide a very light system. It uses only 54 MB RAM when running idle. See the attached screenshot. This can be a good alternative if you want a server and want to use some graphical tool sometimes. (After using that tool, you can exit from Fluxbox and return to the text mode menus.) But above all, it is a good alternative for a computer without enough RAM for a full desktop environment (less than 512 MB RAM).

[SIZE=4]Tested and debugged system to install [Ubuntu flavours of] Xenial 32-bit alias 16.04 LTS[/SIZE]

This is a compressed image file of an installed Ubuntu mini system with text user interface. It is a good start for installing various flavours of Ubuntu or your own custom system by selecting which program packages to install. It is made to be installed with *mkusb*, but can be installed with other cloning tools too, for example *mkusb-nox* in text mode or {*7-zip* & Win32 Disk Imager} in Windows. This 32-bit system in meant to run in BIOS mode.

This system has been made up to date June 29, 2016. Features of the corresponding 64-bit UEFI-and-BIOS systems have been added: htop, a menu to select text mode font size, and the 'tasksel' menu for all the options of the Ubuntu Server.

The 'Intl' text in the file name indicates that the system contains the package 'xserver-xorg-video-intel', which makes the system work will some old Intel graphics chips.

dd_X32-Txt-Startx-Intl_2016-06-29_7.8GB.img.xz

with the following md5sum:

7873e02b1cc5dcb5efe9a76569d7e2ba  dd_X32-Txt-Startx-Intl_2016-06-29_7.8GB.img.xz

[hr][/hr] user: guru password: changeme

[hr][/hr] There is a corresponding tarball to be installed with the One Button Installer

X32-Txt-Startx-Intl_2016-06-29.tar.xz

#373

sudodus said:

+ The *font size* is set in the shellscript text-mode-menu.

Yep i figured that out already!:)

sudodus said:

+ The problem with startx is solved by providing a system with Fluxbox et.al. already installed. Then it can be started via startx also in 32-bit computers, and provide a very light system. It uses only 54 MB RAM when running idle. See the attached screenshot. This can be a good alternative if you want a server and want to use some graphical tool sometimes. (After using that tool, you can exit from Fluxbox and return to the text mode menus.) But above all, it is a good alternative for a computer without enough RAM for a full desktop environment (less than 512 MB RAM).

Thanks for the heads up. Will keep you updated with anything new. Best Regards

#374

runrickus said:

+ The font size is set in the shellscript text-mode-menu.

Yep i figured that out already!

Yes, but in the version of 2016-06-29 it is done automatically (without entering the font menu).

+ The problem with startx is solved by providing a system with Fluxbox et.al. already installed. Then it can be started via startx also in 32-bit computers, and provide a very light system. It uses only 54 MB RAM when running idle. See the attached screenshot. This can be a good alternative if you want a server and want to use some graphical tool sometimes. (After using that tool, you can exit from Fluxbox and return to the text mode menus.) But above all, it is a good alternative for a computer without enough RAM for a full desktop environment (less than 512 MB RAM).

Thanks for the heads up. Will keep you updated with anything new. Best Regards

After more testing I found a hiccup with my old IBM Thinkpad. Fluxbox is started with startx and on exit it returns to the text mode menu. But a very pale menu, hardly visible. It is recovered by switching screens

*ctrl + alt + F2* (and a login prompt is displayed will full contrast) *ctrl + alt + F1* (and the full colour of the text mode menu is back)

This behaviour reminds of the method to recover from the 'lost cursor bug', and is maybe related, but the Thinkpad uses the Mobility Radeon 7500 chip (not Intel graphics).

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1568604

My old Dell with Pentium 4 is *not* affected by this hiccup. It uses a different graphics chip, nvidia NV34 [Geforce FX5200].

These two computers are both 12 years old. It is still possible but getting difficult to keep everything working with a new linux operating system :-)

#375

[SIZE=4]mkusb version 11.0.1[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] New: mkusb version 11 is divided in mkusb (FOSS) and usb-pack-efi (with compiled code) [/td][/tr][/table]

*mkusb* has been re-structured to be completely FOSS, Free and open-source software. The file usb-pack_efi.tar.gz is provided via a separate package for people who want it, while other people can get a lean version without any compiled code. This is done to prepare for getting mkusb into an official repository.

  • mkusb is prepared to be FOSS without 'usb-pack_efi.tar.gz' with optional use of this package to create persistent live drives that work in UEFI and BIOS mode with 64-bit *and* 32-bit iso files
  • the new package usb-pack-efi is available from ppa:mkusb/unstable during a testing period. Then it will be available from ppa:mkusb/ppa
  • the function *get_usb_pack_efi* is created (in mkusb)
  • the program logic of mkusb is modified to work as well as possible both with and without usb-pack_efi.tar.gz
  • the output (to zenity dialogue windows and to the log) is modified to help managing the new structure

*mkusb-nox* is not modified at all, but remains at version version 7.5.9.7

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 10.6.6 is still uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#376

[COLOR="#505050"][SIZE=3]Persistent live systems[/SIZE]

Most of the time it is enough with a live only USB pendrive and only a waste of effort to create a persistent live system. The cloning method of mkusb is very reliable and works with most linux distros. It needs hybrid iso files. But sometimes it is better to have a persistent live system, and beginning with version 10 mkusb can create such systems.[/COLOR]

[COLOR="#505050"][SIZE=3]Persistent live system in one single drive[/SIZE]

You can create a persistent live drive (typically a USB drive) with mkusb. Then there will be an entry in the grub boot menu to select persistence, and the whole persistent live system will reside in one drive.

This mkusb/persistent system is described at the following link[/COLOR]

mkusb/persistent

[hr][/hr] [SIZE=4]Simple persistence - one boot drive with a cloned copy of the iso file and another drive for persistence[/SIZE]

I use the term 'Simple persistence' for a system, that uses a cloned read-only boot drive (CD, DVD, USB) and another drive with partitions for persistence.

It is very easy to create persistence this way, but maybe a bit inconvenient to use it. You have to enter the boot option persistent every time it is used, because the cloned system from the iso file has a read-only ISO 9660 file system (and cannot be changed). (If you use a tool that creates a live-only boot drive with a writable file system, it is possible to edit the configuration and get an entry in the boot menu to select persistence, but it is outside of the scope of this description.)

This method is described at the following link,

mkusb/sp

There are both advantages and disadvantages to have the persistence separate from the boot drive. It is possible to make partitions for persistence in an internal drive as well as in an external drive. You can have several drives with persistence for different purposes or simply backup copies.

#377

just keeps on getting better...Thanks sudodus

#378

1fallen said: just keeps on getting better...Thanks sudodus

You are welcome :-)

-o-

How come there are rectangles with white and gray in the attached screenshot?

#379

Forum Glitch I suppose :confused: Never noticed it til just now... Thanks for your hard work old friend.;)

#380

What that probably is when 1fallen took a screenshot and used "select a region" instead of the Entire Screen or Active window. It's done that to me a few times. Sometimes it does and sometimes it doesn't

Nice Wiki by the way sudodus! :D

#381

Cavsfan said: What that probably is when 1fallen took a screenshot and used "select a region" instead of the Entire Screen or Active window.

It's done that to me a few times. Sometimes it does and sometimes it doesn't

Nice Wiki by the way sudodus! :D Yep spot on Cavsfan just checked in my screenshot folder and they are present there also.:) And remember keep on arch-ing:P

#382

You are welcome *Cavsfan* :-)

#383

Unattended upgrade broke persistent live installation, see here.

#384

I made a boot/installation media of Mythbuntu 16.04 by mkusb 10.6.6. I run a persistent live session. Unattended-upgrades started to operate and install e.g. new kernel on the USB flash drive. The consequence was that system ran out of inodes here: /dev/loop0 mounted at /rofs. How to recover?

Upgrades do not work for the kernel in any persistent live system, because the kernel is started before the overlay structure becomes active.

In general it is *not* a good idea to upgrade a persistent live system completely, like an installed system - you can add new program packages, and you can upgrade a few application programs, where you really need an upgraded version for something to work. And you need regular backups, for example via the system described at Backup and restore of persistent overlay data

If you want a generally updated and upgraded system, it is better to

  1. either create an installed system, which is suitable to update && dist-upgrade via the command line or automatically.
  1. or grab the newest daily iso file, and create a new persistent live system. You find it via this link: Xenial Daily. In your case, select a version of Mythbuntu, and you will find a link to the download information. (The 16.04 daily iso files will no longer be updated after 16.04.5 is released.)

I suggest that you save the /home directory in the casper-rw partition (to another drive) and copy it to your new persistent live system (now based on the current daily live iso iso). It will save your tweaks. You must re-install the additional program packages you need manually.

#385

I was surprised the system started automatic security upgrades by default. Not sure if it is a bug in mkusb, but I had better to disable unattended upgrades there in the persistent session. I have not tested if the upgrades will run in normal live session, too.

I guess I had better make new persistent live system and disable unattended-upgrades immediately once I boot it. &#8211; jarno yesterday

Looking at the persistent live Ubuntu 16.04 LTS system - the Software & Updates screen / Update - I notice, that Automatic updates is set to 'Download and install automatically'. This is bad in a persistent live system.

After leaving the persistent live Ubuntu 16.04 LTS system running overnight, I found that it had performed an automatic upgrade:

*df* revealed that the content in casper-rw had increased to 1.6 GiB,

ubuntu@ubuntu:~$ df /media/ubuntu/casper-rw/
Filesystem     1K-blocks  Used Available Use% Mounted on
/dev/sda5        9259672 42864   8730052   1% /media/ubuntu/casper-rw

# waiting overnight ...

ubuntu@ubuntu:~$ df /media/ubuntu/casper-rw/
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sda5        9259672 1620968   7151948  19% /media/ubuntu/casper-rw

ubuntu@ubuntu:~$ df -h /media/ubuntu/casper-rw/
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda5       8.9G  1.6G  6.9G  19% /media/ubuntu/casper-rw

and I can confirm that the current kernel was installed. After saving the 'evidence' to my main computer, I rebooted, and it works. Of course, it is still using the kernel from the iso file image, but it works (as a persistent live drive).

However, this is risky: If not enough space (and inodes) in the casper-rw partition or file, the upgrade operation will be incomplete and fail. There might be big problems even if there is space left in casper-rw, and finally, this is wasting the available space, unless you have a huge casper-rw partition.

-o-

I am surprised that the persistent live system started an automatic upgrade. I don't think it is caused by the installer (mkusb), because the files controlling those actions are not touched. I can test what happens in an Ubuntu 16.04.1 LTS system, that I leave by itself for a long time. (I have no own experience of Mythbuntu.)

Yes, until this is resolved,* it is a good idea to disable unattended-upgrades, but above all, to take regular backups, when you use a persistent live system*.

#386

There is a separate thread for the problem with unattended updates in persistent live drives: Unattended-upgrades can break persistent live media

and a bug report at Launchpad: Bug #1619188: Unattended upgrades can break persistent live media

If this bug affects you, please mark 'Affects me too' to confirm the bug at Launchpad.

#387

[SIZE=4]mkusb version 11.0.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] change from 'Download and install automatically' to 'Display immediately' [/td][/tr][/table]

*Change the default settings for security updates for persistent live systems*

*mkusb 11.0.2* can change the default from 'Download and install automatically' to 'Display immediately'. It is available from the unstable PPA

  • the function chk4ubuntu_upgrades is created, and provides a user interface to select or skip this action.
  • the changes are implemented by writing two files to the casper-rw partition
  • [*]upper/etc/apt/apt.conf.d/10periodic
  • [*]upper/etc/apt/apt.conf.d/20auto-upgrades

*mkusb-nox* is not modified at all, but remains at version version 7.5.9.7

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb
sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 11.0.1 is uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb
#388

I ran a long time test with a persistent live Ubuntu 16.04.1 LTS amd64 (made with mkusb) during several days and nights and it did *no* unattended upgrade. So the tweak in mkusb version 11.0.2 works for me :-)

You find it at the unstable PPA. See this link: [[mkusb] from the unstable PPA](https://help.ubuntu.com/community/mkusb/gui#from_the_unstable_PPA)

#389

[SIZE=4]mkusb version 11.0.3[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] fix to manage 'flash cards' seen as /dev/mmcblk0, /dev/mmcblk1, ... by built-in card readers in laptops. [/td][/tr][/table]

*mkusb and mkusb-nox 11.0.3* display flash cards among USB drives, while [s]ata drives are considered more important to protect from overwriting by mistake - you must toggle 'usb-only' to see also the ata drives. . It is available from phillw.net, described in this link,

mkusb/gui#from phillw.net

[hr][/hr]

Soon you will get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 11.0.1 is uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#390

I was able to boot my Intel NUC from a persistent live micro SD card (in an SD adapter) from the built-in slot. The card is recognized as /dev/mmcblk0. See the terminal window dialogue. See also the attached file.

lubuntu@lubuntu:~$ [COLOR="#0000FF"]sudo lshw -class bus|grep -A100 '*-core'|grep -v '*-core'|while true;do read ans;if [ "$ans" == "${ans/\*-}" ]; then echo "$ans"; else exit; fi;done[/COLOR]
description: Motherboard  
product: [SIZE=3]NUC6i3SYB[/SIZE]
vendor: Intel corporation
physical id: 0
version: H81132-502
serial: GESY5490011S
slot: Default string
lubuntu@lubuntu:~$ [COLOR="#0000FF"]sudo lsblk -fm /dev/mmcblk0[/COLOR]
NAME        FSTYPE  LABEL                     UUID                                 MOUNTPOINT               NAME         SIZE OWNER GROUP MODE
mmcblk0                                                                                                     mmcblk0     29.7G root  disk  brw-rw----
&#9500;&#9472;mmcblk0p1 ntfs    usbdata                   0CEAB56011020FF7                     /media/lubuntu/usbdata   &#9500;&#9472;mmcblk0p1  9.5G root  disk  brw-rw----
&#9500;&#9472;mmcblk0p2                                                                                                 &#9500;&#9472;mmcblk0p2    1M root  disk  brw-rw----
&#9500;&#9472;mmcblk0p3 vfat    lub1604164                0FA8-5C36                                                     &#9500;&#9472;mmcblk0p3  122M root  disk  brw-rw----
&#9500;&#9472;mmcblk0p4 iso9660 Lubuntu 16.04.1 LTS amd64 2016-07-20-12-16-02-00               /cdrom                   &#9500;&#9472;mmcblk0p4  874M root  disk  brw-rw----
&#9492;&#9472;mmcblk0p5 ext4    casper-rw                 87cede8d-2eb6-495b-a882-b3e43c717288 /media/lubuntu/casper-rw &#9492;&#9472;mmcblk0p5 19.3G root  disk  brw-rw----
lubuntu@lubuntu:~$[COLOR="#0000FF"] sudo parted /dev/mmcblk0 print[/COLOR]
Model: SD SE32G (sd/mmc)
Disk /dev/mmcblk0: 31.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 2      1049kB  2097kB  1049kB               primary  bios_grub
 3      2097kB  130MB   128MB   fat32        primary  boot, esp
 4      130MB   1046MB  916MB                primary
 5      1046MB  21.7GB  20.7GB  ext2         primary
 1      21.7GB  31.9GB  10.2GB  ntfs         primary  msftdata

lubuntu@lubuntu:~$ [COLOR="#0000FF"]df -h[/COLOR]
Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           384M  6.2M  378M   2% /run
/dev/mmcblk0p4  855M  855M     0 100% /cdrom
/dev/loop0      809M  809M     0 100% /rofs
/cow             19G  125M   18G   1% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs           1.9G  4.0K  1.9G   1% /tmp
tmpfs           384M  4.0K  384M   1% /run/user/999
/dev/mmcblk0p5   19G  125M   18G   1% /media/lubuntu/casper-rw
/dev/mmcblk0p1  9.5G   50M  9.5G   1% /media/lubuntu/usbdata
lubuntu@lubuntu:~$ [COLOR="#0000FF"]uname -a[/COLOR]
Linux lubuntu 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
lubuntu@lubuntu:~$ [COLOR="#0000FF"]lsb_release -a[/COLOR]
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial
lubuntu@lubuntu:~$ 

Although I had created the drive when in the corresponding built-in slot in a Lenovo X131e, I could not boot it from there (in that computer). However, I could boot it in that computer, and in other computers, when connected via USB, built-in as in my Toshiba or via an adapter. (Also USB 3 adapters work and I can reach 60 MB/s read and write speed with the right kind of card.)

Now it will also be easier and safer to install operating systems for Raspberry Pi and other small devices, that boot from flash cards.

-o-

I have tried to test and debug all actions by mkusb and mkusb-nox, and now I need your help to find new bugs. So when you have time, please test version 11.0.3 of mkusb and mkusb-nox, and report your result. Both good and bad test results are welcome :-)

#391

My Lenevo T61 will not allow for bot (unless I use PLOP bootloader?) Will try that and on another machine. Very smooth to ssd card.

note: Sorry .. the forums is persistently not allowing upload of screeshots.

#392

OK.. this is amazing success!! I cannot believe it booted my 4GB SD card on my HP Pavilion. I am going to try some other ISOs. I booted the mini.iso just fine. mkusb recognizes an SD card that I thought was dead and restored cloned image. It also booted on a non pae system and notifed me as such.

Can't send screenshots as forum is having problems.

Regards..

#393

Installed gnome 14.04 persistent on MMC/SD. Very well done! I could not get this machine to work with MMS/SD. mkusb worked out of the box. One GUI bug. I copied ubuntu-gnome.iso to Desktop then opened mkusb. When I tried to go to dekstop directory to choose .ISO it would bounce back to home/username so I had to quit mkusb and copy it manualy to the home directory and thn it worked. Regards..


ubuntu-gnome@ubuntu-gnome:~$ inxi -Fxz
System:    Host: ubuntu-gnome Kernel: 3.13.0-24-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: Gnome 3.10.4 Distro: Ubuntu 14.04 trusty
Machine:   System: HP-Pavilion product: RK574AA-ABA a1730n
           Mobo: ASUSTek model: NODUSM3 version: 1.05 Bios: Phoenix version: 5.04 date: 12/15/2006
CPU:       Dual core AMD Athlon 64 X2 5000+ (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 svm) bmips: 4008.3 
           Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 02:00.0 
           X.Org: 1.15.1 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1440x900@59.9hz 
           GLX Renderer: Gallium 0.4 on NVA8 GLX Version: 3.0 Mesa 10.1.0 Direct Rendering: Yes
Audio:     Card: NVIDIA High Definition Audio Controller driver: snd_hda_intel bus-ID: 02:00.1 
           Sound: Advanced Linux Sound Architecture ver: k3.13.0-24-generic
Network:   Card: NVIDIA MCP51 Ethernet Controller driver: forcedeth port: c800 bus-ID: 00:14.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 324.1GB (0.0% used) 1: id: /dev/sda model: ST3320820AS size: 320.1GB temp: 34C 
           2: id: /dev/sdd model: SD/MMC size: 4.0GB temp: 0C 
Partition: ID: / size: 820M used: 136M (18%) fs: overlayfs ID: swap-1 size: 2.01GB used: 0.00GB (0%) fs: swap 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A gpu: 55.0 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 168 Uptime: 26 min Memory: 776.8/2000.9MB Runlevel: 2 Gcc sys: 4.8.2 
           Client: Shell (bash 4.3.8) inxi: 1.9.17 
ubuntu-gnome@ubuntu-gnome:~$ 
#394

Yes indeed Very well done....I have not fired up the ubuntu machine yet but on Arch works a treat.:KS Will give it more extensive testing tonite sudous....up to my eyeballs in honey-do's for the afternoon.;) Regards

#395

ventrical said: Installed gnome 14.04 persistent on MMC/SD. Very well done! I could not get this machine to work with MMS/SD. mkusb worked out of the box. One GUI bug. I copied ubuntu-gnome.iso to Desktop then opened mkusb. When I tried to go to dekstop directory to choose .ISO it would bounce back to home/username so I had to quit mkusb and copy it manualy to the home directory and thn it worked.

Regards..

I will try to reproduce this bug - and try to squash it. It should work also with iso files in the Desktop directory.

#396

1fallen said: Yes indeed Very well done....I have not fired up the ubuntu machine yet but on Arch works a treat.:KS

Will give it more extensive testing tonite sudous....up to my eyeballs in honey-do's for the afternoon.;) Regards

I'm looking forward to the results of your further tests :-)

#397

sudodus said: Installed gnome 14.04 persistent on MMC/SD. Very well done! I could not get this machine to work with MMS/SD. mkusb worked out of the box. One GUI bug. I copied ubuntu-gnome.iso to Desktop then opened mkusb. When I tried to go to dekstop directory to choose .ISO it would bounce back to home/username so I had to quit mkusb and copy it manualy to the home directory and thn it worked.

Regards..

I will try to reproduce this bug - and try to squash it. It should work also with iso files in the Desktop directory.

*I could not reproduce this bug in 16.04.1 LTS*, neither in my installed Lubuntu + Xubuntu system nor in a persistent live Lubuntu system.

See this mkusb.log file (high-lights in red) and the attached screenshots #1-2.


The mkusb console window displays,
or the file ~/mkusb.log contains:
output from the engine behind the zenity curtain.
---------------------------------------------------------------------------
start [mkusb 11.0.3] @ 2016-09-16 06:24:04 AM
---------------------------------------------------------------------------
Current directory=/home/lubuntu
main: usbonly=true
main: liveonly=true
No input file specified yet
main: source=''
TERM=unknown
ubuntu
---------------------------------------------------------------------------
menu_shell:
select_source: imagefile=/home/lubuntu/Downloads/mini.iso
---------------------------------------------------------------------------
menu_shell:
select_source: imagefile=/home/lubuntu/Downloads/mini.iso
---------------------------------------------------------------------------
menu_shell:
[COLOR="#cc0000"]select_source: imagefile=/home/lubuntu/Desktop/TinyCore-5.4.iso[/COLOR]
---------------------------------------------------------------------------
menu_shell:
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/lubuntu/Desktop/TinyCore-5.4.iso
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /dev/loop2 is write-protected, mounting read-only
disk_name_type=title
MENU TITLE TinyCore _found_ in iso-file
MENU TITLE TinyCore _not_ in any possible target drive
Booted from: /dev/sda
/dev/sda is busy; cannot be unmounted. Close any program that is using
this device if you want to select and use it as a target for mkusb (maybe
change directory if a terminal window is using the partition)!
ans=1
 
Installing [COLOR="#cc0000"]/home/lubuntu/Desktop/TinyCore-5.4.iso to /dev/mmcblk0[/COLOR] ...
 
gpt_zap: done
---------------------------------------------------------------------------
do_n_show:
&lt; "TinyCore-5.4.iso" pv -n -s 14680064 | dd bs=4096  of=/dev/mmcblk0
 
( < "TinyCore-5.4.iso" pv -n -s 14680064 | dd bs=4096  of=/dev/mmcblk0 && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 )
Please wait for sync (flushing file system buffers to the device)
until 'Done' is written ...
'pv %'; 'dd final output'
100
3584+0 records in
3584+0 records out
14680064 bytes (15 MB, 14 MiB) copied, 0.0604942 s, 243 MB/s
Done
do_n_show: Work done
---------------------------------------------------------------------------
Syncing the device ...
Done :-)
Cleanup after mkusb finished :-)
---------------------------------------------------------------------------
Total time used [by mkusb] = 290 s; 00:04:50

-o-

Did you try a persistent live Ubuntu Gnome 14.04 LTS? 'Kernel: 3.13.0-24-generic' tells me it is not updated & upgraded at all. *I tried in Ubuntu Gnome 14.04.1 LTS*, which is where you should start, if you want the trusty kernel, and *I could not reproduce the bug* :???:

$ uname -a
Linux ubuntu-gnome 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I don't know why and how you moved the iso file to the desktop (I don't know the name of the 'desktop' in Ubuntu Gnome, files in ~/Desktop are not displayed on the 'desktop'). Anyway, if the iso file is in the directory ~/Desktop, it works. See 'this mkusb.log' and attachments #3-4.


The mkusb console window displays,
or the file ~/mkusb.log contains:
output from the engine behind the zenity curtain.
---------------------------------------------------------------------------
start [mkusb 11.0.3] @ 2016-09-16 07:42:20 AM
---------------------------------------------------------------------------
Current directory=/home/ubuntu-gnome
main: usbonly=true
main: liveonly=true
No input file specified yet
main: source=''
TERM=xterm
ubuntu
---------------------------------------------------------------------------
menu_shell:
select_source: imagefile=/home/ubuntu-gnome/Desktop/mini.iso
---------------------------------------------------------------------------
menu_shell:
[COLOR="#cc0000"]select_source: imagefile=/home/ubuntu-gnome/Desktop/TinyCore-5.4.iso[/COLOR]
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/ubuntu-gnome/Desktop/TinyCore-5.4.iso
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: block device /home/ubuntu-gnome/Desktop/TinyCore-5.4.iso is write-protected, mounting read-only
disk_name_type=title
MENU TITLE TinyCore _found_ in iso-file
MENU TITLE TinyCore _not_ in any possible target drive
Booted from: /dev/sda
/dev/sda is busy; cannot be unmounted. Close any program that is using
this device if you want to select and use it as a target for mkusb (maybe
change directory if a terminal window is using the partition)!
ans=1
 
[COLOR="#cc0000"]Installing /home/ubuntu-gnome/Desktop/TinyCore-5.4.iso to /dev/mmcblk0 ...[/COLOR]
 
gpt_zap: done
---------------------------------------------------------------------------
do_n_show:
&lt; "TinyCore-5.4.iso" pv -n -s 14680064 | dd bs=4096  of=/dev/mmcblk0
 
( < "TinyCore-5.4.iso" pv -n -s 14680064 | dd bs=4096  of=/dev/mmcblk0 && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 )
Please wait for sync (flushing file system buffers to the device)
until 'Done' is written ...
'pv %'; 'dd final output'
100
3584+0 records in
3584+0 records out
14680064 bytes (15 MB) copied, 0.04388 s, 335 MB/s
Done
do_n_show: Work done
---------------------------------------------------------------------------
Syncing the device ...
Done :-)
Cleanup after mkusb finished :-)
---------------------------------------------------------------------------
Total time used [by mkusb] = 243 s; 00:04:03
#398

I installed mkusb (as per your instructions) on a laptop with ubuntu-trusty - fully upgraded (unity-desktop). I copied (dragged) the ubuntu-gnome-14.04. iso from a USB stick to the desktop. When I ran mkusb it would not let me go to the /desktop. It would also not allow me to drag the .ISO file from the desktop to home/user_name. So , as I said .. I had to close mkusb, open nautilus and then drag the .ISO file to home/user_name and it worked. I'll try with another .ISO today.

Regards..

#399

Copied mini.ios to desktop. mkusb will still not allow me to access desktop. It sort of graphically bounces to /home.

#400

I think I see the problem now. You are trying to trying with root's Desktop directory. But you should change directory to the current user's home directory, and then to the Desktop, so for example

in an installed system: /home/ventrical/Desktop

in a live system: /home/ubuntu/Desktop

Does this solve the problem?

It should also be possible to drag and drop the iso-file's desktop icon into mkusb's window 'Select source file' - and it will be accepted (and in the correct place), if the permissions allow, and I think they do (at least it works for me).

-o-

I think there is something for me to do here. In a fresh install of mkusb, the window 'Select source file' is located at /root. It is not very intuitive, and should be changed to the default user's home directory ~ alias "$HOME". I will look into that.

#401

I am just going along with the program (as before) I didn't change anything. The #root comes up right after I select an .iso.

regards..

#402

I am trying to understand your problem. Obviously there is something that is wrong with mkusb in your system. Either it is making you confused, or it is acting in a different way compared to what I see here. So something is wrong.

Now I have installed mkusb into a live system of Ubuntu 14.04.1 LTS amd64. It should be close to your Ubuntu version. If no input file is selected, the window should default to $HOME of the user, in a live system 'ubuntu', maybe in your case 'ventrical'. But if you click on the bookmarks in the top left corner, you will get root's home directory, which is not what you want.

The first attached screenshot show how it looks for me. The second screenshot illustrates drag n drop.

Is this what you have ventrical, or is your system getting locked somehow?

#403

ventrical said: Copied mini.ios to desktop. mkusb will still not allow me to access desktop. It sort of graphically bounces to /home.

Yes I see the same... But the Drag and Drop works. Second Screenshot is after the Drag and Drop. But this is not how "I" usually use it. So far so good with the normal way of using it for a USB install. But still testing it.:)

#404

Could it be a problem with permissions? But mkusb is running via sudo -H, so unless you have very special permissions, it should be able to read your iso file. Anyway, I'm install Ubuntu Trusty from the first point release. We'll soon know, if I'm affected too ;-)

#405

1fallen said: Yes I see the same... But the Drag and Drop works.

But this is not how "I" usually use it. So far so good with the normal way of using it for a USB install. But still testing it.:)

Are you logged in as root in Arch, or as a regular user?

#406

sudodus said: Are you logged in as root in Arch, or as a regular user?

Never do I log in as root...:)

#407

My friend.. I do not run mkusb from 'live' systems. All my instances of mkusb, past , present and future are on HARD installs:)

Here is most recent screenshot - (I was able to fanagle to desktop and it worked) but now there is new bug.. policykit will not go aways until after 4 or 5 times.

#408

ventrical said: My friend.. I do not run mkusb from 'live' systems. All my instances of mkusb, past , present and future are on HARD installs:)

Here is most recent screenshot - (I was able to fanagle to desktop and it worked) but now there is new bug.. policykit will not go aways until after 4 or 5 times.

Is this replying to sudodus?? or me.. "HARD installs"

#409

In my *installed* Ubuntu Trusty test system, mkusb behaves like the live system. The default directory (when no input file is selected), is the user's "$HOME", in this case ~tester alias /home/tester, as shown by the attached screenshot.

As you can see lsb_release says 14.04.5 LTS, but uname confirms that it is the Trusty kernel, 3.13. And df confirms that it is an installed system.

I must ask again: is the problem the two bookmarks at the top left corner, 'Home' and 'Desktop'? Do not use them, because they belong to root. The reason is that mkusb is run via sudo -H, so that zenity, when started from mkusb, has root as the user id.

I can agree, that it is confusing. I can think of a method to fix this, but it would mean a lot of re-building of mkusb. It would be possible to separate the selection of the input file from the other parts of mkusb, and to run only the other part with sudo. Then the bookmarks at the top left corner, 'Home' and 'Desktop', would belong to the current user, in the example of this post, 'tester'.

Is this the problem, or is it something else?

#410

1fallen said: Is this replying to sudodus?? or me.. "HARD installs"

Well.. you are both my friends .. but it was to sudodus :)

Sorry..:)

#411

ventrical said: Well.. you are both my friends .. but it was to sudodus :)

Sorry..:)

No worries :smile: Just wanted to be sure...but kind of thought that was the case. After all you know me better than most here..:D

#412

sudodus said: In my *installed* Ubuntu Trusty test system, mkusb behaves like the live system. The default directory (when no input file is selected), is the user's "$HOME", in this case ~tester alias /home/tester, as shown by the attached screenshot.

As you can see lsb_release says 14.04.5 LTS, but uname confirms that it is the Trusty kernel, 3.13. And df confirms that it is an installed system.

I must ask again: is the problem the two bookmarks at the top left corner, 'Home' and 'Desktop'? Do not use them, because they belong to root. The reason is that mkusb is run via sudo -H, so that zenity, when started from mkusb, has root as the user id.

I can agree, that it is confusing. I can think of a method to fix this, but it would mean a lot of re-building of mkusb. It would be possible to separate the selection of the input file from the other parts of mkusb, and to run only the other part with sudo. Then the bookmarks at the top left corner, 'Home' and 'Desktop', would belong to the current user, in the example of this post, 'tester'.

Is this the problem, or is it something else?

Ok.. for some reason it now remembers it's navigation from last session.

I'm just reporting behaviour like you asked us to. This behaviour was not there of previous versions. But it is working on this session.

#413

whoops.. ok..gotchya :)

#414

ventrical said: My friend.. I do not run mkusb from 'live' systems. All my instances of mkusb, past , present and future are on HARD installs:)

Here is most recent screenshot - (I was able to fanagle to desktop and it worked) but now there is new bug.. policykit will not go aways until after 4 or 5 times.

It is not policykit, it is sudo with a zenity front-end for the password (because gksudo is no longer part of Ubuntu). What is happening? Are there problems because you type the wrong password? Is the zenity window persisting after you have typed the correct password? - Do you think I should add the gksu package and use gksudo instead?

#415

sudodus said: What is happening? Are there problems because you type the wrong password? Is the zenity window persisting after you have typed the correct password?

Just to pipe in... I'm not seeing that behavior on my end. In fact the window when you are done asking if you want to see Logs now closes immediately instead of force closing or manually closing it.

#416

ventrical said: Ok.. for some reason it now remembers it's navigation from last session.

Yes, the previously selected input file is saved in the file /usr/share/mkusb/selected. This has been working for a long time, for years.

I'm just reporting behaviour like you asked us to. This behaviour was not there of previous versions. But it is working on this session.

Your feedback is good as usual :-) I am too used to the program, I don't use it the 'wrong' ways, so I don't see what can cause problems.

But this time I have extra problems to understand what is the problem. And I think the problems you describe should have been around for a rather long time, at least since January (2016), because I don't think I have touched things that would change these things lately. Of course - I could be wrong, but this is what I think - and anyway, whenever a bug or confusing feature is discovered, it will help improving the program.

#417

1fallen said: Just to pipe in... I'm not seeing that behavior on my end. In fact the window when you are done asking if you want to see Logs now closes immediately instead of force closing or manually closing it.

It closes after 1 s instead of 3 s (so you have to be quick to open the zenity error log).

#418

sudodus said: It closes after 1 s instead of 3 s (so you have to be quick to open the zenity error log).

And that is a good thing now.:) Before that it waited a lot longer than 3 secs for me...I usually just closed it myself. But everything I have done with the new version of mkusb has worked a treat for me. So I give it 5 :KSs.:D All kidding aside Nice Job sudodus.

#419

Thanks *1fallen*,

Anyway, I will look into ways to fix the problem *ventrical* found - I hope to find a way without too much re-writing of the code.

#420

I think I have fixed the problem *ventrical* found. Please test it :-)

[SIZE=4]mkusb version 11.0.4 and 10.0.5[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] function select_source_as_user runs 'as user' not 'as root', mmcblk? added to filter [/td][/tr][/table]

*mkusb* uses a new function, 'select_source_as_user'.

It runs 'as user' not 'as root', so that the window has the correct home and desktop directories, when searching for source files (iso files, other image files and block devices (CD, DVD, USB, MMC); mmcblk? is added to the filter, so that a flash card can be found and selected as the source to be cloned: /dev/mmcblk0, /dev/mmcblk1 ...

A minor fix in mkusb-nox raised the version number to 11.0.5: removed an error output from lsblk, when no mmcblk? device is found.

It is available from phillw.net, described in this link, mkusb/gui#from phillw.net

[hr][/hr] After some more basic tests you will get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb 11.0.1 is still the version uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#421

This is a demo of the new features of mkusb:

  1. Attachment #1: The desktop bookmark is useful.
  1. Attachment #2: Select filter for flash drives seen as /dev/mmcblk devices also as source drive for cloning. The corresponding log file is displayed.

The mkusb console window displays,
or the file ~/mkusb.log contains:
output from the engine behind the zenity curtain.
---------------------------------------------------------------------------
start [mkusb 11.0.4] @ 2016-09-17 12:45:40
---------------------------------------------------------------------------
Current directory=/home/tester
main: usbonly=true
main: liveonly=true
No input file specified yet
main: source=''
TERM=unknown
ubuntu
---------------------------------------------------------------------------
menu_shell:
[COLOR="#cc0000"]select_source: imagefile=/dev/mmcblk0[/COLOR]
---------------------------------------------------------------------------
menu_shell:
imagefile=/dev/mmcblk0
Clone a device ... :
Booted from: /dev/sda
/dev/mmcblk0 is busy; it is the source device
/dev/sda is busy; in fstab
ans=3
 
[COLOR="#cc0000"]Installing /dev/mmcblk0 to /dev/sdb ...[/COLOR]
 
gpt_zap: done
---------------------------------------------------------------------------
do_n_show:
&lt; /dev/mmcblk0 pv -n  | dd bs=4096  of=/dev/sdb
 
( < /dev/mmcblk0 pv -n  | dd bs=4096  of=/dev/sdb && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 )
Please wait for sync (flushing file system buffers to the device)
until 'Done' is written ...
'pv %'; 'dd final output'
...
...
...
490240+0 records in
490240+0 records out
2008023040 bytes (2,0 GB) copied, 411,325 s, 4,9 MB/s
Done
do_n_show: Work done
---------------------------------------------------------------------------
Syncing the device ...
Done :-)
Cleanup after mkusb finished :-)
---------------------------------------------------------------------------
Total time used [by mkusb] = 1030 s; 00:17:10
login attempt 1

#422

sudodus said: Yes, the previously selected input file is saved in the file /usr/share/mkusb/selected. This has been working for a long time, for years.

Your feedback is good as usual :-) I am too used to the program, I don't use it the 'wrong' ways, so I don't see what can cause problems.

But this time I have extra problems to understand what is the problem. And I think the problems you describe should have been around for a rather long time, at least since January (2016), because I don't think I have touched things that would change these things lately. Of course - I could be wrong, but this is what I think - and anyway, whenever a bug or confusing feature is discovered, it will help improving the program.

I am sorry but I disagree with you. The file manager was not working like previous versions. After update it is now going to /home correctly. Despite this it is doing a masterful job with detecting MSD cards.

Thank you for great bug fix :)

Regards..

#423

Thanks *ventrical* for testing, finding this bug and verifying that mkusb works as it should after the bugfix :-)

I checked (in 16.04.1 LTS) and the same thing happens [with the home bookmark in the file selector] in some random samples all the way back to mkusb 9.0.1 from Sep 6 2014. But I have not checked in previous versions of Ubuntu. Probably part of the engine under the hood has changed, and is causing this changed behaviour (for example a new version of sudo).

I discovered an hour ago (before lunch), that Fedora 24 is different in a new way, and needs [SIZE=3]sudo -iH mkusb[/SIZE] (instead of [SIZE=3]sudo -H mkusb[/SIZE] in Ubuntu and also Fedora 20 and 21). So things are changing under the hood, and it is necessary to keep testing application programs in order to keep them running correctly :-P

*Edit:* I was able to change the code of mkusb, so that it will continue to work as before with ``` sudo -H mkusb

#424

[SIZE=4]mkusb and mkusb-nox version 11.0.7 and 11.0.8[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] fixes so that mkusb works also in Fedora 24 and openSUSE 42.1 [/td][/tr][/table]

Things have changed under the hood while I was looking in another direction. There were problems not only with *Fedora 24*, but also with *openSUSE 42.1*, but there are bug-fixes in version 11.0.7, that make mkusb and mkusb-nox work in both of those distros. See mkusb/v11 and Simple to test mkusb in linux distros, which do not manage an Ubuntu PPA.

*Edit 1:* I tested mkusb and mkusb-nox version 11.0.7 works in live systems of *Debian Jessie 8.6* and *Mageia 5*, and they work in these distros too. Persistence works with Debian Jessie too (as well as in Ubuntu), but not with Fedora, openSUSE and Mageia.

*Edit 2:* Version 11.0.8: bug-fix in the mechanism in select_source_as_user: default isdisplay=0 (alias default 'OK')

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb 11.0.5 is the version uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#425

There are new versions of the quick start manuals for mkusb and mkusb-nox.

#426

sudodus said: There are new versions of the quick start manuals for mkusb and mkusb-nox.

Thanks!.. got them both just now.

#427

1fallen said: Thanks!.. got them both just now.

You are welcome :-)

#428

[SIZE=4]mkusb and mkusb-nox version 11.1.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table]

  • mkusb-nox: added feature: make USB install drive for Windows
  • mkusb and mkusb-nox: several fixes to work well also in Debian *testing* alias 'Stretch' and *unstable* alias 'Sid'

[*]This method is tested and works with Windows versions 7, 8, 10. With 64-bit versions of Windows, the target drive will be able to boot and install in BIOS mode as well as in UEFI mode. [*]It was not possible to extract the content from the Windows iso file directly to a USB pendrive. The files were not copied correctly (with any of the standard copying tools: cp, rsync, dd) in Ubuntu 16.04.1 LTS (the current Ubuntu version, when this feature was added to mkusb-nox). But it works in a reliable way to extract to a tarfile, and then extract from the tarfile to the USB pendrive. The user dialogue is displayed in the attached screenshot.

[*]made the text strings refer to Debian like Ubuntu (no longer main focus on Ubuntu) [*]mkusb 'needs' rsync (not default in debian sid) [*]fix for new format of the colour specification [*]fix for text mode browser (run in xterm) [*][TABLE="class: cms_table"][tr][td="bgcolor: #e8a020"]persist_check_body_bg: separate background colour of the final checkpoint when persistent live[/td][/tr][/table]

  • *mkusb-nox: added feature: make USB install drive for Windows*
  • *mkusb and mkusb-nox: several bugfixes for Debian*, made things work not only in 'Jessie' but also in 'Stretch' and 'Sid'
  • *updated versions of the text mode manuals (version 11.1.1)*,
man mkusb
man mkusb-nox

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb 11.0.5 is the version uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#429

Got it!:) I seen where you were offered to view the Manual as well. This has become my go to tool for most of what I do. (In Testing) As far as I can see....another fine release sudodus.

#430

First, thanks so much for this tool, it's amazing! The alternatives (unetbootin, etc.) never seemed to work quite right for me.

I'm writing to ask how I can chroot into the overlaid filesystem. I don't see instructions anywhere. My use case is that I want to add a user to the persistent live environment with an encrypted home directory (ecryptfs) and it would be much more convenient to do so without having to actually boot the live usb.

Thanks!

#431

I don't know how to chroot into the overlaid filesystem (in the casper-rw partition). It is not a complete system.

But I have installed such a second user with an encrypted home directory, and it works. It is not too difficult to do it while running the live system.

#432

Thanks for the quick response. I will think of what I can overlay the casper-rw partition over to serve as the basis of the chroot. If I come up with something, can you tell me what the appropriate mount command would it be? Would I have to install the overlayroot package and then do something like ``` sudo mount -t overlayfs -o lowerdir=/path/to/base_system,upperdir=/media/mkusb/casper-rw/upper overlayfs /mountpoint

#433

I was able to get the mounts setup properly to do this. I had to do the following:

$ sudo aptitude install aufs-tools
$ mkdir overlay_mountpoint rofs
$ sudo mount /media/LiveUSB/casper/filesystem.squashfs rofs -t squashfs -o loop # mount the read-only part
$ sudo mount -t aufs -o br=/media/casper-rw/upper:rofs none overlay_mountpoint # mount the overlay

From there I could chroot into overlay_mountpoint and just run:

# adduser --encrypt-home foo

Rebooting to the live USB I can login as foo into an encrypted home.

#434

You know chrooting much better than I. Thanks for sharing this method to chroot into the overlaid system :KS

#435

[SIZE=4]mkusb and mkusb-nox version 11.1.5[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table] There are also some minor bug-fixes.

  • mkusb-nox: mkusb-nox independent [of other files]: echo commands instead of grub-win-install.cfg
  • mkusb: toram: menuentry with toram added (RAM drive to be used when enough RAM)

Notice the differences between the screenshots and how to identify that RAM drive is actually used. An important difference is high-lighted with a [COLOR="#FF0000"]red dot for the 'toram case'[/COLOR] and an [COLOR="#e8a020"]orange dot[/COLOR] for the other case.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb 11.0.5 is the version uploaded at the stable PPA, ppa:mkusb/ppa.

You get/update that version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#436

[SIZE=4]mkusb and mkusb-nox version 11.1.5[/SIZE]

mkusb and mkusb-nox version 11.[COLOR="#cc0000"]1[/COLOR].5 are copied to the stable PPA for the Ubuntu releases 16.04 LTS, 16.10 and Zesty (to become 17.04).

mkusb and mkusb-nox version 11.[COLOR="#0000ff"]0[/COLOR].5 remain in the stable PPA for the older Ubuntu releases because the new version is not tested enough.

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

*Edit:* You can install the version 11.1.5 from the unstable PPA into the older Ubuntu releases if you wish. See the previous post.

#437

Mkusb is coming along great, For sure it is the most useful Live USB maker out there.

However...

One thing I still like about the original MultiBootUSB is the ability to drag and drop O/S iso files onto it. This makes it east to upgrade from one version to another, review daily builds, multiboot, etc. It would (seem to) be a simple option to add to mkusb. As proof of concept I took a flash drive made using the EFI/GPT option and used gparted to reformat sdb4 to FAT32. I also split the casper-rw partition in half to add a home-rw partition. After modifying grub.cfg a bit, I dropped the Ubuntu 16.04 64bit Desktop iso onto the sdb4 partition. Booting seems to take a little longer but everything else worked OK.

I added some stuff to the home folder, installed a few programs and modified the desktop, the drive was persistent. Then the 16.04 iso was replaced with a 14.04 64 bit iso. The disk failed to boot, whining about Low Graphics Mode. I then deleted the data in casper-rw, but not home-rw, the drive then booted fine. The data in home was still there but the desktop mods and downloaded programs were missing. This was repeated using a 12.04 32bit iso which again would not boot until e was pressed at the grub menu and .efi removed from the menuentry. This time the desktop mods persisted, including the shortcut to install 14.04. To speed up the tests I renamed the new iso's to match the iso name in grub.cfg so it would not require editing each upgrade. I'm sure there is a more elegant way to do

this. Another option might be to store the iso('s) on sdb1 so they can also be updated using a Windows machine, but this would not be so simple.

Forgive me if this idea has already been discussed to death or is too much like grub-n-iso, however it would be nice to have all of these options in one tool.

#438

Thanks for your ideas to improve mkusb, C.S.Cameron :-)

There is a reason why I do not use the iso files as files, but clone them to a partition of suitable size: I was not able to boot some community re-spins from iso files.

But I have another development branch with iso files, also multiple iso files can be used. You have probably seen this link (but I remind you of it),

One pendrive for all PC (Intel/AMD) computers - single-boot dual-boot multi-boot

Recently I have focused very much on mkusb, and I am preparing a new interface, which should be easier to use for beginners, and easier to maintain. You will soon find it :-)

-o-

After that version is debugged, polished and ready for general use, I would have time to look into your ideas, maybe starting from 'One pendrive for all PCs' (and merging it into the same user interface if not too complicated).

I agree, now that big and fast USB pendrives are rather cheap, it is a good idea to have a separate home-rw partition, and that way it should be easy to upgrade or to switch between different iso files and still keep the tweaks and personal files, that are stored in the home directory.

#439

No, no, no! I would not remove mkusb's ability to clone to the iso9660 partition, only add a toggle so that dd can copy the .iso file to a read/write FAT32 partition instead, if desired. I am not so sure about OPFAC, I've been spending quite a bit of time updating old "Ask Ubuntu" posts with the mkusb solution, (and don't want to switch horses mid stream). It seems there is a team over there that marks new USB boot questions as Duplicates, (often of ten year old questions?), even if they have nothing in common and the original solution no longer works.

#440

Since 14.04 home-rw partitions in a persistent install do not seem to be working the same as /home partitions in a Full install. The home-rw partition contains some folders same as a full install including: Desktop, Documents, Downloads, Music, etc. Desktop mods are not saved in home-rw unless it is the only, (or possibly first), persistent partition. Program installs, wireless passwords and such are only stored in casper-rw. Don't get me wrong, I think a home-rw option would be great in mkusb.

Edit: If sdb5 is home-rw and sdb6 is casper-rw, desktop mod's, (wallpaper), are preserved in home-rw.

#441

C.S.Cameron said: No, no, no! I would not remove mkusb's ability to clone to the iso9660 partition, only add a toggle so that dd can copy the .iso file to a read/write FAT32 partition instead, if desired.

I am not so sure about OPFAC, I've been spending quite a bit of time updating old "Ask Ubuntu" posts with the mkusb solution, (and don't want to switch horses mid stream). I see. Well, I will not change mkusb without asking for advice, listening to the advice and thinking twice.

It seems there is a team over there that marks new USB boot questions as Duplicates, (often of ten year old questions?), even if they have nothing in common and the original solution no longer works.

"Ask Ubuntu" is managed in a different way compared to the Ubuntu Forums, Ubuntu wiki pages and Ubuntu help pages. I have also noticed this problem. Maybe there is a bot, that is marking new USB boot questions as Duplicates.

Since 14.04 home-rw partitions in a persistent install do not seem to be working the same as /home partitions in a Full install.

The home-rw partition contains some folders same as a full install including: Desktop, Documents, Downloads, Music, etc. Desktop mods are not saved in home-rw unless it is the only, (or possibly first), persistent partition. Program installs, wireless passwords and such are only stored in casper-rw. Don't get me wrong, I think a home-rw option would be great in mkusb.

Edit: If sdb5 is home-rw and sdb6 is casper-rw, desktop mod's, (wallpaper), are preserved in home-rw.

I will look closely into the behaviour of home-rw. I agree that it can be useful.

[hr][/hr] *Extract or copy?*

Do you mean to extract the iso file to a read/write FAT32 partition, or to copy the iso file as a file, and to provide grub menuentries to use the iso file?

[hr][/hr] You can have a look at the *unstable PPA of [COLOR="#0000FF"]xenial[/COLOR]* and newer versions or look at *phillw.net*, where there is an early version of this new horse, now named *dus*, '[COLOR="#748f02"]D[/COLOR]o [COLOR="#748f02"]U[/COLOR]SB [COLOR="#748f02"]S[/COLOR]tuff', with the graphical interface *guidus*. After debugging and polishing it can be renamed to mkusb (maybe it will become mkusb version 12).

You get/update this refurbished version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install dus     # to get a general version provided with ***dialog*** menus for text mode
sudo apt-get install guidus  # to get dus with a GUI interface and ***zenity*** menus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and via this link: mkusb/gui#from_phillw.net

The intention is to make it easier to use and easier to maintain. I removed some features, that nobody has commented on and I think very few have used, and I think the user interface is much easier to use compared to mkusb and mkusb-nox. For example, there are no 'toggle' menu entries, and the style is 'wizard' with the tasks following each other. (The 'final checkpoint' is changed for a special reason: The current mkusb version with coloured background is good, but it depends on zenity's support for html, which has failed for long periods of time more than once during a couple of years. The new version (screenshot #5) should be as safe as before, and it is only using basic zenity features: the 'Go' radio button must be selected *and* the 'Go' button must be pressed).

I hope and think it should work with minimal instructions.

'dus' might not look as good as the current mkusb version, but it is possible to remove some rough edges. Of course we can expect bugs at this stage, but I think it will soon surpass mkusb in user friendliness.

See the attached screenshots, and install dus have a look at the real thing and tell me what you think! Early feedback can make a big difference :-)

#442

Is sudodus really just one person? The amount of work produced seems more like it comes from a large team.

Extract or copy?

Do you mean to extract the iso file to a read/write FAT32 partition, or to copy the iso file as a file, and to provide grub menuentries to use the iso file?

I was thinking that if the iso is copied to a FAT32 partition, it can easily be replaced without reinstalling with mkusb, With new versions the info in casper-rw needs to be deleted. This is the grub.cfg I used:

set default="1"
set timeout=10
if loadfont /boot/tools/fonts/unicode.pf2 ; then
set gfxmode="640x480"
insmod gfxterm
insmod vbe
terminal_output gfxterm
if terminal_output gfxterm; then true ; else
terminal gfxterm
fi
fi
insmod tga
if background_image /boot/tools/images/bg.tga ; then
set color_normal=blue/black
set color_highlight=red/black
else
set color_normal=white/black
set color_highlight=white/light-gray
fi

GRUB_GFXMODE=1024x768x16
insmod vbe

menuentry "ubuntu-16.04.1-desktop-amd64.iso" {
set root=(hd0,4)
loopback loop /ubuntu-16.04.1-desktop-amd64.iso
linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/ubuntu-16.04.1-desktop-amd64.iso noeject noprompt -- persistent
initrd (loop)/casper/initrd.lz
}

Dus is looking good but when it is done I hope you re-name it "mkusb II", or "son-of-mkusb", mkusb is getting a pretty good rep and is gaining quite a following, Please not "new mkusb" Image 4 is the only one that is at all a little confusing.

#443

C.S.Cameron said: Is sudodus really just one person? The amount of work produced seems more like it comes from a large team.

I have retired from work, so I have a lot of time ;-)

There are people who help me with testing, which is very important. So I am not alone.

I was thinking that if the iso is copied to a FAT32 partition, it can easily be replaced without reinstalling with mkusb, With new versions the info in casper-rw needs to be deleted. This is the menuentry I used:

menuentry "ubuntu.iso" {
set root=(hd0,4)
loopback loop /ubuntu.iso
linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/ubuntu.iso noeject noprompt -- persistent
initrd (loop)/casper/initrd.lz

I will confirm later when my mother-n-law gets off that computer. OK> Dus is looking good but when it is done I hope you re-name it "mkusb II", or "son-of-mkusb", mkusb is getting a pretty good rep and is gaining quite a following, Please not "new mkusb"

I see what you mean. Another alternative is simply 'mkusb version 12.x.x' (continuing after version 11.x.x). There were big changes of the user interface between the versions 7 and 8 (plain text --> dialog menus) and between the versions 8 and 9 (dialog menus --> zenity menus) too.

Image 4 is the only one that is at all a little confusing.

I see. 'c for cloning' in three cases :-P What do you suggest - just one line to clone and make installer/live-only drives? Should there be a separate line for Windows (Windows iso files are automatically detected)?

#444

I think the version 12.x.x is best

C - Clone L - Live P - Persistent W - Windows

What does Cloning do? I have been afraid to try it. Can I use it to clone home folders and partitions?

Other than that everything is quite intuitive and fast, did I see during install that it was still only about 3.5MB?

#445

*I will make a new menu according to your suggestion.* C, L and W will lead the user the same way, but it is less confusing :-)

Cloning is what is used to create the standard live-only drives from iso files (each byte is copied as is from the iso file to the target block device). dd is doing this job under the hood.

[Expansion of a compressed image and] cloning is used to flash image files to installed systems. This is the standard method to install systems into mobile phones and various devices, for example Raspberry Pi. I use it to install 'my' UEFI-and-BIOS installed systems into pendrives, memory cards, SSDs or HDDs.

Yes, dus is quite small, only a few bash shell-scripts. It uses standard tools, that come with the standard linux systems, and adds a few, that should be available in the standard repositories, if not already installed, for example zenity and pv.

#446

Hello,

I've created usb flash live persistent ubuntu 16.04 install from iso with Unetbootin tool + some manual config tweaks on 16gb flash stick. And now my current grub.cfg entries looks like:


menuentry "Ubuntu 16.04" {
    set gfxpayload=keep
    linux    /casper/vmlinuz.efi  file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash persistent --
    initrd    /casper/initrd.lz
}

menuentry "Ubuntu 16.04 to RAM" {
    set gfxpayload=keep
    linux    /casper/vmlinuz.efi  file=/cdrom/preseed/ubuntu.seed boot=casper toram quiet splash persistent --
    initrd    /casper/initrd.lz
}

So the first one is for simple persistant boot and the second is for boot to ram. So the problem with the 1st is that it's very laggy with write operations on flash stick so I was intended to fix it with the "toram" parameter in the 2nd entry. But then I use 2nd - It looks like it works - I see increased RAM consumption - but in fact "toram" variant turned to be MUCH MORE laggy than 1st.

How can It be? Can I fix it?

#447

I know too little about your computer to give a good answer. Please specify your computer

  • Brand name and model
  • CPU
  • RAM (size)
  • graphics chip/card
  • wifi chip/card

Before knowing more I can only guess - maybe your system is swapping, maybe your system has problems with the graphics, maybe there is some other problem.

-o-

If the slowness only affects writing to the pendrive, you should consider this:

It is typical that the startup is slower with 'toram', but after that it should be more responsive, provided that there is enough RAM. But you must understand what is pushed 'to RAM': the programs of the Ubuntu system. If you write to the pendrive it has to be written to the pendrive's hardware (it may be cached, but sooner or later it must be written), and 'toram' does not make the flash memory hardware faster. The best solution is to get a fast USB 3 pendrive (even if you only have USB 2 ports in the computer). See this link and links from it,

FromUSBStick#Notes_about_speed

#448

sudodus said: But you must understand what is pushed 'to RAM': the programs of the Ubuntu system. If you write to the pendrive it has to be written to the pendrive's hardware (it may be cached, but sooner or later it must be written),

I was thinking that during work process system with "toram" option store all changes in RAM and writes it to casper virtual partition only on system shutdown. Am I wrong?

#449

Well, I tested by copying a lubuntu iso file (approx. 0.9 GB) to an external drive (USB) with *pv*, progress view.

It copied 71 % quickly (obviously to RAM), but then is was much slower (and it started writing, the target drive's LED flashed). The *pv* process finished after a fairly short time, and it took a long time to finish *sync*. There was no swapping (I had enough RAM, 4 GB, and slightly more than 1 GB was used, as indicated by *htop*).

-o-

The answer to your question is that at least the system implemented via the 'toram' boot option starts writing before the RAM is full and does not wait until shutdown.

Maybe the system by *terminator14* at this link would work more like you would like it to work.

#450

One thing I have found running in RAM is that it takes about the same time to boot a program the first time but is considerably faster following times.

#451

So is there any working method for my scheme? I mean to load OS and home partition fully in RAM from fllash drive on system boot and sync it back only on system shutdown? To exclude any slow write/read operations during work process like it is on typical live usb flash boot + sync to usb drive.

#452

Sounds like Puppy Tahr which is based on Ubuntu 14.04.

#453

[SIZE=4]mkusb and mkusb-nox version 11.1.7[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table]

  • mkusb: fixed bug for 100% persistence: using 'ntfssize' in mkusb (and dus-persistent 0.0.1)

. more colours in the console: (alongside green, red and inversevideo) now also blue for programs that dus 'wants' .menu entries to dus-live as separated into c,l,w to be less confusing:

  • dus 0.0.1

c - Clone l - Live p - Persistent w - Windows

The changes of the interface are illustrated with the attached screenshots with colour codes according to this table,

[TABLE="class: cms_table"] [tr][td="bgcolor: #ebeceb"]Interfaces:[/td][/tr] [tr][td]zenity menu[/td][/tr] [tr][td="bgcolor: #3580ca"][color="beige"]dialog menu[/color][/td][/tr] [tr][td="bgcolor: #2b2c2b"][color="#ffffff"]plain text interface[/color][/td][/tr] [tr][td="bgcolor: #ebeceb"]Console colour codes:[/td][/tr] [tr][td="bgcolor: #2b2c2b"][color="#ffffff"]standard text[/color][/td][/tr] [tr][td][color="#2b2c2b"]general high-light[/color][/td][/tr] [tr][td="bgcolor: #afd700"]'logo colour'[/td][/tr] [tr][td="bgcolor: #0000dd"][color="#ffffff"]dus 'wants'[/color][/td][/tr] [tr][td="bgcolor: #dd0000"][color="#ffffff"][b]dus 'needs' and error messages[/b][/color][/td][/tr] [tr][td="bgcolor: #00bb00"][color="#ffffff"]Done [noparse]:-)[/noparse][/color][/td][/tr] [/table]

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get the test version dus (with guidus) via the following additional commands

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb and mkusb-nox version 11.1.7 are copied to the stable PPA after further testing in all current versions of Ubuntu.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#454

[SIZE=4]Upgrade mkusb[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] If you upgrade mkusb: remove the old version before installing mkusb version 11.1.7 [/td][/tr][/table]

Because of a new structure of the mkusb PPA with 'common packages', you may need to remove the old mkusb package before it will work correctly to install new versions, to 'upgrade' mkusb. This is only a temporary problem until the new structure of mkusb 11.1.7 is installed (you need do it only once).

We assume that you have the PPA repository already. Then the following command should do what you want,

sudo apt-get remove mkusb  # remove the old version of mkusb with its set of files and directories

sudo apt-get update
sudo apt-get install mkusb mkusb-nox usb-pack-efi
#455

Sorry I have been busy with "Life" ...But Thanks sudodus for my Go to Tool for Testing purpose's. Regards

#456

1fallen said: Sorry I have been busy with "Life" ...But Thanks sudodus for my Go to Tool for Testing purpose's.

Regards

Hi 1fallen,

Did you notice the revamped user interface, *made simpler in several ways* (you may like some and dislike some of them), now called *dus* and *guidus*? Have a look at post #439, try them (guidus is a 'thin front end' for dus) and tell me what you think. What you say is important :-)

[hr][/hr] [COLOR="#494949"]As usual for testers:

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get the test version dus (with guidus) via the following additional commands

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

#457

sudodus said: Hi 1fallen,

Did you notice the revamped user interface, *made simpler in several ways* (you may like some and dislike some of them), now called *dus* and *guidus*? Have a look at post #439, try them (guidus is a 'thin front end' for dus) and tell me what you think. What you say is important :-)

[HR][/HR] [COLOR=#494949]As usual for testers:

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get the test version dus (with guidus) via the following additional commands

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net I agree with C.S.Cameron to keep or add the toggle so that dd can copy the .iso file to a read/write FAT32 partition instead, if desired. I am going to do some testing on this today an tommorow...so I will add more when finished. But Please Note "I" may not be as fusy as some others...just grateful for a working solution to fit my needs. And this has replaced everything (Other tools I used to use) that I need to do. Much Appreciated.:D

#458

*The main reason for dus is to make things simpler* compared to mkusb and mkusb-nox, for the end user as well as for the maintainer.

Dus has a unified user interface, but the executing parts are separate batch files. It will be easy to add a new executing part (and modify the user interface for it).

Dus can clone live-only drives and create systems in read/write partitions (persistent live drives for linux and install drives for Windows). This is the same as with mkusb and mkusb-nox.

I have an 'extractor' that can extract iso files to a single read/write partition, a stand-alone program in the pipeline, which might be attached to dus too. This is something that the current mkusb and mkusb-nox cannot do (except the special case for Windows).

The dus interface can work as a GUI with zenity, as a text menu interface with dialog (like mkusb version 8) and with a simple text interface (like mkusb 1-7 and mkusb-nox). So the same program can work in desktops, laptops but also in servers, other systems without graphics and via ssh.

-o-

These features are removed (not available in dus),

  • Automatic identification for iso-testing (with the blue background at the final checkpoint).
  • Advanced options in the wipe menu
  • The help menu and the overview window
  • The fancy graphics using the webkit extension in zenity (the --html option)
  • The hidden console (going back to a naked console window)

There are several reasons why these things are removed. I am open for feedback and ready for discussion. Maybe you have good arguments why some of these simplifying steps should be reversed.

-o-

I intend to create a manual page and an 'about' window/screen.

#459

The only thing that I could find..is Selecting a Color back-ground kept kicking me back to select another color after selecting the color that I wanted. But the working parts IE: Help to select drive, Flow, Manual page, Wiki page, Tweak zenity window size, About, And Quit...All worked as expected. So other than the Background colours...I found nothing else to point out. Screenshots Included for the Background colours Issue I ran into. Regards

#460

Thanks for testing, 1fallen :-)

I will look into the tool to select a colour background and try to fix it. (It was broken by an upgrade of zenity, and I thought it was working again after a fix, but obviously I did not manage to get it working all the way.

  • Which version of zenity are you running (in Arch)?

-o-

Now to a couple of important general questions:

  • Did you try any more than the first quick check of the revamped interface: dus with guidus?
  • Do you think it is good or bad to remove those features (listed in my previous post)?
#461

sudodus said: Thanks for testing, 1fallen :-)

I will look into the tool to select a colour background and try to fix it. (It was broken by an upgrade of zenity, and I thought it was working again after a fix, but obviously I did not manage to get it working all the way.

  • Which version of zenity are you running (in Arch)?

-o-

Now to a couple of important general questions:

  • Did you try any more than the first quick check of the revamped interface: dus with guidus?

Your Welcome glad to be of help.:smile:

  • Do you think it is good or bad to remove those features (listed in my previous post)?
  • Which version of zenity are you running (in Arch)?

This was the same behaviour in both Arch and Ubuntu 16.04 zenity:On Ubuntu

apt policy zenity
zenity:
  Installed: 3.18.1.1-1ubuntu2
  Candidate: 3.18.1.1-1ubuntu2
  Version table:
 *** 3.18.1.1-1ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

And on Arch:

pacman -Q zenity
zenity 3.22.0+1+gcd1647c-1
  • Did you try any more than the first quick check of the revamped interface: dus with guidus?

Yes I did and I was glad for this addition (Useful)..I would think this would be favorable to most users of ''mkusb.

  • Do you think it is good or bad to remove those features (listed in my previous post)?

I'm kind of on the fence on this.. my friend...and to be honest I have not thought about what it would be like with or with out them (At least for my use).:confused: But I trust you will make the right decision here. (I know I'm not a lot help here ;)) Just don't break it...I've grown to like this little tool a LOT!:lolflag: Best Regards

#462

Thanks again for your feedback, 1fallen. It helps making the right decision :-)

#463

Mkusb and Puppy Tahr

Not a lot of people know that mkusb will make a good base for a Puppy install.

  1. Start mkusb, select persistent, select Puppy iso as source, select target device, ignore warnings about unsupported O/S.
  1. When mkusb is complete replug flash drive and open gparted.
  1. Remove the -rw label on partition 5, close gparted.
  1. Open grub.cfg, the following worked:
set default="1"
set timeout=10
if loadfont /boot/tools/fonts/unicode.pf2 ; then
set gfxmode="640x480"
insmod gfxterm
insmod vbe
terminal_output gfxterm
if terminal_output gfxterm; then true ; else
terminal gfxterm
fi
fi
insmod tga
if background_image /boot/tools/images/bg.tga ; then
set color_normal=blue/black
set color_highlight=red/black
else
set color_normal=white/black
set color_highlight=white/light-gray
fi

GRUB_GFXMODE=1024x768x16
insmod vbe

menuentry "Puppy Tahr" {
set root=(hd0,4)
linux /vmlinuz psavemark=5
initrd /initrd.gz
}
  1. When shutting down after first boot, Save, select partition 5 of the flash drive, (sdb5?) for the save partition.

A iso install is also possible.

#464

Thanks for sharing this solution for Puppy Tahr, C.S.Cameron :-)

#465

1fallen said: The only thing that I could find..is Selecting a Color back-ground kept kicking me back to select another color after selecting the color that I wanted.

I tested it in my updated main computer with Lubuntu 16.04.1 LTS and zenity version

zenity:
  Installerad: 3.18.1.1-1ubuntu2
  Kandidat:    3.18.1.1-1ubuntu2
  Versionstabell:
 *** 3.18.1.1-1ubuntu2 500
        500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status

and it works for me. I could make a new colour for the final checkpoint when making a standard live drive as illustrated with the attached screenshot.

Did you notice that there are colours for three different 'occasions' that are to be modified (or accepted as they are) in sequence:

  • making standard live drives and wiping (standard red)
  • persistent live drives (standard orange)
  • isotesting (standard blue)

This sequence (while modifying the colours) might be confusing. Or is there a real bug, that I cannot provoke? I tested also in a live Xenial amd64 system, and it works there too.

*Edit:* I think I understand now. You are right, there is a bug: the text in the windows (and the title bars) is the same for all three instances which is confusing. I will change the text to describe correctly what it is all about.

#466

[SIZE=4]mkusb and mkusb-nox version 11.1.8[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table]

  • mkusb: fixed bug for colour selection: different text for each case

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get the test version dus (with guidus) via the following additional commands

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb and mkusb-nox version 11.1.7 are still in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#467

C.S.Cameron said: Mkusb and Puppy Tahr

Not a lot of people know that mkusb will make a good base for a Puppy install.

  1. Start mkusb, select persistent, select Puppy iso as source, select target device, ignore warnings about unsupported O/S.
  1. When mkusb is complete replug flash drive and open gparted.
  1. Remove the -rw label on partition 5, close gparted.
  1. Open grub.cfg, the following worked:
set default="1"
set timeout=10
if loadfont /boot/tools/fonts/unicode.pf2 ; then
set gfxmode="640x480"
insmod gfxterm
insmod vbe
terminal_output gfxterm
if terminal_output gfxterm; then true ; else
terminal gfxterm
fi
fi
insmod tga
if background_image /boot/tools/images/bg.tga ; then
set color_normal=blue/black
set color_highlight=red/black
else
set color_normal=white/black
set color_highlight=white/light-gray
fi

GRUB_GFXMODE=1024x768x16
insmod vbe

menuentry "Puppy Tahr" {
set root=(hd0,4)
linux /vmlinuz psavemark=5
initrd /initrd.gz
}
  1. When shutting down after first boot, Save, select partition 5 of the flash drive, (sdb5?) for the save partition.

A iso install is also possible.

+1:D I have used a similar method also. But I like this one. With an .iso install...works a treat. Thanks for the share

#468

sudodus said: I tested it in my updated main computer with Lubuntu 16.04.1 LTS and zenity version

zenity:
  Installerad: 3.18.1.1-1ubuntu2
  Kandidat:    3.18.1.1-1ubuntu2
  Versionstabell:
 *** 3.18.1.1-1ubuntu2 500
        500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status

and it works for me. I could make a new colour for the final checkpoint when making a standard live drive as illustrated with the attached screenshot.

Did you notice that there are colours for three different 'occasions' that are to be modified (or accepted as they are) in sequence:

  • making standard live drives and wiping (standard red)
  • persistent live drives (standard orange)
  • isotesting (standard blue)

This sequence (while modifying the colours) might be confusing. Or is there a real bug, that I cannot provoke? I tested also in a live Xenial amd64 system, and it works there too.

*Edit:* I think I understand now. You are right, there is a bug: the text in the windows (and the title bars) is the same for all three instances which is confusing. I will change the text to describe correctly what it is all about.

Thank You;)...And not like this was a show stopper by any means. And just to add this...I really like the new text windows in both guidus and mkusb. I'm impressed!:KS

#469

I have had a problem canceling mkusb several times, If I hit cancel on the first screen or two, it continues on to the next screen and the next.

#470

Please describe exactly which screen and I will look into it and try to fix the problem.

#471

I was just testing it, When I try to X out of mkusb 11.1.8, the program keeps going to the next panel. It closes if I hit cancel. I tried it on two computers. It stops by itself after the mkusb console window. Not a big deal, but could panic a novice, (not that it scared me).

#472

Which window? There are windows where the cancel button is given another function, for example to show the 'About' information or the man page 'man mkusb'. Is this the problem? If you find it confusing, I can change that behaviour :-)

But maybe it is another problem, that I don't quite understand yet. Which distro, version and flavour is the host system, where you run mkusb?

#473

It only happens if I hit the X in the upper left corner of the window, Cancel works OK. One computer is a HP EliteBook 8560w, 24gb RAM. It is booting from a 128GB Lexar USB3 made using mkusb, it is running 16.04 that I installed 11.1.8 to. The other computer is an old Acer with 8GB RAM running 14.04 only, using 11.1.5.

#474

Is it happening in one particular window, in that case, what is the title of the window?

I guess that you mean that it happens in Ubuntu 14.04 and 16.04, and in 11.1.5 and 11.1.8.

I will look for it ...

#475

mkusb version 11.1.9 is waiting for testing. It is only uploaded to phillw.net and to the *unstable* repository of *xenial* (until tested).

#476

X Welcome window X About window X Man window X Starter Menu window X Check Zenity Error window X Console window Then it closes.

Apple would probably call this a feature.

#477

Yes, I think it *was* a feature, a 'guided tour' :-P Now it is removed (at least from the windows in the main work flow). Did you check in mkusb version 11.1.9, that it works better?

And by the way, the work flow is much simpler in the new version, now called 'dus'. Please compare mkusb and dus.

#478

And just to show some of the changes. guidus should show as screenshot 1 and mkusb sceernshots2 & 3

#479

If I type "dus" in Unity I don't see it, I got to launch it from nautilus. and then the nautilus window stays open while dus runs.

#480

*guidus* is the front end with a desktop file, which makes it work from Unity's dash or the menu of other desktop environments. The following commands,

sudo add-apt-repository universe
sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install guidus

will install guidus and it will bring dus and the 'necessary' program packages. The usb-pack-efi package may be installed separately.

#481

[SIZE=4]Easy way to get an installed system and persistent live system in the same 32 GB pendrive[/SIZE]

I played a little with *dus* and our new method to install 'into the same USB pendrive' :-)

The previous tests were made with Ubuntu 16.04.1 LTS 64-bit and a cloned live-only pendrive. This time I tried Lubuntu 16.04.1 LTS 32-bit and

  • started from a persistent live pendrive, but booted it live-only to RAM (removed persistent from the 'toram persistent' option).
  • unmounted the mounted partitions (with umount, not eject).
  • reduced the size of the usbdata partition.
  • started the installer and this time selected 'Something else' at the partitioning window.
  • selected the unallocated space for the root partition '/'. I did not select any swap partition (optional).

When the installation finished, I

  • 'continued testing', and flushed the buffers with sync.

After reboot I

sudo update-grub

  • copied the grub.cfg of the persistent live system to /etc/grub.d/40_custom
  • edited /etc/default/grub to make it display at boot
  • and ran ```

to get the tweaks into the grub.cfg file of the installed system.

It works, and I can boot an installed system, a live system and a persistent live system :-)

See the attached screenshots and if you are really interested, grab the attached tarball to see the tweaked grub files

$ tar -tvzf grub-files.tar -rw-r--r-- root/root 1205 2016-12-01 15:12 etc/default/grub -rwxr-xr-x root/root 1485 2016-12-01 14:29 etc/grub.d/40_custom -r--r--r-- root/root 8603 2016-12-01 15:13 boot/grub/grub.cfg



-o-

This pendrive is rather portable as long as no proprietary drivers are installed, but this particular set-up was made such that the installed system only boots in BIOS mode. But the persistent live system boots in UEFI mode too. It is probably straightforward to add the installed system to the grub.cfg of the persistent live system and make it boot in UEFI mode too, but the main purpose was to get an  'installed + persistent live combo pendrive'.
#482

Installing mkusb from a Windows machine?

Too bad mkusb can not be run from Windows, it is so much better than Rufus, UNetbootin, SDC, etc. Windows has problems seeing multiple partitions on a flash drive. Windows has problems seeing filesystems other than FAT and NTFS. But wait, Ubuntu can be installed from Windows as a Live system using one of the above tools. As in above post, the flash drive can be booted with the "toram" option. Mkusb and a Ubuntu iso can then be downloaded. The pendrive is then unmounted, Mkusb can then be used to make a persistent install to the original pendrive.

This process could probably be automated in a Windows version of mkusb/dus.

#483

Interesting :-) Yes, several of these step could probably be automated.

There is a work-around, that would make it easier. The end user need only install from a compressed image file with the target system 'ready made'. This can be done *in Windows*,

  1. Download a compressed image file.
  1. Check the file with *md5summer*
  1. Expand the compressed image file *7-zip*,

4. Clone/flash/install the image file with *Win32 Disk Imager* to a target drive, typically a USB pendrive.

See this link: Win32DiskImager/iso2usb

I think this approach is the most straight-forward one. Do you think it is worthwhile to provide such an image with a persistent live system (with mkusb/dus installed)?

#484

There are a few sites out with there with open source images for VBox, mostly older versions. I see the Ubuntu site has .img files for Server, but I don't see any for Desktop.

I doubt that anyone has .img files for a persistent mkusb type install... yet.

I haven't played with image files since we last discussed it, quite a few years ago. Can Image Writer handle mulltiple flash drive partitions on a Windows machine? (I bricked two multipartition flash drives once trying to format them in Windows). I don't recall needing to decompress the .img file the last time I used Image Writer.

I really like a mkusb install, I think people would use it, If you make an image I will test it.

I am at present working off of a Puppy flash drive I mostly made with mkusb, (puppy does allow multiple persistent partitions). Vbox does not run off it as fast as I expected though.

#485

How would you like the image?

*- Size*

Should I make a tailor made image for a particular pendrive size (in that case which size), or a small image, 8 GB, with partitions to be expanded with gparted afterwards?

*- Version and flavour of Ubuntu*

I suggest either the 16.04.1 LTS or the daily Xenial iso file with the proposed repository turned off for stability. Which one would you suggest?

I suggest standard Ubuntu 64-bit, and Lubuntu 32-bit as a light alternative, so two images.

*- Partition table*

What about an MSDOS or a GUID partition table (GPT)? GPT works with huge drives (> 2 TB), MSDOS is needed for some middle-aged HP computers to boot.

I think you want a casper-rw partition and a live-rw partition. What about a usbdata partition with NTFS? And what about the relative sizes of these partitions?

#486

sudodus said: *guidus* is the front end with a desktop file, which makes it work from Unity's dash or the menu of other desktop environments. The following commands,

sudo add-apt-repository universe
sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install guidus

will install guidus and it will bring dus and the 'necessary' program packages. The usb-pack-efi package may be installed separately.

@sudodus,

Just leave it the way it is! The console on the left-top in unity7 desktop (16.04amd64) is just beautiful .. the theme and everything. Don't put any toggles in it. Just my suggest. I would rather use guidus than mkusb because it is easier on my eyes and I do not have to fanaggle with toggling. So , since there are other options with mkusb (toggling .. etc..) leave guiusb for users who just want to do USB stuff!! :)

Regards..

#487

@ ventrical,

Do you mean that you found no bugs in guidus (and dus) - not even any wishlist bugs :-P

The intention is that it should be easier to use (and easier to maintain), but anyway. What about the name - do you think it is a good idea to let it replace mkusb? In other words, to rename it and let it be mkusb version 12. This is what C.S.Cameron thinks. He has spent a lot of time to make the mkusb 'trademark' known via AskUbuntu. Also other people think that I should keep the name mkusb. And now I want to hear your opinion.

(There have been major revamps of the user interface of mkusb before: from mkusb 7 (plain text which is still used as mkusb-nox) to mkusb 8 (with 'dialog' menus in text mode), and from mkusb 8 to mkusb 9 (with the current 'zenity' menus, that you have helped me to polish).

#488

I have to agree with ventrical...why mess with perfection.:D Seriously I think it is good as is. Now watch all the critics come out....:p

#489

sudodus said: @ ventrical,

Do you mean that you found no bugs in guidus (and dus) - not even any wishlist bugs :-P

The intention is that it should be easier to use (and easier to maintain), but anyway. What about the name - do you think it is a good idea to let it replace mkusb? In other words, to rename it and let it be mkusb version 12. This is what C.S.Cameron thinks. He has spent a lot of time to make the mkusb 'trademark' known via AskUbuntu. Also other people think that I should keep the name mkusb. And now I want to hear your opinion.

(There have been major revamps of the user interface of mkusb before: from mkusb 7 (plain text which is still used as mkusb-nox) to mkusb 8 (with 'dialog' menus in text mode), and from mkusb 8 to mkusb 9 (with the current 'zenity' menus, that you have helped me to polish).

I am only giving a first impression. I am downloading zesty/current now and will use guidus to create USB image.

You have two different sets. One set is guidus and the other is mkusb. Why can't we just leave the choice up to the end_user what to install? We have to keep in mind that graphical user interfaces create options for theming. We mostly interact with our computers by what we see on the output peripherials like video. For some reason (perhaps just by chance) the way you have the (echo) terminal set up in left justified, dark background and highlighted with terminal green (which is how I started out with UNIX several decades ago) . Also there is that soft border buffer to the right which gives the terminal some graphical elegance and is easier to look at. (eye-candy) :) So there are certain ways of theming our applications that can enhance the end_user experience and make the overall experience more intuitive. guidus does not provide too much room for guessing games and therefore less chance of making mistakes etc.. On the otherhand we can make our programs more forensic to look at and this type of forensic theming (which is happening with unity7 and unity8-desktop) discourages people to work the application. It just becomes more frustrating .. even for wizards..:)

Regards..

#490

1fallen said: I have to agree with ventrical...why mess with perfection.:D

Seriously I think it is good as is. Now watch all the critics come out....:p

Thanks 1fallen for the backup on this. This is what has happened to some of the other desktop apps. They have become so forensic to work with and the help - alongs are few and far between. We can't just keep theming ubuntu apps for geeks, nerds and cli junkies. We have to embrace the other end_users out there who really do not understand what is going on in the background. Theming can be done to create a nostalgia, an effervescence so to speak and a large continuum of end_users are status quo for effervescence and nostalgia. So .. you're right .. why ruin a good thing "mess with perfection". It's just becomes a bunch of more counter-productive downtime.

Regards..

#491

One reason is that many people will stay with what they know. They will continue with mkusb, and will not find dus. But I see your point, different tools suit different people. guidus might be better for some people, and mkusb (as it is now, version 11) is better for other people.

Am I understanding correctly, that you think guidus is easier to use, but not good-looking enough - the crude console window might scare people - and should be hidden like in mkusb?

#492

Using the crude console window makes the programming much simpler - this is one reason. Also, it gives the user a more direct feedback, if something goes wrong, something that I did not foresee, and it will be easier to debug (help the user and if possible improve the program). But it must not scare the typical end user.

#493

sudodus said: Using the crude console window makes the programming much simpler - this is one reason. Also, it gives the user a more direct feedback, if something goes wrong, something that I did not foresee, and it will be easier to debug (help the user and if possible improve the program). But it must not scare the typical end user.

...sigh...

Obviously you are not reading my replies..

@sudodus,

Just leave it the way it is! The console on the left-top in unity7 desktop (16.04amd64) is just beautiful .. the theme and everything.

#494

OK, now I am sure. I thought that maybe you were joking about 'retro' style for oldtimers who grew up with consoles. Thanks for your feedback, ventrical. I really appreciate it :-)

#495

sudodus said: OK, now I am sure. I thought that maybe you were joking about 'retro' style for oldtimers who grew up with consoles. Thanks for your feedback, ventrical. I really appreciate it :-)

Well .. it's no secret that I am an oldtimer :) and as I said .. (as you say retro-style) .. yes .. that works for me but my main point (I guess) is that the terminal *theme* is easier for me to understand plus you have added other notifications which come up in the terminal which are a little more informative as the guidus application is running through it's algorithms.

Regards..

ventrical..

#496

Putting up 2 links to videos I made. Hope they are helpful.

[URL="https://youtu.be/S2Jpkm6r7n8"]https://youtu.be/S2Jpkm6r7n8

https://youtu.be/tKrBiK32_RM

[/URL]

#497

ventrical said: Putting up 2 links to videos I made. Hope they are helpful.

[URL="https://youtu.be/S2Jpkm6r7n8"]https://youtu.be/S2Jpkm6r7n8

[/URL]https://youtu.be/tKrBiK32_RM

Hey Good Job eh?:popcorn:

#498

I have limited Internet consumption here, 20GB/mo, smaller the better for testing, I have a free 4gb and 8gb drive.

#499

Well we have mkusb & mkusb-nox, why not mkusb-dus? they all make USB.

#500

C.S.Cameron said: Well we have mkusb & mkusb-nox, why not mkusb-dus? they all make USB.

Yeah.. that will work. Good point.

Regards..

#501

C.S.Cameron said: There are a few sites out with there with open source images for VBox, mostly older versions.

I see the Ubuntu site has .img files for Server, but I don't see any for Desktop.

I doubt that anyone has .img files for a persistent mkusb type install... yet.

I haven't played with image files since we last discussed it, quite a few years ago. Can Image Writer handle mulltiple flash drive partitions on a Windows machine? (I bricked two multipartition flash drives once trying to format them in Windows). I don't recall needing to decompress the .img file the last time I used Image Writer.

I really like a mkusb install, I think people would use it, If you make an image I will test it.

I am at present working off of a Puppy flash drive I mostly made with mkusb, (puppy does allow multiple persistent partitions). Vbox does not run off it as fast as I expected though.

sudodus said: How would you like the image?

*- Size*

Should I make a tailor made image for a particular pendrive size (in that case which size), or a small image, 8 GB, with partitions to be expanded with gparted afterwards?

*- Version and flavour of Ubuntu*

I suggest either the 16.04.1 LTS or the daily Xenial iso file with the proposed repository turned off for stability. Which one would you suggest?

I suggest standard Ubuntu 64-bit, and Lubuntu 32-bit as a light alternative, so two images.

*- Partition table*

What about an MSDOS or a GUID partition table (GPT)? GPT works with huge drives (> 2 TB), MSDOS is needed for some middle-aged HP computers to boot.

I think you want a casper-rw partition and a live-rw partition. What about a usbdata partition with NTFS? And what about the relative sizes of these partitions?

C.S.Cameron said: I have limited Internet consumption here, 20GB/mo, smaller the better for testing, I have a free 4gb and 8gb drive.

The size of the compressed image file is almost independent of the size of the extracted system. So this is a choice between providing a system that is ready for a 16 GB or 32 GB drive, or to provide a system for a smaller drive and expect the end user to move and expand partitions with gparted afterwards to use the whole drive.

Of course, this must not be the 'final product', only a prototype for testing, and for that purpose it should with 4 GB.

#502

ventrical said: Putting up 2 links to videos I made. Hope they are helpful.

[URL="https://youtu.be/S2Jpkm6r7n8"]https://youtu.be/S2Jpkm6r7n8

https://youtu.be/tKrBiK32_RM

[/URL]

Nice videos :-)

#503

C.S.Cameron said: Well we have mkusb & mkusb-nox, why not mkusb-dus? they all make USB.

And/Or give the user a choice when starting via mkusb.desktop (so via dash and menus), a choice that will be remembered and pre-selected the next time the desktop file is started?

#504

it is just so much simpler for me to :


sudo apt-get install guidus

:)

#505
espeak 'sudo apt-get install guidus'

sounds better than

espeak 'sudo apt-get install mkusb'

but there is also the history of mkusb, so maybe it is best to have both names alongside each other and 'let the market decide' which to use.

#506

Mkusb is a name people have grown to trust and respect, having mkusb in the name adds a level of confidence to the product. I like the idea of giving the user a choice, but there should be a way to reset, just in case they want to try the other installer.

4GB is good, I'm getting pretty quick at modifying partitions. I have been using gparted in Puppy it is pretty fast and seems to ask less questions than in Ubuntu.

I plan on starting to play with grub-n-iso tomorrow anything new with it?

#507

C.S.Cameron said: Mkusb is a name people have grown to trust and respect, having mkusb in the name adds a level of confidence to the product.

I like the idea of giving the user a choice, but there should be a way to reset, just in case they want to try the other installer.

I will try to find a solution, that will be inclusive :-)

4GB is good, I'm getting pretty quick at modifying partitions. I have been using gparted in Puppy it is pretty fast and seems to ask less questions than in Ubuntu.

OK, I can start making and testing a compressed image of a 4 GB persistent live system with mkusb and guidus installed. Maybe I can upload it tomorrow.

I plan on starting to play with grub-n-iso tomorrow anything new with it?

No, nothing new, but I helped a user to create a multiboot with 2 iso files yesterday according to Post #8 of the tutorial for grub-n-iso 'Build your own single boot or multiboot pendrive for all PC (Intel/AMD) computers'. It works :-)

#508

A persistent live drive by and with dus or mkusb booted with the toram boot option can use partition #4 (the image of the original iso file) to create a new live system (in another drive).

You should specify the source file /dev/sdx4.

See the attached screenshot, where the boot drive is recognized as drive letter b, so /dev/sdb4 (high-lighted with the orange dots).

I checked the target drive for defects. 'Check finished: no errors found', and the target drive is happy to boot.

-o-

*Edit:* dus (and guidus) finds and offers a *quick choice* of partition #4 (the image of the original iso file) to create a new live system (in another drive). Since it has the ISO 9660 file system, which is read-only, it need not be unmounted, so you need *not* boot with toram. There is built-in logic to check it. See the second attached screenshot.

#509

That is really handy, no more scampering around at the last minute looking for an iso file like with the other installers. stands to reason as it is a clone of the iso.

#510

sudodus said:

but there is also the history of mkusb, so maybe _it is best to have both names alongside each other and 'let the market decide' which to use._ That works for me!:KS

#511

I seem to have an issue with getting and installing *mksub*.

hugh@8930:~/Downloads$ sudo apt install mkusb mkusb-nox
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package mkusb
E: Unable to locate package mkusb-nox
hugh@8930:~/Downloads$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

Is the universe repository available?

#512

him610 said: I seem to have an issue with getting and installing *mksub*.

hugh@8930:~/Downloads$ sudo apt install mkusb mkusb-nox
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package mkusb
E: Unable to locate package mkusb-nox
hugh@8930:~/Downloads$ lsb_release -a
No LSB modules are available.
Distributor ID:    Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:    16.04
Codename:    xenial

Is the universe repository available?

Hi,

Have you tried this yet?

Works on all my computers.

#513

him610 said: I seem to have an issue with getting and installing *mksub*.

hugh@8930:~/Downloads$ sudo apt install mkusb mkusb-nox
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package mkusb
E: Unable to locate package mkusb-nox
hugh@8930:~/Downloads$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

Is the universe repository available?

bearlake said: Hi,

Have you tried this yet?

Works on all my computers.

Yes, him610, there is a detailed description in bearlake's link. I will write the details here to make it easier to find:

  1. You need the mkusb PPA in order to install mkusb.
  1. Yes, the universe repository is available, but must be activated in standard Ubuntu.

So try with the following sequence of commands in a terminal window:

-o-

If you run standard Ubuntu, you need an extra instruction to get the repository Universe. (Kubuntu, Lubuntu ... Xubuntu have the repository Universe activated automatically.)

sudo add-apt-repository universe  # only for standard Ubuntu
sudo add-apt-repository ppa:mkusb/ppa  # and press Enter
sudo apt-get update
sudo apt-get install mkusb mkusb-nox usb-pack-efi
#514

[SIZE=4]Test version of a compressed image file of a '4GB' persistent live system[/SIZE]

C.S.Cameron said: 4GB is good, I'm getting pretty quick at modifying partitions. I have been using gparted in Puppy it is pretty fast and seems to ask less questions than in Ubuntu.

[COLOR="#696969"]I uploaded an early test version of a '4GB' compressed image file. You find it via this link,

uefi-n-bios/dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test0.img.xz [/COLOR] *Edit:* I uploaded an improved test version of a '4GB' compressed image file. You find it via this link,

uefi-n-bios/dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz

Here are the size and md5sum of the compressed image file.

$ ls -l dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz
-rw-r--r-- 1 sudodus sudodus 1599526076 dec  6 10:20 dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz

$ md5sum dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz
135970e593e59c311f0f0f7690f50424  dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz

[SIZE=4]Tips for new users[/SIZE]

*[SIZE=3]In linux[/SIZE] mkusb, mkusb-nox, guidus and dus* can install a persistent live system from this image file.

*[SIZE=3]In Windows[/SIZE]* you can expand the file with *7-zip* and after that install alias 'write' it with *Win32 Disk Imager*.

[SIZE=4]Description[/SIZE]

It works to run this system in a pendrive or memory card as it is, but the intention is to install it in a fast USB 3 pendrive or fast memory card with at least 16 GB and then move and expand the partitions to use the whole drive. The following link describes the slightly different case with an installed system, but should help a beginner to move and expand, 'grow', partitions with *gparted*.

  • a first test file 'test0' and not intended for regular use
  • smaller than 4 GB to fit also in 'undersized' pendrives and memory cards (which are smaller than the nominal size)
  • MSDOS partition table to boot also in middle-aged HP computers
  • an extra partition compared to the standard made by mkusb and dus: a home-rw partition
  • Ubuntu 16.04.1 LTS 64-bit operating system
  • mkusb and dus (with guidus) installed
  • works in UEFI and BIOS mode booted from USB (both pendrive and card via USB adapter tested in three computers)
  • works in BIOS mode booted from the SD card slot in my NUC 6i3SYH
  • does not boot in UEFI mode from the SD card slot in my NUC 6i3SYH (lacks some drivers)

uefi-n-bios/GrowIt.pdf

Please try it and tell me what needs to be improved :-)

*Edit:* You find details of the partitioning in the following copy of some terminal window commands and the output from them, and in the screenshot of gparted, when booted in UEFI mode from a 4 GB SD card via a USB adapter.

ubuntu@ubuntu:~$ [COLOR="#0000FF"]**sudo lsblk -fm**[/COLOR]
NAME   FSTYPE   LABEL                    UUID                                 MOUNTPOINT               NAME     SIZE OWNER GROUP MODE
sda                                                                                                    sda    232.9G root  disk  brw-rw----
&#9500;&#9472;sda1 vfat     EFI                      274B-0C82                                                     &#9500;&#9472;sda1   300M root  disk  brw-rw----
&#9500;&#9472;sda2                                                                                                 &#9500;&#9472;sda2     1M root  disk  brw-rw----
&#9500;&#9472;sda3 ext4     root                     864c54c6-961a-4ad9-8c23-35eb8e0f24fb                          &#9500;&#9472;sda3   100G root  disk  brw-rw----
&#9492;&#9472;sda4 swap                              b69324e1-cab0-459c-97f3-bb42926ee94e [SWAP]                   &#9492;&#9472;sda4     5G root  disk  brw-rw----
sdb                                                                                                    sdb      3.7G root  disk  brw-rw----
&#9500;&#9472;sdb1 ntfs     usbdata                  65274DEC6903A569                     /media/ubuntu/usbdata    &#9500;&#9472;sdb1   384M root  disk  brw-rw----
&#9500;&#9472;sdb2                                                                                                 &#9500;&#9472;sdb2     1K root  disk  brw-rw----
&#9500;&#9472;sdb3 vfat     ubu1604164               CBD2-7CEE                            /media/ubuntu/ubu1604164 &#9500;&#9472;sdb3   122M root  disk  brw-rw----
&#9500;&#9472;sdb4 iso9660  Ubuntu 16.04.1 LTS amd64 2016-07-19-21-27-51-00               /cdrom                   &#9500;&#9472;sdb4   1.4G root  disk  brw-rw----
&#9500;&#9472;sdb5 ext4     casper-rw                04c4b799-eeff-4642-8267-a09ff3c7445a /media/ubuntu/casper-rw  &#9500;&#9472;sdb5   768M root  disk  brw-rw----
&#9492;&#9472;sdb6 ext4     home-rw                  33354151-7e7f-4fab-9e46-9df7c850deea /home                    &#9492;&#9472;sdb6   766M root  disk  brw-rw----
loop0  squashfs                                                               /rofs                    loop0    1.4G root  disk  brw-rw----
ubuntu@ubuntu:~$ [COLOR="#0000FF"]**df**[/COLOR]
Filesystem     1K-blocks    Used Available Use% Mounted on
udev             1951440       0   1951440   0% /dev
tmpfs             393216    6476    386740   2% /run
/dev/sdb4        1477840 1477840         0 100% /cdrom
/dev/loop0       1425792 1425792         0 100% /rofs
/cow              774256  199072    520136  28% /
/dev/sdb6         755656    2936    697820   1% /home
tmpfs            1966072     180   1965892   1% /dev/shm
tmpfs               5120       4      5116   1% /run/lock
tmpfs            1966072       0   1966072   0% /sys/fs/cgroup
tmpfs            1966072       4   1966068   1% /tmp
tmpfs             393216      52    393164   1% /run/user/999
/dev/sdb5         774256  199072    520136  28% /media/ubuntu/casper-rw
/dev/sdb3         122990   54699     68292  45% /media/ubuntu/ubu1604164
/dev/sdb1         393212   66056    327156  17% /media/ubuntu/usbdata
ubuntu@ubuntu:~$ [COLOR="#0000FF"]**sudo parted /dev/sdb print**[/COLOR]
Model: Generic- USB3.0 CRW -SD (scsi)
Disk /dev/sdb: 3965MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system  Flags
 3      2097kB  130MB   128MB   primary   fat32        boot
 4      130MB   1663MB  1533MB  primary
 2      1663MB  3274MB  1611MB  extended               lba
 5      1664MB  2469MB  805MB   logical   ext2
 6      2470MB  3274MB  803MB   logical   ext4
 1      3274MB  3676MB  403MB   primary   ntfs

ubuntu@ubuntu:~$ [COLOR="#0000FF"]**test -d /sys/firmware/efi/ && echo efi || echo bios**[/COLOR]
efi
ubuntu@ubuntu:~$ 

*Edit:* I created a new subpage about Win32 Disk Imager in order to help people install these compressed images from Windows,

Win32DiskImager/compressed-image_2_USB-or-SD

#515

Downloading image now.

Was playing with grub-n-iso, works good enough, possibly could store iso's on FAT32 first partition so iso's could be loaded using Linux or windows, (I'm building a drive now for a young friend who is in computer fixit school, that is what he prefers).

The only problem is that the mkusb and dus interfaces sure have me spoiled.

My wish list for dus is still to have the option to load iso files rather than make an iso clone. You could call it mkusb-dus-n-iso.

#516

I see, C.S.Cameron,

Let us think about it, and try to see what would be a good way to combine mkusb, dus and grub-n-iso.

Did you try this one? Post #49 in 'One pendrive for all PC (Intel/AMD) computers - single-boot dual-boot multi-boot':A compressed image file with a persistent live system of Lubuntu 14.04.3 LTS (32-bit) and mkusb version 10.4

It is one year old, but I could refresh it with a current iso file, and current versions of mkusb and guidus. And it might not be tested by anybody (except me), so you can expect some remaining bugs. For example, I think the first thing to do is to start an LX-terminal. After that links2check and links2update will work. Do you think it is a good starting point?

#517

I will get on it as soon as I figure grub out for a multi iso booter I am putting on an external HDD partition.

#518

my USB boot drive is not responding. Ric Flair Drip

#519

@kinghov,

*Please describe what you have, what you have done and what you want.* Otherwise it is not possible to help.

The computer:

  • Brand name and model
  • CPU
  • RAM (size)
  • graphics chip/card
  • wifi chip/card

The operating system(s):

  • distro and version
  • single boot or dual boot
  • USB drive
  • UEFi mode or BIOS mode

The tool:

  • which tool did you use to create the USB boot drive?
  • did you make a live-only drive or a persistent live drive or an installed system in the USB drive?

The file:

  • Which file did you try to install from?
  • Did you check the md5sum?

What happens, when you try to boot?

  • Please describe it with *details*.
  • Does the USB boot drive work in another computer?
  • Does another boot drive (USB or DVD) work in this computer?
#520

[SIZE=4]Test version of a compressed image file of a '4GB' persistent live system with Ubuntu[/SIZE]

I uploaded an improved test version of a '4GB' compressed image file. You find it via this link,

uefi-n-bios/dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz

Here are the size and md5sum of the compressed image file.

$ ls -l dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz
-rw-r--r-- 1 sudodus sudodus 1599526076 dec  6 10:20 dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz

$ md5sum dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz
135970e593e59c311f0f0f7690f50424  dd_Ubuntu_16.04.1-persist-live-mkusb-guidus-4GB-test1.img.xz

[SIZE=4]Tips for new users[/SIZE]

*In linux* mkusb, mkusb-nox, guidus and dus can install a persistent live system from this image file.

*In Windows* you can expand the file with 7-zip and after that install alias 'write' it with Win32 Disk Imager.

It works to run this system in a pendrive or memory card as it is, but the intention is to install it in a fast USB 3 pendrive or fast memory card with at least 16 GB and then move and expand the partitions to use the whole drive. The following link describes the slightly different case with an installed system, but should help a beginner to move and expand, 'grow', partitions with gparted.

uefi-n-bios/GrowIt.pdf

[SIZE=4]New way to select source device in guidus: 'ISO 9660 partition found. Quick choice possible'[/SIZE]

This is a very small drive, and it is also split into several partitions. There is not space enough in any of the partitions to download an Ubuntu iso file into it, but the Ubuntu system resides in partition #4 with the ISO 9660 file system. There is a *quick choice* to select it in order to install into another drive (for example another USB pendrive or memory card). If you answer 'No' you arrive at the standard tool to select source file.

See the screenshots. See also this copy of the output to the console,

 guidus - Do USB Stuff 
guidus needs superuser permissions (sudo) for some tasks,
in order to prepare and write to the target, a block device.
 dus 0.0.2 
source device: /dev/sda4 'Ubuntu 16.04.1 LTS amd64'
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
cands=1
sdb
Corsair_Voyager
 7.5G
usb
USB or memory card
p_target: target=/dev/sdb
live system or temporary superuser permissions
live system or temporary superuser permissions
live system or temporary superuser permissions
 Clone/extract  system from the source
'/dev/sda4'
to the target device (drive) '/dev/sdb'
MODEL            NAME   FSTYPE  LABEL                      SIZE
Voyager          sdb    iso9660 Lubuntu 16.04.1 LTS amd64  7.5G
                 &#9500;&#9472;sdb1 iso9660 Lubuntu 16.04.1 LTS amd64  855M
                 &#9492;&#9472;sdb2 vfat    Lubuntu 16.04.1 LTS amd64  2.3M
/dev/sda4
/dev/sdb
-----
live system or temporary superuser permissions
source=/dev/sda4
target=/dev/sdb
source=/dev/sda4
ls -l  /dev/sda4
brw-rw---- 1 root disk 8, 4 Dec  6 10:50 /dev/sda4
Cloning a device to a USB drive or memory card ...................
gpt_zap: done

Installing '/dev/sda4' to '/dev/sdb' ... :

< "/dev/sda4" pv  | dd bs=4096  of=/dev/sdb
 Please wait for sync until 'Done' is written 
 (flushing file system buffers to the device)
1.43GiB 0:03:22 [7.21MiB/s] [================================>] 100%            
374272+0 records in
374272+0 records out
1533018112 bytes (1.5 GB, 1.4 GiB) copied, 318.295 s, 4.8 MB/s
Syncing the device ...
 Done :-) 
p_clean:
live system or temporary superuser permissions
live system or temporary superuser permissions
live system or temporary superuser permissions
live system or temporary superuser permissions
clean if necessary and return
clean if necessary and quit
 Press Enter to finish guidus 

Please try it and tell me what needs to be improved :-)

*Edit:* I created a new subpage about Win32 Disk Imager in order to help people install these compressed images from Windows,

Win32DiskImager/compressed-image_2_USB-or-SD

#521

[SIZE=4]Test version of a compressed image file of a '7.8GB' persistent live system with Lubuntu[/SIZE]

I uploaded a test version of a '7.8GB' compressed image file. This is a more mature system (than the previous test versions), with removed journaling in the root-overlay partition casper-rw to reduce wear. Journaling is still active in the home-overlay home-rw partition. It is based on the *Lubuntu Xenial i386 (32-bit) current daily iso file (dated 2016-12-05)*, so 16.04.1+ (with the xenial-proposed repository turned off to improve the stability).

Notice that this Lubuntu system boots in 32-bit and 64-bit computers and in UEFI and BIOS mode. The only limit is that it does not manage in secure boot. The Ubuntu version described in the previous post boot boots in 64-bit computers in BIOS and UEFI mode including secure boot (but not in 32-bit computers because it has a 64-bit kernel).

You find the compressed image file with Lubuntu via this link,

uefi-n-bios/dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1-guid.img.xz: Use with mkusb, mkusb-nox, dus and guidus

uefi-n-bios/dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1.img-msdos.xz: Use with other tools, for example in Windows

Here are the size and md5sum of the compressed image file.

$ ls -l dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1-*.img.xz
-rw-r--r-- 1 sudodus sudodus 946567388 dec  6 19:01 dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1-guid.img.xz
-rw-r--r-- 1 sudodus sudodus 940944856 dec  7 14:01 dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1-msdos.img.xz

$ md5sum dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1-*.img.xz
9092833492d5d38ce965f7ca991f0d2c  dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1-guid.img.xz
a1d48a7eab884388486525163b17e13c  dd_Lubuntu_16.04.1-persist-live-mkusb-guidus-7.8GB-test1-msdos.img.xz

[SIZE=4]Tips for new users[/SIZE]

*In linux* mkusb, mkusb-nox, guidus and dus can install a persistent live system from this image file.

*In Windows* you can expand the file with 7-zip and after that install alias 'write' it with Win32 Disk Imager.

[SIZE=4]Description[/SIZE]

  • an improved test file 'test1' also intended for regular use
  • smaller than 8 GB to fit also in 'undersized' pendrives and memory cards (which are smaller than the nominal size)
  • *GUID partition table, GPT:* Modern, works with huge drives. Needs gpt-fix - use with mkusb, mkusb-nox and guidus
  • *MKUSB partition table:* Easier to move and grow. Works with middle-aged HP. Works with any tool, also in Windows
  • an extra partition compared to the standard made by mkusb and dus: a home-rw partition
  • Lubuntu 16.04.1+ LTS 32-bit operating system
  • mkusb and dus (with guidus) installed
  • works in UEFI and BIOS mode booted from USB (both pendrive and card via USB adapter tested in three computers)
  • works in BIOS mode booted from the SD card slot in my NUC 6i3SYH
  • does not boot in UEFI mode from the SD card slot in my NUC 6i3SYH (lacks some drivers)

It works to run this system in a pendrive or memory card as it is with Lubuntu and nominally 8 GB, but it makes things better if it in a fast USB 3 pendrive or fast memory card with at least 16 GB and then move and expand the partitions to use the whole drive. The following link describes the slightly different case with an installed system, but should help a beginner to move and expand, 'grow', partitions with gparted. uefi-n-bios/GrowIt.pdf

See the screenshots:

  • Lubuntu with the guidus welcome screen booted from a 32 GB SD card in a USB adapter
  • The SD card after cloning but before growing the partitions, as seen by gparted
  • The SD card after growing the partitions. This is only an example, you may want to change the proportion between the partitions. It is also possible to move the boundaries between the three big paritions later, if and when you need more space in one of them
  • A USB pendrive with an MSDOS partition table after cloning but before growing the partitions, as seen by gparted. Notice the extended partition.

The Lubuntu system resides in partition #4 with the ISO 9660 file system. In *guidus* there is a *quick choice* to select it in order to install into another drive (for example another USB pendrive or memory card). If you answer 'No' you arrive at the standard tool to select source file.

*Edit:* I created a new subpage about Win32 Disk Imager in order to help people install these compressed images from Windows,

Win32DiskImager/compressed-image_2_USB-or-SD

#522

Sudodus, Win32 Disk Imager is not showing .XZ files as image file type, only file types shown are .IMG, .img & *.*. *.* Seems to be working, says it was successful, will edit post after reboot, (My windows machine is doing failed update loops so it might be a while, I wish cussing was allowed in the Forums).

Nope, won't boot on HP and gparted shows drive as unformated.

I'm sure mkusb can handle .xz files, (I'll double check), but I can not find a Win alternative.

#523

sudodus said: ...

*In Windows* you can expand the file with 7-zip and after that install alias 'write' it with Win32 Disk Imager.

...

C.S.Cameron said: Sudodus, Win32 Disk Imager is not showing .XZ files as image file type, only file types shown are .IMG, .img & *.*.

*.* Seems to be working, says it was successful, will edit post after reboot, (My windows machine is doing failed update loops so it might be a while, I wish cussing was allowed in the Forums).

Nope, won't boot on HP and gparted shows drive as unformated.

I'm sure mkusb can handle .xz files, (I'll double check), but I can not find a Win alternative.

*After preprocessing with 7-zip* (or WinZip if available) to expand to an img file, *Win32 Disk Imager does the job for me*, also with big images.

#524

@C.S.Cameron,

Do you think that this two step rocket is 'too much' for a beginner, who wants to try linux? Do you think, that

  1. either we must find and recommend a tool for Windows, that can install a working system in one step from a compressed image file,
  1. or we must provide an uncompressed image file for Windows users, so that Win32 Disk Imager and other similar tools can use the downloaded file directly?

Is this the main reason why you want a small image, that you want a 4 GB image rather than an 8 GB image? (At least until we find a tool for Windows, that can install a working system in one step from a compressed image file.) Or is it due to the 4 GB file size limit in FAT32? Or just because a huge uncompressed file is cumbersome? Or because people want to use their old 4 GB pendrives or cards?

*Edit:* Extending this argument, would it be useful to provide a *minimal 2 GB image with Lubuntu* and only a casper-rw partition (or a minimal usbdata partition and no home-rw at all)?

#525

I created a new subpage about Win32 Disk Imager in order to help people install these compressed images from Windows,

Win32DiskImager/compressed-image_2_USB-or-SD

#526

I'm not hot on two-step installs myself. Can the mkusb compressed image be self extracting?

What about using Ubuntu Minimal, I think it can be made to run mkusb/dus?

If you could keep the size of install to 50MB it would be cool, at least to us with limited internet consumption.

People will be downloading this as an installer, not to browse the internet or use Libre office?

https://help.ubuntu.com/community/Installation/MinimalCD

#527

I have uploaded some UEFI and BIOS compressed images, that can do the thing after adding guidus, but they are installed systems, and the compressed images are around 320 MiB, so not really small, and not suitable for persistent live systems, and they must be extracted from compressed files.

An alternative would be to continue along the path of 9w, which comes with a small iso file, that I create from the very start. 9w could be stripped (it uses LXDE now).

But if we skip the graphical desktop environment, we will also lose gparted - Is this what we want?

And the general question - Will Windows users accept a text mode interface during the transition to Linux?

-o-

Self-extracting? Yes, within Windows. After self-extraction Win32 Disk Imager can do its job, so it would make things easier to manage.

#528

Yea, I was wondering what the size would be if we just added the stuff required to run the GUI's. No Libre Office, etc.

Puppy starts at about 300MB but you can delete apps and remaster, Not sure what minimum install is including mkusb? I think I read in one of your papers that mkusb can run in Puppy?

I installed the .XZ image with Archive Manager and all went well. Had to start dus from Neptune.

I want to avoid going into Windows as much as possible.

#529

9W also sounds cool. I think I will try to play with some small versions tomorrow. A small version might also work for running VBox. Not sure about messing with command line though.

If I need to boot Windows tomorrow I will try the two-step extraction.

#530

I hope you remember that mkusb, mkusb-nox and dus can use a compressed image directly. They will recognize the extensions img.gz (gzip compression) and img.xz (xz compression), and do the extraction and cloning via a command with a pipeline from the extracting tool, zcat or xzcat. So the problem is in Windows.

Wary Puppy can only run mkusb-bas, because it lacks some features of a modern linux distro. But I think TahrPup is better, and should be able to run mkusb, mkusb-nox and dus.

Messing with a crude command line interface is probably not an option except for server gurus. But text mode dialog menus might be an alternative. Install the package

sudo apt-get install dialog

and run dus

  1. in text mode
dus filename
  1. in a terminal window with the option -d
dus -d filename

Revamping 9w might be an alternative.

[hr][/hr] *Edit:* @ C.S.Cameron,

I must admit, that I don't understand what you want to achieve now. I think you have a good idea, but I don't get it. A couple of days ago I thought that you want a convenient way to get a persistent live drive all set up including a home-rw partition, *from Windows*. I think it would give the end user a system that can be used as it is (and has mkusb and/or guidus installed in order to create new systems).

But now with a minimal system - what should this minimal system do, and how would it make things simpler for an end user?

You mentioned that the system with mkusb and/or dus needs no browser. How do you suggest the iso file(s) should be found, downloaded and accessed?

  • with another operating system and copied to the pendrive?
  • accessed from another partition when the computer is booted from the pendrive?
  • via some tailor made interface into the computer, when booted from the pendrive? - This could be complicated and need a lot of updating to match the changes of the linux distros.
#531

That was a couple of days ago, now you have produced a way for Windows users to install Persistent Ubuntu to USB with mkusb/dus included. All that is needed is a one step install process. If I can recall, (it has been awhile), Winzip, (shareware based on pkzip freeware), has a self extractor: http://www.winzip.com/prodpagese.html. Something like this could possibly be used to extract an image to USB?

My thoughts on minimal install is faster download, many clients already have their preferred iso file, some clients might not trust iso files from unofficial sources. A minimal install could fit into a corner of a small pendrive leaving room for several iso files, Similar to the original MultiBootUSB. The user would initially use their Windows O/S for browsing and downloading iso's.

By minimal I mean no "Libre Office", no "Firefox", no SDC, no "Amazon", no "Software Center", no Games, no Persistence, etc.

Not sure about Ubiquity.

The install could include "Files" so the user could snatch iso's stored on the hard drive or if the partition for iso's is FAT or NTFS, the iso's could be dropped on the USB from Windows or Ubuntu.

The minimal mkusb drive could also be used to install persistent mkusb iso clones to another USB or to itself.

OK, I guess that would be two-stepping.

Just a thought, perhaps not a great one. (At least I don't get downvotes here like over at Ask).

I have been doing most of my mkusb/dus installs lately from a USB made using mkusb. Which I suppose I am also using for text editing, Internet browsing, downloading, installing software and posting off the wall suggestions on Forums.

#532

Thanks for explaining :-)

I have started the environment to create 9w (it sits in an SSD, that I connect externally), and I have created a crude prototype with dus.

  • It boots into text mode, where dus can run with dialog menus.
  • I can also run startx to get into LXDE, where guidus can run with zenity menus, and where gparted works.

This system is still based on Debian Wheezy, which makes it very small, but maybe not able to manage brand new hardware. The iso file is 271 MiB, and it includes for example Iceweasel (the Debian fork of Firefox), but no fancy office suite (not Libreoffice). It can be made smaller by removing packages. But when I upgrade the system base to Debian Jessie or Ubuntu Xenial, which come with systemd and a lot of more drivers and language packs for Asian languages, it will grow a lot.

I have not yet checked how it behaves, when I try to make it persistent live. It will probably need special treatment. Anyway, it would be better to base the system on a newer version, Ubuntu Trusty comes without systemd, and might be a good option to keep the size small.

#533

I suppose that if you don't ask, you don't receive. 300 MB sounds reasonable, 1/6 the size of Ubuntu desktop iso, 6 times as fast to download.

I took a look at WinZip, self extracting, big signs on the extract process saying Demo Not for Commercial Use or something like that. clicking the exe extracts the payload to a predetermined folder, (unless changed by user), say c:\mkusb. The folder can be opened, the image clicked and Image Writer chosen to open it.

Gave MS IExpress a try, it is Microsoft's version of a zip self extractor. It makes an exe file that when clicked, extracts the compressed file and dumps it in the program of your choice, say Image Writer. only thing User needs to do is confirm USB is correct in IW. (or so they say).

I will post this now, just in case IExpress crashes my computer or eats my hard drive, I don't trust MS much. Will edit post if results are positive and computer is still working.

#534

[SIZE=4]Small 9w iso files with guidus and gparted installed[/SIZE]

Two small iso files with guidus and gparted installed are uploaded. The intention is that it can be

+ Downloaded to Windows and installed by cloning, for example with Win32 Disk Imager. It works in CD/DVD drives and memory cards too. The iso file are only 230 MiB and 231 MiB, and use the LXDE desktop environment. There are some networking tools, and the extrememly light Links2 browser with two dedicated desktop files to find Ubuntu and Debian iso files quickly.

+ Used by people who have already downloaded an Ubuntu iso file, and do not want to do it again, which would be the case, if an image of a persistent live system is installed.

Compare with the previous posts #512 with Ubuntu and #519 with Lubuntu. These are installed in a two-step procedure in Windows. On the other hand you get a working persistent live system, not only the guidus installer.

  • But in linux it is better to install mkusb, mkusb-nox, guidus and dus from the Launchpad PPA. See this link: mkusb/gui#Installation

See the following screenshots (running in VirtualBox). I have tested these systems in a few computers too.

  • Notice that one file has a minimal 32-bit i486 non-pae kernel that runs also in very old computers.
  • The other file has a 32-bit i686-pae kernel, which is better to manage more than 2 GiB RAM. Recommended for most users.
  • Both systems run only in BIOS mode. If you think it is worthwhile, I can try to make a 64-bit system for UEFI mode.

[hr][/hr] You get these small 9w iso files with guidus and gparted installed 9w-dus.iso via these links

phillw.net/isos/linux-tools/9w/9w-dus-i486.iso phillw.net/isos/linux-tools/9w/9w-dus-i686.iso

The sizes and md5sums are:

$ ls -l 9w-dus*
-rw-rw-r-- 1 sudodus sudodus  241172480 dec  8 19:52 9w-dus-i486.iso
-rw-rw-r-- 1 sudodus sudodus  242221056 dec  9 22:34 9w-dus-i686.iso
$ md5sum 9w-dus*
34b0f8faec016623e13e9d9ede52076d  9w-dus-i486.iso
ec8f99563513831c6a17af8382deb5d2  9w-dus-i686.iso
#535

I don't think you can beat 230MB with a stripped down puppy. Downloading now.

Have not had luck with IExpress with the 3.5GB .img file.

#536

sudodus said: [SIZE=4]Small 9w iso file with guidus and gparted installed[/SIZE]

A small iso file with guidus and gparted installed is uploaded. The intention is that it can be

+ Downloaded to Windows and installed by cloning, for example with Win32 Disk Imager. It works in CD/DVD drives and memory cards too. The iso file is only 230 MiB, and it uses the LXDE desktop environment. There are some networking tools, and the extrememly light Links2 browser with two dedicated desktop files to find Ubuntu and Debian iso files quickly.

+ Used by people who have already downloaded an Ubuntu iso file, and do not want to do it again, which would be the case, if an image of a persistent live system is installed.

Compare with the previous posts #512 with Ubuntu and #519 with Lubuntu. These are installed in a two-step procedure in Windows. On the other hand you get a working persistent live system, not only the guidus installer.

Been Playing with it for about 1 hour now...and having a good time in the process. First thing I had Noticed though...could not connect to the internet with my wifi...but Ethernet worked. Tested with booting on a Acer Aspire 5550 laptop.

Network:   Card-1: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe
           driver: tg3
           Card-2: Intel Centrino Advanced-N 6205 [Taylor Peak]
           driver: iwlwifi

More to come.

#537

1fallen said: Ben Playing with it for about 1 hour now...and having a good time in the process.

First thing I had Noticed though...could not connect to the internet with my wifi...but Ethernet worked. Tested with booting on a Acer Aspire 5550 laptop. More to come.

Much the same for the Internet and wifi but Ethernet worked as stated above.

Now try to get my head around all that is happening here.

#538

1fallen said: Ben Playing with it for about 1 hour now...and having a good time in the process.

First thing I had Noticed though...could not connect to the internet with my wifi...but Ethernet worked. Tested with booting on a Acer Aspire 5550 laptop. More to come.

The small iso file with guidus and gparted installed is based on Debian Wheezy, so the kernel is old (linux 3.2.0-4-486 #1 Debian 3.2.78-1 i686). We must not expect that there will be drivers for [new] wifi chips.

But it might be useful as an intermediate system from Windows to linux, for example in order to install a persistent live Ubuntu or Debian system.

#539

C.S.Cameron said: I don't think you can beat 230MB with a stripped down puppy.

Downloading now. I'm looking forward to your results. Will you be able to do what you want to do with this small iso file with guidus and gparted installed?

Have not had luck with IExpress with the 3.5GB .img file.

Too bad IExpress does not work. Maybe the file is too big for it. But it should be possible to use WinZip or some free tool to create a self-extracting file. Maybe the Windows version of 7-zip can do it.

#540

I tested 'the small iso file with guidus and gparted installed' in a Toshiba laptop with an Intel i5 CPU. I used the usdata partition of a persistent live pendrive to show, that it works to mount an NTFS partition with an iso file, and access the file from there to create a persistent live drive.

So this 'emulates' a case, where you have downloaded an Ubuntu family iso file but failed to create a persistent live drive with tools in Windows.

  1. Clone the small iso file with guidus and gparted installed into a USB pendrive or a CD disk or DVD disk or a memory card, whatever device you can boot from.
  1. Boot into this cloned system.
  1. Mount the partition, where you have an Ubuntu family iso file, or where there is space enough to download and store an iso file and download it.
  1. Check the md5sum.
  1. Start guidus and let it guide you through the necessary steps.

See the attached screenshots :-)

#541

Today I have spent trying to fix my mkusb/16.04/VBox/Win10 flash drive. A few days ago I tried resizing the NTFS partition so I could add space to the Casper-rw partition. The NTFS partition appeared to have become fragmented. Not a problem, I backed up the files on the partition, re-formated it NTSF and moved the files back into it. Not much problem besides VBox not recognizing the massive VDI file until I made another machine. Everything was good for a couple days... Today I went to boot the drive and it was stuck on the screen with the word UBUNTU in the center and five blinking dots under it. I let it go for about an hour. Examination showed the casper-rw partition was corrupt as the drive would boot ok using the casper-rw file on another pendrive and that pendrive would not boot with this casper-rw partition. We have had a few power outages due to storms here. Is there any way to fix a corrupt persistent partition? There is lots of free space on it, so the problem is not overfilling. The stick boots fine if I copy contents of another USB's Casper-rw partition to it's persistent partition.

I have only had a chance to try the small iso on VBox, looks really nice, (but would prefer 64bit). I am thinking this would also make a good base for another VBox drive. Will try it on USB as soon as I have one free.

#542

Is there any way to fix a corrupt persistent partition?

I think you know this better than I, and I can only suggest some tricks, that you know already.

  1. Boot into a live-only session and try to repair the file system of the casper-rw partition,
sudo e2fsck -f /dev/sdxy

where x is the drive letter and y is the partition number (should be 5 if made by mkusb or dus).

  1. If this does not help and if /home is a directory in casper-rw, (actually .../casper-rw/upper), keep .../home and 'lost+found', while you remove all the other directories and files from the casper-rw partition.

-o-

Use the *backup script* that I provided (or some other backup method) often. It can save the day, when these things happen. I mean *when* (not *if*) :-P

#543

sudodus said: The small iso file with guidus and gparted installed is based on Debian Wheezy, so the kernel is old (linux 3.2.0-4-486 #1 Debian 3.2.78-1 i686). _We must not expect that there will be drivers for [new] wifi chips._

Oh of course... just pointing out "My" findings is all...I never have expectations in testing New things.:) All in all...This is kind of a nifty little project. Thanks

#544

No worries, your feedback was good. (I was only explaining *why* there is a problem with this system and wifi.)

#545

I took the .iso and dd'd it into an .img, did not seem much difference in size, 236 MB. Ran it thru MS IExpress, first time got it to go from clicking the .exe file to opening Image Writer. Only problem was the 9w-dus.img was not the source file in IW. I think it, (or some Free software), should be able to make the image open in Image Writer by clicking the .exe. Next time got it to automatically put the .img file into the folder of the users choosing. The .img finally installed great to flash drive usung IW. It gave a good first impression, got to do some more test driving. Thinking synaptic is not very large, might be a thought to include it.

#546

The iso files needs no treatment with MS IExpress. It is only as an alternative to the img.xz compressed image files.

The iso files can be cloned/copied/flashed directly as they are by the cloning program (for example Image Writer).

-o-

*Synaptic* is on the wish list. I am looking forward to more feedback from you, C.S.Cameron :-)

The iso file that you are testing has an i486 kernel (non-pae), which is good also for very old computers (for example laptops with Pentium M and Celeron M processors). But I have another iso file in the pipeline, this time with an i686-pae kernel, which can manage more RAM than 2 GB in a good way. I tested in my laptop with 4 GB RAM, and it makes a big difference, because it will be possible to download an Ubuntu iso file into the default location, $HOME/Downloads. The non-pae version can download a Lubuntu iso file to that location but not standard Ubuntu.

#547

I uploaded a new iso file with i686-pae kernel and some minor improvements: a directory entry on the desktop to quickly find available drives, where iso files might be stored (and auto-mounting all mountable devices and partitions). The old iso file is renamed.

  • Notice that one file has a minimal 32-bit i486 non-pae kernel that runs also in very old computers.
  • The other file has a 32-bit i686-pae kernel, which is better to manage more than 2 GiB RAM. Recommended for most users.
  • Both systems run only in BIOS mode. If you think it is worthwhile, I can try to make a 64-bit system for UEFI mode.

[hr][/hr] You get these small 9w iso files with guidus and gparted installed via these links

phillw.net/isos/linux-tools/9w/9w-dus-i486.iso phillw.net/isos/linux-tools/9w/9w-dus-i686.iso

The sizes and md5sums are:

$ ls -l 9w-dus*
-rw-rw-r-- 1 sudodus sudodus  241172480 dec  8 19:52 9w-dus-i486.iso
-rw-rw-r-- 1 sudodus sudodus  242221056 dec  9 22:34 9w-dus-i686.iso
$ md5sum 9w-dus*
34b0f8faec016623e13e9d9ede52076d  9w-dus-i486.iso
ec8f99563513831c6a17af8382deb5d2  9w-dus-i686.iso
#548

C.S.Cameron said:

Thinking synaptic is not very large, might be a thought to include it. Great thought...I second it to include.:KS Seeing as it is a more or less a starter for newer users. But won't be a show stopper if not.

#549

sudodus said: I uploaded a new iso file with i686-pae kernel and some minor improvements: a directory entry on the desktop to quickly find available drives, where iso files might be stored (and auto-mounting all mountable devices and partitions). The old iso file is renamed.

  • Notice that one file has a minimal 32-bit i486 non-pae kernel that runs also in very old computers.
  • The other file has a 32-bit i686-pae kernel, which is better to manage more than 2 GiB RAM. Recommended for most users.
  • Both systems run only in BIOS mode. If you think it is worthwhile, I can try to make a 64-bit system for UEFI mode.

[HR][/HR] You get these small 9w iso files with guidus and gparted installed via these links

phillw.net/isos/linux-tools/9w/9w-dus-i486.iso phillw.net/isos/linux-tools/9w/9w-dus-i686.iso

The sizes and md5sums are:

$ ls -l 9w-dus*
-rw-rw-r-- 1 sudodus sudodus  241172480 dec  8 19:52 9w-dus-i486.iso
-rw-rw-r-- 1 sudodus sudodus  242221056 dec  9 22:34 9w-dus-i686.iso
$ md5sum 9w-dus*
34b0f8faec016623e13e9d9ede52076d  9w-dus-i486.iso
ec8f99563513831c6a17af8382deb5d2  9w-dus-i686.iso

Thanks will look at it tomorrow.

#550

Synaptic is on the wish list. But you should remember that this primitive system is read-only, not persistent, so people would only enjoy what they install until reboot or shutdown. Do you still want it?

I am thinking of revamping the UEFI-n-BIOS installed mini system into a system for this purpose with lxde, dus, gparted, links2, synaptic and maybe also some other handy tools. What do you think about this idea?

#551

sudodus said: Synaptic is on the wish list. But you should remember that this primitive system is read-only, not persistent, so people would only enjoy what they install until reboot or shutdown. Do you still want it?

_I am thinking of revamping the UEFI-n-BIOS installed mini system into a system for this purpose with lxde, dus, gparted, links2, synaptic and maybe also some other handy tools. What do you think about this idea?_

I think that would be perfect....I kind of thought you would eventually anyway.:KS

#552

The original 9w install seems to be invisible in gparted and the partitions do not show up when it is plugged into a running Ubuntu machine, (recursive says gparted)?

Is this intentional? It would probably be good to give a FAT32 partition for sticking iso(s) on. I understand FAT is simpler than NTFS.

The .iso format seems OK but IW does not see it except with *.*. Giving the user a .img file would be most convenient but what is the compression ratio vs .xz?

With my 128GB drive, 0.1% non-contiguous, I copied the contents of casper-rw over to another partition, re-formatted and moved the contents of work back, this worked with home stuff ok but I had to re-install VBox, the virtual machines and update the hardware locks.

When backing up a casper-rw partition, it might be a good idea to record the UUID of the partition and use it when restoring.

#553

You post contains some very substantial feedback. I wll try to reply to all of it :-)

C.S.Cameron said: The original 9w install seems to be invisible in gparted and the partitions do not show up when it is plugged into a running Ubuntu machine, (recursive says gparted)?

Is this intentional?

I would call it a bug. *gparted* cannot show typical partition tables and file systems of hybrid iso files. You can view such partition tables and file systems with *lsblk*, for example:

sudo lsblk -fm

But this file system is read-only, so it is not suitable for a persistent live drive. *The 9w system is only a small intermediate system with tools to help you create a persistent live system* of Ubuntu, an Ubuntu flavour or Debian from a 'full iso file' of a current version (when this is written Ubuntu 16.04.1 LTS or Debian 8.6 'Jessie').

It would probably be good to give a FAT32 partition for sticking iso(s) on. I understand FAT is simpler than NTFS.

This should be possible, but is it really what you want and what people need? Even if we can make a persistent live drive with 9w, it will be an old Debian Wheezy system.

The .iso format seems OK but IW does not see it except with *.*. Giving the user a .img file would be most convenient but what is the compression ratio vs .xz?

These 9w iso files are hybrid iso files. They work as cloned alias burned to CD/DVD disks as well as cloned alias flashed to USB pendrives and memory cards (and SSDs and HDDs). This makes them easy to use.

An iso file is a special case of an img file. To be more verbose: An iso file is a synthetic image file with an ISO 9660 file system, built with tools from scratch, not created as an image of a system already installed into a device. So you can simply rename it,

mv file.iso file.img

and make the Windows Image Writer happy.

The main part of the iso file is the compressed file system squashfs. In addition there are some files for booting, and they are not compressed. I don't think it is worthwhile to compress an iso file.

With my 128GB drive, 0.1% non-contiguous, I copied the contents of casper-rw over to another partition, re-formatted and moved the contents of work back, this worked with home stuff ok but I had to re-install VBox, the virtual machines and update the hardware locks.

Am I understanding correctly, that this was caused by a power outage?

I have a similar portable system with Ubuntu, Virtualbox and Windows in a virtual machine. I back it up with *Clonezilla* - to get a compressed image of the whole system. It is rather straightforward, and I think a reliable way to get back to a working system.

When backing up a casper-rw partition, it might be a good idea to record the UUID of the partition and use it when restoring. Yes, with several partitions and backups, it can be a good way to keep track of you different backups. I can look into it, to see how to make it. But maybe it is better to use Clonezilla and get a general backup solution for your more complicated setup.

#554

I think I could see the partition contents ok using the Puppy File thing.

Is it possible to install 9w to a corner of the flash drive and leave the remaining space FAT32 so it can be used? I would not make the drive Persistent, I dont think it would be usefull to most of the people wanting a mkusb installer. Those wanting persistence can make it themselves.

Either a power outage or I yanked the flash drive too soon. It seemed to work for a while but is now giving more problems, It seems the files are non-contiguous. I copied the casper-rw stuff over to another pen drive and tried using that for casper-rw. Certain folders from the original casper-rw would make that drive non-contiguous also, so I don't think there is physical damage. Have you heard of a de-fragger for files on ext partitions?

VirtualBox complained about the UUID's when I was trying to start it from the rebuilt casper-rw.

#555

C.S.Cameron said: I think I could see the partition contents ok using the Puppy File thing.

Good :-)

Is it possible to install 9w to a corner of the flash drive and leave the remaining space FAT32 so it can be used? I would not make the drive Persistent, I dont think it would be usefull to most of the people wanting a mkusb installer. Those wanting persistence can make it themselves.

It should be possible to make a small FAT32 partition and leave the rest of the drive unallocated. This way an end user would be able to create a new partition with a file system and use the drive for storage. But Windows might only see the first partition. A better alternative is to boot into another computer and 'grow' the original FAT32 partition to use the whole drive. (Could be done in Windows right after cloning.)

Either a power outage or I yanked the flash drive too soon. It seemed to work for a while but is now giving more problems, It seems the files are non-contiguous. I copied the casper-rw stuff over to another pen drive and tried using that for casper-rw. Certain folders from the original casper-rw would make that drive non-contiguous also, so I don't think there is physical damage. Have you heard of a de-fragger for files on ext partitions?

No, but sometimes it helps to repair the ext file system with

sudo e2fsck -f /dev/sdxy

where x is the drive letter and y is the partition number

VirtualBox complained about the UUID's when I was trying to start it from the rebuilt casper-rw.

I see. I think making a backup image with Clonezilla will override this problem, because it will preserve everything, including the UUIDs.

#556

Just as long as a person has control over the space not used by the O/S.

I tried e2fsck, It reported the non-contiguouse partition but did not fix it.

Thanks for the tip about clonezilla and UUID's, I guess the same goes for dd if I was brave enough to use it.

One more item for the wish list is a spell checker, I just figured out why none of my text is red when I am using Pupppy.

#557

Yes, cloning is cloning so dd preserves the UUIDs too. But use mkusb or dus if you want to clone the whole device that way. They wrap a safety belt around dd. That's why are here (discussing in this thread) ;-)

The advantage with Clonezilla is that it only bothers about used blocks, all the free space is skipped, which can make a huge difference in time to do the job.

-o-

What spell checker package would you want to use?

#558

Giving it some thought, I am probably the only person that requires a spell checker in a bootable USB maker :-)

#559

[SIZE=4]Installed systems with guidus and gparted[/SIZE]

Two compressed image files with guidus and gparted installed are uploaded. The intention is that they can be

+ Downloaded to Windows and installed by cloning, for example with Win32 Disk Imager. They work from USB drives, memory cards and from internal drives too. But they can *not* be installed alongside Windows in the same drive. They were originally developed from the 32-bit Ubuntu mini.iso and the 64-bit Ubuntu Server iso files and use the LXDE desktop environment. Both wired and wireless networks work for me. The extrememly light Links2 browser with two dedicated desktop files help you find Ubuntu and Debian iso files quickly.

+ Used by people who have already downloaded an Ubuntu iso file, and do not want to do it again, which would be the case, if an image of a persistent live system is installed. These new files are smaller than any of the iso files of official Ubuntu desktop flavours. Only the mini.iso and the Ubuntu Server iso files can compete in size, but they contain no graphical desktop, and they cannot be run live (they are only installers).

Compare with the previous posts #512 with Ubuntu and #519 with Lubuntu. These new files are installed with the same two-step procedure in Windows. Those systems bring persistent live systems, while these bring installed systems (installed like a regular installed system, but also possible to install into a USB pendrive or memory card).

  • But if you have a running linux operating system it is better to install mkusb, mkusb-nox, guidus and dus from the Launchpad PPA. See this link: mkusb/gui#Installation

[SIZE=4]Demo and testing[/SIZE]

See the following screenshots of the UEFI n BIOS system.

It logs in via lightdm. The *dus mounter* auto-mounts the drives that are possible to mount to help an inexperienced user to find them via the 'media' folder link on the desktop. This is a special feature of these compressed image files. The text mode menu is started with the command

~/text-mode-menu

I installed scrot (afterwards) to be able to make screenshots. The second screenshot is from BIOS mode (in my Toshiba laptop), and the third screenshot is from UEFI mode (in my Intel NUC booted from an SD card is the built-in card slot). I reduced the resolution with xrandr in order to get a suitably sized screenshot to upload.

I have tested these systems in a few computers, and *I look forward to feedback from your tests*. Now there are many alternative systems available, and it will be interesting to find out, what you find works best, so that we can focus on that system, to debug and polish it :-)

  • Notice that these systems need log in with user and password. It is a good idea to change the password, if you want to use the system beyond testing.

[B]user: guru password: changeme[/B]

  • Notice that one file has a 32-bit i686-pae kernel that runs in 32-bit and 64-bit computers but only in BIOS mode.
  • The other file has a 64-bit amd64 kernel, which works in most new and middle-aged PC computers with Intel and AMD processors. This image file is recommended for most users because it makes systems that can boot in *UEFI and BIOS* mode.
  • Both of these systems are updated & dist-upgraded to be up to date when they were created, Dec 11 and Dec 12 2016, so '16.04.1+'.

[hr][/hr] You get these Installed systems with guidus and gparted installed via these links

dd_X32-dus-lxde-Intl_2016-12-11_7.8GB.img.xz 32-bit, only BIOS mode, 371 MiB

dd_dus-lxde_16.04-UEFI-n-BIOS_2017-05-07_intel-4-pendrive-7.8GB.img.xz 64-bit, UEFI n BIOS, 542 MiB (updated)

The sizes and md5sums are:

$ ls -l dd_*dus-lxde*.img.xz
[COLOR="#0000CD"]-rw-r--r-- 1 sudodus sudodus 568263936 maj  7 13:23 dd_dus-lxde_16.04-UEFI-n-BIOS_2017-05-07_intel-4-pendrive-7.8GB.img.xz[/COLOR]
-rw-r--r-- 1 sudodus sudodus 388936712 dec 11 21:28 dd_X32-dus-lxde-Intl_2016-12-11_7.8GB.img.xz
$ md5sum dd_*dus-lxde*.img.xz
[COLOR="#0000CD"]50817e86dd34d05ee45c5e3f899314af  dd_dus-lxde_16.04-UEFI-n-BIOS_2017-05-07_intel-4-pendrive-7.8GB.img.xz[/COLOR]
4e640f50799f65ea0fbf039d6910a2b4  dd_X32-dus-lxde-Intl_2016-12-11_7.8GB.img.xz

Alternate download:

drive.google.com/open?id=0BzX-18u3W1sQTTktLUpwLUstVzg

a4762ca8ffd292e5ce18cb59662d61e5  9W-DUS_i686.exe
4ae4235b64bb759073e9efc5898f0054  9W-DUS_i686.exe.torrent
631bcb1ca0dea918fea17433d91a194d  9W-DUS_i686.img.xz
2c9b58de362ef32a09e06a85afc266de  9W-DUS_i686.img.xz.torrent
ec8f99563513831c6a17af8382deb5d2  9w-dus-i686.iso
f103dfacad669751f6b271e921eaca39  9w-dus-i686.iso.torrent
[COLOR="#0000CD"]977fe780f2888b5787c792f2b212378d  dd_dus-lxde_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB.img.xz
2d8035d5a240f357985c8df40b64729e  dd_dus-lxde_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB.img.xz.torrent[/COLOR]
13e4fa2ecb8243b39388f31dbfd3a0ea  dd_text_16.04-UEFI-n-BIOS_2017-01-15_intel-4-pendrive-7.8GB.img.xz
569eb14b2d183e7f15eadf265883db5e  dd_text_16.04-UEFI-n-BIOS_2017-01-15_intel-4-pendrive-7.8GB.img.xz.torrent

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] [B]user: guru password: changeme[/B] [/td][/tr][/table]

#560

Downloading now.

Yesterday was trying to figure out how to use guidus to make an archive file as mentioned in this thread. I noticed that there is no back button. This meant I had to restart every time I made a mistake.

Doing some experimenting, (hacking), today using mkusb and guidus to install grub to USB. When I make a Live non persistent drive, and try to open it in gparted there is a warning about block size being 2048 vs 512 and if I click ignore enough times gparted shows the drive as being 16GB vs 4GB. This does not happen if Persistent install is chosen.

#561

C.S.Cameron said: Downloading now.

Yesterday was trying to figure out how to use guidus to make an archive file as mentioned in this thread. I noticed that there is no back button. This meant I had to restart every time I made a mistake.

I think I see the point. So instead of going back to the previous menu, you would like to return to the same menu. I have thought about it. The problem is that I use the standard tool zenity, and it is limited. I would need an extra button, but see no way to get it without selecting some other tool, and that would make dus (the future mkusb) less portable.

*Edit:* Or do you mean something else?

By the way, please explain what you mean by 'use guidus to make an archive file' :-)

Doing some experimenting, (hacking), today using mkusb and guidus to install grub to USB. When I make a Live non persistent drive, and try to open it in gparted there is a warning about block size being 2048 vs 512 and if I click ignore enough times gparted shows the drive as being 16GB vs 4GB. This does not happen if Persistent install is chosen.

I think this is a bug in gparted. It does not recognize the partition table and iso 9660 file system of hybrid iso files correctly. Obviously hybrid iso files work (can be cloned to CD/DVD/USB drives to create bootable drives of most modern linux distros), but gparted 'does not understand'.

-o-

I have not forgotten this item:

Is it possible to install 9w to a corner of the flash drive and leave the remaining space FAT32 so it can be used?

but I have been busy with the other tasks. Do you think that the 9w images are the best (for moving from Windows to linux)?

  • Is the small size the deciding factor?
  • Is it working well enough?
  • How important is it to have something that works also in UEFI mode?

Or is it too early to decide ... you need more time to test the different alternatives, also the compressed image files of installed systems, that you started uploading recently?

#562

"But use mkusb or dus if you want to clone the whole device that way" - Post 555.

If only two buttons you have chosen the right ones.

Gparted sees the Persistent install OK, just not the Live one.

I really like 9w and have already recommended it to people as is.

#563

Hi C.S.Cameron,

I select a device to clone (or in general, to use as an input file) like this:

A. Start from the command line and enter the source file or device as a parameter (this is what I do most of the time).

dus /dev/sdx

B. Use the graphical file selector. Look at the bottom right corner (just above the OK button). Change the mask to s[dr]? or ***** and change directory to /dev to 'see' the devices. See the attached screenshot.

In the particular case with 9w-dus-i686.img.xz you can interrupt the cloning after one GB is cloned, because there is no partition beyond that, but in the general case you have to clone the whole device. Clonezilla is more efficient, because it clones only used blocks.

-o-

I have tried a lot to make a good extracted image of 9w which boots from *grub*, 9w-dus-i686.img.xz

It boots in many computers, but not in my son's HP Elitebook 8560p. (Have you got the same brand name and model, or something very similar?). It seems to continue reading from the pendrive forever, and does not boot at all, not even to the internal system until I make a hard shutdown and remove the pendrive. :-(

  • The Elitebook works with the corresponding iso file 9w-dus-i686.iso
  • The Elitebook works with Ubuntu family boot drives made with the same procedure.

Although we know, that it does not work 'everywhere', you and other people might find it useful anyway. It comes with a usbdata partition, which is available from Windows like the mkusb-dus persistent live drives. But it is very small, all partitions fit within one GB, in order to work with small pendrives and memory cards. After compression the size is 249 MiB.

I tried, and it works to expand the usbdata partition from the system itself (when booted from a pendrive with this 9w system).

Download and try this extracted image in some computers, and check that you can expand the usbdata partition and use it for storage and transfer to/from Windows :-)

9w-dus-i686.img.xz

$ [COLOR="#0000FF"]ls -l 9w-dus-i686.img.xz[/COLOR]
-rw-r--r-- 1 sudodus sudodus 260632536 dec 13 12:12 9w-dus-i686.img.xz
$ [COLOR="#0000FF"]md5sum 9w-dus-i686.img.xz[/COLOR]
ca2eae1ef3598c2fa999414f47d28451  9w-dus-i686.img.xz
$ [COLOR="#0000FF"]sudo lsblk -fm /dev/sdd[/COLOR]
NAME   FSTYPE  LABEL     UUID                                 MOUNTPOINT NAME    SIZE OWNER GROUP MODE
sdd                                                                      sdd      15G root  disk  brw-rw----
&#9500;&#9472;sdd1 ntfs    usbdata   6BC03D6B35A855ED                                &#9500;&#9472;sdd1  576M root  disk  brw-rw----
&#9500;&#9472;sdd3 vfat    9wdusi686 01F5-10BD                                       &#9500;&#9472;sdd3  122M root  disk  brw-rw----
&#9492;&#9472;sdd4 iso9660 9w-dus    2016-12-09-22-33-42-00                          &#9492;&#9472;sdd4  250M root  disk  brw-rw----
$ [COLOR="#0000FF"]sudo parted /dev/sdd print[/COLOR]
Model: SanDisk Cruzer (scsi)
Disk /dev/sdd: 16,0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 3      2097kB  130MB  128MB  primary  fat32        boot
 4      130MB   392MB  262MB  primary
 1      392MB   **[COLOR="#cc0000"]996MB[/COLOR]**  604MB  primary  ntfs
#564

[SIZE=4]New extracted 1 GB image of 9w with guidus[/SIZE]

I tried another way to create a good extracted image of 9w, which boots at least in all computers where I can test, 9W-DUS_i686.img.xz

The system in this file boots via *syslinux*, and has one single FAT32 partition slightly larger than 1 GB, so to be sure *you need a 2 GB pendrive or memory card*.

I made this system via a detour to Windows and *Rufus*. But if I made it in a big pendrive and reduced the size of the partition with gparted, computers would not boot from it.

So I made it in a 1 GB micro SD card and it can boot all tested computers, also the stubborn HP Elitebook 8560p. I cloned it to a bigger pendrive and card, and it boots, but only if I leave the partition as it is (I cannot 'grow' it like I am used to from the linux world of grub booting).

Instead I used *gparted to create an NTFS partition behind the boot partition* to be able to use the whole pendrive. I know that it works in linux, but I found that it works also in an up to date Windows 10 system: *Windows can manage more than one partition in a USB pendrive*. See the attached screenshots :-)

An obvious alternative for Windows users is to download the 9w-dus-i686.iso file and use *Rufus* to create a USB pendrive. It is straightforward, and I think a reliable method.

-o-

Please download and try this extracted image in some computers, and check that you can create a usbdata partition and use it for storage and transfer to/from Windows :-)

9W-DUS_i686.img.xz

$ [COLOR="#0000FF"]ls -l 9W-DUS_i686.img.xz[/COLOR]
-rw-r--r-- 1 sudodus sudodus 238642484 dec 13 20:58 9W-DUS_i686.img.xz
$ [COLOR="#0000FF"]md5sum 9W-DUS_i686.img.xz[/COLOR]
631bcb1ca0dea918fea17433d91a194d  9W-DUS_i686.img.xz
$ [COLOR="#0000FF"]sudo lsblk -fm /dev/sdd[/COLOR]
[sudo] password for sudodus: 
NAME   FSTYPE LABEL  UUID                                 MOUNTPOINT NAME    SIZE OWNER GROUP MODE
sdd                                                                  sdd     958M root  disk  brw-rw----
&#9492;&#9472;sdd1 vfat   9W-DUS D8F3-9758                                       &#9492;&#9472;sdd1  957M root  disk  brw-rw----
$ [COLOR="#0000FF"]sudo parted /dev/sdd print[/COLOR]
Model: Generic- USB3.0 CRW -SD (scsi)
Disk /dev/sdd: 1005MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  [COLOR="#FF0000"]1005MB[/COLOR]  1003MB  primary  fat32        boot, lba

This is what the system looks like in a 32 GB pendrive:

$ [COLOR="#0000FF"]sudo lsblk -fm /dev/sdd[/COLOR]
NAME   FSTYPE LABEL   UUID                                 MOUNTPOINT          NAME    SIZE OWNER GROUP MODE
sdd                                                                            sdd    29,8G root  disk  brw-rw----
|-sdd1 vfat   9W-DUS  D8F3-9758                            /media/sudodus/9W-DUS  |-sdd1  957M root  disk  brw-rw----
`-sdd2 ntfs   usbdata 1ACBE11B219B20A3                     /media/sududus/usbdata `-sdd2 28,9G root  disk  brw-rw----
$ [COLOR="#0000FF"]sudo parted /dev/sdd print[/COLOR]
Model: SanDisk Extreme (scsi)
Disk /dev/sdd: 32,0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  [COLOR="#FF0000"]1005MB[/COLOR]  1003MB  primary  fat32        boot, lba
[COLOR="#800080"] 2      1005MB  32,0GB  31,0GB  primary  ntfs[/COLOR]
#565

Thank you for providing todays entertainment.

Mine is a 8560w about 5 years old, user gets to spec processor, video card, RAM, etc, Does your son's boot USB3 OK? Mine does not seem to.

#566

161214 AM - 9w-dus-i686.img.xz

Extracted .xz file to USB using Dus.

USB would not boot on HP, Booted fine to RAM on Acer.

Opened gparted and could see all sdb partitions, big smile.

Expanded sdb1 NTFS partition and copied Ubuntu ISO to it.

Tried dus but it would not self install with ISO on unmounted partition, (duh).

Copied ISO to desktop folder.

Ran dus and it worked perfectly making a self install.

Wish list - a button to move ISO file from sdb1 to desktop and auto un-mount sdb. Although self install would probable be a rare case and not required when installing Persistent Ubuntu to a second pendrive.

#567

C.S.Cameron said: Thank you for providing todays entertainment.

Mine is a 8560w about 5 years old, user gets to spec processor, video card, RAM, etc, Does your son's boot USB3 OK? Mine does not seem to.

You are welcome :-)

Yes, it can boot from a Sandisk Extreme USB 3 pendrive. (If I remember correctly, there are only USB 2 ports in my son's Elitebook, including one USB 2 plus eSATA combo, but the Sandisk Extreme pendrives are good because of the fast memory management, they make a big difference compared to standard USB 2 pendrives.)

#568

C.S.Cameron said: 161214 AM - 9w-dus-i686.img.xz

Extracted .xz file to USB using Dus.

USB would not boot on HP, Booted fine to RAM on Acer.

Opened gparted and could see all sdb partitions, big smile. :-)> Expanded sdb1 NTFS partition and copied Ubuntu ISO to it.

Tried dus but it would not self install with ISO on unmounted partition, (duh).

Copied ISO to desktop folder.

Ran dus and it worked perfectly making a self install. Yes, this works when there is enough RAM.> Wish list - a button to move ISO file from sdb1 to desktop and auto un-mount sdb. Although self install would probable be a rare case and not required when installing Persistent Ubuntu to a second pendrive.

Yes, I note this button on the wish list (maybe OK with a desktop file). Right now, I will wait a while for more items coming to the wish list.

For example, how important is it to have a system that works in UEFI mode? Did you test that compressed image file yet, post #557 'Installed systems with guidus and gparted'. The size is 542 MiB. I could not make it smaller and at the same time make it boot correctly into a graphical user interface, but it would be possible to make a much smaller image file with a text mode interface.

Do you think there are enough people who would want a light-weight UEFI and BIOS system in order to run dus in text mode (with dialog menus)?

#569

I downloaded the 64 bit version but have not had a chance to play with it yet, no free 8GB pendrive at the moment.

(it is running a mkusb install of puppy with VBox installed, The vdf file is on a second pendrive, USB2, so slow, might retire it very soon).

Seeing how well 9w works for it's size, I'm wondering if a larger 64 bit version is really needed, but I would like to try the text mode version. This might not suit all Windows users, better to start them into Linux gently.

Extracted the .img file from 9w-dus-i686.img.xz, and ran it through Iexpress, .exe file was 256MB. The extract process is familiar to anyone who has installed a Windows program. Click the image.exe file and you are asked what folder you want to put the image file into and offered a default location. Found a Linux image.exe maker, I will try it out if it is not too complicated. https://ubuntuforums.org/showthread.php?t=847329

#570

It seems that you, C.S.Cameron, are happy with 9w, and that you do not really need a tool for UEFI and BIOS. We will notice, if people want a corresponding tool for UEFI.

It is interesting to read about your tests with self-extracting files to make things easy in Windows. *Are you ready to upload something now?* Or is your internet connection too slow for uploading? In that case you could give me a recipe to make a copy of your best self-extracting file and upload it from here.

#571

I gave the Linux .zip to .exe converter a try and was quite impressed, very fast.

It extracts the .img file to the same folder the .exe file is in.

This is handy, a Windows user puts the .exe into a folder double clicks it then double clicks the resulting .img file and Image Writer is ready to write, (Destination should be confirmed).

In Ubuntu I clicked ftp://ftp.info-zip.org/pub/infozip/win32/unz552xn.exe

I downloaded the .exe file, Extracted unzipsfx.exe and put it into folder 9wselfextract.

Compressed 9w-dus-i686.img to .zip format using nautilus and put it in the same folder.

CD'd to the folder in terminal and ran:

cat /unzipsfx.exe /9w-dus-i686.img.zip > /9w-dus-i686.img.exe zip -A /9w-dus-i686.img.exe (not sure if I had to run the second line)?

The .exe file was created as fast as greased lightning.

I took that into Windows 7 and the results were as mentioned above.

The resulting 9w USB ran as it should.

The attached file should show the process in MS Iexpress, open Iexpress and use it to open the zipped file. I prefer the free program myself.

#572

Thanks for these instructions to make a self-extracting file :-)

#573

I explored "dd_dus-lxde_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB" today. Got a bit frustrated with password, does it really need a password? I tried to remove it without luck. Maybe I am getting too used to Puppy. Also does the install need to be 8GB? I suppose a Ubuntu ISO will soon be 2GB and there should be room for that. Ahh, I see now this is a Full install, still I would mostly use a drive like this for installing to USB, (or running VBox, which worked OK). Looking for programs that are not required, did I see two word processors and two terminals? I will explore a bit more tomorrow. The more I see the more I like.

#574

Your feedback will improve the system :-)

I can make this UEFI-n-BIOS system log in without a password, but the idea is to be able to use this system as it is in a USB pendrive, in an SSD or HDD (internal or external). I think some people want to log in with a password, and some people without a password. I could even make an OEM system, where the user can select the computer name and user ID (and to log in with or without a password).

I think an installed system really needs at least 8 GB. Otherwise it will be full very soon. This is really a different animal than the 9w systems you have been testing. It brings a long lasting installed system 'in one step', and the user can decide what to install.

#575

[SIZE=4]Two self-extracting 1 GB images of 9w with guidus[/SIZE]

I made self-extracting files for Windows according to C.S.Cameron's recipe and the tool from tp.info-zip.org/pub/infozip/win32/unz552xn.exe

These files are extracted to exactly the same systems as the previous compressed image files

9w-dus-i686.img.xz  # boots via grub and has a menu option 'toram'
9W-DUS_i686.img.xz  # boots via syslinux and works in some HP computers, which do not want to boot the version with grub

As before, the intention is to use Win32DiskImager or some other cloning tool to clone the extracted image into a USB pendrive, and the first step, to extract the image is very easy and needs no extra tool.

An alternative is to download the 9w-dus-i686.iso file and use *Rufus* to create a USB pendrive. It is also straightforward, and I think a reliable method.

-o-

Please download and check that it works to extract these images in Windows :-)

9w-dus-i686.exe - boots via grub and has a menu option 'toram' 9W-DUS_i686.exe - boots via syslinux and works in some HP computers, which do not want to boot the version with grub


$ [COLOR="#0000FF"]ls -l 9*exe[/COLOR]
-rw-rw-r-- 1 sudodus sudodus 263332287 dec 15 13:07 9w-dus-i686.exe
-rw-rw-r-- 1 sudodus sudodus 240253642 dec 15 13:07 9W-DUS_i686.exe
$ [COLOR="#0000FF"]md5sum 9*exe[/COLOR]
6952b55e1d2348d96b5b86a9325d5fa5  9w-dus-i686.exe
a4762ca8ffd292e5ce18cb59662d61e5  9W-DUS_i686.exe
$ [COLOR="#0000FF"]md5sum 9*img[/COLOR]
09940f815c8ed37fcb2e5564e2d6b963  9w-dus-i686.img   # md5sum of the extracted file (as seen by Win32DiskImager)
a13c9a148f8c070353804a7003ec4e21  9W-DUS_i686.img   # md5sum of the extracted file (as seen by Win32DiskImager)
#576

Seeing a file in .exe format makes me cringe a bit, but it seems to get the job done.

Noting that Image Writer is only a few MB I am wondering if 9w-dus and IW could be packaged together, so that clicking the .exe file opens IW with 9w-dus already as the image? Google finds pages for "win32 disk imager portable" but not any actual downloads.

#577

Such a package would make things much easier :-) I don't know how that should be done, and if we would be allowed to do it. I suppose the developer/maintainer of Win32 Disk Imager should be involved.

#578

Just to confirm: 9w-dus does not work with my HP EliteBook but is OK with the Acer. 9W-DUS works with both.

My mission for today is trying to get my Intel ComputeStick to boot the linuxium Lubuntu. with a mkusb USB.

#579

Thanks for the confirmation and good luck with the mission for today :-)

#580

The linuxium Lubuntu install via dus worked well in the Intel ComputeStick. Ian MORRISON has done a great job with the drivers for Ubuntu, better I think, than the Intel ones for Windows 10.

dd_dus-lxde_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB runs out of the box on the ComputeStick, but of course the HDMI audio, bluetooth and WiFi drivers were not there.

An entertainment center might be a great use for that drive.

The USB3 pendrive would not boot on the USB3 socket? nor would Puppy.

#581

Hi C.S.Cameron,

Now that you have tested the different versions of live, persistent live, and install systems to help Windows users convert their computers to linux, which of the versions would you suggest that I *focus on and improve* (maybe with some more tool)? Or should they have about the same focus, because they serve different purposes?

And what about the name - do you still think we should keep the name mkusb

  • for example mkusb-dus and mkusb-classic to be selected in a menu, with a pre-selected choice?
#582

Tough question, simple answer - I like them all.

I like "dd_dus-lxde_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB" because it runs on every computer I tried, even a HP EliteBook and an IntelComputeStick. I have not succeeded in installing the Linuxium drivers to it yet. It also has possibilities as a single purpose drive such as a virtual drive running VBox or as an entertainment center with Firefox , VLC and perhaps Audacity. If it was under 300 MB there would be no contest.

I like 9w-dus for it's download size and the multiple partitions give a feeling of security. but it would not boot the EliteBook or ComputeStick, perhaps if I set the ComputeStick to 32bit it might work, (but would have no HDMI sound drivers or WIFI)

The 9W-DUS worked on everything but the ComputeStick. Same comments as above. I think If there was only one choice allowed, this would be it.

But I am still testing and could change my mind.

#583

Would it help you, and do you think it would help other people if I create and upload a torrent file of the UEFI-n-BIOS image? That might compensate for the size (more reliable to download with a slow or glitchy internet connection).

Can we expect that

  1. some users might let their computers feed the torrent
  2. the users who need the file can manage to get it via torrent?

By the way, I could also make torrent files for the self-extracting files, if we think it would be used.

#584

[SIZE=4]Compressed image of an installed 32-bit Xenial mini system with dus[/SIZE]

I uploaded a system 'between the 9w files and the UEFI-n-BIOS file' in properties and size. This is a compressed image of an installed 32-bit Xenial mini system with dus and gparted similar to the UEFI-n-BIOS system, but it is can be installed to a 4 GB pendrive or memory card. This system needed less extra program packages to work in graphics mode than the UEFI-n-BIOS image, so the compressed images is much smaller, 368 MiB. It boots into a text interface, but LXDE is only 'one Enter key away'. See the screenshots.

[SIZE=3]
9w-dus-i686.exe                                                     252 MiB
9W-DUS_i686.exe                                                     230 MiB

[COLOR="#0000FF"]dd_X32-Txt-Startx-Intl_2016-12-11_4GB.img.xz                        368 MiB[/COLOR]
dd_text_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB.img.xz  542 MiB[/SIZE]

-o-

Please download and check that it works to extract this image, and how it works. Would it be a candidate for a self-extracting file too?

dd_X32-Txt-Startx-Intl_2016-12-11_4GB.img.xz

$ ls -l dd_X32-Txt-Startx-Intl_2016-12-11_4GB.img.xz
-rw-r--r-- 1 sudodus sudodus 385293184 dec 18 17:13 dd_X32-Txt-Startx-Intl_2016-12-11_4GB.img.xz
$ md5sum dd_X32-Txt-Startx-Intl_2016-12-11_4GB.img.xz
07e6767e8715b22e32f848c2f22d9e9b  dd_X32-Txt-Startx-Intl_2016-12-11_4GB.img.xz

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] [B]user: guru password: changeme[/B] [/td][/tr][/table]

#585

I would support a torrent file(s). It is a bummer having a large download fail in the middle.

I still prefer 9W-DUS as a method for Windows users to get dus, small download, works on most computers and simple to recover USB, no pesky ISO9660 partition to get rid of after.

Part of the reason I like dd_text... is that it is 64bit and could be useful for other things as well, VBox for instance.

dd_X32.. sort of seems like a compromise, I will be doing more testing on it today.

#586

[SIZE=4]Torrent files for systems with guidus, that should help people install linux from Windows.[/SIZE]

Now, after the Christmas food, I have uploaded some torrent files. I made them and tested that they work during the days since the previous post in this thread.

You find them at this link: phillw.net/isos/linux-tools/torrents/

Alternate link: drive.google.com/open?id=0BzX-18u3W1sQTTktLUpwLUstVzg

$ [COLOR="#0000FF"]ls -l *.torrent[/COLOR]
-rw-r--r-- 1 sudodus sudodus 38115 dec 23 22:30 9W-DUS_i686.exe.torrent
-rw-r--r-- 1 sudodus sudodus 37878 dec 23 22:26 9W-DUS_i686.img.xz.torrent
-rw-r--r-- 1 sudodus sudodus 38415 dec 23 22:28 9w-dus-i686.iso.torrent
-rw-r--r-- 1 sudodus sudodus 23190 dec 24 18:39 dd_dus-lxde_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB.img.xz.torrent

$ [COLOR="#0000FF"]md5sum *.torrent[/COLOR]
4ae4235b64bb759073e9efc5898f0054  9W-DUS_i686.exe.torrent
2c9b58de362ef32a09e06a85afc266de  9W-DUS_i686.img.xz.torrent
f103dfacad669751f6b271e921eaca39  9w-dus-i686.iso.torrent
2d8035d5a240f357985c8df40b64729e  dd_dus-lxde_16.04-UEFI-n-BIOS_2016-12-12_intel-4-pendrive-7.8GB.img.xz.torrent

I will try to keep a computer running with a torrent client. Referring to the results with other torrents I think it will work. I know that it can seed these torrents inside my local network, but I don't know yet, if it will seed through the firewall of my router and all the way to your computer.

So please try to get one of these files via torrent, and let me know as soon as possible if it works or does not work. When we know that it works, I will ask for help to seed these torrents.

#587

Merry Christmas or whatever: Will give it a try, seems like everyone on the island is trying to message or Skype right now.

#588

The torrent client *transmission* is 'stalled' right now in my running computer, and I don't know if it will be activated via the internet, or if I would have to activate it manually or restart it. Please let me know.

-o-

Christmas Eve is the main celebrating day in my country, and also the day of messages, electronic Christmas cards etc. Anyway, this is an English speaking forum, so I attach my 'card' today on Christmas Day. The light was beautiful on Dec 19, and I could save some of it in the attached greeting, intended for everybody independent of religion and political preferences, even if there is a religious symbol :-)

#589

Always wondered what they did on Christmas in /dev/root. Torrent opens OK but can't find a seed for 9W-DUS. Wrote the image today for OpenELEC using dus. It is an Entertainment Center, I think it is made by the Pi people, there is a 64bit version 171MB download. Might be worth looking at: http://openelec.tv/

#590

I paused and restarted the torrents. Please hang on and check if it will start downloading within the next few minutes!

#591

Torrent downloaded OK, now showing three seeds and two peers.

#592

So the torrent is working :-)

#593

[SIZE=4]dus is mkusb version 12.0.0[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table]

  • dus (alias guidus and mkusb-dus) is mkusb version 12.
  • You can select the classic mkusb interface as mkusb-11

You will notice some changes from version 11 to 12. *dus* is version 12, the default version now.

  • In the GUI interface you can switch between the new interface dus and the classic mkusb-11, version 11. See the attached screenshots.
  • In a text interface you can switch between the new interface dus, mkusb-11, mkusb-nox and mkusb-bas.
$ [COLOR="#0000FF"]mkusb[/COLOR]
---------------------------------------------------------------------
Usage: mkusb [input-file]      # optional parameter
---------------------------------------------------------------------
d:  dus , guidus, mkusb-dus    - New, easy to use
e: Eleven, sudo -H mkusb-11    - Classic user interface
n: NoX,    sudo mkusb-nox      - original text mode
b. Bas,    sudo mkusb-bas      - basic text mode for old/basic linux
q. Quit
---------------------------------------------------------------------
Select version of mkusb (d/e/n/b/q) 
  • There is a new manual, which matches mkusb-dus
man mkusb

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb             # to install
sudo apt-get dist-upgrade              # to upgrade to the current version (alongside all other upgrades)
sudo apt-get install mkusb guidus dus  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (with guidus) via the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and later on via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb and mkusb-nox version 11.1.7 are still in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#594

[SIZE=4]New quick start manual for mkusb version 12, alias dus and guidus[/SIZE]

There is a new version of the Quick start manual and mkusb PPA (See the alternate links, if http://phillw.net/isos/linux-tools/mkusb/ is temporarity down).

#595

I ended up getting both a mkusb and guidus icon. The guidus icon opens up guidus, (V12). The mkusb icon gives a choice between guidus 12 and mkusb 11. All works as expected,,, which is good.

#596

Sounds good :-) I'll wait for feedback from some other people, and I will use it myself for some more time, before I will copy this version into the stable PPA.

#597

C.S.Cameron said: I ended up getting both a mkusb and guidus icon.

The guidus icon opens up guidus, (V12). The mkusb icon gives a choice between guidus 12 and mkusb 11. All works as expected,,, which is good.

Yes .. works here. I can't get the uploader to work in FF (zesty-fully upgraded). Will have to try later with screenshots.

Regards..

#598

ventrical said: Yes .. works here. I can't get the uploader to work in FF (zesty-fully upgraded). Will have to try later with screenshots.

Regards..

Which uploader did not work for you? And which file/package did you try to upload? I want to check if there is bug in zesty for me too.

#599

Just a screenshot using the ubuntu uploader.

#600

I see.

#601

ahh .. try again..

#602

Do you something that you want to be changed (for example the title)?

#603

How about from 'dus' to 'dus-tool'. 'dus' all by itself is more like a mnemonic and may confuse. dus-tool is more linuxy :)

Regards..

#604

I'll think about dus-tool :-)

My thought is that *dus* is short (easy to type) and not occupied by any linux program (at least I did not find any such programs), and dus can be post-fix to mkusb (mkusb-dus in the same way as mkusb-nox and mkusb-bas and mkusb-11).

I often use ``` dus source-file-name


This is more convenient than the previous commands

sudo -H mkusb

or

sudo -H mkusb source-file-name

and

sudo mkusb-nox source-file-name


and it works because sudo is built into dus (with -H when appropriate).
#605

But 'dus-tool' is more specific to new users or intermediate users who have been using linux/ubuntu. It is intuitively assumed that there is a relation with mkusb. At least this is from an instructional development perspective unless you are targeting programmers and developers.

Regards..

#606

Let us listen to the opinions of other people :-)

#607

I still see mkusb as a brand name sorta like Cadillac. When Cadillac put big fins on the rear and started calling it Coupe DeVille, people still new it was a Cadillac. They never abandoned the Cadillac name although it was a totally different car than the '58.

#608

And this is a change in the opposite direction - I removed the big fins from mkusb (versions 9 - 11) and made the basic looking dus, but I see the point. Some people (maybe many people) will still prefer (or should we say remember) the name mkusb: mkusb-dus, as an alternative to mkusb -11 (and mkusb-nox and mkusb-bas).

#609

[SIZE=4]dd_text_16.04-UEFI-n-BIOS_2017-01-15_intel-4-pendrive-7.8GB.img.xz.torrent[/SIZE]

There is a new torrent file that you can use to build your own custom operating system

The dd_text_16.04-UEFI-n-BIOS compressed image file was made up to date, and a torrent file was uploaded in January 2017. It can be used, if you want to start with a light-weight system and install your own selection of program packages - desktop packages, server packages and application packages.

dd_text_16.04-UEFI-n-BIOS_2017-01-15_intel-4-pendrive-7.8GB.img.xz.torrent

Use *mkusb* to install from the downloaded compressed image file to a USB pendrive, a memory card, or maybe an external SSD or HDD.

See details at this link: Installation/UEFI-and-BIOS/torrent

#610

sudodus I have a problem here...did you change the address.

wget http://phillw.net/isos/linux-tools/mkusb/mkusb-installer
--2017-01-19 10:02:45--  http://phillw.net/isos/linux-tools/mkusb/mkusb-installer
Resolving phillw.net (phillw.net)... 176.31.100.215
Connecting to phillw.net (phillw.net)|176.31.100.215|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-01-19 10:02:45 ERROR 404: Not Found.
#611

Phill'w server is temporarily down. He is revamping it and intends to get it up and running during this weekend.

Right now there would be nothing newer to get via phillw.net/isos/linux-tools/mkusb/mkusb-installer compared to what you get via the ppa:mkusb/unstable

But maybe you want something old or something special - please tell me, and I can try to upload it somewhere else.

*Edit:* I think I understand now - you want to install mkusb into Arch (or maybe some other non-ubuntu and non-debian distro). I have no good solution for that right now. Do you think we should design such a method, for example an installer tarball to download, extract, and run something similar to mkusb-installer locally?

#612

Just want the installer for a "New Install" of Arch for friend. Now you know... I know about the Repos for a Ubuntu Install Right??:P Thanks

#613

What do you think about an *installer tarball* to download, extract, and run something similar to mkusb-installer locally? Would it be enough to limit it to guidus alias mkusb-dus - that is without the bells and whistles of mkusb classic (mkusb-11)?

#614

That's alright sudodus...he can just wait for the server to come on line this weekend. (Got to have all the whistles and bells as I am showing you off to this friend.) Just wanted to be sure the address had not been changed on us.:)

#615

I will keep an eye on the server and let you know, when it is up and running again :-)

#616

[SIZE=4]Install dus with guidus alias mkusb version 12 from a tarball[/SIZE]

http://phillw.net is up and running now :-) but the directory structure is changed :-(

I don't know if it is the final structure. If it is, I have a lot of work to modify links at many web pages. Also the scripts called by ``` mkusb-installer


So *@1fallen*, maybe you should consider the tarball at

[help.ubuntu.com/community/mkusb/gui/tarball](https://help.ubuntu.com/community/mkusb/gui/tarball)

I think it is worth testing.

*@everybody*, It would be valuable to get this tarball tested in Ubuntu and other linux distros, also non-debian distros.

[SIZE=4]Graphical tool to create Windows boot drives[/SIZE]

This tarball provides a graphical tool to create Windows boot drives, and should replace mkusb-nox in most cases. See this link

[help.ubuntu.com/community/mkusb#Windows_USB_install_drive](https://help.ubuntu.com/community/mkusb#Windows_USB_install_drive)
#617

This is on a Arch install:

lsb_release -a
LSB Version:    1.4
Distributor ID:    Arch
Description:    Arch Linux
Release:    rolling
Codename:    n/a
sudo ./dus-installer i
[sudo] password for me: 
Do you want to install 'dus' with the graphical user interface 'guidus'? y
install dus ...
'guidus' -> '/usr/bin/guidus'
'guidus.desktop' -> '/usr/share/applications/guidus.desktop'
'dus' -> '/usr/bin/dus'
'dus-live' -> '/usr/sbin/dus-live'
'dus-persistent' -> '/usr/sbin/dus-persistent'
'dus-restore' -> '/usr/sbin/dus-restore'
'dus-wipe' -> '/usr/sbin/dus-wipe'
'mkusb-common' -> '/usr/bin/mkusb-common'
'usb-pack-efi' -> '/usr/bin/usb-pack-efi'
'mkusb.svg' -> '/usr/share/icons/hicolor/scalable/apps/mkusb.svg'
'mkusb.svg' -> '/usr/share/icons/mkusb.svg'
'mkusb.png' -> '/usr/share/icons/hicolor/48x48/apps/mkusb.png'
'dus.8.gz' -> '/usr/share/man/man8/dus.8.gz'
'mkusb_sdir/backup' -> '/usr/share/mkusb/backup'
'mkusb_sdir/grub.cfg' -> '/usr/share/mkusb/grub.cfg'
'mkusb_sdir/grub-win-install.cfg' -> '/usr/share/mkusb/grub-win-install.cfg'
'mkusb_sdir/maybe-problems.txt' -> '/usr/share/mkusb/maybe-problems.txt'
'mkusb_sdir/restore' -> '/usr/share/mkusb/restore'
'usb-pack_sdir/usb-pack_efi.tar.gz' -> '/usr/share/mkusb/usb-pack_efi.tar.gz'
'/usr/bin/mkusb-dus' => '/usr/bin/guidus'
'/usr/share/applications/mkusb-dus.desktop' => '/usr/share/applications/guidus.desktop'
'/usr/share/man/man8/mkusb-dus.8.gz' => '/usr/share/man/man8/dus.8.gz'
which: no pv in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
please install: pv
which: no gdisk in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
please install: gdisk
which: no xterm in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
please install: xterm
which: no dialog in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
please install: dialog

This will complain if you do not have "xterm" and "pv" and "gdisk" and last "dialog" installed first. But after that all is good. Thanks sudodus!;)

#618

Thanks 1fallen, for testing the tarball in Arch :-)

#619

The Thanks belongs to you sudodus. :smile: Just got done burning a Live installer to a USB Drive for a installation. My friend thought this little tool was a needed application for himself also. See your gaining fans all over the place now. Regards

#620

[SIZE=4]mkusb version 12.0.0 and 12.0.1[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] In the stable PPA, ppa:mkusb/ppa, mkusb is upgraded to version 12.0.0 In the unstable PPA, there is now mkusb version 12.0.1: minor bug-fix, removed 'double dus' in two window titles [/td][/tr][/table]

The main change is that from version 11 to 12. *dus* is version 12, the default version now.

  • In the GUI interface you can switch between the new interface dus and the classic mkusb-11, version 11. See this link,

help.ubuntu.com/community/mkusb/12

  • In a text interface you can switch between the new interface dus, mkusb-11, mkusb-nox and mkusb-bas.
$ [COLOR="#0000FF"]mkusb[/COLOR]
---------------------------------------------------------------------
Usage: mkusb [input-file]      # optional parameter
---------------------------------------------------------------------
d:  dus , guidus, mkusb-dus    - New, easy to use
e: Eleven, sudo -H mkusb-11    - Classic user interface
n: NoX,    sudo mkusb-nox      - original text mode
b. Bas,    sudo mkusb-bas      - basic text mode for old/basic linux
q. Quit
---------------------------------------------------------------------
Select version of mkusb (d/e/n/b/q) 
  • There is a new manual, which matches mkusb-dus
man mkusb
  • There is a quick start manual for each version, 11 and 12,

mkUSB-quick-start-manual-11.pdf mkUSB-quick-start-manual-12.pdf

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb                          # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and later on via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 12.0.0 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following link,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

#621

[SIZE=4]General comments about upgrading[/SIZE]

Normally you want to keep an installed system up to date automatically, via a GUI application or the following command lines,

sudo apt-get update
sudo apt-get dist-upgrade

Then all installed packages (from standard repositories and PPAs) will be upgraded.

But a *live-only or persistent live system* can be damaged by such general updates & upgrades. Instead it is recommended to keep most program packages as they are, and only upgrade packages when really necessary. The following command lines work, when you want to update & upgrade the program packages that belong to mkusb without affecting the other program packages.

sudo apt-get update
sudo apt-get install mkusb guidus dus mkusb-common
sudo apt-get install mkusb-nox

[SIZE=4]Upgrading from mkusb 11 to 12[/SIZE]

Re-install also the package mkusb-common in order to upgrade the shellscript mkusb-start.

sudo apt-get install --reinstall mkusb guidus dus mkusb-common

If there are still problems because of the change from mkusb version 11 to 12, you can purge mkusb

sudo apt-get purge mkusb

and also remove mkusb files manually with

sudo rm /usr/sbin/{mkusb*,dus}
sudo rm /usr/bin/mkusb*
sudo rm /usr/share/mkusb/

After that it should work according to the instructions above.

#622

[SIZE=4]mkusb version 12.0.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] The main change is improved logic to manage usb-pack-efi when creating persistent live drives. [/td][/tr][/table]

[*] sudo password managed better at start, dus no longer asks for usb-pack-efi but dus-persistent does

[*] improved logic when missing usb-pack-efi for distros without 'apt-get' [*] selection of usb-pack-efi when grub.cfg is missing [*] opensuse: logic for grub2-install (in grubi386-pc)

  • dus:
  • dus-persistent:

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb                          # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 12.0.0 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#623

Just wanted to say these MKUSB tools are awesome and working fine in Mint 18.1 Serena. It's insanely frustrating finding advanced ISO/USB tools for Mint that actually work right. Unetbootin is still producing unbootable flash drives and went full retard on persistence, at least in the repo version. Then there isn't another good tool in sight until you hit Fedora. This fills the gap. Thanks.

#624

I'm glad that mkusb works well for you, *nannerpuss* :-)

Which version do you prefer, 11 (classic) or 12 (dus)?

#625

[SIZE=4]mkusb version 12.0.3[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] The only change is in dus-persistent: label=usbboot for partition #3 [/td][/tr][/table]

dus-persistent: label=usbboot for partition #3 (instead of a variable label depending on the distro, version and flavour). This is stable and works also when reading the system from a block device.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb                          # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 12.0.0 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#626

[SIZE=4]mkusb version 12.0.4[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

guidus.desktop and mkusb.desktop: added %f to the exec lines mkusb-start: added "$@" [/td][/tr][/table]

  1. dus: modified p_checkpoint: 'src_orig=' to make it easy to change the source file
  2. modifications to transfer source file as parameter for integration with file browsers

These modifications make it easier to integrate mkusb (both version 11 and version 12) with a file browser.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb                          # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] [TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] *Edit:* mkusb version 12.04 was copied to the stable PPA 'ppa:mkusb/ppa' (2017-02-19) [/td][/tr][/table]

mkusb version 12.0.4 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#627

[SIZE=4]Ubuntu can be installed to the pendrive it was booted from[/SIZE]

It is *easier and more convenient to use two USB pendrives*, if you want to create an installed system in a USB pendrive.

However, it is *possible to install Ubuntu into to the pendrive it was booted from*. Use the boot option toram and unmount all partitions in the drive that you booted from. After that you can use the standard installer and install into the same pendrive.

If there is an internal drive, things may be more tricky in order to avoid writing bootloading things to the internal drive, but this is not due to the fact that it is installed to the same drive as the system was booted from.

See the following links,

Boot options

How to unmount a live DVD/USB?

Can Ubuntu be installed to the pendrive it was booted from?

#628

[SIZE=4]mkusb version 12.0.5[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] preinst and postinst added to the debian directory debian/control - mkusb - depends:... mkusb-common (>= 12.0.5) ... [/td][/tr][/table]

There is a problem when upgrading from version 9-11 to version 12, because some files, that belonged to the package mkusb was moved to a separate packade mkusb-common, used also by dus. The problem is solved by letting mkusb-common install to file names mkusb12... and directory name mkusb12, and after installation copy the files to the corresponding file names mkusb... and directory name mkusb12.

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb                          # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 12.0.5 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#629

[SIZE=4]Compressed image files with a persistent live system and mkusb[/SIZE]

Use a cloning tool, for example *Disks* or *mkusb* in linux, or 7-zip and Win32 Disk Imager in Windows to expand and {copy/clone/flash/burn/restore/install} this kind of files into a USB pendrive, a flash memory card or a hard disk drive or SSD with *at least 8 GB*.

[SIZE=3]Lubuntu 16.04.2 LTS (32 bit and 64 bit) with mkusb version 12.0.4[/SIZE]

Download the following compressed image files from this link to google drive,

dd_Lubuntu_16.04.2_i386_persist-live_mkusb-12.0.4_7.8GB_msdos-pt.img.xz for 32 & 64 bit in BIOS & UEFI mode, *not* secure boot

dd_Lubuntu_16.04.2_amd64_persist-live_mkusb-12.0.4_7.8GB_guid-pt.img.xz for 64 bit in BIOS & UEFI mode, works in secure boot

Check that the download was good with *md5sum*

a3473ff10368d1a2a0f471687ad2247b  dd_Lubuntu_16.04.2_amd64_persist-live_mkusb-12.0.4_7.8GB_guid-pt.img.xz
63baa0f95b4143e8e86670b75adffd58  dd_Lubuntu_16.04.2_i386_persist-live_mkusb-12.0.4_7.8GB_msdos-pt.img.xz
#630

[SIZE=4]mkusb version 12.0.6,7[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table]

  • mkusb-select: made to print versions directly with -v
  • mkusb.8: The manual made up to date (12.0.6)
  • mkusb.8: The manual improved (12.0.7)

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb                          # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 12.0.7 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#631

Thanks sudodus! I have been seeing this a bit lately and today:

Connecting to phillw.net|xxx.xx.100.215|:80... failed: Connection refused

All is good using The PPA on Ubuntu but for Arch..not so much.:(

#632

I know. Phill revamped his server, that had been very stable for years, around New Year, and he has not reached a stable state yet with the new system.

If *mkusb version 12 alias dus* is OK, you can get a version that is current enough via this link,

mkusb/gui/tarball

The current version (2017-03-15) in the tarballs was created 2017-02-11 and is *dus 12.0.4*. The versions 12.0.5 and 12.0.6 contain only fixes outside *dus* itself (related to mkusb and to the debian packaging), so you will not miss anything concerning the features and capabilities of *dus*.

#633

sudodus said: I know. Phill revamped his server, that had been very stable for years, around New Year, and he has not reached a stable state yet with the new system.

Yep I remember you telling me this. Just wanted something tell the others I have shown the "phillw.net" method is all. They message me now.;) LOL Thanks

#634

You are welcome :-)

And please let me know, whenever there is some other problem with mkusb or maybe some new feature that might be useful (and possible to add).

#635

[SIZE=4]mkusb version 12.0.8[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table]

  • dus-live: improved logic for running and reporting gpt_fix
  • dus-persistent: function menu_name when reading from block device
  • mkusb-11: fix to transfer source file as parameter and via 'selected'
  • mkusb.8: The manual made up to date

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/unstable
sudo apt-get update
sudo apt-get install mkusb                          # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 12.0.7 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#636

[SIZE=4]mkusb version 12.0.9[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

[/td][/tr][/table]

  • dus, function p_list_drives: skipping floppy: grep -v zram --> grep -v -e zram -e ^fd (to fix a bug that affects old computers)

[hr][/hr] You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

and via this link: mkusb/gui#from_phillw.net

[hr][/hr] mkusb version 12.0.9 is in the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#637

Hello Sudodus,

I attempted to use *mkusb* today and encountered a slight discrepancy. I had selected the source and the destination, but when I got to the final checkpoint there was nothing displayed in the large whitespace area that normally shows ones choices. A screenshot is attached. contents of mkusb.log shown below.


The mkusb console window displays,
or the file ~/mkusb.log contains:
output from the engine behind the zenity curtain.
---------------------------------------------------------------------------
start [mkusb 10.6.6] @ 2017-04-08 06:00:15 PM
---------------------------------------------------------------------------
Current directory=/home/hugh
main: usbonly=true
main: liveonly=true
No input file specified yet
main: source=''
TERM=unknown
ubuntu
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/hugh/Downloads/ubuntu-16.04.2-server-amd64.iso
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /dev/loop0 is write-protected, mounting read-only
disk_name_type=desktop
Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 _found_ in iso-file
Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 _not_ in any possible target drive
Booted from: /dev/sda
ans=1
---------------------------------------------------------------------------
menu_shell:
select_source: imagefile=/home/hugh/Downloads/lxle_16_04_2_64.iso
---------------------------------------------------------------------------
menu_shell:
imagefile=/home/hugh/Downloads/lxle_16_04_2_64.iso
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /dev/loop0 is write-protected, mounting read-only
disk_name_type=desktop
LXLE Linux _found_ in iso-file
LXLE Linux _not_ in any possible target drive
Booted from: /dev/sda
ans=1
---------------------------------------------------------------------------
menu_shell:
Cleanup after mkusb finished :-)
---------------------------------------------------------------------------
Total time used [by mkusb] = 258 s; 00:04:18
login attempt 1
#638

Hello him610,

I notice that you are using an old version of mkusb. Please update it to the current version, 12.0.9 according to post #634. If you still have the same or a similar problem, I will try hard to fix the bug, and in that case I will also need help from you (that you test various things that I suggest and share your results).

-o-

At this stage I can only guess, and I guess that there is a problem with the graphics. What graphics chip/card are you using, and what graphics driver?

#639

[SIZE=4]mkusb version 12.1.0[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

  • dus, bugfix for Debian Jessie in function p_source: lsblk -Jo ... --> pcalx lsblk -Po ...

    p_calx lsblk -Po name,fstype|grep iso9660|cut -d \" -f 2|grep -m1 4$|sed s#^#/dev/#
    p_calx lsblk -no label $stmp|head -n1
    p_calx lsblk -o model,name,size,fstype,label,mountpoint|grep -e '^[^ ]' -e iso9660

[/td][/tr][/table]

  • artful, there are versions for artful (to become Ubuntu version 17.10) in ppa:mkusb/ppa as well as in ppa:mkusb/unstable.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.0.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
sudo apt-get dist-upgrade                           # to upgrade to the current version (alongside all other upgrades)

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#640

All is good from: [URL="https://help.ubuntu.com/community/mkusb/gui#from_phillw.net"]from_phillw.net ;) [/URL]

#641

Hi 1fallen,

Yes, Phill's server works again, so now you and your friends can get the whole mkusb up to date for arch :-)

But I updated the tarballs too, as an alternative (where to get dus).

#642

sudodus said: Hi 1fallen,

Yes, Phill's server works again, so now you and your friends can get the whole mkusb up to date for arch :-)

_But I updated the tarballs too, as an alternative (where to get dus)._

Very nice! :D Thanks sudodus :KS

#643

[SIZE=4]mkusb version 12.1.1[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb, dus-persistent 12.1.1

. grub-n-iso: .. 'tweak 3 grub.cfg': search --set=root --fs-uuid instead of (hd0,4) .. 'hint for debian live': user: 'user', password: 'live' . select_boot_system: simpler search for "*amd64*" (for Ubuntu 17.04) . show_result: minor cosmetic fix (variable width of zenity window) [/td][/tr][/table]

  • fixes for Ubuntu 17.0.4 and Debian Jessie and for computers that do not boot to (hd0)

'tweak 3 grub.cfg':

search --set=root --fs-uuid <the-UUID-of-partition-no-4>

is a major modification, which might cause problems in some cases, that I have not tested. So I will leave the tarballs at version 12.1.0 for a while.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.0.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#644

Please test *dus version 12.1.1* described at this link

*In particular, check that it can create a working persistent live drive* with

'tweak 3 grub.cfg': search --set=root --fs-uuid instead of (hd0,4) in grub.cfg.

search --set=root --fs-uuid <the-UUID-of-partition-no-4>

This is a major modification, which might cause problems in some cases. So this version should be tested extensively before making it the default version in the stable PPA.

[hr][/hr] Note 1: Remember that *mkusb-dus* can only make *persistent live* drives from

  • Ubuntu, Ubuntu community flavours and some respins based on Ubuntu
  • Debian Jessie, ToriOS and maybe some respins based on Debian Jessie

*mkusb-dus can make live-only drives from all hybrid iso files*, and most modern linux distros provide hybrid iso files.

Note 2: This version with the 'search tweak' was made in response to feedback at AskUbuntu and I found the solution at the Arch website.

#645

Hi sudodus, Thanks for all your work. Have tried many methods to create a persistent live usb over the years with varying success. Worked without a hitch with the easy to follow dialogs. Used mkusb stable(12.1.1) to install Lubuntu 16.04.

Just a question on how much space should I allocate for persistence on a 4gb flash drive or would the default mkusb setting be ok? I used 25%. Also what's the difference running in "persistent live to ram" mode? I have 4gb of ram.

#646

[SIZE=5]Use only operating systems that are supported, 'current versions'[/SIZE]

When a linux distro is getting close to end of life, please try to find a new version or another distro with support for a fair interval of time, and that works in the computer. After end of life there will be no updates, not even security updates, so the connection to internet is no longer secure.

Notice that the standard Ubuntu LTS versions are supported for 5 years, while the LTS versions of the other flavours are supported for 3 years. The other (non-LTS) versions are only supported for 9 months.

See this link, http://www.ubuntu.com/info/release-end-of-life

You can use *mkusb-dus* to create a USB boot drive or a memory card with a new operating system to try (and install if it works well).

[SIZE=5]mkusb-dus version 12.1.2 - what works 2017-05-02[/SIZE]

[SIZE=4]A. Live-only[/SIZE]

A.1 [B][I]mkusb-dus can make live-only drives from all hybrid iso files, and most modern linux distros provide hybrid iso files. [/I][/B] A.2 Hybrid iso files

  • All current Ubuntu iso files
  • 12.04 iso files except early mini.iso files

A.3 Possible to make into hybrid iso files

  • Ubuntu 10.10 and newer desktop iso files

Examples:

isohybrid ubuntu-10.10-desktop-i386.iso
isohybrid ubuntu-11.04-desktop-amd64.iso

A.4 Impossible to make into hybrid iso files

  • Ubuntu 10.04, 10.04.x and older iso files

But mkusb-dus can make a persistent live drive of Ubuntu 10.04.1 LTS

[SIZE=4]B. Persistent live[/SIZE]

B.1 Linux distributions, 'distros'

mkusb-dus can only make persistent live drives running in and creating from 'desktop' or 'live' iso files of the following distros

B.1.1 *Ubuntu*, Ubuntu community flavours and some respins based on Ubuntu B.1.2 *Debian Jessie, ToriOS* and maybe some respins based on Debian Jessie

B.2 Versions

B.2.1 *Current versions*

[B][I]mkusb-dus can make persistent live drives in and from current versions of Ubuntu[/I][/B] (not versions that have passed end of life)

B.2.2 *Running mkusb-dus in Ubuntu 12.04* (which has passed end of life)

search --set=root --fs-uuid <the-UUID-of-partition-no-4>

does not work because the UUID cannot be detected. Instead the old

set root=(hd0,4)

method is used (in grub.cfg), which works in most cases, but the persistent live drive may fail in some new computers running in UEFI mode.

Working persistent live drives can be created with 12.04 itself as well as of the current releases including Artful (to become 17.10).

B.2.3 *Running mkusb-dus in Ubuntu Artful* (to become 17.10)

B.2.3.1 Persistent live drives made from Ubuntu 12.04.1 LTS do not boot with persistence because the casper-rw partition cannot be overlayed, but they boot live only. (It does not work with the precise kernel.)

B.2.3.2 Persistent live drives made from Ubuntu 12.04.5 LTS boot with persistence. (It works with the trusty kernel.)

B.2.4 *Running mkusb-dus in Ubuntu 16.04.1 LTS* (currently the version with the longest lifetime)

Persistent live drives made from Ubuntu 10.04.1 LTS, 12.04.1 LTS and Artful (to become 17.10) boot with persistence.

#647

guber2 said: Just a question on how much space should I allocate for persistence on a 4gb flash drive

or would the default mkusb setting be ok? I used 25%. Also what's the difference running in "persistent live to ram" mode? I have 4gb of ram.

I would use all available drive space for persistence in a 4 GB pendrive (select 100%). The reason to use less is that you need drive space to exchange data with computers running Windows. In your case the 'usbdata' partition occupies the remaining 75% of the available drive space. Do you need that?

"Persistent live to ram" means that the image of the iso file is not mounted as a partition, but copied to RAM, which makes reading from it much faster. But it will use RAM, so that less RAM will be available for other purposes. So if you intend to use a lot of RAM for your application programs, it might be a bad idea. If there is a separate swap partition, for example in the internal drive, the system will swap instead of fail, when you run out of RAM, but it will be very slow.

Try (and check how much RAM is used) with and without "to ram", and use the method that works best for you.

From the output of ``` df -h

Filesystem Size Used Avail Use% Mounted on /dev/sda4 911M 911M 0 100% /cdrom # standard persistent live (without "to ram") /dev/shm 956M 911M 45M 96% /cdrom # persistent live to ram

#648

[SIZE=4]mkusb version 12.1.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb, dus-persistent 12.1.2

'tweak 3 grub.cfg': search --set=root --fs-uuid instead of (hd0,4) does not work when running mkusb-dus in Ubuntu 12.04 because the UUID of the iso9660 file system cannot be identified. The old method with set root=(hd0,4) is selected as a fallback. [/td][/tr][/table]

'tweak 3 grub.cfg':

search --set=root --fs-uuid <the-UUID-of-partition-no-4>

is a major modification, which might cause problems in some more cases, that I have not tested. So I will leave the tarballs at version 12.1.0 for a while.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.0.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#649

Ahh ok, looking in disks I found I had created 3gb of free space. Just me not understanding how persistence works.

Reinstalled using 100% pesistence. Gave a failed message at the end but the usb boots.

#650

@guber2,

Interesting :-)

Please tell me which *linux distro and version* you are running, when you use mkusb-dus, and I will debug it and try to make it work correctly (not report an error, if/when it works).

Also, please *update & upgrade dus to version 12.1.2* according to post #646 or get dus-persistent directly from http://phillw.net/isos/linux-tools/mkusb and try again.

sudo cp dus-persistent /usr/sbin
#651

I am using Ubuntu Gnome 17.04. Upgraded mkusb to 12.1.2 and didn't get the error message at end.

#652

guber2 said: I am using Ubuntu Gnome 17.04.

Upgraded mkusb to 12.1.2 and didn't get the error message at end.

That's good, mkusb-dus *should* work well in Ubuntu Gnome 17.04.

12.1.1 was a bugfix to solve a problem for a particular user, and I could guess that it would be necessary to modify it at least once to make it work correctly in all relevant cases. Thanks for your feedback :-)

#653

sudodus said: That's good, mkusb-dus *should* work well in Ubuntu Gnome 17.04.

12.1.1 was a bugfix to solve a problem for a particular user, and I could guess that it would be necessary to modify it at least once to make it work correctly in all relevant cases. Thanks for your feedback :-) Actually didn't realize I added the unstable ppa. Just skimmed the first post in this thread. All good.... it's much more fun being unstable. 8-[ Thanks.

#654

@guber2,

I have modified the beginning of the first post in this thread to avoid getting the unstable PPA by mistake.

#655

12.1.2 Does not recognize USB. [s]Cannot copy and past from terminal in the usual manner so it's pretty well useless to test here.[/s]

I'll try another machine later on.

Regards..

edit- different USB used on same machine.

#656

Other USB on same machine - now booted live - peristent


System:    Host: mythbuntu Kernel: 3.13.0-19-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: Xfce 4.11.4 (Gtk 2.24.22) Distro: Ubuntu 14.04 trusty
Machine:   Mobo: ASUSTeK model: P5B-E version: Rev 1.xx Bios: American Megatrends version: 1807 date: 04/15/2009
CPU:       Dual core Intel Core2 Duo CPU E8400 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11980.8 
           Clock Speeds: 1: 2995.200 MHz 2: 2995.200 MHz
Graphics:  Card: NVIDIA GF119 [GeForce GT 610] bus-ID: 01:00.0 
           X.Org: 1.15.0 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1440x900@59.9hz 
           GLX Renderer: Gallium 0.4 on NVD9 GLX Version: 3.0 Mesa 10.1.0 Direct Rendering: Yes
Audio:     Card-1: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 
           Card-2: NVIDIA GF119 HDMI Audio Controller driver: snd_hda_intel bus-ID: 01:00.1 
           Sound: Advanced Linux Sound Architecture ver: k3.13.0-19-generic
Network:   Card: Qualcomm Atheros Attansic L1 Gigabit Ethernet driver: atl1 ver: 2.1.3 bus-ID: 03:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1508.3GB (-) 1: id: /dev/sda model: WDC_WD15EURS size: 1500.3GB temp: 29C 
           2: USB id: /dev/sdb model: v255w size: 8.0GB temp: 0C 
Partition: ID: / size: 4.8G used: 349M (8%) fs: overlayfs 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 35.5C mobo: 36.0C gpu: 38.0 
           Fan Speeds (in rpm): cpu: 4245 psu: 0 sys-1: 0 sys-2: 0 
Info:      Processes: 167 Uptime: 16 min Memory: 520.6/3009.4MB Runlevel: 2 Gcc sys: 4.8.2 
           Client: Shell (bash 4.3.0) inxi: 1.9.17 
mythbuntu@mythbuntu:~$ 

It certainly offers a lot of end_user options in the GUI which is not a bad thing. There is one interval that I think is not clear. I'll send up a comment on that in next post.

I'll let this machine run for a few hours , reboot and see how stable it is.

Nice work sudodus.

#657

Ok.. loaded unstable on 17.10

Will...,

  1. Attempt to make live-persistent usb 17.04 gnome-desktop
  2. Attempt to uprade USB to 17.10 live.

Regards..

#658

@ventrical,

As you can see in post #644, B.2.3, it works for me to create persistent live drives from the current versions of Ubuntu, even 12.04.5 LTS but not 12.04.1 LTS, when running mkusb-dus in Artful alias 17.10. So I think that you will succeed in creating a working persistent live drive with 17.04 (even if I have not tested gnome-desktop).

But I am afraid that it will not work to upgrade the persistent live system from 17.04 to 17.10. If I understand correctly, persistent live drives are suitable for storing data, tweaking the user settings and installing some application programs. It is a bad idea to do general update & upgrade, and it is impossible to upgrade the kernel. Such adventures might break the system.

The following methods can save what can be saved and get back to a working persistent live system:

A. Repair

  1. Boot into a live-only session (select the live-only alias 'Try Ubuntu' menuentry)
  2. Keep /upper/home and remove everything else in the casper-rw partition
  3. Boot into a persistent live session and reinstall application programs (and global settings if any)

B. Use the backup, if you created backup(s) with the built-in script 'backup'. See this link. Of course you can also use rsync or some other tool to backup the content of the casper-rw partition.

  1. Boot into a live-only session (select the live-only alias 'Try Ubuntu' menuentry)
  2. Remove everything in the casper-rw partition
  3. Use the built-in restore script 'restore'
#659

OK.. thanks.

I ran into some problems on my UEFI system. My Boot Options section of BIOS gives me three instances of my Kingston Data Traveller USB stick and they are all the same so I have to blindly choose which one. One goes into BIOS , one goes into Live option and the other fails with squashfs run.

Before you adress that question .. I have ubuntu-mate 17.04 live-persistent and it keeps asking for password when I do something that needs root. I thought it was "ubuntu". What is password.?

regards..

#660

I think the password has zero length. Press the Enter key directly. At least this works in Lubuntu including 17.04.

Thanks for testing :-)

Edit:

I started a torrent to get ubuntu-mate-17.04-desktop-amd64.iso and test. I think *you should need no password* to run sudo (or gksudo) or applications that use pkexec. This is the case in Ubuntu MATE too, when I test it. I think something is wrong, when it asks for a password (unless you have set a password as described by @1fallen).

#661

ventrical said: I have ubuntu-mate 17.04 live-persistent and it keeps asking for password when I do something that needs root. I thought it was "ubuntu". What is password.?

regards..

I've seen this from time to time also. To get around this, just open a terminal and execute the following command:

sudo passwd ubuntu

follow the prompts and set a password; the current password is blank so if it asks for a password here or for sudo, just press enter.

#662

1fallen said: I've seen this from time to time also.

To get around this, just open a terminal and execute the following command:

sudo passwd ubuntu

follow the prompts and set a password; the current password is blank so if it asks for a password here or for sudo, just press enter.

Thanks :)

btw .. it will report 'wrong password' if I leave blank. At least thats for MATE. Don't know about the others. Of course will try later to test. it worked just excellent using MythUbuntu. I loaded the unstable/ppa: on yakkety ubuntu-desktop. Created persistive 14.04 myth, still running beautiful.

#663

This is strange, ventrical.

My first guess would be that either the download failed or there is some corruption in the casper-rw partition.

A. Basic checks

  1. Did you check the iso file with md5sum?
  2. Did you check with the grub menuentry 'Check disk for defects'?
  3. Did you check with the grub menuentry 'Try Ubuntu MATE without installing'?

B. If the three checks above are successful, I suggest that you remove the content from the casper-rw partition and try again (to add some data, do some tweaks and install some program package, for example mkusb and dus from ppa:mkusb/unstable).

  1. What happens with sudo the first time you boot persistent live with a clean casper-rw partition?
  2. What happens with sudo after rebooting persistent live again?

If you encounter the problem with sudo again, adding your experience and that of @1fallen would suggest that there is something fishy with the management of elevated permissions in Ubuntu MATE when running persistent live.

-o-

Ubuntu MATE 17.04 works persistent live for me after several reboots. I am testing the amd64 version and it works both in UEFI and BIOS mode.

See the screenshots.

#664

[SIZE=4]mkusb version 12.1.3[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.1.3

. p_persistent: suggest to select an iso file for dus-persistent or try to clone if an image file . main: code to skip to cloning (calling the function p_live), when a compressed image file is entered as parameter. [/td][/tr][/table]

  • dus: bugfix to direct the user to clone [compressed] image files and create persistent live drives only from iso files

There is output, a zenity window and red text to the console window, when this is activated. See the attached screenshot. [hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.0.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#665

[SIZE=4]mkusb version 12.1.4[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.1.4

dus, dus-live, dus-persistent: *fixes for some unusual file names*, for example t1.img.xzxx.img.xz and t2.isoxx.iso, where the logic to identify the file extensions failed.

           ${source/.iso} --> ${source%.iso}
           ${source/.img} --> ${source%.img}
           ${source/.img.[gx]z} --> ${source%.img.[gx]z}

[/td][/tr][/table]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.0.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#666

[SIZE=4]mkusb version 12.1.5[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.1.5

. backup: A small but important improvement to keep automounting the usbdata and casper-rw partitions in some Ubuntu versions and Ubuntu based distros, for example LXLE 16.04.2 LTS. the new version has two new options, '--one-file-system' and '--exclude=upper/media'.

  • backup and restore: debugged and improved a lot by testing extensively in a persistent pendrive.
diff backup backup-1
169c169
< sudo tar --one-file-system --exclude=upper/media -cvzf "$tdir/$tarball" .
---
> sudo tar -cvzf "$tdir/$tarball" .

. restore: Several changes to make the usage easier and more reliable, when restoring also from other directories than the default '/media/$USER/usbdata'.

See this link for more details: **Backup and restore of persistent overlay data** [/td][/tr][/table]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.1.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#667

This is the first I have seen this sudodus

error: target not found: grub-pc
error: target not found: mount
error: target not found: xz-utils

So i have a failed install ATM...(On Arch)...Have not booted to Ubuntu yet to try.

#668

Hi 1fallen,

Please describe how to provoke the bug, so that I can get to fix it, if possible :-P

Version of OS, version of mkusb, and what to select to get there.

May I guess that you do it in an installed system in UEFI mode - where there is a conflict between grub-efi and grub-pc in Ubuntu, maybe also in Arch.)

See this link for a discussion about that: mkusb persistent: Using data from the source iso file

-o-

I don't know about the packages mount and xz-utils. Maybe mount and xz come with different names in Arch (and I think you have them already).

#669

This part works fine:

wget http://phillw.net/isos/linux-tools/mkusb/mkusb-installer

This is where the errors come to light:

bash mkusb-installer

Script generates as such:

2017-05-10 09:00:07 (127 KB/s) - &#8216;dus&#8217; saved [43947/43947]

dus: md5sum OK
dus-live: md5sum OK
dus-persistent: md5sum OK
dus-restore: md5sum OK
dus-wipe: md5sum OK
Install if necessary the help packages gdisk grub-pc pv xterm wmctrl zenity
pv [and maybe wmctrl(?) ]needs the 'community' repository
warning: pv-1.6.0-2 is up to date -- reinstalling
warning: parted-3.2-5 is up to date -- reinstalling
warning: gptfdisk-1.0.1-2 is up to date -- reinstalling
warning: util-linux-2.29.2-2 is up to date -- reinstalling
warning: coreutils-8.27-1 is up to date -- reinstalling
**error: target not found: mount**
warning: gzip-1.8-2 is up to date -- reinstalling
**error: target not found: xz-utils**
warning: xterm-327-1 is up to date -- reinstalling
warning: rsync-3.1.2-2 is up to date -- reinstalling
warning: tar-1.29-2 is up to date -- reinstalling
warning: wmctrl-1.07-4 is up to date -- reinstalling
warning: zenity-3.24.0-1 is up to date -- reinstalling
**error: target not found: grub-pc**
guidus.desktop: md5sum OK
/usr/bin/xterm
Try if any of the legacy desktop files works for you!
Keep only the best one :-)
mkusb-legacy.desktop: md5sum OK
mkusb-legacy-root.desktop: md5sum OK
mkusb-legacy-sudo.desktop: md5sum OK
mkusb.svg: md5sum OK
mkusb.svg: md5sum OK
mkusb.png: md5sum OK
dus.svg: md5sum OK
dus.svg: md5sum OK
dus.png: md5sum OK
dus.8.gz: md5sum OK
mkusb.8.gz: md5sum OK
mkusb-nox.8.gz: md5sum OK

Done, test with the following small ISO files in
the directory /home/me
'mini.iso' and 'TinyCore-5.4.iso'

So no joy. Version I have now to finish my work..."mkusb-11" I had to use this to get mkusb-11 back,

sudo rm /usr/sbin/{mkusb*,dus}
sudo rm /usr/bin/mkusb*
sudo rm -r /usr/share/mkusb/

If you need more let me know.:) No UEFI...I'm in legacy mode here

#670

Well after some thought and a little trickery here. (I won't mention the trickery part here) I finally got it to work on Arch. I wonder what has changed though...as this is not a proper install method. :confused: Specs if needed:

inxi -Fxz
System:    Host: me-pc Kernel: 4.10.13-1-ARCH x86_64 (64 bit gcc: 6.3.1)
           Desktop: MATE 1.18.0 (Gtk 3.22.13) Distro: Arch Linux
Machine:   Device: desktop Mobo: HP model: 828A v: 1.01
           UEFI [Legacy]: AMI v: F.14 date: 09/19/2016
CPU:       Quad core Intel Core i5-6400 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 21704
           clock speeds: max: 3300 MHz 1: 2626 MHz 2: 1858 MHz 3: 2600 MHz
           4: 2783 MHz
Graphics:  Card-1: Intel HD Graphics 530 bus-ID: 00:02.0
           Card-2: NVIDIA GF114 [GeForce GTX 560 Ti] bus-ID: 01:00.0
           Display Server: X.Org 1.19.3 driver: nvidia
           Resolution: 1920x1080@60.00hz
           GLX Renderer: GeForce GTX 560 Ti/PCIe/SSE2
           GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes
Audio:     Card-1 NVIDIA GF114 HDMI Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Card-2 Intel Sunrise Point-H HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.10.13-1-ARCH
Network:   Card-1: Intel Device 24fb driver: iwlwifi bus-ID: 03:00.0
           IF: wlp3s0 state: up speed: N/A duplex: N/A mac: <filter>
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 04:00.0
           IF: enp4s0 state: down mac: <filter>
Drives:    HDD Total Size: 3000.6GB (11.4% used)
           ID-1: /dev/sda model: WDC_WD5000AAKS size: 500.1GB
           ID-2: /dev/sdb model: WDC_WD20EADS size: 2000.4GB
           ID-3: USB /dev/sdc model: 2115 size: 500.1GB
Partition: ID-1: / size: 445G used: 46G (11%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 13.76GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
           ID-3: swap-2 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/zram0
Sensors:   System Temperatures: cpu: 30.0C mobo: N/A gpu: 0.0:38C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 179 Uptime: 32 min Memory: 1130.5/11930.1MB
           Init: systemd Gcc sys: 6.3.1
           Client: Shell (bash 4.4.121) inxi: 2.3.8 
#671

Thanks, I will look into mkusb-installer's 'subscript' mk_install-and-test-mkusb.bash.

#perms    	size	date      	time 	file-name
-rwxrwxr-x	4,5K	2014-10-02	14:37	"mkusb-installer"
-rw-r--r--	14K	2017-02-11	23:23	"mk_install-and-test-mkusb.bash"

It in Arch - installed and up to date, I understand.

#672

sudodus said: Thanks, I will look into mkusb-installer's 'subscript' mk_install-and-test-mkusb.bash.

#perms        size    date          time     file-name
-rwxrwxr-x    4,5K    2014-10-02    14:37    "mkusb-installer"
-rw-r--r--    14K    2017-02-11    23:23    "mk_install-and-test-mkusb.bash"

It in Arch - installed and up to date, I understand. Thanks for the extra effort and time... i have added to your work-load. :)

-rw-r--r--  1 me   me        13607 Feb 11 15:23  mk_install-and-test-mkusb.bash
-rw-r--r--  1 me   me         4528 Oct  2  2014  mkusb-installer
-rw-r--r--  1 me   me         4528 Oct  2  2014  mkusb-installer.1
-rw-r--r--  1 me   me         4528 Oct  2  2014  mkusb-installer.2
-rwxr-xr-x  1 root root        516 May 10 10:29  mkusb-legacy.desktop
-rwxr-xr-x  1 root root        259 May 10 10:29  mkusb-legacy-root.desktop

EDIT: All is good even with the method I used to install it.

Filesystem      Size  Used Avail Use% Mounted on
sysfs              0     0     0    - /sys
proc               0     0     0    - /proc
udev            5.9G     0  5.9G   0% /dev
devpts             0     0     0    - /dev/pts
tmpfs           1.2G   11M  1.2G   1% /run
/dev/sde        1.5G  1.5G     0 100% /cdrom
/dev/loop0      1.5G  1.5G     0 100% /rofs
aufs            5.9G   32M  5.8G   1% /
securityfs         0     0     0    - /sys/kernel/security
tmpfs           5.9G  172K  5.9G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           5.9G     0  5.9G   0% /sys/fs/cgroup
cgroup             0     0     0    - /sys/fs/cgroup/systemd
pstore             0     0     0    - /sys/fs/pstore
cgroup             0     0     0    - /sys/fs/cgroup/net_cls,net_prio
cgroup             0     0     0    - /sys/fs/cgroup/devices
cgroup             0     0     0    - /sys/fs/cgroup/hugetlb
cgroup             0     0     0    - /sys/fs/cgroup/freezer
cgroup             0     0     0    - /sys/fs/cgroup/cpuset
cgroup             0     0     0    - /sys/fs/cgroup/blkio
cgroup             0     0     0    - /sys/fs/cgroup/perf_event
cgroup             0     0     0    - /sys/fs/cgroup/cpu,cpuacct
cgroup             0     0     0    - /sys/fs/cgroup/pids
cgroup             0     0     0    - /sys/fs/cgroup/memory
systemd-1          0     0     0    - /proc/sys/fs/binfmt_misc
hugetlbfs          0     0     0    - /dev/hugepages
debugfs            0     0     0    - /sys/kernel/debug
mqueue             0     0     0    - /dev/mqueue
fusectl            0     0     0    - /sys/fs/fuse/connections
tracefs            -     -     -    - /sys/kernel/debug/tracing
tmpfs           5.9G  144K  5.9G   1% /tmp
tmpfs           1.2G  168K  1.2G   1% /run/user/999
gvfsd-fuse         0     0     0    - /run/user/999/gvfs

Screenshot of device's and the error trying to remount. (on purpose) So all is good so far! ;) Live install here:

#673

Thanks for sharing this tutorial, its very useful! :)

#674

[SIZE=5]New compressed image files of persistent live systems are uploaded[/SIZE]

[SIZE=4]Very flexible LXLE 16.04.2 system (32 bit) with mkusb version 12.1.5[/SIZE]

You can download the compressed image file from the following link

dd_LXLE_16.04.2_i386_persist-live_mkusb-12.1.5_7.8GB_msdos-pt.img.xz

and check the md5sum

$ md5sum dd_LXLE_16.04.2_i386_persist-live_mkusb-12.1.5_7.8GB_msdos-pt.img.xz
2576227d0fed29d57acc94f9f2c5a11d  dd_LXLE_16.04.2_i386_persist-live_mkusb-12.1.5_7.8GB_msdos-pt.img.xz

This persistent live LXLE system contains lxle_16_04_2_32.iso and mkusb version 12.1.5.

. The system is very flexible. It works in 32 & 64 bit computers in BIOS & UEFI mode, also in secure boot. There is an msdos partition table, suitable when not installing with mkusb, for example in Windows. See the attached links.

. There is a backup file of the original system. The system as stored in the casper-rw partition can be restored to the original state from the tarball 1-casper-rw.tar.gz, but the content of the usb-data partition is still there, and other (more current states can be backed up and restored from other tarballs. It is a good idea to store copies of the backup files (tarballs) in a separate drive.

You find more information about this LXLE system at the following link, help.ubuntu.com/community/mkusb/persistent/LXLE. There are screenshots from running in old, middle aged and [rather] new computers (2004-2016).

[hr][/hr] One reason to create this kind of images with mkusb is that, if the computer runs an installed Ubuntu system in UEFI mode, it will not be possible to install and use the package 'grub-pc' to make the target persistent live drive bootable in BIOS mode (because there is a conflict with 'grub-efi'). But in a persistent live Ubuntu, both 'grub-pc' and 'grub-efi' can be installed alongside each other. So it is possible to create systems that boot also in BIOS mode from a persistent live system running in UEFI mode.

Advantages: very flexible and stable system, one image works for 'almost all' PC computers.

Disadvantage: big image file, ~ 2GB.

Another reason is that it is straightforward to create a USB pendrive by cloning also from other operating systems and with other tools. See for example this link, wiki.ubuntu.com/Win32DiskImager/compressed-image_2_USB-or-SD

[hr][/hr] [SIZE=4]Very flexible Bodhi Linux 4.1.0-32 system (32 bit) with mkusb version 12.1.5[/SIZE]

A corresponding system based on the iso file bodhi-4.1.0-32.iso and mkusb version 12.1.5. It is also very flexible in the same way as the LXLE system.

Advantages: very flexible, modern and rather small system (~800 MB, smaller than the corresponding Lubuntu and LXLE images), one image works for 'almost all' PC computers.

Disadvantage: The system is not as stable as Lubuntu and LXLE.

You find more information about this Bodhi Linux system at the following link, help.ubuntu.com/community/mkusb/persistent/bodhi. There are screenshots from running in an old and a [rather] new computer (2004,2016).

[hr][/hr] [SIZE=4]Small and low resource text mode Debian live 8.8.0 (64-bit) with mkusb version 12.1.8[/SIZE]

Download the compressed image file from one of the following links

dd_text_Debian-live-8.8.0-amd64_persist-live_user-live_mkusb-12.1.8_2017-05-19_4GB_msdos-pt.img.xz

and check the md5sum


6d6c0deb0a192d95d9e206700bd979b9  dd_text_Debian-live-8.8.0-amd64_persist-live_user-live_mkusb-12.1.8_2017-05-19_4GB_msdos-pt.img.xz

dd_text_Debian-live-8.8.0-amd64_persist-live_user-live_mkusb-12.1.8_2017-05-21_4GB_msdos-pt_ssh-with-password.img.xz

and check the md5sum

a704d2fdd871465536fa6148ca0b35f7  dd_text_Debian-live-8.8.0-amd64_persist-live_user-live_mkusb-12.1.8_2017-05-21_4GB_msdos-pt_ssh-with-password.img.xz

This system comes in a small file compared to the other persistent live systems with mkusb (~470 MiB) and needs not much hardware in order to run. It works in 64-bit computers in BIOS & UEFI mode ('''not''' in secure boot). There is an msdos partition table, suitable when not installing with mkusb, for example in Windows.

It is easy to connect remotely via ssh to the version '...ssh-with-password.img.xz'.

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] [B]user: user password: live[/B]

Please be aware of the risk, when using remote login with a password. So even if you change the password, you should only use that system behind a router with a firewall. [/td][/tr][/table]

Advantages: modern, should boot in new computers, small, low resource, drivers for advanced graphics chips not necessary (because of text mode). Disadvantages: 'only' text mode, limited support for network hardware compared to the Ubuntu based systems.

See also this link: Debian live with mkusb.

[hr][/hr] [SIZE=4]Very small and low resource text mode Clonezilla live 2.5.0-25 (64-bit) with mkusb version 12.1.8+[/SIZE]

This might be a useful tool for new computers, because it is

. works in UEFI mode and BIOS mode (but not with secure boot)

  • modern, uses Debian's 64-bit linux kernel 4.9.6-3 (2017-01-28)
  • small, compressed image size, ~260 MiB, expands to 4 GB, so it fits in a 4GB USB pendrive or memory card
  • simple, uses text mode, so less problems with drivers for graphics chips/cards
  • low resource, uses very little RAM
  • combination tool, you get both Clonezilla and mkusb

Download the compressed image file from one of the following links

dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt.img.xz

dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt_ssh-with-password.img.xz

and check the md5sum


d781cb88b917bed0e0d050f74c417a3d  dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt.img.xz

f12b557f2806379b494d35d03b1312eb  dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt_ssh-with-password.img.xz
  • These systems come in small files compared to the other persistent live systems with mkusb (246 MiB and 260 MiB) and need not much hardware in order to run. They work in 64-bit computers in BIOS & UEFI mode (not in secure boot). There is an msdos partition table, suitable when not installing with mkusb, for example in Windows.
  • It is easy to connect remotely via ssh to the version '...ssh-with-password.img.xz'.

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] [B]user: user password: live[/B]

Please be aware of the risk, when using remote login with a password. So even if you change the password, you should only use that system behind a router with a firewall. [/td][/tr][/table]

  • Advantages: modern, should boot in new computers, small, low resource, drivers for advanced graphics chips not necessary (because of text mode).
  • Disadvantages: 'only' text mode, limited support for network hardware compared to the Ubuntu based systems (good for wired network, maybe not so good for wifi), does not work in 32-bit computers.
#675

[SIZE=4]mkusb version 12.1.6 and 12.1.7[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

mkusb 12.1.6

  • dus-persistent: function menu_package_installer: ask to update & upgrade only installed systems (not live or persistent live systems). This avoids upgrading persistent live systems by mistake, which might break them by filling the available drive space for persistence.

[hr][/hr] mkusb 12.1.7

  • dus: p_need_pck mkfs.vfat "package dosfstools".

Some Debian iso files come without dosfstools, so dus needs to check for it, because it is used to create FAT32 file systems in dus-live, dus-persistent and dus-restore.

[/td][/tr][/table]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.1.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#676

[SIZE=4]mkusb version 12.1.8[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.1.8

During testing with a Debian live drive running in text mode several fixes to improve the performance (in text mode).

dus: separate function usage called directly if '-h' dus: function p_checkpoint: --defaultno for the 'dialog' menu to increase the safety in text mode dus: function p_chk_programs: improved logic to ask for zenity and dialog in text mode

[/td][/tr][/table]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.1.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#677

Works Good Here:

System:    Host: me-750-417c Kernel: 4.10.0-21-lowlatency x86_64 (64 bit gcc: 6.3.0)
           Desktop: Gnome 3.24.1 (Gtk 3.22.11-0ubuntu3) dm: gdm3
           Distro: Ubuntu 17.04

Just got through burning Elementary Os to check out.

#678

@1fallen,

Thanks for testing this new version :-)

#679

Happy to help...:) Besides we should be thanking you.

#680

[SIZE=4]Update about compressed image files of persistent live systems[/SIZE]

One reason to create this kind of images with mkusb is that, if the computer runs an installed Ubuntu system in UEFI mode, it will not be possible to install and use the package 'grub-pc' to make the target persistent live drive bootable in BIOS mode (because there is a conflict with 'grub-efi'). But in a persistent live Ubuntu, both 'grub-pc' and 'grub-efi' can be installed alongside each other. So it is possible to create systems that boot also in BIOS mode from a persistent live system running in UEFI mode.

Another reason is that it is straightforward to create a USB pendrive by cloning also from other operating systems and with other tools. See for example this link, wiki.ubuntu.com/Win32DiskImager/compressed-image_2_USB-or-SD

[hr][/hr] [SIZE=3]Lubuntu 16.04.2 LTS (32 bit and 64 bit) with mkusb 12.1.4[/SIZE]

There are three versions of this persistent live Lubuntu system,

dd_Lubuntu_16.04.2_i386_persist-live_mkusb-12.1.4_7.8GB_msdos-pt.img.xz for 32 & 64 bit in BIOS & UEFI mode, *not* secure boot; msdos partition table, suitable when not installing with mkusb, for example in Windows

dd_Lubuntu_16.04.2_amd64_persist-live_mkusb-12.1.4_7.8GB_guid-pt.img.xz for 64 bit in BIOS & UEFI mode, works in secure boot; *gpt*, which is good for big drives but needs fixing (done automatically by mkusb)

dd_Lubuntu_16.04.2_amd64_persist-live_mkusb-12.1.4_7.8GB_msdos-pt.img.xz for 64 bit in BIOS & UEFI mode, works in secure boot; msdos partition table, suitable when not installing with mkusb, for example in Windows

Advantages: flexible and stable systems, that work in most PC computers Disadvantage: Two systems (image files) are necessary to work in all computers. The 32-bit version does not work with secure boot, and the 64-bit version does not with with 32-bit computers

You find more information about these Lubuntu systems at the following link, help.ubuntu.com/community/mkusb/persistent/lubuntu.

[hr][/hr] [SIZE=3]Very flexible LXLE 16.04.2 system (32 bit) with mkusb version 12.1.5[/SIZE]

This persistent live LXLE system contains lxle_16_04_2_32.iso and mkusb version 12.1.5.

. The system is very flexible. It works in 32 & 64 bit computers in BIOS & UEFI mode, also in secure boot. There is an msdos partition table, suitable when not installing with mkusb, for example in Windows. See the attached links.

. There is a backup file of the original system. The system as stored in the casper-rw partition can be restored to the original state from the tarball 1-casper-rw.tar.gz, but the content of the usb-data partition is still there, and other (more current states can be backed up and restored from other tarballs. It is a good idea to store copies of the backup files (tarballs) in a separate drive.

Advantages: very flexible and stable system, one image works for 'almost all' PC computers.

Disadvantage: big image file, ~ 2GB.

You find more information about this LXLE system at the following link, help.ubuntu.com/community/mkusb/persistent/LXLE. There are screenshots from running in old, middle aged and [rather] new computers (2004-2016).

[hr][/hr] [SIZE=3]Very flexible Bodhi Linux 4.1.0-32 system (32 bit) with mkusb version 12.1.5[/SIZE]

A corresponding system based on the iso file bodhi-4.1.0-32.iso and mkusb version 12.1.5. It is also very flexible in the same way as the LXLE system.

Advantages: very flexible, modern and rather small system (~800 MB, smaller than the corresponding Lubuntu and LXLE images), one image works for 'almost all' PC computers.

Disadvantage: The system is not as stable as Lubuntu and LXLE.

You find more information about this Bodhi Linux system at the following link, help.ubuntu.com/community/mkusb/persistent/bodhi. There are screenshots from running in an old and a [rather] new computer (2004,2016).

[hr][/hr] [SIZE=3]Small and low resource text mode Debian live 8.8.0 (64-bit) with mkusb version 12.1.8[/SIZE]

This system comes in a small file compared to the corresponding persistent live systems with graphical desktops (~470 MiB) and needs not much hardware in order to run. It works in 64-bit computers in BIOS & UEFI mode (*not* in secure boot). There is an msdos partition table, suitable when not installing with mkusb, for example in Windows.

It is easy to connect remotely via ssh to the version '...ssh-with-password.img.xz'.

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] [B]user: user password: live[/B]

Please be aware of the risk, when using remote login with a password. So even if you change the password, you should only use that system behind a router with a firewall. [/td][/tr][/table]

Advantages: modern, should boot in new computers, small, low resource, drivers for advanced graphics chips not necessary (because of text mode). Disadvantages: 'only' text mode, limited support for network hardware compared to the Ubuntu based systems.

You find where to download the compressed image files at this link: Debian live with mkusb.

[hr][/hr] [SIZE=3]Very small and low resource text mode Clonezilla live 2.5.0-25 (64-bit) with mkusb version 12.1.8+[/SIZE]

This might be a useful tool for new computers, because it is

. works in UEFI mode and BIOS mode (but not with secure boot)

  • modern, uses Debian's 64-bit linux kernel 4.9.6-3 (2017-01-28)
  • small, compressed image size, ~260 MiB, expands to 4 GB, so it fits in a 4GB USB pendrive or memory card
  • simple, uses text mode, so less problems with drivers for graphics chips/cards
  • low resource, uses very little RAM
  • combination tool, you get both Clonezilla and mkusb

Download the compressed image file from one of the following links

dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt.img.xz

dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt_ssh-with-password.img.xz

and check the md5sum


d781cb88b917bed0e0d050f74c417a3d  dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt.img.xz

f12b557f2806379b494d35d03b1312eb  dd_text_clonezilla-live-2.5.0-25-amd64_persist_mkusb-12.1.8_2017-05-23_4GB_msdos-pt_ssh-with-password.img.xz
  • These systems come in small files compared to the other persistent live systems with mkusb (246 MiB and 260 MiB) and need not much hardware in order to run. They work in 64-bit computers in BIOS & UEFI mode (not in secure boot). There is an msdos partition table, suitable when not installing with mkusb, for example in Windows.
  • It is easy to connect remotely via ssh to the version '...ssh-with-password.img.xz'.

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] [B]user: user password: live[/B]

Please be aware of the risk, when using remote login with a password. So even if you change the password, you should only use that system behind a router with a firewall. [/td][/tr][/table]

  • Advantages: modern, should boot in new computers, small, low resource, drivers for advanced graphics chips not necessary (because of text mode).
  • Disadvantages: 'only' text mode, limited support for network hardware compared to the Ubuntu based systems (good for wired network, maybe not so good for wifi), does not work in 32-bit computers.
#681

[SIZE=4]mkusb version 12.1.9[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.1.9

During testing with a Clonezilla live drive (amd64 iso file) running in text mode I made mkusb recognize Clonezilla's name for the live root system (as seen by for example 'df').

dus and dus-persistent: checking for 'overlay': device name for live root in Clonezilla [/td][/tr][/table]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.1.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#682

[SIZE=4]Small 9w systems with guidus alias mkusb-dus and gparted updated to a current version of dus[/SIZE]

These 9w systems work well with old computers and provide a way to get started with the Ubuntu family operating systems. They are updated with dus (mkusb-dus) version 12.1.9 in May 25, 2017.

See the following links and screenshots for more details.

Small 9w systems with guidus alias mkusb-dus and gparted installed: The Ubuntu help wiki page

[SIZE=3]ISO file[/SIZE]

9w-dus_2017-05-25.iso

[SIZE=3]Good grub booter (but only in BIOS mode), compatible with Windows for data transfer[/SIZE]

Post #561 describes a system that is updated to 9w-dus-i686-grub_2017-05-25_1GB.exe

There are problems to boot in some middle-age HP computers, but it boots in most other computers.

[SIZE=3]Very reliable syslinux booter (but only in BIOS mode)[/SIZE]

Post #562 describes a system that is updated to 9W-DUS_i686_2017-05-25.img

This is a very good booter, and a 'usbdata' partition with the NTFS file system can be created. But Windows can read the NTFS partition only in a few 32 GB USB 3 pendrives (maybe because Windows thinks those drives are not pendrives but USB hard disk drives or SSDs).

I found a small SD card (nominally 256 MB), installed from the iso file with Rufus and made an image file of it. It needs no compression, so it is easier to install with 'any' cloning tool, for example from Windows.

#683

[SIZE=4]mkusb version 12.2.0, 12.2.1[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.2.0

  • dus is modified for knoppix in function p_list_drives and function p_ldr

mkusb 12.2.1

[/td][/tr][/table]

  • dus: p_need_pck_s mkfs.ntfs "package ntfs-3g" (for debian)
  • dus-persistent: tweaks to work with "9w-debian-wheezy"

There are several tweaks in dus-persistent:

59,60d58
< # 2017-05-31  sudodus  tweaks to work with "9w-debian-wheezy"
< # 2017-05-31  sudodus  version 12.2.1
62c60
< version="${0##*/} 12.2.1"
---
> version="${0##*/} 12.1.9"
1025,1027c1023
< if [ "$disk_name_type" == "debian" ] \
< || [ "$disk_name_type" == "torios-debian" ] \
< || [ "$disk_name_type" == "9w-debian-wheezy" ]
---
> if [ "$disk_name_type" == "debian" ] || [ "$disk_name_type" == "torios-debian" ]
1053,1055c1049
< if [ "$disk_name_type" == "debian" ] \
<  || [ "$disk_name_type" == "torios-debian" ] \
<  || [ "$disk_name_type" == "9w-debian-wheezy" ]
---
> if [ "$disk_name_type" == "debian" ] || [ "$disk_name_type" == "torios-debian" ]
1275,1286d1268
<  tmpstr=$(grep -i 9w "$looper/isolinux/isolinux.cfg" 2>/dev/null| \
<  grep -i Debian|grep -i ' 3.2'|sed 's/^.*9w/9w/')
<  if [ "$tmpstr" != "" ]
<  then
<   disk_name_type="9w-debian-wheezy"
<   /bin/echo -e "$inversvid $tmpstr $resetvid"
<   echo ""
<  fi
< fi
< 
< if [ "$disk_name_type" == "" ]
< then
1304,1305c1286
< && [ "$disk_name_type" != "debian" ] \
< && [ "$disk_name_type" != "9w-debian-wheezy" ]
---
> && [ "$disk_name_type" != "debian" ]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.1.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#684

Works on Artful just fine :): "Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170530)"

#685

@1fallen,

Thanks for testing the new version in Artful :-)

@everybody,

I have updated and uploaded some iso files and image files and compressed image files which contain new versions of mkusb-dus, newer than what is found in the stable PPA. You can find them via the following links and links from them,

Compressed image file with a persistent live system

Small 9w systems with guidus alias mkusb-dus and gparted installed

http://phillw.net/isos/linux-tools/uefi-n-bios: sort according to 'last modified' to find the newest files.

http://phillw.net/isos/linux-tools/9w: sort according to 'last modified' to find the newest files.

and get an overview of the latest modifications at the following link

https://help.ubuntu.com/community/mkusb/12

*Edit:* Today I also tested that mkusb version 12.2.1 works in and with Linux Mint 18.1 Serena from the iso file 'linuxmint-18.1-cinnamon-64bit.iso'. I tested both in a persistent live system and an installed system.

#686

[SIZE=4]mkusb version 12.2.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.2.2

[/td][/tr][/table]

  • dus: p_cal1, p_call, p_calx: no sudo when running as root
  • dus-persistent: tweaks to work with "9w-debian-jessie"

The following tweaks were made in in dus-persistent:


61,62d60
< # 2017-06-07  sudodus  tweaks to work with "9w-debian-jessie"
< # 2017-06-07  sudodus  version 12.2.2
64c62
< version="${0##*/} 12.2.2"
---
> version="${0##*/} 12.2.1"
118d115
< niow=false
1061c1058
<  if [ "$disk_name_type" == "debian" ] && ! $niow
---
>  if [ "$disk_name_type" == "debian" ]
1282d1278
<   niow=true
1284,1296d1279
<   /bin/echo -e "$inversvid $tmpstr $resetvid"
<   echo ""
<  fi
< fi
< 
< if [ "$disk_name_type" == "" ]
< then
<  tmpstr=$(grep -i 9w "$looper/isolinux/isolinux.cfg" 2>/dev/null| \
<  grep -i Debian|grep -i ' 3.16'|sed 's/^.*9w/9w/')
<  if [ "$tmpstr" != "" ]
<  then
<   niow=true
<   disk_name_type="debian"

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.2.2 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#687

Is there a reason for us Ubuntu users to upgrade? I did though on Artful, as shown.

@me-750-417c:~$ dus --version
 dus 12.2.2 
#688

[SIZE=4]9w-dus version based on Debian Jessie i686[/SIZE]

A new version of 9w is based on Debian Jessie i686 (version 8). This version has newer hardware drivers and *works better with newer computers and hardware components, for example graphics and network devices* compared to the original 9w based on Debian Wheezy (version 7).

This 9w-dus version is described at the link, where you can also find links to download an iso file and some compressed image files (for linux) and self-extracting files (for Windows),

9w-dus based on Debian Jessie

These 9w-dus files come with mkusb-dus version 12.2.2, which was developed to work well in this environment.

#689

1fallen said: Is there a reason for us Ubuntu users to upgrade?

I did though on Artful, as shown.

@me-750-417c:~$ dus --version
 dus 12.2.2 

For 'regular end users', no.

For testers, yes, please test that this version does not introduce some regression, when running in a standard Ubuntu flavour :-P

(And you are welcome to test the new 9w-dus version based on Debian Jessie.)

#690

I'm on it now...;) I will only report back if some some regression comes about! Thanks

#691

[SIZE=4]mkusb version 12.2.3,12.2.4 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.2.3

. grub_n_iso: bpsiz=256 (usbboot size doubled) for debian 9 . menu_entry_1: special treatment for debian 9

  • dus-persistent: tweaks for debian 9, currently 'stretch':

mkusb 12.2.4

. tweaked to recognize and run from TahrPup . FINAL WARNING ---> Final checkpoint [/td][/tr][/table]

  • mkusb-bas alias mkusb version 7.4.3:

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb is also available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.2.4 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#692

[SIZE=4]mkusb version 12.2.3 and Debian 9 live[/SIZE]

mkusb version 12.2.3 can create a live-only and a persistent live drive from the current Debian live iso files. I tested with the following command line,

dus debian-live-9.0.1-amd64-cinnamon.iso

This iso file is identifying itself as 'Debian Stretch' (recently upgraded from 'testing' to 'stable'). When this is written, you can get it via this link (but the content will be updated and you can expect to find new versions in the future)

https://www.debian.org/CD/live/

[SIZE=4]Live-only[/SIZE]

After *cloning* from the iso file to create a live-only USB pendrive, the target drive will boot in both UEFI and BIOS mode.

[SIZE=4]Persistent live[/SIZE]

With the default settings when creating a persistent live drive, the target drive will only boot in BIOS mode, but if you select booting with *usb-pack-efi*, it will boot in both UEFI and BIOS mode. This is different from Ubuntu amd64 systems, which can boot from UEFI too when created with the default settings.

#693

[SIZE=4]mkusb version 12.2.4 and TahrPup and several other linux distros tested[/SIZE]

mkusb 12.2.3 was tested with and in several linux distros, which are more or less similar to Ubuntu and Debian.

It was necessary to modify mkusb-bas in order to make it work well with TahrPup because the default setting is to boot TahrPup to RAM, so that there is nothing 'binding' the boot drive, and it was difficult to select the correct target drive. The other linux distros worked 'well enough' with mkusb.

Generally mkusb can create live-only drives by cloning. This is the standard usage mode and enough in order to test and install other linux distros.

  1. mkusb was tested by creating a live-only drive of the other linux distro.
  1. mkusb was installed in the other linux distro.

If the distro is similar enough to Ubuntu or Debian, installing via PPA works.

help.ubuntu.com/community/mkusb/gui

help.ubuntu.com/community/mkusb/install-to-debian

If the distro is more different from Ubuntu or Debian, installing via a dus tarball works.

help.ubuntu.com/community/mkusb/gui/tarball

If the distro is too basic or light-weight or different, installing only mkusb-bas might work as the case with TahrPup.

help.ubuntu.com/community/mkusb/v7#mkusb_version_7.4.x_-_mkusb-bas

[SIZE=3]Distros that work with mkusb are listed at the following links[/SIZE]

Linux distros where mkusb works

Linux distros with limited compatibility for mkusb

#694

[SIZE=4]Preparing mkusb-dus for localization (to support local languages)[/SIZE]

Please help us test a bleeding edge version of mkusb-dus, at the moment ahead of the unstable version!

Israel Dahl. the developer of ToriOS, has added code, that makes all text strings into variables, so that values can be read from lists for different languages. There are still no such lists, but there are many and big modifications in the shellscript code. It works in the few tests that I have run, but it needs more testing.

You find a tarball and a signed md5sum file at the following links

dus-plus-localization.tar.gz

md5sum-dus-plus-localization.txt.asc

tar -xvzf dus-plus-localization.tar.gz

cd dus-tplus-localization

sudo ./dus-installer i

You can expect to install some program packages, that will be used by mkusb-dus, typically

xterm, zenity, dialog, gdisk, pv

in a persistent live Lubuntu 16.04.1 LTS, probably a different set of program packages in other Ubuntu based or other operating systems.

(Except for the download links and minor modifications) you can refer to the instructions at this link in order to install this bleeding edge version of mkusb-dus prepared for localization.

[hr][/hr] The unstable version (still without localization) is available via the previous 'tarballs to download' links as well as via the unstable PPA 'ppa:mkusb/unstable'.

#695

Anything you want specifically tested sudodus?

&#8594; dus --version
 dus 12.2.4 
live system or temporary superuser permissions
--version is neither an iso file nor an img.{gz,xz} file

So far just a quick run through...creating bootable installers works fine. In fact all my normal chores I use it for works Great.

#696

Hi 1fallen,

I think doing what works in 12.2.4 (without localization) needs testing with localization in different environments and by different people, so it would be valuable if you try to

  • make a live-only boot drive (cloning a linux iso file (for example Arch) and a compressed image file, for example from Compressed image file with a persistent live system)
  • make a persistent live drive (Ubuntu family or Debian Jessie or Stretch from an iso file)
  • wipe the first mibibyte (quickly done)
  • restore to a standard storage device (also quickly done)

(I have tested (successfully) to make a Windows 10 install drive. I think you can give it lower priority, but if you have time and a Windows 7-10 iso file ...)

Edit: Please notice that you get this version with localization *only via the special tarball*, that I link to in my previous post.

#697

sudodus said: Hi 1fallen,

I think doing what works in 12.2.4 (without localization) needs testing with localization[U] in different environments and by different people, so it would be valuable if you try to [/U]

(I have tested (successfully) to make a Windows 10 install drive. I think you can give it lower priority, but if you have time and a Windows 7-10 iso file ...)

Edit: Please notice that you get this version with localization *only via the special tarball*, that I link to in my previous post.

Okey Dokey:D I'll do just that then.:) I should have figured that myself...must be tired.:D

#698

I used unetbootin to put Linux Mint 17 "Qiana" - Release i386 on my usb stick. When I try to boot from the usb, a menu comes up asking me to choose. I choose start Linux Mint, then the system hangs. The screen goes blank and nothing happens.

#699

@Kevin McCready,

Please describe your computer with as many details as possible, at least

  • Brand name and model
  • CPU
  • RAM (size)
  • graphics chip/card
  • wifi chip/card

Which operating system are you running now (some linux operating system or Windows or MacOS)? Is this where you were running Unetbootin to create the USB boot drive? Or did you use another computer for that purpose?

Knowing these details will help me to help you. Otherwise I can only guess what is the problem. There may be problems with Unetbootin, but I think the problem is somewhere else, for example with a driver for the graphics chip.

#700

Sorry about that. I should have remembered to supply details of my computer. Yes I'm using this one (details below). I've tried 2 versions of unetbootin. I've noticed that in each attempt, a little blue screen pops up very quickly in the upper left corner of the screen and then disappears. It's too quick to see what's happening. Once when I let it go for a few hours (I went for a walk), I came back and a couple of squares were painted on the screen of the screen saver from Qiana (so, yes it could be a graphics problem).

mkusb didn't work either.

My system: DISTRIB_ID=LinuxMint DISTRIB_RELEASE=18 DISTRIB_CODENAME=sarah DISTRIB_DESCRIPTION="Linux Mint 18 Sarah" NAME="Linux Mint" VERSION="18 (Sarah)" ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME="Linux Mint 18" VERSION_ID="18" HOME_URL="http://www.linuxmint.com/" SUPPORT_URL="http://forums.linuxmint.com/" BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/" UBUNTU_CODENAME=xenial

Lenovo h50 550 tower computer F12 for boot menu http://www.harveynorman.co.nz/computers/desktops/lenovo-h50-550-desktop-2tb.html 16GB RAM and an AMD A10-7800 processor offer an ultra fast computing experience with speeds up to 3.5Ghz Graphics Card Memory 2GB Brand Lenovo Processor Processor Model A10-7800 Processor Type AMD A10 Processor Speed 3.5GHz Graphics and Video Graphics Card Brand ATI Graphics Card Type Radeon R7 350 Graphics Card Memory 2GB Memory Ram 16GB Ram Type DDR3 1600 Storage Capacity Capacity 2 TB Type HDD Optical Drive Optical Drive Type DVD-Writer Connections Bluetooth Yes Connections 3.5mm Audio in port 3.5mm Audio out port HDMI port Expansion Slots 7-in-1 Card Reader USB 2x USB 3.0, 2x USB 2.0 Wireless Ready 802.11ac

unetbootin: Installed: 647-1~xenial1 Candidate: 647-1~xenial1 Version table: *** 647-1~xenial1 500 500 http://ppa.launchpad.net/gezakovacs/ppa/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 608-1 500 500 http://ucmirror.canterbury.ac.nz/ubuntu xenial/universe i386 Packages

#701

@Kevin McCready,

You have

  1. Unetbootin 647-1~xenial1, which is the version found via the PPA, ppa:gezakovacs/ppa, so it is up to date (while the Ubuntu universe repository has an older version, 608-1).
  1. Linux Mint Sara (corresponding to Ubuntu Xenial (16.04.1 LTS) with the xenial kernel series). It *should* work to use mkusb with this version of Linux Mint. I think I have tested it, and I can test it again. Which desktop environment are you using with Linux Mint Sara (Cinnamon, KDE, MATE, XFCE)? When I know, I can download that iso file and test to create a USB boot drive with mkusb.
  1. Graphics Card Type Radeon R7 350, which means that it might help with the boot option nomodeset. See the following links,

Boot options

help.ubuntu.com/community/RadeonDriver

There are proprietary drivers via the following link, and it 'says' that it would work with Ubuntu 16.04 64-bit (xenial) and your graphics chip, but I have read elsewhere, that proprietary radeon drivers only work with previous versions (Ubuntu version 14.04.1 LTS with the Trusty kernel). Please notice that there might be no support for 32-bit Ubuntu based operating systems for your graphics chip. Try if you wish, but it might be a bumpy ride.

support.amd.com/en-us/download/linux

  1. I found no information about the wifi chip/card (except 'Wireless Ready 802.11ac'). Wifi might or might not cause problems. Some chips need a proprietary driver.

-o-

So, there might be problems with the graphics. I suggest that you try with some boot options, start with nomodeset.

-o-

Edit: The point release Linux Mint 18.1 Serena uses the same xenial kernel series as Sara, and it is much improved after several months of debugging, so I would recommend that you download and try it. This is the version (with the Cinnamon desktop environment) that I downloaded and tried several months ago, and mkusb can create USB boot drives that work well in my computers.

#702

Thanks so much. My env is Mate. I followed the links but I still don't understand how to boot from my usb with nomodeset. The reason I am trying to boot an older version of linux is that it used to work with my scanner, so I am trying to set up a dual boot so I can use my scanner when I need to.

PS. does -o- mean anything, or is it just a separator?

#703

Kevin McCready said: Thanks so much. My env is Mate.

I'll download and test Linux Mint Sara with MATE (64-bit), to check how mkusb can manage it.

I followed the links but I still don't understand how to boot from my usb with nomodeset.

Is the live drive booting via syslinux (only in BIOS mode) or via grub (in UEFI mode, in some cases also in BIOS mode)? This decides how to enter a boot option? (I know best how to enter boot options in systems that are created with mkusb (but it should work in a similar way with Unetbootin),

- via syslinux in BIOS mode: press the TAB key to get a long line

> /casper/vmlinuz ... quiet splash --_

The underscore at the end is the cursor and does not belong to the line. Now you can type nomodeset. If you want the boot option to be active both in the live session and the installed system (if you decide to install it), you should enter it twice, so that the line will look like this near the the end,

> /casper/vmlinuz ... quiet splash nomodeset -- nomodeset

Press the Enter key, when you are ready to boot.

- via grub: press the 'e' key to get to a new menu with a few lines.

Focus on the line starting with 'linux'. Now you can type nomodeset. If you want the boot option to be active both in the live session and the installed system (if you decide to install it), you should enter it twice, so that the line will look like this near the the end,

 linux ... quiet splash nomodeset -- nomodeset

Press {ctrl + x} or F10 when you are ready to boot.

Tip: The lines are long and will probably be displayed with line breaks to fit on the screen. (Do not worry about that.)

The reason I am trying to boot an older version of linux is that it used to work with my scanner, so I am trying to set up a dual boot so I can use my scanner when I need to.

PS. does -o- mean anything, or is it just a separator?

Only a separator :-)

#704

@Kevin McCready,

I used Unetbootin version 608-1 from the Ubuntu Xenial repository, and this old version can create a working USB boot drive from the file

linuxmint-18-mate-64bit.iso

which should match your Linux Mint Sara. I could also verify that basically the same instructions work in order to enter boot options as I described in the previous post (which describe how to do it in a boot drive made by mkusb).

#705

Wow. Thanks so much. Your boot instructions worked. I think I was in BIOS mode. A blue screen came up and I booted from the USB. Then a linux menu came up and I selected an option that allowed me to do nomodeset. Then I was able to use the scanner. It's totally weird that Mint 17 can use the scanner but Mint 18 can't. Anyway, thanks again. For the record my scanner is Hewlett-Packard ScanJet 5300C.

#706

@Kevin McCready,

You are welcome. I'm glad that I could help you boot with the boot option nomodeset, and that you can use your scanner now :-)

#707

[SIZE=4]mkusb 12.2.4 is in the stable PPA ppa:mkusb/ppa (updated 2017-07-14)[/SIZE]

The following link lists the updates of mkusb version 12,

help.ubuntu.com/community/mkusb/12

#708

mkusb 12.2.4 works in the current daily build of Artful Aardvark running on Wayland.

In order to test running on Wayland you should

  • click on the cog wheel
  • at the log in screen
  • of an installed system and
  • select 'Ubuntu on Wayland'.

See the detailed description at this link,

popey.com/blog/posts/ubuntu-artful-desktop-july-shakedown.html

*Edit:* mkusb version 12 alias mkusb-dus works with Wayland in Artful Aardvark, but there are problems with mkusb-11 with the classic user interface.

mkusb-11 is run via the command line

sudo -H mkusb-11

and it seems that no graphic application programs works, when run with sudo -H or gksudo. xterm and nautilus are also failing as illustrated with this dialogue,


tester@tester-SATELLITE-PRO-C850-19W:~$ [COLOR="#0000FF"]sudo -H xterm[/COLOR]
No protocol specified
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
tester@tester-SATELLITE-PRO-C850-19W:~$ [COLOR="#0000FF"]gksudo xterm[/COLOR]
Error copying '/home/tester/.Xauthority' to '/tmp/libgksu-AFm8zq': No such file or directorytester@tester-SATELLITE-PRO-C850-19W:~$ [COLOR="#0000FF"]sudo -H nautilus[/COLOR]
No protocol specified
Unable to init server: Could not connect: Connection refused

(nautilus:12455): Gtk-WARNING **: cannot open display: :0
tester@tester-SATELLITE-PRO-C850-19W:~$ [COLOR="#0000FF"]gksudo nautilus[/COLOR]
Error copying '/home/tester/.Xauthority' to '/tmp/libgksu-GoAF5n': No such file or directorytester@tester-SATELLITE-PRO-C850-19W:~$ 

Is this by intention or a bug in Artful Aardvark?

#709

[SIZE=4]mkusb version 12.2.5 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.2.5

  • mkusb-start: bugfixes to make it work correctly with mkusb-11

. 'if [ "$@" != "" ]' --> 'if [ "$*" != "" ]'

. logical variable nopsw introduced and used to manage cases when sudo will run without entering a password [/td][/tr][/table]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.2.4 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#710

[SIZE=4]Persistent live drive with a standard user, that cannot mount internal drives[/SIZE]

I made a persistent live drive with mkusb from ubuntu-16.04.[COLOR="#cc0000"]1[/COLOR]-desktop-amd64.iso, which has the longest support of the present iso files.

*A standard user ID (alongside the normal live system's user 'ubuntu') cannot run programs that need sudo*: 'standard is not in the sudoers file. This incident will be reported.' Partitions on the internal drive are not mounted. To mount them, you need sudo permissions both for mount and udisksctl.

*The persistent live system will boot into the ubuntu user, and you log out in order to switch to the standard user.*

[SIZE=4]Encrypted home[/SIZE]

It is possible to create the standard user ID with encrypted home and login with a [good] password. This can be done easily, if the program users-admin is installed by activating the repository universe and installing the package gnome-system-tools.

sudo add-apt-repository universe
sudo apt update
sudo apt install gnome-system-tools

*Tick the box* according to the attached screenshot in order to create the new user with encrypted home.

*The computer should be shut down or rebooted after using the encrypted home*. Otherwise the live user (or another user) gets access to encrypted data.

[SIZE=4]Persistent live drive with a standard user and a user with administration permissions[/SIZE]

I made a persistent live drive with mkusb from ubuntu-16.04.[COLOR="#cc0000"]2[/COLOR]-desktop-amd64.iso, which is a newer LTS iso file, in order to test that these tasks work with more than one iso file.

In some computers, the system may leave you with a black screen after logging in (after a logout). This might depend on the graphics driver. If it happens, you can do something with the mouse or keyboard to get to the desktop. If still no luck you can enter a text screen and then return to the graphics screen with the hotkey combinations

*ctrl + alt + F1* *ctrl + alt + F7*

It is possible to create another user ID with administration permissions, that can manage system tasks, for example install and upgrade program packages (if you want to separate the tasks because of security reasons). One (or both) user ID(s) can be made with encrypted home if you wish.

With these two user IDs it will be possible to remove the live system's normal user 'ubuntu'. You can do it from the user ID with administration permissions after killing the processes that are running with the user 'ubuntu'

ps -Af | grep ubuntu  # identify which processes to kill
sudo kill <the PID numbers that you found (without any brackets)>

sudo deluser ubuntu

After that you can also remove the content in the 'casper-rw' partition (or file) concerning the deleted user (if you wish), but there is probably not much data, so not very important unless you suspect there is some confidential data.

Now after removing the live system's normal user 'ubuntu', *the persistent live system will boot to the login screen, and you can select which user ID to log in to, the standard user or the user with administration permissions*. I like this behaviour, and I think it is worth the extra effort (compared to a system with a standard user alongside the normal live system's user 'ubuntu').

[SIZE=4]Backup is important[/SIZE]

Frequent backup is important, because it is a

  • persistent live system (makes it sensitive)
  • an encrypted system (makes it difficult to repair/recover).

See this link: Backup and restore of persistent overlay data

[SIZE=4]Security - turn off swapping[/SIZE]

If this kind of system finds a swap partition in the internal drive, it will probably use it, and might leave traces that are not encrypted. So please *turn off swapping if there is a linux swap partition in an internal drive in the computer*, where you are running the system.

You must log in or 'su' into the user ID with administration permissions, 'guru', to turn off swapping

su - guru
/sbin/swapon -s  # check
sudo /sbin/swapoff -a
/sbin/swapon -s  # check
exit

Comparing this kind of persistent live system to an installed system (in a USB pendrive in both cases),

Advantage:

  • more portable (than an installed system).

Disadvantages:

  • less stable (than an installed system).
  • less secure (encrypted home is less secure than encrypted disk, which is possible with an installed system). But it might be secure enough.
#711

Post #708 got me wondering, where is Guest user in a persistent install? Mkusb does not provide a guest account, nor does UNetbootin, MultiBootUSB, YUMI, Rufus, etc. A guest account is safer than a standard account and cleans itself after every use. A guest account is safer than "Try Ubuntu" in grub, as internal drives are placed off limits. A guest account is automatically added with a normal install to HDD or a Full install to flash drive.

The Guest account is controlled by lightdm.conf. For grub2 booters with persistent partitions, such as mkusb, open casper-rw/upper/etc/lightdm/lightdm.conf and change "allow-guest=true". Now there will be a Guest account.

For Syslinux booters with casper-rw files such as UNetbootin, first mount the casper-rw file:


sudo mkdir /media/casper

sudo mount -o loop casper-rw /media/casper/

Then edit casper/upper/etc/lightdm/lightdm.conf and change "allow-guest=true". A guest account will be added to boot options.

#712

@C.S.Cameron,

Thanks for the tweak to get 'guest' user in a persistent live system of Ubuntu and Ubuntu family flavours :-)

#713

@C.S.Cameron,

Do you think it would be a good idea to add an entry in the settings menu of mkusb to select a 'guest' user?

#714

I've been wondering why it is turned off in the first place, It is included with every Full install. There is not a lot of reason for including a Guest session in a Live install. Since most Persistent installs are created from Live ISO's, I suppose that guest user never got switched on.

It would seem reasonable to me to keep allow-guest switched off when making a Live install and to turn allow-guest on for a Persistent install. Giving the user an option when creating the USB would be nice as, long as it is not seen as clutter.

#715

C.S.Cameron said: It would seem reasonable to me to keep allow-guest switched off when making a Live install and to turn allow-guest on for a Persistent install. Giving the user an option when creating the USB would be nice as, long as it is not seen as clutter.

So there are two alternatives

  1. To always turn on allow-guest
  1. To offer it as a fourth option in the 'select settings' menu. See the attached screenshot. Do you think this fourth option would clutter the 'select settings' menu?
#716

Just to note though likely unimportant - In 17.04 and newer guest sessions have been disabled due to a security flaw that's not fixed (and may never as Gnome doesn't use guest.. 16.04.x I believe was not affected.

#717

@mc4man,

Thanks for the heads up about the security flaw :-)

#718

I don't think a fourth menu item would be too bad.

#719

mc4man said: Just to note though likely unimportant -

In 17.04 and newer guest sessions have been disabled due to a security flaw that's not fixed (and may never as Gnome doesn't use guest.. 16.04.x I believe was not affected.

It is easy enough adding a Guest user to Ubuntu 17.04 Gnome using ``` sudo apt install lightdm


You got to give up GDM to do so.

But the thing about it being a security flaw got me worried.
#720

@mc4man,

Is this the bug you are referring to:

Bug #1677924 - Local privilege escalation via guest user login

or is it another bug?

#721

sudodus said: @mc4man,

Is this the bug you are referring to:

Bug #1677924 - Local privilege escalation via guest user login

or is it another bug? I'm not sure... The bug I was thinking about was here, the fix was to disable - https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1663157 (atm I've only 16.04 so don't know current status in 16.10 > 17.04

#722

It seems there is no secure way to use guest session in 16.10 and 17.04 yet.

So I think it is bad idea to invite to using it via an option in mkusb. If people want to use guest session, they can still enable it, but they will have to find out how to do it and take the decision themselves.

#723

I have been testing all morning and it looks like any guest session on a _persistent_ Ubuntu drive will report being unconfined, at least as far back as 14.04. Live sessions also report being unconfined. I guess the message is: Don't loan your persistent flash drive to strangers.

#724

[SIZE=4]mkusb version 12.2.6 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.2.6

. tweaks to work with extix debian . tweaks to work with debian stretch [/td][/tr][/table]

  • dus-persistent: probe_source and grub_n_iso:

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.2.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#725

[SIZE=4]mkusb version 12.2.7 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.2.7

. new function partitioner: partitioning moved from grub_n_iso

  • dus-persistent:

. 'grubimg' added to clone partitions 2 and 3 with grub for BIOS mode when running in an installed system in UEFI mode. This is a major improvement, and may need polishing in the near future.

. minor tweaks to improve the dialogue, when running in an installed system in UEFI mode [/td][/tr][/table]

If *you* have a computer with an installed system with Ubuntu or Debian, please test that mkusb and dus-persistent work with 'grubimg' that is cloning from grub.img.xz to create partitions 2 and 3 :-P

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.2.7 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#726

[SIZE=4]Do it yourself[/SIZE]

When the boot structure is modified in Ubuntu or the booting software, there can be problems until the extracting tools are modified to manage the modification. It is worthwhile to find a method that is as simple as possible and to learn how to use it in order to manage the extraction also when the boot structure is modified.

1. General description:

help.ubuntu.com/community/Installation/iso2usb

2. Detailed istructions to make a boot drive, that boots both in UEFI and BIOS mode:

help.ubuntu.com/community/Installation/iso2usb/diy

[hr][/hr] Please notice that this method works with Ubuntu desktop 64-bit ISO files (including Ubuntu community flavours, Kubuntu, Lubuntu ... Xubuntu) and with Windows ISO files. 32-bit versions will boot only in BIOS mode.

*In UEFI mode this method should work with most linux distros*. In BIOS mode it might work if the boot structure of the linux distro is rather similar to Ubuntu's boot structure.

So it is a general method to create USB boot drives (and bootable memory cards).

[hr][/hr] Edit: Welcome to participate in the following thread, where this simple 'do it yourself' method is discussed,

UEFI: Interesting simple method to boot - but how does it work?

#727

[SIZE=4]mkusb version 12.2.8, 12.2.9 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.2.8

  • dus-live:

. new function partition_msdos_fat: extracting from the file 'grub4win.img.xz' to clone the head and the partition with grub for BIOS mode when running in an installed system in UEFI mode

. minor tweaks to improve the dialogue, when running in an installed system in UEFI mode

mkusb 12.2.9

  • dus-persistent:

. removed redundant 'echo' output about 'grubimg' (output to the console, when running in an installed system in UEFI mode)

[/td][/tr][/table]

Please test that mkusb and dus-live work correctly, when running an installed system in UEFI mode, and cloning from grub4win.img.xz to create the partition table, and a partition with grub for BIOS for a Windows USB install drive.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.2.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#728

Question at AskUbuntu:

Prevent Windows 10 from formatting ext4 partition on pendrive

I used to create two partitions on pendrives that would be used either on Windows or GNU/Linux.

The first partition I'd format with ntfs, the second one with ext4. This way Windows would not see the second partition and would not ask to format when plugged in.

Since one of the last updates to Windows 10, this trick does not work anymore.

These pendrives I'm talking about are given to teachers at schools that use random GNU/Linux distributions but at home use Windows 10. When they get back to the school from home they realize that the ext4 partition is gone, as they just clicked 'yes' when Windows asked to format the partition.

I have tried to hide the second partition with parted, but I don't find the right switch.

What should I do in order to hide/protect the ext4 partition on the pendrive from Windows 10?

I did some testing and suggested a work-around using the UDF file system instead of ext4. I found out, that

  • *Windows 10* can read a partition with UDF and *does not prompt you to format it*.
  • symbolic links work
  • linux style permissions on individual files and partitions work
  • it works with UDF in the casper-rw partition of a persistent live system (made by mkusb and fixed manually afterwards).

See this link,

UDF can replace ext4 to protect a partition with linux style

#729

I can not get UDF working for casper-rw partitions with 64bit 'buntu, only with 32bit 'buntu? With 64 bit I get (initramfs) mounting aufs on /root failed: invalid argument aufs mount failed. Anybody else have this problem?

#730

UDF in the casper-rw partition works with earlier versions of Ubuntu, but not with

Ubuntu 16.04.3 64bit

I verified that persistence works with ext4 before I changed to UDF. So I something has changed, that breaks this feature. Good catch!

I checked with Lubuntu Artful 64-bit, to be released as 17.10 during this month (because I have that iso-file already). And it works with UDF in the casper-rw partition :-) I have *not* checked with standard Ubuntu Artful 64-bit, but the boot structure should be the same, and I guess the casper structure for persistence should be the same too.

lubuntu@lubuntu:~$ df -h|grep -e /cow -e casper-rw
/cow            6.9G   19M  6.9G   1% /
/dev/sda5       6.9G   19M  6.9G   1% /media/lubuntu/casper-rw

lubuntu@lubuntu:~$ sudo lsblk -f /dev/sda|grep -e udf -e casper-rw
&#9492;&#9472;sda5 udf     casper-rw           59d481fa4c696e75                     /media/lubuntu/casper-rw

lubuntu@lubuntu:~$ uname -a
Linux lubuntu 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12 16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

lubuntu@lubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu Artful Aardvark (development branch)
Release:        17.10
Codename:       artful

Edit 1: I checked Lubuntu 17.04 64-bit, which has the same kernel as Ubuntu 16.04.3 64-bit, and it is affected too, does not work with UDF in the casper-rw partition.

Edit 2: This does not depend on 32bit/64-bit architecture. For example Ubuntu 16.04.1 64-bit works with UDF in the casper-rw partition, but Lubuntu 17.04 32-bit, is affected too, does not work with UDF in the casper-rw partition.

#731

Ubuntu 14.04.3 64bit did not work for me, Ubuntu 17.10 beta2 64bit did.

Might not hurt to have a toggle in mkusb to switch between casper-rw formats. Windows wanting to format every time you plug in the stick is annoying.

I wondered if this might have something to do with how do-it-yourself casper-rw partitions stopped working with UNetbootin installs. They still do not work with 17.10, however home-rw partitions do work on the same disk as long as there is a casper-rw file. casper-rw can not be reused when upgrading versions, home-rw can.

#732

C.S.Cameron said: Ubuntu 14.04.3 64bit did not work for me, Ubuntu 17.10 beta2 64bit did.

This matches my results with Lubuntu.

Might not hurt to have a toggle in mkusb to switch between casper-rw formats. Windows wanting to format every time you plug in the stick is annoying.

You are right. I would like to integrate it into the settings menu, and there should be automatic installation of the udf tools. There will be a fair amount of programming and testing to make it work correctly in two shellscripts. So it will take some time to do it ...

Edit 1: I think we should test using UDF during a long time and look for alternatives before adding this feature to mkusb.

  1. I think that we should test UDF in the casper-rw during a long time, to check that it is stable enough (not too much worse than with ext4 without journaling, which is set up now by mkusb). A problem is that there is no repair tool for UDF in linux, and the repair tool in Windows is not well known.
  1. An alternative is to create a casper-rw file with ext4 in a partition with a file system, that allows more than 4 GB file size. Would there be any drawback with such a system?
  1. After some preliminary testing, I found some problems: Persistence works with a home-rw file in a FAT32 partition (in the live drive), but I could not make a home-rw file or casper-rw file work in UDF or NTFS (and it would be meaningless in an ext4 partition). So it seems that a partition or two with UDF is still the best alternative to keep Windows from wanting to format every time you plug in the stick. I replaced the usbdata partition with a home-rw partition with UDF, and it works in Lubuntu 17.10.

lubuntu@lubuntu:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           384M  6.1M  378M   2% /run
/dev/sda4       918M  918M     0 100% /cdrom
/dev/loop0      858M  858M     0 100% /rofs
[COLOR="#B22222"]/cow             15G   21M   15G   1% /
/dev/sda1        15G  3.9M   15G   1% /home[/COLOR]
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs           1.9G  4.0K  1.9G   1% /tmp
tmpfs           384M  8.0K  384M   1% /run/user/999
[COLOR="#B22222"]/dev/sda5        15G   21M   15G   1% /media/lubuntu/casper-rw[/COLOR]

lubuntu@lubuntu:~$ sudo lsblk -o name,fstype,size,label,mountpoint /dev/sda
NAME   FSTYPE     SIZE LABEL               MOUNTPOINT
sda              29.8G                     
[COLOR="#B22222"]&#9500;&#9472;sda1 udf       14.3G home-rw             /home[/COLOR]
&#9500;&#9472;sda2              1M                     
&#9500;&#9472;sda3 vfat       244M usbboot             
&#9500;&#9472;sda4 iso9660    937M Lubuntu 17.10 amd64 /cdrom
[COLOR="#B22222"]&#9492;&#9472;sda5 udf       14.3G casper-rw           /media/lubuntu/casper-rw[/COLOR]

lubuntu@lubuntu:~$ uname -a
Linux lubuntu 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12 16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

See also the attached screenshot.

I wondered if this might have something to do with how do-it-yourself casper-rw partitions stopped working with UNetbootin installs. They still do not work with 17.10, however home-rw partitions do work on the same disk as long as there is a casper-rw file. casper-rw can not be reused when upgrading versions, home-rw can.

I don't know about the do-it-yourself casper-rw partitions and Unetbootin. If the function switches with the same versions of Ubuntu, yes, maybe they are related, otherwise, I guess not. And I understand from your description, that the function does not switch with the same versions as 'our' casper-rw partitions with UDF.

Edit 2: I tried to repair a damaged UDF file system in Windows 10, but it did not work.

I provoked a damaged file system by unplugging while a big iso file was copied (to a pendrive with a UDF file system). I made a similar test by unplugging while copying a directory with subdirectories and many small files.

  • In both cases the UDF file system could be mounted in Ubuntu as well as in Windows, and many files could be read. It was even possible to loop mount a truncated big iso file and read what had already been written.
  • But there were errors, as could be seen, for example when running
sudo du -hs /media/sudodus/test-udf
  • Windows considered the file system healthy, and did not suggest to repair it.
  • When selecting repair anyway (forcing Windows to repair it), Windows spent some time, and finished with a message that it could *not* repair it. (In contrast, a healthy UDF is 'repaired' by the corresponding action in Windows).

sudo dosfsck -r /dev/sdxn

  • So Windows cannot repair UDF, when damaged by unplugging during copying to it. (In contrast, Windows can repair corresponding damages in FAT32, and also the linux command line ```

- There are problems, but also opportunities, because it seems you can continue using UDF, even with some damages, for example after unplugging during copying to it.
#733

Use the boot option toram and unmount all partitions in the drive that you booted from. After that you can use the standard installer and install into the same pendrive.

#734

@Wadim_Korneev,

You are right, the boot option toram is quite useful. But things are more straightforward, if you boot from one drive and install into another drive. (For example, if something goes wrong, you have to start from the beginning and make the USB drive a live drive again, if you were installing into itself.)

#735

[SIZE=4]mkusb version 12.2.9 is in the stable PPA[/SIZE]

mkusb version 12.2.9 is in the stable PPA. Right now the same version is in the stable as in the unstable PPA. It has been tested via the unstable PPA for more than one month.)

[SIZE=4]mkusb PPA has a version for Bionic (to be released as 18.04 LTS)[/SIZE]

You are welcome to test mkusb in Bionic. If you do, please post feedback here, success as well as failures :-P

Edit:

I tested the current (2017-11-09) daily Lubuntu amd64 Bionic in my Toshiba laptop, http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/

In a live-only system (cloned from the iso file) I could install and run mkusb and create a persistent live system. The persistent live system works too.

#736

[SIZE=4]mkusb minimal shellscript - mkusb-min[/SIZE]

mkusb-min is simple, the shellscript is very small compared to the other versions, yet it serves the purpose to wrap a safety belt around 'dd'.

Small and flexible

  • mkusb-min needs no extra packages (but makes the user experience nicer, if you install pv). It runs in text screens, terminal windows, via ssh and other network connections.
  • mkusb-min works in many different linux distros. It needs bash, some standard tools and features, that are present in almost all current linux distros (2017).

There are more details, for example how to download mkusb-min and how to use it, at the following link,

help.ubuntu.com/community/mkusb/min

#737

[SIZE=4]mkusb can create a persistent live USB drive with Kali Linux[/SIZE]

I tested with the iso file kali-linux-light-2017.3-amd64.iso, and mkusb version 12.2.9 works without any tweaks (I selected 67% of the remaining space for persistence in a 16 GB pendrive).

See the following links,

help.ubuntu.com/community/mkusb/persistent

Re: Kali Live USB persistence error(Kernel Panic) - post #3

https://docs.kali.org/category/introduction

#738

Pardon the dumb question. I'm running version 12.2.9 on Kubuntu 16.04.3 , ran mkusb on a 17.10.1 ISO and selected the "C" option (clone). Is that the 'normal' option to use ? I just want to do a fresh instal of 17.10.1 on a test laptop and it looks strange when I boot. The mkusb went fine and the usb 'looks' fine.

#739

False positive - I had used a dodgy USB port on the test laptop. :)

oygle said: Pardon the dumb question. I'm running version 12.2.9 on Kubuntu 16.04.3 , ran mkusb on a 17.10.1 ISO and selected the "C" option (clone). Is that the 'normal' option to use ? I just want to do a fresh instal of 17.10.1 on a test laptop and it looks strange when I boot. The mkusb went fine and the usb 'looks' fine.

#740

@oygle,

Yes, the "C" option (clone) is the 'normal' option.

I'm glad you found and solved the problem.

#741

sudodus said: Yes, the "C" option (clone) is the 'normal' option.

I'm glad you found and solved the problem.

Thanks. :)

#742

I installed latest version from PPA in Ubuntu 16.04 LTS with Kernel 4.14.14 today.

Dash didn't display single icon for MKUSB as it should but rather 5 or 6 generic gear icons with various "mk..." program names above them.

I should have rebooted then but selected the first one (mkusb-12 I think). After a minute my syslog filled to 1.3 GB and CPU usage jumped to 80% or so the whole time. I made a 30 second .gif if you're interested.

Disadvantage of 2 GB/s NVMe Gen 3 x 4 SSD is syslog can fill fast in a 1 minute loop. To empty the syslog I used echo > /var/log/syslog.

After rebooting the mk-usb icon showed up normally in Dash and I successfully created today's build of Ubuntu 18.04 Bionic Beaver to USB thumb drive in Persistanced mode. Works Great :)

I had an older dd wrapper script I had to disable with chmod a-x because it stops /bin/dd which mkusb calls.

BTW Ubuntu 18.04 LTS Bionic Beaver per-releese worked flawlessly on Skylake i7-6700HQ laptop using internal 1080p screen and external 1080p tv hooked to Thunderbolt3, USB Type-C with DP to HDMI converter. I was impressed.

#743

Thanks for the feedback :-)

WinEunuchs2Unix said: I installed latest version from PPA in Ubuntu 16.04 LTS with Kernel 4.14.14 today.

Dash didn't display single icon for MKUSB as it should but rather 5 or 6 generic gear icons with various "mk..." program names above them.

I am developing mkusb in my main computer, which is running 16.04 LTS based on 16.04.1 and still with the xenial kernel (linux 4.4 series). So that is one difference to your system with kernel 4.14. But I have tested mkusb in 16.04.3, 17.04, 17.10 and Bionic and I have never seen anything like what you describe.

I should have rebooted then but selected the first one (mkusb-12 I think). After a minute my syslog filled to 1.3 GB and CPU usage jumped to 80% or so the whole time. I made a 30 second .gif if you're interested.

Disadvantage of 2 GB/s NVMe Gen 3 x 4 SSD is syslog can fill fast in a 1 minute loop. To empty the syslog I used echo > /var/log/syslog.

Maybe mkusb has a problem with your 2 GB/s NVMe Gen 3 x 4 SSD. How is it shown by lsblk?


sudo lsblk -f
sudo lsblk -m

After rebooting the mk-usb icon showed up normally in Dash and I successfully created today's build of Ubuntu 18.04 Bionic Beaver to USB thumb drive in Persistanced mode. Works Great :)

I'm glad the problem was solved by rebooting. But mkusb *should* work directly after installing (without rebooting).

I had an older dd wrapper script I had to disable with chmod a-x because it stops /bin/dd which mkusb calls.

This might have caused problems, but not the problem in Dash.

BTW Ubuntu 18.04 LTS Bionic Beaver per-releese worked flawlessly on Skylake i7-6700HQ laptop using internal 1080p screen and external 1080p tv hooked to Thunderbolt3, USB Type-C with DP to HDMI converter. I was impressed.

Bionic works well for me too. I have installed it in an external SSD and run it in various computers :-)

#744

[SIZE=4]mkusb version 12.3.0 and 12.3.1 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.3.0

  • dus dus-persistent mkusb-start mkusb-11:

zenity window sizes fixed for Ubuntu Bionic because of a new zenity version

mkusb 12.3.1

  • dus:

zenity window sizes fixed for Ubuntu Bionic because of a new zenity version (more)

[/td][/tr][/table]

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.3.1 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#745

[SIZE=4]VirtualBox in persistent live Ubuntu or Ubuntu family flavour[/SIZE]

There is a question at AskUbuntu about problems with VirtualBox is a persistent live system made with mkusb.

I tested with host systems made with mkusb from Lubuntu 16.04.1 LTS 'Xenial dot one' and 17.10.1 'Artful dot one'. I use a Lubuntu host because of the ultra-light desktop environment, to save as much horsepower and RAM as possible for the virtual machine and the guest operating system.

Problems with the graphics rendering with Lubuntu as guest made me confused, but I think those problems depend on the Lubuntu guest, and not on the host system (that it is a persistent live operating system). I had no problems with the guest system, when booted from standard Ubuntu, Kubuntu or Xubuntu.

In both cases I installed VirtualBox from the repositories,


sudo apt update
sudo apt install virtualbox

The first successful test was with a Lubuntu 16.04.1 64-bit host and a Xubuntu 16.04.1 64-bit guest.

To get a new, yet released and stable system, I focus on the host system made from Lubuntu17.10.1 'Artful dot one'. In this system I can run 'Try Ubuntu' with the following iso files as guest operating systems,

  • Kubuntu, Ubuntu, Xubuntu 16.04 LTS
  • Ubuntu 17.10
  • Ubuntu Bionic (to be released as 18.04 LTS)

See the attached screenshots.

[SIZE=3]Details[/SIZE]

I selected a suitable 'internal environment' in VirtualBox to match the guest operating system, that I wanted to run,

  • 'General -- Basic -- Version: Ubuntu (64-bit)
  • enough RAM (2 GB in a computer with 4 GB)
  • connected the virtual optical drive to an iso file
  • created a virtual disk
  • and in one case *installed* Xubuntu from xubuntu-16.04.1-desktop-amd64.iso

See the last screenshot.

Edit: Running VirtualBox in Lubuntu 16.04.1 LTS and 17.10.1, I found that the boot option nomodeset makes Virtualbox render the graphics correctly for Lubuntu 17.10.1 and Bionic guests, but the resolution will be limited to 1024x768 (and lower).

#746

I used:

sudo apt install virtualbox-qt

Not sure if there is a difference?

#747

C.S.Cameron said: I used:

sudo apt install virtualbox-qt

Not sure if there is a difference?

I have not tried virtualbox-qt. Is it better than the 'standard' virtualbox package?

What differences do you notice?

Edit: I tested (as before in a Lubuntu 17.10.1 host), and I noticed no difference between the VirtualBox engines installed by the packages virtualbox-qt and virtualbox.

#748

I attempted to create a live, persistent flash drive using mkusb with a linux-mint 18 iso image. I used the PPA approach, so I assume I had the most updated version of mkusb. Although mkusb did all the steps, it did not label the persistence drive as "casper-rw". Without that label on the persistence drive, the live flash will not save (well, it didn't for me anyways). If I had not known about the need for the label, I would not have been able to get persistence to work. Possibly mkusb needs to be updated to apply the label?

Thanks! Mark

#749

@marks2,

Please tell me the exact name of the Linux Mint 18 iso file, that you used, and I will test and debug mkusb.

[hr][/hr] Edit 1: Also, please tell me in which operating system (distro and version) you installed mkusb (and tried to create a persistent live Linux Mint pendrive).

[hr][/hr] Edit 2: Before knowing what you tried, I

  • downloaded linuxmint-18.3-cinnamon-64bit.iso
  • made a persistent live Mint drive (when booted in Ubuntu 16.04 LTS)
  • booted into the persistent live Mint drive
  • installed mkusb from the PPA
  • created another persistent live Mint drive (when booted in the persistent live Mint)

See the attached screenshot, which shows that the partition for persistence is labeled 'casper-rw'.

I rebooted into this new persistent live drive with Mint, and it works like it should for me.

So I think that you either used another Linux Mint iso file or were running another operating system, where you installed mkusb and tried to create a persistent live Linux Mint drive. Or maybe there was some temporary error or hardware error(?)

Please notice that mkusb can only create persistent live drives in a reliable way, in and with Ubuntu and Debian and some linux distros and re-spins, that are created from them and similar enough. So far the standard versions of Linux Mint have been similar enough to Ubuntu for mkusb to work, when I have tested it.

#750

[SIZE=5]How to keep /home from an old persistent live drive when creating a new one[/SIZE]

Instead of updating & upgrading a persistent live drive it is better to create a new drive from a newer iso file,

But this way you might lose everything, that you have installed and tweaked as well as your personal files.

[SIZE=4]The following steps work to keep the home directory /home (I tested it today),[/SIZE]

  • from an old Lubuntu 16.04.1 LTS persistent live system (created by mkusb)
  • to a new Lubuntu Bionic (18.04 LTS) persistent live system (created by mkusb).
  1. It is always a good idea to backup your persistent live drive regularly, at least your personal data. So this is the first step.
  1. The easiest way is to use two USB drives. If necessary, get a new USB drive (and a fast one).
  1. Use mkusb to create a fresh persistent live system in the new USB drive.
  1. Boot into this new USB drive and select [COLOR="#0000CD"]Try Lubuntu[/COLOR] (*not* with persistence).
  1. Plug in the old persistent live drive and let the partitions be mounted (wait a few seconds).
  1. Open a terminal window and run the following commands to check that the casper-rw partitions are mounted and that the relevant directories are there,

sudo lsblk -fm
sudo ls -l /media/lubuntu/casper-rw*
sudo ls -l /media/lubuntu/casper-rw*/upper

Check the rsync command line with a 'dry run',

sudo rsync -Havn /media/lubuntu/casper-rw1/upper/home /media/lubuntu/casper-rw/upper
  1. If necessary, mount the source partition or target partition and/or modify the command line. For example, if your old persistent live system was created with another tool or manually, you must probably mount the casper-rw file or partition manually.
  1. When the dry run looks good, remove the option n and run
sudo rsync -Hav /media/lubuntu/casper-rw1/upper/home /media/lubuntu/casper-rw/upper
  1. Shutdown
  1. Unplug the old persistent live drive. [COLOR="#cc0000"]Important![/COLOR]
  1. Reboot into the new old persistent live drive and select a Persistent live option.

Now the new persistent live system should use the home directory that you transferred from the old drive. Check for personal files, history in terminal window, tweaks etc. (But you must install program packages again, because they were not stored in you home directory.)

[SIZE=4]Alternative: create a home-rw partition[/SIZE]

You may prefer to create a separate partition with the label home-rw.

In this case you should copy from the old /home to the mountpoint of this partition (when it is not being used), so for example when booted live-only, Try Lubuntu.

So, if the mount point is /media/lubuntu/home-rw,

Test with dry run,

sudo rsync -Havn /media/lubuntu/casper-rw/upper/home/ /media/lubuntu/home-rw

Here there is an important trailing slash (.../home[COLOR="#cc0000"]/[/COLOR]). Modify if necessary and when it looks good, run

sudo rsync -Hav /media/lubuntu/casper-rw/upper/home/ /media/lubuntu/home-rw

This makes it easier in the future: You can simply keep your home-rw partition

  • copy the content with rsync from the old home-rw partition to a new home-rw partition in another drive or
  • copy from the backed up content of /home to a new home-rw partition).

When you have confirmed, that your system is persistent, and that it uses both casper-rw and home-rw, you can remove /media/lubuntu/casper-rw/upper/home/.

The following link describes a special case, but it can be useful because shows some more details,

What you can do with your two 4GB USB pendrives

#751

It was linuxmint-18.3-xfce-64bit.iso. Installed from a non-persistent stick with the same designation. Thanks!

#752

It works for me with linuxmint-18.3-xfce-64bit.iso too, just like with the Cinnamon version, described in post #747


mint@mint ~ $ sudo lsblk -fm /dev/sdb
NAME   FSTYPE  LABEL                       UUID                                 MOUNTPOINT NAME    SIZE OWNER GROUP MODE
sdb                                                                                        sdb    14.9G root  disk  brw-rw----
&#9500;&#9472;sdb4 iso9660 [COLOR="#cc0000"]Linux Mint 18.3 Xfce 64-bit[/COLOR] 2017-12-13-11-48-04-00               /cdrom     &#9500;&#9472;sdb4  1.7G root  disk  brw-rw----
&#9500;&#9472;sdb2                                                                                     &#9500;&#9472;sdb2    1M root  disk  brw-rw----
&#9500;&#9472;sdb5 ext4    [COLOR="#cc0000"]casper-rw[/COLOR]                   2e4566e7-0b1d-4e99-8161-acb337e4ab84            &#9500;&#9472;sdb5  6.5G root  disk  brw-rw----
&#9500;&#9472;sdb3 vfat    usbboot                     31EB-42C8                                       &#9500;&#9472;sdb3  244M root  disk  brw-rw----
&#9492;&#9472;sdb1 ntfs    usbdata                     550EB28B7925C6A4                                &#9492;&#9472;sdb1  6.5G root  disk  brw-rw----

mint@mint ~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           384M  6.1M  378M   2% /run
/dev/sdb4       1.8G  1.8G     0 100% /cdrom
/dev/loop0      1.7G  1.7G     0 100% /rofs
[COLOR="#cc0000"]aufs            6.4G   33M  6.1G   1% /[/COLOR]
tmpfs           1.9G  220K  1.9G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs           1.9G  8.0K  1.9G   1% /tmp
cgmfs           100K     0  100K   0% /run/cgmanager/fs
tmpfs           384M   40K  384M   1% /run/user/999
mint@mint ~ $

Please try again following the steps in that post. Good luck :-)

Edit: It might be easier for you to

  • first create a live-only USB drive with Linux Mint
  • boot into that drive and install mkusb from the ppa
  • make the Linux Mint iso file available to the system for example via an internal drive (or by copying it into the live-only system. which works if there is enough RAM).
  • use mkusb to create a persistent live system in another USB pendrive.

Then you can shutdown and remove the live-only pendrive and boot into the persistent live pendrive.

#753

This was pretty much the procedure I followed. The internal drive was a windows volume (because it had space). Had I been thinking, I would have captured the output of the mkusb. It seemed to be doing a lot more than when I had used unetbootin and certainly created more partitions. The only thing that broke was the labeling of the casper-rw partition. The target flash drive had 2 partitions (the wreckage of a Windows vs. Lin&#365; formatting disaster). Could that have thrown off the mkusb scripts? Thanks!

#754

sudodus said: [SIZE=5]How to keep /home from an old persistent live drive when creating a new one[/SIZE]

Instead of updating & upgrading a persistent live drive it is better to create a new drive from a newer iso file,

Is there a way to capture a list of installed apps and then use that to re-install apps? Re-installing apps is what seems to take a big block of time.

Thanks!

#755

Look in "Ubuntu Software" / "installed" for installed programs. However this does not show User installed programs I seem to recall that Synaptic gives that info.

#756

marks2 said: This was pretty much the procedure I followed. The internal drive was a windows volume (because it had space). Had I been thinking, I would have captured the output of the mkusb. It seemed to be doing a lot more than when I had used unetbootin and certainly created more partitions. The only thing that broke was the labeling of the casper-rw partition. The target flash drive had 2 partitions (the wreckage of a Windows vs. Lin&#365; formatting disaster). Could that have thrown off the mkusb scripts? Thanks!

mkusb starts by wiping the first mibibyte of the drive. That way the partition table is wiped, and the previous content of the drive is no longer relevant.

When creating a persistent live drive, mkusb creates 5 partitions. Partition #5 is labeled 'casper-rw' and will store data (that makes the system persistent live).

If there were only 2 partitions in the target drive after mkusb did its job, something went really wrong for you.

[hr][/hr] Please try again, and come back to tell us the result. If you start mkusb-dus from a terminal window, you can capture the output.


cd 'directory-where-you-have-the-iso-file'
dus linuxmint-18.3-xfce-64bit.iso

When mkusb-dus has finished, you can mark all text, copy it to clipboard, paste it into an editor, and save it as a file.

Then you can paste the content of the file from the editor to an edit window here at the Ubuntu Forums and render it as code. Please post the output between code tags like this

[noparse]```

output

 
to get output like this
 

output


This will help me debug your problem. Otherwise I can hardly guess (because it works for me).
#757

marks2 said: Is there a way to capture a list of installed apps and then use that to re-install apps? Re-installing apps is what seems to take a big block of time.

Thanks!

If you want/need to install a lot of program packages, I would recommend that you create an installed system (if not in an internal drive, you can install it into a USB drive of at least 16 GB). I mean installed the same way as into an internal drive, but into a USB drive. See this link,

Boot Ubuntu from external drive

#758

C.S.Cameron said: Look in "Ubuntu Software" / "installed" for installed programs. However this does not show User installed programs

I seem to recall that Synaptic gives that info.

@marks2,

I think, that the Synaptic Package Manager gives information about all installed packages. And it is there in

*Menu -- System*

of Linux Mint 18.3 Xfce.

#759

Rsync worked great maintaining permissions and all, (I prefer the grsync GUI if I gotta run rsync myself). I'm taking a look how this works with desktop /home partitions and/or directories. It might be cool to keep a flash drive OS sync'd with a desktop computer.

FYI, I avoid rsync more than I should so I used gparted to extract an existing home directory to a partition:

Made Persistent flash drive of new release using mkusb, created space for home partition using gparted. Copied casper-rw partition from old USB to space on new USB using gparted, changed label from casper-rw to home-rw, closed gparted, removed old USB. Ran gksu nautilus, mounted and opened home-rw, moved, (Not copied), contents of /upper/home/ to root of home-rw. Deleted any home folder from new casper-rw/upper/.

Rsyncing is probably easier.

So far in testing casper-rw files and home-rw files, (as found on a syslinux type USB's, ie UNetbootin), work in the same way as partitions but need to be mounted with sudo mount -o loop casper-rw /media/casper/ when worked on.

How hard would it be to add home-rw partitions to mkusb? Maybe a mkusb pro version.

#760

C.S.Cameron said: Rsync worked great maintaining permissions and all, (I prefer the grsync GUI if I gotta run rsync myself).

... How hard would it be to add home-rw partitions to mkusb? Maybe a mkusb pro version.

Not difficult, but a fair amount of hard work to make it work well ;-)

But I am not sure that it is a good idea to add it to mkusb, because there are advantages with a single partition for persistence: In a fairly small USB pendrive, the risk of filling one of two small partitions is higher than the risk of filling one partition with the size of both those two partitions.

Some time ago we were talking about offering a choice of udf file system in the casper-rw partition. I did not do it, partly because there is no repair tool for udf, partly because it is fairly easy to replace ext4 with udf with a few command lines, and we can link to instructions for it. I think similar arguments apply for a home-rw partition.

The instructions could be improved and more general. Maybe we can help each other to write such instructions and store them on a new page at

https://help.ubuntu.com/community/Installation/

or somewhere else, if you think there is a better place.

#761

You are right about casper-rw not being right for a small pendrive, I'd say less than 16GB, but I find it handy to have a seperate home if there is enough space, I always use a separate /home partition on internal installs and on external Full installs that I plan to use.

I can appreciate that it is a lot easier to add a home-rw partition by hand than to write it into mkusb, but it is still toward the top of my mkusb wish list.

#762

@C.S.Cameron,

I guess you mean 'You are right about home-rw not being right for a small pendrive'. I see your point, and I accept that you put making a 'home-rw' partition high on the wish-list. I will think about it again, and when there is time, I will fix it.

  • What about default size? Should the 'percentage for persistence' be divided in half?
  • What about installing in a drive with an existing 'home-rw' partition? Should it be preserved (and re-used)? It might be nice for the end user, but a bit more complicated for me to make.
#763

[SIZE=4]New tool to make persistent live drives with casper-rw and home-rw partitions[/SIZE]

mk-persistent-live_with_home-rw is a text mode shellscript, that builds a persistent live boot drive with a 'casper-rw' partition for system persistence and a 'home-rw' partition for home persistence. There are two modes, to

- create a persistent live system - upgrade a persistent live system, . replace the iso file . wipe: create new file system in the 'casper-rw' partition . preserve: keep the content in the 'home-rw' partition

The purpose of this tool is to make it easy to keep the persistent live drive up to date. Usually it does not work to simply transfer the whole content of the 'casper-rw' partition because the previous overlay of the system files does not match. But it is usually possible to keep the home directory including personal files and the settings (usually in hidden configuration files in the user's home directory).

[hr][/hr] There are more details and links to a download page at

'Post #144' in the Ubuntu Forum Tutorial thread

[B]One pendrive for all PC (Intel/AMD) computers - single-boot dual-boot multi-boot,

Make persistent live drives with casper-rw and home-rw partitions *New 2018-04-30*[/B]

You are welcome to test the shellscript and give feedback to help me make it better :-)

#764

[SIZE=4]mkusb can create a persistent live USB drive with Elementary OS[/SIZE]

I tested with the iso file elementaryos-0.4.1-stable.20180214.iso, and mkusb version 12.3.1 works without any tweaks.

See the following link,

elementary-persistent-live-by-mkusb.jpg

#765

[SIZE=4]Windows can use usbdata of persistent live drive by mkusb[/SIZE]

When mkusb creates a persistent live drive, partition #1 gets an NTFS file system and the label usbdata and it can be used, when connected to a computer running Windows.

There has been some doubts, that it does not work with Windows 10, so I have tested in a Windows 10 system, that is completely up to date (as well as previous tests with earlier versions (Windows XP, 7, 8, 10). It works for me, Windows can read and write files in the usbdata partition.

The following link shows what it looks like for me. You can expect to find something similar, but probably in another language, when you connect your persistent live drive to a computer running Windows 10,

windows-can-see-usbdata-of-persistent-live-drive-by-mkusb.jpg

[hr][/hr] In older versions of Windows, including the original Windows 10, only the first partition in USB pendrives could be read by Windows. This is the reason why I designed the partition table like this. The current up to date Windows 10 can read also other partitions, if there are Microsoft file systems, FAT32, exFAT, NTFS and also the file systems of CDs and DVDs, iso9660 and udf.

Although not located at the drive's head end, usbdata with NTFS is partition #1 in the partition table, and that is what counts. There are tools that can re-make the partition table so that the number in the partition table will match the position "on the drive's surfuce". If you use such a tool, there may be problems except with an up to date Windows 10. It manages several partitions also in USB drives. There will also be problems to use the drive as a persistent live drive. So do not tamper with the partition table unless you know what you are doing.

GPT is the modern partition table. Use it whenever you can. This is the default setting in mkusb.

But some middle-aged HP computers won't boot grub from GPT via USB. In that case you must create the persistent live drive with an MSDOS partition table (alias MBR).

#766

[SIZE=4]New tool to backup & restore the /home directory of persistent live drives in mkusb's casper-rw partition[/SIZE]

mkusb-backup-n-restore-home is a bash shellscript with a zenity graphical user interface, that 'only' manipulates the /home directory in casper-rw partitions of mkusb persistent drives.

There are two modes, to

  • backup the /home directory to a tarball
  • restore the /home directory from a tarball

The purpose of this tool is to make it easy to keep the persistent live drive up to date. Usually it does not work to simply transfer the whole content of the 'casper-rw' partition because the previous overlay of the system files does not match. But it is usually possible to keep the home directory including personal files and the settings (usually in hidden configuration files in the user's home directory).

Upgrade (or repair) a persistent live system like this:

  1. Backup the /home directory to a tarball using mkusb-backup-n-restore-home
  1. Create a fresh persistent live system of standard Ubuntu or the same flavour (Kubuntu, Lubuntu ... Xubuntu) as before using mkusb. Use the daily iso files of the LTS versions to get a system that is up to date.
  1. Restore the /home directory from the tarball to the fresh persistent live system.

[hr][/hr] There are more details and links to a download page at

'Post #149' in the Ubuntu Forum Tutorial thread

[B]One pendrive for all PC (Intel/AMD) computers - single-boot dual-boot multi-boot, Backup and restore the /home directory in casper-rw partitions of mkusb persistent drives *New 2018-05-20*[/B]

You are welcome to test the shellscript and give feedback to help me make it better :-)

#767

[SIZE=4]mkusb version 12.3.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.3.2

. new tool that can backup and restore the /home directory of casper-rw partitions of persistent live drives by mkusb-dus

  • dus: 'dus-home-backup' and 'dus-home-restore' in starter menu, see the two first attached screenshots.
  • dus-home-backup:
  • dus-home-restore: symbolic link to dus-home-backup
  • mkusb-backup-n-restore-home: symbolic link to dus-home-backup
  • the manual 'man mkusb' made up to date

[/td][/tr][/table]

You can backup a running persistent live drive. In that case you should *not* write the tarball into your home directory, but into another directory, for example an internal drive, another external drive or the drive's own 'usbdata' partition, if it is big enough. Mount the partition if necessary. See the third attached screenshot.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.3.2 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA.

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Upgrading mkusb is described in the following links,

help.ubuntu.com/community/mkusb#Upgrade_mkusb

Upgrading from mkusb 11 to 12

#768

[SIZE=4]Two help texts are upgraded to match mkusb version 12.3.2[/SIZE]

  • The built in text mode manual man mkusb
  • The pdf file mkUSB-quick-start-manual-12

You can download the quick start manual and check the md5sums at this link http://phillw.net/isos/linux-tools/mkusb/

[[img]https://help.ubuntu.com/community/mkusb/pictures?action=AttachFile&do=get&target=16-mkusb-quick-start-manual-12.png[/img]](http://phillw.net/isos/linux-tools/mkusb/mkUSB-quick-start-manual-12.pdf)

*Alternative:* You find alternate links at Quick start manual and mkusb PPA (if http://phillw.net/isos/linux-tools/mkusb/ is temporarity down).

#769

HiYa sudodus I'm here and got your message :) Will test this a bit later today>>>you know life gets in the way at times. ;) Anything you need me to check in particular?

#770

Hi @1fallen,

Please use mkusb version 12.3.2 (for example from the unstable PPA).

Please check

  • in bionic (standard Ubuntu or one of the community flavours, whichever you prefer, all should work)
  • clone the iso file to a live-only USB boot drive and check that it boots correctly
  • make a persistent live drive with default settings and check that it boots correctly
  • backup the home directory of the persistent live drive (after you have used it (and have at least some data in ~/.bash_history)
  • restore the home directory of the persistent live drive and check that it boots correctly and can use the restored data
  • extra (if you wish) - create another persistent live system (xenial or cosmic) and restore the home directory from the bionic system to this persistent live drive and check that it is portable between versions. This is easiest if you stay with the same flavour of Ubuntu.
#771

Ok, but give me some time later today.:) Maybe even tomorrow. That's a great check list and helps me a ton. Thanks sudodus

#772

Thanks @1fallen,

I'm looking forward to your results :-)

#773

I made a Ubuntu 18.04 flash drive from laptop running 16.04. Works great so far, very fast, easy to use, the home backup is a great feature as is. Restore gave a warning but worked ok.

What next?

#774

@C.S.Cameron,

Thanks for testing :-)

Please try to remember (or test again) to specify the warning.

[hr][/hr] What's next:

  • Copy this version (mkusb 12.3.2) to the stable PPA, ppa:mkusb/ppa
  • Maybe create a stand-alone tool to replace the ext4 file system in the 'casper-rw' partition with udf. (I don't want to integrate it in mkusb because there is no well-known tool to repair the udf file system. As you may remember, this is a way to keep Windows from prompting to format the partition.)
  • What would you suggest?
#775

"This casper-rw partition is not clean."

"It may work..."

#776

I see. This warning is written, when you restore to a 'casper-rw', where there are files already (in the home directory or in other system directories (except etc where mkusb writes some files to prevent massive automatic updates)).

Maybe it should be written in a different way: 'clean' could be replaced by 'empty' or some other word.

#777

I think this restore home option is a first for bootable USB makers, good work.

Sooo... I was just noticing that Startup Disk Creator now comes with QEMU, making it easy to test the finished flash drive without having to reboot the computer. MultiBootUSB also comes with a QEMU app.

Do you think it would be worth adding QEMU to mkusb?

If it is part of SDC then it is installed by default and only needs to be triggered when mkusb has completed an install. I don't think it would add any bulk to the mkusb app.

#778

@C.S.Cameron,

Thanks for the tip about QEMU :-) I will think about it, and see if I can use it, but I don't know how to do it in an easy way right now.

(I have use KVM with virt-manager (which is related to QEMU) but I have not used QEMU directly, except maybe several years ago.)

#779

Oops, I was wrong. QEMU does not come with SDC and I can't figure out how it got there, see:

https://askubuntu.com/questions/1049121/where-did-qemu-come-from-in-my-startup-disk-creator

#780

@C.S.Cameron,

I read your question at AskUbuntu. I tested in my Lubuntu 18.04 LTS, and I had no luck there either even though some QEMU packages are installed, but not the package qemu itself.

#781

For me Test Disk started working in SDC after running:

sudo apt-get install qemu-kvm qemu virt-manager virt-viewer libvirt-bin

There is some possibility it might be a combination of other QEMU commands I ran.

I will zero the disk and try again if you don't get it working.

#782

I will have a look at it, probably in a dedicated system that I set up in a separate computer (not my main computer). And it may take some time. Input from you is welcome in the meantime ;-)

#783

Zeroed the full USB using mkusb, installed Persistent Ubuntu 18.04 using mkusb defaults, booted USB and ran sudo apt-get install qemu-kvm qemu virt-manager virt-viewer libvirt-bin , rebooted and made a Live USB using Startup Disk Creator, option to Test Disk appeared at end of installation.

#784

That makes it easy to implement a testing environment, @C.S.Cameron,

It could be a good idea to look at the code of usb-creator-gtk to see how 'test' is implemented. I think it is a python script.

#785

Currently following up on a problem where the booting process hangs at post login. It may be some backlight issue, but I would like to update the BIOS on this Dell Laptop Inspiron 3542. But how do you update with a non Windows OS ? Dell have a guide at Updating the Dell BIOS in Linux and Ubuntu Environments

I'd much prefer to use mkusb though, so may ask on the Dell forum for them to change it. What is "disks" anyway ? I don't have that. Plus the Dell article states we will be notified if the BIOS needs updating. Nope, doesn't happen. Anyway, most of those issues I need to chase up with Dell; just checking here that mkusb is valid to use for updating the BIOS.

#786

oygle said: Currently following up on a problem where the booting process hangs at post login. It may be some backlight issue, but I would like to update the BIOS on this Dell Laptop Inspiron 3542. But how do you update with a non Windows OS ? Dell have a guide at Updating the Dell BIOS in Linux and Ubuntu Environments

Dell's link looks good. Please notice that there is a difference between systems 2015 onwards and systems before 2015. I found documentation for your computer model from 2014, but the computer might still be manufactured 2015 onwards, so I don't know what to select.

Maybe it is safest to use FreeDOS.

I'd much prefer to use mkusb though, so may ask on the Dell forum for them to change it. What is "disks" anyway ? I don't have that. Plus the Dell article states we will be notified if the BIOS needs updating. Nope, doesn't happen. Anyway, most of those issues I need to chase up with Dell; just checking here that mkusb is valid to use for updating the BIOS.

  • I have never used mkusb to update the BIOS, so I cannot give you any guarantee, but it can to do what Disks can do (to create a partition with a FAT32 file system) as described in Dell's link.
  • Disks alias gnome-disksis a tool to do several tasks with mass storage devices (disks, drives), and it is bundled with Ubuntu and several (maybe all) Ubuntu community flavours.
#787

sudodus said: Dell's link looks good. Please notice that there is a difference between systems 2015 onwards and systems before 2015. I found documentation for your computer model from 2014, but the computer might still be manufactured 2015 onwards, so I don't know what to select.

Thanks, I have since been notified by Dell that it is a 2014 model.

sudodus said:

Maybe it is safest to use FreeDOS.

Yes, probably.

sudodus said:

  • Disks alias gnome-disksis a tool to do several tasks with mass storage devices (disks, drives), and it is bundled with Ubuntu and several (maybe all) Ubuntu community flavours.

Okay, I guess if that is the tool they suggest, I'd better use that. Thanks for your help. :)

#788

I've been using a persistent flash drive made with mkusb for a few weeks. The drive made with mkusb is more reliable than the other flash techniques including a full install to a flashdrive (actually all the other approaches corrupt within a day or two).

I know it's usually suggested that you can't upgrade grub on a persistent flashdrive, but since mkusb creates a real partition (not a iso file), I'm wondering if a method has been worked for making necessary upgrades.

In particular, I would like to upgrade grub to allow the insertion of the intel microcode. This is in response to the Meltdown/Spectre memory threat. If there was some minor concern about drivers I would not want to try this. But in light of the seriousness of the threat I thought an approach like this would be helpful

My strategy is posted below. Will this work? Could it work with tweaks? It would be sad if it corrupted my current setup, which has been working well.

Thanks! Mark

Putting together posts from other forums and conversations, this is the strategy I was thinking of: [COLOR=#000000][FONT=Arial] #1 Boot without persistence

Make working directories

mkdir /media/{rootfs,cow,persist_usb}[/FONT][/COLOR]

#Mount the persistent directory [COLOR=#000000][FONT=Arial]mount /dev/sd?4 /media/cow[/FONT][/COLOR]

#(I don't know what letter until I try this)

#Mount the supporting systems:

[COLOR=#000000][FONT=Arial]for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do[/FONT][/COLOR][COLOR=#000000][FONT=Arial] [/FONT][/COLOR][COLOR=#000000][FONT=Arial] mkdir /media/rootfs/$dir && mount --bind /$dir /media/rootfs/$dir[/FONT][/COLOR][COLOR=#000000][FONT=Arial] [/FONT][/COLOR][COLOR=#000000][FONT=Arial]done[/FONT][/COLOR][COLOR=#000000][FONT=Arial]

combine the supporting directories and persistent directory

[/FONT][/COLOR] [COLOR=#000000][FONT=Arial]mount -t aufs -o dirs=/media/cow/../upper=rw:/media/rootfs=ro unionfs /media/persist_usb[/FONT][/COLOR]

change root to the combined directory and update grub

[COLOR=#000000][FONT=Arial]chroot /media/persist_usb [/FONT][/COLOR][COLOR=#000000][FONT=Arial] [/FONT][/COLOR][COLOR=#000000][FONT=Arial]update-grub2 # inside chroot[/FONT][/COLOR]

#789

@marks2,

I'm glad that your persistent live drive works well :-)

But I am not sure that it will work to upgrade grub in order to make your Intel microcode work. This does not mean that I think it will not work. I simply do not understand how to make it work and check that it really works.

On the other hand, you can use a new version of Ubuntu or Ubuntu community flavour (Kubuntu, Lubuntu, ... Xubuntu), where the Meltdown/Spectre memory threat is mitigated.

See this link: SpectreAndMeltdown

If you make a persistent live system from an 18.04.1 LTS iso file, there should be no problem.

If you want to keep the content of your home (personal files and tweaks), you can use mkusb to backup and restore home to this new persistent live system.

#790

There are tests that will tell you if the microcode has been loaded.

I don't suppose there's a way to just replace the 18.04 partition (the one that is/was an ISO I assume) with 18.04.1 ?? Otherwise, if I run mkusb again, I assume everything (including all the software I've installed) will get wiped. So even though I've made a backup it will be a long time before everything is working OK.

Thanks! -- Mark

#791

@marks2,

I thought that you were using an older version.

Also in Ubuntu 18.04 LTS (the original iso file released in April 2018) the Meltdown/Spectre memory threat is mitigated. This work was done during the end of 2017 and the very beginning of 2018.

So if you are happy with the function of your current persistent live system made from 18.04 LTS, you need not worry about the Meltdown/Spectre memory threat.

#792

@sudodus

Maybe I'm trying to fix the wrong problem then. During the boot I get a microcode warning:

TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)

The subsequent lines report that microcode is updated to version 0x17. So it's 11 updates behind. I have no idea how significant that is.

Apparently the Meltdown thing is continuing to evolve.

I'm wondering if there is a way to just replace the iso9660 partition (it's dev/sdb4 on my setup) with the iso from a new live stick?

Thanks! Mark

#793

marks2 said: @sudodus

Maybe I'm trying to fix the wrong problem then. During the boot I get a microcode warning:

TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)

The subsequent lines report that microcode is updated to version 0x17. So it's 11 updates behind. I have no idea how significant that is.

Neither do I (know how significant that is).

Apparently the Meltdown thing is continuing to evolve.

The microcode is doing other things too (not only mitigating Meltdown and Spectre), so the upgrades might focus on other tasks ...

I'm wondering if there is a way to just replace the iso9660 partition (it's dev/sdb4 on my setup) with the iso from a new live stick?

[B]If there is space enough (in the partition) you can clone from the iso file to the partition (/dev/sdx4) but after that you cannot expect the persistent live drive to work. The 'system content' of the casper-rw partition will no longer match what it is supposed to overlay. [/B] The 'home content' will be OK, but for example installed program packages will be lost, if you backup 'home', create a new system and restore 'home' to the new system. (What you suggest is equivalent to that action.)

#794

It turns out that 18.04.1 has the same problem. Why did they release .1 without fixing that? So it might require the steps I initially outlined, attempting to write to partition that is usually read-only.

Thanks -- Mark

#795

@marks2,

Instead of fighting with a persistent live system, you can try to create an installed system in a fast USB 3 pendrive or an SSD connected via USB 3 or eSATA. This way you will get a system, where is it possible (maybe even easy) to install the Intel microcode, that you want. I am running such systems successfully, and I find them stable.

See this link with details to help with the installation: How do I install Ubuntu to a USB key? - install like into an internal drive

#796

Yes, I'll probably try that next. I actually had done that with a Kingston USB3. It lasted maybe 3 days before corrupting. It seems to me that that there are optimizations for running on a flash that are not made with a full install. You don't want all that IO activity that a real drive can handle.

It may not be a fair comparison since the persistent drive I'm currently using supports higher speeds.

The best luck I've had with persistent setups was with puppy linux installed on a no-name USB2 flash drive that I used for years. The puppy approach prevented I/O blocking and over-frequent writes to the drive. Unfortunately, puppy is now only randomly supported.

The situation with Spectre sounds pretty dire. It appears that the new debian/ubuntu ISOs are being shipped with the bad microcode that intel rolled back. This may actually be worse than no microcode at all. The distributors probably assume that users can upgrade as soon as they install. But this isn't true with a live system.

Thanks! -- Mark

#797

Hey sudodus, I've installed persistent Ubuntu 18.04 using mkusb, but from the first time I did boot up I've got weird temporal background color switches: https://askubuntu.com/questions/1078919/booting-ubuntu-18-04-strange-white-green-blue-background

They do not bother much, but I'm interested in solution or some kind of guideline where I could check for defect that causes these background changes.

Also, it seems that running command [B]sudo update-initramfs -c Gives me this output:[/B] > update-initramfs is disabled since running on read-only media The strange output appears mentioning that I'm running on a read-only media. But the changes I make to the system are persistent. This is kind of confusing

#798

boqsc said: Hey sudodus, I've installed persistent Ubuntu 18.04 using mkusb, but from the first time I did boot up I've got weird temporal background color switches: https://askubuntu.com/questions/1078919/booting-ubuntu-18-04-strange-white-green-blue-background

They do not bother much, but I'm interested in solution or some kind of guideline where I could check for defect that causes these background changes.

I think it is a compatibility problem between the graphics driver and and the graphics chip/card at an early stage of the boot process. One way to 'get rid of it' should be to turn off the plymouth output of '5 dots' by removing 'splash' from the lines starting with 'linux' in .../boot/grub/grub.cfg.

Mount the usbboot partition, edit the file with nano and save it. Replace x by the actual drive letter for the persistent live drive, for example b or c.


sudo mount /dev/sdx3 /mnt
sudo nano /mnt/boot/grub/grub.cfg

Also, it seems that running command [B]sudo update-initramfs -c Gives me this output:[/B]

update-initramfs is disabled since running on read-only media

The strange output appears mentioning that I'm running on a read-only media. But the changes I make to the system are persistent. This is kind of confusing

'update-initramfs' is intended for installed systems, not for live or persistent live systems.

(The output message is somewhat misleading.)

#799

sudodus said: I think it is a compatibility problem between the graphics driver and and the graphics chip/card at an early stage of the boot process. One way to 'get rid of it' should be to turn off the plymouth output of '5 dots' by removing 'splash' from the lines starting with 'linux' in .../boot/grub/grub.cfg.

Mount the usbboot partition, edit the file with nano and save it. Replace x by the actual drive letter for the persistent live drive, for example b or c.


sudo mount /dev/sdx3 /mnt
sudo nano /mnt/boot/grub/grub.cfg

Well, this solution solves splash screen background problem by removing the splash screen itself. No Splash screen - no Splash screen background problem. :|

#800

boqsc said: Well, this solution solves splash screen background problem by removing the splash screen itself.

No Splash screen - no Splash screen background problem. :|

That's right.

A problem with live and persistent live systems is that you cannot use a separately installed graphics driver (the overlay of a persistent live system is applied after the driver is activated). It might help with some boot option, for example 'nomodeset', but you might as well turn off the splash screen, so that is what I would recommend.

#801

Is there any known method to reconnect live persistent usb drive after it was accidently disconnected?

#802

boqsc said: Is there any known method to reconnect live persistent usb drive after it was accidently disconnected?

No, I am sorry, but I don't think so.

[hr][/hr] If you are lucky, there was nothing in the buffer (waiting to be written to the casper-rw partition), otherwise the data for persistence might be corrupted and you need to *restore the casper-rw partition from the backup*.

If there is no backup, you should wipe the content of the casper-rw partition and start from the beginning to install programs etc. It might be possible to save the content of your home directory.

#803

sudodus said: @marks2,

Instead of fighting with a persistent live system, you can try to create an installed system in a fast USB 3 pendrive or an SSD connected via USB 3 or eSATA. This way you will get a system, where is it possible (maybe even easy) to install the Intel microcode, that you want. I am running such systems successfully, and I find them stable.

See this link with details to help with the installation: How do I install Ubuntu to a USB key? - install like into an internal drive

I've done this as well, installed to a generic USB3 flash drive. It seems to work fine though it's slower than installing to a HDD or SDD. My machine having USB2 ports didn't help anything, I'm sure. I can't comment about durability, i haven't used it that much. it used to be recommended to use an ext2 file system to reduce writes (no journal) but I've also read that the latest iterations of of ext4 don't produce much more flash wear than ext2. Just take your time and put the bootloader on the correct drive.

#804

@sudodus, Ubuntu 18.10 has been released, mkusb works fine, I'm writing from persistent Ubuntu. Side note: I've got an error printed out in the terminal while using mkusb:

- sed:tweak 3 grub.cfg

Failed :-( Check carefully what happened But as I said, it had no effect, at least so far, on operating system's usability.

#805

@boqsc ,

The error output you refer to is caused by the following code in the file dus-persistent of mkusb.


# tweak 3 grub.cfg

# search by UUID

partprobe
mount "$part" "$targ1" 2>&1
uid4="$(lsblk -Po name,uuid "${tu}4"|cut -d '"' -f 4)"
if [ "$uid4" != "" ]
then
 [COLOR="#B22222"]sed -i "s/set root=(hd0,4)/search --set=root --fs-uuid $uid4/" "$targ1"/boot/grub/grub.cfg[/COLOR]
 if [ $? -ne 0 ]
 then
  error="$error - sed: tweak 3 grub.cfg"
  result="failed :-("
  echo "$result"
 fi
fi

It works for me, when run in an up to date installed Lubuntu 18.04 LTS (64-bit) to create Ubuntu 18.10. I used default settings (in mkusb).

The result in the file grub.cfg is


 menuentry "Run Ubuntu - persistent live" {
[COLOR="#B22222"] search --set=root --fs-uuid 2018-10-17-22-44-30-00[/COLOR]
        set gfxpayload=keep
        linux   ($root)/casper/vmlinuz  file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash persistent ---
        initrd  ($root)/casper/initrd
}

which means that the sed command was successful (and should return 0 on exit).

Please note that mkusb creates a persistent live system that works in most cases also when this sed command fails, but it will be more robust when the sed command succeeds.

[hr][/hr] Can you find something that is different in your case compared to my case? In what operating system did you install and run mkusb? Version and flavour of Ubuntu? Other possible differences? If you tell me the details I can create such a system and try to reproduce your result (with the error output).

#806

[SIZE=4]mkusb version 12.3.2 for version 19.04, Disco Dingo[/SIZE]

The PPA at Launchpad includes versions of mkusb for the new developing version 19.04, Disco Dingo.

mkusb was tested today, 2018-11-05, with a Lubuntu daily iso file from the testing tracker, disco-desktop-amd64.iso, and it works as it should.

[hr][/hr] If you run standard Ubuntu, you need an extra instruction to get the repository Universe. (Kubuntu, Lubuntu ... Xubuntu have the repository Universe activated automatically.)

Text after the # character is not used by the shell interpreter, it is a comment for the human eye.

sudo add-apt-repository universe  # this line only for standard Ubuntu
sudo add-apt-repository ppa:mkusb/ppa          # stable PPA for regular usage
# sudo add-apt-repository ppa:mkusb/unstable   # PPA for development and testing; remove the # in front of the command to use it
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#807

Short version: Selecting "Start Lubuntu - persistent live", "Start Lubuntu - persistent live to RAM" and "Start Lubuntu" from the grub menu all lead to the following error:


error:  disk `hd0,4' not found.
error:  you need to load the kernel first.

Press any key to continue. . .

Looking at [FONT=&quot]/dev/sdb3[/FONT], the grub.cfg file indeed has [FONT=&quot]set root=(hd0,4)[/FONT] in each stanza. Dropping into the grub command line and doing the [FONT=&quot]set root=([TAB][/FONT] thing, the available drives are [FONT=&quot]memdisk[/FONT], [FONT=&quot]hd0[/FONT], [FONT=&quot]hd1[/FONT] and [FONT=&quot]hd2[/FONT]. We're looking for ($root)/casper/vmlinuz, and it'll be on the EFI partition. Hand-editing the grub cfg at boot time so that root points to (hd1,gpt3) works a charm.

Any ideas on why the correct partition wasn't picked up when the USB was created?

System info: USB created using mkusb 11.2.2 running under and up-to-date Ubuntu 18.04.1 LTS host. ISO is lubuntu-18.04-desktop-amd64.iso.

#808

@rountree,

Thanks for the feedback :-)

The development of mkusb version 11 was discontinued long ago (there was some overlap with version 12 'dus'). But I must admit, that version 11 has not been tested with Ubuntu 18.04 LTS and later versions, while it may still be a good alternative for older versions of Ubuntu and Ubuntu community flavours like Lubuntu.

Please use the current version 12.3.2 (also known as 'dus' and 'mkusb-dus'). It is tested with all the current versions of Ubuntu and the Ubuntu community flavours including 18.04.x LTS, 18.10 and Disco Dingo (to be released as 19.04), and I think it can do what it is expected to do.

By the way, lubuntu-18.04.1-desktop-amd64.iso is debugged and polished compared to lubuntu-18.04-desktop-amd64.iso. Both iso files come with the linux 4.15 kernel series.

In the attached file (created with default settings by mkusb version 12.3.2 in my Lubuntu 18.04.1 LTS installed system) you can see that there is persistence (the root partition has the same data as the casper-rw partition as shown by df).

#809

@sudodus

Thanks for the quick response! I'll grab the latest version and see if it's fixed there.

Barry

#810

Hello Sudodus

I made presistent live USB stick of Xubuntu 18.04.1 by dus 12.3.2. In presistent session I installed nvidia-340 (in Additional drivers dialog) in order to test, if the driver works with certain Nvidia graphics hardware. I wish it could be used with more than one hardware for which the driver is meant for. When I rebooted the persistent live, I saw by ``` sudo lshw -c video | grep driver

#811

jis said: So I wonder why the driver can not work in persistent USB session?

Proprietary video drivers need to load before the casper-rw persistence partition loads. A cart before the horse thing as the instructions to load the driver are located in the persistence file.

If you want to use proprietary drivers, you need to do a Full install to USB.

Good news is that Nvidia now does not load the drivers if the computer does not have a Nvidia card.

#812

C.S.Cameron said: Proprietary video drivers need to load before the casper-rw persistence partition loads. A cart before the horse thing as the instructions to load the driver are located in the persistence file.

If you want to use proprietary drivers, you need to do a Full install to USB.

Good news is that Nvidia now does not load the drivers if the computer does not have a Nvidia card. +1 :-)

See for example How do I install Ubuntu to a USB key? (without using Startup Disk Creator)

@C.S.Cameron, you know some good methods too (please post a link or two).

#813

mkusb is well documented ... but I'm puzzled at the behavior on Ubuntu 18.10

Installed per the wiki

sudo -H dus custom.iso dus 12.3.2 Drive that contains source file: /dev/sda Live drive, that is booted from: /dev/sda cands=2 20G 20G built-in device sdc SanDisk_Cruzer_Glide 14.3G usb USB or memory card p_target: target=/dev/14.3G No target device or bad target device p_clean:

That is, creating a persistent volume keeps failing ... the target appears healthy (can install other stuff to it, reformat, etc.) I'd have expected it to be addressed as /dev/sdc (actually, at the time I thought it was sdb, but I've done enough experiments and changed ports, it's changed places over time).

Is there some part of the fine wiki I've missed? Some obvious configuration blunder?

#814

@khbkhb,

  1. Something goes very wrong when you get

p_target: target=/dev/14.3G

Let us try to debug the problem together.

  1. Is Ubuntu 18.10
  • the operating system, where you installed mkusb, or
  • the operating system, that you want to install (somehow customized)?
  1. Please describe with more details your custom iso file.
  1. I run dus directly without sudo as

dus custom.iso

Please try if that works better.

[hr][/hr]

  1. Please run the following commands (with your USB pendrive, the SanDisk_Cruzer_Glide, connected).

sudo lsblk -f
sudo lsblk -m
sudo parted -ls
df -h

Post the output between code tags like this (it makes the output easier to read)

[noparse]```

output

 
to get output like this
 

output


[hr][/hr]
Edit 1:

I tested in an Ubuntu 18.10 system, installed and up to date (updated & upgraded today), and mkusb works for me. There is something in your Ubuntu system, that is confusing the identification of drives.

It will be interesting to see the output of the four command lines according to item 4 above.

tester@tester-desktop:/mnt/home/tester/Downloads$ [COLOR="#0000FF"]dus ubuntu-18.10-desktop-amd64.iso [/COLOR] dus 12.3.2 live system or temporary superuser permissions Drive that contains source file: /dev/sda Live drive, that is booted from: /dev/sda cands=2 sdb DT_Workspace_32GB 29,1G ata built-in device sdc SanDisk_Cruzer_Blade 3,7G usb USB or memory card p_target: target=/dev/sdb live system or temporary superuser permissions settings= percent=50 Prepare persistent live system from 'ubuntu-18.10-desktop-amd64.iso' to the target device (drive) '/dev/sdb' MODEL NAME FSTYPE LABEL SIZE DT Workspace sdb 29,1G &#9500;&#9472;sdb1 ntfs usbdata 13,5G &#9500;&#9472;sdb2 1M &#9500;&#9472;sdb3 vfat usbboot 244M &#9500;&#9472;sdb4 iso9660 Ubuntu 18.10 amd64 1,9G &#9492;&#9472;sdb5 ext4 casper-rw 13,5G p_clean: live system or temporary superuser permissions Drive that contains source file: /dev/sda Live drive, that is booted from: /dev/sda cands=2 sdb DT_Workspace_32GB 29,1G ata built-in device sdc SanDisk_Cruzer_Blade 3,7G usb USB or memory card p_target: target=/dev/sdb settings=msdos percent=50 Prepare persistent live system from '/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso' to the target device (drive) '/dev/sdb' MODEL NAME FSTYPE LABEL SIZE DT Workspace sdb 29,1G &#9500;&#9472;sdb1 ntfs usbdata 13,5G &#9500;&#9472;sdb2 1M &#9500;&#9472;sdb3 vfat usbboot 244M &#9500;&#9472;sdb4 iso9660 Ubuntu 18.10 amd64 1,9G &#9492;&#9472;sdb5 ext4 casper-rw 13,5G /mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso /dev/sdb 50 settings=msdos ----- live system or temporary superuser permissions /mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso /dev/sdb 50 settings=msdos source=/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso target=/dev/sdb percent=50 msdos=true upefi=false dni=false source=/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso ls -l /mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso -rw-r--r-- 1 tester 1003 1999503360 mar 2 11:59 /mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso --------------------------------------------------------------------------- start [dus-persistent 12.3.0] @ 2019-03-02 14:17:20 --------------------------------------------------------------------------- Making a USB boot drive or memory card .......................... running operating system: ubuntu grub_n_iso "$source" "$target" "$result" grub_n_iso /mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso /dev/sdb *** tu=/dev/sdb ************************************************** selected target partition table: 'msdos' --------------------------------------------------------------------------- mount: /tmp/dus.q7IdlRWz28: WARNING: device write-protected, mounted read-only. Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 --------------------------------------------------------------------------- mount: /tmp/dus.xPQtOVETj3: WARNING: device write-protected, mounted read-only. select_boot_system: usb-pack_efi is available select_boot_system: usb-pack_efi: using variable 'upefi=false' item 00 '/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso' is identified as the source ISO file <pre> MODEL NAME FSTYPE LABEL MOUNTPOINT SIZE DT Workspace sdb 29.1G |-sdb1 ntfs usbdata 13.5G |-sdb2 1M |-sdb3 vfat usbboot 244M |-sdb4 iso9660 Ubuntu 18.10 amd64 1.9G `-sdb5 ext4 casper-rw 13.5G </pre> Using the file '/usr/share/mkusb/grub.cfg' item 10 Clean for a GUID partition table GPT fdisk (gdisk) version 1.0.3

Warning! Disk size is smaller than the main header indicates! Loading secondary header from the last sector of the disk! You should use 'v' to verify disk integrity, and perhaps options on the experts' menu to repair the disk. Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header.

Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged

************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************

Command (? for help): This option deletes all partitions and creates a new protective MBR. Proceed? (Y/N): Command (? for help): Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdb. The operation has completed successfully. Wipe the first megabyte (mibibyte) to get a clean boot area 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00255564 s, 410 MB/s Wait 5 seconds and a little more ... item 20

selected 'grub.img' --------------------------------------------------------------------------- Selected percentage of remaining space for persistence = 50 ---------------------------------------------------------------------------

partition 2 - bios_grub installing via 'grub.img' partition 3 - fat32 boot,efi via 'grub.img' ... 62976+0 records in 62976+0 records out 257949696 bytes (258 MB, 246 MiB) copied, 2.52553 s, 102 MB/s GPT fdisk (gdisk) version 1.0.3

Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header.

Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables.

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged

************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************

Command (? for help): Caution: The CRC for the backup partition table is invalid. This table may be corrupt. This program will automatically create a new backup partition table when you save your partitions.

Problem: The secondary header's self-pointer indicates that it doesn't reside at the end of the disk. If you've added a disk to a RAID array, use the 'e' option on the experts' menu to adjust the secondary header's and partition table's locations.

Identified 2 problems!

Command (? for help): Expert command (? for help): Relocating backup data structures to the end of the disk

Expert command (? for help): Recovery/transformation command (? for help): Recovery/transformation command (? for help): Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdb. The operation has completed successfully. partition 1 - ntfs 'usbdata' Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. partition 4 - iso9660 - cloned system Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. partition 5 - ext4 - 'casper-rw' Warning: The resulting partition is not properly aligned for best performance. Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. item 30 using grub.img: keeping file system of /dev/sdb3: item 40 preparing /dev/sdb1 ------------------------------------------------ 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0643452 s, 16.3 MB/s umount: /dev/sdb1: not mounted. Cluster size has been automatically set to 4096 bytes. Creating NTFS volume structures. Creating root directory (mft record 5) Creating $MFT (mft record 0) Creating $MFTMirr (mft record 1) Creating $LogFile (mft record 2) Creating $AttrDef (mft record 4) Creating $Bitmap (mft record 6) Creating $Boot (mft record 7) Creating backup boot sector. Creating $Volume (mft record 3) Creating $BadClus (mft record 8) Creating $Secure (mft record 9) Creating $UpCase (mft record 0xa) Creating $Extend (mft record 11) Creating system file (mft record 0xc) Creating system file (mft record 0xd) Creating system file (mft record 0xe) Creating system file (mft record 0xf) Creating $Quota (mft record 24) Creating $ObjId (mft record 25) Creating $Reparse (mft record 26) Syncing root directory index record. Syncing $Bitmap. Syncing $MFT. Updating $MFTMirr. Syncing device. mkntfs completed successfully. Have a nice day. preparing /dev/sdb5 ------------------------------------------------ 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0117795 s, 89.0 MB/s umount: /dev/sdb5: not mounted. mke2fs 1.44.4 (18-Aug-2018) Creating filesystem with 3532667 4k blocks and 884736 inodes Filesystem UUID: 93537b80-4975-4357-814f-c028242afcd2 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done

item 50 mount: /tmp/dus.xPQtOVETj3: /mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso is already mounted. fatlabel: warning - lowercase labels might not work properly with DOS or Windows tune2fs 1.44.4 (18-Aug-2018) --------------------------------------------------------------------------- source=/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso --------------------------------------------------------------------------- item 60 umount: /dev/sdb3: not mounted. mount /dev/sdb3 /tmp/dus.ss4BsyAKRB /dev/sdb3 241M 6.1M 235M 3% /tmp/dus.ss4BsyAKRB item 65 umount: /dev/sdb1: not mounted. /dev/sdb1 14G 65M 14G 1% /tmp/dus.VhmwNfOMl0 use 'grub.img' so do not remove files: item 70 UEFI Bootloader: Installing for x86_64-efi platform. Installation finished. No error reported. item 80 Bootloaders via 'grub.img', skipping 'usb-pack_efi': set timeout=10 set default=0 menuname: ubuntu-18.10-desktop-amd64.iso set security upgrade action to 'Display immediately' umount: /dev/sdb4: not mounted. --------------------------------------------------------------------------- do_n_show: &lt; "/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso" pv -ni2 | dd of=/dev/sdb4 bs=4096

( < "/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso" pv -ni2 | dd of=/dev/sdb4 bs=4096 && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 ) Please wait for sync (flushing file system buffers to the device) until 'Done' is written ... 'pv %'; 'dd final output' 31 41 49 55 61 67 72 78 84 91 97 100 488160+0 poster in 488160+0 poster ut 1999503360 byte (2,0 GB, 1,9 GiB) kopierade, 31,0616 s, 64,4 MB/s Done do_n_show: Work done --------------------------------------------------------------------------- Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. Syncing the target device ... item 90 Wait 5 seconds and a little more ... <pre> parted -s "/dev/sdb" print Model: Kingston DT Workspace (scsi) Disk /dev/sdb: 31.2GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags:

Number Start End Size File system Name Flags 2 1049kB 2097kB 1049kB primary bios_grub 3 2097kB 258MB 256MB fat32 primary boot, esp 4 258MB 2277MB 2019MB primary 5 2277MB 16.7GB 14.5GB ext2 primary 1 16.7GB 31.2GB 14.5GB ntfs primary msftdata

lsblk -o MODEL,NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE "/dev/sdb" MODEL NAME FSTYPE LABEL MOUNTPOINT SIZE DT Workspace sdb 29.1G |-sdb1 ntfs usbdata 13.5G |-sdb2 1M |-sdb3 vfat usbboot 244M |-sdb4 iso9660 Ubuntu 18.10 amd64 1.9G `-sdb5 ext4 casper-rw 13.5G </pre> Done :-) The target device is ready to use. '/mnt/home/tester/Downloads/ubuntu-18.10-desktop-amd64.iso' was installed item 100 Cleanup after dus-persistent finished :-) Cleanup after dus-persistent finished :-) --------------------------------------------------------------------------- Total time used [by dus-persistent] = 91 s; 00:01:31 p_clean: live system or temporary superuser permissions clean if necessary and return

tester@tester-desktop:/mnt/home/tester/Downloads$ [COLOR="#0000FF"]lsb_release -a[/COLOR] No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.10 Release: 18.10 Codename: cosmic

tester@tester-desktop:/mnt/home/tester/Downloads$ [COLOR="#0000FF"]uname -a[/COLOR] Linux tester-desktop 4.18.0-15-generic #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux tester@tester-desktop:/mnt/home/tester/Downloads$

#815

[SIZE=4]Problem with the 4 GiB max file size in FAT32[/SIZE]

Several (but not all) Windows 10 iso files released in October 2018,

Win10_1809Oct_Language_x64.iso
  • use woeusb according to this link. This works in both BIOS and UEFI mode but not with secure boot.
#816

Hi, I found this thread because I had some problems with an installation of KNOPPIX and the DVD version exceeds 4GB. For my problem I found the use of ddrescue to be the solution as in the third possibility of https://fossbytes.com/create-bootable-usb-media-from-iso-ubuntu/ and it has the advantage of being straightforward and it works on Ubuntu 18.10 as that is what I'm running on this PC.

#817

@jdeca57,

*Thanks for your tip about ddrescue*, a tool that I am using right now to extract as much as possible from a friend's two DVD disks from the baptize ceremony for his son. The DVD disks are terribly scratched and ddrescue does a tremendous job. I have used ddrescue to save what can be saved from failing hard disk drives too :-)

mkusb *can* manage iso files that exceed 4 GiB. The problem of my previous post is about files contained in the iso files (in this particular case install.wim) that exceed 4 GiB in recent Windows iso files. I don't think any *file inside* a Knoppix 'DVD' iso file exceeds that level, and by the way, that is not relevant, when cloning the iso file.

ddrescue as well as dd and other *cloning tools* can create live-only boot drives from linux iso files that are *hybrid* iso files. mkusb can also clone it (and in a safer way, because it helps you identify the target drive and provides a final checkpoint).

[hr][/hr] Do I read your post correctly, when I assume that the current Knoppix DVD iso file is a hybrid iso file? Previous versions, that I have tested were not, and must be treated with isohybrid in order to make USB boot drives when cloned. See the following link,

help.ubuntu.com/community/mkusb/install-to-debian#Knoppix.

#818

sudodus said: @jdeca57,

Do I read your post correctly, when I assume that the current Knoppix DVD iso file is a hybrid iso file? Previous versions, that I have tested were not, and must be treated with isohybrid in order to make USB boot drives when cloned.

Well if you mean that it booted after a ddrescue and nothing else then yes, the current 8.2 is hybrid. But OK, in a few weeks they release 8.5...

#819

jdeca57 said: Well if you mean that it booted after a ddrescue and nothing else then yes, the current 8.2 is hybrid. But OK, in a few weeks they release 8.5...

Yes, that is what I mean. I downloaded and tried the current version of Knoppix and you are right.

It looks very interesting; for example, after cloning it uses the remaining space of the USB pendrive for a partition 'KNOPPIX-DATA' with the reiserfs file system. It manages to create a persistent live system automatically (after cloning)!

#820

sudodus said: Yes, that is what I mean. I downloaded and tried the current version of Knoppix and you are right.

It looks very interesting; for example, after cloning it uses the remaining space of the USB pendrive for a partition 'KNOPPIX-DATA' with the reiserfs file system. It manages to create a persistent live system automatically (after cloning)! Wowee, that was easy using knoppix and gddrescue. Downloaded and installed to a 15gb usb stick. Automatically created an 11gb data partition. Booted up to an lxde session with compiz as window manager...wobbly windows and all. Installed kupfer and plank and still there after a reboot.

#821

[SIZE=4]mkusb version 12.3.2 for version 19.10, Eoan Eanimal[/SIZE]

The PPA at Launchpad includes versions of mkusb for the new developing version 19.10, Eoan Eanimal

mkusb was tested today, 2019-05-04, with a Lubuntu daily iso file from the testing tracker, eoan-desktop-amd64.iso, and it works as it should.

[hr][/hr] If you run standard Ubuntu [persistent] live, you need an extra instruction to get the repository Universe. (Kubuntu, Lubuntu ... Xubuntu have the repository Universe activated automatically.)

Text after the # character is not used by the shell interpreter, it is a comment for the human eye.

sudo add-apt-repository universe  # this line only for standard Ubuntu
sudo add-apt-repository ppa:mkusb/ppa          # stable PPA for regular usage
# sudo add-apt-repository ppa:mkusb/unstable   # PPA for development and testing; remove the # in front of the command to use it
sudo apt-get update
sudo apt-get install mkusb

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#822

Thank you very much! :KS

#823

This tool is very nice and seems to be quite polished. But unfortunately it couldn't make my live and persistent linux mint 19.2 work with uefi and secure boot: I get the notification "[COLOR=#000000][FONT=Roboto]operating system loader signature not found"[/FONT][/COLOR]

#824

@jools77,

I *think* that Linux Mint does not provide a signed kernel. It means that it should work in UEFI mode if you turn off secure boot. Standard Ubuntu and the Ubuntu family flavours (Kubuntu, Lubuntu ... Xubuntu) do provide a signed kernel and should work also with secure boot, at least when installed. But I think there can be problems to boot some computers from USB with secure boot even with a signed kernel.

#825

Hello! Firstly, thank you for taking the time to create this tool - i've just used it to do a dual boot windows/kubuntu system and it was a nice easy tool to use.

I just wanted to make one suggestion for improvement! I have always used Unetbootin in the past, but the ppa seems to be down for 18.04 onwards, hence I was looking for another tool. Mkusb has worked wonderfully apart from one thing - persistence made the Kubuntu install extremely slow. This is something I've been doing for years with Unetbootin and never experienced this problem, and having looked around the web a bit it seems that there are some other people with the same experience.

Most people suggest "buy a really quick USB key" but the truth is I've been regularly using two old usb keys (both more than 5yrs old and with lots of R/W usage) - always the same two, and like I said with Unetbootin this never happened.

So I thought it might be helpful for the developer to check out how Unetbootin implements persistence, and work out what it does differently, it might be easy to make the same change for mkusb and the performance is 10x quicker or more. The only downside to making USBs persistent in Unetbootin, was that if you selected a large persistence file, say 4gb, on an old stick like mine, it took ages to actually make the stick. But once it was made it ran as smooth as a hard drive.

Thanks again, I hope this might be of some help!

#826

@jahja,

I see your point, but I am afraid, that there will be other disadvantages, if I would modify mkusb to use a file for persistence the same way as Unetbootin does. That would limit the size of the storage for persistence to 4 GB. Instead I suggest the following methods to make things faster:

  1. Backup all persistent data
  2. Use mkusb to overwrite the whole USB device with zeros (which can restore the write speed of an old USB pendrive to almost the original speed)
  3. Use mkusb to create a fresh persistent live system

If you still have problems, you can do one or both of the following things

  1. Use gparted to reduce the size of the partition for persistence to the same as the file for persistence that you use with Unetbootin
  2. Use gparted to create an ext2 file system in the partition for persistence. Remember to set the label to 'casper-rw'

I would be very interested in your result, how these steps can change the speed of your persistent live system.

#827

Have been doing some testing with unetbootin-windows-661 and Ubuntu 19.04 & 19.05 lately. Seems to work fine for me, have even managed to replace the Persistent file with a Persistent partition. (I understand that there have been problems with unetbootin-ubuntu with 18.04 and later, but there are now workarounds.

It seems that Persistent Ubuntu runs mostly in RAM nowadays, wondering if maybe @jahja's RAM is no longer sufficient for the latest Ubuntu. I am not finding a difference in speed between UNetbootin install and a mkusb install. Will take a closer look.

#828

[SIZE=4]Remote login via ssh into a persistent live drive[/SIZE]

There is no (publicly known) password for the default user in Ubuntu based flavours and distros. When asked for a password, for example to run sudo, you simply press the Enter key. But ssh wants a password, so it does not work to log in remotely via ssh into a persistent live drive.

I found the following workaround, create a second user with a password, and tested it with Lubuntu Eoan.

After login to the second user it is possible to switch user to the default user ('lubuntu' in Lubuntu persistent live).

There are more details at this link.

#829
#830
#831

[SIZE=5]Much easier to create persistent live drives with a partition for persistence[/SIZE]

Because the new feature alias removed bug in casper it is now much easier to create persistent live drives with a partition for persistence. It is already there in Debian 10 and in Ubuntu Eoan

  • So we will soon have it in Ubuntu 19.10 :-)
  • It will take months (maybe years) until it will appear in Ubuntu 18.04.x LTS.
  • We can expect to get it in Ubuntu 20.04 LTS.

[SIZE=4]Opportunity[/SIZE]

This will make it much easier to create persistent live drives with big storage for persistence, and we can expect that most tools will add this feature. See the following link,

[SIZE=4]Risk[/SIZE]

General tools may start prompting people into trying to create partitions for persistence with Ubuntu 18.04.x LTS. It will fail and people will get frustrated with a USB drive that does not work at all. We should be prepared, and recognize when this happens.

Rufus has released a version with this feature, and I have already seen a few cases at AskUbuntu, where this has happened.

This is a typical output from a USB pendrive that does not boot with Ubuntu 18.04.x, when Rufus failed to make it work with a partition for persistence:


(initramfs) mount: mounting /cow on /root failed: invalid argument
overlay mount failed

[hr][/hr] Edit 1: Please remember that mkusb works as usual.

Edit 2: Please read the next post, where @Akeo, the developer of Rufus, gives his version of the risk/problem.

I want to add that I have often recommended Rufus, and I hope to continue to do so. I am glad that Rufus is early to use this new feature alias squashed bug.

But I see a risk here, that people will get frustrated, so I try to let people [who help here] know and recognize what happens, when beginners (and people who do not read warnings) fail to make a working USB boot drive. Knowing the problem will make it easier to help. I think most people need 'only' a live-only USB drive, and cloning is a robust method for that purpose, 'dd-mode' in Rufus.

Please note that it is still possible to create a file in the FAT32 partition with the name 'casper-rw' and an ext file system for persistence in 18.04.x LTS. This risk/problem/discussion will probably be forgotten when Ubuntu 20.04 LTS is released in April 2020.

#832

You may want to mention that the reason why persistence doesn't work with 18.04 LTS or any pre 19.10 version, when persistence is added through a second partition on the bootable drive, has nothing to do with the utility involved and is due to a major bug in the [FONT=courier new]casper[/FONT] scripts that, unfortunately (and despite multiple reports) has been left unaddressed for years. See https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855.

Especially, if you manually create a FAT32 and an ext3/ext4 partition on a drive, then copy the content for the 18.04 ISO onto the FAT32 partition and edit [FONT=courier new]/boot/grub/grub.cfg[/FONT] to add add [FONT=courier new]persistence[/FONT] to the kernel options, you will run into the same [FONT=courier new]overlay mount failed[/FONT] issue.

I will also point out that, when creating a bootable drive with in Rufus with an Ubuntu ISO, users do receive a very prominent notification (it will always appears during the creation process) advising them that, because this is an ISOHybrid, they need to choose between writing it in ISO (default) or DD mode and also advising them that, if they encounter any issue when booting in ISO mode, they should recreate the drive in DD mode (in which case persistence will be disabled and they will be able to to boot).

Therefore, people who do pay attention to the Rufus prompts should never be left stranded...

#833

@Akeo:

From 14.04 to 19.04 persistent same disk partitions did not work, however putting casper-rw persistence partition on a second USB, or on the internal HDD worked fine.

Thank you for adding persistent partitions to Rufus, I think you are the first to add persistent partitions to a boot disk maker for Windows.

#834

uRock said: 404

It was missing the s in windows in the link. Fixed it.

#835

deadflowr said: It was missing the s in windows in the link.

Fixed it.

You're awesome! Thanks for fixing that.

#836

@Akeo,

I have often recommended Rufus, and I hope to continue to do so. I am glad that Rufus is early to use this new feature alias squashed bug. It is a great tool that works well even for beginners who run Windows and are interested in Linux.

But I see a risk here, that people will get frustrated, so I try to let people [who help here] know and recognize what happens, when beginners (and people who do not read warnings) fail to make a working USB boot drive. Knowing the problem will make it easier to help. I think most people need 'only' a live-only USB drive, and cloning is a robust method for that purpose, 'dd-mode' in Rufus.

I do not want to bash Rufus, only steer away from problems.

#837

[SIZE=4]mkusb-minp[/SIZE]

mkusb-minp is a bash shellscript that is twice the size of mkusb-min (still very small compared to mainstream mkusb). It wraps a safety belt around dd and can also create persistent live drives from iso files of Ubuntu 19.10 and Debian 10 and newer versions.


$ wc mkusb-minp
  548  1713 12103 mkusb-minp

548 lines (and 12103 characters). It should be rather easy to see what the shellscript is doing simply by reading it in a text editor.

There is [not yet] any fancy user interface, only text dialogue (for a text screen or terminal window) with high-lighting using ANSI escape sequences.

Help text:


$ ./mkusb-minp -h
               This shellsript wraps a safety belt around 'dd'               
Clone from an iso or image file to a target device (typically a USB pendrive)
Usage:
 sudo /path/mkusb-minp [-p] <source file> <target device> 
Cloning:
 sudo ./mkusb-minp file.iso /dev/sdx
 sudo ./mkusb-minp file.img /dev/sdx
Persistence: for Ubuntu 19.10+ and Debian 10+
 sudo ./mkusb-minp -p file.iso /dev/sdx
Help:
./mkusb-minp -h
Version:
./mkusb-minp -v
Available devices (tran-MODEL  device),
 ata-SanDisk_SD6SB1M256G1001_143104401008  /dev/sda 
 ata-WDC_WD4002FYYZ-01B7CB1_K3GWHAEB  /dev/sdb 
 usb-Kanguru_SS3_07073AA487E2C547-0:0  /dev/sdc 
 ata-PLDS_DVD-RW_DH16AESH_S0C19802ZVJ8EZ00N797  /dev/sr0 
$ 

See details at

help.ubuntu.com/community/mkusb/minp - small, can clone and also make persistent live drives

The method for persistence

[hr][/hr] I hope you are curious and test mkusb-minp, particularly making persistent live drives. I am very interested in feedback :-)

#838

[SIZE=4]New version: mkusb version 12.3.3[/SIZE]

[SIZE=4]New version: mkusb-minp 2.2[/SIZE]

The PPA at Launchpad includes versions of mkusb for all current versions of Ubuntu and also the new developing version 19.10, Eoan.

  • dus: starter menu: text mode read command updated
  • dus-persistent: upefi for debian buster
  • dus-wipe: partprobe added near the end

mkusb was tested today, 2019-10-11, with a Lubuntu Eoan iso file from the testing tracker, and also with Debian Buster (10), and it works as it should.

  • Version 12.3.3 is uploaded to the unstable PPA, ppa:mkusb/unstable.
  • Version 12.3.3 is uploaded to the stable PPA, ppa:mkusb/ppa.

[hr][/hr] If you run standard Ubuntu, you need an extra instruction to get the repository Universe. (Kubuntu, Lubuntu ... Xubuntu have the repository Universe activated automatically.)

Text after the # character is not used by the shell interpreter, it is a comment for the human eye.

sudo add-apt-repository universe  # this line only for standard Ubuntu
sudo add-apt-repository ppa:mkusb/ppa          # stable PPA for regular usage
# sudo add-apt-repository ppa:mkusb/unstable   # PPA for development and testing; remove the # in front of the command to use it
sudo apt-get update
sudo apt-get install mkusb mkusb-nox

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

[hr][/hr] The new mkusb-minp is described at the following Ubuntu help page,

help.ubuntu.com/community/mkusb/minp - small, can clone and also make persistent live drives from an Ubuntu Eoan (19.10) iso file

[hr][/hr] Edit: After testing mkusb 12.3.3 is uploaded to the stable PPA and available for regular usage.

#839

sudodus…

Just a humble thank you for all the time and effort you have put into this awesome app for all these years.

#840

Dito!

#841

@DuckHook and @C.S.Cameron,

Thanks for the friendly words :-)

#842

[SIZE=4]mkusb version 12.3.3 for version 20.04 LTS, Focal Fossa[/SIZE]

The PPA at Launchpad includes versions of mkusb for the new developing version 20.04 LTS, Focal Fossa

mkusb could not be tested today, 2019-10-18, with an Ubuntu daily iso file from the testing tracker, focal-desktop-amd64.iso, because there is no such file yet. So we are ready for testing, and if you have set the repositories to fossa and have an early Ubuntu fossa installed system, please try mkusb.

[hr][/hr] If you run standard Ubuntu [persistent] live, you need an extra instruction to get the repository Universe. (Kubuntu, Lubuntu ... Xubuntu have the repository Universe activated automatically.)

Text after the # character is not used by the shell interpreter, it is a comment for the human eye.

sudo add-apt-repository universe  # this line only for standard Ubuntu
sudo add-apt-repository ppa:mkusb/ppa          # stable PPA for regular usage
# sudo add-apt-repository ppa:mkusb/unstable   # PPA for development and testing; remove the # in front of the command to use it
sudo apt-get update
sudo apt-get install mkusb

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#843

[SIZE=4]mkusb works in focal fossa[/SIZE]

Today I found an Ubuntu Focal Fossa iso file in the iso-tracker, and I could use it to install mkusb from the focal PPA.

It was a bit clunky, because add-apt-repository was not present. I had to edit the sources.list file and import the relevant gpg key for ppa:mkusb manually for it to work.

This is what I did:

  • in my working computer I created a persistent live drive from the Ubuntu Focal Fossa iso file.
  • booted the Ubuntu Focal Fossa persistent live system and installed mkusb
  • used mkusb to create another persistent live system (Lubuntu 18.04.1 LTS)
  • tested that the created system (Lubuntu 18.04.1 LTS) works correctly.

See the attached screenshot.

Conclusion:

We can expect mkusb to continue to work, but wait until Focal is more complete (e.g. that add-apt-repository is available) until you test it.

#844

Buggy ext3 file system in persistent live drive made by Rufus

We are happy that @Akeo has developed Rufus to create persistent live drives using a partition for persistence. It works, and seems to work well with small partitions for persistence.

However, if you try with bigger USB pendrives, 16 GB, 32 GB etc. there will be increasing problems, at least when created in some Windows 10 computers (updated and upgraded to be up to date 2019-10-23). It is really bad with an SSD of 60 GB.

I noticed that the ext3 file system is buggy. When running the command


sudo e2fsck -f /dev/sdxn

where x is the drive letter and n is the partition number for the 'casper-rw' partition for persistence, several errors were found and they could be fixed.

The symptom in a persistent live drive is that part of the space is occupied, 'lost', and it seems that it increases dramatically with the size of the partition.

Examples (size of USB drive, the partition for persistence gets what is left, when the system is written)

[size=3]
Size  Loss
 GB   GiB

  4    0.3
 16    4.6
 60   40    # Yes, 40 GiB are lost in this case !!!
[/size]

GB decimal, GiB binary (because this is what is shown by most tools)

Details are shown in the attached screenshots. Please use the file name to identify each screenshot.

[HR][/HR] There are three alternatives to fix this problem:

  1. Ask @Akeo to fix the problem. I have started doing that.

Edit { Link to a bug report }

  1. Repair the ext3 file system with e2fsck. I have tried that and it works, but you need a working linux operating system for it. It does not work when booted into the drive itself, even when booted live-only, because a log directory seems mounted to the partition and it is busy, cannot be unmounted.
  1. Install another tool in Windows, and create a fresh file system in the partition for persistence, to format it (or should we say re-format it). I have tried with AOMEI Partition Assistent Standard Edition (freeware), and it works (better than Rufus).
#845

[SIZE=4]mkusb version 12.3.4[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.3.3

mkusb 12.3.4

  • dus: p_starter: text mode read command updated
  • dus-persistent: upefi for debian buster
  • dus-wipe: part_info: added partprobe
  • dus-persistent: added delays at 'tweak 3 grub.cfg'

[/td][/tr][/table]

These are minor tweaks or bug-fixes to make mkusb more robust.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.3.4 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus
#846

[SIZE=4]Do It Yourself method to make a USB boot drive with or without persistence[/SIZE]

The following Ubuntu help page has been debugged and updated,

help.ubuntu.com/community/Installation/iso2usb/diy

The main new feature is that there are instructions to use a partition for persistence. This makes it possible to use big USB drives, not only pendrives but also memory cards and SSDs connected via USB adapters, and take advantage of the whole drive [remaining drive space behind the live system] for persistence.

Another new feature is that there are detailed instructions for Debian 10 live alongside the improved instructions for Ubuntu.

Please notice that if you need only boot in UEFI mode, you need not use the image file 'grub-do-it-yourself.img.xz', which provides a BIOS bootloader. Then it is enough to use the method that I learned from @oldfred:

Create a partition with a FAT32 file system on the USB drive and extract the content of the iso file into that partition. If you want a [second] partition for persistence, you should make that [first] partition rather small, only big enough to extract 'everything' from the iso file plus maybe some drive space for transfer of data between Windows and Ubuntu.

#847

[SIZE=4]mkusb version 12.3.5, 12.3.6[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.3.5

mkusb 12.3.6

[/td][/tr][/table]

  • dus: p_target: warning if target size>sizwarn (128 GB)
  • dus: p_target: [COLOR="#CC0000"]red[/COLOR] warning if target size >= sizwarn (now 60 GB)

The normal usage of mkusb is to create a bootable live-only or persistent live system in a USB pendrive, which is usually small compared to drives used for installed operating systems or mass storage of data. But it is also possible for mkusb to write to a big target drive (to make it bootable, to restore it to a storage device and to wipe it).

There is a new pop up menu warning when trying to write to a drive with size >= 60 GB. This should help the end user avoid overwriting a big drive, when they intend to write to a small USB pendrive or small SSD.

There is already an old warning when the user tries to write to a drive that is identified by the system as an ATA drive or mmcblk drive: 'not a USB drive'. The new warning is similar (but with different text: the target drive size in GB). One of these warnings or both of them may pop up. See the attached screenshots.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.3.6 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe  # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb mkusb-nox                # to install
# sudo apt-get dist-upgrade                         # upgrade to current version (with all other upgrades), only for installed systems
sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus
#848

The install of unstable via PPA went without a hitch on 18.04 and 19.10. Thanks for this!

#849

@uRock,

Thanks for testing :-)

#850

Thanks Sudodus, now that I have finally got some SSDs, I am sure that I will make good use of the extra warning. It looks good, but is there a possibility to do it in red?

#851

It would be possible, but I try to keep mkusb as independent as possible of special features, so that it can work with many distros and versions, with various versions of zenity and libraries that it uses. I used colour high-lighting with red background in mkusb versions 9-11, but skipped it in mkusb version 12, dus, for this reason.

Text colour high-lighting should be common enough to be available and working in most linux systems (and is used in the welcome window of dus).


<b><span bgcolor=$logorgb>- Do USB Stuff -</span>

and


<span fgcolor='#cc0000'>The target device will be completely overwritten</span>

Please edit the file /usr/bin/dus in the function p_target at or near line number 1744 and when you get something that you think works well, please show it to me, and I can enter it into the official code.

Maybe

line number 1744 can be modified to


 tell_risk="<span fgcolor='#cc0000'>'$target' drive size = $sizgb GB. $pls_chk</span>"

Please try and maybe you can improve it for example by adding asterisks or exclamation marks.

Edit:

This warning with [COLOR="#CC0000"]red[/COLOR] text is uploaded to the PPAs now as mkusb - 12.3.6-1ubuntu2

After testing in ppa:mkusb/unstable

it is also uploaded to the stable ppa:mkusb/ppa

#852

sudodus,

This is continuing our discussion on askubuntu (I couldn't use the same username here).

@Matthew, I like your comment in the bug report about errors in the ext3 file system made by Rufus. I wish that we will be able to cooperate with Pete Batard. You mention that Rufus is user friendly, more so than mkusb. I have to agree with that. You are welcome to help improving the user interface of mkusb - You can go deeply into the code (which is simply bash shellscripts, nothing advanced, no compiling). Or you can stay at the design level, suggesting how the user interface should be (and someone else may be able to implement it, maybe I maybe some other person).

> @Matthew, I have also some other ideas, that can make things much simpler for end users, *Please let me know if you are interested and have time to cooperate.* In that case you can get a user ID at the Ubuntu Forums, and we can use the message system over there (or some other way of direct communication, maybe even email).

I can't make a long-term commitment to mkusb, because it is just one stage on my journey to getting a working computer when Windows 7 support ends. However, as I offered to do with Rufus, I would like to give something back to the project, since you have so kindly helped me (both personally and by maintaining the project for everyone).

I think the way that I can best help is with the documentation. This is actually one of the strongest points of your work, because you are very careful to document everything you do, either in this thread or on the Ubuntu Community Wiki. It could not be easier for someone to get involved on the scripting side. However, it makes sense to use my professional training in textbook design.

The 'Quick Start Guide' has many good points: the spelling and grammar are adequate, each individual page is clearly designed, and technical jargon is explained. However, I sometimes struggled to understand the relationship between the different slides/pages, as in this example:

[IMG]https://i.imgur.com/o9z8FWc.png[/IMG]

I also did not understand the relationship between mkusb, dus, and guidus until I found the Superuser howto. I think it is important to establish this at the start of the document.

I would guess that the weak points in the information structure are the natural result of a document that has been revised by someone who already knows the software well.

If you are able to place an editable version of the Quick Start Guide (ODT, ODP, PPT?) in a place where I can find it (forum attachment, Box, Dropbox?), then perhaps I could edit the document and then send it back to you.

#853

Hi linmanfu alias Matthew,

I'm glad that you want to edit the mkusb quick start manual :-)

I'm uploading it at

phillw.net/isos/linux-tools/mkusb/mkUSB-quick-start-manual-12.odp

We can decide to use some other location in the future, for example at the locations you suggested or google drive, where both of us can access the same document.

#854

[SIZE=4]mkusb version 12.3.7, 12.3.8[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.3.7

mkusb 12.3.8

[/td][/tr][/table]

  • dus-persistent: menu_entry_1: new menuentry with toram nopersistent
  • grub.cfg: new menuentry with toram nopersistent
  • modifications for nvme drives (alongside mmcblk) in dus, dus-live, dus-persistent, dus-restore

A new feature in Ubuntu 19.10 causes the creation of a partition with the label 'casper-rw' if there is unallocated drive space available. This happens not only with the boot option 'persistent' but it is the default (without any particular 'casper' boot option). A live drive will mount the 'casper-rw' parition to /var/crash which can be unmounted and /var/log which will be busy, so that it cannot be unmounted.

But there is a boot option to make the live drive truly live-only: nopersistent, and I have added a menuentry for mkusb to make it easy for you in order to

  • backup, restore or repair the partition for persistence
  • unmount all partitions on the boot drive so that it can be unplugged or used as a target for a new installation.

nvme drives are getting more popular, and it is time for mkusb to manage such drives. It will still be very uncommon with persistent live system in nvme drives, but it will probably be more common to wipe such a drive using mkusb.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb           # to install
# sudo apt-get dist-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.3.8 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb            # to install
# sudo apt-get dist-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus
#855

I have tested mkusb in a fairly new laptop with an nvme drive.

  • It is a Lenovo V130 with a Samsung drive
  • Windows was installed with the storage controller mode RST (a setting in a UEFI/BIOS menu)
  • In order for Ubuntu to see the drive I had to change to the storage controller mode AHCI
  • I backed up Windows with Clonezilla
  • I installed persistent live Lubuntu Focal (yes, into the nvme drive, so the persistent live system is really fast).

It works as it should in this drive. See the attached screenshot.

[HR][/HR] Edit: Please notice that you need mkusb version 12.3.8 in order to manage nvme drives.

#856

[SIZE=4]mkusb version 12.3.7, 12.3.8[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.3.7

mkusb 12.3.8

[b]mkusb 12.3.8-1ubuntu3

[/td][/tr][/table]

  • dus-persistent: menu_entry_1: new menuentry with toram nopersistent
  • grub.cfg: new menuentry with toram nopersistent
  • modifications for nvme drives (alongside mmcblk) in dus, dus-live, dus-persistent, dus-restore
  • mkusb-11 deprecated, replaced by a 'goodbye message' [/b]

$ mkusb-11
mkusb-11 version 11.2.3 - goodbye message

+-----------------------------------------------------------------------+
|                                                                       |
|  The real mkusb version 11 was edited last time  2018-03-10 (11.2.2)  |
|  and it was only cosmetic. The previous edit was 2017-03-28 (11.2.1)  | 
|  It has been replaced by mkusb version 12 alias dus.                  |
|                                                                       |
|  If you are still using version 11, please try version 12, which has  |
|  been developed with several new features and bugfixes.               |
|                                                                       |
|  If you really want to continue using version 11 (mkusb-11), please   |
|  let me know via **a post here in this thread.**                          |
|                                                                       |
+---------------------------------------------------------------------- +

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb           # to install
# sudo apt-get dist-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.3.8 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb            # to install
# sudo apt-get dist-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus
#857

[SIZE=4]mkusb version 12.3.9[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.3.9

  • dus: new functions 'p_langC' and 'p_langR' that set and reset the environment variables LANG and LC_ALL which are used when the local language creates problems (for example with 'lsblk').
  • mkusb-11: 'goodbye message' replaced by the real program again until the new version of dus is tested and verified to work well with languages that use characters which might create problems.

[/td][/tr][/table]

The new functions 'p_langC' and 'p_langR' are used in the following parts of dus:

  • main program
  • function p_list_drives
  • function p_source
  • function p_target

in order to use standard language, LANG=C and LC_ALL=C, to avoid problems with some characters, that appear in some languages.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt-get update
sudo apt-get install mkusb           # to install
# sudo apt-get dist-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt-get install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.3.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt-get update
sudo apt-get install mkusb            # to install
# sudo apt-get dist-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

and you get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt-get install dus
sudo apt-get install guidus
#858

This is exactly what I wanted, thanks!

#859

[SIZE=4]xorriso-dd-target - a new tool to create USB boot drives in a safe way[/SIZE]

**scdbackup** is developing a Debian tool to create USB boot drives in a safe way, 'wrap a safety belt around dd'. He hopes that this tool will replace dd, cp and cat as standard tool for many linux distros (including Ubuntu).

I have helped him with testing and tips based on my experience with mkusb and from trying to help at reported disasters that have happened to users because dd (as well as cp and cat) will do what the user tells it to do without questions, for example destroy the family pictures because of a simple mistake with a device letter.

scdbackup is developing and maintaining the xorriso tools for optical media.


**xorriso-dd-target**

is the name of this new Debian tool to create USB boot drives in a safe way.

[SIZE=3]You are welcome to test it and report your results here.[/SIZE]

Link to the tool (a shellscript written for sh)

Link to the source code of the man page

You can copy and paste the script and man page from the links via a text editor and get them into your computer. If you save the manual content with the name [FONT=Courier New]xorriso-dd-target.1[/FONT], you can display it (in the same directory) with


man ./xorriso-dd-target.1

This is a quick start manual that helps you get started with 2 test examples

Help text:


$ ./xorriso-dd-target -help
usage:  ./xorriso-dd-target [options] [device_name [device_name ...]]

Looks on GNU/Linux for USB and Memory Card devices and evaluates
whether the found devices are plausible targets for image copying.
If no device names and no -list_all are given, then a plain list of
advisable device names is printed to stdout. One per line.
Device names must not begin by '-' and must be single words. They must
not begin by '/dev/'. E.g. 'sdc' is valid, '/dev/sdc' is not valid.
If device names are given, then they get listed with advice shown.
If one of the given device names gets not advised, the exit value is 1.

The option -plug_test can determine the desired target device by
inquiring the system with unplugged device and then with plugged one.

Only if option -DO_WRITE is given and -list_all is not, and if exactly
one advisable device is listed, it really gets overwritten by the
file content of the given -image_file. In this case the exit value
is zero if writing succeeded, non-zero else.
Option -dummy prevents this kind of real action and rather shows the
unmount and write commands on stdout.

Options:
 -plug_test         Find the target device by asking the user to press
                    Enter when the desired target is _not_ plugged in,
                    to then plug it in, and to press Enter again.
                    This overrides device names and option -list_all.
                    The found device is then shown with advice, vendor,
                    and model. Option -DO_WRITE is obeyed if given.
 -list_all          Print list of all found devices with advice, vendor
                    and model. One per line. Ignore any device names.
                    Ignore -DO_WRITE.
 -list_long         With each line printed by -list_all or a submitted
                    device name, let lsblk print info which led to the
                    shown reasons.
 -with_vendor_model Print vendor and model with each submitted device
                    name.
 -max_size n[M|G|T] Set upper byte size limit for advisable devices.
                    Plain numbers get rounded down to full millions.
                    Suffix: M = million, G = billion, T = trillion.
                    Be generous to avoid problems with GB < GiB.
 -min_size n[M|G|T] Set lower byte size limit for advisable devices.
                    After processing like with -max_size, one million
                    gets added to the size limit.
 -look_for_iso      Demand presence of an ISO 9660 filesystem. If so,
                    any further filesystem type is acceptable on that
                    device. Else only ISO 9660 and VFAT are accepted.
 -with_sudo         Run '/bin/lsblk -o FSTYPE' by sudo.
                    If no filesystems are detected and the program
                    has no superuser power, the device is not advised.
                    If -DO_WRITE is given, run umount and dd by sudo.
 -image_file PATH   Set the path of the image file which shall be
                    written to a device. Its size will be set as
                    -min_size.
 -DO_WRITE          Write the given -image_file to the one advisable
                    device that is found. If more than one such device
                    is found, then they get listed but no writing
                    happens. In this case, re-run with one of the
                    advised device names to get a real write run.
 -dummy             Report the -DO_WRITE actions but do not perform
                    them.
 -dummy_force       If a single device name is given, do a run of
                    -dummy -DO_WRITE even against the advice of
                    this program. This probably shows you ways to
                    shoot your own foot.
 -help              Print this text to stdout and then end the program.
Examples:
 ./xorriso-dd-target -with_sudo -list_all
 ./xorriso-dd-target sdc
 ./xorriso-dd-target -with_sudo -image_file debian-live-10.0.0-amd64-xfce.iso -DO_WRITE -dummy
 ./xorriso-dd-target -with_sudo -image_file debian-live-10.0.0-amd64-xfce.iso -DO_WRITE -plug_test

We hope that the shellscript will soon get into a Debian repository (in Ubuntu the Universe repository, maybe into Focal Fossa).

#860

[SIZE=4]mkusb-plug uses xorriso-dd-target and mkusb-minp[/SIZE]

mkusb-plug is a wrapper script that helps the user to identify the target device by a plug-in test method.

  • The script prompts the user to the plug test method of xorriso-dd-target.
  • I tried to make it reasonably user friendly.

You can find an experimental version of mkusb-plug at

**help.ubuntu.com/community/mkusb/plug**

  1. Download the tarball [FONT=Courier New]mkusb-plug-plus-tools.tar.gz[/FONT] and extract plug-dir with its files.
  1. There is a GUI (using zenity like mkusb-dus). (For example the final checkpoint is a copy of that for mkusb-dus).
  1. There is an installer in plug-dir,
  1. There are checks for necessary programs, that you may have to install into your version or flavour of Ubuntu or Debian.
  1. How should I make mkusb-plug avallable, when ready for regular users?
  • via PPA: ppa:mkusb/ppa
  • as a tarball (like this experimental version)
  • some other way?
  1. Some bugs are found and squashed but there are probably more bugs to squash before mkusb-plug can get rid of the label 'experimental' :-P

Please have a look at mkusb-plug and tell me what you think.

#861

This is a bug or issue report for mkusb (dus version 12.3.9). On an old laptop (HP G60-125NR), the system loads OK but it has so much major flickering it's useless. Whenever I move the mouse or some other GUI event happens, the bottom half of the screen rapidly moves up and down.

I tried both linuxmint-19.2-cinnamon-64bit.iso and ubuntu-18.04.2-desktop-amd64.iso. I tried to change the driver to NVIDIA but it always went back to the default.

The same systems load OK without flickering and without needing to change the driver when using Startup Disk Creator and the same USB stick.

I can't spend too much time on this but I can run some commands using both setups.

#862

Hi tolstoy-dot-com,

Thanks for the heads up :-) I am interested in finding the bug and to squash it. Before you start running some commands I have a few questions.

  • Is there flickering when you run mkusb or when you run the system that is created by mkusb?
  • Are you making a USB boot drive from the iso files [FONT=Courier New]linuxmint-19.2-cinnamon-64bit.iso[/FONT] and [FONT=Courier New]ubuntu-18.04.2-desktop-amd64.iso[/FONT]?
  • What version (of Ubuntu or Ubuntu flavour or Linux Mint) is running in the computer, when you run mkusb and the Startup Disk Creator?
  • The Startup Disk Creator is cloning, and creates a live (live-only) USB drive. You can create either a live (live-only) or a persistent live drive with mkusb. What kind of drive did you create with mkusb?

[hr][/hr] The graphics driver is installed before the overlay for persistence is activated, so it is not possible to install a proprietary drive in such a system.

It may help with the boot option [FONT=Courier New]nomodeset[/FONT], but in order to use the full power of an nvidia graphics chip, you should have an installed system. It is possible to install Ubuntu (and Linux Mint) into a USB pendrive like you would install it into an internal drive. See this link.

#863

Sudodus-

I just tried out your script and it works perfectly. Using Kubuntu 18.04 I was required to install exact first. Perhaps a check at install for all required libraries may help newbies? It's no biggie though...

I used an old 8gb sd card through a micro sd to USB adapter attached to an USB 3 hub connected by a 10 mtr usb2 extension cable (2 x 5mtr - my HTPC is in the attic). If your script is going to work in this setup it is pretty robust!:biggrin:

I installed the fsarchiver.iso to the 8gb and then used that to back up my original ssd and then restore my / and /home partitions to my spare ssd and it is working perfectly.

Nicely done son, will be using this from now on, keep up the good work!

#864

vidtek said: Sudodus-

I just tried out your script and it works perfectly. Using Kubuntu 18.04 I was required to install exact first. Perhaps a check at install for all required libraries may help newbies? It's no biggie though...

I am glad that it works well for you.

You are right, in the installer there should be a check for necessary help packages to be installed. I'll fix that in the next version :-)

[hr][/hr] Edit: The installer is updated so that it checks for expect and zenity in the current version mkusb-plug 2.1, that is uploaded now. (There are some other bug-fixes too.)


#!/bin/bash

# Copyright (c) 2020
# Nio Wiklund alias sudodus <nio dot wiklund at gmail dot com>
# Thomas Schmitt <scdbackup@gmx.net>
# Provided under GPL version 2 or later.

# date        sign     comment
#
# 2019-12-23  sudodus  created GUI version 2; version 1 is text only)
#                      using xorriso-dd-target, mkusb-minp, zenity, expect
#                      plus standard tools in Ubuntu and Debian
# 2019-12-27  sudodus  bugfixes for Debian in
#                       ver_test_minp: sudo added
#                       main: sudo added in 'test_tool sudo mkusb-minp'
#                      get_target: new text 'Do you expect ...?'
#                      main: added check for -h and -v
#                      installer: added check for zenity and expect  

version=2.1
...

See this link: help.ubuntu.com/community/mkusb/plug

#865

Just finished testing the 181229 daily of mkusb-plug.

I like this installer, it is at least as easy as installing mkusb/gidus, except... There were problems with Samba, (there always seems to be problems with Samba). The program ran fine and made a working focal Persistent drive.

_The things I don't like Include:_

  • The Try/Install page, grub menu is better. (But it is OK for people mainly wanting an installer thumb drive).
  • Lack of grub 2. I use a mkusb foundation for most Flash drive projects. Your grub system is the main reason. It works great for standard persistent drives. It is easy to modify for Multi Booting ISO's, and for Full Installs etc.
  • There is no NTFS data partition. I think this is a necessity with large flash drives or SSDs.

Thank you for your hard work.

#866

@ C.S.Cameron,

Thanks for testing mkusb-plug and for the detailed feedback :-)

I do not intend to replace the current mkusb-dus, but mkusb-plug can be an alternative alongside the good old version.

Is there any feature of mkusb-plug, that you think could be included into mkusb-dus to make it better?

#867

[SIZE=4]mkusb-plug 2.2 [/SIZE]

I made an option to create a live (live-only) drive with a 'usbdata' partition for storage. You can select three file systems

  1. NTFS - compatible with Windows 10, not earlier versions because it is not partition #1, It you want earlier versions to manage a usbdata partition, you should use good old mkusb-dus.
  1. exFAT - compatible with Windows 10 and newer versions of MacOS (at least read only in MacOS).
  1. FAT32 - compatible with most operating systems (except earlier versions of Windows because it is not partition #1), but the file size is limited to 4 GiB as we both know.

Please try and look for bugs in mkusb-plug 2.2

See this link: help.ubuntu.com/community/mkusb/plug

#868

[SIZE=4]mkusb-xscl uses xorriso-dd-target[/SIZE]

mkusb-xscl is a wrapper script that helps the user to identify the target device with all the options and methods of xorriso-dd-target.

mkusb-xorr was renamed to mkusb-xscl, where 'xscl' is an acronym for eXtra Safe CLoner.

  • There is a main menu, where you can select the options to be used. These options are saved in a file.
  • I tried to make it reasonably user friendly.

You can find an experimental version of mkusb-xscl at

**help.ubuntu.com/community/mkusb/xscl**

  1. Download the tarball [FONT=Courier New]mkusb-xscl-plus-tools.tar.gz[/FONT] and extract xscl-dir with its files.
  1. There is a GUI (using zenity like mkusb-dus). (For example the final checkpoint is a modified copy of that for mkusb-dus).
  1. There is an installer in xscl-dir,
  1. There are checks for necessary programs, that you may have to install into your version or flavour of Ubuntu or Debian.
  1. How should I make mkusb-xscl avallable, when ready for regular users?
  • via PPA: ppa:mkusb/ppa
  • as a tarball (like this experimental version)
  • some other way?
  1. Some bugs are found and squashed but there are probably more bugs to squash before mkusb-xscl can get rid of the label 'experimental' :-P

Please have a look at mkusb-xscl and tell me what you think.

#869

I had no problem with mkusb-plug, until yesterdays version, It started warning that mkfs.exfat was not in path and exited. Returning to the last version, it started working again.

I did find mkusb-xscl too complex. A good set of instructions might help but probably would not be followed by a lot of people.

#870

C.S.Cameron said: I had no problem with mkusb-plug, until yesterdays version, It started warning that mkfs.exfat was not in path and exited.

Returning to the last version, it started working again.

I see the problem. Did you upgrade by installing mkusb-plug manually or by running the updated installer from the **new tarball**?

This new version of the installer *should* look for mkfs.exfat and some other tools, that should be available in order to run all the possible actions by mkusb-plug. And if necessary help you install them.

Please try the new version of the installer and let me know if it works (helps you make mkfs.exfat and some other tools available).

Edit 1: Or do you think that the user should not be forced to install exfat-utils and exfat-fuse (that bring mkfs.exfat and other exfat tools). That the issue would be raised only if/when trying to create an exFAT partition? I could modify mkusb-plug to work like that.

Edit 2: I decided that I *should* modify mkusb-plug to work like that: mkfs.exfat need not be available (there will only be a warning), but of course, if the user tries to create an exfat file system, mkusb-plug will fail. Anyway, *a new tarball is uploaded now.* It contains also a new version of xorriso-dd-target. Please try it :-)

I did find mkusb-xscl too complex. A good set of instructions might help but probably would not be followed by a lot of people. Yes, I understand and I must agree with you. If you find it difficult I am sure that it will be too difficult for a lot of people [to use without reading detailed instructions which is the typical way people use such tools]. I am thinking about methods to help people get things set more or less automatically rather than having such a wide set of options.

Maybe it will be difficult to make a GUI for xorriso-dd-target that is better than mkusb-plug, and at the same time, maybe it is enough with mkusb-plug. What do you think about that?

#871

I tried today's version of mkusb-plug. If it would put a shortcut on my desktop, there are times I would use it instead of guidus. (There would still be times I require mkusb's usbboot though). Wondering if there is anyway to split available space between persistence and data. I am impressed with how much you have done in a short time.

#872

C.S.Cameron said: I tried today's version of mkusb-plug.

If it would put a shortcut on my desktop, there are times I would use it instead of guidus. (There would still be times I require mkusb's usbboot though).

I am thinking of integrating mkusb-plug into the mkusb PPA and I am also thinking of making a desktop file to add to the menu and possibility to put it onto the desktop. But I will probably wait with that until the tool itself is in a stable phase (when it is reliable and needs no major improvemnets).

Wondering if there is anyway to split available space between persistence and data. I am impressed with how much you have done in a short time.

It is possible, but maybe the plug-in tool can be a front-end to dus-persistent too. That way mkusb-minp (which is the engine in mkusb-plug) can be kept simple, and the advanced partitioning stuff is made with dus-persistent, this time called from mkusb-plug (as an alternative alongside called from mkusb-dus).

#873

[SIZE=4]Revamping the old help page help.ubuntu.com/community/Installation/FromUSBStick[/SIZE]

Please have a look at the following web page,

**help.ubuntu.com/community/Installation/FromUSBStick/tmp**

'tmp' because I am in the process of revamping the old help page to make it easier to use.

Any feedback is welcome - Is the tmp page

...

  • easy or difficult to understand?
  • good or bad that there are sub-pages instead of one big page?
  • what should be added?
  • what might be modified?
  • what should be left as in the original page?
#874

Thank you ):P

#875

Attached quick review of Installation/FromUSBStick/tmp for discussion. (I hope) Some items may be unpractical.

#876

Some minor details for discussion, otherwise looks ready to post.

#877

C.S.Cameron said: Some minor details for discussion, otherwise looks ready to post.

  1. My intention was to have details like download links in the sub-page (in order to keep to main page as small and clean as possible). But you prefer to have that information in the main page. Do you think that many users will not enter into the sub-pages, so that it is important to have all really important data in the main page?
  1. The rendering of spaces between lines of bullet lists may differ between browsers. The software for the Ubuntu help pages privides this style (and I think it looks better than what happens when I try to add extra space).
#878

[SIZE=4]The help page help.ubuntu.com/community/Installation/FromUSBStick is revamped now[/SIZE]

After getting help with some details by @C.S.Cameron, the revamped help page is ready for pubiishing.

Please browse to help.ubuntu.com/community/Installation/FromUSBStick and its sub-pages (those links are in the green blocks of text).

If you find anything that needs improvements or if something should be added or removed, do not hesitate. Let me know now.

[hr][/hr] You can find the old page at help.ubuntu.com/community/Installation/FromUSBStick-old

#879

[SIZE=4]mkusb-plug can be started like any graphical program now[/SIZE]

With version 2.4.1, now upgraded to version 2.4.4, there is a desktop file 'mkusb-plug.desktop', so you can start mkusb-plug

  • like any other graphical program
  • but also from a terminal window according to the help text

 $ mkusb-plug -h
 Tool to create boot drive, typically a live USB drive
 Usage:    mkusb-plug [source file]
 Examples:
           mkusb-plug linux.iso           # make live drive
           mkusb-plug linux.img           # clone image file
           mkusb-plug ubuntu-19.10+.iso   # make persistent live
           mkusb-plug debian-10+.iso      # make persistent live
           mkusb-plug -v                  # version
           mkusb-plug -h                  # help

The terminal window will serve as console for the program.

[hr][/hr] Edit:

'Like any other graphical program' means

  • via the menu or other way to access programs graphical desktop programs (depending on the desktop environment)

. select 'Open with ...' . expand 'System Tools' and select mkusb-plug

  • via right-clicking on an iso file

The next time you can expect the desktop environment to remember your choice, so that it will be easier to select mkusb-plug.

#880

[SIZE=4]mkusb version 12.4.0, 12.4.1, 12.4.2, 12.4.3[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.4.0

  • dus: p_lisdz: quoting array variables, kudos to Jonathan Starnes, in Launichpad bug report #1731359.

mkusb 12.4.1

  • dus-persistent & dus-restore: parted set partition type FAT32 (fixes a minor (cosmetic) bug)
  • new package mkusb-plug added to the PPA

mkusb 12.4.2

  • dus: p_menudz: wider menus for zenity and dialog
  • dus: p_target: red warning about size also for dialog and text
  • dus: p_list: line 1294: redirected error output to /dev/null
  • mkusb-select: added menu entry for mkusb-plug
  • mkusb package: debian/control: moved mkusb-plug to recommends because in Xenial mkusb-plug cannot edit the partition table after cloning

mkusb 12.4.3 Newest new: In the developing Focal Fossa, to be released as 20.04 LTS, the default label of the partition for persistence is changed from [FONT=Courier New]casper-rw[/FONT] to [FONT=Courier New]writable[/FONT]. This is implemented in mkusb-plug version 2.5.5, (which is bundled with mkusb version 12.4.3 in the PPA).

[/td][/tr][/table]

Please notice that

+: mkusb-plug works and can be installed via PPA in Ubuntu 18.04.x LTS and newer versions.

+: mkusb-plug can create persistent live drives for Ubuntu 19.10 and newer versions.

0: mkusb-plug works in Ubuntu 16.04.x LTS, but cannot be installed via PPA because the available version of the partitioning tool fdisk is packaged in a deprecated way. But you can install mkusb in 16.04.x from a tarball.

-: mkusb-plug does not work in Ubuntu 15.10 and older versions. Use mkusb-dus (or mkusb-bas if it is a very old version).


$ mkusb -v                   # alias mkusb-select -v
mkusb-dus:  dus 12.4.2
mkusb-plug: mkusb-plug 2.5.0
mkusb-nox:  mkusb-nox 11.1.9
mkusb-bas:  mkusb version 7.4.3
mkusb-11:   mkusb 11.2.2

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.4.2 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt-get install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#881

[SIZE=4]Testing mkusb in Focal Fossa[/SIZE]

I have been testing various versions of mkusb in the developing Ubuntu version Focal Fossa, and can summarize the current status.

  • mkusb works in Focal Fossa - can create working boot drives.
  • mkusb can create working boot drives from Focal Fossa iso files.

[hr][/hr] Issues, that I think is related to the new version of grub, 2.04.

  • It has been noticed earlier, that there are problems with 'grub-n-iso' alias iso-boot, to boot via grub 2.04 into an iso file.
  • mkusb-dus has a problem with persistent live drives in UEFI mode. They boot, but directly into a persistent live system. I have not found a way for it to stay at the menu to let the user select according to the menuentries. This happens in one of my computers, a Toshiba laptop bought 2013. But the same persistent live drives work correctly in UEFI mode with two other (and newer) laptop computers, a Dell and a Lenovo.

There is a workaround for these problems: select usb-pack-efi in the settings menu. Then old grub files are used (version 2.02) and things work as they should.

This does not affect [persistent live drives made by] mkusb-plug. It means that we should be able to find what makes the difference and fix the problem.

#882

[SIZE=4]Rufus 3.9 can make good persistent live drives of Ubuntu 19.10 and newer versions[/SIZE]

**Rufus** is a well-known tool that can use this new feature in Ubuntu 19.10. Be sure to use Rufus 3.9 or a newer version:

  • works well to create live-only drives with all current Ubuntu versions,
  • can create persistent live drives of Ubuntu 19.10 and future versions. Please upgrade to version 3.9 (or newer), which creates a good ext3 file system and can make good persistent live drives. (Rufus 3.8 had an experimental feature for persistence and created a buggy ext3 file system.)
  • Please read the changelog at the web site, and the warnings (pop-up windows), they can help you avoid serious mistakes.

Edit: Rufus 3.9 has arrived :-)

#883

[SIZE=4]mkusb-plug version 2.5.5[/SIZE]

In the developing Focal Fossa, to be released as 20.04 LTS, the default label of the partition for persistence is changed from [FONT=Courier New]casper-rw[/FONT] to [FONT=Courier New]writable[/FONT]. This is implemented in mkusb-plug version 2.5.5, (which is bundled with mkusb version 12.4.3 in the PPA).

#884

I think that I had problems using "writable" and "home-rw" partitions on the same mkusb Focal drive, "casper-rw" still worked with "home-rw" partitions.

Edit I made another 20.04 Persistent drive using mkusb 12.4.3 and defaults. I relabeled the "casper-rw" folder to "writable". I reformatted the usbdata partition as ext4 an labeled it home-rw. Everything seems to work same as with casper-rw + home-rw partitions.

I like how you have mkusb-plug working, much better than running scripts.

#885

C.S.Cameron said: I think that I had problems using "writable" and "home-rw" partitions on the same mkusb Focal drive, "casper-rw" still worked with "home-rw" partitions.

Edit I made another 20.04 Persistent drive using mkusb 12.4.3 and defaults. I relabeled the "casper-rw" folder to "writable". I reformatted the usbdata partition as ext4 an labeled it home-rw. Everything seems to work same as with casper-rw + home-rw partitions.

Thanks for testing and verifying that "writable" works with "home-rw" :-)

As you notice I have not yet implemented checking for 20.04 in mkusb-dus.

I implemented checking for 20.04 to use the label 'writable' in mkusb-plug in order to be prepared to offer an early working solution, if the casper bug #1863672 won't be fixed. We suspect that there is a *race condition* in some computers, and such bugs are difficult to fix. See comment #25 and the following comments of that bug report.

If necessary (in April), I intend to implement checking for 20.04 in mkusb-dus and make it create the label 'writable' too.

I like how you have mkusb-plug working, much better than running scripts.

Please describe how you use mkusb-plug (how it is working better for you than mkusb-dus, if that is what you mean).

#886

I just meant that picking the mkusb-plug item off the mkusb menu is easier than running the mkusb-plug scripts. Nothing is better for making a Persistent flashdrive than mkusb-dus.

#887

[SIZE=4]mkusb version 12.4.4, 12.4.4-1ubuntu2,3,4,5 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.4.4

  • dus-persistent: grub-n-iso: label for persistence in focal fossa 'writable' (but still 'casper-rw' in older versions)

mkusb 12.4.4-1ubuntu2

mkusb 12.4.4-1ubuntu3 - mkusb-tow: main: fixed buggy command for targsiz mkusb - 12.4.4-1ubuntu4 - mkusb-tow: wf_cleanup: made to work correctly in text mode (bugfix) mkusb - 12.4.4-1ubuntu5 - mkusb-plug: mkusb-sedd and mkusb-tow: several minor bugfixes after testing in xubuntu focal in order to make things work in systems like xubuntu focal, that automatically mounts partitions that are created and after partprobe. [/td][/tr][/table]

  • mkusb-plug 2.6.0: get_action: added action to make Windows installer
  • mkusb-tow 'TO Windows': new shellscript that does the work for mkusb-plug (to make Windows installer)

mkusb version 12 alias dus calls dus-persistent and its new version checks for the version of Ubuntu in the iso file and selects file name or partition label 'writable' for focal fossa (20.04 LTS) and 'casper-rw' for the previous versions.

mkusb-plug calls mkusb-tow 'TO Windows', which is developed from iso2usb/diy/windows-installer-for-big-files, mkusb-tow can manage current Windows 10 iso files with a file 'install.wim', that exceeds 4 GiB.

mkusb-tow uses zenity when available, but it can also work as a *stand-alone tool in text mode* (but mkusb-plug needs graphics mode and zenity).

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.4.4 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#888

Just to clear my mind, I understand mkusb-plug is now part of guidus - install - Live-only. I am a little confused as I do not see the name mkusb-plug anywhere.

#889

Sorry for the confusion:

mkusb-plug is a program package, that can be installed via the mkusb PPA (ppa:mkusb/ppa and ppa:mkusb/unstable). It is [stlll?] loosely tied to the main mkusb package.

guidus is another program package, that can be installed via the mkusb PPA (ppa:mkusb/ppa and ppa:mkusb/unstable). It is closer tied to the main mkusb package.

So in order to get the main mkusb system and add mkusb-plug, you install both of them


sudo apt update
sudo apt install mkusb mkusb-plug
#890

Good yes, I've done that, but how do I start mkusb-plug? Is there a icon that I can select? I am used to running the mkusb-plug script, I missed the part about running the latest version.

#891
  1. I am testing right now, and I have found a silly but bad bug in mkusb-tow, that is used by mkusb-plug to make a Windows installer. I am testing now after fixing that bug, and later today I intend to upload a new version.
  1. You can start mkusb-plug
  • Directly from command line: mkusb-plug
  • From the script mkusb (in command line)
  • From the start menu or if gnome, the tool that shows the GUI applications (I don't know the name of that tool)
  • In a file browser by right-clicking on an iso file and selecting mkusb-plug

Edit: mkusb 12.4.4-1ubuntu4 with a bugfix is uploaded to ppa:mkusb/unstable now. An additional bugfix made mkusb-tow work also in text mode (as a stand-alone tool) while mkusb-plug needs graphics and zenity.

#892

I found my mkusb-plug icon, thank you. 2.6.0 works great but I get: Oops Something has gone wrong log out, a few times, but it runs okay after. When shutting down I get ... Access beyond end of device, scrolling for five to ten minutes. When quitting mkusb12.4.4 it now has message: Please remove the installation medium then press enter. I do not recall this from some previous versions.

#893

@C.S.Cameron,

I do not recognize the warnings and error messages that you get. Please describe in detail how you use mkusb 12.4.4 (I guess you mean mkusb-dus), and how you use mkusb-plug.

  • Which scenario:

. computer: brand name and model, boot mode, amount of RAM, graphics chip/card . operating system: version, live or installed . source iso files: full names (*buntu.iso, windows.iso) . target device: USB drive or memory card or SSD (brand name and model)

  • When do you get these warnings and error messages? Please describe as exactly as possible what you did and when it happened.

*I will try to test with as similar scenario as possible:* similar computer, same operating system and same iso files.

Or are you testing in a virtual machine?

Edit: 'Please remove the installation medium then press enter.' is a typical message when shutting down a live drive (or persistent live drive). I do not understand how it can appear, when quitting mkusb.

#894

sudodus said:

. computer: brand name and model, boot mode, amount of RAM, graphics chip/card . operating system: version, live or installed . source iso files: full names (*buntu.iso, windows.iso) . target device: USB drive or memory card or SSD (brand name and model)

Computer 1: HP, Elitebook, 8560W, i7, BIOS, 24 GB RAM, Nvidia Quadro 2000, Windows 10 installed,

Computer 2: Acer 8572, i5, BIOS, 8GB RAM, Ubuntu 18.04 upgraded from 16.06 (Unity) installed,

Focal-desktop-amd64-2020-02-23, Tested "Persistent" and "usbdata" installs, 4GB Kingston Data Traveler USB2.

After starting I get: "Oh no! Something has gone wrong... log out", with both 2.6.0 mkusb-plug "usbdata" and "persistent" installs. First few runs only.

When shutting down I get ... Access beyond end of device, that scrolls for five to ten minutes. with persistent installs but not usbdata installs.

When quitting Guidus12.4.4 Persistent, it now has message: "Please remove the installation medium then press enter" for both for both persistent and usbdata installs, I think this was happening with previous version also.

All above items happen with both the HP and Acer.

#895
  • Thanks for those details. My son has a computer that is very similar to your Elitebook. I have no own experience of Acer computers, but since both computers are affected, I will test with my son's Elitebook.

[hr][/hr]

Some additional questions:

. From an 'installed' system in USB or from a persistent live system or from a live-only system? . Did you run mkusb-plug in Ubuntu Focal?

  • How did you run mkusb-plug in the Elitebook?
  • Did you run mkusb-plug in Ubuntu 18.04 upgraded from 16.04.6 in the Acer? This could cause a problem because I know that mkusb-plug has a problem with 16.04.x LTS: It does not find a suitable version of fdisk when installing from the PPA. But I have tested that it works when installed from the tarball (in 16.04.6 LTS).
  • Which locale (language) are you using? I have tested with 'English US' and 'Swedish', but I have not tested with for example 'English UK'.
  • Did you [try to] create a live and persistent live drive with Ubuntu Focal?
#896
  • Ran mkusb-plug in the Elitebook from Full install of 18.04.3 in 32GB DataTraveler3.
  • Have not tried running mkusb-plug in Ubuntu Focal yet.
  • I ran mkusb-plug in Ubuntu 18.04 upgraded from 16.04.6 in the Acer.
  • I have tested with 'English US' only.

-I made a live and persistent live drive of Ubuntu Focal using both guidus and mkusb-plug. Only the persistent mkusb-plug says ... Access beyond end of device. I will try installing to a different USB today.

#897

Thanks @C.S.Cameron,

These details should be enough for me to reproduce the bugs that you see.

I can start testing in my own computers now, but it may take some time until I can try with my son's Elitebook.

#898

C.S.Cameron said: Computer 1: HP, Elitebook, 8560W, i7, BIOS, 24 GB RAM, Nvidia Quadro 2000, Windows 10 installed,

Computer 2: Acer 8572, i5, BIOS, 8GB RAM, Ubuntu 18.04 upgraded from 16.06 (Unity) installed,

Focal-desktop-amd64-2020-02-23, Tested "Persistent" and "usbdata" installs, 4GB Kingston Data Traveler USB2.

After starting I get: "Oh no! Something has gone wrong... log out", with both 2.6.0 mkusb-plug "usbdata" and "persistent" installs. First few runs only.

When shutting down I get ... Access beyond end of device, that scrolls for five to ten minutes. with persistent installs but not usbdata installs.

When quitting Guidus12.4.4 Persistent, it now has message: "Please remove the installation medium then press enter" for both for both persistent and usbdata installs, I think this was happening with previous version also.

All above items happen with both the HP and Acer.

C.S.Cameron said:

  • Ran mkusb-plug in the Elitebook from Full install of 18.04.3 in 32GB DataTraveler3.
  • Have not tried running mkusb-plug in Ubuntu Focal yet.
  • I ran mkusb-plug in Ubuntu 18.04 upgraded from 16.04.6 in the Acer.
  • I have tested with 'English US' only.

-I made a live and persistent live drive of Ubuntu Focal using both guidus and mkusb-plug. Only the persistent mkusb-plug says ... Access beyond end of device. I will try installing to a different USB today.

[SIZE=4]A race condition?[/SIZE]

I tested with a system created for this purpose in my Toshiba computer with a generation 3 Intel i5 CPU and 4 GB RAM booted in BIOS mode. This is different from your Acer, but maybe good enough for a comparison.

  • Ubuntu desktop 16.04.6 LTS and release-upgraded to 18.04 LTS and made up to date (with the 4.15.0-91 kernel series.
  • Set up ppa:mkusb/unstable and installed mkusb mkusb-plug usb-pack-efi
  • Zsynced Ubuntu Focal iso file dated 2020-03-25 'focal-desktop-amd64.iso'
$ md5sum focal-desktop-amd64.iso
99a91ca69ee9af5d6ff427d56cabcf8a  focal-desktop-amd64.iso
  • Used the USB 2 drive Kingston Datatraveler_G3 (an old and slow USB 2 drive with 4 GB, as similar as possible to what you used in your test).
  1. I wiped the whole Kingston USB device to make the conditions as good as possible.
  1. I used mkusb-plug making a live-only system with an NTFS partition:

Everything worked as expected (as I wanted it to work) both when running mkusb-plug and when booting into the live-only system and running it.

  1. mkusb-plug making a persistent live system:

Creating the system had this problem:

partprobe could not refresh the partition table after creating the partition for persistence. There was an output from function 'prober' in 'mkusb-sedd':


function prober {

pcnt=0
partnr=/dev/$(lsblk -lno name "${target}" | sort | tail -n1)
while [ "$partnr" == "$partn0" ]
do
 if [ $pcnt -gt 10 ]
 then
  echo -e "$redback prober: cannot identify new partition made by fdisk $resetvid"
  echo -e "$redback This can sometimes be fixed via two steps $resetvid"
  echo -e "$redback 1. wipe the first mibibyte with mkusb-dus $resetvid"
  echo -e "$redback 2. unplug and replug the target drive.    $resetvid"
  echo -e "$redback Sometimes, if the drive is getting slow,  $resetvid"
  echo -e "$redback you need to wipe the whole target drive,  $resetvid"
  echo -e "$redback or reboot the computer to make this work. $resetvid"
  exit
 elif  [ $pcnt -gt 8 ]
 then
  echo -en "$redback Please unplug and replug the target drive, $resetvid
$trgtxt
$redback and then press the Enter key to continue $resetvid"
  read
  sleep 4
  umount "${target}*" 2> /dev/null
 fi
 partprobe 2> /dev/null
 delay=$(( 4 + pcnt ))
 sleep "$delay"
 pcnt=$((pcnt + 1))
 partnr=/dev/$(lsblk -lno name "${target}" | sort | tail -n1)
 echo "prober: $partnr for persistence"
done
}

I followied the advice from 'prober': Unplugging and replugging did not help, but wiping the first mibibyte and rebooting helped. After that mkusb-plug worked as expected. I have seen this problem before (that is why I created the function 'prober'). There are less problems with fresh and responsive drives (so I recommend a fast USB 3 drive for persistence and/or other read-write partitions, but all drives can get tired, and then wiping the whole device will often help).

The persistent live system had this problem:

It seemed to work correctly when booted, but at shutdown there was the following complaint:

EXT4-fs error (device sdb3): ext4_free_branches:1019: inode £32962: block 133124: comm systemd-journal: Read failure

This was preceded by several buffer I/O errors on dev sdb device sdb3.

The error outputs were preceded by the output text "Please remove the installation medium, then press ENTER:"

I pressed the Enter key and rebooted into the persistent live drive.

The persistent live system could reboot and what I had saved was there (the bash history and a created text file).

[B]My experience is that mkusb-plug and persistent live systems are reliable with a faster and more responsive USB drive than this old USB 2 drive, but also an originally fast USB 3 pendrive (for example Sandisk Extreme) may need wiping (wipe the whole device with mkusb-dus). [/B] I repeated shutdown and had the error output again. But when tested in my main computer the file system seemed good,


$ LANG=C sudo e2fsck -f /dev/sdc3
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
writable: 1370/73872 files (6.0% non-contiguous), 138723/294912 blocks

I will test with the same Ubuntu system and some other USB drives and update this post ...

Edit 1:

Test with a Kanguru SS3 14,8GiB (16GB) USB 3 drive creating the drive was successful (without wiping the drive before).

But running the persistent live system has problems at shutdown. After the system has written "Please remove the installation medium, then press ENTER:" there is some maybe(?) harmless output: 'I/O error', but after a few more seconds there will be a lot of output about trying where it should not try,


Access beyond end of device
Access beyond end of device
...'

and there are errors in the persistent file system,


$ sudo e2fsck -f /dev/sdc3
e2fsck 1.44.1 (24-Mar-2018)
Superblockets senaste monteringstid ligger i framtiden.
	(med mindre än en dag, förmodligen för att hårdvaruklockan går fel)
Superblockets skrevs senast i framtiden.
	(med mindre än en dag, förmodligen för att hårdvaruklockan går fel)
Pass 1: Kontrollerar inoder, block och storlekar
Pass 2: Kontrollerar katalogstruktur
Pass 3: Kontrollerar katalogförbindelser
Pass 4: Kontrollerar referensräknare
Pass 5: Kontrollerar gruppsammanfattningsinformation
Antal fria block är fel (3079575, räknade=2995601).
Fixa<j>? ja
Antal fria inoder är fel (796853, räknade=796697).
Fixa<j>? ja

writable: ***** FILSYSTEMET MODIFIERADES *****
writable: 1415/798112 filer (5.6% ej sammanhängande), 191599/3187200 block

But the persistent live system works as expected. The history and a saved file is still there.

I have not seen this before, and it seems to be an error that is caused by a new bug maybe in the iso file, maybe in mkusb-plug. I will continue testing ...

Edit 2:

Test with a Sandisk Extreme 14,9GiB (16GB) USB 3 drive creating the drive was successful (without wiping the drive before).

The result is the same with the Sandisk USB 3 drive as with the Kangaroo USB 3 drive (except that the numbers of free blocks are different, which is easy to understand because the exact sizes are different and other conditions may differ too).


$ sudo e2fsck -f /dev/sdc3
[sudo] lösenord för olle: 
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Kontrollerar inoder, block och storlekar
Pass 2: Kontrollerar katalogstruktur
Pass 3: Kontrollerar katalogförbindelser
Pass 4: Kontrollerar referensräknare
Pass 5: Kontrollerar gruppsammanfattningsinformation
Antal fria block är fel (3036205, räknade=3033889).
Fixa<j>? ja
Antal fria inoder är fel (806528, räknade=806514).
Fixa<j>? ja

writable: ***** FILSYSTEMET MODIFIERADES *****
writable: 1326/807840 filer (6.0% ej sammanhängande), 192245/3226134 block

I have the following focal iso files, and can try to find out if there is a difference between the oldest and newest versions, and in that case where the problem appeared. I would guess that the flavour makes no difference, but I can check for that too.


$ ls -ltr ../*/focal-desktop-amd64*.iso|cut -d ' ' -f 6-
feb  6 07:01 ../ubuntu/focal-desktop-amd64-2020-02-06.iso
feb  7 07:32 ../xubuntu/focal-desktop-amd64-2020-02-07.iso
feb 12 16:00 ../lubuntu/focal-desktop-amd64-2020-02-12.iso
mar 12 04:36 ../kubuntu/focal-desktop-amd64.iso
mar 25 01:29 ../xubuntu/focal-desktop-amd64.iso
mar 25 07:27 ../ubuntu/focal-desktop-amd64.iso
mar 25 17:08 ../lubuntu/focal-desktop-amd64.iso

Edit 3 and 4:

In order to do things faster I tested in a Kingston SV300S37A60G SSD with 60 GB via a USB to SATA adapter:

  • Ubuntu Focal dated Februay 6 (before switching to 'writable', so uses 'casper-rw')
  • Kubuntu Focal dated March 12 (after switching to 'writable')

work as expected (the bug described above does not affect these versions. Unfortunately I have saved no iso files between March 12 and March 25 (because I did not expect this bug to appear).

This was promising. Then I tested also Lubuntu Focal dated March 25 (the same date as that of Ubuntu that failed. It worked in the SSD, but when tested in a 16 GB pendrive (the Kanguru drive described earlier) it failed. Is this a race condition like the problem that 'casper-rw' (now a second choice after 'writable') works only in some computers? Also the Kubuntu persistent live system is affected by this bug, when installed in the Kanguru pendrive.

I tested the persistent live drives in two computers, a Dell Latitude E7240 and a Lenovo V130-14IKB both with Intel i5 processors and 8 GiB RAM.

Edit 5:

I continued testing on March 27, this time with a persistent live drive made from Ubuntu 20.04 LTS amd64 2020-02-06-08 in a Sandisk Extreme USB 3 16 GB pendrive, that was wiped (totally overwritten with zeros to be as responsive as possible.

I created the persistent live drive in my main computer with Lubuntu 18.04.x, originally installed as 18.04.1 LTS and kept with the 4.15 kernel series. I used mkusb-plug.

Such a persistent live drive has worked before, and the casper package is the old one inherited from Eoan using casper-rw. So I had to re-label the partition for persistence.

I booted into the persistent live system in the Lenovo V130 (which I used also yesterday). There was persistence as expected.

Normally I have pressed the Enter key, when "Please remove the installation medium, then press ENTER:" was written to the terminal window, and things were looking good. With the experiences from yesterday I waited a while, and yes, the spamming with


Access beyond end of device
Access beyond end of device
...'

started also in this case.

The computer was shut off directly after pressing the enter key. After that I moved the pendrive to the main computer and checked the file system of the partition for persistence. I repeated the procedure above adding some data to persist, and the file system was clean.


$ sudo e2fsck -f /dev/sdc3
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Kontrollerar inoder, block och storlekar
Pass 2: Kontrollerar katalogstruktur
Pass 3: Kontrollerar katalogförbindelser
Pass 4: Kontrollerar referensräknare
Pass 5: Kontrollerar gruppsammanfattningsinformation
casper-rw: 1626/811008 filer (7.0% ej sammanhängande), 177838/3242006 block

So my conclusion is that this 'access beyond end of device' is a bug, but maybe a bug we can live with because it appears only after the system is ready for shutdown/reboot. In some cases the number of free blocks and free inodes are correct, in other cases they are not correct, but persistence seems to work and the mismatches can be corrected without damaging the stored data.

Edit 6:

The beta versions of the Focal iso files are still suffering from this bug, but I have a feeling that they behave slightly better than the iso files made one or two weeks earlier.

#899

I continued with tests of persistent live drives made with mkusb-dus

  • USB pendrive: Sandisk Extreme 16 GB
  • The persistent live system was created in my main computer with Lubuntu 18.04.x LTS
  • The persistent live system was tested in the Lenovo V130 (which I used also yesterday).
  • focal-desktop-amd64-2020-02-06.iso

The action looked good at first but behind the Plymouth interface the same thing is happening. You see a gimpse of it after pressing the Enter key after "Please remove the installation medium, then press ENTER:" was written to the terminal window.

Turning off quiet splash in the grub menu makes messages at shutdown look the same as for persistent live systems made with mkusb-plug.

  • focal-desktop-amd64-2020-03-25.iso

The action at shutdown does not happen behind the Plymouth interface. Instead there is only a cursor at the top left corner. Actually the system is waiting for you to press the Enter key (but it does not tell you so). After pressing the Enter key you get all those silenced messages ( the same as for persistent live systems made with mkusb-plug). Maybe this indicates another (minor?) bug or system change that makes it hard for mkusb (not only the 'access beyond end of device' bug).

In both cases persistence works, and (at least in the test of this post) the file system of the partition for persistence was healthy.

This confirms the conclusion at the end of the previous post: This is a bug, but it does not affect persistence. However it is ugly and makes it more difficult to use a persistent live drive.

[hr][/hr] Edit: If the iso file of the released Ubuntu 20.04 LTS will behave in the same way, I will try hard to work around these bugs, but right now I don't know how to do it. At least I should remove quiet splash from grub.cfg of persistent live drives made with mkusb-dus so that the users can see "Please remove the installation medium, then press ENTER:".

#900

sudodus said: ... but it may take some time until I can try with my son's Elitebook.

A persistent live drive made with mkusb-dus from the current (2020-03-27) daily Lubuntu Focal iso file works in an HP Elitebook 8560p booting in BIOS mode with an Intel generation 2 i5 CPU, when using an MSDOS partition table.

As usual a pendrive made with mkusb-dus and GPT did not boot.

I tried also with a persistent live drive made with mkusb-plug from the current (2020-03-28) Ubuntu daily Focal iso file. It booted and worked like in the more modern computer described in a previous post, but it booted very slowly. This old computer works significantly faster with Lubuntu (compared to Ubuntu) Focal.

The same 'access beyond end of device' bug affects the persistent live drives also in this computer.

#901

Hey Guys,

I would like to create a multi-boot usb that I can put just the iso images of different older operating systems (such as ms-dos 6.22, windows 3.1, up to windows xp) and also ubuntu as this will be for emergency installs and to run some of my older dos/windows programs I have on cd-rom. Is there such a tool or can I do this with grub? I have just started to learn a bit about the grub config in linux so bare with me, I am totally lost with working that way. Any help would be greatly appreciated. If there is a tool that could do such a thing, that would make my day, and boy could I use that!

Thank you in advance! Brian

#902

@jesterb,

I suggest that you try multiboot-usb by Sundar.

If you need more details, I refer to C.S.Cameron, who is active at these Ubuntu Forums and knows better than I how to create *multiboot* USB drives. He has written several posts here and at AskUbuntu describing how to create what you want. So let us wait for advice from him.

#903

I think Windows install tool (https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool) only works with one Windows ISO at a time as does Rufus (https://rufus.ie/)

YUMI (https://www.pendrivelinux.com/yumi-multiboot-usb-creator/) and MultiBootUSB (http://multibootusb.org/) don't boot Windows ISO's but are great with Linux ISO's

I have heard positive things about, but not tried WinSetupFromUSB (https://www.winsetupfromusb.com/downloads/) and Easy2Boot (https://www.easy2boot.com/) Both say they will multiboot Windows and Linux ISO's.

I would not be surprised if there was an easy way to get mkusb to multiboot Windows ISO's.

#904

C.S.Cameron said: ...

I would not be surprised if there was an easy way to get mkusb to multiboot Windows ISO's.

Whoever can develop mkusb for this purpose is welcome, either to include it in mkusb or to fork it into a new tool :-)

[hr][/hr] I store iso files in my main computer and use USB pendrives as temporary devices: So whenever I need a USB boot drive I create it from the relevant iso file (usually with mkusb-dus or mkusb-plug).

For this reason I have focused on single boot systems.

#905

sudodus said: @jesterb,

I suggest that you try multiboot-usb by Sundar.

If you need more details, I refer to C.S.Cameron, who is active at these Ubuntu Forums and knows better than I how to create *multiboot* USB drives. He has written several posts here and at AskUbuntu describing how to create what you want. So let us wait for advice from him.

Thanks sudodus,

I have tried downloading multiboot-usb, and my usb drive is not detected in that program, but it is in Ubuntu linux 18.04. I have formatted to ext4. Not sure if it needs to be fat32 or ntfs. As a side note: Although there were no files on the usb drive, I just did a format using linux disks application, I did not choose to erase. Could that be why it is not detected in the multiboot-usb program? I am testing in a virtualbox vm at the moment, I don't want to do a refresh yet, but it looks like I am going to do it now.

#906

jesterb said: Thanks sudodus,

I have tried downloading multiboot-usb, and my usb drive is not detected in that program, but it is in Ubuntu linux 18.04. I have formatted to ext4. Not sure if it needs to be fat32 or ntfs.

I don't know which file systems that work with multiboot-usb. *Please try* with another file system. Unfortunately there are Windows iso files that are too big for FAT32, > 4 GiB, but maybe it works with NTFS.

As a side note: Although there were no files on the usb drive, I just did a format using linux disks application, I did not choose to erase. Could that be why it is not detected in the multiboot-usb program?

It *should* be OK to just format using Disks. You should not need to erase. But if still problems, you can erase only the first mibibyte which is very fast. You can do that with mkusb. And then there should be no traces of previous partition tables or file systems that might confuse the partitioning tool (Disks) or multiboot-usb.

[hr][/hr] Please have a look at the tips by C.S.Cameron at this link and let us know what works best for you :-P

#907

I refer to the testing described in post #896.

The beta versions of the Focal iso files are still suffering from the bug manifested by the following error messages


buffer I/O errors
Access beyond end of device

However the persistent USB boot drives made with mkusb from the beta iso files behave slightly better than from iso files made one or two weeks earlier. So I am not modifying mkusb for this purpose. I will watch the progress until the final release of 20.04 LTS, and if necessary modify mkusb (mkusb-dus and mkusb-plug).

#908

@jesterb MultiBootUSB does not do Windows. I have had best luck with this tool using USB drives formatted FAT32. MBUSB has a 4GB limit for persistence for each 'Buntu OS. A MBUSB drive boots on both BIOS and UEFI systems.

YUMI BIOS is similar but has unlimited persistence for each 'Buntu OS. YUMI UEFI is limited to 4GB persistence per OS.

I prefer using mkusb to multiboot ISO files: https://askubuntu.com/questions/962536/partitioning-a-usb-and-making-separate-bootable-drives/962676#962676 But have not had luck using it to boot windows ISO's except by installing VBox on a mkusb persistent drive.

#909

Another mkusb Hack How to Copy Ubuntu Install from Internal Drive to Bootable USB https://askubuntu.com/questions/1224659/how-to-copy-ubuntu-install-from-internal-drive-to-bootable-usb

#910

+1 :-)

#911

I have used mkusb quite a bit over the years, no problems. Today I tried to use the usb from a mkusb done about 2 weeks ago, to reinstall Kubuntu 19.10 on a HP laptop . Booted from the usb okay and got a splash screen but no 'Install Kubuntu ' logo. Waited 10 or 15 minutes, still nothing. Thinking that the usb may be damaged, I did the mkusb again on a 19.10 box (Dell laptop) and used the latest 19.10 ISO. All went okay, then used that usb on the HP laptop. It has been at least 30 minutes now, the splash screen is there but no icon to install Kubuntu. Checking the usb, no activity there either.

Can I do the boot from a usb and no splash screen so I can see what is going on ? This HP laptop is quite old and has a broken screen but have a monitor hooked up. Also, I have used the usb boot sequence from a mkusb on that laptop a number of times and no problems.

So the splash scrren is there, mouse pointer active and I can move it around. No left or right click does anything. No icon with "install Kubuntu". I select option "e" when doing the mkusb.

#912

@oygle,

I am ready to help you debug this problem by testing here (but of course my computers are different from yours).

  1. Did you remember to check with md5sum that the iso file is good?
  1. Did you create a live-only or a persistent live drive?
  1. It really *should work* when cloned because the cloning process is very robust and should not differ between tools. So it is well debugged with the Kubuntu 19.10 iso file.

Edit: Some HP computers do not want to boot via grub from USB when there is a GUID partition table (GPT). For such computers you should select MSDOS partition table in the 'Settings' menu, when you make a persistent live drive.

#913

sudodus said: I am ready to help you debug this problem by testing here (but of course my computers are different from yours).

Thanks @sudodus - I have done more research/reading and some articles suggested that if part of the HDD was corrupt there can be problems with an install. I did even use 'Startup Disk Creator' to make the usb, but that did the same thing. So, 2 different utilities/tools and the same error/problem. What baffles me though is that I have used mkusb in the past to do a fresh install on the HP laptop.

sudodus said:

  1. Did you remember to check with md5sum that the iso file is good?

I knew that the ISO was okay as I only checked it about 2 weeks ago. However , just checked again with md5sum and it is okay.

sudodus said:

  1. Did you create a live-only or a persistent live drive?

I tried with both, but same problem.

sudodus said:

  1. It really *should work* when cloned because the cloning process is very robust and should not differ between tools. So it is well debugged with the Kubuntu 19.10 iso file.

Edit: Some HP computers do not want to boot via grub from USB when there is a GUID partition table (GPT). For such computers you should select MSDOS partition table in the 'Settings' menu, when you make a persistent live drive.

I can wipe the HDD completely if that would help. At present it has 19.10 on it but the desktop/plasma/menus is a total mess and I can't even switch between tasks. That is why I thought a fresh install may be warranted. But if I did wipe it clean, I would also like to check for any bad clusters, and mark those areas as 'unusable' or similar. Just to rule out the chance of this being a case of the install doing some sort of 'hang' or whatever when trying to write into bad blocks, etc. Thanks for your help.

#914

Cloning with mkusb and the Ubuntu Startup Disk Creator should give the same results. It there are problems with that process, there is some other problem (with the running operating system or the hardware (internal or external). So I think you are on the right track. It is a good idea to check the internal drive's S.M.A.R.T. status and after that create a partition with ext4 and after that run


sudo e2fsck -cf /dev/sdxn

where x is the device letter and n is the partition number where you have the ext4 file system.

I suggest that you test the RAM too. You can use memtest. Run it overnight - there should be no error at all during that time.

#915

@sudodus thanks for your help.

sudodus said: Cloning with mkusb and the Ubuntu Startup Disk Creator should give the same results. It there are problems with that process, there is some other problem (with the running operating system or the hardware (internal or external). So I think you are on the right track. It is a good idea to check the internal drive's S.M.A.R.T. status and after that create a partition with ext4 and after that run

I couldn't even create a partition. There have been far too many weird things going on with that laptop. It won't even let me drop down to Konsole, plus there are processes still there from before I last shutdown ? Can't navigate on the desktop, or swap between tasks. So at present running a secure erase on the hard drive, it will take 2 hours. I did have DBAN on a usb, booted to usb but the laptop went and booted to the HDD. Virus in the MBR ?? Myth Busters would say it is plausible...lol

#916

So, after the HDD was reformatted, tried the usb again, same problem. When powering down the laptop there was a very quick message, something like "no caching mode page found". Did another mkusb , noticed this afterwards ..

NAME MODEL FSTYPE LABEL MOUNTPOINT SIZE NAME sdb TOSHIBA_USB_DRV iso9660 Kubuntu 19.10 amd64 7.5G sdb sdb1 iso9660 Kubuntu 19.10 amd64 2.1G sdb1 sdb2 vfat Kubuntu 19.10 amd64 3.9M sdb2 sdb3 ntfs usbdata 5.3G sdb3

with the 'live' option, there was no default, it asked whether I wanted to use vfat or iso9660. I took a 'y' to both, not knowing ??

Edit #2

After watching the video at https://www.youtube.com/watch?v=buWwqeGfVmc , did this

sudo /sbin/hdparm -I /dev/sdb

/dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0

Edit #3

@sudodus - You mentioned > Some HP computers do not want to boot via grub from USB when there is a GUID partition table (GPT). For such computers you should select MSDOS partition table in the 'Settings' menu, when you make a persistent live drive. . But no matter what initial menu options I used with mkusb there was no settings option ?

#917

@oygle,

I see from


NAME MODEL FSTYPE LABEL MOUNTPOINT SIZE NAME
sdb TOSHIBA_USB_DRV iso9660 Kubuntu 19.10 amd64 7.5G sdb
sdb1 iso9660 Kubuntu 19.10 amd64 2.1G sdb1
sdb2 vfat Kubuntu 19.10 amd64 3.9M sdb2
sdb3 ntfs usbdata 5.3G sdb3

that you have used mkusb-plug, and then there is no problem with HP computers that do not want to boot via grub from USB because mkusb-plug uses a semi-cloning method (uses sed to modify the linux lines in the menuentries in [FONT=Courier New]grub.cfg[/FONT], and boots via syslinux in BIOS mode). So you are not suffering from that problem. It might have affected you, if you used mkusb-dus alias the classic mkusb version 12.

The USB drive described above looks good to me. It should be possible to boot from it. If the computer fails, you could try with another maybe older version of Kubuntu or standard Ubuntu, but I think there is a serious problem with the hardware.

What operating system did you run when you ran [FONT=Courier New]hdparm[/FONT] (to get the output shown in the previous post)?

What happens when you try to check the S.M.A.R.T. status via Disks when running the same operating system?

[hr][/hr] I am not good at interpreting the output of hdparm, but I can imagine that your output indicates problems.

I think you can get better help if you create an own separate thread for this problem. That way many more people will see your description, particularly people who are good at troubleshooting hardware problems. (Those people might not be interested in this tutorial thread about methods to make boot drives.)

If you create an own separate thread, please post a link to that new thread here, so that I and others who have seen your problem here can follow the development in the new thread (and maybe contribute to it).

#918

sudodus said: @oygle,

The USB drive described above looks good to me. It should be possible to boot from it. If the computer fails, you could try with another maybe older version of Kubuntu or standard Ubuntu, but I think there is a serious problem with the hardware.

Yes I agree, something wrong with the hardware, memory, motherboard, it is old. BUT, out of frustration I used "Startup Disk Creator" on a DVD, used it and it is now installing on the HP laptop.

sudodus said: What operating system did you run when you ran [FONT=Courier New]hdparm[/FONT] (to get the output shown in the previous post)?

Kubuntu 19.10

sudodus said: What happens when you try to check the S.M.A.R.T. status via Disks when running the same operating system?

It isn't installed yet on that laptop but will do soon. I did get Smartmontools installed on the HP laptop before I wiped the HDD, and the 2 min quick test was okay, but all the other log type info said 'pre fail' or 'old', etc, so the laptop is due to be tossed out for sure.

sudodus said: I think you can get better help if you create an own separate thread for this problem. That way many more people will see your description, particularly people who are good at troubleshooting hardware problems. (Those people might not be interested in this tutorial thread about methods to make boot drives.)

If you create an own separate thread, please post a link to that new thread here, so that I and others who have seen your problem here can follow the development in the new thread (and maybe contribute to it).

Okay there is one at https://ubuntuforums.org/showthread.php?t=2440334 , had some replies , but as I thought it was mkusb specific problem, added a post here. Thanks for all your help @sudodus, very much appreciated. :)

Just to recap quickly on what I tried

  • 2 different usb devices
  • 'live' , 'persistent live' and other settings in mkusb
  • Rest BIOS to defaults in HP laptop, plus checked the BIOS settings many times
  • No memory test as yet
  • Startup Disk Creator to usb, no install option there either
#919

@oygle,

There seems to be a specific problem affecting booting from USB. Fortunately it does not affect booting from DVD :-)

I will look at that other thread now ...

#920

[SIZE=4]mkusb version 12.4.5 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb - 12.4.5

mkusb - 12.4.5-1ubuntu2

mkusb - 12.4.5-1ubuntu3

mkusb - 12.4.5-1ubuntu4

mkusb - 12.4.5-1ubuntu5

[/td][/tr][/table]

  • backup and restore: 'live-rw' --> 'writable'
  • backup and restore: getcnt and getdrw: fix to work with mmcblk devices
  • backup and restore: getcnt and getdrw: minor bugfixes after testing
  • debian/control: mkusb et.al. depend: mkusb-common (>= 12.4.5)
  • debian/update-control: depends updated 'automatically'

The **backup** and **restore** scripts for the partition for persistence are upgraded to match the new label 'writable' replacing the old deprecated label 'live-rw'. Please notice that 'casper-rw' is also working as label for persistence and the backup and restore scripts can manage both labels, 'casper-rw' and 'writable'.

There are also modifications in order to make backup and restore work not only with USB drives but also memory cards that are seen as mmcblk devices.

There are also modifications in the debian scripts in order to force upgrading of relevant subpackages of mkusb, when mkusb is upgraded manually (for example in persistent live systems, when you may not want general upgrading).

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.4.4 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#921

This is to inform that I could make persistent usb installation using mkusb on Ubuntu 18.04 for ExTiX LXQt Mini 20.4, Build 200402 iso. This distribution is based on Ubuntu 20.04 and uses LXQt Desktop. It uses the latest Linux Kernel 5.6.2.

Kamalakar

#922

Hi Kamalakar,

Interesting :-) Sometimes I test Extix, and persistence works with some versions, but not all.

Please explain which version of mkusb that you used, mkusb-dus or mkusb-plug and if you could use the default settings, or if you had to modify any settings or tweak something manually.

#923

longpanda said: Hi, I recommand a new tool, Ventoy. With ventoy you just need to copy the iso file to the USB drive and boot it.

See http://www.ventoy.net for detail.

Aonther interesting FOSS project :-)

#924

sudodus said: Hi Kamalakar,

Interesting :-) Sometimes I test Extix, and persistence works with some versions, but not all.

Please explain which version of mkusb that you used, mkusb-dus or mkusb-plug and if you could use the default settings, or if you had to modify any settings or tweak something manually. dus 12.4.4 I selected Install/Persistent_Live/ I have UEFI machine. I got confused for Grub selection but selected grub-image (I think).

The installation worked fine with persistence. I have 3 partitions on usb EXTIX, persistence and usbdata.

NB: the iso is extix-20.4-64bit-efi-lxqt-nvidia-mini-1170mb-20200404.iso 1.3 GB.

Kamalakar

#925

Thanks for the detailed description, Kamalakar,

I was curious, so I downloaded and tested this Extix version.

filename: [FONT=Courier New]extix-20.4-64bit-efi-lxqt-nvidia-mini-1170mb-20200404.iso[/FONT] size: 1.3 GB md5sum: [FONT=Courier New]071f969c9186dc1233baa8ecb26e52cf[/FONT]

I created it when booted in BIOS mode.

  • with the default settings the created USB drive booted live-only
  • when I selected the setting 'upefi' - USB-pack-EFI the created USB drive booted with persistence (and it works both in BIOS mode and UEFI mode.

I know that the setting 'upefi' - USB-pack-EFI is suggested when running mkusb in an installed system booted in UEFI mode, so it was easy to guess what to do in order to get things working also from BIOS mode :-)

*Comment:* Although this iso file is based on Ubuntu, the overlay system for persistence is inspired by Debian. For example, the label on the partition for persistence is 'persistence' (and Debian iso files are treated the same way in order to make a persistent live drive).

#926

sudodus said: Thanks for the detailed description, Kamalakar,

  • when I selected the setting 'upefi' - USB-pack-EFI the created USB drive booted with persistence (and it works both in BIOS mode and UEFI mode.

.

I also have one Laptop working in BIOS mode. I tried another installation on it selecting uefi but it does not boot in BIOS and boots only on uefi. Do I need some other version of mkusb?

Kamalakar

#927

@Kamalakar,

Please describe the problematic installation

  • Linux distro and version.
  • Is the problem affecting a live-only or persistent live system made by mkusb? Or is it an installed system, (installed from a USB system that was made by mkusb)?

Talking about mkusb version 12 alias mkusb-dus

If you ran in UEFI mode and used mkusb to create a persistent live drive, you must accept using usb-pack-efi to make the USB drive boot in BIOS mode. Otherwise it will only boot in UEFI mode.

Talking about mkusb-plug

mkusb-plug is 'semi-cloning', actually using sed to modify grub.cfg and txt.cfg to

replace [FONT=Courier New]**'quiet splash' **[/FONT]with [FONT=Courier New]**'persistent  '**[/FONT]

and creating a partition for persistence behind the cloned image of the iso file. This works with the Ubuntu 19.10 and newer versions and with current versions of Debian, and with some but far from all re-spins based on Ubuntu and Debian. So if your problematic installation does not work with mkusb-dus, it *might* work with mkusb-plug.

#928

My BIOS Laptop is HP which required selection of MSDOS and upefi. I read about this on this site.

Now persistence is working on acer aspire which is UEFI and HP Probook which is BIOS.

Kamalakar

#929

@Kamalakar,

I see. My son has such an HP computer, so I had that experience 'at home' and made it possible to select an MSDOS partition table for such computers (that refuse to boot via grub from a USB drive). Selecting upefi, USB-pack-EFI, can be useful in several cases.

I'm glad that you made things work. Thanks for the link and for sharing your experience :-)

#930

[SIZE=4]The installer Calamares in Lubuntu 20.04[/SIZE]

  • Calamares works from live (live-only) as well as from persistent live systems made by mkusb.
  • Calameres does not work from live systems booted to RAM using the boot option 'toram'. See this bug report.

There are more details about creating an installed system when booted from a [persistent] live drive made by mkusb at this link.

#931

Thanks for the thread man! Been trying to find this information for a while

#932

[SIZE=4]Xubuntu Core 20.04 LTS with mkusb 12.4.5 (mkusb-dus and mkusb-plug)[/SIZE]

  • This compressed image file contains a semi-cloned persistent live system made with mkusb-plug.
  • The following program packages are added: mkusb, usb-pack-efi, firefox, gedit.

. md5sum=5705d687d4b75c4657a3d1392da5c13d . The size 1.14 GiB is smaller than the standard 20.04 LTS iso files (Xubuntu: 1.55 GiB, Lubuntu: 1.63 GiB).

  • It is straightforward to extract and clone from the compressed image file to a USB pendrive or memory card.

. boologo, txt.cfg, loopback.cfg, grub.cfg. This is expected with this systsem.

  • When you boot into this persistent live system, you will notice that some files are modified from the original Xubuntu versions,
#933

I see that mkusb is also plagued by disk checking on boot. Not just with Live USB but with Persistent USB also. If not fast enough with ctl-c it runs until over 80% complete. Very irritating. If it was just a run once it would not be so bad. Is there some way to get rid of this or is it a bug we have to live with? I also see the Try Ubuntu/Install Ubuntu screen popping up again. I don't recall seeing this on a Persistent USB in quite a while.

Edit: Try Ubuntu/Install Ubuntu screen can be disabled by overwriting the text in syslinux.cfg with:


default live
label live
  say Booting an Ubuntu Persistent session...
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed boot=casper persistent initrd=/casper/initrd quiet splash noprompt --

Edit 2: Oops, Just realized that a mkusb does not have a writable syslinux.cfg, must have tested above on a Rufus USB.

#934

C.S.Cameron said: I see that mkusb is also plagued by disk checking on boot.

Not just with Live USB but with Persistent USB also. If not fast enough with ctl-c it runs until over 80% complete. Very irritating. If it was just a run once it would not be so bad. Is there some way to get rid of this or is it a bug we have to live with?

I don't know, but I would be very happy, if someone could suggest a work-around. Someone suggested the Escape key.

I also see the try/install screen popping up again. I don't recall seeing this on a Persistent USB in quite a while.

I have noticed that the grub menu will be displayed in some computers, when booting in UEFI mode, and not in other computers. Is this what you are talking about? Or are you talking about something else?

I think many people want those menus to be displayed in order to provide the choice.

Anyway, I have been able to remove some command lines about graphic mode before the menuentries and/or boot option 'vt_handoff' in order to display the grub menu in UEFI mode in two of my computers.

#935

Someone suggested the Escape key.

I believe esc key switches the boot back and forth between "quiet splash" being off and on. It does not stop the check. The reason the check does not stop sooner, Akeo and I think is that filesystem.squashfs, a large file, is being checked and the routine can not stop in the middle of a file.

#936

C.S.Cameron said: Someone suggested the Escape key..

I believe esc key switches the boot back and forth between "quiet splash" being off and on. It does not stop the check. The reason the check does not stop sooner, Akeo and I think is that filesystem.squashfs, a large file, is being checked and the routine can not stop in the middle of a file.

That's a good theory :-) Anyway, I don't know any way to turn it off. Maybe we can get a good answer from Michael Hudson-Doyle, who fixed the bug about casper-rw.

#937

[SIZE=4]mkusb version 12.4.5 for version 20.10 LTS, Groovy Gorilla[/SIZE]

The PPA at Launchpad includes versions of mkusb for the new developing version 20.10 LTS, Groovy Gorilla.

mkusb could not be tested today, 2019-10-18, with an Ubuntu daily iso file from the testing tracker, groovy-desktop-amd64.iso, because there is no such file yet. So we are ready for testing, and if you have set the repositories to groovy and have an early Ubuntu groovy installed system, please try mkusb.

[hr][/hr] If you run standard Ubuntu [persistent] live, you need an extra instruction to get the repository Universe. (Kubuntu, Lubuntu ... Xubuntu have the repository Universe activated automatically.)

Text after the # character is not used by the shell interpreter, it is a comment for the human eye.

sudo add-apt-repository universe  # this line only for standard Ubuntu live
sudo add-apt-repository ppa:mkusb/ppa          # stable PPA for regular usage
# sudo add-apt-repository ppa:mkusb/unstable   # PPA for development and testing; remove the # in front of the command to use it
sudo apt update
sudo apt install mkusb

sudo apt install usb-pack-efi  # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files
#938

C.S.Cameron said: ...

I also see the Try Ubuntu/Install Ubuntu screen popping up again. I don't recall seeing this on a Persistent USB in quite a while.

Edit: Try Ubuntu/Install Ubuntu screen can be disabled by overwriting the text in syslinux.cfg with:


default live
label live
  say Booting an Ubuntu Persistent session...
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed boot=casper persistent initrd=/casper/initrd quiet splash noprompt --

Edit 2: Oops, Just realized that a mkusb does not have a writable syslinux.cfg, must have tested above on a Rufus USB.

I did not realize this at first (because I often use Lubuntu, which is not affected by this feature). But I think I understand now. You can remove the boot option [FONT=Courier New]maybe-ubiquity[/FONT] from the 'linux line' of grub.cfg:

from


menuentry "Ubuntu - persistent live" {
 search --set=root --fs-uuid 2020-04-23-07-51-42-00
        set gfxpayload=keep
        linux   ($root)/casper/vmlinuz  file=/cdrom/preseed/ubuntu.seed **maybe-ubiquity** quiet splash persistent ---
        initrd  ($root)/casper/initrd
}

to


menuentry "Ubuntu - persistent live" {
 search --set=root --fs-uuid 2020-04-23-07-51-42-00
        set gfxpayload=keep
        linux   ($root)/casper/vmlinuz  file=/cdrom/preseed/ubuntu.seed  quiet splash persistent ---
        initrd  ($root)/casper/initrd
}

If you confirm that this is what you mean, I can modify that in mkusb-dus (the shellscript dus-persistent), maybe also in mkusb-plug (the shellscript mkusb-sedd).

Edit: When dropping the option [FONT=Courier New]maybe-ubiquity[/FONT], the option to select language will also be dropped. Maybe it is worthwhile to keep this option anyway, or to create an extra menuentry for the purpose to select language?

#939

Great tool. Thanks for share it.

#940
#941

Re: maybe-ubiquity

Yes very good, removing "maybe-ubiquity" from the grub.cfg persistent menuentry eliminates the "Try Ubuntu / Install Ubuntu" screen and the amount of time it adds to booting.

For a Persistent install it might be a good idea to put an "Install Ubuntu" option in the grub menu. That way it would not slow down booting.

No need to change the Live only boot.

#942

I have tried to make a bug report concerning Live USB Disk Check. It is my first ever Bug Report, not sure I did it right.

https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1875548

#943

[SIZE=4]mkusb version 12.4.6, 12.4.7 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"] mkusb 12.4.6

mkusb 12.4.7

[/td][/tr][/table]

  • dus-persistent: grub-n-iso: 'tweak 4', menu_entry_1: 'maybe-ubiquity' to set language for persistent live in one menuentry, but removed from the standard menuentry for persistence
  • grub.cfg: menu entry with 'maybe-ubiquity' to set language for persistent live
  • dus-persistent: grub-n-iso and grub.cfg: to manage 'fsck.mode=skip' to check the live system integrity in persistent live menu entries

The current version of mkusb-dus, 12.4.7, creates persistent live drives, that can *help during iso-testing because you can skip testing the integrity of the drive*, which can last for minutes in slow USB drives. So if you use the default 'persistent live' menu entry for Lubuntu with Calamares or the 'live-only to RAM' for the other Ubuntu flavours with Ubiquity it should work faster than with a standard live drive.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.4.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#944

[SIZE=4]Add a menuentry for persistence into the default grub.cfg and txt.cfg in the iso file[/SIZE]

We can add a menuentry for persistence into the default configuration files for grub and syslinux in the iso files of the Ubuntu 20.04 LTS flavours. This would make it straightforward to get a persistent live system directly by cloning the iso file.

You have probably already noticed that when you boot a USB drive cloned from an iso file of 20.04 LTS, a partition with the label writable will be created. In the default ‘live’ case it is used to store logs (and maybe dump files) in order to help debug problems during booting and installing.

And if you add the boot option persistent the system will become a persistent live system, where you can install programs and save files in your standard directories (Documents, Downloads, Music, Pictures …) and they will survive shutdown and reboot.

So with an extra boot option in the default grub.cfg and txt.cfg files, the user will get the option to run the default cloned drive not only live-only but also persistent live. This can be achieved with mkusb now, but most end users will never install it, they will probably not even know about it. But the standard Ubuntu Startup Disk Creator is there for cloning.

[SIZE=3]Demo example with Lubuntu[/SIZE]

The small configuration files (that are modified) and their md5sums as well as a compressed image file and its md5sum are uploaded at this link to a Google Drive directory.

If you extract the compressed image file to a USB pendrive or memory card (or other drive), you will get a system that behaves pretty much like a Lubuntu 20.04 LTS system cloned from the iso file.

Please notice that you need not create a partition for persistence. Lubuntu will do that automatically.

Try it and get a feeling of how the Lubuntu live system will work, when the new boot options for persistence are there.

Edit: You can use mkusb to extract directly to the target drive, Maybe you can also use Disks,[FONT=Courier New] gnome-disks[/FONT], directly. You can use several tools to extract from compression to a file and after that clone to the drive.

#945

How to add a menuentry for persistence into the default grub.cfg and txt.cfg on a read only ISO9660 partition?

I have tried writing to the 20.04 Desktop ISO file without luck.

I am not sure how you do it for mkusb.

However "persistent" can it be added to boot by pressing F6 each time.

#946

C.S.Cameron said: How to add a menuentry for persistence into the default grub.cfg and txt.cfg on a read only ISO9660 partition?

I have tried writing to the 20.04 Desktop ISO file without luck.

I am not sure how you do it for mkusb.

However "persistent" can it be added to boot by pressing F6 each time.

I ask the developers of Lubuntu to do it (add a menuentry for persistence into the default grub.cfg and txt.cfg on a read only ISO9660 partition) :-P If successful with them, maybe it will be possible to do something similar with standard Ubuntu desktop the other Ubuntu flavours.

Otherwise I think mkusb will do for you. Maybe you want mkusb to do something else or add something. In that case please ask for it. Maybe I see a way to fix it.

[hr][/hr] Anyway please download the compressed image file from this link and try it. You can extract and clone it to a USB drive with mkusb. The system you get in the USB drive mimics the way an improved Lubuntu iso file would work, when cloned. (But it is not exactly the same, obviously.)

#947

[SIZE=4]mkusb version 12.4.8 ... 12.5.5 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

.. mkusb-sedd: ... puer: relies on automatic creation of partition for persistence by Ubuntu (faster and more robust now) ... p_checkpoint: 'Are you sure?' added in text mode .. mkusb-tow: ... p_checkpoint: 'Are you sure?' added in text mode

  • mkusb 12.4.8: mkusb-plug

. improved identification of version number

  • mkusb 12.4.9: mkusb-plug: . mkusb-sedd: puer:

.. dus-persistent: grub-n-iso: ... 'grub-graph-prefix' to improve grub menu with the ... grub background file 'mkusb-grub-bg_800x600.png'

  • mkusb 12.5.0

.. dus-persistent: probe_source: recognizing Sparky Linux as a Debian respin

  • mkusb 12.5.1

.. manage two usb-pack-efi versions: added p_usb_pack_manage and p_usb_pack_toggle ... call p_usb_pack_manage from p_starter and p_setting ... dus-persistent: grub_n_iso: removed verbosity for extraction of usb-pack_efi ... usb-pack-efi: installs two tarballs: usb-pack_efi-0.tar.gz and sb-pack_efi-1.tar.gz

  • mkusb 12.5.2

.. dus: p_usb_pack_manage and dus-persistent: separate usb-pack_efi files for grub 2.02 and grub 2.04 ... [FONT=Courier New]usb-pack_efi-x.tar.gz[/FONT] --> [FONT=Courier New]usb-pack_efi-x.tar.xz[/FONT] ... and corresponding [FONT=Courier New]grub-x.img.xz[/FONT] for better compression plus several tweaks with logical statements

  • mkusb 12.5.3

.. dus: p_usb_pack_toggle: changed default 0 --> 1 .. grub.cfg: changed logic detecting rmmod tpm and bootmode and changed text colours .. grub-graph-prefix: changed text colours .. mkusb-grub-bg_800x600.png: background with 'water-mark'

  • mkusb 12.5.4

.. dus-persistent: at tweak 3: setting search by UUID failed .. p_setting: new test for usb-pack-efi

  • mkusb 12.5.5

[/td][/tr][/table]

[SIZE=3]Automatic creation of a partition for persistence in mkusb 12.4.8 via mkusb-plug 2.7.0[/SIZE]

mkusb-plug version 2.7.0 is bundled with mkusb 12.4.8. It relies on automatic creation of a partition for persistence by Ubuntu which makes it faster and more robust. In other words, mkusb-plug only 'semi-clones' with sed to replace 12 characters: the boot option string [FONT=Courier New]'quiet splash'[/FONT] with [FONT=Courier New]'persistent'[/FONT] and two space characters. It no longer creates a partition for persistence for Ubuntu and the Ubuntu flavours. Instead it lets the live system do it the first time it is booted. (mkusb-plug is still creating a partition for persistence with Debian iso files.)

Improved identification of version number in mkusb-plug is a bug-fix that you might never notice.

[SIZE=3]dus-persistent makes nicer grub menus[/SIZE]

[SIZE=3]Nicer grub menu in mkusb 12.5.0[/SIZE]

In the grub menu the text size is controlled and there is a wallpaper in mkusb 12.5.0 . The menu looks the same in BIOS mode and UEFI mode. In high resolution screens the menu text was too small in UEFI mode, and it was difficult to read. Please notice that this feature works for Ubuntu and the Ubuntu family flavours with the default settings, but it does not work with usb-pack-efi. See the attached screenshot.

[SIZE=3]Three new Linux distros can be made persistent live by mkusb 12.5.1[/SIZE]

  1. After adding a test in mkusb 12.5.1 dus-persistent can recognize Sparky Linux 5.11 and treat it 'as Debian' in order to make persistence work. Sparky can be made persistent live both via mkusb-dus and via mkusb-plug and both in BIOS mode and UEFI mode (screenshot).
  1. Elementary 5.1-stable.20200501 was already recognized 'as Ubuntu' and persistence works. In both cases it defaults to usb-pack-efi.
  1. Endless 3.8 creates a persistent live system automatically when cloned to a USB drive, so it is straight-forward for mkusb-dus.

[SIZE=3]Choice between an old and a new usb-pack_efi in mkusb 12.5.2[/SIZE]

The classic (old) usb-pack_efi is renamed to [FONT=Courier New]usb-pack_efi-0.tar.gz[/FONT]. It works well with most cases. It can boot 32-bit systems even in UEFI mode. But it cannot boot anything with secure boot because it lacks the necessary signature.

The new usb-pack_efi [FONT=Courier New]usb-pack_efi-1.tar.gz[/FONT] works with new systems. It can boot a system in UEFI mode (if the system has the necessary signature). But it cannot boot 32-bit systems in UEFI mode.

You can select which version to use by linking from either version to [FONT=Courier New]usb-pack_efi.tar.gz[/FONT] via the menu system of mkusb-dus. There is a menu entry in the starter menu. See the attached screenshot.

[SIZE=3]Added separate files for grub 2.02 and grub 2.04 in mkusb 12.5.3[/size]

Separate files for grub 2.02 and grub 2.04 were added alongside the original usb-pack-efi file and grub image file.


grub-0.img.xz
grub-2.02.img.xz
grub-2.04.img.xz
usb-pack_efi-0.tar.xz
usb-pack_efi-2.02.tar.xz
usb-pack_efi-2.04.tar.xz

There are several tweaks to help select the version of these files in a convenient way without increasing the user interaction (beyond that of the previous version mkusb 12.5.2). For example

  • improved help text in dus-persistent:

The image file 'grub.img.xz' is not found.

or if it is installed, select it in the settings menu.

  • Please install the package 'usb-pack-efi' -
  • Changed ownership to 'root' of files in [FONT=Courier New]usb-pack_efi-0.tar.xz[/FONT]

[SIZE=3]Various tweaks in mkusb 12.5.4 and 12.5.5[/size]

Various tweaks to make things better after some tests and feedback from users: The new version of usb-pack_efi is the default now, and the wallpaper is less intrusive, a grey colour to make it nice for the eyes and a watermark (instead of the colourful mkusb logo; compare the screenshots). Some logical statements in the grub.cfg templates are improved. There is also a new test for the existence of usb-pack-efi before starting dus-persistent (to create a persistent live drive).

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Unstable 2: This new version of mkusb might also be available via this link: mkusb/gui#from_phillw.net. Unstable 3: There are tarballs with only dus and guidus (mkusb version 12) as a last alternative.

[hr][/hr] Stable: mkusb version 12.5.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#948
#949

After feedback from @C.S.Cameron I intend to copy mkusb version 12.5.5 to the stable PPA, ppa:mkusb/ppa

Then I start thinking about the next thing to improve, and it will probably be to include usb-pack-efi as recommended and to remove some irritating pop up windows when running installed systems in UEFI mode.

I am also considering porting the up to date tool to create Windows installer drives from mkusb-plug to mkusb-dus. This is particularly important now that woeusb does not install in Ubuntu 20.04 LTS.

#950

[SIZE=4]mkusb version 12.5.6 - 12.5.7 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

.. dus: p_winsel: select method to make Windows installer, the ... old method or the new mkusb-tow imported from mkusb-plug .. mkusb-plug: mkusb-tow: wf_cleanup: added umount after partprobe to ... manage problems because of automount plus some cosmetics .. dus-persistent: Silently select grub.img and usb-pack-efi, when ... running in an installed system in UEFI mode .. modified debian/control file to tie packages closer together

  • mkusb 12.5.6

.. dus-persistent: find_distr, chk4uefi: ... recognizing Sparky Linux as Debian respin when running .. p_chk_programs: using 'p_want_pck_s mkusb-tow ...' ... p_need_pck pv --> p_want_pck pv ... p_want_pck watch-flush .. dus-live & dus-persistent: using watch-flush via wf_prep & wf_cleanup .. debian/install files: mkusb-tow and watch-flush moved to mkusb-common

.. minor tweaks in dus-live & dus-persistent: .. made independent of pv, added 'faintvid' ANSI escape sequence

.. Package: mkusb-common: ... Replaces: mkusb (<< 12.5.7), dus (<< 12.5.7), mkusb-plug (<< 12.5.7) ... Breaks: mkusb (<< 12.5.7), dus (<< 12.5.7), mkusb-plug (<< 12.5.7) [/td][/tr][/table]

  • mkusb 12.5.7
  • mkusb 12.5.7-1ubuntu2
  • mkusb 12.5.7-1ubuntu3 (tweak of the debian package system)

[SIZE=3]There are two improvements in version 12.5.6 [/SIZE]

  • New tool to make a Windows installer boot drive ported from mkusb-plug to mkusb-dus: [FONT=Courier New]mkusb-tow[/FONT] 'TO Windows' works well with most current Windows iso files, including those with a file, install.wim, that expands to more than 4 GiB. So two partitions are created, one with FAT32 to boot from and one with NTFS where the main content of the iso file is extracted. The old mkusb method, that works well in 32-bit systems (but not when install.wim exceeds 4 GiB) is still available.
  • When running in an installed system booted in UEFI mode mkusb-dus selects method silently for persistent live drives. This is made because it is nowadays common to run Ubuntu in this way, and we still want to make drives that boot both in UEFI mode and BIOS mode. Earlier there were warnings, that compressed files were extracted instead of running commands because the grub tool to create a BIOS bootloader (grub-pc) is not compatible with grub for UEFI (grub-efi).

[SIZE=3]You may notice some improvements in version 12.5.7 [/SIZE]

  • Sparky Linux is recognized as a working host operating system by mkusb.
  • [FONT=Courier New]watch-flush[/FONT] is imported from mkusb-plug to mkusb-dus in order to show what is happening while the system i flushing the buffers (during writing to a USB drive or memory card).

The programs [FONT=Courier New]watch-flush[/FONT] and [FONT=Courier New]mkusb-tow[/FONT] are moved from the mkusb-plug package to the mkusb-common package. This may cause a hiccup when upgrading from a previous version. You can fix it with the following commands


sudo apt update
**sudo apt -f install**        # this is the crucial command line with -f, --fix-broken
sudo apt install mkusb

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.5.7 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#951

Thanks for these helpful thread and for the codes. I am trying this for last weeks. But I didn't get the result that I want. I used to save this codes in google docs. In the list of codes I have all the important codes which used to make a document and logo. I have a code for [[COLOR=#000000]subscript and superscript in google docs[/COLOR]]("https://thetechvin.com/how-to-do-subscript-in-google-docs/") and so many codes like that. In this thread, I have found so many codes that I can include in my list of imp codes. SO thank you so much.:p:p

#952

[SIZE=4]Instructions to make a boot drive, that boots both in UEFI and BIOS mode[/SIZE]

Alongside testing mkusb version 12.5.7 from the unstable PPA, I suggest that you look at the following link,

[SIZE=3]Do it yourself - with the isoboot alias grub-n-iso method[/SIZE]

help.ubuntu.com/community/Installation/iso2usb/isoboot

where I describe a basic way to use a small compressed image file,


dd_grub-boot-template-for-uefi-n-bios.img.xz

that I think will be convenient to use, both

  • to create a simple [persistent] live drive with the iso-boot alias grub and iso method, and
  • to create an installed system that can boot both in UEFI and BIOS mode according to C.S.Cameron's method, and
  • (maybe even) to create a multiboot USB pendrive.

I think it is convenient to use this compressed image file (more convenient than to let mkusb create a persistent live drive, and then delete partitions in order to create the partitions for an installed system).

#953

I have given this a few tries and it is much faster than creating a persistent USB using dus and then taking it apart. It is good for just about any bootable USB project that needs to boot both BIOS and UEFI including Full installs, MultiBoot Persistent installs, MultiBoot ISO file installs, MultiBoot Full installs, MultiBoot Mixed installs, Installs using ISO's extracted to ext4 partitions rather than ISO9660 partitions, Utility/repair disks, etc.

#954

Sudodus:

FYI

Have been thinking about swap space. https://askubuntu.com/questions/1247133/how-to-handle-full-install-usb-and-swap-space/1247151#1247151

A Live or Persistent USB will use every swap partition it can find on a computer.

When creating a Full install USB, Ubiquity will format every swap partition it can find on the computer and add them to fstab.

Swap can be turned off using ``` sudo swapoff -a


The mounting of a particular swap partition at boot can be eliminated using Disks or by adding a line to fstab: ```
/dev/disk/by-uuid/7a5013b7-9e87-45d1-b6a1-e37afde9955d none swap sw,noauto 0 0

Adding a swap file to a full install of Ubuntu seems to eliminate the use of swap partitions, unless they are added to fstab using Disks or by hand.

My plan for tomorrow is to try to add a swap file to a Persistent drive, maybe even add hibernation.

#955

@C.S.Cameron,

This is interesting information about swapping :-)

I'm looking forward to what you can report after testing with a swap file in a persistent live drive.

#956

I must be missing something here. I read the install process a few times to try to simplify it for me. I appreciate all the work you put into this, but In the end, it has become a TL;DR type of install. Way to complex in light of the outcome.

I found Ventoy to be the most simple, and easiest multiboot ISO I have ever come across! I found it by accident, but it was mentioned on post #921 above that I missed somehow.

#957

@VMC,

If you want a tool to create a multiboot USB drive, I agree, that there are tools that are more polished and easier to use. You mention Ventoy and I can mention YUMI and MultibootUSB.

The method that I describe here (in post #950) is not really a tool but a 'do it yourself' method with some help to make it boot both in BIOS mode and UEFI mode. Some people prefer to build things themselves, and the main target for it is not multiboot drives, but the other two kinds of drives/systems, that I listed,

  • to create a simple [persistent] live drive with the iso-boot alias grub and iso method, and
  • to create an installed system that can boot both in UEFI and BIOS mode according to C.S.Cameron's method.
#958

sudodus said: @VMC,

If you want a tool to create a multiboot USB drive, I agree, that there are tools that are more polished and easier to use. You mention Ventoy and I can mention YUMI and MultibootUSB.

The method that I describe here (in post #950) is not really a tool but a 'do it yourself' method with some help to make it boot both in BIOS mode and UEFI mode. Some people prefer to build things themselves, and the main target for it is not multiboot drives, but the other two kinds of drives/systems, that I listed,

  • to create a simple [persistent] live drive with the iso-boot alias grub and iso method, and
  • to create an installed system that can boot both in UEFI and BIOS mode according to C.S.Cameron's method.

Thanks for the info. I was trying to understand the difference between yours and the others. I don't mind, and do prefer DIY projects. I just stumbled across longpanda post#921, and after using it, I really liked it. By the way his is ad free, not so with Easy3Boot. Also E2B suggest a huge partition space to use?! I've used the others in the past, but Ventoy is the easiest, and doesn't take up much space to run.

#959

I was really disappointed with MultiBootUSB the last time I tried it. The Linux version worked better than the Windows version, but it was not handling 20.04 very well. It looks almost like it has been abandoned. YUMI BIOS/GRUB 0.0.2.2 worked well but is Windows only. Good to see it is working on Both BIOS and UEFI.

Ventoy looks interesting, (even though I am not keen on running scripts). Seems to boot 20.04 okay, think I will play with it for a while, see if it works with Clear Linux. Does not look as versatile as mkusb though.

#960

C.S.Cameron said: ...Ventoy looks interesting, (even though I am not keen on running scripts). Seems to boot 20.04 okay, think I will play with it for a while, see if it works with Clear Linux. Does not look as versatile as mkusb though.

I could not get Clear Linux to boot using Ventoy. I emailed the author, he is looking that.

#961

VMC said: I could not get Clear Linux to boot using Ventoy. I emailed the author, he is looking that.

Quite a coincidence, I could not get Ventoy to boot Clear either, neither would MBUSB, YUMI or UNetbootin.

Ventoy has the most complex grub.cfg file I have ever seen.

As soon as I figure out how to get persistence working I am going to try to see if it will boot a Full install.

#962

I have a problem just to install Clean linux. It doesn't play well for dual boot. I then used another hard drive and it failed. I thought I was able to install in the past.

#963

The Phoronix Benchmarks made me interested: https://www.phoronix.com/scan.php?page=article&item=windows-may2020-linux&num=1. I am trying it on a Live USB made using baliniaEtcher. Clear looks like Ubuntu on the outside, but things look different on the inside. It seems smooth and fast , but maybe "better the devil you know than the devil you don't know" Page that explains Ventoy Persistence: https://www.ostechnix.com/create-persistent-bootable-usb-using-ventoy-in-linux/?unapproved=78804&moderation-hash=bbbe0e003dd340fde711e98d1789dd15#comment-78804. I built a 6GB persistence.img file, no 4GB limit. USB won't boot on my HP.

#964

[SIZE=4]Easy way to get installed Ubuntu 20.04 LTS that boots in UEFI and BIOS[/SIZE]

This is the easy way for you to get an installed Ubuntu system, that boots both in UEFI and BIOS mode, and you can use it in several cases. However,

  • if you want to learn how to do it, or
  • if you want to be sure of the content (and don't rely on me), or
  • if you want hibernation, or
  • if you want an encrypted disk (LVM with LUKS encryption),

then you must do it yourself. (In the encrypted disk case, you must create the passphrase yourself during the installation.)

Using a method similar to what is described by C.S.Cameron I have created

  • a compressed image file of
  • an installed system of Ubuntu 20.04 LTS
  • that can boot both in UEFI mode and BIOS mode (alias CSM alias legacy mode).

This compressed image file expands to 15.7 GB, so it fits into drives with size at least 16 GB. It is easy to extract and clone it to an external drive

. extraction tool, . plus cloning tool, . plus a tool to fix the gpt partition table gpt-fix. You may have problems in Windows to find such a tool, and in several cases you can skip it, and the drive will work anyway.

  • with mkusb (only one step),
  • but you can use any

After extraction, cloning and fixing, it is a good idea to expand the root partition, where Ubuntu is installed in order to use the whole drive, when you are using a big drive ( > 16 GB ).

There are more details about this image file

dd_unb_ubuntu-20.04_15GB_2020-06-26.img.xz

at the following links,

help.ubuntu.com/community/Installation/UEFI-and-BIOS

help.ubuntu.com/community/Installation/UEFI-and-BIOS/stable-alternative - details of the method to create the system

Finally, the installed system has a password, and you are encouraged to change it,

Password: changeme

#965

I tried this and am impressed. Smaller to download than the Ubuntu ISO but contains a Full 20.04 install. Easy and quick to flash to USB disk from Windows or Linux. I used Rufus. Simple to customize and upgrade. Just like having a desktop on a thumbdrive or SD card. Good job sudodus

#966

[SIZE=3]Easy way to get installed Ubuntu 20.04 LTS that boots in UEFI and BIOS - continued[/SIZE]

I have a computer with an nvidia card, and installed the nvidia proprietary driver, that was recommended and selected automatically by Ubuntu. It works well in that computer, I could see that VLC uses vdpau acceleration (using the graphics chip to play video).

Then I moved the drive with the installed Ubuntu 20.04 LTS system to other computers (laptops), that have no nvidia card, and the graphics work as before, the correct free drivers are selected and work as they should.

So in this way, this installed system is more portable than a [persistent] live system, where you cannot install an nvidia proprietary driver.

Finally, please notice that *you*, the end user, must install the proprietary driver (if you want it). Due to the licensing rules it must not be included in the compressed image file, and the same applies to the package ubuntu-restricted-extras.

#967

[SIZE=4]mkusb version 12.5.8 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. dus-wipe: added p_zentest, wf_prep, wf_cleanup to use watch-flush [/td][/tr][/table]

  • mkusb 12.5.8

[SIZE=3]Improvement in version 12.5.8 [/SIZE]

The program [FONT=Courier New]watch-flush[/FONT] is used also when wiping the whole device. This keeps the user informed about the progress and eta (estimated time until the wiping is finished).

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.5.8 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#968

exelente

#969

There is a bug in the Groovy iso files, that affects booting from iso files. In many PC computers, it has been impossible to boot from USB drives with cloned live systems. There is a bug-fix, that makes it work again, at least in some computers. See these links,

[hr][/hr] Persistence by mkusb-dus is also affected. Persistent live systems of Ubuntu family flavours with these new Groovy iso files need the 'upefi' setting - usb-pack-efi - in order to work. I will wait a while before modifying mkusb, because I expect more changes until this bug is completely fixed.

[hr][/hr] For isotesting other features and program packages you can create USB drives with grub-n-iso systems according to the following link. Such systems seem to work both live-only and persistent live, they are not affected by this bug.

#970

BIOS/UEFI Template Broken? Re dd_grub-boot-template-for-uefi-n-bios.img.xz

Cloned template to disk using Rufus, Etcher, etc, in Windows.

Boot gives: Error no such partition / ... / GRUB rescue

Install GRUB: sudo mount /dev/sdx2 /mnt , sudo grub-install --boot-directory=/mnt/boot /dev/sdx

Boots to GRUB menu in Bios mode, not in UEFI mode

Adding NTFS partition with ubuntu.iso boots in Bios mode, not in UEFI mode

Installed template to disk using mkusb.

Boots to GRUB menu in Bios mode, not in UEFI mode.

Install GRUB: sudo mount /dev/sdx2 /mnt , sudo grub-install --boot-directory=/mnt/boot /dev/sdx

Boots to GRUB menu in Bios mode and in UEFI mode.

Created .img file of modified USB using disks.

Installed new image file to USB using Rufus in Windows.

It boots to GRUB menu in Bios mode and in UEFI mode.

Added NTFS partition and ubuntu.iso file, boots to Ubuntu in Bios mode and in UEFI mode.

Am I doing something wrong? If not please fix bootloader in template. it is a great tool that can be used in Linux and Windows.

#971

@C.S.Cameron,

  1. Have you checked with

<<<'666fa434dda8de3c6e9ddde83f85f197  dd_grub-boot-template-for-uefi-n-bios.img.xz' md5sum -c

in the directory, where you have the template file? I checked now with the file in my computer and the uploaded file at phillw.net, and they match that md5sum. This template file is dated June 4 10:05 (2020).

  1. Did you forget to extract from compression before cloning into a USB drive in Windows or with mkusb-plug? Only mkusb-dus and Rufus + 7zip (or another compressing/extracting tool) will do unless you extract as a separate step.
  1. Or is the USB drive tired and not quite reliable?
  1. If the template matches the md5sum, and you extracted & cloned correctly, you have found a bug in the original template, that it might not work in some computer(s). Please describe the computer: Brand name and model. If I understand correctly, you have problems to boot in UEFI mode. I have not seen any such problems with this template, so I need your help to debug it.

[hr][/hr] I double-checked in a Dell Precision M4800 and a Lenovo V130 right now: in BIOS mode and in UEFI mode (with and without secure boot), and it boots to the grub menu in all these cases.

#972

MD5SUM's match

Dates match: June 4 10:05 (2020).

Ubuntu 20.04 Install:

Zero'd Kingston Data Traveler 4GB USB2, (~2007), installed .img.xz on Acer, (BIOS), using Disks. Kingston Data Traveler 4GB USB2, (~2007), installed .img on Acer, (BIOS), using Disks. Booted to menu with BIOS boot on Acer. Booted to menu with BIOS boot on HP. Booted to menu with UEFI boot on GigaByte.

SanDisk Cruzer Fit 16GB USB2, installed .img.xz on Acer, (BIOS), using Disks SanDisk Cruzer Fit 16GB USB2, installed .img on Acer, (BIOS), using Disks Booted to menu with BIOS boot on Acer. Booted to menu with BIOS boot on HP. Booted to menu with UEFI boot on GigaByte.

Kingston Data Traveler 4GB USB2, installed .img.xz on Acer, (BIOS), using mkusb Kingston Data Traveler 4GB USB2, installed .img on Acer, (BIOS), using mkusb Booted to menu with BIOS boot on Acer. Booted to menu with BIOS boot on HP. Booted to menu with UEFI boot on GigaByte.

SanDisk Cruzer Fit 16GB USB2, installed .img.xz on Acer, (BIOS), using mkusb SanDisk Cruzer Fit 16GB USB2, installed .img on Acer, (BIOS), using mkusb Booted to menu with BIOS boot on Acer. Booted to menu with BIOS boot on HP. Booted to menu with UEFI boot on GigaByte.

Windows 10 Install:

Kingston Data Traveler 4GB USB2, installed .img.xz on HP, (BIOS), using Rufus Kingston Data Traveler 4GB USB2, installed .img on HP, (BIOS), using Rufus Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

SanDisk Cruzer Fit 16GB USB2, installed .img.xz on HP, (BIOS), using Rufus SanDisk Cruzer Fit 16GB USB2, installed .img on HP, (BIOS), using Rufus Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

Kingston Data Traveler 4GB USB2, installed .img.xz on HP, (BIOS), using Etcher Kingston Data Traveler 4GB USB2, installed .img on HP, (BIOS), using Etcher Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

SanDisk Cruzer Fit 16GB USB2, installed .img.xz on HP, (BIOS), using Etcher SanDisk Cruzer Fit 16GB USB2, installed .img on HP, (BIOS), using Etcher Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

Kingston Data Traveler 4GB USB2, installed .img.xz on GigaByte, (UEFI), using Rufus Kingston Data Traveler 4GB USB2, installed .img on GigaByte, (UEFI), using Rufus Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

SanDisk Cruzer Fit 16GB USB2, installed .img.xz on GigaByte, (UEFI), using Rufus SanDisk Cruzer Fit 16GB USB2, installed .img on GigaByte, (UEFI), using Rufus Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

Kingston Data Traveler 4GB USB2, installed .img.xz on GigaByte, (UEFI), using Etcher Kingston Data Traveler 4GB USB2, installed .img on GigaByte, (UEFI), using Etcher Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

SanDisk Cruzer Fit 16GB USB2, installed .img.xz on GigaByte, (UEFI), using Etcher SanDisk Cruzer Fit 16GB USB2, installed .img on GigaByte, (UEFI), using Etcher Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on Acer. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on HP. Boot gave: Error no such partition / Entering rescue mode... / GRUB rescue> on GigaByte.

To make a long story short, Template seems to be working when installed using Ububtu 20.04. It does not seem to be working, (for me), when installed using Windows 10.

Acer TravelMate 8572T - 6805 i5 8GB RAM BIOS boot Ubuntu 18.04. HP EliteBook 8560W i7 24GB RAM BIOS boot Windows 10 Ver 1909, (Ubuntu 20.04) GigaByte GB-BXi7-5775R i7 8GB RAM UEFI boot Windows 10 Ver 1909, (Ubuntu 20.04)

Kingston USB drive is 13 years old but has always been reliable. SanDisk is about 5 years old and has never been a problem.

Etcher 1.5.101 does not have a problem with .xz if 7Zip is installed on computer. But I tried everything compressed and extracted.

Previously the USB made with mkusb was not showing up on the boot menu as UEFI, without reinstalling grub, but mkusb seems to be completely working now.

#973

@C.S.Cameron,

Thanks for the test results. I will try to reproduce your test results from Windows.

I have a faint idea of what might be the problem: The GPT backup table at the tail end of the drive is missing. If this is the problem, it should be possible to fix with **gptfix** or manually with gdisk. So you can try that even before I get any own test results.

Edit:

This gptfix is built into mkusb. The partitioning tools that I use in Ubuntu will also fix the GPT backup table, when I add a partition, and I will always do that (when using it for 'grub-n-iso' as well as template for an installed system). Have you tested if your systems will boot in UEFI mode after you have created another partition in a drive with the template?

#974

One thing I noticed is that there is a file named efi.img in the /boot/grub folder of the image that is not being extracted by Rufus or etcher, but is being extracted by mkusb and Disks? I tried replacing this file by hand yesterday but it did not seem to help.

I got a little lost trying gptfix and gdisk yesterday.

My previous experiments indicated that once the disk was booting to the GRUB menu there was no problem when NTFS and an ISO were added. If it wasn't booting to the menu in UEFI mode, adding the ISO did not help.

EDIT: Oops, no. efi.img only disappears if I install BIOS GRUB.

#975

C.S.Cameron said: One thing I noticed is that there is a file named efi.img in the /boot/grub folder of the image that is not being extracted by Rufus or etcher, but is being extracted by mkusb and Disks? I tried replacing this file by hand yesterday but it did not seem to help.

If the extracting tool (7-zip) and the cloning tool work correctly, the cloned drive should be identical to what is created by mkusb, *except* the GPT backup partition table at the tail end of the drive.

I got a little lost trying gptfix and gdisk yesterday.

Maybe you must install gdisk, and maybe the version must be fairly up to date. In my main computer with 18.04.x LTS I have 'GPT fdisk (gdisk) version 1.0.3'

My previous experiments indicated that once the disk was booting to the GRUB menu there was no problem when NTFS and an ISO were added. If it wasn't booting to the menu in UEFI mode, adding the ISO did not help.

EDIT: Oops, no. efi.img only disappears if I install BIOS GRUB.

I think it is like this: It might not work to boot 'only the template' in UEFI mode. But after you create a partition (with a file system, where to put either an iso file or an installed system), the tool to create the partition should fix the GPT backup partition table at the tail end of the drive. At least this has been my experience. And then the drive should boot also in UEFI mode.

But I have still not tried to do it from Windows, and I will return when I have test results from that adventure.

#976

@C.S.Cameron,

Will this new template

dd_grub-boot-template-for-uefi-n-bios_new.img.xz

work for you in UEFI mode also when you create it in Windows?


$ <<<'02f0af35a3fbfe10b9cbbc0c0aa2ce96  dd_grub-boot-template-for-uefi-n-bios_new.img.xz' md5sum -c
dd_grub-boot-template-for-uefi-n-bios_new.img.xz: OK

Maybe your problem is that you use target drives that are smaller than the drive, where the template was created. In that case this new template file should work better, because it was created in a USB drive with size 1 GB.

In my computers it behaves somewhat better than the previous version, even without using gpt-fix. For example gparted is more happy with it. But I won't know until I get your test results, because also the old version boots in my computers with smaller USB drives (than where it was created) both in UEFi and BIOS modes without using gpt-fix.

#977

@sudodus:

When flashed on Windows, using Rufus or Etcher or W32DI, BIOS partition is No1, EFI partition is No2.

Boots to "error: no such partition. / Entering rescue mode.../grub rescue>"

Added NTFS partition and ubuntu.iso, still boots to "error: no such filesystem. / Entering rescue mode.../grub rescue>"

When flashed to USB on Ubuntu using mkusb, BIOS partition is now No2, EFI partition is No3. Why?

Mkusb drive boots to menu in BIOS and UEFI modes no errors.

Added NTFS partition and ubuntu.iso to mkusb drive boots Ubuntu Live in BIOS and UEFI as expected.

I am perplexed, As you say, the cloned drives should be identical no matter what flashed them.

If I create a new image from the working mkusb drive above using Disks, the restored clone works if made using Rufus, Etcher, Disks and mkusb.

If I flash "dd_unb_ubuntu-20.04_15GB_2020-06-26.img.xz" using Rufus or Etcher, the USB works no problem, both BIOS and UEFI.

#978

C.S.Cameron said: @sudodus:

When flashed on Windows, using Rufus or Etcher or W32DI, BIOS partition is No1, EFI partition is No2.

Boots to "error: no such partition. / Entering rescue mode.../grub rescue>"

Added NTFS partition and ubuntu.iso, still boots to "error: no such filesystem. / Entering rescue mode.../grub rescue>"

When flashed to USB on Ubuntu using mkusb, BIOS partition is now No2, EFI partition is No3. Why?

Mkusb drive boots to menu in BIOS and UEFI modes no errors.

Added NTFS partition and ubuntu.iso to mkusb drive boots Ubuntu Live in BIOS and UEFI as expected.

I am perplexed, As you say, the cloned drives should be identical no matter what flashed them.

If I create a new image from the working mkusb drive above using Disks, the restored clone works if made using Rufus, Etcher, Disks and mkusb.

If I flash "dd_unb_ubuntu-20.04_15GB_2020-06-26.img.xz" using Rufus or Etcher, the USB works no problem, both BIOS and UEFI.

I can only draw the conclusion that Windows thinks it is smart and wants to help us. But it is not smart enough. instead of pure cloning, it discovers that there is no partition #1 and therefore re-numbers the partitions, which we don't want at all. (It happens with all the tools you try in Windows, and I don't think all the tools would be programmed to do it, hence I blame Windows for this extra action. (In Swedish we use the term *björntjänst* (bear's service) for such unwanted 'helpful' actions. Maybe *disservice* is the correct term in English.)

If this conclusion is correct, a solution would be to modify the partition numbering in the template, and to modify the content of the grub configuration (not only grub.cfg) to match the new partition structure. This may take some time. Another solution would be to add a partition #1 into the current template. This is more like a quick fix, but might work too.

#979

I was thinking maybe a small ext4 partition and a small NTFS partition. They could be expanded as necessary. Partition 1 could be the traditional NTFS usbdata partition. ISO files can be stored on either, or the ext4 partition could be relabeled as casper-rw/writable, or it could be reformatted as FAT32 for use by multiboot persistent-path folders.

#980

@C.S.Cameron,

[B]Will these new templates

[s]dd_grub-boot-template-for-uefi-n-bios_ext4_3.5GB.img.xz

dd_grub-boot-template-for-uefi-n-bios_ntfs_3.5GB.img.xz[/s]

work for you in UEFI mode also when you create boot drives from them in Windows?[/B]

Check with

[s]dd_grub-boot-template-for-uefi-n-bios_filesys_3.5GB.img.xz.md5[/s]


$ md5sum -c dd_grub-boot-template-for-uefi-n-bios_filesys_3.5GB.img.xz.md5
dd_grub-boot-template-for-uefi-n-bios_ext4_3.5GB.img.xz: OK
dd_grub-boot-template-for-uefi-n-bios_ntfs_3.5GB.img.xz: OK

$ ls -lh dd_grub-boot-template-for-uefi-n-bios_*_3.5GB.img.xz
-rw-r--r-- 1 sudodus sudodus 3,1M aug  3 16:50 dd_grub-boot-template-for-uefi-n-bios_ext4_3.5GB.img.xz
-rw-r--r-- 1 sudodus sudodus 3,2M aug  3 17:12 dd_grub-boot-template-for-uefi-n-bios_ntfs_3.5GB.img.xz

These compressed files contain a 'partition #1' either with ext4 or NTFS. For me ext4 works better with 'grub-n-iso'. The drive with NTFS gets stuck at shutdown (but works during the operation).

  • A live (live-only) system can be created in a 4 GB pendrive or memory card,
  • a persistent live system needs at least 8 GB and
  • an installed system needs at least a 16 GB pendrive or memory card.

If the user wants to install an operating system, and the drive is big enough, it can be a good idea to keep an NTFS partition to exchange files with Windows. The operating system can be installed into a new partition that is created in the unallocated drive space.

If the user want a persistent live system, I suggest that partition #1 has the ext4 file system. A partition for persistence can be created in the unallocated drive space, and the file system can be ext2 (less wear) or ext4 (more stable due to journaling).


$ lsblk -fm /dev/sd[cd]
NAME   FSTYPE LABEL     UUID                                 MOUNTPOINT                 SIZE OWNER GROUP MODE
sdc                                                                                    29,5G root  disk  brw-rw----
&#9500;&#9472;sdc1 [COLOR="#cc0000"]ext4[/COLOR]   modify-me b60b12f7-5b75-4922-ac96-331f3b309772 /media/sudodus/modify-me     3G root  disk  brw-rw----
&#9500;&#9472;sdc2                                                                                  977K root  disk  brw-rw----
&#9492;&#9472;sdc3 vfat   usbboot   02D3-7915                                                     244,1M root  disk  brw-rw----
sdd                                                                                     7,4G root  disk  brw-rw----
&#9500;&#9472;sdd1 [COLOR="#cc0000"]ntfs[/COLOR]   MODIFY-ME 61C3CA6C0D30D421                     /media/sudodus/MODIFY-ME     3G root  disk  brw-rw----
&#9500;&#9472;sdd2                                                                                  977K root  disk  brw-rw----
&#9492;&#9472;sdd3 vfat   usbboot   02D3-7915                                                     244,1M root  disk  brw-rw----
#981

@sudodus: Both ext4 and NTFS versions worked for me in Win 10 using Rufus and Etcher. However Both had a blinking curser when quitting. Hitting Esc exits the splash screen so we can see what is happenig. I tried something a little different and just made the ext4 and NTFS partitions 1MB each. This seems pretty versatile when modifying the partitions. I got a notice in GParted about EFI problems that I figure were what you mentioned efi-fix was about.

[ATTACH=CONFIG]286598[/ATTACH][ATTACH=CONFIG]286600[/ATTACH][ATTACH=CONFIG]286599[/ATTACH]

#982

C.S.Cameron said: @sudodus:

Both ext4 and NTFS versions worked for me in Win 10 using Rufus and Etcher. However Both had a blinking curser when quitting.

i don't get any problem, except when running 'grub-n-iso' with the iso file in an NTFS file system. (It shuts down nicely when the iso file resides in an ext4 file system.)

Please explain what you were running and how you quit, when you had that blinking cursor.

Hitting Esc exits the splash screen so we can see what is happening. Yes.> I tried something a little different and just made the ext4 and NTFS partitions 1MB each. This seems pretty versatile when modifying the partitions.

If I understand correctly, you would prefer a template with

  • partition #1: size 1 MB, NTFS
  • partition #4: size 1 MB, ext4

A drive made from this template cannot be used as is, those partitions must be modifed, at least the size, maybe also to another file system. For example, the default grub.cfg points to a file 'ubuntu.iso' in partition #1, and that works best with ext4 (in partition #1). So this is not my favourite template. But you have reasons to want it this way, and *I can create and upload such a template for you and for end users, who follow your advice* here at the Ubuntu Forums and at AskUbuntu.

I got a notice in GParted about EFI problems that I figure were what you mentioned efi-fix was about.

[ATTACH=CONFIG]286598[/ATTACH][ATTACH=CONFIG]286600[/ATTACH][ATTACH=CONFIG]286599[/ATTACH] Yes, that is the idea with 'gpt-fix'. gparted can fix it too, but maybe only when the drive is bigger than the original one.

#983

@C.S.Cameron,

[s]Will this new template

dd_grub-boot-template-for-uefi-n-bios_CSC_1GB.img.xz

work for you to help people create USB systems (installed and/or grub-n-iso ...)?

[hr][/hr] Check the download with

dd_grub-boot-template-for-uefi-n-bios_CSC_1GB.img.xz.md5[/s]


$ md5sum -c dd_grub-boot-template-for-uefi-n-bios_CSC_1GB.img.xz.md5
dd_grub-boot-template-for-uefi-n-bios_CSC_1GB.img.xz: OK

$ ls -l dd_grub-boot-template-for-uefi-n-bios_CSC_1GB.img.xz*
-rw-r--r-- 1 sudodus sudodus 2850876  4 aug 11.57 dd_grub-boot-template-for-uefi-n-bios_CSC_1GB.img.xz
-rw-r--r-- 1 sudodus sudodus      87  4 aug 12.48 dd_grub-boot-template-for-uefi-n-bios_CSC_1GB.img.xz.md5

$ lsblk -fm /dev/sdc
NAME        FSTYPE LABEL           UUID                                 MOUNTPOINT               SIZE OWNER GROUP MODE
sdc                                                                                             1006M root  disk  brw-rw----
&#9500;&#9472;sdc1      ntfs   usbdata         3379F00E4AF983B6                     /media/sudodus/usbdata     2M root  disk  brw-rw----
&#9500;&#9472;sdc2                                                                                           977K root  disk  brw-rw----
&#9500;&#9472;sdc3      vfat   usbboot         02D3-7915                                                   244,1M root  disk  brw-rw----
&#9492;&#9472;sdc4      ext4   root            47c14817-7db6-4323-8f78-bbc8872079e3 /media/sudodus/root        1M root  disk  brw-rw----
$

I created partitions #1 and #4 with gparted and made a compressed image.

#984

Please excuse the delay in my reply.

dd_grub-boot-template-for-uefi-n-bios_ntfs_3.5GB.img USB was not recognized when plugged into either Win10 computer. USB was accessible after changing file system from NTFS to FAT32.

dd_grub-boot-template-for-uefi-n-bios_CSC_GB.img Drives shows in File manager, but both Win10's says "E:\ is not accessible / insufficient system resources..." USB was accessible after changing file system from NTFS to FAT3

If I create GPT partition table with NTFS filesystem using GParted, drive is recognized in Win10.

NTFS usbdata partition on Persistent drive made with mkusb is accessible by Windows 10.

I am confused.

#985

@C.S.Cameron,

I think it can be difficult to get a template that is small and at the same time works well with Windows. But it might be worthwhile to keep trying.

My questions for this kind of template to work with your detailed instructions:

  • What is necessary?
  • What would be nice?
  • What cannot be accepted?
  • As it is now, there are a few versions of this template at phillw.net. Which of them is closest to what you want?
#986

Sudodus: I've run dozens and dozens of template installs using Rufus and Etcher the last few days, looking for a little enlightenment. Have not come to a firm conclusion yet.

  • What is necessary? Ability to create using Windows alone.
  • What would be nice? The least effort as possible.
  • What cannot be accepted? Perhaps instability?

So far NTFS does not seem to be working with Windows and has problems shutting down.

Fat32 shuts down quickly and can be used by Windows. It can also be used for ISO files and persistent files and persistent-path folders. I think it is more stable than NTFS. But who knows how quickly Ubuntu / Linux files will hit the 4GB threshold? A ISO booting USB with FAT32 can also be created on an Apple computer.

An ext4 partition would be nice, (maybe necessary), for Linux people and for a persistent partition if desired.

Please make one more template file with a 1MB ext4 partition / placeholder next to the boot partition and a 1MB FAT32 partition / placeholder on its right.

#987

@C.S.Cameron,

Finally I tested in Windows. The kind of template that you asked for as well as the other current versions do not work. For some reason Windows does not want to modify partitions, that I created in Linux. So it is no use to upload a drive with a minimal FAT32 partition.

Instead there is a major makeover. I modified the numbering in the partition table of the two partitions for booting:


sda2 --> sda1
sda3 --> sda2

and modified the grub bootloaders to work correctly.

[B]Will this new template 'only-p1p2' <--> 'only partition #1 and partition #2',

dd_grub-boot-template-for-uefi-n-bios_only-p1p2.img.xz

work for you to help people create USB systems (installed and/or grub-n-iso ...)?[/B]

[hr][/hr] Check the download with

grub-boot-templates-for-uefi-n-bios.md5


$ ls -l dd_grub-boot-template-for-uefi-n-bios_only-p1p2.img.xz*
-rw-r--r-- 1 root root 3681860 aug  8 17:18 dd_grub-boot-template-for-uefi-n-bios_only-p1p2.img.xz
-rw-r--r-- 1 root root      89 aug  8 18:10 dd_grub-boot-template-for-uefi-n-bios_only-p1p2.img.xz.md5

$ lsblk -fm /dev/sdc
NAME   FSTYPE LABEL   UUID                                 MOUNTPOINT   SIZE OWNER GROUP MODE
sdc                                                                    1006M root  disk  brw-rw----
&#9500;&#9472;sdc1                                                                  977K root  disk  brw-rw----
&#9492;&#9472;sdc2 vfat   usbboot 02D3-7915                                       244,1M root  disk  brw-rw----

As it is now, you can create a new partition in Windows, and if you select FAT32, it will work as an isodevice (where you have the iso file(s)). Of course, in Linux it is better to use ext4.

You can add another partition, select ext4 and the label 'writable' for persistence, or the label 'usbdata' and NTFS for storage and exchange of data with [current versions of] Window 10.

I did some testing and I think it works now, both in UEFI mode and BIOS mode. But I have not tested everything, that you might do with this template, so *I'm looking forward to the result of your tests* :-P

#988

@sudodus

I have also given up trying to get micro partitions to work in an image file for use by Windows 10.

I have had good luck making an ISO booting USB totally in Windows 10 using the latest Template image:

  • Open Windows Disk Management.
  • Select unallocated disk space on USB.
  • Select "New Single Volume"
  • Specify space required. Leave some unallocated space if using ext4 Persistent partition.
  • Use default drive letter.
  • Make FAT32, (NTFS also works but does not shut down).
  • Copy Ubuntu ISO file to new partition. Rename to "ubuntu.iso".
  • If using Persistence file(s) add to root of new partition. If using multi persistence, add Persistence file(s) to uniquely named folders. Persistence files must go on FAT32 partition.
  • Boot USB.
  • If using persistent partition, open GParted and create New ext4 partition in remaining unallocated space, label it "casper-rw" or "writable". If using a home-rw persistent partition create another ext4 partition and label it home-rw.
#989

C.S.Cameron said: @sudodus

I have had good luck making an ISO booting USB totally in Windows 10 using the latest Template image:

Finally something that works also in Windows :-)

Q1: What about the name of the template. Would you like to suggest a suitable name for it (or are you happy with the current name)?

Q2: Should we keep also one of the old templates to be managed in Linux for cases where the user might want to share data with older versions of Windows, and 'usbdata' must be partition #1 (or is it enough with one single template, that works with Linux and the current version of Windows 10)?

#990

The current name is not bad, only some users might be concerned about the "dd_" part of it. Replacing dd with mkusb might give it some cred. Making bios_grub and boot,efi partitions to 1 & 2 is I think necessary for consistency. p1p2 may not be needed in the name. "mkusb-grub-boot-template-for-uefi-n-bios.img.xz" sort of has a nice ring to it.

I think that if the image is flashed to USB in Windows the original partition numbering does not matter. Numbering appears to be based on the partitions actually on the disk at the time. However if the image is flashed in Linux with mkusb or disks the original order is kept. Then I think the new FAT32 partition can be number one, to suit older Windows. NTFS still can't be seen by Windows 10. ie dd_grub-boot-template-for-uefi-n-bios_ntfs_3.5GB.img.xz had the partitions in the right order, (NTFS No1), in Windows Disk Manager, but the NTFS partition can't be seen in Windows Files.

Giving it some thought,I think an image just like the NTFS one but with FAT32 file system would work with older Windows. I will try to find my XP virtual machine and check.

#991

@C.S.Cameron,

This sounds good. I'll wait for your result with an image just like the NTFS one but with FAT32 file system would work with older Windows (your XP virtual machine).

#992

I found my 32bit Windows XP VM. took me about an hour to figure out XP does not like GPT, Duh. Now to find a Win 7 VM...

#993

@C.S.Cameron,

Maybe we can say that people who still run Window XP , Windows 7 and Windows 8 can go via an Ubuntu [persistent] live drive and install mkusb (which can create an MSDOS partition table as an alternative to the standard GPT).

Then we can focus on people who run Windows 10 for our template.

#994

@sudodus:

Yea, but people still running Windows XP probably need to try Ubuntu the most. They can start with a Rufus or UNetbootin persistent install and work their way up from there, next stop mkusb, then the world.

I tried a USB with "dd_grub-boot-template-for-uefi-n-bios_ntfs_3.5GB.img.xz" installed, on a Windows 7 VM.

Windows 7 File Manager could not see the NTFS partition, (Disk Manager could see it, but could not do anything with it).

I reformatted the NTFS partition to FAT32 and the partition was accessible. I copied Ubuntu 20.04 ISO to it, working in windows 7. I added a "casper-rw" file and renamed it "writable".

[B]The USB boots right up and is persistent. [/B]

#995

@C.S.Cameron

Good result with Windows 7 :-)

  1. Did you reformat to FAT32 in Ubuntu?
  1. Did you try the same in Windows 10 (copy Ubuntu 20.04 ISO to the FAT32 partition, and try booting from the drive)? In other words, are Windows 7 and Windows treating a drive made from the 3.5GB template in the same way, or not?
  1. Finally, do you want me to upload a corresponding 3.5GB template with FAT32 in partition #1? In that case, *what size should it occupy?* Slightly less than 4GB or slightly less than 8 GB (slightly less in order for it to work with drives that might be 'undersized'; the size of several USB pendrives and memory cards is not quite as big as the nominal size, for example 3.9GB or 7.8GB.)
#996

@sudodus The .xz size of the image that includes a 3.5B FAT32 or NTFS partition one is not much larger than the .xz without it. (but takes a little longer to flash, which is not a big deal).

1) Yes, But I am hoping the image will come with FAT32 off the shelf.

2) Yes I think so. Both worked with the original image file okay. The EliteBook Windows 10 seems to be having a bit of difficulty booting the drive made with Windows 7*. The Gigabyte computer is not having a problem at all, but it uses UEFI.

3) Yes please. 3.5GB seems to be the right size, (but I am probably the last person on earth using something that small). It is easy to enlarge the partition.

*Seems to be working okay now though.

#997

@C.S.Cameron,

Edit: The set of 'mkusb_grub-boot-template-for-uefi-n-bios' files has been edited, and the current set is shown in post #999 [hr][/hr] I tried to listen to what you want: modified the names and created a new template with an FAT32 file system in partition #1.

You found these templates at https://**phillw.net/isos/linux-tools/uefi-n-bios**/?C=N;O=D

[s]- mkusb_grub-boot-template-for-uefi-n-bios_**use-in-ubuntu**.img.xz

and the md5sums in the file mkusb_grub-boot-templates-for-uefi-n-bios.md5[/s]


$ ls -trl mkusb_grub-boot-template*
-rw-r--r--. 1 nio nio 2768416  4 jun 10.05 mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz
-rw-r--r--. 1 nio nio 3681860  8 aug 17.18 mkusb_grub-boot-template-for-uefi-n-bios_use-in-windows.img.xz
-rw-r--r--. 1 nio nio 3313020 11 aug 15.25 mkusb_grub-boot-template-for-uefi-n-bios_fat32_3.5GB_use-in-windows.img.xz
-rw-r--r--. 1 nio nio 3331492 11 aug 22.47 mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz
-rw-r--r--. 1 nio nio     409 11 aug 23.42 mkusb_grub-boot-templates-for-uefi-n-bios.md5

$ md5sum -c mkusb_grub-boot-templates-for-uefi-n-bios.md5
mkusb_grub-boot-template-for-uefi-n-bios_fat32_3.5GB_use-in-windows.img.xz: OK
mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz: OK
mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz: OK
mkusb_grub-boot-template-for-uefi-n-bios_use-in-windows.img.xz: OK

$ lsblk -fm /dev/sdc
NAME   FSTYPE LABEL     UUID                                 MOUNTPOINT             SIZE OWNER GROUP MODE
sdc                                                                                14,6G root  disk  brw-rw----
&#9500;&#9472;sdc1 vfat   ISODEVICE D39A-66D7                            /media/nio/ISODEVICE   3,4G root  disk  brw-rw----
&#9500;&#9472;sdc2                                                                                1M root  disk  brw-rw----
&#9500;&#9472;sdc3 vfat   usbboot   02D3-7915                                                   245M root  disk  brw-rw----
&#9492;&#9472;sdc4 ext4   writable  edd959eb-b3db-4bd1-8c5d-cc2e4c3d0877                         11G root  disk  brw-rw----

I think this palette with templates should provide working solutions for most cases, where you want to use templates to create a grub-n-iso (isoboot) system or an installed system in an external drive (USB pendrive, memory card, external SSD or HDD via USB or eSATA).

Please test that the templates work for you.

Edit 1: I tested again, and this time Windows 10 could not use the template with a FAT32 partition (in particular, could not see the FAT32 partition, hence not put any iso file into it :(

I don't know why it worked the first time but not after that - I tried to reboot, but it did not help. If you can use it in Windows 7, fine, otherwise I think it is better to remove this template, because I don't see how it can be used, where the other templates don't work.

Edit 2: I created a new template file for old Windows, that see only partition #1. I made it slightly bigger too, but still with some margin smaller than the standard nominal size 4 GB.

This time the partition is not only number 1, but also located at the head of the drive, before the other partitions. There is still a problem that Windows refuses to edit it, but Windows can to copy a file into it. So we can provide [FONT=Courier New]ubuntu.iso[/FONT] and get a successful grub-n-iso boot drive, that works both in UEFI mode and BIOS mode.

I think this file


mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz

should work for you in old versions of Windows. But I have only tested it in Windows 10, so I am looking forward to your test result :-P

#998

Thanks Sudodus That should keep me entertained for a while.

#999

Sudodus:

mkusb_grub-boot-template-for-uefi-n-bios_fat32_3.5GB_use-in-windows.img.xz was flashed using Rufus. Apparently Etcher does not like Linux ISO's with Windows in the name. It wants to treat them as Windows ISO's. After changing the word "windows" to "wins" it worked in Etcher also..The resulting USB was not accessible in Windows 7 or 10, except by Rufus and Windows Disk Manager, WDM was not able to fix it. *

mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz worked great for me using Rufus. Easy and quick way to make an ISO booter. The USB was accessible in both Windows 7 and 10. After changing the word "windows" to "wins" it worked in Etcher also. I made a working Ubuntu ISO booter on Windows 7 using the image. Funny thing is the .xz file worked in Rufus even though I could not find 7zip installed on the VM? I wonder if a similar Template would work with a NTFS partition?. The Template did not work for me in Etcher on a 4B drive even renamed to "wins". I think Etcher thought it is too big for my 4GB USB. Rufus managed to squeeze it onto the same 4GB USB.

mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz made a drive that was visible to Windows Disk Manager and I was able to add a NTFS partition, but it would not completely shut down.This image mostly worked in a Windows 7 but not able to format unallocated space. Only Rufus could see it. The 4GB Template version with a FAT32 partition included, saved a step over this version.

mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz worked great using mkusb to flash the USB. It did not work using Gnome-Disks. I created a FAT32 partition using GParted that was visible in Windows 10 but not in 7. I changed the drive letter using WDM and it became usable in Windows 7. I should also mention that the fat32_4GB_use-in-windows.img also worked with mkusb and also worked with Gnome-Disks and was usable in Windows 10 and in 7 without changing drive letter..

If I was marooned on a jungle island, somewhere in the Indian ocean and could only have one of the above I would pick "mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz". My second choice would be the bios_use-in-ubuntu.img.xz.

  • I'm not sure how reproducible my results are. I could have sworn that the first time I ran the 3.5GB Template it worked okay. I have run the 4GB template a dozen times today with consistent results.
#1000

C.S.Cameron said:

mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz made a drive that was visible to Windows Disk Manager and I was able to add a NTFS partition, but it would not completely shut down.This image mostly worked in a Windows 7 but not able to format unallocated space. Only Rufus could see it. The 4GB Template version with a FAT32 partition included, saved a step over this version.

mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz worked great using mkusb to flash the USB. It did not work using Gnome-Disks. I created a FAT32 partition using GParted that was visible in Windows 10 but not in 7. I changed the drive letter using WDM and it became usable in Windows 7. I should also mention that the fat32_4GB_use-in-windows.img also worked with mkusb and also worked with Gnome-Disks and was usable in Windows 10 and in 7 without changing drive letter..

Thanks for these detailed tests.

Question: Are you talking about the same template in the above paragraphs, or is one of them about

[FONT=Courier New]mkusb_grub-boot-template-for-uefi-n-bios_use-in-windows.img.xz[/FONT]

(renamed from [FONT=Courier New]dd_grub-boot-template-for-uefi-n-bios_only-p1p2.img.xz[/FONT]) ?

[hr][/hr] Comment: I will check the problem, when using Gnome-Disks.

Edit: with [FONT=Courier New]mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz[/FONT] and Gnome-Disks, the drive needs also treatment with gpt-fix in order to work (this treatment is built into mkusb-dus). I can try to reduce this problem (so that gpt-fix is no longer necessary).

So it is easier to use [FONT=Courier New]mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz[/FONT], but the FAT32 partition is at the drive's head end so its size is difficult to increase, which is a disadvantage. But I understand that you prefer it anyway, because when you consider the general performance, it is best among the tested templates.

#1001

I made a new version of [FONT=Courier New]mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz[/FONT]

mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz mkusb_grub-boot-template-for-uefi-n-bios_use-in-wins.img.xz

with the md5sums in

Check the download with

grub-boot-templates-for-uefi-n-bios.md5

This 'use in Ubuntu' file behaves better in my tests when clonied with Gnome-Disks. Please test how it works in Windows 7 and 10 for you.

I also renamed the files to make Etcher accept them.


$ l -tr mkusb_grub-boot-template*
-rw-r--r-- 1 nio nio 3681860  8 aug 17.18 mkusb_grub-boot-template-for-uefi-n-bios_use-in-wins.img.xz
-rw-r--r-- 1 nio nio 3331492 11 aug 22.47 mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz
-rw-r--r-- 1 nio nio 2768936 14 aug 16.03 mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz

Edit: I should add to "This 'use in Ubuntu' template file behaves better in my tests when cloned with Gnome-Disks." that I

  • cloned with Gnome-Disks and then
  • used Gparted to create a FAT32 partition and
  • let Gparted do the fix that it wants to do (somewhat corresponding to 'gpt-fix').

This will become partition #1, located behind the boot partitions, so it is not limited in size. It looks good in Windows 10, and I am looking forward to your test in Windows 7, where I hope you can use it, for example to read and write files.

#1002

sudodus said:

Question: Are you talking about the same template in the above paragraphs, or is one of them about

Oops, looks like a copy paste error, The first paragraph should have been for the Windows Template, the next paragraph was correctly about the Ubuntu one. I did not find much difference between them.

So it is easier to use [FONT=Courier New]mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz[/FONT], but the FAT32 partition is at the drive's head end so its size is difficult to increase, which is a disadvantage. But I understand that you prefer it anyway, because when you consider the general performance, it is best among the tested templates.

Yes, I think for casual use I would use fat32_4GB_use-in-wins.img, but I don't want to be too hasty. Will confirm after I have given it a bit more thought.

#1003

After giving the matter a little more thought:

mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz creates a drive with a 4GB Fat 32 partition visible to Windows 10 and Windows 7, Linux and IOS.

Windows Disk Manager and GParted can be used to turn the unformatted space on a larger USB into a FAT32 or NTFS partition that can be seen by Windows 10 or Linux. GParted can be used to turn it into a stable ext partition for use by Linux.

Booting the USB flash drive to Ubuntu using toram, I was able to unmount the USB using "sudo umount -lrf /isodevice" and in GParted move the boot partitions to the right and expand the 4GB FAT32 partition to use all the extra space. (Do not forget to leave 1MB of free space to the right of the EFI partition). The resulting drives FAT32 partition was accessible in both Windows 7 and 10 as long as it was number one and on the far left side.

The '4GB_use-in-windows.img can be used to make an ISO booting USB of any complexity, that can be used in BIOS mode and UEFI mode computers. It can also serve as a foundation for a Full install drive and many other bootable USB projects.

I am a little confused about why the FAT32 partition has been wanting to be on the left side of WDM and GParted. I do not ever recall mkusb's usbdata partition having trouble in Windows 7?

#1004

C.S.Cameron said: After giving the matter a little more thought:

mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz creates a drive with a 4GB Fat 32 partition visible to Windows 10 and Windows 7, Linux and IOS.

Windows Disk Manager and GParted can be used to turn the unformatted space on a larger USB into a FAT32 or NTFS partition that can be seen by Windows 10 or Linux. GParted can be used to turn it into a stable ext partition for use by Linux.

Booting the USB flash drive to Ubuntu using toram, I was able to unmount the USB using "sudo umount -lrf /isodevice" and in GParted move the boot partitions to the right and expand the 4GB FAT32 partition to use all the extra space. (Do not forget to leave 1MB of free space to the right of the EFI partition). The resulting drives FAT32 partition was accessible in both Windows 7 and 10 as long as it was number one and on the far left side.

The '4GB_use-in-windows.img can be used to make an ISO booting USB of any complexity, that can be used in BIOS mode and UEFI mode computers. It can also serve as a foundation for a Full install drive and many other bootable USB projects.

Am i understanding correctly, that you need only one of these templates,

mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz

and for that purpose we might rename it (by removing 'use-in-wins')?

I am a little confused about why the FAT32 partition has been wanting to be on the left side of WDM and GParted. I do not ever recall mkusb's usbdata partition having trouble in Windows 7?

  • It might make a difference, that mkusb creates the partition table directly onto the USB drive, while the template almost always has a mismatch concerning the size of the drive.
  • Windows 10 has changed the treatment of USB drives, for example can use more than the first partition now. It is possible that the treatment of USB drives has changed in other ways too, for example that it is less tolerant to partitions and file systems created by other operating systems, that may not be 100% identical to what it 'expects' or 'wants'.
  • It is also possible that Linux its tools (for example Gparted) have changed, so that the current versions do not create exactly the same partition tables and file systems as they did some years ago.
#1005

sudodus said: Am i understanding correctly, that you need only one of these templates,

mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz

and for that purpose we might rename it (by removing 'use-in-wins')?

I would like to see at least the original Template dd_grub-boot-template-for-uefi-n-bios.img.xz and the new Template mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz remain available.

The original Template has been mentioned quite a few times in Ask Ubuntu.

The only that I am a little uneasy about is that 4GB_use-in-wins.img was not working on my 4GB drive in Etcher. I would not doubt that I am the only person left with a working 4GB USB2 drive.

#1006

C.S.Cameron said: I would like to see at least the original Template dd_grub-boot-template-for-uefi-n-bios.img.xz and the new Template mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz remain available.

The original Template has been mentioned quite a few times in Ask Ubuntu.

OK

The only that I am a little uneasy about is that 4GB_use-in-wins.img was not working on my 4GB drive in Etcher. I would not doubt that I am the only person left with a working 4GB USB2 drive.

What 's the exact size of that drive, which is nominally 4 GB?

The template should work in a drive size >= 3965190144 bytes (~ 3965 MB, 10-base)


$ LANG=C [COLOR="#0000CD"]**sudo parted /dev/sdd p**[/COLOR]
Model: Generic- USB3.0 CRW -SD (scsi)
Disk /dev/sdd: 3965MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  3640MB  3639MB  fat32              msftdata
 2      3640MB  3641MB  1049kB                     bios_grub
 3      3641MB  3898MB  257MB   fat32              boot, esp

$ LANG=C [COLOR="#0000CD"]**sudo parted /dev/sdd u b p**[/COLOR]
Model: Generic- USB3.0 CRW -SD (scsi)
Disk /dev/sdd: 3965190144B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start        End          Size         File system  Name  Flags
 1      1048576B     3639607295B  3638558720B  fat32              msftdata
 2      3639607296B  3640655871B  1048576B                        bios_grub
 3      3640655872B  3897556991B  256901120B   fat32              boot, esp

#1007

One is: cscameron@cscameron-T:~$ lsblk -b --output SIZE -n -d /dev/sdb 4022337536 The other is: cscameron@cscameron-T:~$ lsblk -b --output SIZE -n -d /dev/sdc 4007657472

Must be a flaw in Etcher, or my computer.

#1008

@ C.S.Cameron,

I would also think that the problem is in Etcher. You could double-check that it works with Rufus and with {7-zip + Win32DiskImager} with these pendrives.

#1009

Etcher worked with the 4GB .img after extracting it from the .xz. The 3.5GB .xz worked fine as is? At least now I know what works.

#1010

@ C.S.Cameron,

Your result indicates that Etcher needs some margin (between the size of the image and the size of the target drive) for {extraction + cloning} to work (or be accepted). Can you live with


mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz

as it is now (made from a drive with 3965190144 bytes (~ 3965 MB, 10-base) and expanding to a drive with at least the same size)?

#1011

Yes thank you sudodus. It is not so difficult to extract the .img file before using Etcher. It is probably better to use Rufus when working in Windows.

#1012

I did some housecleaning of the templates in the web directory for UEFI and BIOS files,

**[https://phillw.net/isos/linux-tools/uefi-n-bios/**](https://phillw.net/isos/linux-tools/uefi-n-bios/)

and created a new md5sum file for the remaining templates,


grub-boot-templates-for-uefi-n-bios.md5

The following files are there now (with some 'doublets' to allow for old links to work)


$ls -l *templ*
-rw-r--r-- 1 nio nio 2735732  2 jun 17.26 dd_grub-boot-template-for-uefi-n-bios_bright-bg.img.xz
-rw-r--r-- 1 nio nio 2768936 14 aug 16.03 dd_grub-boot-template-for-uefi-n-bios_dark-bg.img.xz
-rw-r--r-- 1 nio nio 2768416  4 jun 10.05 dd_grub-boot-template-for-uefi-n-bios.img.xz
-rw-r--r-- 1 nio nio 2768936  2 aug 15.59 dd_grub-boot-template-for-uefi-n-bios_new.img.xz
-rw-r--r-- 1 nio nio 3681860  8 aug 17.18 dd_grub-boot-template-for-uefi-n-bios_only-p1p2.img.xz
-rw-rw-r-- 1 nio nio     721 19 aug 15.08 grub-boot-templates-for-uefi-n-bios.md5
-rw-r--r-- 1 nio nio 3331492 11 aug 22.47 mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz
-rw-r--r-- 1 nio nio 2768936 14 aug 16.03 mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz
-rw-r--r-- 1 nio nio 3681860  8 aug 17.18 mkusb_grub-boot-template-for-uefi-n-bios_use-in-wins.img.xz

if I understand correctly,. @C.S.Cameron prefers to use the following two files,


mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz  # in Windows

dd_grub-boot-template-for-uefi-n-bios.img.xz  # in Ubuntu

I think that


mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz  # in Ubuntu

should be best in Ubuntu, because it works also with Gnome-Disks and small USB drives (>= 1 GB). But it may need some testing to check that there are no regressions for other cases.

#1013

Yes thank you sudodus. It is not so difficult to extract the .img file before using Etcher. It is probably better to use Rufus when working in Windows.

#1014

[SIZE=4]mkusb version 12.5.9, 12.6.0, 12.6.1 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. dus-live: mkcmd_runcmd: size also when cloning from block device . watch-flush: fix if dirtorig = 0 to avoid division by zero

  • mkusb 12.5.9

. dus-persistent: grub-n-iso: --no-same-owner added to tar command .. tar -xf "$mkusb_sdir"/usb-pack_efi.tar.xz --directory "$targ1" . To make 'usb-pack-efi' work with secure boot with fix for the boothole bug there are new versions of the files .. usb-pack_efi-2.02.tar.xz .. usb-pack_efi-2.04.tar.xz

  • mkusb 12.6.0

.. If grubimg, do not extract from usb-pack_efi.tar.xz .. use the same image as grub-2.02.img.xz and grub-2.04.img.xz .. (not now, maybe later simplify the logic for grubimg) .. A set of tests indicate, that this version works also with secure boot taking care of the fix to squash the boothole bug. [/td][/tr][/table]

  • mkusb 12.6.1

[SIZE=3]Improvement in version 12.5.9 [/SIZE]

Minor bugfix to show progress including flushing the buffers also when cloning from block device

[SIZE=3]Improvement in version 12.6.0, 12.6.1 [/SIZE]

Major improvement to make mkusb-dus work with secure boot with fix for the boothole bug via 'usb-pack-efi'

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.5.8 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1015

Minor problem with mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz I am unable to resize the ESP partition.

#1016

C.S.Cameron said: Minor problem with mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-windows.img.xz

I am unable to resize the ESP partition.

  1. Are you talking about this file:

$ ls -l mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz
-rw-r--r-- 1 root root 3331492 aug 11 22:47 mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz

$ md5sum mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz
f13fc267e60401a883193005983e7709  mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz
  1. Why do you want to resize the ESP partition?
  1. What tool do you use?
  1. What is the error output or symptom?
#1017

Yes that is the file. Oops, it looks like this is normal with the template images. The FAT32 boot partition can be moved, but it can not be expanded or contracted, at least the usable space can not be expanded or contracted. ie in GParted the overall size of the partition can be expanded, but the Used space plus the Unused space remain the same. The original space is white and the new space is grey. I have not been able to shrink the overall size once expanded. I have never noticed this before.

Sorry, this sounds pretty confusing, I have just been trying to boot groovy ISO files in UEFI and have not had much luck.

#1018

@C.S.Cameron,

Thanks for the details.

  1. Yes, I can confirm that gparted cannot change the size of [the FAT file system in] the ESP partition.
  1. I tested with a fresh partition with FAT32 in a GUID partition table (GPT). And gparted fails with that system too.
  1. I tested with a fresh partition with FAT32 in an MSDOS partition table (the old kind of partition table). In this case gparted *can* change the size.

It looks like a bug in gparted.

[HR][/HR] Now my questions are:

  • Why do you want to resize the ESP partition?
  • Is this important, so important, that I should create a template with an MSDOS partition table in order to work around this problem?
#1019

This template


mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz

worked for me with the Lubuntu Groovy daily iso file dated 2020-09-14.

Today I tested with the current daily Lubuntu Groovy dated 2020-09-20, and it works too, both in BIOS mode and UEFI mode. See the attached file.

#1020

Not so important. I was just doing some trial and error experimenting. This was just a curiosity I had never noticed before.

Both mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz and mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins_2020-09-07.img.xz are working for me in BIOS mode with groovy-desktop-amd64(200910).iso. In UEFI mode I either got the initramfs unpacking error or the skip to internal drive. I will try do download the latest daily tonight.

#1021

[SIZE=4]mkusb version 12.6.2, 12.6.3, 12.6.4 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. dus & dus-*; variable font and window size of zenity .. new function: p_zensize where msiz percent sets the size

. mkusb-plug: mkusb-sedd: puer, puer0: .. Workaround because of bug: .. https://bugs.launchpad.net/bugs/1895329

. added manual size for zenity font and window: p_zensize, .. new function p_zen_siz_select, new file "$HOME/.mkusb/fontsave", p_starter ... (new menu entry to manage the size of zenity windows and xterm console) .. dus-persistent & dus-home-backup: p_zensize .. mkusb-start & guidus.desktop: variable font in xterm [/td][/tr][/table]

  • mkusb 12.6.2
  • mkusb 12.6.3
  • mkusb 12.6.4

[SIZE=3]Improvement in version 12.6.2 [/SIZE]

Automatic logic in mkusb-dus to get a suitable text size and window size in high resolution screens, greater than 1920x1080.

Details about font size for high resolution: The default font in monitors with 2560x1440 or 3840x2160 pixels may be too small in Ubuntu Desktop and the Ubuntu family flavours.

In Ubuntu 20.04.x LTS with Gnome desktop environment you can use [FONT=Courier New]gnome-tweak-tool[/FONT] and increase the default fonts from 11 to 16, which should make things nice. This is matched by the automatic logic in mkusb-dus. (However, if you use the shortcut by the Ubuntu settings tool and set '200%', mkusb-dus will believe that the font is still too small, and make the windows (and font, that it can control) very large.)

[SIZE=3]Improvement in version 12.6.3 [/SIZE]

Workaround because of Bug #1895329: The partition for persistence with [FONT=Courier New]ext[/FONT] file system is created by mkusb-sedd in mkusb-plug (instead of expecting it to be created automatically as in Ubuntu 20.04.x LTS).

[SIZE=3]Improvement in version 12.6.4 [/SIZE]

In mkusb-dus version 12.6.4 control of font and window size for the xterm console is added and for zenity it is improved. If you use the the Ubuntu Settings tool and select 'Scale 200%', or 'Fractional scaling' the automatic logic of mkusb-dus will believe that the font is still too small, and make the zenity windows (and font, that it can control) very large.

In this case you can select 'manage Zenity window and font size' from the starter menu of dus (mkusb-dus), and then select 'Fixed size of zenity windows and fonts' from the submenu. You will probably be satisfied with the default font size, but you can increase the size if you wish.

There are more details at Font size for high resolution.

[hr][/hr] Unstable 1: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas, mkusb-plug)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.6.3 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1022

Mkusb Program Installer For installing programs without the need for internet.

Required:

Computer(s) with no Internet access, (Target computer).

Access to computer with Internet access.

USB drive.

Procedure:

  • Create a Persistent USB install using mkusb.
  • Install Synaptic on the USB. "sudo apt install synaptic".
  • Open "Software and Updates" / "Ubuntu Software" confirm everything checked except "Source code" and "Cdrom...", Close and Reload.
  • In Synaptic search for the program you want to install, select the main program and click "Mark for Installation" or "Mark for Complete Installation".
  • Open Files in Synaptic and click "Generate package download script". Save results in it's own folder as "newprogram.sh" where newprogram is the programs name. Do not press "Apply".
  • In Terminal cd to the newprogram folder and run "sudo chmod +x newprogram.sh" then run the script "./newprogram.sh". (This may create a bunch of .deb files inside the folder)
  • Boot the Target drive and copy the newprogram package folder to the Downloads folder of the Target drive.
  • In Terminal cd to the newprogram folder and run "sudo dpkg -i *".

The program and it's dependencies should now be installed.

#1023

@ C.S.Cameron,

Thanks for these instructions for installing programs to a computer without [an own connection to the] internet :-)

#1024

I'm doing a BIOS update, instructions at https://www.dell.com/support/article/en-uk/sln171755/update-the-dell-bios-in-a-linux-or-ubuntu-environment?lang=en . As it is an older computer (pre 2015) and I boot into Legacy mode (not UEFI) I'm following the steps at section 3 and 4 - https://www.dell.com/support/article/en-au/sln171755/update-the-dell-bios-in-a-linux-or-ubuntu-environment?lang=en#CreatingaUSBBootableStorageDevice

UNetbootin keeps on wanting me to 'mount' the USB, plus it doesn't give the option /dev/sdb1 , even though a mount command displays the usb mounted at /dev/sdb1

Can I simply use mkusb to correctly format the usb and then copy the BIOS as an EXE ??

#1025

So I used mkusb to do a live ISO of FreeDos, however cannot copy the EXE for the BIOS onto the usb, as it gives me a 'read only' errors. Have tried copying with 'sudo', same problems. The problem was that there was no room left on the ISO, plus permission errors. Any attempts to use 'UNetbootin' resulted in the usb drive not being detected, despite the fact a mount command showed that it was clearly mounted.

Installed isomaster, and added the EXE file to the ISO, then used mkusb to create a bootable ISO on the usb. It looks okay, the extra file is there now. Now to do the renoot and update the BIOS (gulp).

#1026

@oygle,

I'm glad you found a way to run FreeDOS. But I think there is an easier way:

Download [FONT=Courier New]FD12FULL.zip[/FONT] from

www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/

Extract it and use mkusb (mkusb-dus) directly on the image file to flash it to a USB pendrive,


unzip FD12FULL.zip
dus FD12FULL.img

[hr][/hr] I tested that it can boot my Dell Precision M4800 (in BIOS mode).

After booting I selected language and did not install it: selected 'No, return to DOS'. That way I had a running system booted from the USB drive.

There is a FAT16 file system, where you can add files, so when connected to a computer with Ubuntu or Windows, you can copy your EXE file into it, and then boot and update the BIOS.


$ LANG=C sudo parted /dev/sdc p
Model: JetFlash Transcend 8GB (scsi)
Disk /dev/sdc: 7902MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      32,3kB  537MB  537MB  primary  fat16        boot

If the free space is too small for the file(s) that you want to use, it should be possible to use [FONT=Courier New]FD12LITE.zip[/FONT] instead, which has only the most necessary tools. After increasing the size of the FAT16 partition to 511 MiB with [FONT=Courier New]gparted[/FONT], there will be lots of free space.

Another alternative is to create another FAT16 partition (not exceeding 512 MiB) to store the files.


$ lsblk -o name,fstype,label,size /dev/sdc
NAME   FSTYPE LABEL     SIZE
sdc                     7,4G
&#9500;&#9472;sdc1 vfat   FD-SETUP  512M
&#9492;&#9472;sdc2 vfat   STORAGE   511M

$ LANG=C sudo parted /dev/sdc p
Model: JetFlash Transcend 8GB (scsi)
Disk /dev/sdc: 7902MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 1      32,3kB  537MB   537MB  primary  fat16        boot
 2      537MB   1073MB  536MB  primary  fat16

FreeDOS will see the second partition as [FONT=Courier New]D:[/FONT]

#1027

@sudodus - This morning I tried several times to boot from the usb (after mkusb had made the ISO image on it), but everytime , it kept going into Kubuntu. This was despite the fact that I had 'boot from USB' as first boot priority. Then I felt to look here, and saw your post. Followed your instructions, added the Bios EXE file, rebooted, and this time the Bios menu had changed it it had boot from usb as an option on the first screen. Took that, followed your instructions, ran the Bios EXE and it has successfully done the Bios upgrade.

I tried the 'parted' command, the output is slightly diffeent to yours ..

$ LANG=C sudo parted /dev/sdb1 p

[sudo] password for oygle: Model: Unknown (unknown) Disk /dev/sdb1: 537MB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags:

Number Start End Size File system Flags 1 0.00B 537MB 537MB fat16

It is SO GOOD to have this done and it certainly was the easy way. Thank you, thank you @sudodus :D :D :D [IMG]https://media.giphy.com/media/6tHy8UAbv3zgs/giphy.gif[/IMG]

#1028

[SIZE=4]mkusb version 12.6.5, 12.6.6 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. dus-persistent: probe_source: usb-pack_efi auto-set for 20.10 . mkusb-plug: .. mkusb-sedd: puer, puer0: Workaround reverted ... (bug-fix for https://bugs.launchpad.net/bugs/1895329) .. srctst: Cannot to create data partition for version 20.10

  • mkusb 12.6.5

- mkusb 12.6.6 . dus-live: gpt_fix: added "-e 'Problem:'" to first grep command . mkusb-plug: .. mkusb-sedd: new functions gpt_fix, gpt_zap ... datp: using gpt_fix, gpt_zap (and partprobe) .. get_action and scrtst: no longer check to exclude 20.10 [/td][/tr][/table]

[SIZE=3]Improvement in version 12.6.5 [/SIZE]

  • dus-persistent: Auto-setting to use usb-pack_efi for Ubuntu 20.10 'Groovy'

. Again using the automatic creation of the ext4 partition to be used for persistence. . Exiting from the alternative to create a usbdata partition for Ubuntu Ubuntu 20.10 'Groovy' because it does not work. Suggesting to use mkusb-dus instead for this purpose.

  • mkusb-plug:

[SIZE=3]Improvement in version 12.6.6 [/SIZE]

  • mkusb-plug: Because of the GPT in Groovy iso files, it was necessary to fix the backup partition table at the tail end of the drive. The functins gpt_fix, gpt_zap were ported from dus-live to mkusb-sedd and upgraded in order to make it possible to create a partition behind the cloned partitions. (Excluding the action to create data partition for version 20.10 was reverted, it is possible again.) *This fix works in most computers, but there are some old HP computers, that fail to boot when mkusb-plug has created a data partition for version 20.10 and Hirsuit Hippo.*
  • dus-live: gpt_fix upgraded to match improvement necessary in mkusb-sedd.

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.6.6 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1029

sudodus said: I did some housecleaning of the templates in the web directory for UEFI and BIOS files,

https://phillw.net/isos/linux-tools/uefi-n-bios/

and created a new md5sum file for the remaining templates,


grub-boot-templates-for-uefi-n-bios.md5

The following files are there now (with some 'doublets' to allow for old links to work)


$ls -l *templ*
-rw-r--r-- 1 nio nio 2735732  2 jun 17.26 dd_grub-boot-template-for-uefi-n-bios_bright-bg.img.xz
-rw-r--r-- 1 nio nio 2768936 14 aug 16.03 dd_grub-boot-template-for-uefi-n-bios_dark-bg.img.xz
-rw-r--r-- 1 nio nio 2768416  4 jun 10.05 dd_grub-boot-template-for-uefi-n-bios.img.xz
-rw-r--r-- 1 nio nio 2768936  2 aug 15.59 dd_grub-boot-template-for-uefi-n-bios_new.img.xz
-rw-r--r-- 1 nio nio 3681860  8 aug 17.18 dd_grub-boot-template-for-uefi-n-bios_only-p1p2.img.xz
-rw-rw-r-- 1 nio nio     721 19 aug 15.08 grub-boot-templates-for-uefi-n-bios.md5
-rw-r--r-- 1 nio nio 3331492 11 aug 22.47 mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz
-rw-r--r-- 1 nio nio 2768936 14 aug 16.03 mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz
-rw-r--r-- 1 nio nio 3681860  8 aug 17.18 mkusb_grub-boot-template-for-uefi-n-bios_use-in-wins.img.xz

if I understand correctly,. @C.S.Cameron prefers to use the following two files,


mkusb_grub-boot-template-for-uefi-n-bios_fat32_4GB_use-in-wins.img.xz  # in Windows

dd_grub-boot-template-for-uefi-n-bios.img.xz  # in Ubuntu

I think that


mkusb_grub-boot-template-for-uefi-n-bios_use-in-ubuntu.img.xz  # in Ubuntu

should be best in Ubuntu, because it works also with Gnome-Disks and small USB drives (>= 1 GB). But it may need some testing to check that there are no regressions for other cases.

can i try that with vmware environment?

#1030

@dezintop,

Yes, you are welcome to try it. I did some similar tests in VirtualBox (long ago) so I would think it will work, but I have never used vmware.

Please let us know how it works for you :-)

#1031

Windows installer UEFI mode

Yesterday I was experimenting with a Windows 10 ISO on a USB msdos partition table. I extracted a Windows ISO to a NTFS partition on a Persistent USB made using mkusb. I ran "sudo update-grub" an added "ntldr /bootmgr" as a line below "chainloader +1". The installer ran fine in BIOS mode. I tried the same think on a gpt partition table but it would not run in BIOS mode. It did run on a UEFI mode computer. I tried it again after removing the Windows menuentry from grub.cfg. The Windows installer ISO still ran OK. Finally I extracted the ISO to a NTFS partition on a freshly zeroed USB drive. It still worked. I am wondering if this method is working consistently on other peoples UEFI computers? I believe that the same is true for a Ubuntu ISO that has been extracted to a USB drive booting in UEFI mode.

#1032

@C.S.Cameron,

I have access to various computers for testing. In UEFI mode all of them can boot most Linux systems when extracted to a FAT32 partition. The same is true for the Windows installer, when the iso file contains files smaller than 4 GiB. We know that there is a problem when there is a file, [FONT=Courier New]install.wim[/FONT], that exceeds that limit.

**Some computers *but not all* [computers that I have access to] can boot from an NTFS partition in UEFI mode.** This is a good option for the Windows installer where it works. So end users should test this method in their computers.

[hr][/hr] In mkusb I use the method to boot to a small FAT32 partition, and then let Windows transfer the boot process to a bigger NTFS partition, where all the files are extracted (including the huge [FONT=Courier New]install.wim[/FONT]). This works in all computers that I have access to, and I am rather confident that it works in the vast majority of computers.

#1033

I have been trying to install Kubuntu 20.04.1 to a laptop, however running into many problems. Have been using

mkusb kubuntu-20.04.1-desktop-amd64.iso 

and then select the "e" option. Do you think it may require selecting another option ?? Related discussion at https://ubuntuforums.org/showthread.php?t=2452691

#1034

@oygle,

I will answer at that other thread.

#1035

Thanks @sudodus

#1036

@sudodus - just an FYI, the only way I was able to see the "Try" and "Install" options was to follow your advice and use recovery mode (grub) to select the 'Text graphics' option.

#1037

I downloaded OpenMandriva and openSUSE Tumbleweed and used Mkusb to create the usb boot device. The usb was created OK, but I got this crash " _user_bin_udevadm.0-crash". This is on Ubuntu 20.10 with mkusb 12.6.6-1ubuntu2.

#1038

P-I H said: I downloaded OpenMandriva and openSUSE Tumbleweed and used Mkusb to create the usb boot device. The usb was created OK, but I got this crash " _user_bin_udevadm.0-crash".

This is on Ubuntu 20.10 with mkusb 12.6.6-1ubuntu2.

Thanks for the heads up.

Please give me more details: Is this an installed and fully updated & upgraded system? Can you think of any particular unusual settings or things installed, or should I troubleshoot this bug in a standard Ubuntu 20.10 system?

I will look into this bug, but I cannot do it at once ...

#1039

No hurry. This is on a standard Ubuntu 20.10 installation

p-i@pi-Asus-B450:~$ inxi -Fz
System:
  Kernel: 5.8.0-33-generic x86_64 bits: 64 Desktop: N/A 
  Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx 
  serial: <filter> UEFI: American Megatrends v: 2704 date: 08/23/2019 
CPU:
  Info: 8-Core model: AMD Ryzen 7 1700 bits: 64 type: MT MCP 
  L2 cache: 4096 KiB 
  Speed: 1378 MHz min/max: 1550/3750 MHz Core speeds (MHz): 1: 1378 2: 1381 
  3: 1636 4: 1381 5: 1497 6: 1497 7: 3736 8: 1497 9: 1372 10: 1427 11: 1485 
  12: 1496 13: 2894 14: 1485 15: 1388 16: 1398 
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
  driver: amdgpu v: kernel 
  Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 2560x1440~60Hz 
  OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.38.0 
  5.8.0-33-generic LLVM 11.0.0) 
  v: 4.6 Mesa 20.2.1 
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] 
  driver: snd_hda_intel 
  Device-2: AMD Family 17h HD Audio driver: snd_hda_intel 
  Sound Server: ALSA v: k5.8.0-33-generic 
Network:
  Device-1: Intel I211 Gigabit Network driver: igb 
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 912.90 GiB used: 96.15 GiB (10.5%) 
  ID-1: /dev/nvme0n1 vendor: Kingston model: SA1000M8480G size: 447.13 GiB 
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 960 EVO 250GB 
  size: 232.89 GiB 
  ID-3: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
Partition:
  ID-1: / size: 227.74 GiB used: 96.13 GiB (42.2%) fs: ext4 
  dev: /dev/nvme1n1p2 
Swap:
  ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) file: /swapfile 
Sensors:
  System Temperatures: cpu: 37.9 C mobo: 32.0 C gpu: amdgpu temp: 26.0 C 
  Fan Speeds (RPM): cpu: 420 case-1: 872 case-2: 817 case-3: 827 gpu: amdgpu 
  fan: 1147 
Info:
  Processes: 382 Uptime: 5m Memory: 15.56 GiB used: 1.61 GiB (10.3%) 
  Shell: Bash inxi: 3.1.07 
p-i@pi-Asus-B450:~$ 

I thought it might be related to make usb installation media for other distributions, but I tested with a groovy iso and got the crash. This is a picture of the mkusb console print out.

#1040

@P-I H,

Thanks for those details :-)

More questions:

  1. Where and when is the message about the crash printed? (I can't see it in your screenshot of the mkusb console.)
  1. Is your Ubuntu 20.10 system booted in UEFI mode or BIOS mode?
  1. Which locale (language) are you using in this Ubuntu 20.10 system?
#1041

3 it's English(United States), but formats is Sverige and keyboard is swedish.

  1. usr_bin_udevadm crashes just before the mkusb script is ready. The crash info is in /var/crash
  2. It's booted inn UEFI. BIOS is set to only boot in UEFI mode
#1042

Used mkusb on another computer with Hirsute and kernet 10.4 and didn't get any crash. I suppose the crash depends on the installation This is a picture of parts of the crash report. I didn't get the dialouge to report a bug in launchpad.

#1043

@P-I H,

Thanks for those details.

I made a quick test with Ubuntu 20.10 installed in my test computer, a Toshiba with Intel i5 (generation 3), in UEFI mode and with US English. I did not see any sign of a crash, neither in a terminal window nor in /var/crash.

So it is difficult for me to troubleshoot the problem. Maybe it depends on some combination of your hardware and the drivers for it and mkusb. It would be interesting if you can find some more details of what can cause the crash and what can make the system avoid the crash (for example by running various versions of Ubuntu live in the Asus-B450 and some other computer).

#1044

[SIZE=4]mkusb version 12.6.7, 12.6.8, 12.6.9 [/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. guidus: skip parameter if %f is '%f' (for hippo hirsute)

. dus-live: mkcmd_runcmd: ... wait for the buffered data to get flushed ...

. dus-persistent: .. grub_n_iso & probe_source: identifying 20.04.2 & 21.04 .. probe_source: usb-pack_efi auto-set for 21.04 & 20.04.2 [/td][/tr][/table]

  • mkusb 12.6.7
  • mkusb 12.6.8
  • mkusb 12.6.9

[SIZE=3]Improvement in version 12.6.7 [/SIZE]

  • guidus.desktop, when initiated from the menu in pcmanfm-qt, did not start correctly, complained:

%f is neither an iso file nor an img.{gz,xz} file

fixed by editing the shellscript guidus: if statement to skip parameter if %f is '%f' makes it work also in hippo hirsute

[SIZE=3]Improvement in version 12.6.8 [/SIZE]

  • Better information about flushing the buffers:

"Please wait for sync until 'Done' is written. If there is a progress window, wait for the buffered data to get flushed so that all data are transferred to the target device."

[SIZE=3]Improvement in version 12.6.9 [/SIZE]

Modified structure of the iso files of 20.04.2 & 21.04 makes it necessary to add a new way to identify these versions of Ubuntu. At the same time using usb-pack_efi is selected automatically for these new versions. The modifications were made in dus-persistent (and mkusb-plug *may* need some corresponding modification).

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.6.9 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1045

I have played with Opensuse Tumbleweed. This iso is 4.3 GB and perhaps this is the cause of the problem with the udev crash. Mkusb's terminal window shows that the copy is ready, but in the other window tthe copy goes on, but very slow. At first in 0 Mb/s. After a while the the copy will finish and the terminal window shows that you have to hit enter to finish. In case you are interested I can provide some screenshots.

#1046

P-I H said: I have played with Opensuse Tumbleweed. This iso is 4.3 GB and perhaps this is the cause of the problem with the udev crash. Mkusb's terminal window shows that the copy is ready, but in the other window tthe copy goes on, but very slow. At first in 0 Mb/s. After a while the the copy will finish and the terminal window shows that you have to hit enter to finish. In case you are interested I can provide some screenshots.

Yes please :-P

#1047

Will take some time. I have to change computer. Now I'm setting up a new gnome installation in Tumbleweed.

#1048

Pictures 1- Other window at start at 15-28-19 2- Terminal window 100% at 15-29-51 3- Other window whe terminal window shows 100 % at 15-30-05 4- Other window when almost ready at 15-32-27 5- Terminal window after almost ready at 15-32-46

#1049

The two last pictures 6- Other window when finished at 15-34-30 7- Terminal window when finished 15-34-52

#1050

Thanks @P-i H :-)

#1051

@P-i H,

The screenshots show what I would expect:

  • pv will show 100%, way before the buffers are flushed (syncing).
  • Instead of simply waiting in silence, there is output showing how the buffers are flushed.

The sequence above is particularly obvious, when there is a lot of RAM and a fairly new version of Ubuntu

  • Finally there is cleanup after writing and after that you can finish mkusb-dus.

-o-

I think there should be the same output from mkusb-dus also when there is 'nothing wrong'.

Are these screenshots connected to the problem you saw, that usr_bin_udevadm crashes just before the mkusb script is ready?

In that case, is there any output showing it except the crash info in /var/crash?

Edit: Maybe there should be some explaining text in the window showing how the buffers are flushed. Please suggest what should be written to explain better, what is happening :-)

#1052

I thought it might be connected to the problem. When you make a boot usb of over 4 GB it takes quit a long time before Done is written. The terminal window is the main window and perhaps a text like this should give a better understanding "Please wait for sync until 'Done* is written and the dus-live window shows a ready transfer" I will install Ubuntu 20.10 on another computer and see if I get the crash.

#1053

P-I H said: I thought it might be connected to the problem. When you make a boot usb of over 4 GB it takes quit a long time before Done is written.

The terminal window is the main window and perhaps a text like this should give a better understanding "Please wait for sync until 'Done* is written and the dus-live window shows a ready transfer" I will install Ubuntu 20.10 on another computer and see if I get the crash.

or maybe:

"Please wait for sync until 'Done' is written and, if there is a progress window wait for the buffered data to get flushed, so that all data are transferred to the target device"

#1054

That's fine.

#1055

P-I H said: That's fine.

Done, mkusb-dus version 12.6.8 is uploaded with the new information (text with blue background)

#1056

I am away from my home and borrowed Dell Inspiron Laptop with Windows 7 for my use. I downloaded Rufus and Xubuntu 20.04.1 ISO and installed persistent Live system on USB and it is working fine.

I installed mkusb on it and installed persistent Live system on another USB but the boot gets stuck at splash image showing mkusb icon.

Please note that the usb made with Rufus boots with Syslinux.

Kamalakar

#1057

@Kamalakar,

Thanks for the heads up :-)

I need some more details to troubleshoot this bug. (I have access to two Dell laptops (with generation 4 Intel i5 and i7 CPUs) but no Inspiron, and mkusb can make working persistent live systems in those computers.)

  • Which version of Dell Inspiron is it (version letters and number)? Which CPU, graphics chip and how much RAM is there?
  • Which version of mkusb did you use (you find dus 12.6.8 and mkusb-plug 2.8.4 via ppa:mkusb/unstable according to [FONT=Courier New]mkusb -v[/FONT])?
  • Did you install from the Xubuntu 20.04.1 iso file also with mkusb? Did you check that the iso file was good (correctly downloaded/copied)?
  • Did you use mkusb-dus or mkusb-plug to create the persistent live system? If the computer refuses to boot from USB via grub, please try mkusb-plug.
  • Did you connect only one USB drive with a persistent live system during boot? It may cause problems to boot with both the Rufus-made system and the mkusb-made system connected at the same time because there are two partitions for persistence and maybe also because of other confusing system partitions.
#1058

sudodus said: @Kamalakar,

Inspiron N4010 Reg Model P11G CPU Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) RAM 3 GB

  • Which version of Dell Inspiron is it (version letters and number)? Which CPU, graphics chip and how much RAM is there?
  • Which version of mkusb did you use (you find dus 12.6.8 and mkusb-plug 2.8.4 via ppa:mkusb/unstable according to [FONT=Courier New]mkusb -v[/FONT])?

dus 12.6.6

  • Did you install from the Xubuntu 20.04.1 iso file also with mkusb? Did you check that the iso file was good (correctly downloaded/copied)?

Yes. Yes..

  • Did you use mkusb-dus or mkusb-plug to create the persistent live system?

mkusb--dus

> If the computer refuses to boot from USB via grub, please try mkusb-plug. I have tried mkusb-plug and it works. The Live System boots using syslinux like the usb created with Rufus. Does it mean this Laptop can't boot with grub?

  • Did you connect only one USB drive with a persistent live system during boot?

Yes.

Kamalakar

#1059

@Kamalakar,

Thanks for the details :-)

The specs that you report *should* be good enough for a persistent live drive by mkusb-dus to work. But I know that there are things beyond what is easy to see, that can create problems. There are old HP computers that are unwilling to boot from USB via grub (usually in BIOS mode). This can be worked around by selecting MSDOS partition table (instead of default GPT) in the settings menu of mkusb-dus, when preparing for a persistent live drive.

Your problem may be the same. You can test it (by selecting MSDOS partition table in the settings menu). But it may also be another problem, so if that does not work, but it works to make live-only as well as persistent live drives with mkusb-plug, you may have to boot Xubuntu 20.04.1 via syslinux (at least in BIOS mode). Please notice that you can create a *persistent* live drive with mkusb-plug from a Xubuntu 20.04.1 iso file.

Xubuntu 20.10 is always booting via grub, also when cloned to a USB drive. *If you are interested and have the time, you can test creating a persistent live drive (of 20.10) with Rufus as well as with mkusb-dus and mkusb-plug and share your results* :-P

#1060

sudodus said: @Kamalakar,

Thanks for the details :-)

The specs that you report *should* be good enough for a persistent live drive by mkusb-dus to work. But I know that there are things beyond what is easy to see, that can create problems. There are old HP computers that are unwilling to boot from USB via grub (usually in BIOS mode). This can be worked around by selecting MSDOS partition table (instead of default GPT) in the settings menu of mkusb-dus, when preparing for a persistent live drive.

Your problem may be the same. You can test it (by selecting MSDOS partition table in the settings menu). But it may also be another problem, so if that does not work, but it works to make live-only as well as persistent live drives with mkusb-plug, you may have to boot Xubuntu 20.04.1 via syslinux (at least in BIOS mode). Please notice that you can create a *persistent* live drive with mkusb-plug from a Xubuntu 20.04.1 iso file.

Xubuntu 20.10 is always booting via grub, also when cloned to a USB drive. *If you are interested and have the time, you can test creating a persistent live drive (of 20.10) with Rufus as well as with mkusb-dus and mkusb-plug and share your results* :-P

I have tried by selecting MSDOS partition table in mkusb-dus both on Xubuntu 20.04.1 iso and Xubuntu 20.10i,iso. The Live drive does not boot. It boots only via syslinux when created through Rufus or mkusb-plug.

This leads me to another question. Suppose I do full install to usb will it boot? If it does not is there any way to install syslinux on full install to usb so that it boots.

Kamalakar

#1061

kagashe said: I have tried by selecting MSDOS partition table in mkusb-dus both on Xubuntu 20.04.1 iso and Xubuntu 20.10i,iso. The Live drive does not boot.

It boots only via syslinux when created through Rufus or mkusb-plug.

This leads me to another question. Suppose I do full install to usb will it boot? If it does not is there any way to install syslinux on full install to usb so that it boots.

Kamalakar

I don't know, but I think that you will get the same behaviour with a full install as with a persistent live system. I have read some paper about booting an installed system via syslinux, but I have never tried it, so I don't know the details.

Another option might be to try booting that Dell Inspiron in UEFI mode - I think it is more likely to work via grub (persistent live as well as installed compared to booting in BIOS mode).

#1062

sudodus said: I don't know, but I think that you will get the same behaviour with a full install as with a persistent live system. I have read some paper about booting an installed system via syslinux, but I have never tried it, so I don't know the details.

Another option might be to try booting that Dell Inspiron in UEFI mode - I think it is more likely to work via grub (persistent live as well as installed compared to booting in BIOS mode).

There is no UEFI on this Laptop.

Kamalakar

#1063

@Kamalakar,

  • Well, I think it would be possible (but maybe difficult) to make this old Dell Inspiron boot into an installed system in a USB drive via syslinux.
  • Maybe it will be good enough to run a persistent live system created with Rufus or mkusb-plug.
  • But it *might* work to boot via grub into an internal drive, if your friend wants to replace the old Windows 7.
  • If still problems with grub, [FONT=Courier New]mkusb-sedd[/FONT] (a sub-shellscript of mkusb-plug) can install a persistent live system into an internal drive, and a persistent live system is more reliable when running from a SATA-connected drive (compared to a USB drive).
#1064

kagashe said: This leads me to another question. Suppose I do full install to usb will it boot?

If it does not is there any way to install syslinux on full install to usb so that it boots.

Kamalakar

It is very easy to try a full install to USB using a pre-built image file. The one on the following link was created by sudodus and boots in either BIOS or UEFI mode. It should work on just about any old computer that boots USB. See: https://askubuntu.com/questions/1300454/easy-full-install-usb-that-boots-both-bios-and-uefi

#1065

C.S.Cameron said: It is very easy to try a full install to USB using a pre-built image file. The one on the following link was created by sudodus and boots in either BIOS or UEFI mode. It should work on just about any old computer that boots USB. See: https://askubuntu.com/questions/1300454/easy-full-install-usb-that-boots-both-bios-and-uefi

Thanks. Created on 16 GB USB through Rufus on Windows 7. It boots on Ubuntu 20.04 Desktop..

Kamalakar

#1066

@sudodus

Created a persistent Lubuntu 20.04.2 thumb-drive using dus 12.6.9 (persistence)

Output and command at terminal can be viewed (for now) via https://paste.ubuntu.com/p/6xpctxFXTF/

System was booted first on

  • dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

quick play, sudo apt update, 4 upgrades applied & system rebooted booted again on same box & looked good... no upgrades available, command history present :)

Next boot was on (command history present, no package upgrades found etc)

  • hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

Next boot was tried on uEFI

  • sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)

On this box I get a "Your vaio failed to Start Windows" ??

There was a delay before that appearing, where I assume it tried to boot thumb-drive from prior tests. The vaio has a Lubuntu installed (or other installed, probably focal.2) which boots.

I suspect this is an issue with persistent-thumb drive, as Lubuntu 20.04.2 daily boots when written via cloning...

Next boots on (without issues)

  • hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
  • hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)
  • dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
  • dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) ; persistent to ram option used

An install was attempted on (persistence) -- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) but it failed.. the reason is a known calamares (lubuntu) bug, but on a box that has never experienced it before, but most likely unrelated to mkusb/dus/

FYI: of minimal value, but iso.qa.ubu page is http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/226329/testcases/1303/results/

#1067

Don't know what to make of this, but @sudodus

New RC has been *spun* for Lubuntu 20.04.2 now, so it was written to thumb-drives dus focal-deskt<tab>

First was written with the standard LIVE mode only Second was written with persistence as before.

So far I've only booted on

  • sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)

which is where I had issues last time with persistence.. but both have booted on sony *crapbook*.

I then rebooted box; ejected & re-inserted media & it booted again...

Persistence is working, as it knew my wifi & could connect... Sorry I'm not sure what to make of this, maybe as it contradicts (I think) my prior findings... but it's what I've got now.. I'll continue testing, but my current focus is on Lubuntu's latest RC.

I could later boot it on sony device, but when I attempted to boot it on

the box skipped it (like it does for non-bootable media)

  • hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
#1068

@guiverc,

Thanks for testing mkusb-dus version 12.6.9 :-)

I am looking forward to your final conclusions from testing how the released Lubuntu 20.04.2 LTS iso file can be used to create persistent live drives, and how they work in your Sony Vaio and the hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290).

If still some failures, it will also be interesting to compare the result with 20.04.1 LTS and hirsute hippo. (For example: maybe we should *not* force dus-persistent to use usb-pack_efi for 20.04.2.)

It is also possible that there is a race condition, that can explain unpredictable results when booting.

#1069

Sorry, my primary focus was on the 20.04.2 release.. and mkusb testing only when time permitted.

My conclusions (as far as I recall) were it was *bad luck* (it failed, then it worked?? I'd need to do more testing, but on 50% I'd blame bad luck & not *mkusb*, as I seem to have occasional *bad luck* with thumb-drives, which get used, re-used so often....

The current daily ISO of *hirsute* written with persistence appears to have issues with [I]hirsute

[/I]It's failed to boot on

  • hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) ; uEFI capable box
  • sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)

It boots as expected

  • hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  • dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

(log of 'mkusb' write can be seen at https://paste.ubuntu.com/p/pyRTxK8gB2/)

First successful boot was done on hp dc7700, packages updated (3), touch blah, then reboot. On reboot (same box), all updates were applied, command history present & my touched file present.

attempts to reboot on hp.8200 & sony.vaiocrap were re-attempted but failed. dell.755 which was next tried with updated packages present, my 'blah' file present, command history etc & all as expected. dell.755-5 was reboot & all good again.

It looks to me like issues are with uEFI; at least from this *very limited* testing.

I've had issues today and on uEFI boxes including the sony.crap, which is a *little* consistent with the other day (but still inconsistent). I'm unlikely to do more today (*mkusb* wise), as I want to repeat some Lubuntu *install* testing (*and it's getting too warm with multiple boxes on; something most people will likely be envious of!*).

http://iso.qa.ubuntu.com/qatracker/milestones/419/builds/226913/testcases/1303/results

#1070

@guiverc,

Thanks for continuing the tests with mkusb-dus.

My conclusions (as far as I recall) were it was bad luck (it failed, then it worked?? I'd need to do more testing, but on 50% I'd blame bad luck & not mkusb, as I seem to have occasional bad luck with thumb-drives, which get used, re-used so often....

I have failed to provoke the failures of mkusb similar to yours, but I have different hardware (computers and USB pendrives). I will keep testing mkusb-dus (making persistent live drives) ...

I notice in your log of the mkusb console that cloning the iso file into partition #4 is very slow (the long list of numbers from 11 to 100 and the total time 9 min 31 sec). *It would be interesting to check if your luck will be better after wiping the whole devices (thumb-drives, which get used, re-used so often).* The problem might not only be speed, but also choking of the buffer in the USB management system, and my experience is that wiping the whole device will remove some obstacles so that things will work smoother.

#1071

Greeting:

I have been trialing mkusb 12.6.9 and mkusb-plug 2.8.4 with 20.04.2 for a while now. It has been a totally boring experience, everything has worked as expected.

The highlight was finding the option in mkusb-plug to create a usbdata partition with a choice of filesystems. Mkusb has gained a lot of features, I wonder if new manpage(s) are necessary.

My next exercise will be to test the latest version of mkusb with the latest version of Ubuntu to become designated as being supported, 14.04 LTS. For the story on this one see:

https://meta.askubuntu.com/questions/19510/is-ubuntu-14-04-off-topic-on-ask-ubuntu/19514?noredirect=1#comment42249_19514

Regards

#1072

I installed Ubuntu 14.04.3 to a USB using dus 12.6.9 installed on 20.04. (Wow running 14.04 again was great). I installed mkusb 12.6.9 onto the 14.04 USB. mkusb-plug had unmet dependencies, (fdisk), and would not install. I also had no luck installing fdisk. Once mkusb 12.6.9 was installed I used it to install 14.04.3 to another USB. I could not find the dus icon but dus boots okay from Terminal. Ubuntu 14.04 installed on USB from 12.6.9 installed on 14.04 works as expected. To bad about mkusb-plug.

#1073

@C.S.Cameron,

Thanks for testing mkusb-dus and mkusb-plug.

  1. I could not make mkusb-plug work with old versions of Ubuntu because of certain dependency problems, and you have discovered it. There is a detailed description here.
  1. I must admit that I have sort of abandoned Ubuntu 14.04.x LTS because its normal support has ended. This version is at extended security maintenance now (paid-for-support for companies, probably mainly for Ubuntu Server installations). I have tested the current versions of mkusb-dus with Ubuntu 16.04.x LTS. So I am happy that it still can be used with 14.04.x LTS although with some quirks.
  1. You are right, I had better spend some time on new manpage(s) and/or a manual in some other format.
#1074

I've used mkusb over several years and found it to be a very solid and easy to use product. It has always been for making bootable USB's from an ISO for Kubuntu/Ubuntu. Now I need to make a bootable USB for Windows 8.1, so obviously mkusb can do this also. Have downloaded the ISO from https://www.microsoft.com/en-au/software-download/windows8ISO , purchased a Win 8.1 pro key and now need to make the bootable USB.

Of course anything regards this from the Microsoft site is all EXE's and in fact the tool suggested by one company was rufus. However I see that is also an EXE. So, to use mkusb for this, are there any specific parameters or options to be aware of please ?

#1075

@oygle,

  • mkusb works in Ubuntu (and some other Linux distros).
  • mkusb can create bootable USB drives with the Windows installer (for Windows 7 and newer versions). You can use mkusb-dus (mkusb version 12) or mkusb-plug for this purpose.

So you can boot into an Ubuntu or Ubuntu family flavour operating system and use mkusb to create a Windows installer in a USB drive. The size of the USB drive should be at least 8 GB. I think you will find the options for this purpose in the graphical user interfaces of mkusb-dus and mkusb-plug. Please ask again if you need more details.

[hr][/hr] As you write, Rufus is an exe file which is executable in Windows but not in Ubuntu. Rufus works well to create bootable USB drives with an installer for Ubuntu, another Linux distro or Windows.

#1076

@oygle,

I have tried to make simple step by step instructions for installing Windows using mkusb-plug.

https://askubuntu.com/questions/1274878/make-windows-10-bootable-usb-in-ubuntu/1274975#1274975

#1077

@sudodus - Thanks for your help. As it turns out, the plan to erase an old laptop and install Win 8 or 10 on that, have now come to a halt. I had no end of problems with trying to use the Microsoft ISO and a purchashed key, plus it does seem the HDD is well on its way out. It also seemed the MS install wrote to the USB, as the usb had errors ??

It was hard to determine if the problems were on the usb or not, but I suspect the usb was fine. I even tried this

mkusb-nox Win8.1_English_x64.iso

but then after spending most of the day on it, there arose a "loop situation" where the attempted installs appeared to only partially work, take out the media, restart, .. again and again. I need to forget about doing this on that old (now "cactus") laptop.

C.S.Cameron said: @oygle,

I have tried to make simple step by step instructions for installing Windows using mkusb-plug.

https://askubuntu.com/questions/1274878/make-windows-10-bootable-usb-in-ubuntu/1274975#1274975

Thank you, I have made a note of that.

#1078

@oygle,

mkusb-nox does not work with newer versions of Windows, that 'want to' create a file greater than 4 GB. Nowadays I would recommend mkusb-dus or mkusb-plug instead.

  • Is there any sign of failure (error message or warning message) when you try to create the Windows installer in the USB drive?
  • Please use mkusb-dus to wipe the whole USB pendrive 'Wipe the whole device'. After that it may behave better.

[hr][/hr] Edit:

If you want to run in text mode, you can run mkusb-tow directly (instead of mkusb-nox). mkusb-tow is called from the GUIs of mkusb-dus and mkusb-plug. But it is safer to start it via a GUI (to get the correct target device).


$ mkusb-tow
 Run 'mkusb-tow' with sudo or as root 
------------- mkusb-tow makes it safer to create a boot drive -------------
From Windows iso file create installer in e.g. USB pendrive or memory card
Usage:
 sudo /path/mkusb-tow <source file> <target device> 
Example:
 sudo mkusb-tow windows.iso /dev/sdx
Help:
mkusb-tow -h
Version:
mkusb-tow -v
Available devices 
NAME      SIZE TRAN   MODEL
sda     238,5G sata   SanDisk SD6SB1M2
sdb       3,7T sata   WDC WD4002FYYZ-0
sdc      14,6G usb    Extreme         
nvme0n1 232,9G nvme   KINGSTON SA2000M8250G                   
#1079

@sudodus, Thanks very much for your help.

sudodus said: mkusb-nox does not work with newer versions of Windows, that 'want to' create a file greater than 4 GB. Nowadays I would recommend mkusb-dus or mkusb-plug instead.

That could well have been the problem.

sudodus said:

  • Is there any sign of failure (error message or warning message) when you try to create the Windows installer in the USB drive?

No, none at all, whether I used the gui or the command line of mkusb and the tools included with it, all actions were fine, no errors.

sudodus said:

  • Please use mkusb-dus to wipe the whole USB pendrive 'Wipe the whole device'. After that it may behave better.

Thanks, yesterday I did actually get to install the Win 8.1 by modifying a registry key, so it's all okay now, thanks for your help. :D

#1080

[SIZE=4]mkusb version 12.7.0, 12.7.1, 12.7.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

* dus: p_checkpoint: full lsblk output to zenity * mkusb-plug: srctst and mkusb-sedd: puer: . identify new versions of Ubuntu (.disk/info) . and and a minor cosmetic tweaks (zenity window size)

  • mkusb 12.7.0

* dus-persistent: probe_source: upefi [from now] always default for debian

  • mkusb 12.7.1

* dus 12.7.2 and mkusb-plug 2.8.6 with several sub-scripts: quoted grep 'patterns' [/td][/tr][/table]

  • mkusb 12.7.2

[SIZE=3]Improvement in program package mkusb version 12.7.0 [/SIZE]

  • dus 12.7.0: p_checkpoint: full lsblk output to zenity

The zenity window will show the full output of lsblk


lsblk -o MODEL,NAME,FSTYPE,LABEL,SIZE "$target"

in order to make it easier than before to identify the target device and avoid mistakes.

  • mkusb-plug 2.8.5: srctst: added a second test to identify newer versions of Ubuntu iso files and a minor cosmetic tweak (zenity window size)
  • mkusb-sedd 2.8.5: puer: added a second test to identify newer versions of Ubuntu iso files and some minor cosmetic tweaks (zenity window size etc)

[SIZE=3]Improvement in program package mkusb version 12.7.1 [/SIZE]

  • dus-persistent 12.7.1: probe_source: upefi [from now] always default for debian

This is a simplification because upefi (usb-pack-efi) works in all current and recently deprecated Debian versions. The new version tested is Debian Bullseye alias version 11: using the file [FONT=Courier New]debian-live-11.0.0-amd64-standard.iso[/FONT]

[SIZE=3]Improvement in program package mkusb version 12.7.2 [/SIZE]

dus 12.7.2 and mkusb-plug 2.8.6 with several sub-scripts: quoted grep 'patterns' (that were previously not quoted and vulnerable to unexpected results when there are certain file names).

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.7.1 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1081

The following link suggests a work-around for a question at AskUbuntu,

"How to preserve and freeze modification made during a LiveSession of LiveDisc and to prevent any further modification without remastering the LiveDisc".

**Custom LiveDisc: Workaround using a persistent live system**

I have tested a step further on this path, to actually run live (live-only with or without toRAM). And it seems to work (at least in the current Lubuntu Impish iso file, to be released as version 21.10).

Summary:

  • Create a persistent live Ubuntu family system with mkusb
  • Boot persistent live and modify your system to get the custom system that you want
  • Boot live and create a tarball with 'backup' in the 'usbdata' partition.
  • Run 'extractor4live' and your live system is now the custom system.
  • Next time run 'extractor4live' again ...

Encryption?

  • The tarball is not encrypted. I think it can be left to the end user, who wants encryption, to replace the tarball with an encrypted zip-file. This is a rather simple encryption, but maybe enough for a private user. An installed system with LVM and LUKS-encrypted disk can be recommended for more advanced encryption.

extractor4live:


#!/bin/bash

grep ' persistent' /proc/cmdline
if [ $? -eq 0 ]
then
 echo persistent
 echo 'You should use this shellscript when booted live (live-only)'
else
 echo live
 usbd=$(find /media/ -name "extractor4live" | head -n1)
 usbd=${usbd%/*}
 cd /
 sudo tar --exclude=./upper/usr/lib/systemd/* --strip-components=2 \
      -xvf "$usbd"/1-writable.tar.gz ./upper/ \
      > "$usbd"/list4live.log  2> "$usbd"/error4live.log
fi

Please test the following instructions, and give me feedback, particularly if something must be improved :-P

README:


Instructions about the files in this directory

**1. Backup and restore**

The file 'backup' must be run when booted live, and it will backup the content of the
partition for persistence.

./backup

It will create one tarball each time,

1-writable.tar.gz
2-writable.tar.gz
...

The file 'restore' must be run when booted live, and it will restore content of the
partition for persistence from the selected tarball.

./restore

**2. Running a custom system live (live-only)**

2.1 Modify the system by running a persistent live system,

install tools
tweak the appearance
...

2.2 Boot live, change directory to this one (usbdata) and run 'backup'

Now you have a tarball. Normally one tarball, '1-writable.tar.gz'.

2.3 If you wish, you can change the label of the partition for persistence to
something else than 'writable' or 'casper-rw', for example 'ext-data'. This will
make the drive live-only (until you change the label back again).

**3. Make the live system into your custom system**

You can run **live** or **live + toRAM**. And you can repeat this many times.

3.1 Boot live, change directory to this one (usbdata) and run 'extractor4live'

./extractor4live

It will extract what is stored in the tarball '1-writable.tar.gz' to the live system,

and write to the log files

error4live.log
list4live.log

I have seen the following errors, but do not know yet, if they cause problems.

tar: rofs: Cannot utime: Read-only file system - OK
tar: rofs: Cannot change ownership to uid 0, gid 0: Read-only file system - OK
tar: etc/xdg/autostart/gnome-software-service.desktop: Cannot mknod: Operation not permitted - OK
tar: etc/security/limits.d/audio.conf.disabled: Cannot mknod: Operation not permitted - ?
tar: Exiting with failure status due to previous errors - only 'summary'

Please check for errors and report bugs, that may be related to them.

3.2 Change directory to your home and enjoy :-)

cd

3.2 More than one custom live system

If you have two or more tarballs, you can make extractor files for each of them.

**4. Start using your custom live system**

When you shutdown or reboot, what you have done in the live system is forgotten,
except if you store things in the 'usbdata' partition or the 'ext-data' partition.
So normally you should change directory to your home and enjoy :-)

cd
#1082

sudodus said: [SIZE=4]mkusb version 12.7.0[/SIZE]

  • dus 12.7.0: p_checkpoint: full lsblk output to zenity

The zenity window will show the full output of lsblk


lsblk -o MODEL,NAME,FSTYPE,LABEL,SIZE "$target"

in order to make it easier than before to identify the target device and avoid mistakes.

Thank you !!

I LOVE that feature !!

#1083

re extractor4live: I get Syntax error: end of file unexpected (expecting "then"), when trying to run the script. I'm not very good at scripts.

#1084

@C.S.Cameron,

Sorry, the script is kind of rough, not very user friendly (yet), but I don't get that error. There should be a 'then' after the line with 'if', and there is unless you did not get it right when copy/pasting it into an editor. The last line should contain 'fi' (not 'if'), which is closing the if-statement (if-then-else-fi). Maybe that is the problem?

When booted live you should first create a 'backup' tarball of the partition for persistence, and put this file 'extractor4live' into the NTFS file system of 'usbdata', and then run it to get the 'custom live' system.

#1085

Do I need to activate the script with chmod +x ? I made the tarball by running the /usbdata/backup script I copy / pasted the extractor4live script from page 108. I double checked every item you mentioned, still no luck.

#1086
  • I think all files in usbdata will be executable by default (because of the way it is automounted).
  • It should not complain expecting "then". Please check the md5sum,

$ md5sum extractor4live readme.e2l
0a906573c175eec439d5898067a10efd  extractor4live
400cd939afb1a54d99809bfc4730fbf1  readme.e2l

It is possible that I uploaded and edited the file code in the post. Please tell the web browser to re-read the page so that your browser will display a current version of the file code. (Today I copied and pasted it into an editor and wrote it to another file name and checked that it is what it is supposed to be with diff and with md5sum.)

I can upload 'extractor4live' and 'readme.e2l' to a server, where you can download them.

See phillw.net/isos/linux-tools/mkusb

#1087

Here is a new one that does not involve Bootable USB's

Was commenting on an ask question and mentioned extracting ISO files to USB for UEFI boot. Wondered why extract to USB, why not just extract to the internal Windows drive. Did some experimenting and finally got around to making a 10GB FAT32 partition on the Windows drive using Windows Disk Management. Extracted the ISO to that and rebooted. Pressed F12 and UEFI gave me the option to boot Ubuntu. Ubuntu Live booted up just fine. Lots of people on Ask Ubuntu ask how to boot Live Ubuntu without a USB. My usual answer is DriveDroid, WinGRUB or UNetbootin Frugal mode, (which I have had lots of problems with). This method gives another simple option for people with UEFI computers.

#1088

@C.S.Cameron,

+1 to this method. Yes, I understand that it works like that in UEFI mode via a temporary menu. Congratulations to finding that it can be useful in this new context (to boot Ubuntu live without a bootable USB).

#1089

I think I got the extractor4live working okay. It produces the log files but it does not change the Live apps and settings to what is in the tarball.

#1090

@C.S.Cameron,

This makes me interested.

  • What is written in the log files?

Please suggest what I should test:

  • Which iso file are you starting from?
  • An app and a setting, that won't work for you.

Edit: It works this way with mkusb (installed via the PPA)

#1091

error4live.log:

tar: var/cache/man/tr: Cannot mknod: File exists
tar: var/cache/man/cat2: Cannot mknod: Operation not permitted
tar: var/cache/man/sl: Cannot mknod: File exists
tar: var/cache/man/ru: Cannot mknod: File exists
tar: var/cache/man/ja: Cannot mknod: File exists

And more of the same.

list4live.log

./upper/root/
./upper/root/snap/
./upper/root/snap/snap-store/
./upper/root/snap/snap-store/common/
./upper/root/snap/snap-store/current
./upper/root/snap/snap-store/518/
./upper/var/
./upper/var/log/
./upper/var/log/boot.log
./upper/var/log/gpu-manager.log
./upper/var/log/syslog
./upper/var/log/unattended-upgrades/
./upper/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
./upper/var/log/faillog
./upper/var/log/casper.log
./upper/var/log/dmesg
./upper/var/log/gdm3/
./upper/var/log/lastlog
./upper/var/log/kern.log
./upper/var/log/auth.log
./upper/var/log/wtmp
./upper/var/log/cups/
./upper/var/log/cups/access_log
./upper/var/log/dmesg.0
./upper/var/log/journal/
./upper/var/log/journal/f2700725140e4d0788d6f608572e70e6/
./upper/var/log/journal/f2700725140e4d0788d6f608572e70e6/system.journal
./upper/var/log/journal/f2700725140e4d0788d6f608572e70e6/system@fa7eba92b2ee4e359e41e45b81a6716f-0000000000000001-0005c9327b5e07e4.journal
./upper/var/lib/
./upper/var/lib/AccountsService/
./upper/var/lib/AccountsService/users/
./upper/var/lib/AccountsService/users/ubuntu
./upper/var/lib/AccountsService/icons/
./upper/var/lib/upower/
./upper/var/lib/upower/history-time-empty-AS10D71-73-1710.dat
./upper/var/lib/upower/history-rate-AS10D71-73-1710.dat
./upper/var/lib/upower/history-time-full-AS10D71-73-1710.dat
./upper/var/lib/upower/history-charge-AS10D71-73-1710.dat
./upper/var/lib/polkit-1/
./upper/var/lib/polkit-1/localauthority/
./upper/var/lib/polkit-1/localauthority/50-local.d/
./upper/var/lib/polkit-1/localauthority/50-local.d/disable-hibernate.pkla
./upper/var/lib/polkit-1/localauthority/10-vendor.d/
./upper/var/lib/polkit-1/localauthority/10-vendor.d/10-live-cd.pkla
./upper/var/lib/apt/
./upper/var/lib/apt/cdroms.list~
./upper/var/lib/apt/lists/
./upper/var/lib/apt/lists/Ubuntu%2021.04%20%5fHirsute%20Hippo%5f%20-%20Release%20amd64%20(20210420)_dists_hirsute_restricted_binary-amd64_Packages
./upper/var/lib/apt/lists/Ubuntu%2021.04%20%5fHirsute%20Hippo%5f%20-%20Release%20amd64%20(20210420)_dists_hirsute_main_binary-amd64_Packages
./upper/var/lib/apt/lists/partial/
./upper/var/lib/apt/lists/Ubuntu%2021.04%20%5fHirsute%20Hippo%5f%20-%20Release%20amd64%20(20210420)_dists_hirsute_Release
./upper/var/lib/apt/lists/Ubuntu%2021.04%20%5fHirsute%20Hippo%5f%20-%20Release%20amd64%20(20210420)_dists_hirsute_Release.gpg
./upper/var/lib/apt/cdroms.list
./upper/var/lib/udisks2/
./upper/var/lib/udisks2/mounted-fs-persistent
./upper/var/lib/dbus/
./upper/var/lib/dbus/machine-id
./upper/var/lib/alsa/
./upper/var/lib/alsa/asound.state
./upper/var/lib/gdm3/
./upper/var/lib/gdm3/greeter-dconf-defaults
./upper/var/lib/dpkg/
./upper/var/lib/dpkg/diversions
./upper/var/lib/dpkg/diversions-old
./upper/var/lib/colord/
./upper/var/lib/colord/.cache/
./upper/var/lib/colord/storage.db
./upper/var/lib/colord/mapping.db
./upper/var/lib/snapd/
./upper/var/lib/snapd/apparmor/
./upper/var/lib/snapd/apparmor/profiles/
./upper/var/lib/snapd/apparmor/profiles/snap.snap-store.hook.configure
./upper/var/lib/snapd/apparmor/profiles/snap.snap-store.snap-store
./upper/var/lib/snapd/apparmor/profiles/snap.snap-store.ubuntu-software
./upper/var/lib/snapd/apparmor/profiles/snap.snap-store.ubuntu-software-local-file
./upper/var/lib/snapd/apparmor/profiles/snap-update-ns.snap-store
./upper/var/lib/snapd/apparmor/snap-confine/
./upper/var/lib/snapd/apparmor/snap-confine/overlay-root
./upper/var/lib/snapd/device/
./upper/var/lib/snapd/device/private-keys-v1/
./upper/var/lib/snapd/device/private-keys-v1/zhe6qjK-4VV3aiRgTAzon567PDGV_lu3iQxp4Z33T678hNwOVZZjnJ3PW0O7mnxm
./upper/var/lib/snapd/system-key
./upper/var/lib/snapd/mount/
./upper/var/lib/snapd/mount/snap.snap-store.fstab
./upper/var/lib/snapd/state.json
./upper/var/lib/snapd/hostfs/
./upper/var/lib/NetworkManager/
./upper/var/lib/NetworkManager/timestamps
./upper/var/lib/NetworkManager/seen-bssids
./upper/var/lib/NetworkManager/NetworkManager.state
./upper/var/lib/NetworkManager/NetworkManager-intern.conf
./upper/var/lib/plymouth/
./upper/var/lib/plymouth/boot-duration
./upper/var/lib/whoopsie/
./upper/var/lib/whoopsie/whoopsie-id
./upper/var/lib/systemd/
./upper/var/lib/systemd/timesync/
./upper/var/lib/systemd/timesync/clock
./upper/var/lib/systemd/rfkill/
./upper/var/lib/systemd/rfkill/platform-acer-wmi:wlan
./upper/var/lib/systemd/rfkill/platform-acer-wmi:bluetooth
./upper/var/lib/systemd/rfkill/pci-0000:09:00.0-bcma-1:wlan
./upper/var/lib/systemd/rfkill/pci-0000:00:1a.0-usb-0:1.2:1.0:bluetooth
./upper/var/lib/systemd/random-seed
./upper/var/lib/systemd/linger/
./upper/var/lib/systemd/timers/
./upper/var/lib/systemd/timers/stamp-update-notifier-motd.timer
./upper/var/lib/systemd/timers/stamp-fwupd-refresh.timer
./upper/var/lib/systemd/timers/stamp-logrotate.timer
./upper/var/lib/systemd/timers/stamp-apt-daily.timer
./upper/var/lib/systemd/timers/stamp-fstrim.timer
./upper/var/lib/systemd/timers/stamp-e2scrub_all.timer
./upper/var/lib/systemd/timers/stamp-man-db.timer
./upper/var/lib/systemd/timers/stamp-apt-daily-upgrade.timer
./upper/var/lib/systemd/timers/stamp-anacron.timer
./upper/var/lib/systemd/timers/stamp-motd-news.timer
./upper/var/lib/systemd/backlight/
./upper/var/lib/systemd/backlight/pci-0000:00:02.0:backlight:acpi_video0
./upper/var/lib/ubuntu-drivers-common/
./upper/var/lib/ubuntu-drivers-common/last_gfx_boot
./upper/var/lib/PackageKit/
./upper/var/lib/PackageKit/transactions.db
./upper/var/lib/bluetooth/
./upper/var/lib/bluetooth/F0:7B:CB:F2:BA:C4/
./upper/var/lib/bluetooth/F0:7B:CB:F2:BA:C4/settings
./upper/var/crash/
./upper/var/spool/
./upper/var/spool/cups/
./upper/var/spool/cups/tmp/
./upper/var/snap/
./upper/var/snap/snap-store/
./upper/var/snap/snap-store/common/
./upper/var/snap/snap-store/common/fontconfig/
./upper/var/snap/snap-store/common/fontconfig/d5178ab6d91b49bf20a416737dcea9e8-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/767a8244fc0220cfb567a839d0392e0b-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/16c2fda60d1b4b719f4b3d06fd951d25-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/49f0de54bdd920fe4f0dfd4cbac43e6b-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/cabbd14511b9e8a55e92af97fb3a0461-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/b47c4e1ecd0709278f4910c18777a504-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/f6d4eedfaab2589bde49f7a3ff831d22-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/550f3886151c940c12a5ed35f6a00586-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/d82eb4fd963d448e2fcb7d7b793b5df3-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/0c9eb80ebd1c36541ebe2852d3bb0c49-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/c5c45a61289222e0d30b1a26ef4effbe-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/f6e6e0a5c3d2f6ae0c0c2e0ecd42a997-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/57e423e26b20ab21d0f2f29c145174c3-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/3047814df9a2f067bd2d96a2b9c36e5a-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/56cf4f4769d0f4abc89a4895d7bd3ae1-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/04aabc0a78ac019cf9454389977116d2-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/3830d5c3ddfd5cd38a049b759396e72e-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/4c599c202bc5c08e2d34565a40eac3b2-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/589f83ef4c36d296ce6e1c846f468f08-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/32b6488e5b8292a2e95c79d947e009e8-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/14a5e22175779b556eaa434240950366-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/a48eab177a16e4f3713381162db2f3e9-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/4f3e3037c9980c83b53a9351efadef62-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/b9d506c9ac06c20b433354fa67a72993-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/b872e6e592da6075ffa4ab0a1fcc0c75-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/da43223dd54fb3bb4243ae19d4b583b2-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/4b2eda6bb976bda485cb2176619421d5-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/707971e003b4ae6c8121c3a920e507f5-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/2300eef321c393bfd76478a5c0e95b23-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/85e0a52ce643a7ba2ae53e5d6949cead-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/f259c2cffa685e28062317905db73c4a-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/fe547fea3a41b43a38975d292a2b19c7-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/9b89f8e3dae116d678bbf48e5f21f69b-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/0d8c3b2ac0904cb8a57a757ad11a4a08-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/e13b20fdb08344e0e664864cc2ede53d-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/089dead882dea3570ffc31a9898cfb69-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/564b2e68ac9bc4e36a6f7f6d6125ec1c-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/aec30016f93e1b46d1a973dce0d74068-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/d52a8644073d54c13679302ca1180695-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/6333f38776742d18e214673cd2c24e34-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/1ac9eb803944fde146138c791f5cc56a-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/d589a48862398ed80a3d6066f4f56f4c-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/3f589640d34b7dc9042c8d453f7c8b9c-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/fonts.conf
./upper/var/snap/snap-store/common/fontconfig/573ec803664ed168555e0e8b6d0f0c7f-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/7ab2eb8330e5664a2b0e875ad8d37ad9-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/a4e60e8d1e10d2fdff3fe3037a1845fb-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/6b2c5944714ca7831b25bed9e85cb5c8-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/CACHEDIR.TAG
./upper/var/snap/snap-store/common/fontconfig/dc05db6664285cc2f12bf69c139ae4c3-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/9d2451b1fd30e5bffe8383fd27c35478-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/551ecf3b0e8b0bca0f25c0944f561853-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/c855463f699352c367813e37f3f70ea7-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/bab58bb527bb656aaa9f116d68a48d89-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/6afa1bb216ce958c1589e297e8008489-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/4d9c95eba1cb85bbcf2878543262124a-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/3f7329c5293ffd510edef78f73874cfd-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/674d1711f2d1d2a09646eb0bdcadee49-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/370e5b74bf5dafc30834de68e24a87a4-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/def309198bfa603429122923fa2bb2d4-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/6cc790b63b123a6a96ee260fcdad32a9-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/2151c34eae6ab8b65f2db52eba5f75d1-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/660208299946a285a940457d1287da33-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/2171a34dccabdb6bcbbc728186263178-le64.cache-7
./upper/var/snap/snap-store/common/fontconfig/22368d551a680bfe5a62c02760edf4ea-le64.cache-7
./upper/var/cache/
./upper/var/cache/apparmor/
./upper/var/cache/apparmor/2afb0764.0/
./upper/var/cache/apparmor/2afb0764.0/snap-confine.snapd.11588
./upper/var/cache/apparmor/2afb0764.0/snap.snap-store.hook.configure
./upper/var/cache/apparmor/2afb0764.0/snap.snap-store.snap-store
./upper/var/cache/apparmor/2afb0764.0/.features
./upper/var/cache/apparmor/2afb0764.0/snap.snap-store.ubuntu-software
./upper/var/cache/apparmor/2afb0764.0/snap.snap-store.ubuntu-software-local-file
./upper/var/cache/apparmor/2afb0764.0/usr.lib.snapd.snap-confine.real
./upper/var/cache/apparmor/2afb0764.0/snap-update-ns.snap-store
./upper/var/cache/debconf/
./upper/var/cache/debconf/config.dat
./upper/var/cache/debconf/passwords.dat
./upper/var/cache/debconf/config.dat-old
./upper/var/cache/debconf/templates.dat
./upper/var/cache/cups/
./upper/var/cache/cups/job.cache.O
./upper/var/cache/cups/rss/
./upper/var/cache/cups/org.cups.cupsd
./upper/var/cache/cups/job.cache
./upper/var/cache/man/
./upper/var/cache/man/tr
./upper/var/cache/man/cat2
./upper/var/cache/man/sl
./upper/var/cache/man/ru
./upper/var/cache/man/ja
./upper/var/cache/man/ko
./upper/var/cache/man/fr
./upper/var/cache/man/es
./upper/var/cache/man/zh_TW
./upper/var/cache/man/fr.ISO8859-1
./upper/var/cache/man/id
./upper/var/cache/man/de
./upper/var/cache/man/it
./upper/var/cache/man/index.db
./upper/var/cache/man/cat1
./upper/var/cache/man/zh_CN
./upper/var/cache/man/fr.UTF-8
./upper/var/cache/man/ro
./upper/var/cache/man/sv
./upper/var/cache/man/cat5
./upper/var/cache/man/cs
./upper/var/cache/man/CACHEDIR.TAG
./upper/var/cache/man/hu
./upper/var/cache/man/cat7
./upper/var/cache/man/cat3
./upper/var/cache/man/cat8
./upper/var/cache/man/nl
./upper/var/cache/man/fi
./upper/var/cache/man/cat6
./upper/var/cache/man/pt_BR
./upper/var/cache/man/pl
./upper/var/cache/man/da
./upper/var/cache/man/cat4
./upper/var/cache/man/pt
./upper/var/cache/man/uk
./upper/var/cache/man/sr
./upper/var/tmp/
./upper/rofs/
./upper/home/
./upper/home/ubuntu/
./upper/home/ubuntu/.local/
./upper/home/ubuntu/.local/share/
./upper/home/ubuntu/.local/share/gvfs-metadata/
./upper/home/ubuntu/.local/share/gvfs-metadata/root.6NBE80
./upper/home/ubuntu/.local/share/gvfs-metadata/uuid-720C0D7F5ED4DD73
./upper/home/ubuntu/.local/share/gvfs-metadata/trash:-94eef8d1.log
./upper/home/ubuntu/.local/share/gvfs-metadata/trash:
./upper/home/ubuntu/.local/share/gvfs-metadata/uuid-afa33799-8ee8-4656-bdb4-abb5bdb17f1b
./upper/home/ubuntu/.local/share/gvfs-metadata/home-b6b39f58.log
./upper/home/ubuntu/.local/share/gvfs-metadata/root
./upper/home/ubuntu/.local/share/gvfs-metadata/uuid-720C0D7F5ED4DD73-d8550bec.log
./upper/home/ubuntu/.local/share/gvfs-metadata/uuid-afa33799-8ee8-4656-bdb4-abb5bdb17f1b-3eed0c7f.log
./upper/home/ubuntu/.local/share/gvfs-metadata/root-51516bc1.log
./upper/home/ubuntu/.local/share/gvfs-metadata/home
./upper/home/ubuntu/.local/share/keyrings/
./upper/home/ubuntu/.local/share/nautilus/
./upper/home/ubuntu/.local/share/nautilus/scripts/
./upper/home/ubuntu/.local/share/recently-used.xbel
./upper/home/ubuntu/.local/share/flatpak/
./upper/home/ubuntu/.local/share/flatpak/db/
./upper/home/ubuntu/.local/share/ibus-table/
./upper/home/ubuntu/.local/share/gnome-shell/
./upper/home/ubuntu/.local/share/gnome-shell/gnome-overrides-migrated
./upper/home/ubuntu/.local/share/evolution/
./upper/home/ubuntu/.local/share/evolution/tasks/
./upper/home/ubuntu/.local/share/evolution/tasks/trash/
./upper/home/ubuntu/.local/share/evolution/tasks/system/
./upper/home/ubuntu/.local/share/evolution/tasks/system/tasks.ics
./upper/home/ubuntu/.local/share/evolution/addressbook/
./upper/home/ubuntu/.local/share/evolution/addressbook/trash/
./upper/home/ubuntu/.local/share/evolution/addressbook/system/
./upper/home/ubuntu/.local/share/evolution/addressbook/system/photos/
./upper/home/ubuntu/.local/share/evolution/addressbook/system/contacts.db
./upper/home/ubuntu/.local/share/evolution/memos/
./upper/home/ubuntu/.local/share/evolution/memos/trash/
./upper/home/ubuntu/.local/share/evolution/calendar/
./upper/home/ubuntu/.local/share/evolution/calendar/trash/
./upper/home/ubuntu/.local/share/evolution/calendar/system/
./upper/home/ubuntu/.local/share/evolution/mail/
./upper/home/ubuntu/.local/share/evolution/mail/trash/
./upper/home/ubuntu/.local/share/gnome-settings-daemon/
./upper/home/ubuntu/.local/share/gnome-settings-daemon/input-sources-converted
./upper/home/ubuntu/.local/share/tracker/
./upper/home/ubuntu/.local/share/tracker/data/
./upper/home/ubuntu/.local/share/tracker/data/tracker-store.journal
./upper/home/ubuntu/.local/share/tracker/data/tracker-store.ontology.journal
./upper/home/ubuntu/.local/share/icc/
./upper/home/ubuntu/.local/share/icc/edid-935070517023a07a77d48b4e21fe2e70.icc
./upper/home/ubuntu/.local/share/sounds/
./upper/home/ubuntu/.local/share/applications/
./upper/home/ubuntu/.local/share/session_migration-ubuntu
./upper/home/ubuntu/.local/share/xorg/
./upper/home/ubuntu/.local/share/xorg/Xorg.0.log
./upper/home/ubuntu/.local/share/xorg/Xorg.0.log.old
./upper/home/ubuntu/.config/
./upper/home/ubuntu/.config/user-dirs.dirs
./upper/home/ubuntu/.config/gtk-3.0/
./upper/home/ubuntu/.config/gtk-3.0/bookmarks
./upper/home/ubuntu/.config/ubuntu-system-settings/
./upper/home/ubuntu/.config/ubuntu-system-settings/wizard-has-run
./upper/home/ubuntu/.config/update-notifier/
./upper/home/ubuntu/.config/user-dirs.locale
./upper/home/ubuntu/.config/mozc/
./upper/home/ubuntu/.config/mozc/ibus_config.textproto
./upper/home/ubuntu/.config/nautilus/
./upper/home/ubuntu/.config/gnome-session/
./upper/home/ubuntu/.config/gnome-session/saved-session/
./upper/home/ubuntu/.config/dconf/
./upper/home/ubuntu/.config/dconf/user
./upper/home/ubuntu/.config/libreoffice/
./upper/home/ubuntu/.config/libreoffice/4/
./upper/home/ubuntu/.config/libreoffice/4/user/
./upper/home/ubuntu/.config/libreoffice/4/user/database/
./upper/home/ubuntu/.config/libreoffice/4/user/database/biblio.odb
./upper/home/ubuntu/.config/libreoffice/4/user/database/biblio/
./upper/home/ubuntu/.config/libreoffice/4/user/database/biblio/biblio.dbf
./upper/home/ubuntu/.config/libreoffice/4/user/database/biblio/biblio.dbt
./upper/home/ubuntu/.config/libreoffice/4/user/gallery/
./upper/home/ubuntu/.config/libreoffice/4/user/gallery/sg30.thm
./upper/home/ubuntu/.config/libreoffice/4/user/gallery/sg30.sdv
./upper/home/ubuntu/.config/libreoffice/4/user/basic/
./upper/home/ubuntu/.config/libreoffice/4/user/basic/Standard/
./upper/home/ubuntu/.config/libreoffice/4/user/basic/Standard/dialog.xlb
./upper/home/ubuntu/.config/libreoffice/4/user/basic/Standard/Module1.xba
./upper/home/ubuntu/.config/libreoffice/4/user/basic/Standard/script.xlb
./upper/home/ubuntu/.config/libreoffice/4/user/basic/script.xlc
./upper/home/ubuntu/.config/libreoffice/4/user/basic/dialog.xlc
./upper/home/ubuntu/.config/libreoffice/4/user/config/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/sdraw/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/sdraw/statusbar/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/sdraw/images/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/sdraw/images/Bitmaps/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/sdraw/menubar/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/sdraw/popupmenu/
./upper/home/ubuntu/.config/libreoffice/4/user/config/soffice.cfg/modules/sdraw/toolbar/
./upper/home/ubuntu/.config/libreoffice/4/user/config/autotbl.fmt
./upper/home/ubuntu/.config/libreoffice/4/user/psprint/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.bundle.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.script.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.sfwk.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.executable.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/uno_packages/cache/uno_packages/
./upper/home/ubuntu/.config/libreoffice/4/user/registrymodifications.xcu
./upper/home/ubuntu/.config/libreoffice/4/user/pack/
./upper/home/ubuntu/.config/libreoffice/4/user/pack/ExtensionInfo.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/database/
./upper/home/ubuntu/.config/libreoffice/4/user/pack/database/biblio.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/database/biblio/
./upper/home/ubuntu/.config/libreoffice/4/user/pack/database/biblio/biblio.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/basic/
./upper/home/ubuntu/.config/libreoffice/4/user/pack/basic/dialog.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/basic/Standard/
./upper/home/ubuntu/.config/libreoffice/4/user/pack/basic/Standard/Module1.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/basic/Standard/dialog.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/basic/Standard/script.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/basic/script.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/config/
./upper/home/ubuntu/.config/libreoffice/4/user/pack/config/autotbl.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/registrymodifications.pack
./upper/home/ubuntu/.config/libreoffice/4/user/pack/autotext/
./upper/home/ubuntu/.config/libreoffice/4/user/pack/autotext/mytexts.pack
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/lastsynchronized
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.bundle.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.script.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.sfwk.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/shared/registry/com.sun.star.comp.deployment.executable.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/buildid
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/lastsynchronized
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.bundle.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.script.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.sfwk.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/bundled/registry/com.sun.star.comp.deployment.executable.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.bundle.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.script.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.help.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/backenddb.xml
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.sfwk.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/registry/com.sun.star.comp.deployment.executable.PackageRegistryBackend/
./upper/home/ubuntu/.config/libreoffice/4/user/extensions/tmp/extensions/
./upper/home/ubuntu/.config/libreoffice/4/user/autotext/
./upper/home/ubuntu/.config/libreoffice/4/user/autotext/mytexts.bau
./upper/home/ubuntu/.config/goa-1.0/
./upper/home/ubuntu/.config/evolution/
./upper/home/ubuntu/.config/evolution/sources/
./upper/home/ubuntu/.config/evolution/sources/system-proxy.source
./upper/home/ubuntu/.config/gnome-initial-setup-done
./upper/home/ubuntu/.config/eog/
./upper/home/ubuntu/.config/pulse/
./upper/home/ubuntu/.config/pulse/f2700725140e4d0788d6f608572e70e6-device-volumes.tdb
./upper/home/ubuntu/.config/pulse/f2700725140e4d0788d6f608572e70e6-default-source
./upper/home/ubuntu/.config/pulse/f2700725140e4d0788d6f608572e70e6-card-database.tdb
./upper/home/ubuntu/.config/pulse/cookie
./upper/home/ubuntu/.config/pulse/f2700725140e4d0788d6f608572e70e6-stream-volumes.tdb
./upper/home/ubuntu/.config/pulse/f2700725140e4d0788d6f608572e70e6-default-sink
./upper/home/ubuntu/.config/ibus-mozc-gnome-initial-setup-done
./upper/home/ubuntu/.config/ibus/
./upper/home/ubuntu/.config/ibus/bus/
./upper/home/ubuntu/.config/ibus/bus/f2700725140e4d0788d6f608572e70e6-unix-0
./upper/home/ubuntu/.cache/
./upper/home/ubuntu/.cache/fontconfig/
./upper/home/ubuntu/.cache/fontconfig/CACHEDIR.TAG
./upper/home/ubuntu/.cache/fontconfig/158c65c810c0d352a587f5be66058e87-le64.cache-7
./upper/home/ubuntu/.cache/fontconfig/807752c9e168308eb5108dacded5237a-le64.cache-7
./upper/home/ubuntu/.cache/mesa_shader_cache/
./upper/home/ubuntu/.cache/mesa_shader_cache/be/
./upper/home/ubuntu/.cache/mesa_shader_cache/be/59620e30a9e4a068aec7aeeef4be4c98f25108
./upper/home/ubuntu/.cache/mesa_shader_cache/28/
./upper/home/ubuntu/.cache/mesa_shader_cache/28/bc59bf9c8397d2aa7566929cdde362823dff53
./upper/home/ubuntu/.cache/mesa_shader_cache/28/9e98896b8d4813ad744e5878f66e0da42e6103
./upper/home/ubuntu/.cache/mesa_shader_cache/31/
./upper/home/ubuntu/.cache/mesa_shader_cache/31/6633b1845ecaf0ea1321e8bf5a7f9d3f3faa9e
./upper/home/ubuntu/.cache/mesa_shader_cache/7d/
./upper/home/ubuntu/.cache/mesa_shader_cache/7d/30734fa3ce0e994330da82c1782195856ce12c
./upper/home/ubuntu/.cache/mesa_shader_cache/99/
./upper/home/ubuntu/.cache/mesa_shader_cache/99/a4c72514c65130473e3c1ce4212cecc71bd222
./upper/home/ubuntu/.cache/mesa_shader_cache/bc/
./upper/home/ubuntu/.cache/mesa_shader_cache/bc/16c1fbb303dc661a89b721dec148821679f16a
./upper/home/ubuntu/.cache/mesa_shader_cache/53/
./upper/home/ubuntu/.cache/mesa_shader_cache/53/afef6f5c9c220fb0ba9152813376d5326fb750
./upper/home/ubuntu/.cache/mesa_shader_cache/08/
./upper/home/ubuntu/.cache/mesa_shader_cache/08/923d9be90e93b7593d9b61c4d3810aa1c571d2
./upper/home/ubuntu/.cache/mesa_shader_cache/0d/
./upper/home/ubuntu/.cache/mesa_shader_cache/0d/96ef84349849d2877362f556e5785c063110e3
./upper/home/ubuntu/.cache/mesa_shader_cache/98/
./upper/home/ubuntu/.cache/mesa_shader_cache/98/4b2be3a8b561c5f054a18ba4160a147703eafb
./upper/home/ubuntu/.cache/mesa_shader_cache/d0/
./upper/home/ubuntu/.cache/mesa_shader_cache/d0/018b8ed4b9228ce94ae651c104b873a31981ad
./upper/home/ubuntu/.cache/mesa_shader_cache/1c/
./upper/home/ubuntu/.cache/mesa_shader_cache/1c/b510738917fc0a27be3d52cdc41952451b1a1e
./upper/home/ubuntu/.cache/mesa_shader_cache/e4/
./upper/home/ubuntu/.cache/mesa_shader_cache/e4/18684397157755241aae81e550f08711f06d1b
./upper/home/ubuntu/.cache/mesa_shader_cache/d5/
./upper/home/ubuntu/.cache/mesa_shader_cache/d5/1908b7881b99000cd9fa487bda5e2fd03a94a6
./upper/home/ubuntu/.cache/mesa_shader_cache/72/
./upper/home/ubuntu/.cache/mesa_shader_cache/72/396d8b91cb0dadabfddcb63a17640d7b5b0efc
./upper/home/ubuntu/.cache/mesa_shader_cache/7f/
./upper/home/ubuntu/.cache/mesa_shader_cache/7f/08504b484629b37c889883213f65c3d93af549
./upper/home/ubuntu/.cache/mesa_shader_cache/7f/bb765ccf8df4107f7f64450e627cd778249d8b
./upper/home/ubuntu/.cache/mesa_shader_cache/21/
./upper/home/ubuntu/.cache/mesa_shader_cache/21/45b805b2149abf83225756f5be8f4d02980a0a
./upper/home/ubuntu/.cache/mesa_shader_cache/c1/
./upper/home/ubuntu/.cache/mesa_shader_cache/c1/c078e4ed262dd8eb1cffc4a9f5db9c8fd85153
./upper/home/ubuntu/.cache/mesa_shader_cache/47/
./upper/home/ubuntu/.cache/mesa_shader_cache/47/aea6d97160947ce6547c29f47e538eee214fcb
./upper/home/ubuntu/.cache/mesa_shader_cache/a0/
./upper/home/ubuntu/.cache/mesa_shader_cache/a0/68f7659937849ee583afe960c25786e5a7fc98
./upper/home/ubuntu/.cache/mesa_shader_cache/index
./upper/home/ubuntu/.cache/mesa_shader_cache/43/
./upper/home/ubuntu/.cache/mesa_shader_cache/43/766a7cf11147ae06f033408806e85cf74c0987
./upper/home/ubuntu/.cache/mesa_shader_cache/43/14d0274d817cf42fb051d329af5890390e3d65
./upper/home/ubuntu/.cache/mesa_shader_cache/49/
./upper/home/ubuntu/.cache/mesa_shader_cache/49/929cfebbb8c9307e0855d93915573ddf3aa385
./upper/home/ubuntu/.cache/mesa_shader_cache/1e/
./upper/home/ubuntu/.cache/mesa_shader_cache/1e/5127e263f8742e466802312b20ebf728d6c133
./upper/home/ubuntu/.cache/mesa_shader_cache/1e/cc0e7644b310fb7dbacb0278457dcea9916b14
./upper/home/ubuntu/.cache/mesa_shader_cache/14/
./upper/home/ubuntu/.cache/mesa_shader_cache/14/fa6c01d1e98dfeb28c63c039a73003a084c21b
./upper/home/ubuntu/.cache/mesa_shader_cache/f9/
./upper/home/ubuntu/.cache/mesa_shader_cache/f9/277e97a107f7b6e8aa8679a285add10712df4d
./upper/home/ubuntu/.cache/mesa_shader_cache/f9/3730713869e4d854a206fc4bcc5a0e070ed43b
./upper/home/ubuntu/.cache/mesa_shader_cache/25/
./upper/home/ubuntu/.cache/mesa_shader_cache/25/81e9c2a6e693b9d02f0fe817ea8589675a2f4b
./upper/home/ubuntu/.cache/mesa_shader_cache/25/5cf14f9079c08cfa38417cf2290676b99fe8b0
./upper/home/ubuntu/.cache/mesa_shader_cache/fd/
./upper/home/ubuntu/.cache/mesa_shader_cache/fd/db314b9aec69b993702a01b265b4b59680d890
./upper/home/ubuntu/.cache/mesa_shader_cache/50/
./upper/home/ubuntu/.cache/mesa_shader_cache/50/be0cd2dffd40f62d2045da3934fe7aeb252af9
./upper/home/ubuntu/.cache/mesa_shader_cache/87/
./upper/home/ubuntu/.cache/mesa_shader_cache/87/c83aa5d46eb11296be597ff2ec1b211132251c
./upper/home/ubuntu/.cache/mesa_shader_cache/87/26148560940365ff5c41694ce13455e0cfd3ab
./upper/home/ubuntu/.cache/mesa_shader_cache/87/89fa3d0294176cc90c119de895c7d5fcae402d
./upper/home/ubuntu/.cache/mesa_shader_cache/7a/
./upper/home/ubuntu/.cache/mesa_shader_cache/7a/c5b784875b4a8c6c0aa46ef9fba379683b73b4
./upper/home/ubuntu/.cache/mesa_shader_cache/52/
./upper/home/ubuntu/.cache/mesa_shader_cache/52/5277b5c041260ecdb191fac34b095af692f8e4
./upper/home/ubuntu/.cache/mesa_shader_cache/c4/
./upper/home/ubuntu/.cache/mesa_shader_cache/c4/01e5825434ded8e4160516d725f81d1a750363
./upper/home/ubuntu/.cache/mesa_shader_cache/de/
./upper/home/ubuntu/.cache/mesa_shader_cache/de/1c601186e64d1f08369f16bfa0d70083fce8b0
./upper/home/ubuntu/.cache/mesa_shader_cache/79/
./upper/home/ubuntu/.cache/mesa_shader_cache/79/b4910d1e8b36a8f8773f506d555fef914e81c0
./upper/home/ubuntu/.cache/mesa_shader_cache/79/0b94896465f1fda2cf6dee13f6a9206168ccad
./upper/home/ubuntu/.cache/mesa_shader_cache/79/33299bf1d79984d2e70d6f73495f3dd92e9f1c
./upper/home/ubuntu/.cache/mesa_shader_cache/44/
./upper/home/ubuntu/.cache/mesa_shader_cache/44/3409c45a004d6f91232abce3c5791b94bf333a
./upper/home/ubuntu/.cache/mesa_shader_cache/74/
./upper/home/ubuntu/.cache/mesa_shader_cache/74/fec6eee93e7ad434294dbcdcf5877213f6c821
./upper/home/ubuntu/.cache/mesa_shader_cache/74/7a5513d48012978354e9114ca518288567602d
./upper/home/ubuntu/.cache/mesa_shader_cache/91/
./upper/home/ubuntu/.cache/mesa_shader_cache/91/cab9376c7228d604d7f601df765f29218c6836
./upper/home/ubuntu/.cache/mesa_shader_cache/91/0b8932521856dfd9da67d606c482e109d80466
./upper/home/ubuntu/.cache/mesa_shader_cache/1b/
./upper/home/ubuntu/.cache/mesa_shader_cache/1b/6c9ad1a051f0e10c723bbdead0f38bdaa5bcb9
./upper/home/ubuntu/.cache/mesa_shader_cache/1b/fa8ab7a2c77771f6afc2fdbe59175cc9355a02
./upper/home/ubuntu/.cache/mesa_shader_cache/c3/
./upper/home/ubuntu/.cache/mesa_shader_cache/c3/9279d44c311dbb1d8ec4390f57240008e0dbc0
./upper/home/ubuntu/.cache/mesa_shader_cache/1d/
./upper/home/ubuntu/.cache/mesa_shader_cache/1d/13585cf4d67a70a9e41990798201596c04a466
./upper/home/ubuntu/.cache/mesa_shader_cache/bd/
./upper/home/ubuntu/.cache/mesa_shader_cache/bd/58bd922409ba46be057d880e32d4ce97578bd7
./upper/home/ubuntu/.cache/mesa_shader_cache/e5/
./upper/home/ubuntu/.cache/mesa_shader_cache/e5/75762a09919d164cccf59fc42edb0ba95a52f2
./upper/home/ubuntu/.cache/mesa_shader_cache/15/
./upper/home/ubuntu/.cache/mesa_shader_cache/15/c64b9616e51b6ba7e2d1ce6c258ea306d7931a
./upper/home/ubuntu/.cache/mesa_shader_cache/51/
./upper/home/ubuntu/.cache/mesa_shader_cache/51/d3b4d16f50b6c609c1584633be6cfdf18b5a9e
./upper/home/ubuntu/.cache/mesa_shader_cache/a4/
./upper/home/ubuntu/.cache/mesa_shader_cache/a4/7f762c9b048d006f474d9b612283779238e63b
./upper/home/ubuntu/.cache/mesa_shader_cache/96/
./upper/home/ubuntu/.cache/mesa_shader_cache/96/392997bddff4297b4f944513742d914c1bd090
./upper/home/ubuntu/.cache/mesa_shader_cache/24/
./upper/home/ubuntu/.cache/mesa_shader_cache/24/6a1939f354ed6c96b6fd11c269f4334f827fab
./upper/home/ubuntu/.cache/mesa_shader_cache/e3/
./upper/home/ubuntu/.cache/mesa_shader_cache/e3/32be99cfcaf57a33e32b32b21b893691b3729f
./upper/home/ubuntu/.cache/mesa_shader_cache/db/
./upper/home/ubuntu/.cache/mesa_shader_cache/db/bac5667511e413182032679ad0cea6ee8b6e91
./upper/home/ubuntu/.cache/mesa_shader_cache/58/
./upper/home/ubuntu/.cache/mesa_shader_cache/58/863b3bcdb2ccfa0cf476c169bf56b72c4133c6
./upper/home/ubuntu/.cache/mesa_shader_cache/8f/
./upper/home/ubuntu/.cache/mesa_shader_cache/8f/0c2e9c71ec579d435501f3fedbfd32783ad538
./upper/home/ubuntu/.cache/mesa_shader_cache/97/
./upper/home/ubuntu/.cache/mesa_shader_cache/97/9b26a2a8c067bd9b29a80825eef27320c53012
./upper/home/ubuntu/.cache/mesa_shader_cache/37/
./upper/home/ubuntu/.cache/mesa_shader_cache/37/bc9c794c7bcb392a069102062060a4d4ba9b33
./upper/home/ubuntu/.cache/mesa_shader_cache/05/
./upper/home/ubuntu/.cache/mesa_shader_cache/05/89e02d3eacf9e526ad4efa9104e6246d990216
./upper/home/ubuntu/.cache/mesa_shader_cache/18/
./upper/home/ubuntu/.cache/mesa_shader_cache/18/6f87b2bb9ebf177c2a2b96a45875d4d4efb233
./upper/home/ubuntu/.cache/mesa_shader_cache/18/1118b22a395dfe135ba2b02de728cd8e131136
./upper/home/ubuntu/.cache/mesa_shader_cache/60/
./upper/home/ubuntu/.cache/mesa_shader_cache/60/17120ae7a68280c6dd2b9be32df20e359bfb7d
./upper/home/ubuntu/.cache/mesa_shader_cache/eb/
./upper/home/ubuntu/.cache/mesa_shader_cache/eb/ffd0cb0367884a84fad2e3e29bc467d4826707
./upper/home/ubuntu/.cache/mesa_shader_cache/4f/
./upper/home/ubuntu/.cache/mesa_shader_cache/4f/f3da55fa3959ed9d476cdbcbb980df3620de3f
./upper/home/ubuntu/.cache/mesa_shader_cache/f6/
./upper/home/ubuntu/.cache/mesa_shader_cache/f6/5bb25e1de8614700cb36d8960fe13dd63c4c69
./upper/home/ubuntu/.cache/mesa_shader_cache/6e/
./upper/home/ubuntu/.cache/mesa_shader_cache/6e/0f663859d7044f05bd4c9a56700846b5c9d919
./upper/home/ubuntu/.cache/mesa_shader_cache/6e/dbc0be13fed85bccace57dc3a7196a467b3d72
./upper/home/ubuntu/.cache/mesa_shader_cache/0b/
./upper/home/ubuntu/.cache/mesa_shader_cache/0b/3c15efa8ab04e3d311cc1d4fefef89d18d9f94
./upper/home/ubuntu/.cache/mesa_shader_cache/fe/
./upper/home/ubuntu/.cache/mesa_shader_cache/fe/c228c09c299d197738bcae1c2995a66eda1f49
./upper/home/ubuntu/.cache/mesa_shader_cache/5f/
./upper/home/ubuntu/.cache/mesa_shader_cache/5f/b17eec7d8dfd6276f3979ce5936ae2f8c3d8a2
./upper/home/ubuntu/.cache/mesa_shader_cache/5f/ecb5f461a6092f5c7841340660106d2db51f3b
./upper/home/ubuntu/.cache/mesa_shader_cache/11/
./upper/home/ubuntu/.cache/mesa_shader_cache/11/1e14ca71f73e47ff9fd2867215192267a5a31c
./upper/home/ubuntu/.cache/mesa_shader_cache/ca/
./upper/home/ubuntu/.cache/mesa_shader_cache/ca/81bc737ac65539c5e54b55e37f1914197699cf
./upper/home/ubuntu/.cache/mesa_shader_cache/ca/b6b38266574485e89ec602b4389151f2cf7dab
./upper/home/ubuntu/.cache/mesa_shader_cache/65/
./upper/home/ubuntu/.cache/mesa_shader_cache/65/c6ff263076d7cb97c05bbe336353a7e098b6c9
./upper/home/ubuntu/.cache/mesa_shader_cache/d2/
./upper/home/ubuntu/.cache/mesa_shader_cache/d2/602ffe4932d58a6c0c55ce7d7ead48677ae129
./upper/home/ubuntu/.cache/mesa_shader_cache/42/
./upper/home/ubuntu/.cache/mesa_shader_cache/42/3062377f85943684daa3941c213020b8195f9b
./upper/home/ubuntu/.cache/mesa_shader_cache/4e/
./upper/home/ubuntu/.cache/mesa_shader_cache/4e/22cd1d9f0578a05a6bedb05b85e079c13866f2
./upper/home/ubuntu/.cache/mesa_shader_cache/6c/
./upper/home/ubuntu/.cache/mesa_shader_cache/6c/e10551347ff498a67fba4af97d99bdffbb4626
./upper/home/ubuntu/.cache/mesa_shader_cache/dc/
./upper/home/ubuntu/.cache/mesa_shader_cache/dc/4053ac7ec59cc947a354f8848499c844ef2a3d
./upper/home/ubuntu/.cache/mesa_shader_cache/2f/
./upper/home/ubuntu/.cache/mesa_shader_cache/2f/c7b60d3d0ee3e1df810e89033513769707113f
./upper/home/ubuntu/.cache/mesa_shader_cache/80/
./upper/home/ubuntu/.cache/mesa_shader_cache/80/24919453570e8813dcf6203e09d99b98680748
./upper/home/ubuntu/.cache/mesa_shader_cache/8d/
./upper/home/ubuntu/.cache/mesa_shader_cache/8d/aff4bf4f61347fcaabcbd1c13b07f45a4f73e9
./upper/home/ubuntu/.cache/mesa_shader_cache/ed/
./upper/home/ubuntu/.cache/mesa_shader_cache/ed/d1fc7edb5f94519c18ee0107d388ebc31a03b0
./upper/home/ubuntu/.cache/mesa_shader_cache/e1/
./upper/home/ubuntu/.cache/mesa_shader_cache/e1/2d865f3512951604e91a347b431bbc91a379c2
./upper/home/ubuntu/.cache/mesa_shader_cache/a5/
./upper/home/ubuntu/.cache/mesa_shader_cache/a5/0740b0f20032d5d5f2f75f23ef0a974e62a924
./upper/home/ubuntu/.cache/mesa_shader_cache/3a/
./upper/home/ubuntu/.cache/mesa_shader_cache/3a/837e1384d0e0ab736aa2ec7f31fed6e9ce3da0
./upper/home/ubuntu/.cache/mesa_shader_cache/9e/
./upper/home/ubuntu/.cache/mesa_shader_cache/9e/fe0c955bcb4ce1130ffbda99ef88693ee1fe63
./upper/home/ubuntu/.cache/mesa_shader_cache/b6/
./upper/home/ubuntu/.cache/mesa_shader_cache/b6/954aaf7ad44d2addbe8c597eb88d2a1a35593f
./upper/home/ubuntu/.cache/mesa_shader_cache/59/
./upper/home/ubuntu/.cache/mesa_shader_cache/59/826377dcea701d7ac3658de21739ce0e0b65df
./upper/home/ubuntu/.cache/mesa_shader_cache/9a/
./upper/home/ubuntu/.cache/mesa_shader_cache/9a/e3b25a188dc5eb2044f9f6df114759b9ecbafa
./upper/home/ubuntu/.cache/mesa_shader_cache/f4/
./upper/home/ubuntu/.cache/mesa_shader_cache/f4/20bd104b3fa41fb3e66d0beec27a8e055da095
./upper/home/ubuntu/.cache/mesa_shader_cache/69/
./upper/home/ubuntu/.cache/mesa_shader_cache/69/a8264670391f5c3bd0eb78c8bcc9bf5031edb4
./upper/home/ubuntu/.cache/mesa_shader_cache/b8/
./upper/home/ubuntu/.cache/mesa_shader_cache/b8/ddef16b13b52583df9af22f9b43b43a9681ccd
./upper/home/ubuntu/.cache/mesa_shader_cache/ef/
./upper/home/ubuntu/.cache/mesa_shader_cache/ef/2ee02c9d6ef23ff3427e89f524a8c40a66eb69
./upper/home/ubuntu/.cache/mesa_shader_cache/7e/
./upper/home/ubuntu/.cache/mesa_shader_cache/7e/5b0ae0f9c4aef75b5d7276213e2a2bc0dc10a4
./upper/home/ubuntu/.cache/mesa_shader_cache/f1/
./upper/home/ubuntu/.cache/mesa_shader_cache/f1/bde7d283ac01b40d8aed8cabe1044c9acdcf31
./upper/home/ubuntu/.cache/mesa_shader_cache/39/
./upper/home/ubuntu/.cache/mesa_shader_cache/39/0af16f7a64537c7e9a7812c88a5fc2ae5348db
./upper/home/ubuntu/.cache/libgweather/
./upper/home/ubuntu/.cache/ibus-table/
./upper/home/ubuntu/.cache/event-sound-cache.tdb.f2700725140e4d0788d6f608572e70e6.x86_64-pc-linux-gnu
./upper/home/ubuntu/.cache/thumbnails/
./upper/home/ubuntu/.cache/thumbnails/normal/
./upper/home/ubuntu/.cache/thumbnails/normal/6e45fe8edad5deb77b443d8d64382576.png
./upper/home/ubuntu/.cache/thumbnails/large/
./upper/home/ubuntu/.cache/thumbnails/large/32a78caafcb5757fe96b23ef773e7c1f.png
./upper/home/ubuntu/.cache/thumbnails/large/6e45fe8edad5deb77b443d8d64382576.png
./upper/home/ubuntu/.cache/thumbnails/large/01e05700ddbe8c295287286c6b944f49.png
./upper/home/ubuntu/.cache/evolution/
./upper/home/ubuntu/.cache/evolution/tasks/
./upper/home/ubuntu/.cache/evolution/tasks/trash/
./upper/home/ubuntu/.cache/evolution/addressbook/
./upper/home/ubuntu/.cache/evolution/addressbook/trash/
./upper/home/ubuntu/.cache/evolution/memos/
./upper/home/ubuntu/.cache/evolution/memos/trash/
./upper/home/ubuntu/.cache/evolution/sources/
./upper/home/ubuntu/.cache/evolution/sources/trash/
./upper/home/ubuntu/.cache/evolution/calendar/
./upper/home/ubuntu/.cache/evolution/calendar/trash/
./upper/home/ubuntu/.cache/evolution/mail/
./upper/home/ubuntu/.cache/evolution/mail/trash/
./upper/home/ubuntu/.cache/tracker/
./upper/home/ubuntu/.cache/tracker/meta.db-wal
./upper/home/ubuntu/.cache/tracker/db-version.txt
./upper/home/ubuntu/.cache/tracker/locale-for-miner-apps.txt
./upper/home/ubuntu/.cache/tracker/no-need-mtime-check.txt
./upper/home/ubuntu/.cache/tracker/last-crawl.txt
./upper/home/ubuntu/.cache/tracker/db-locale.txt
./upper/home/ubuntu/.cache/tracker/first-index.txt
./upper/home/ubuntu/.cache/tracker/parser-version.txt
./upper/home/ubuntu/.cache/tracker/ontologies.gvdb
./upper/home/ubuntu/.cache/tracker/meta.db-shm
./upper/home/ubuntu/.cache/tracker/meta.db
./upper/home/ubuntu/.cache/gvfs/
./upper/home/ubuntu/.cache/ibus/
./upper/home/ubuntu/.cache/ibus/bus/
./upper/home/ubuntu/.cache/ibus/bus/registry
./upper/home/ubuntu/.cache/gstreamer-1.0/
./upper/home/ubuntu/.cache/gstreamer-1.0/registry.x86_64.bin
./upper/home/ubuntu/Desktop/
./upper/home/ubuntu/Desktop/ubiquity.desktop
./upper/home/ubuntu/Pictures/
./upper/home/ubuntu/Pictures/Wallpapers/
./upper/home/ubuntu/Pictures/Wallpapers/wallpaper (copy).png
./upper/home/ubuntu/Pictures/Wallpapers/wallpaper.png
./upper/home/ubuntu/Pictures/wallpaper.png
./upper/home/ubuntu/Public/
./upper/home/ubuntu/Documents/
./upper/home/ubuntu/.bashrc
./upper/home/ubuntu/Templates/
./upper/home/ubuntu/Downloads/
./upper/home/ubuntu/.gnupg/
./upper/home/ubuntu/.gnupg/private-keys-v1.d/
./upper/home/ubuntu/.bash_logout
./upper/home/ubuntu/.profile
./upper/home/ubuntu/Music/
./upper/home/ubuntu/Videos/
./upper/boot/
./upper/boot/grub/
./upper/boot/grub/grubenv
./upper/cdrom/
./upper/etc/
./upper/etc/shadow
./upper/etc/login.defs
./upper/etc/machine-id
./upper/etc/shadow-
./upper/etc/gshadow-
./upper/etc/pam.d/
./upper/etc/pam.d/login
./upper/etc/apt/
./upper/etc/apt/sources.list
./upper/etc/apt/apt.conf.d/
./upper/etc/apt/apt.conf.d/50unattended-upgrades
./upper/etc/apt/apt.conf.d/00aptitude
./upper/etc/apt/apt.conf.d/10periodic
./upper/etc/apt/apt.conf.d/20auto-upgrades
./upper/etc/apt/sources.list~
./upper/etc/sudoers.d/
./upper/etc/sudoers.d/casper
./upper/etc/passwd
./upper/etc/gdm3/
./upper/etc/gdm3/custom.conf
./upper/etc/nsswitch.conf
./upper/etc/default/
./upper/etc/default/cryptdisks
./upper/etc/default/amd64-microcode
./upper/etc/default/console-setup
./upper/etc/default/acpi-support
./upper/etc/default/kerneloops
./upper/etc/default/grub
./upper/etc/default/im-config
./upper/etc/default/keyboard
./upper/etc/default/irqbalance
./upper/etc/default/useradd
./upper/etc/default/dbus
./upper/etc/default/alsa
./upper/etc/default/zfs
./upper/etc/default/cron
./upper/etc/default/saned
./upper/etc/default/intel-microcode
./upper/etc/default/sssd
./upper/etc/default/crda
./upper/etc/default/networkd-dispatcher
./upper/etc/default/openvpn
./upper/etc/default/avahi-daemon
./upper/etc/default/ufw
./upper/etc/default/grub.d/
./upper/etc/default/grub.d/init-select.cfg
./upper/etc/default/apport
./upper/etc/default/anacron
./upper/etc/default/locale
./upper/etc/default/rsync
./upper/etc/default/acpid
./upper/etc/passwd-
./upper/etc/group-
./upper/etc/hosts
./upper/etc/xdg/
./upper/etc/xdg/autostart/
./upper/etc/xdg/autostart/screen-reader-profile.desktop
./upper/etc/gshadow
./upper/etc/.pwd.lock
./upper/etc/ssl/
./upper/etc/ssl/private/
./upper/etc/ssl/private/ssl-cert-snakeoil.key
./upper/etc/ssl/certs/
./upper/etc/ssl/certs/ssl-cert-snakeoil.pem
./upper/etc/ssl/certs/1c7314a2.0
./upper/etc/fonts/
./upper/etc/fonts/fonts.conf
./upper/etc/group
./upper/etc/systemd/
./upper/etc/systemd/sleep.conf
./upper/etc/systemd/networkd.conf
./upper/etc/systemd/system.conf
./upper/etc/systemd/user.conf
./upper/etc/systemd/journald.conf
./upper/etc/systemd/logind.conf
./upper/etc/systemd/system/
./upper/etc/systemd/system/snap-snap\\x2dstore-518.mount
./upper/etc/systemd/system/snap-gtk\\x2dcommon\\x2dthemes-1514.mount
./upper/etc/systemd/system/snap-gnome\\x2d3\\x2d34\\x2d1804-66.mount
./upper/etc/systemd/system/snap-snapd-11588.mount
./upper/etc/systemd/system/snap-core18-1997.mount
./upper/etc/systemd/pstore.conf
./upper/etc/systemd/timesyncd.conf
./upper/etc/systemd/resolved.conf
./upper/etc/fstab
./upper/etc/cups/
./upper/etc/cups/subscriptions.conf.O
./upper/etc/cups/subscriptions.conf
./upper/etc/cups/ppd/
./upper/etc/cups/ssl/
./upper/etc/casper.conf
./upper/etc/hostname
./upper/usr/
./upper/usr/lib/
./upper/usr/lib/update-notifier/
./upper/usr/lib/update-notifier/apt-check.distrib
./upper/usr/lib/update-notifier/apt-check
./upper/usr/lib/x86_64-linux-gnu/
./upper/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
./upper/usr/lib/x86_64-linux-gnu/libselinux.so.1
./upper/usr/lib/x86_64-linux-gnu/libdl-2.33.so
./upper/usr/lib/x86_64-linux-gnu/libcap-ng.so.0.0.0
./upper/usr/lib/x86_64-linux-gnu/libnss_files-2.33.so
./upper/usr/lib/x86_64-linux-gnu/libpthread-2.33.so
./upper/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0.10.1
./upper/usr/lib/x86_64-linux-gnu/libargon2.so.1
./upper/usr/lib/x86_64-linux-gnu/plymouth/
./upper/usr/lib/x86_64-linux-gnu/plymouth/plymouth-update-initrd
./upper/usr/lib/x86_64-linux-gnu/plymouth/plymouth-populate-initrd
./upper/usr/lib/x86_64-linux-gnu/plymouth/renderers/
./upper/usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/tribar.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/script.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/details.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/text.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/ubuntu-text.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/two-step.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/label.so
./upper/usr/lib/x86_64-linux-gnu/plymouth/plymouth-generate-initrd
./upper/usr/lib/x86_64-linux-gnu/libgpg-error.so.0.29.0
./upper/usr/lib/x86_64-linux-gnu/libc-2.33.so
./upper/usr/lib/x86_64-linux-gnu/libdevmapper.so.1.02.1
./upper/usr/lib/ubuntu-release-upgrader/
./upper/usr/lib/ubuntu-release-upgrader/check-new-release-gtk.distrib
./upper/usr/lib/ubuntu-release-upgrader/check-new-release-gtk
./upper/usr/lib/ubuntu-release-upgrader/check-new-release
./upper/usr/lib/ubuntu-release-upgrader/check-new-release.distrib
./upper/usr/lib/udev/
./upper/usr/lib/udev/rules.d/
./upper/usr/lib/udev/rules.d/60-cdrom_id.rules
./upper/usr/lib/systemd/
./upper/usr/sbin/
./upper/usr/sbin/update-initramfs
./upper/usr/sbin/anacron.distrib
./upper/usr/sbin/anacron
./upper/usr/sbin/update-initramfs.distrib
./upper/usr/share/
./upper/usr/share/glib-2.0/
./upper/usr/share/glib-2.0/schemas/
./upper/usr/share/glib-2.0/schemas/gschemas.compiled
./upper/usr/share/glib-2.0/schemas/casper.gschema.override
./upper/usr/share/fonts/
./upper/usr/share/fonts/truetype/
./upper/usr/share/fonts/truetype/ubuntu/
./upper/usr/share/fonts/truetype/ubuntu/UbuntuMono-R.ttf
./upper/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf
./upper/usr/share/fonts/truetype/dejavu/
./upper/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf
./upper/usr/share/applications/
./upper/usr/share/applications/ubiquity.desktop
./upper/tmp/
./upper/tmp/debconf.O5h904/
./upper/tmp/debconf.O5h904/config.dat
./upper/tmp/debconf.O5h904/passwords.dat
./upper/tmp/debconf.O5h904/debconf.conf
./upper/tmp/debconf.O5h904/config.dat-old
./upper/tmp/debconf.ZX2emw/
./upper/tmp/debconf.ZX2emw/config.dat
./upper/tmp/debconf.ZX2emw/passwords.dat
./upper/tmp/debconf.ZX2emw/debconf.conf
./upper/tmp/debconf.ZX2emw/config.dat-old

I'm running 21.04

#1092

@C.S.Cameron,

Thanks. The content of the log files is not enough for me to tell what is wrong for you.

It is hard to tell what makes your apps and settings fail, and if they should work (similar to in a persistent live system). For example, autostart won't work unless you log out and log in again, because this manual overlay has not happened, when the live system gets to the desktop at boot.

But installed programs should work and (of course) stored documents and pictures. Tweaks for installed programs should also work, for example font size and stored links in the web browser and in the text editor and command line.

Please suggest an application program and a setting, that won't work for you, and I will test it in Ubuntu 21.04.2.0 LTS (that I downloaded via torrent a few minutes ago).

Edit:

I tested now (with 20.04.2.0 LTS and 21.04), made persistent live with mkusb-dus) and

  • installed and tweaked geany - it works (also tweaks and settings are remembered)
  • installed mkusb from ppa:mkusb/unstable - it works
  • tweaked gnome-terminal - it was forgotten, but the command history (stored in ~/.bash_history) works. After some testing I found that if I log in to a text screen and run extractor4live and then log in to the graphics again, and start gnome-terminal, the tweaks are remembered. So obviously, when gnome-terminal is running the active settings override those stored in a file.

I think this illustrates what can happen. Installed programs remain, and also their settings, but things that are started before the manual overlay with extractor4live will not be modified.

Maybe we are ready for a decision:

  • Is this a good alternative to creating an own iso file to get a custom live system?
  • Or is this too complicated and/or flaky to be part of mkusb? (I guess, that you think so.)
  • Maybe it is enough to offer it as a manual tweak for advanced users, who want a simple method to get a custom live drive, that does not save the history (beyond what was saved in the tarball).

@everybody,

All readers who are interested are welcome to this discussion.

#1093

First thing tomorrow

#1094

@sudodus

I wrote an RC of Debian bullseye (*amd64; lxqt with non-free*) to thumb-drive using persistence (i forget the settings; msdos, then accepting what it offered I think for all).

lsblk -o MODEL,NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE "/dev/sdb"
MODEL        NAME   FSTYPE  LABEL                          MOUNTPOINT  SIZE
Cruzer_Facet sdb                                                       7.5G
             |-sdb1 ntfs    usbdata                                    2.1G
             |-sdb2                                                      1K
             |-sdb3 vfat    usbboot                                    244M
             |-sdb4 iso9660 d-live nf blsy-DI-rc2 lx amd64               3G
             `-sdb5 ext4    persistence                                2.1G

It was booted on

- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

monitor setup changed to reflect my box; sudo apt update; sudo apt full-upgrade; install neofetch, aptitude, cowsay, figlet (*stuff that makes me feel at home*;* I'm weird*).

system rebooted & subsequent boot everything is exactly as expected.

Next boot is on

- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

and the only thing mixed up is the monitor configuration; but that is something I expect as the box have different video card & though this & prior box share the same monitors, they aren't the same cards and I have no issues changing that around when I use different boxes (*I've come to expect it*).

Next boot was on

- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

and system was perfect.

My plan was to boot it on other boxes; but I'm too tired now.

Most of my [pre-release] *bullseye *testing was *i386* and not *amd64*, so this RC won't be the latest (*and thus different to the released ISO*), the number of updates subsequently were ~not minor - yet subsequent boots had neofetch & all attempts to sudo apt update; sudo apt full-upgrade resulted in no updates.

To me this was a perfect test. :)

I can test *i386* if helpful, or explore this further (*as I'd intended, but I'm too tired now and won't remember this tomorrow so writing up what I did*)

ISO was written with

guiverc@d960-ubu2:/de2900/debian/amd64$   apt-cache policy mkusb
mkusb:
  Installed: 12.7.1-1ubuntu1
  Candidate: 12.7.1-1ubuntu1
  Version table:
 *** 12.7.1-1ubuntu1 500
        500 http://ppa.launchpad.net/mkusb/unstable/ubuntu impish/main amd64 Packages
        500 http://ppa.launchpad.net/mkusb/unstable/ubuntu impish/main i386 Packages
#1095

Thanks for this test @guiverc :-)

#1096

Using [COLOR="#0000FF"]mkusb 12.7.0[/COLOR], I have come across some unusual behaviour.

I tested this with ubuntu-20.04-desktop-amd64.iso. After the usb device was created and then booting in UEFI mode:-

USB with persistence - UEFI Firmware Setup menu item is missing in Grub USB without persistence - UEFI Firmware Settings is available in Grub

This behaviour also occurs with the Windows application Rufus 3.15

More information in posts 93 and 94 here https://ubuntuforums.org/showthread.php?t=2465291&page=10

#1097

@tea for one,

Thanks for the feedback :-)

The option to enter the firmware is there in a live-only USB drive (without persistence) because mkusb clones the iso file, and it is there (in the grub.cfg file from the iso file).

This means that it will also be there is a persistent live drive made by mkusb-plug because it it almost cloning, using sed and replacing


'quiet splash' with 'persistent  '

In previous versions of Ubuntu mkusb-dus could tweak the grub.cfg from the iso file and make it work, but after some modifications of the boot structure in 20.04 LTS, it is no longer possible, so mkusb must use usb-pack-efi, and there is no call to get into the UEFI/BIOS menus there. It should be possible for me to add that feature. I will think about it ...

#1098

@sudodus

I've been successfully using [COLOR="#0000FF"]mkusb[/COLOR] for a few years now. Today was the first time using [COLOR="#0000FF"]mkusb-plug[/COLOR].

The usb drive was created without difficulty and persistence was added during the first boot of the live session. UEFI Firmware Settings was present in the Grub menu (exactly as you mentioned)

Thank you for your advice

Cheers

#1099

[SIZE=4]Persistent live server[/SIZE]

mkusb can clone most Linux iso files but can make persistent live drives only for Ubuntu Desktop, the community flavours (Kubuntu, Lubuntu ... Xubuntu), Debian live and some respins (distros based on Ubuntu and Debian, where the boot structure is not changed too much).

mkusb cannot make persistent live drives from Ubuntu Server iso files. But you can use the following command line for Ubuntu Live Server 20.04.3 LTS,


sed -e 's# append   initrd=/casper/initrd quiet  ---#append initrd=/casper/initrd persistent --#' -e 's#\tlinux\t/casper/vmlinuz   quiet  ---#linux\t/casper/vmlinuz persistent --#' ubuntu-20.04.3-live-server-amd64.iso > persistent-ubuntu-20.04.3-live-server-amd64.iso

Copy and paste it into a terminal window. It is very important that you get it exactly correct. Otherwise it will fail. Explanation: Editing the iso file can be done within very strict limits. The total size must be preserved and only text strings should be modified. So I replace quiet and some whitespace and one hyphen with persistent both for booting via syslinux in BIOS mode and via grub in UEFI mode.

Now you can clone the modified iso file with a cloning tool, for example mkusb-dus or mkusb-plug, for example


dus persistent-ubuntu-20.04.3-live-server-amd64.iso

The result will be a persistent live drive, that works both in BIOS mode and UEFI mode.

[hr][/hr] To make the persistence useful you can switch to a virtual text screen with ctrl+alt+F3 (or ctrl+alt+F4 ... and back to the menu with ctrl+alt+F1).

#1100

Today (2021-10-16) I tested that mkusb can create working installer drives from a Windows 11 iso file


$ [COLOR="#0000CD"]dus Windows11_InsiderPreview_Client_x64_en-us__22000.iso[/COLOR] 
 dus 12.7.1 
live system or temporary superuser permissions
Drive that contains source file: /dev/sdb
Live drive, that is booted from: /dev/sda
Drive with a partition in fstab: /dev/nvme0n1
cands=1
sdc
Corsair_Voyager_GT_3.0
29,5G
usb
USB or memory card
p_target: target=/dev/sdc
target drive size = 32 GB
-------------------------------------------------------------------------------
live system or temporary superuser permissions
    mkusb-tow: Make Windows installer 
  source file: 'Windows11_InsiderPreview_Client_x64_en-us__22000.iso'
target device: '/dev/sdc'

MODEL            NAME FSTYPE LABEL  SIZE
Voyager GT 3.0   sdc               29,5G
umount: /dev/sdc: inte monterad.
--------------------------------------------------------------------------------
extracting the partition table with grub ...
size to extract (bytes) = 7742685184
7,21GiB 0:00:57 [ 128MiB/s] [================================================================================================================>] 100%            
----- cleanup after writing ------------------------------------------
28375 pts/2    00:00:00 watch-flush
/usr/sbin/mkusb-tow: rad 164: 28375 Avslutad                ( watch-flush "$size" "$tailfile" > /dev/null )
umount: /dev/sdc: inte monterad.
umount: /dev/sdc1: inte monterad.
umount: /dev/sdc2: inte monterad.
mount source file ...
mount: /tmp/tmp.RDf9u87oj9: VARNING: enhet skrivskyddad, monterad som endast läsbar.
mount target partition 1 ...
mount target partition 2 ...
iso file size (bytes) = 5497985024
extracting to FAT partition ...
     44,728,320 100%  146.08MB/s    0:00:00 (xfr#88, to-chk=0/104) 
    439,895,652 100%  166.53MB/s    0:00:02 (xfr#1, to-chk=0/1)
extracting to NTFS partition ...
  5,492,260,661 100%   96.67MB/s    0:00:54 (xfr#944, to-chk=0/1034)  
----- cleanup after writing ------------------------------------------
28919 pts/2    00:00:00 watch-flush
/usr/sbin/mkusb-tow: rad 164: 28919 Avslutad                ( watch-flush "$size" "$tailfile" > /dev/null )
umount: /dev/sdc: inte monterad.
umount: /dev/sdc1: inte monterad.
umount: /dev/sdc2: inte monterad.
--------------------------------------------------------------------------------
NAME MODEL            FSTYPE LABEL       MOUNTPOINT  SIZE NAME
sdc  Voyager GT 3.0                                 29,5G sdc
sdc1                  vfat   WININSTFAT              768M sdc1
sdc2                  ntfs   WinInstNtfs             6,5G sdc2
 Done :-) 
-------------------------------------------------------------------------------
clean if necessary and return
clean if necessary and return
$ 
#1101

I have made a jammy version of ppa:mkusb/unstable and of ppa:mkusb/ppa (the stable PPA). See the attached screenshot.

#1102

I have a requirement to shut the machine down and restart after returning to the premises with restricted physical access where I can't get back in until security will allow. Using a customised persistence usb stick.

I would like to edit the grub.cfg file to remove the requirement to press enter after removing media by adding "noprompt" after quiet splash. This works when manually editing the grub options on boot, *but it still requires the stick to be physically removed and re-inserted in order to boot again to the usb stick.*

I have scoured the internet for answers and others have asked this question in many forums, but not a single answer. I have read and re-read man pages and how-tos until I have spots before the eyes nobody seems at be able to solve this.

My customised usb is generated with Cubic then burned by MKUSB with persistence options. The base distribution for cubic is neon-user-20211021-0945.iso

The persistence works beautifully and works for my situation. I do not want a complete install on the USB stick, I want to use persistence.

My requirement is very simple. Remove both the prompt and the need to remove the stick to reboot.

#1103

@vidtek,

If you made the persistent live drive with mkusb-dus (not mkusb-plug), the file system where grub.cfg resides is writable, so you can mount the partition and edit it. Add the extra boot option 'noprompt' near the end of the line that starts with 'linux', in other words near 'persistent', and try if it works.

if you still must unplug the drive instead of only rebooting, I don't know what is the problem. *Maybe* it helps if you run


sudo partprobe
sync

in a terminal window and wait for a few seconds for things to settle down just before reboot.

#1104

sudodus said: @vidtek,

If you made the persistent live drive with mkusb-dus (not mkusb-plug), the file system where grub.cfg resides is writable, so you can mount the partition and edit it. Add the extra boot option 'noprompt' near the end of the line that starts with 'linux', in other words near 'persistent', and try if it works.

if you still must unplug the drive instead of only rebooting, I don't know what is the problem. *Maybe* it helps if you run


sudo partprobe
sync

in a terminal window and wait for a few seconds for things to settle down just before reboot.

Thanks @sudodus, I'll give it a go and report back. Tony.

EDIT: Well the grub.cfg edit works well, noprompt sorted, Thanks.

Unfortunately your other suggestion did not in real time. I also tried a reboot script with your suggestion:``` sudo partprobe && sync && /sbin/reboot


No joy.  Still requires the stick to be physically unplugged.
#1105

Just realized, editing the previous post doesn't send a notification to you...doh don't get old....

Well the grub.cfg edit works well, noprompt sorted, Thanks.

Unfortunately your other suggestion did not sort the unplugging-plugging issue in real time.

I also tried a reboot script with your suggestion: Code:

sudo partprobe && sync && /sbin/reboot

No joy. Still requires the stick to be physically unplugged/plugged.

Tony

#1106

@vidtek,

I'm glad that at least one of my tips works.

I'm afraid, that the problem with unplugging might be due to things happening in the computer's early boot sequences, for example that the content of some memory locations are not reset: Old content is still there, and those memory locations are not properly cleared by the UEFI/BIOS system at reboot. If that is the case, you can test the system in different computers and it might behave differently.

#1107

sudodus said: @vidtek,

I'm glad that at least one of my tips works.

I'm afraid, that the problem with unplugging might be due to things happening in the computer's early boot sequences, for example that the content of some memory locations are not reset: Old content is still there, and those memory locations are not properly cleared by the UEFI/BIOS system at reboot. If that is the case, you can test the system in different computers and it might behave differently.

Tried on both the other systems --same result on a Samsung 510 older laptop and a strix 270 motherboard with an i7 and 16gb ram. The main testing system runs a Gigabyte z68 with an i7 and 16gb ram. I also tried running scripts on the reboot command inside the .iso file system writing in cubic terminal mode, no difference.

In fact the scripts that purport to reset the usb subsystem don't work either. Nothing works like unplugging/replugging the stick. bugger.

I'm starting to think of an electronic solution rather than a software approach. Maybe inserting a small relay/switching i.c. in the usb cable to simulate the unplugging/plugging action. What do you think? Maybe there is a powered usb hub that I can get off the shelf that disconnects the usb when power is removed-that would work in a remote system with a smart wall plug...time for a google hunt. Tony.

#1108

OK I have been through my mountain of computer stuff and pulled out an Anker 7port with 3 power only usb3 powered hub.

I tried in my workshop to see if when the power was removed the usb hub was reset as though unplugged from the host computer.

It was, the little blue active light went off, the hub was disconnected and I was able to reboot the computer without physically unplugging the usb stick.

So a work-around, not the most elegant solution, a software approach built-in to the live system would have been far more elegant but this works for my application. I have tested it with a smart plug and even using google assistant voice control I was able to achieve my goal. The timing is critical, disconnect too early in the reboot process and it will cause the machine to hang (as the usb stick is the current o/s), too late and the bios boot process will already have started.

If anyone can come up with a way to achieve the same result by removing the way a live system insists on a replug that would be far better.

Thanks to @sudodus for your help:cool:.

Tony.

https://uk.anker.com/products/a7515

#1109

@vidtek,

Thanks for sharing your solution :-)

#1110

I'm wanting to make a 20.04.3 boot usb device. I used "clone" and although I could boot up okay from the usb, it went to a desktop and no options/functions/menus ??

So am now using a "live" version and will see how that goes. But I'm sure it has worked before with just a "clone".

#1111

@oygle,

Are you talking about the following two options in an mkusb menu,

  • Cloning iso file, [compressed] image file or device
  • 'Live-only' or linux installer from iso file

and their influence on the result, the live system?

Both are cloning, doing exactly the same thing. It is only in order to catch the different 'user notions' of what should happen, that there are two options in the menu.

But if you select

  • 'Persistent live' - only Debian and Ubuntu

you get something very different, and you *can* run such a drive live (live-only) too, there is a grub menuentry for it.

[hr][/hr] Please explain the problem with a desktop and no options/functions/menus.

  • Was that when the created live system booted? Or when the installed system booted? Or something else, that I cannot guess?
  • Can you reproduce it (in the same computer, in some other computer, with some other version/flavour of Ubuntu)?

I suspect that it is a problem with the graphics, that the driver does not work well will the graphics hardware. Maybe you can work around it with some boot option, for example 'nomodeset'?

#1112

@sudodus, thank you for your reply. I had initially wanted to make a WIN 8.1 drive as dual boot, and add Kubuntu 20.04.3 - see https://ubuntuforums.org/showthread.php?t=2468850&p=14066766#post14066766 for the last reply.

I'm up to the "hair pulling out" phase, it really does seem that WIndows keeps gaining control and even when I'm able to boot from the usb, all that appears is the desktop (as per pic in that thread). As I only _really_ need the Windows for old MS Money conversions and some old works conversions, and all of those done from time to time, I may just wipe the WIN 8.1, even though I can't see/view the files. I think I only used it for the conversion to QIF format then exported to another computer.

So I think now the only optoin is to wipe/clobber from BIOS, it takes a few hours, but oh well. I'm sure the problem isn't mkusb, as I have used it successfully before, and from memory, all I did was a "clone". Thanks for your help

#1113

@oygle,

When that Probook is without a screen, but there is an external monitor, it is possible that Kubuntu 'thinks' that there is still an internal screen and sends options/functions/menus into cyberspace but none of that to the external monitor.

I'm thinking of my Dell Precision with nvidia graphics, that I connect to a TV. I have the options/functions/menus in the internal screen and can drag windows to the TV and make them fullscreen and enjoy (for example streamed movies or slideshows).

That is the default setting. I'm not sure if there is an option to send the same video to both screens or to only send video to the external screen (monitor). There might be options for that but not easy to identify without the internal screen.

Anyway, I would not blame Windows for it.

#1114

sudodus said: @oygle,

When that Probook is without a screen, but there is an external monitor, it is possible that Kubuntu 'thinks' that there is still an internal screen and sends options/functions/menus into cyberspace but none of that to the external monitor.

Could be,

sudodus said: That is the default setting. I'm not sure if there is an option to send the same video to both screens or to only send video to the external screen (monitor). There might be options for that but not easy to identify without the internal screen.

There are options in Kubuntu to "sync", etc, but I'm not able to get that far with it. Even when I read up on grub and dropped into the options at boot time and select "text graphics" or some option like that, it still went to the desktop view and just hung there.

It's all forced me to re-evaluate my "need" for Windows. Single boot has worked many times on that laptop, meaning fresh installs by using a usb. I'll steer clear of dual booting on that laptop. The no screen/external monitor may be compounding the issues. Have successfully done a VM on Kubuntu in the past with a WIN 8 running in the VM, so that looks like the only way to have Kubuntu and WIN 8.1

The BIOS 'secure erase' is running now, so _should_ have a clean/clear Kubuntu boot after that. Thanks for your help. :)

#1115

I'll make comment here, but I can't currently rule out user-error (ie. *it could still be me*).

I failed trying to write a newly zsync'd ubuntu jammy ISO to thumb-drive

guiverc@d960-ubu2:/de2900/ubuntu_64$   sudo dus jammy-desktop-amd64.iso
 dus 12.7.2 
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
cands=1
sdb
SanDisk_Cruzer_Facet
 7.5G
usb
USB or memory card
p_target: target=/dev/sdb
target drive size = 8 GB
 Clone/extract  system from the source
'jammy-desktop-amd64.iso'
to the target device (drive) '/dev/sdb'
MODEL        NAME FSTYPE  LABEL                   SIZE
Cruzer Facet sdb  iso9660 Ubuntu 22.04 LTS amd64  7.5G
             sdb1 iso9660 Ubuntu 22.04 LTS amd64  3.9G
             sdb2 vfat    ESP                     4.1M
             sdb3                                 300K
             sdb4 ext4    writable                3.6G
jammy-desktop-amd64.iso
/dev/sdb
-----
source=jammy-desktop-amd64.iso
target=/dev/sdb
source=jammy-desktop-amd64.iso
ls -l  jammy-desktop-amd64.iso
-rw------- 1 guiverc guiverc 3246626816 Dec 29 07:57 jammy-desktop-amd64.iso
Making a USB boot drive or memory card ..........................
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /tmp/dus.ZicJXjqvcW: failed to setup loop device for /de2900/ubuntu_64/jammy-desktop-amd64.iso.
umount: /tmp/dus.ZicJXjqvcW: not mounted.
gpt_zap: done

Installing 'jammy-desktop-amd64.iso' to '/dev/sdb' ... :

/usr/bin/pv
< "jammy-desktop-amd64.iso" pv -s 3246626816 | dd bs=4096  of=/dev/sdb
 Please wait for sync until 'Done' is written.
 If there is a progress window,
 wait for the buffered data to get flushed 
 so that all data are transferred to the target device.
/usr/bin/watch-flush
dd: failed to open '/dev/sdb': Operation not permitted
0.00 B 0:00:00 [0.00 B/s] [>                                                                                     ]  0%            
Syncing the device ...
----- cleanup after writing ------------------------------------------
 500040 pts/2    00:00:00 watch-flush
umount: /dev/sdb: not mounted.
umount: /dev/sdb1: not mounted.
umount: /dev/sdb2: not mounted.
umount: /dev/sdb3: not mounted.
umount: /dev/sdb4: not mounted.
 Failed :-( 

and just experienced the same with Lubuntu's ISO too.

** prior ISO
calamares    3.2.41.1-0ubuntu2
calamares-settings-lubuntu    1:22.04.1
calamares-settings-ubuntu-common    1:22.04.1
casper    1.465
lubuntu-default-settings    22.04.1
lupin-casper    0.57build1
** latest ISO
calamares    3.2.41.1-0ubuntu2
calamares-settings-lubuntu    1:22.04.1
calamares-settings-ubuntu-common    1:22.04.1
casper    1.465
lubuntu-default-settings    22.04.1
lupin-casper    0.57build1
** diff
guiverc@d960-ubu2:/de2900/lubuntu_64$   dus jammy-desktop-amd64.iso
 dus 12.7.2 
[sudo] password for guiverc: 
live system or temporary superuser permissions
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
cands=1
sdb
Verbatim_STORE_N_GO
14.4G
usb
USB or memory card
p_target: target=/dev/sdb
target drive size = 16 GB
live system or temporary superuser permissions
 Clone/extract  system from the source
'jammy-desktop-amd64.iso'
to the target device (drive) '/dev/sdb'
MODEL      NAME FSTYPE  LABEL                    SIZE
STORE N GO sdb  iso9660 Lubuntu 22.04 LTS amd64 14.4G
           sdb1 iso9660 Lubuntu 22.04 LTS amd64  1.9G
           sdb2 vfat    ESP                      4.1M
           sdb3                                  300K
           sdb4 ext4    writable                12.5G
jammy-desktop-amd64.iso
/dev/sdb
-----
live system or temporary superuser permissions
source=jammy-desktop-amd64.iso
target=/dev/sdb
source=jammy-desktop-amd64.iso
ls -l  jammy-desktop-amd64.iso
-rw------- 1 guiverc guiverc 2040582144 Dec 29 16:53 jammy-desktop-amd64.iso
Making a USB boot drive or memory card ..........................
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /tmp/dus.FiwfRzQjwk: failed to setup loop device for /de2900/lubuntu_64/jammy-desktop-amd64.iso.
umount: /tmp/dus.FiwfRzQjwk: not mounted.
gpt_zap: done

Installing 'jammy-desktop-amd64.iso' to '/dev/sdb' ... :

/usr/bin/pv
< "jammy-desktop-amd64.iso" pv -s 2040582144 | dd bs=4096  of=/dev/sdb
 Please wait for sync until 'Done' is written.
 If there is a progress window,
 wait for the buffered data to get flushed 
 so that all data are transferred to the target device.
/usr/bin/watch-flush
dd: failed to open '/dev/sdb': Operation not permitted
0.00 B 0:00:00 [0.00 B/s] [>                                                                                     ]  0%            
Syncing the device ...
----- cleanup after writing ------------------------------------------
 512185 pts/4    00:00:00 watch-flush
umount: /dev/sdb: not mounted.
umount: /dev/sdb1: not mounted.
umount: /dev/sdb2: not mounted.
umount: /dev/sdb3: not mounted.
umount: /dev/sdb4: not mounted.
 Failed :-( 

I also tried a dd with the Ubuntu ISO

guiverc@d960-ubu2:/de2900/ubuntu_64$   sudo dd bs=4M oflag=sync status=progress of=/dev/sdb if=/de2900/ubuntu_64/jammy-desktop-amd64.iso
dd: failed to open '/dev/sdb': Operation not permitted

FYI: sudo dus & my usual dus were tried (with both); no difference.

I've not explored this; for now I want to focus on what I'm trying to test for a bug comment & don't want to be distracted.

I used gnome-disks to write the Ubuntu ISO to thumb-drive without issue, and it's writing the Lubuntu ISO now as I type this. Probably of no significance, but I'm using Xfce/Xubuntu as a desktop (*instead of my far more common LXQt/Lubuntu*)``` guiverc@d960-ubu2:/de2900/lubuntu_64$ apt-cache policy mkusb mkusb: Installed: 12.7.2-1ubuntu1 Candidate: 12.7.2-1ubuntu1 Version table: *** 12.7.2-1ubuntu1 500 500 http://ppa.launchpad.net/mkusb/unstable/ubuntu jammy/main amd64 Packages 500 http://ppa.launchpad.net/mkusb/unstable/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status

#1116

@guiverc,

The error message


dd: failed to open '/dev/sdb': Operation not permitted

both for mkusb and 'plain dd' indicates a fundamental problem. I think that either the management of block devices (in the operating system) is corrupted in the host operating system (the Xfce/Xubuntu that you were using as a desktop) or that the USB drive is failing (for example that it is gridlocked (at least temporarily). Gridlock is a first step of failure, that a USB pendrive is read-only, that the hardware is read-only. See this link.

But it makes me confused that it works with Disks ...

[hr][/hr] If you tell me which version of Xubuntu that you were running when mkusb failed, I can install such a system (and make it up to date), install mkusb and try with a current Ubuntu jammy ISO file. (Actually I think that kind of failure would affect every iso file.)

#1117

Yeah it must have been the Xfce session I was using...

A logout & switch to Lubuntu/LXQt (*my system is a multi-desktop system meaning I've multiple desktops installed selected at login*) and I could write the same ISO to the same thumb-drive without issue (it's a *jammy* system updated three+ times per day)

(*the only difference being it'd been written by gnome-disks so no image change was occurring - again a almost certainly moot point*)

I zsync'd the Xubuntu *jammy *daily & am using it now in a *live* session on another box and the write of Lubuntu *focal* is occurring as expected.. ie. no issues on a pure Xubuntu jammy daily (2021-12-31) that's doesn't have all packages *up to date *but should be equivalent to what I used for my last post (#1113) (*it hasn't finished write yet; but it'll get there; it's a thumb-drive that flashes & everything looks just as it should)*

Sorry for the likely misleading last post - some *unique issue* on my box with the desktop/session that had been running ~seven days.

*Development releases are that; problems will occur on occasion... just not expecting them currently given few updates are occurring with much of Canonical/folks on leave...*

#1118

@guiverc,

I appreciate the early warning, and you are welcome again, when something similar is happening.

Finally, thanks for resolving this issue :-)

#1119

@sudodus - I usually select option "e" to make a boot usb with mkusb. At boot I don't get an option to select either UEFI or legacy. Is it because of the option I select with mkusb or is it simply a BIOS limitation ?? See https://ubuntuforums.org/showthread.php?t=2473650

#1120
  1. Are you using the old version mkusb-11? Is this what you mean by 'I usually select option "e" to make a boot usb with mkusb'?

In that case I suggest that you try with "d" or "p", which start newer versions:


$ mkusb
---------------------------------------------------------------------
Usage: mkusb [input-file]      # optional parameter
---------------------------------------------------------------------
d:  dus , guidus, mkusb-dus    - Classic, easy to use
p: Plug,   mkusb-plug          - New, easy to use
n: NoX,    sudo mkusb-nox      - original text mode
b: Bas,    sudo mkusb-bas      - basic text mode for old/basic linux
e: Eleven, sudo -H mkusb-11    - Old user interface
q: Quit
---------------------------------------------------------------------
Select version of mkusb (d/p/n/b/e/q)

The newer versions are developed and tweaked to work well with the current versions of Ubuntu and Ubuntu family flavours (Kubuntu, Lubuntu ... Xubuntu).

  1. Are you creating a live-only installer (usually by cloning), or a persistent live drive?

Generally, if you want to install Ubuntu or an Ubuntu flavour, it is easier with a live-only (cloned) installer in your USB drive. The installer system in the USB drive can boot and install both in legacy mode (alias CSM alias BIOS mode) and in UEFI mode.

  • If booted in legacy mode at the installation, the installed system will be installed in legacy mode.
  • If booted in UEFI mode at the installation, the installed system will be installed in UEFI mode.
  1. The selection of boot mode (legacy mode or UEFI mode) is done before Ubuntu (or any other operating system) starts. So you should select that by modifying the setting in a UEFI-BIOS settings menu or via a temporary menu, often via the hotkey F12 in Dell computers. Press or tap F12 repeatedly directly at boot.
#1121

sudodus said:

  1. Are you using the old version mkusb-11? Is this what you mean by 'I usually select option "e" to make a boot usb with mkusb'?

In that case I suggest that you try with "d" or "p", which start newer versions:

synaptic says 12.7.2 for mkusb, but it got updated this morning, so it would have been the version prior to that.

sudodus said:

  1. Are you creating a live-only installer (usually by cloning), or a persistent live drive?

Yes, live only.

sudodus said:

  1. The selection of boot mode (legacy mode or UEFI mode) is done before Ubuntu (or any other operating system) starts. So you should select that by modifying the setting in a UEFI-BIOS settings menu or via a temporary menu, often via the hotkey F12 in Dell computers. Press or tap F12 repeatedly directly at boot.

Okay thanks for all your help, much appreciated. :)

#1122

This time I selected option p then c (clone). There were extra messages about ISO files ; I selected "I don't know" twice ??

mkusb kubuntu-21.10-desktop-amd64.iso

---------------------------------------------------------------------

Usage: mkusb [input-file] # optional parameter --------------------------------------------------------------------- d: dus , guidus, mkusb-dus - Classic, easy to use p: Plug, mkusb-plug - New, easy to use n: NoX, sudo mkusb-nox - original text mode b: Bas, sudo mkusb-bas - basic text mode for old/basic linux e: Eleven, sudo -H mkusb-11 - Old user interface q: Quit --------------------------------------------------------------------- Select version of mkusb (d/p/n/b/e/q) p live system or temporary superuser permissions source file: 'kubuntu-21.10-desktop-amd64.iso' --cloner spawn bash -c xorriso-dd-target -plug_test -trust_lsblk_udev | tee /tmp/tmp.Vb37rMGYkY

Caused by option -plug_test: Attempt to find the desired device by watching it appear after being plugged in.

Step 1: Please make sure that the desired target device is plugged _out_ now. If it is currently plugged in, make sure to unmount all its fileystems and then unplug it. Press the Enter key when ready.

Found and noted as _not_ desired: sda

Step 2: Please plug in the desired target device and then press the Enter key.

Waiting up to 10 seconds for a new device to be listed ... found: sdb Now waiting 5 seconds to let it settle ......... Found and noted as desired device: sdb

sdb : NO : usb+ has_iso9660+ has_vfat+ has_ext4- : Kingston DataTraveler_2.0 Repeating test of target device with elevated permissions: Testing sudo to possibly get password prompting done now: sudo /bin/lsblk seems ok.

target device: /dev/sdb sdb : NO : usb+ has_iso9660+ has_vfat+ has_ext4- : Kingston DataTraveler_2.0 task: '--cloner' source file: 'kubuntu-21.10-desktop-amd64.iso' target device: /dev/sdb

MODEL NAME FSTYPE LABEL SIZE DataTraveler_2.0 sdb iso9660 Kubuntu 21.10 amd64 3.7G sdb1 iso9660 Kubuntu 21.10 amd64 3.1G sdb2 vfat ESP 4.1M sdb3 300K sdb4 ext4 writable 602M *** cloner *** Trying to unmount partitions if mounted on the target device umount: /dev/sdb: not mounted. umount: /dev/sdb1: not mounted. umount: /dev/sdb2: not mounted. umount: /dev/sdb3: not mounted. umount: /dev/sdb4: not mounted. -------------------------------------------------------------------------------- Please wait until the cloning has finished and 'Done' is written 3372374016=file size 3371171840 bytes (3.4 GB, 3.1 GiB) copied, 545 s, 6.2 MB/s 3216+1 records in 3216+1 records out 3372374016 bytes (3.4 GB, 3.1 GiB) copied, 545.446 s, 6.2 MB/s ----- cleanup after dd ------------------------------------------ 4806 pts/1 00:00:00 mkusb-sedd Warning: Not all of the space available to /dev/sdb appears to be used, you can fix the GPT to use all of the space (an extra 1236692 blocks) or continue with the current setting? Finally, please wait for a few more seconds ... -------------------------------------------------------------------------------- NAME MODEL FSTYPE LABEL MOUNTPOINT SIZE NAME sdb DataTraveler_2.0 iso9660 Kubuntu 21.10 amd64 3.7G sdb sdb1 iso9660 Kubuntu 21.10 amd64 3.1G sdb1 sdb2 vfat ESP 4.1M sdb2 sdb3 300K sdb3 Done :-)

#1123

@oygle,

Yes, there is a lot of output (but no indication of a serious problem).

What about the result? Is the created USB drive working well for you?

[hr][/hr] You find details about using mkusb-plug at this link.

#1124

sudodus said: @oygle,

Yes, there is a lot of output (but no indication of a serious problem).

What about the result? Is the created USB drive working well for you?

I have used the usb created by mkusb to now complete the installation. used it many times to live boot to enable partition changes and do the install, and now it seems the boot has transitioned from Legacy to UEFI. So yes, the USB is working well for me, thanks for your help. :)

#1125

I made usb using Jammy Jellyfish daily iso with persistence. I could run firefox on first boot but when rebooted saving settings firefox didn't open. I tried opening through terminal $ firefox snap-confine has elevated permissions and it is not confined but should be. Refusing to continue to avoid permission escalation attacks

Kamalakar

#1126

@sudodus

This is preliminary, but I'm short of time and thus may have little time to clean up what I have currently...

ISO Tracker page - http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246983/testcases/1303/results

The entries there show a ISO written with mkusb-plug

You'll note it booted fine on many boxes, however if FAILED to boot on

  • hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  • hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)

This is not the first failure I've had, but I didn't explore a prior failure as much as I've done today... (I just re-wrote with dus & tested... on next day I tested I had no issues, but mkusb-plug appears to be box *firmware *specific, and it doesn't like the old HP's)

The same ISO however written using dus jammy<tab>iso boots perfectly on those boxes.... (*dc7700 only at this stage actually*)

so mkusb-plug appears to create an issue for old & slow HP boxes??

Bug report filed as https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290 and filed against casper (it's new; 1.470) - however the same ISO written boots when I use dus thus the current 'incomplete' status..

#1127

kagashe said: I made usb using Jammy Jellyfish daily iso with persistence. I could run firefox on first boot but when rebooted saving settings firefox didn't open. I tried opening through terminal

$ firefox snap-confine has elevated permissions and it is not confined but should be. Refusing to continue to avoid permission escalation attacks

Kamalakar

Thanks for this feedback :-)

  • Which flavour of Ubuntu are you using (standard Ubuntu or one of the flavours (Kubuntu, Lubuntu, ... Xubuntu)?
  • Did you make the persistent live drive using dus (mkusb v.12) or mkusb-plug?
  • Does Firefox in an *installed* system with Jammy work for you?
  • Can you use Firefox from an old style debian package via apt (not snap) in Jammy?

Do you think that this problem is a show stopper for the persistent live method?

#1128

@guiverc,

Thanks for this feedback :-)

I guess that you have problems when running a persistent live system made by mkusb-plug. Is that correct?

Did you have problems when running a cloned copy made by mkusb-plug? (If that happens, any cloning tool should fail to make good drives for those old HP computers).

Did it work when running a persistent live drive made by dus (mkusb v.12)? Maybe it would help to select MSDOS partition table at the settings menu of dus (according to my experience with some old HP computers).

#1129

sudodus said: Thanks for this feedback :-)

Standard Ubuntu but it is happening on Lubuntu as well

  • Which flavour of Ubuntu are you using (standard Ubuntu or one of the flavours (Kubuntu, Lubuntu, ... Xubuntu)?
  • Did you make the persistent live drive using dus (mkusb v.12) or mkusb-plug?

dus the version is latest on Ubuntu 20.04

  • Does Firefox in an *installed* system with Jammy work for you?

I don't intend to install on hard drive, I tried installing on another USB but the installation was not complete. I will try again today.

  • Can you use Firefox from an old style debian package via apt (not snap) in Jammy?

Jammy does not allow installation from apt if you try it installs snap package only. I tried reinstalling snap package it failed.

Do you think that this problem is a show stopper for the persistent live method?

I am going to try one more time with updated iso then I can tell you. Meanwhile someone reading this thread may try.

Kamalakar

#1130

kagashe said: Standard Ubuntu but it is happening on Lubuntu as well

I am going to try one more time with updated iso then I can tell you. Meanwhile someone reading this thread may try.

Kamalakar

I made new usb using updated Jammy daily iso and first booted without persistence. Firefox was working fine. I installed the system on another usb and checked the installed system on many reboots and Firefox is ok.

I switched to first usb and used persistence the Firefox was working fine. I rebooted to save wifi settings and Timezone and firefox is giving same error: $ firefox snap-confine has elevated permissions and it is not confined but should be. Refusing to continue to avoid permission escalation attacks

I googled and found previous bugs in other snap packages.

This has something to do with apparmor and may require some special boot parameter to disable apparmor

Do you think that this problem is a show stopper for the persistent live method?

Yes unless you find a workaround to disable apparmor

Kamalakar

#1131

@kagashe,

Thanks for the detailed tests and explanations :-)

I see, that this problem with Firefox in persistent live systems with Ubuntu Jammy is a show stopper because most people want to use Firefox :-(

I don't know if there is a good solution. An obvious workaround is an installed system in an external drive. There are instructions to create a portable installed system at this link.

#1132

sudodus said: @kagashe,

Thanks for the detailed tests and explanations :-)

I see, that this problem with Firefox in persistent live systems with Ubuntu Jammy is a show stopper because most people want to use Firefox

The show must go on, I have found a workaround!

In Live Persistent mode: $ sudo mkdir /lib/systemd/system/apparmor.service.d

to create a directory apparmor.service.d in /lib/systemd/system/

sudo gedit /lib/systemd/system/apparmor.service.d/30_live_mode.conf

to create config file in the new directory

Paste [Unit] ConditionPathExists=

Save and reboot.

AND Firefox works!

Kamalakar

NB: You can read the link workaround for details. You may consider to create the required folder and config file in mkusb if possible for Ubuntu 22.04

#1133

Thanks kagashe,

When I have time, I will try to fix this in the shellscript dus-persistent, and maybe later in mkusb-plug.

The reason why I plan to do it in dus-persistent is that there are 'similar' fixes for other problems there (and it should be easier than in mkusb-plug).

#1134

I submitted a Bug Report with workaround on Launchpad: Firefox fails to start in Ubuntu 22.04 Live USB persistent on reboot [URL="https://bugs.launchpad.net/apparmor/+bug/1969486"]https://bugs.launchpad.net/apparmor/+bug/1969486 [/URL]

Kamalakar

#1135

[SIZE=4]mkusb version 12.7.3, 12.7.4, 12.7.5[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

because of the program package exfat-utils changed name to exfatprogs in Jammy:

  • mkusb 12.7.3
  • control0: mkusb-plug: Recommends: pv, exfat-utils, exfatprogs

in order to make Firefox work in persistent live Jammy: . dus-persistent: apparmor.service.d/30_live_mode.conf: ConditionPathExists= . new files: fixfox and fixfox.desktop in autostart

  • mkusb 12.7.4

. dus-persistent: probe_source: upefi=true and grubimg=true for newer than 20.04 iso files or 21.04 host systems. This fixes a bug that stops booting in BIOS mode

  • mkusb 12.7.5

[/td][/tr][/table]

[SIZE=3]Improvement in program package mkusb version 12.7.3 [/SIZE]

'Only' a modification of the system file 'control0' used to create the debian package for the PPA.

[SIZE=3]Improvement in program package mkusb version 12.7.4 [/SIZE]

Workaround to make Firefox work after reboot of persistent live system of Jammy (22.04): Simply adding the necessary file to the partition for persistence did not work, but it works to add a desktop file and its 'exec-file' to 'autostart' to create 'apparmor.service.d/30_live_mode.conf' with ConditionPathExists=

Please notice that this fix for Firefox works automatically only with [FONT=Courier New]dus[/FONT] (mkusb-dus alias mkusb version 12), but not with mkusb-plug.

After booting into a persistent live Jammy system made by mkusb-plug you can run


sudo /path/to/fixfox

manually in a terminal window to make Firefox work also after reboot. You can extract fixfox from the attached file.

Version 12.7.4 is in the unstable PPA now, mkusb-dus can create Jammy persistent live systems of standard Ubuntu desktop and 6 desktop flavours, that I tested. Probably it works in the other desktop flavours too.

[FONT=Courier New]mkusb 12.7.4-1ubuntu3[/FONT]

  • fix for Firefox: dus-persistent: using name of '*ubuntu*.seed' in iso file to decide home directory of target system
  • (verified for kubuntu,lubuntu,ubuntu,ubuntu-budgie,ubuntu-mate,ubuntustudio and xubuntu).

[SIZE=3]Improvement in program package mkusb version 12.7.5 [/SIZE]

This is a bugfix in dus-persistent to make dus create persistent live drives that boot in BIOS mode also when the host system (where dus is running) is Ubuntu 22.04 or newer. It avoids mismatch between grub components from different versions by forcing not only using 'usb-pack-efi', but also 'grubimg', using an image file for the head of the target drive instead of letting the host system install grub.

See this link: https://bugs.launchpad.net/bugs/1971119

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 12.7.5 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1136

sudodus said: [SIZE=4]mkusb version 12.7.4[/SIZE]

Workaround to make Firefox work after reboot of persistent live system of Jammy (22.04): Simply adding the necessary file to the partition for persistence did not work, but it works to add a desktop file and its 'exec-file' to 'autostart' to create 'apparmor.service.d/30_live_mode.conf' with ConditionPathExists=

Please notice that this fix for Firefox works automatically only with [FONT=Courier New]dus[/FONT] (mkusb-dus alias mkusb version 12), but not with mkusb-plug.

Version 12.7.4 is in the unstable PPA now, and Firefox works for me, at least with standard Ubuntu and Lubuntu [persistent live made by dus]. Please test that it works for you too :-P [hr][/hr]

Downloaded and installed mkusb version 12.7.4 on Ubuntu 20.04, made new persistent usb using dus and tested. It works for me as well. Thank you for releasing this mkusb version just in time for Ubuntu 22.04 released on 21st April 2022.

Kamalakar

#1137

The fix in mkusb 12.7.4 to make Firefox work is tested and works in standard Ubuntu and in Lubuntu :-)

But when I tested it in Xubuntu Jammy it fails :-(

I have not tested it in any other flavour of Ubuntu Jammy, but obviously I have to improve and test it in all the official flavours of Ubuntu Jammy.

#1138

sudodus said: The fix in mkusb 12.7.4 to make Firefox work is tested and works in standard Ubuntu and in Lubuntu :-)

But when I tested it in Xubuntu Jammy it fails :-(

I have not tested it in any other flavour of Ubuntu Jammy, but obviously I have to improve and test it in all the official flavours of Ubuntu Jammy. Your script to automatically write the file 30_live_mode.conf is not working on Xubuntu.

I created the file manually on Xubuntu and it works.

Kamalakar

#1139

Now mkusb-dus can create Jammy persistent live systems of standard Ubuntu desktop and 6 desktop flavours, that I tested. Probably it works in the other desktop flavours too.

[FONT=Courier New]mkusb 12.7.4-1ubuntu3[/FONT]

  • fix for Firefox: dus-persistent: using name of '*ubuntu*.seed' in iso file to decide home directory of target system
  • (verified for kubuntu,lubuntu,ubuntu,ubuntu-budgie,ubuntu-mate,ubuntustudio and xubuntu).

This version is available via [FONT=Courier New]ppa:mkusb/unstable[/FONT]

#1140

Sudodus:

I have been testing 22.04 Full install to USB, https://askubuntu.com/questions/1403792/how-to-create-a-full-install-of-ubuntu-22-04-to-usb-device-step-by-step/1403793#1403793 Installation works pretty much the same as a 20.04 full install, except that I did not need to reinstall GRUB.

On my HP EliteBook both Ubuntu Beta and Lubuntu Beta have problems with mouse and trackpad and I think keyboard. There is no curser. Is 22.04 working on your son's EliteBook?

Today I downloaded 12.7.4 and gave it some preliminary testing. Both Live and Persistent 22.04 worked fine everywhere I tried, except for the mouse, trackpad and keyboard on the HP.

Firefox takes a while to open, but if I leave it alone it eventually boots.

I have not had a chance to try booting ISO's with 22.04 yet, maybe later today or this weekend.

Edit: The keyboard on the HP is now working.

#1141

@C.S.Cameron,

Thanks for testing mkusb 12.7.4 to make persistent live 22.04 :-)

My son's HP Elitebook is gone. Finally the built-in monitor stopped working. It was possible to run it with low graphics via an external monitor, but my son has a new[er] computer now. (This happened long before Jammy.)

I noticed that the mouse cursor was flaky in other (newer) laptops during a period of development of Jammy, but that problem seems fixed in the released version, Ubuntu desktop 22.04. I did not see that problem in Lubuntu.

#1142

Now mkusb-dus can create Jammy persistent live systems of Ubuntu Kylin too.

[FONT=Courier New]mkusb 12.7.4-1ubuntu4[/FONT]

  • fix for Firefox: dus-persistent: extra fix for Ubuntu Kylin

This version is available via [FONT=Courier New]ppa:mkusb/unstable[/FONT]

If you already installed mkusb12.7.4-1ubuntu3, please install dus to gets its current version dus12.7.4-1ubuntu4


sudo apt update
sudo apt install dus
#1143

Now the mkusb PPAs include the next version, Kinetic.

#1144

Made a persistent USB flash drive (Ubuntu 22.04) with mkusb. Have done this before with the development versions of Ubuntu 22.04. When I try to boot I get the error:

Code: --------- error: symbol 'grub_file_Filters_all' not found Entering rescue mode... grub rescue> _ --------- How can I correct this ?

#1145

Joe_Linux said: Made a persistent USB flash drive (Ubuntu 22.04) with mkusb. Have done this before with the development versions of Ubuntu 22.04. When I try to boot I get the error:

Code: --------- error: symbol 'grub_file_Filters_all' not found Entering rescue mode... grub rescue> _ --------- How can I correct this ?

Please help me troubleshooting by answering some questions and adding some detailed information:

  1. Which version of mkusb are you running
  • version number?
  • mkusb-dus or mkusb-plug?
  1. Was the installation of mkusb successful, or did you see and sign of failure?
  1. In which version of Ubuntu are you running mkusb? (20.04.x or 22.04 or some other version)?

4.Do I understand correctly that you try to make a persistent live system of Ubuntu 22.04?

5 Did you check with sha256sum that the iso file of the new Ubuntu was downloaded correctly?

  1. Please tell me the brand name, model name/number and size of your USB drive.
  1. Please tell me the brand name and model number of your computer.

[hr][/hr] and finally, please check if you can create a working live drive by using the *cloning* option in mkusb? (It can be a first step in getting a working persistent live drive.)

#1146

[SIZE=4]mkusb version 12.7.5[/SIZE]

. dus-persistent: probe_source: upefi=true and grubimg=true for newer than 20.04 iso files or 21.04 host systems. This fixes a bug that stops booting in BIOS mode

  • mkusb 12.7.5

[SIZE=3]Improvement in program package mkusb version 12.7.5 [/SIZE]

This bugfix in dus-persistent should make dus create persistent live drives that boot in BIOS mode also when the host system (where dus is running) is Ubuntu 22.04 or newer. It avoids mismatch between grub components from different versions by forcing not only using 'usb-pack-efi', but also 'grubimg', using an image file for the head of the target drive instead of letting the host system install grub.

See also this link: https://bugs.launchpad.net/bugs/1971119

@ Joe_Linux,

You found a bug. Please let me know if the bug is fixed in mkusb 12.7.5 installed via ppa:mkusb/unstable.

#1147

Can I use this software to create a persistent portable windows drive using Ubuntu?

#1148

mkusb can make live and persistent live Ubuntu drives. It can also create Windows installer drives, but *not* portable Windows drives. mkusb can also extract image files (and gzip and xz compressed image files, ball.tar.gz and ball.tar.xz).

It should be possible to use Rufus (in Windows) to create a portable Windows drive, but I have never tested it.

#1149

[SIZE=4]mkusb version 22.0.1 - 22.0.7[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. Added early version of dus-iso2usb (grub-n-iso) script. . Not yet called by dus, only for testing in text mode. . version 22.0.1 (year based: 2022 ---> 22)

. dus-iso2usb: readparams, addparts: added optional parameter #6, [FONT=Courier New]boot-flag[/FONT], plus extra warnings when large target drives . dus-iso2usb: copyiso: sleep to settle down to get syslbl . dus (itself): new functions p_toolsel and p_seti2u to prepare settings for the script dus-iso2usb . dus-iso2usb now called by dus, but final checkpoint still in text mode

. dus: p_seti2u: fixed other settings when msdos and/or boot-flag selected

. dus-iso2usb: add_parts: if statement for boot-flag also when live-only (alias not persistent)

. dus-iso2usb: read_params: warning and question if the source is not an Ubuntu [flavour] iso file . p_zentest and p_checkpoint added (to dus-iso2usb) . p_toolsel: p_clean and return after call of dus-iso2usb . p_checkpoint: extra question 'Are you sure ?' in text mode - mkusb 22.0.7 . p_toolsel: cleaner return after p_live and p_persistent . dus-iso2usb: read_params, p_checkpoint: fine-tuned output to terminal window [/td][/tr][/table]

  • mkusb 22.0.1
  • mkusb 22.0.3
  • mkusb 22.0.4
  • mkusb 22.0.5
  • mkusb 22.0.6

[SIZE=3]Improvement in program package mkusb version 22.0.1 [/SIZE]

Introduction of [FONT=Courier New][SIZE=3]dus-iso2usb[/SIZE][/FONT]

The first versions of the dus-iso2usb script work only in text mode. Later on it will be called by dus and menus and dialogue windows will be graphical using zenity. ../artwork/mkusb24.png or text based using dialog or even very basic text, if neither zenity nor dialog is available.

The main function of dus-iso2usb is to

  • extract the first partitions and the grub structure from compressed image files
  • create new partitions, one for an iso file labeled 'isodevice', and one optional for persistence labeled 'writable' (or in older systems labeled 'casper-rw').
  • copy iso file to 'isodevice' and add some tweaks.

This makes a system that can boot via grub into an iso file both in UEFI mode and BIOS mode (alias CSM alias legacy mode), 'grub-n-iso'. The following link describes how to do it manually.

help.ubuntu.com/community/Installation/iso2usb/isoboot

help.ubuntu.com/community/Grub2/ISOBoot


$ dus-iso2usb -h
Usage:
sudo -H dus-iso2usb <source> <target> <part-tbl> <grub-ver> <persistent or live-only>
Example:
sudo -H dus-iso2usb lubuntu-22.04-desktop-amd64.iso /dev/sdc gpt grub-2.0.6 persistent
param 1: source file
param 2: target drive
param 3: partition table: gpt or msdos
param 4: grub version: grub-2.0.6 or grub-2.0.4
param 5: persistent or live-only
Help:
 -h
Version:
 -v
Available drives 
NAME      SIZE TRAN   MODEL
sda     238,5G sata   SanDisk SD6SB1M2
sdb       3,7T sata   WDC WD4002FYYZ-0
sdc      55,9G usb    ITY3            
nvme0n1 232,9G nvme   KINGSTON SA2000M8250G
$ 
$ 
$ sudo -H dus-iso2usb lubuntu-18.04.5-desktop-amd64.iso /dev/sdc gpt grub-2.0.6 persistent
 dus-iso2usb 22.0.1 
start [dus-iso2usb 22.0.1] @ 2022-05-11 10:56:09
 source file: 
lubuntu-18.04.5-desktop-amd64.iso
target drive size = 60 GB
 target drive: 
MODEL            NAME     SIZE FSTYPE LABEL     MOUNTPOINT
ITY3             sdc     55,9G                  
                 &#9500;&#9472;sdc1   977K                  
                 &#9500;&#9472;sdc2 244,1M vfat   usbboot   
                 &#9500;&#9472;sdc3     5G ext4   isodevice /media/sudodus/isodevice
                 &#9492;&#9472;sdc5  50,4G ext4   writable  /media/sudodus/writable

 partition table: 
gpt
 grub version: 
grub-2.0.6
 persistent drive: 
/dev/sdc is big enough for a persistent live drive, 60 GB
      Final checkpoint:       
Do you want to go ahead (g/N) g
Are you really sure (y/N) 

Please *test* how [FONT=Courier New]dus-iso2usb[/FONT] works in various computers, particularly in computers (new or old), that are difficult to boot. :-P

You find it via [FONT=Courier New]ppa:mkusb/unstable[/FONT].

[SIZE=3]Improvement in program package mkusb version 22.0.3 [/SIZE]

There are several improvements of dus-iso2usb.

Now [FONT=Courier New]dus-iso2usb[/FONT] is integrated into [FONT=Courier New]dus[/FONT]. It is called via the menu system, both to make live (live-only) systems and to make persistent live systems. But the final checkpoint is still in text mode (so it is still an early version for testing).

There is another [optional] parameter, [FONT=Courier New]boot-flag[/FONT], that can be added as parameter #6. It can be useful for some old HP computers (made around 2010), maybe also for some other old computers. But some computers will not like it and the default setting is not to put a boot-flag onto the live and persistent live system.

I noticed that with some computers and USB pendrives booting works with a flag both in UEFI mode and BIOS mode (alias CSM alias legacy mode). Other computers are more picky about the settings. I was surprised that one USB pendrive was not bootable anywhere with a boot-flag on this system, while other pendrives as well as SSDs connected via an Asmedia USB3 to SATA adapter booted happily.

So if it is difficult to boot your computer from a USB pendrive or memory card, please test various settings with

. the old dus-persistent

  • the new dus-iso2usb

and maybe also some different drives.

[SIZE=3]Improvement in program package mkusb version 22.0.4 [/SIZE]

Improved user friendliness for [FONT=Courier New]dus-iso2usb[/FONT]: fixed other settings when msdos and/or boot-flag selected, which avoids loops in [FONT=Courier New]dus[/FONT] because of combinations of settings that are not compatible.

[SIZE=3]Improvement in program package mkusb version 22.0.5 [/SIZE]

Bugfix: I forgot to put an if statement where a live-only drive is created in [FONT=Courier New]dus-iso2usb[/FONT] in order to put a boot-flag. It is fixed now.

[SIZE=3]Improvement in program package mkusb version 22.0.6 [/SIZE]

[FONT=Courier New]dus-iso2usb[/FONT] is better integrated into [FONT=Courier New]dus[/FONT]. When running in graphics mode and zenity is installed, the final checkpoint is managed with the function p_checkpoint like with other tools that are called from dus and mkusb-plug.

There are also several (minor?) bugfixes and improvements in dus and dus-iso2usb to make the operation more user friendly.

[SIZE=3]Improvement in program package mkusb version 22.0.7 [/SIZE]

This time there are only 'cosmetic' changes in order to reduce and/or improve the output to the terminal window from dus and dus-iso2usb.

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 22.0.7 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1150

@ gilsonsjc persistent portable windows drive I have used Rufus to create several Windows-to-Go USB flashdrives. The type of USB used can make a big difference in install and operating speeds. It can take a long time to run the install process, like overnight. Contrary to the Microsoft site, WTG works on the latest Windows 10 versions. I have read that it also works on Windows 11.

#1151

@ sudodus


mkusb: 
   Installed: 22.0.1-1ubuntu2

ISO (lubuntu kinetic 2022-05-14) written using

sudo -H dus-iso2usb kinetic-desktop-amd64.iso /dev/sdb msdos grub-2.0.4 persistent

Boot on

- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

using persistence option at menu, had the system fully operation in ~6 mins (13:16 start with it fully operational by 13:22... - refer https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/comments/92)

I didn't use stopwatch which is normal (thus no seconds), but last comment (#90) had *jammy* booting reaching fully-functional in 9min 20secs.. Whilst I have no idea as to seconds when I started (13:16) I know it had only *flipped* to 13:22 when it was what I consider *fully-operational/functional*.

My testing can be seen here - http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248073/testcases/1303/results/

It was booted using LIVE option at menu on

- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)

[B]PROBLEM - *failure to boot*

[/B]It failed to boot on

- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

the thumb-drive appeared to not be recognized as a *bootable* device, as any attempt to boot the thumb-drive would soon cause the next device to be used (internal disk drive) & I'd get hdd's grub menu.

I've also been unable to boot it on

- hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)

which usually boots on media that dc7700 finds acceptable, and fails on media the dc7700 has issues with. It's not booting the hdd, I just get a darkish-display & nothing..

#1152

Thanks for the feedback @guiverc,

I can guess what is the problem with the two hp computers with core2duo processors: They want a 'bootable' flag on the partition where grub is located. However, adding that boot flag seems to stop booting in UEFI mode. I am trying to make a configuration work for all these test cases ...

So please add such a boot flag and check if it works in your hp computers with core2duo processors.

#1153

sudodus said: Thanks for the feedback @guiverc,

I can guess what is the problem with the two hp computers with core2duo processors: They want a 'bootable' flag on the partition where grub is located. However, adding that boot flag seems to stop booting in UEFI mode. I am trying to make a configuration work for all these test cases ...

So please add such a boot flag and check if it works in your hp computers with core2duo processors.

I added the boot flag to the partition the ISO was written to on the thumb-drive.

I test booted on (*some uEFI boxes; alas minuscule sample size...*) successfully


- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
- samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000)

It still booted the thumb-drive, as it'd done before (*sorry I failed to close some of my reports on iso.qa.ubuntu.com if you looked... I encountered an openbox bug and got sidetracked noting details on lp & didn't return.. - finishing now*).

The thumb-drive (*same image written much earlier in the day, just with BOOT flag on 2nd partition*) now boots on

- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

I didn't get it to boot on the other hp dc7900, but I'd ignore that test/result.. (*I was unable to get the boot device menu to appear; so I'm not sure tonight it actually attempted to boot the thumb-drive*). I'm not going to fight with that tonight.

#1154

Thanks for the additional tests and feedback @guiverc :-)

#1155

[SIZE=3]Improvement in program package mkusb version 22.0.3 [/SIZE]

There are several improvements of dus-iso2usb.

Now [FONT=Courier New]dus-iso2usb[/FONT] is integrated into [FONT=Courier New]dus[/FONT]. It is called via the menu system, both to make live (live-only) systems and to make persistent live systems. But the final checkpoint is still in text mode (so it is still an early version for testing).

There is another [optional] parameter, [FONT=Courier New]boot-flag[/FONT], that can be added as parameter #6. It can be useful for some old HP computers (made around 2010), maybe also for some other old computers. But some computers will not like it and the default setting is not to put a boot-flag onto the live and persistent live system.

I noticed that with some computers and USB pendrives booting works with a flag both in UEFI mode and BIOS mode (alias CSM alias legacy mode). Other computers are more picky about the settings. I was surprised that one USB pendrive was not bootable anywhere with a boot-flag on this system, while other pendrives as well as SSDs connected via an Asmedia USB3 to SATA adapter booted happily.

So if it is difficult to boot your computer from a USB pendrive or memory card, please test various settings with

. the old dus-persistent

  • the new dus-iso2usb

and maybe also some different drives.

You find

  • mkusb with dus version 22.0.3 via [FONT=Courier New]ppa:mkusb/unstable[/FONT]
  • dus 22.0.3 (not the whole mkusb) via github.com/sudodus/tarballs

Feedback is welcome :-P

#1156

[SIZE=4]Make persistent live Ubuntu or Ubuntu flavour from Arch Linux in text mode[/SIZE]

I downloaded [FONT=Courier New]archlinux-2022.05.01-x86_64.iso[/FONT], cloned it to a USB pendrive, booted it and installed dus-plus (with [FONT=Courier New]dus[/FONT] which is part of mkusb) from github.com/sudodus/tarballs.

[FONT=Courier New]dus[/FONT] works in text mode after installation from its tarball, and I could create persistent live Lubuntu 22.04 LTS in another USB drive.

[hr][/hr] So now the [FONT=Courier New]dus[/FONT] part of mkusb is verified in a current Arch live system. It should also work in an installed Arch without or with a graphic desktop environment.

If you install [FONT=Courier New]dialog[/FONT] you get a nice TUI for [FONT=Courier New]dus[/FONT], but it is not necessary.

If you have a graphical desktop environment in Arch, and you install [FONT=Courier New]zenity[/FONT] and [FONT=Courier New]xterm[/FONT], you get the standard GUI, like in Ubuntu.

[hr][/hr] Edit: You can clone 'any' hybrid iso file with mkusb and get a bootable USB drive. Most current Linux iso files are hybrid iso files.

But mkusb-dus as well as mkusb-plug can only make persistent live drives from Ubuntu and Debian iso files and some respins (with boot structure that are similar enough). You cannot use mkusb to make persistent live drives with Arch, Fedora ...

#1157

@sudodus

Was going to give it a try with Xubuntu jammy on j3400 & dc7700, but the mkusb dialogs are looping on me..

guiverc@d960-ubu2:/de2900/xubuntu_64$   dus jammy-desktop-amd64.iso
 dus 22.0.3 
[sudo] password for guiverc: 
live system or temporary superuser permissions
 p_toolsel starts here ...
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
cands=1
sdb
SanDisk_Cruzer_Facet
 7.5G
usb
USB or memory card
p_target: target=/dev/sdb
target drive size = 8 GB
live system or temporary superuser permissions
-------------------------------------------------------------------------------
settings=msdos,bflag
 p_toolsel after p_seti2u 
pt=msdos
grv=grub-2.0.6
flg=boot-flag
 Use old grub version with msdos partition table 
 p_toolsel starts here ...
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
cands=1
sdb
SanDisk_Cruzer_Facet
 7.5G
usb
USB or memory card
p_target: target=/dev/sdb
target drive size = 8 GB
-------------------------------------------------------------------------------
settings=msdos,bflag
 p_toolsel after p_seti2u 
pt=msdos
grv=grub-2.0.6
flg=boot-flag
 Use old grub version with msdos partition table 
 p_toolsel starts here ...
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
cands=1
sdb
SanDisk_Cruzer_Facet
 7.5G
usb
USB or memory card
p_target: target=/dev/sdb
target drive size = 8 GB
-------------------------------------------------------------------------------
settings=bflag
 p_toolsel after p_seti2u 
pt=gpt
grv=grub-2.0.6
flg=boot-flag
 Do not set 'boot-flag' with 'gpt' or 'grub-2.0.6' 
 p_toolsel starts here ...
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
cands=1
sdb
SanDisk_Cruzer_Facet
 7.5G
usb
USB or memory card
p_target: target=/dev/
No target device or bad target device
clean if necessary and return
clean if necessary and return
guiverc@d960-ubu2:/de2900/xubuntu_64$   apt-cache policy mkusb
mkusb:
  Installed: 22.0.3-1ubuntu1
  Candidate: 22.0.3-1ubuntu1
  Version table:
 *** 22.0.3-1ubuntu1 500
        500 http://ppa.launchpad.net/mkusb/unstable/ubuntu kinetic/main amd64 Packages
        500 http://ppa.launchpad.net/mkusb/unstable/ubuntu kinetic/main i386 Packages
        100 /var/lib/dpkg/status

... Select method/tool - i Select device - sdb dus - settings for dus-iso2usb - tried MSDOS & bootflag,or just bootflag Clonelive/etc - l

#1158

@guiverc,

Thanks for testing dus-iso2usb :-)

This tool is not yet debugged and polished. I think that is why you get the loop. Actually, at the settings menu for iso2usb you must select msdos and old grub in order for boot-flag to be accepted. Please try that again in order to check that a bootable drive can be created for various old computers. Some of them may like the boot-flag, some of them may dislike the boot-flag.

For obvious reasons I intend to improve the user interface in order to avoid setting combinations, that cause problems like the looping that happened for you.

#1159

[SIZE=4]Improvement in program package mkusb version 22.0.4[/SIZE]

Improved user friendlyness for dus-iso2usb: fixed other settings when msdos and/or boot-flag selected, which avoids loops in dus because of combinations of settings that are not compatible.

@guiverc,

This is in response to your feedback. I hope dus with dus-iso2usb will work better for you now :-)

#1160

[SIZE=4]Improvement in program package mkusb version 22.0.5[/SIZE]

Bugfix: I forgot to put an if statement where a live-only drive is created in dus-iso2usb in order to put a boot-flag. It is fixed now.

@C.S.Cameron,

This bugfix should help you make a live-only drive of the newest Ubuntu to boot in your old HP Elitebook.

#1161

[SIZE=4]Improvement in program package mkusb version 22.0.6[/SIZE]

dus-iso2usb is better integrated into dus. When running in graphics mode and zenity is installed, the final checkpoint is managed with the function p_checkpoint like with other tools that are called from dus and mkusb-plug.

There are also several (minor?) bugfixes and improvements in dus and dus-iso2usb to make the operation more user friendly.

Version 22.0.6 resides in [FONT=Courier New]ppa:mkusb/unstable[/FONT] now.

[hr][/hr] Please *test this version* and let me know, if its way to use dus-iso2usb is ready to be copied to the stable PPA, [FONT=Courier New]ppa:mkusb/ppa[/FONT]. If not ready yet, please tell me what needs to be improved or added.

#1162

[SIZE=4]Improvement in program package mkusb version 22.0.7[/SIZE]

This time there are only 'cosmetic' changes in order to reduce and/or improve the output to the terminal window from dus and dus-iso2usb.

Version 22.0.7 resides in [FONT=Courier New]ppa:mkusb/unstable[/FONT] now.

[hr][/hr] Please *test this version* and let me know, if its way to use dus-iso2usb is ready to be copied to the stable PPA, [FONT=Courier New]ppa:mkusb/ppa[/FONT]. If not ready yet, please tell me what needs to be improved or added.

#1163

Sorry I've been unable to test much lately..

I've grabbed today's Lubuntu *kinetic* and written to thumb-drive using


sudo -H dus-iso2usb kinetic-desktop-amd64.iso /dev/sdb msdos grub-2.0.4 persistent

and it fails to boot on

  • hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

It booted (*it felt rather slowly*) on

  • sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)

This testing was without regard to prior instructions sorry (*too long ago for me to remember, and I lacked time to look back, the command was grabbed from my command history*) so maybe is of little use, but I'll continue testing when I can.

apt-cache policy mkusb shows 22.0.7-1ubuntu1 from http://ppa.launchpad.net/mkusb/unstable/ubuntu [SIZE=1] I hope to do more testing later today (*if time allows, will be found here but I plan to edit & add here too*)[/SIZE]

ISO written again, this time with


sudo -H dus-iso2usb kinetic-desktop-amd64.iso /dev/sdb msdos grub-2.0.4 persistent boot-flag

and on

  • hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

boots to MKUSB type grey background (logo) ... then hdd activity (*my smile drops*) .. delay then I get a xmessage window "Now firefox should work in your persistent live system after reboot" so it did work this time, YIPPEE

opened firefox & quick play around then reboot system.

boot again same box (hp dc7700)

This time I got a GRUB type of menu asking how to boot the system before the grey-mkusb-background; I didn't notice any grub-style-menu first boot (*I'm pretty sure*) then got the grey-background again but looks good.... also doesn't look like a first run (*normal live session*) but this time I touch ~/blah read fridge.ubuntu.com, adjust monitor.setup to match my system & other stuff that will show on next boot.

Third boot on hp.dc7700 & it boots to my configured screen setup, my touched ~/blah is present as is command history etc so working perfectly

Booted on

~17:20 at grub menu, and by ~17:27 or ~17:28 system was ~usable... not super fast boot, but it got there faster than it has for some recent ISOs/systems... but system once booted was good.

  • motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
#1164

@guiverc,

Thanks for testing mkusb's dus-iso2usb in the computers, where there can be problems. I'm happy that you found how to apply the boot-flag and make the hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) boot. :-)

It would be interesting if you can also test it in your tablet computer "motion computing j3400" :-P

[hr][/hr] Please notice also that in the current mkusb version, 22.0.7, it is possible to reach dus-iso2usb from the general menu system of dus.

#1165

I did mention the j3400 at the end of my post, but your question about it may have proceeded or been at roughly the same time as my last edit.

My testing on j3400 was minimal, and times rather approx (*digital room clock without seconds*)

(*the with & without boot-flag was ~expected & the purpose of that test*.... *I didn't have time to refresh myself on where I was before the testing, thus my wording was likely less than ideal/clear sorry.. I was also flipping between tasks so brain somewhat scattered*)

#1166

Thanks again @guiverc,

Sorry for not observing the short text: So dus-iso2usb works with the j3400, but not really well. This makes the work that you are doing together with Thomas Schmitt really important. I hope that you will succeed in making the Ubuntu developers include your fix into the current and future iso files.

#1167

[SIZE=4]mkusb version 22.0.8, 22.0.9, 22.1.0, 22.1.1, 22.1.2[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. dus.8 (and mkusb.8) for man dus & man mkusb updated . dus-iso2usb: syslbl="Not Ubuntu 19." when not Ubuntu

. upgrade of mkusb-nox: . made more convenient for isotesting with SSD drives which are seen as ATA even when connected via USB . pv replaced by dd options (takes care of sync too) status=progress oflag=dsync and bs modified to 1M . discouraging text when creating Windows installer . protecting source when a block device (bugfix)

. mkusb-nox: added inverse video and lsblk output to help identify the target device

. dus-iso2usb: redbacks when errors causing exit . dus: p_toolsel: print command line for dus-iso2usb

. several fixes of zenity window sizes . p_ldr: set livedrive in system made by dus-iso2usb which is a grub-n-iso system with isodevice . copyright updated [/td][/tr][/table]

  • mkusb 22.0.8
  • mkusb 22.0.9
  • mkusb 22.1.0
  • mkusb 22.1.1
  • mkusb 22.1.2

[SIZE=3]Improvement in program package mkusb version 22.0.8 [/SIZE]

The man page is updated: several updates (including the introduction of iso2usb): [FONT=Courier New]man mkusb[/FONT] and [FONT=Courier New]man dus[/FONT] link to the same file.

A minor bug-fix avoids an error when trying to use [FONT=Courier New]iso2usb[/FONT] with non-Ubuntu iso files. We cannot expect iso2usb to work [with non-Ubuntu iso files]. It is much more likely that 'cloning' and 'dus-persistent' works (because iso2usb assumes some special features to boot via grub into an iso file). But anyway, there should not be an error with non-Ubuntu iso files, and it is fixed now (at least for Linux Mint 21: no error when running dus-iso2usb, but the USB drive will not work. You should use dus-persistent or mkusb-plug to get a working persistent live drive with Linux Mint 21).

[SIZE=3]Improvement in program package mkusb version 22.0.9 [/SIZE]

There is a major upgrade of [FONT=Courier New]mkusb-nox[/FONT] in order to make it useful today (after six years of 'sleep'). It is a useful cloning tool when running in text mode. 'mkusb-nox' and also useful when iso-testing because it identifies the target device almost automatically.

Users without a GUI may prefer 'mkusb-nox'. It can clone an iso file or img file to make a live drive in a safe way. It has the original mkusb user interface to help you identify and select the correct target device. 'mkusb-nox' works with USB and other drives seen as '/dev/sdx' and memory cards seen as '/dev/mmcblkn' where 'x' is a letter and 'n' is a digit.

'mkusb-nox' can still be very efficient for iso-testing (repeated cloning of daily updates of iso files to the same target device even when running in a terminal window of a graphical desktop environment).


sudo mkusb-nox file.iso all   # 'all' to show all mass storage devices

You find a detailed description in the NOX Quick Start Manual.

Please notice that 'mkusb-dus' works also in text mode and will replace 'mkusb-nox' for many users.

[SIZE=3]Improvement in program package mkusb version 22.1.0 [/SIZE]

User friendly improvement to make it easier to identify input errors when running mkusb-nox:

  • more inverse video
  • lsblk output

[SIZE=3]Improvement in program package mkusb version 22.1.1 [/SIZE]

User friendly improvement to make it easier to identify input errors when running dus-iso2usb:

  • output text with different background (blue or red) to help the user notice what might be wrong (which can be difficult when dus-iso2usb is called from dus).

[SIZE=3]Improvement in program package mkusb version 22.1.2 [/SIZE]

  • User friendliness in dus and dus-persistent (improved zenity window sizes).
  • Bug fix: Identifying and setting the [FONT=Courier New]livedrive[/FONT] variable when running dus in a system made by dus-iso2usb which is a grub-n-iso system with a partition [FONT=Courier New]isodevice[/FONT].

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 22.1.1 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1168

I had issues with a calamares *kinetic* install... :( so I re-wrote the thumb-drive with the *jammy.1 *ISO (*for comparison*) using

sudo mkusb-nox jammy-desktop-amd64.iso all

and I LOVED the warnings of *mismatch* with what was on my thumb-drive, and ISO I was writing to it.

Ubuntu jammy 22.04 amd64 i386  _found_ in iso-file
Ubuntu jammy 22.04 amd64 i386  _not_ in USB device
1: source: jammy-desktop-amd64.iso 
   target: Name: usb-Verbatim_STORE_N_GO  Dev: /dev/sdb  Size: 15506MB 
MODEL      NAME FSTYPE  LABEL                SIZE
STORE N GO sdb  iso9660 Lubuntu 22.10 amd64 14.4G
           sdb1 iso9660 Lubuntu 22.10 amd64  2.6G
           sdb2 vfat    ESP                  4.1M
           sdb3                              300K
           sdb4 ext4    writable            11.8G
 Final checkpoint 
Please check again that it is the correct target device! (y/n)

As my Lubuntu *media* is unique, I can recognize it & rely on visual clues... but my other *flavors *are just a letter/number scrawled in *texta* on the *thumb-drive* that is very hard to read (*always rubs off*) based on a *map* nearby that tells which letter/number I should be using... This will make it much easier for me to find the *correct* thumb-drive I believe.

I liked how it showed on my qterminal, so thank you. Yeah I was getting the same detail before via GUI window, but I do prefer it on textual terminal.

#1169

Thanks for testing, @guiverc,

When developing/modifying software it is important , that new eyes check that things work as they should, and that the dialogue is not confused or confusing.

#1170

Possibly of no value, but my *primary* desktop died awhile back, which was the primary box I wrote *daily* ISOs to thumb-drive. On occasion I use other (*normally Ubuntu*) boxes, but my current *(backup) primary* box is running Debian *testing (bookworm/sid**)* and I'm using mkusb-nox just like I did when using *kinetic*.

guiverc@dc780-deb:~$   lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux bookworm/sid
Release:        testing
Codename:       bookworm
guiverc@dc780-deb:~$   apt-cache policy mkusb-nox

mkusb-nox:
  Installed: 22.1.2-1ubuntu1
  Candidate: 22.1.2-1ubuntu1
  Version table:
 *** 22.1.2-1ubuntu1 500
        500 http://ppa.launchpad.net/mkusb/unstable/ubuntu kinetic/main amd64 Packages

No issues, at least not with Lubuntu *kinetic* I'm mostly writing. It's mkusb-nox I'm mainly using (*and just threw up warning write finished*), but I do use dus on occasion too.

#1171

Please note I'm very happy with this tool, and just not on Debian/Ubuntu, but Arch as well. Just one request if possible, sure would be nice to have it as a Appimage. I'm back testing Suse(Tumbleweed) will play with it on that platform @ sudodus no pressure, more of a want than need. (However you know that. :) )

#1172

@1fallen,

  • You suggest to make an AppImage file for mkusb. I guess Snap and Flatpak would be alternatives. Why do you suggest AppImage?
  • Are you interested only in cloning or also some of the other things mkusb can do (for non-Ubuntu/non-Debian distros)?
  • How important is the user interface: GUI by zenity, TUI by dialog or plain text?
  • Please try the existing dus tarball and mkusb-nox tarball if you have not tested them yet and let me know how close they are to what you would expect from an AppImage file. (Obviously a tarball is not as convenient as an AppImage, but where/how do they work and/or fail for example in Arch and openSUSE)?

. The end of the dus-installer script is


needed="pv parted gdisk lsblk df mount gzip xz xterm rsync tar dialog zenity"

if [ "$action" == "install" ]
then
 for i in $needed
 do
  which "$i" >/dev/null
  if [ $? -ne 0 ]
  then
   if [ "$i" == "lsblk" ]
   then
    echo "please install: util-linux"
   elif [ "$i" == "df" ]
   then
    echo "please install: coreutils"
   elif [ "$i" == "xz" ]
   then
    echo "please install: xz-utils"
   else
    echo "please install: $i"
   fi
  fi
 done
fi

Are the packages util-linux, coreutils and xz-utils used by non-Ubuntu/non-Debian distros? I guess these programs/packages would be included in a corresponding AppImage? Or only part of them e.g. assuming that df, mount, gzip, tar are always there already?

. mkusb-nox is the only file in its tarball and needs no extra file in current versions of Ubuntu and Debian, but may need some extra programs/packages in some other distro.

#1173

I should of known better, let me think on this a bit further. Working on the tarballs as I type this. (I will Report back later)

#1174

A-OK on Arch and Suse"Tumbleweed" Everything functions well on Arch, >> I'm now running some tests On Tumbleweed, to make sure the absent "grub-pc" is not an issue.

inxi -S --no-host
System:
  Kernel: 6.0.0-1-default arch: x86_64 bits: 64 Desktop: Xfce v: 4.16.1
    Distro: openSUSE Tumbleweed 20221013

and:

# /boot/grub2/grub.cfg.
#1175

At this time I withdraw my request for a Appimage. This works for me. BTW, I like the improvements so far.

#1176

@1fallen,

[FONT=Courier New]grub-pc[/FONT] is used 'only' when making a persistent live system with dus-persistent to boot in BIOS mode without using a template, and I don't think dus-persistent will work anyway with openSUSE Tumbleweed because the mkusb scripts do not understand the boot structure (too different from Ubuntu and Debian).

Cloning should work without [FONT=Courier New]grub-pc[/FONT]. Wiping and creating a standard storage device should work too. If I remember correctly making a Windows installer uses a template, so it should work too. But other things might cause problems, so it is important to test that things really work.

Finally, I'm glad that the current tarballs work for you, so that you can withdraw the request for AppImage :-P

#1177

sudodus said:

Cloning should work without [FONT=Courier New]grub-pc[/FONT]. Wiping and creating a standard storage device should work too. If I remember correctly making a Windows installer uses a template, so it should work too. But other things might cause problems, so it is important to test that things really work.

Great minds think alike, I'm doing that now, might be a couple of days before I post back. For the first time in several years of not needing the need for A windows install or installerr, I find a Windows System is needed for my family's use. YUCK....](*,) EDIT: First finding Tumbleweed is a no-go for persistent installs. :(

#1178

sudodus said: Cloning should work without [FONT=Courier New]grub-pc[/FONT]. Wiping and creating a standard storage device should work too. If I remember correctly making a Windows installer uses a template, so it should work too. But other things might cause problems, so it is important to test that things really work.

Agree with the testing. In every problem their should be a testing process, quality control and etc to produce the best outcome. This very important in any kind of studies, institutional, commercial, industrial, and etc. Because we people are tend to do errors, mistakes. That is why don't be afraid to make mistake and be sure when you have gone to that state, mend it as possible go to people that can help you. If they don't want to help you because of "gossip" remember, people are not one sided maybe their are some but unique and genuine people dig deep. I don't go too far in this because I might go into something that is not realistic anymore so, Regards and cheers.

#1179

1fallen said: ...

EDIT: First finding Tumbleweed is a no-go for persistent installs. :(

This has been and still is outside mkusb's territory.

If you want a persistent live Tumbleweed system, and know how to make it manually, or know someone who can make it, maybe we could cooperate ...

#1180

mIk3_08 said: Agree with the testing. In every problem their should be a testing process, quality control and etc to produce the best outcome. This very important in any kind of studies, institutional, commercial, industrial, and etc. Because we people are tend to do errors, mistakes. That is why don't be afraid to make mistake and be sure when you have gone to that state, mend it as possible go to people that can help you. If they don't want to help you because of "gossip" remember, people are not one sided maybe their are some but unique and genuine people dig deep. I don't go too far in this because I might go into something that is not realistic anymore so, Regards and cheers.

Please explain:

  • are you encouraging or discouraging testing of *mkusb* for other (non-Ubuntu and non-Debian) Linux distros or
  • are you encouraging testing of *software in general* but only to a certain point (where development and testing would cost too much)?
#1181

sudodus said: This has been and still is outside mkusb's territory.

Agreed and I knew this going in, but I'm trying anyway. That was kind of my premise on a request for an Appimage. (Not just for making a persistent Suse install) I'm still mucking around though with mkusb, I'm so close. (I know famous last words right. :)) I can make persistent with Ventoy, on Arch and the other unfriendly OS's

#1182

1fallen said: ...

I can make persistent with Ventoy, on Arch and the other unfriendly OS's

^^^ That ^^^ made me think that it gets persistent live automatically when cloned, so I tried that with an openSUSE Tumbleweed iso file,


openSUSE-Tumbleweed-XFCE-Live-x86_64-Snapshot20220616-Media.iso

and yes, it works like that. A partition with [FONT=Courier New]ext4[/FONT] and the label [FONT=Courier New]cow[/FONT] is created automatically (behind the cloned part of the drive) at the first boot and it is used automatically and by default to make the live system persistent. (I created a file and it survived reboot. The bash history survived too.)

So we need not do anything special to make openSUSE Tumbleweed persistent live. Only clone like we do to get Ubuntu and Debian live (live-only) :-)

#1183

sudodus said: ^^^ That ^^^ made me think that it gets persistent live automatically when cloned, so I tried that with an openSUSE Tumbleweed iso file,


openSUSE-Tumbleweed-XFCE-Live-x86_64-Snapshot20220616-Media.iso

and yes, it works like that. sudodus I can't be that stupid, can I??? That did not work for me....don't forget or let me remind, no Ubuntu here. :) Is that the host you used Ubuntu/Flavor

#1184

@1fallen,

I cloned with dus in Lubuntu, but cloning is the same wherever it is run, and with whatever tool. Please try again, for example clone with dus or with mkusb-nox in Arch. It should work. Tumbleweed might want a minimum target drive size for persistence to work, so if it fails, you might try with a bigger USB drive.

#1185

sudodus said: @1fallen,

I cloned with dus in Lubuntu, but cloning is the same wherever it is run, and with whatever tool.

Yes of course, but posting good info is always welcome and needed in Tutorials.

sudodus said: @1fallen,

Tumbleweed might want _a minimum target drive size for persistence to work_, but if it fails, you might try with a bigger USB drive. 64GiG SansUltra, but you jog-ed my memory now with the above. I told you I was getting close to making it work....I'll post back tomorrow, I have a crap load of Honey Dooo's the rest of the day If I want to sleep in the big bed tonite. ;)

#1186

The size 64 GB is more than enough.

I tested now with a Sandisk Extreme 32 GB in BIOS mode and in UEFI mode. Persistence works (when the Tumbleweed iso file was cloned to the drive).

#1187

sudodus said: Please explain:

  • are you encouraging or discouraging testing of *mkusb* for other (non-Ubuntu and non-Debian) Linux distros or
  • are you encouraging testing of *software in general* but only to a certain point (where development and testing would cost too much)? Testing Software in General. Testing is very important. Sorry sudodus if I get you confused. I didn't meant it to be. Peace! Regards and cheers.
#1188

@1fallen,

I want to thank you for making me {realize / remember to check} that openSUSE Tumbleweed will get persistent live by default when cloned to a USB pendrive :-)

Would you suggest that mkusb should check early what iso file it is and recommend how to treat it, for example suggest cloning (with dus-live) and avoid dus-persistent or dus-iso2usb?

@mIk3_08,

Thanks for making it clear what you meant :-)

I agree, that testing software is very important, and it is a good idea to involve many people. Even a small contribution from yet another person is valuable, because a new or different way to use the software might fail or work better than expected.

#1189

sudodus said:

@mIk3_08, Thanks for making it clear what you meant :-) I agree, that testing software is very important, and it is a good idea to involve many people. Even a small contribution from yet another person is valuable, because a new or different way to use the software might fail or work better than expected. You're always welcome sudodus.Its just that I'm not so good enough in English I think. Regards and cheers.

#1190

sudodus said: @1fallen,

I want to thank you for making me {realize / remember to check} that openSUSE Tumbleweed will get persistent live by default when cloned to a USB pendrive :-)

Would you suggest that mkusb should check early what iso file it is and recommend how to treat it, for example suggest cloning (with dus-live) and avoid dus-persistent or dus-iso2usb?

Any time my friend, always happy to help when possible. sudodus I can create a cloned or persistent drive from Arch, but through a KVM install of Ubuntu or most Debian Systems. Sorry I've spent too much time on this, and for the next 2 or 3 days I have to play catch up on my obligations to others. I just wanted to revisit the mkusb on other Distro's. I'll stay in touch though. :) EDIT: I forgot to comment:

sudodus said: @1fallen,

Would you suggest that mkusb should check early what iso file it is and recommend how to treat it, for example suggest cloning (with dus-live) and avoid dus-persistent or dus-iso2usb?

For a newer user>> Yes Even I had to think before the next move. :D

#1191

1fallen said: Any time my friend, always happy to help when possible.

sudodus I can create a cloned or persistent drive from Arch, but through a KVM install of Ubuntu or most Debian Systems. Sorry I've spent too much time on this, and for the next 2 or 3 days I have to play catch up on my obligations to others. I just wanted to revisit the mkusb on other Distro's. I'll stay in touch though. :)

I'm looking forward to more details of how you made a persistent live Arch system. If/when you have time, please share details about your method :-P

EDIT: I forgot to comment:

For a newer user>> Yes Even I had to think before the next move. :D

Thanks for this feedback. I'll start thinking/planning how to detect what iso file it is and where and how to show that information to the user. :-)

#1192

sudodus said: I'm looking forward to more details of how you made a persistent live Arch system. If/when you have time, please share details about your method :-P

I think we have a possible miss-understanding on that, I'm using Arch with mkusb to try persistent installs of non Arch Distro's, but that would be neat trick, think of all the time we could save if that was the case. :) I do have a script that I follow though for an Arch Install.

#1193

1fallen said:

I'm looking forward to more details of how you made a persistent live Arch system. If/when you have time, please share details about your method I think we have a possible miss-understanding on that, I'm using Arch with mkusb to try persistent installs of non Arch Distro's, but that would be neat trick, think of all the time we could save if that was the case. :) I do have a script that I follow though for an Arch Install.

Yes, I misunderstood, but you made a good point.

consider publishing it?

  • Is the script you use for an Arch install (assuming it makes a persistent live system) published? If not, would you
  • Which non-Arch (and non-openSUSE) distros are you trying to make persistent live?
#1194

sudodus said:

consider publishing it?

  • Is the script you use for an Arch install (assuming it makes a persistent live system) published? If not, would you

I PM'ed you on that we will talk about that later. ;)

sudodus said:

Numerous Linux OS's All fail at no kernel found,>>note: Still on a Arch system and a Ubuntu install in a KVM they all work with mkusb.

  • Which non-Arch (and non-openSUSE) distros are you trying to make persistent live?
#1195

@1fallen,

I see. So there are things in mkusb, that work in Ubuntu, but do not work in Arch. If cloning works but not making persistent live drives, I think we should look into the tool [FONT=Courier New]dus-persistent[/FONT].

Is mkusb showing any error? Or is it happy, but the result is bad, 'no kernel found'? It is possible that dus-persistent does not know what to do when the host is neither Ubuntu, Debian nor any respin of those. Do you notice if usb-pack-efi is used? Have you tried to force using usb-pack-efi (in the settings menu)?

[hr][/hr] [FONT=Courier New]dus-iso2usb[/FONT] might work from Arch, but only with iso files of Ubuntu and Ubuntu family flavours.

[hr][/hr] Another alternative is [FONT=Courier New]mkusb-plug[/FONT], that you can get via a tarball from github.

#1196

sudodus said:

Is mkusb showing any error? Or is it happy, but the result is bad, 'no kernel found'? It is possible that dus-persistent does not know what to do when the host is neither Ubuntu, Debian nor any respin of those. Do you notice if usb-pack-efi is used? Have you tried to force using usb-pack-efi (in the settings menu)?

Seems to be happy with results, and definitely no errors reported, just a bad result.

sudodus said: @1fallen,

I see. So there are things in mkusb, that work in Ubuntu, but do not work in Arch. If cloning works but not making persistent live drives, I think we should look into the tool [FONT=Courier New]dus-persistent[/FONT].

Is mkusb showing any error? Or is it happy, but the result is bad, 'no kernel found'? It is possible that dus-persistent does not know what to do when the host is neither Ubuntu, Debian nor any respin of those. Do you notice if usb-pack-efi is used? Have you tried to force using usb-pack-efi (in the settings menu)?

Another alternative is [FONT=Courier New]mkusb-plug[/FONT], that you can get via a tarball from github. Yes it complains of the missing "usb-pack-efi", I going to get and try "mkusb-plug" a little later tonite. Stay Tuned....:)

#1197

@1fallen,

Did you install dus-plus.tar.xz? It contains usb-pack-efi.

(The smaller package dus.tar.xz does not contain it, and when I suggested what to install, I did not think you intended to create persistent live drives.)

#1198

sudodus said: @1fallen,

and when I suggested what to install, I did not think you intended to create persistent live drives.) That's a must for me at times, not often but at times.

All good here for persistent debian install's from a non Debian OS, kaisen was one that was a bit of mystery for persisant on mkusb, but worked with some complaints that warned it might not work.

dus-persistent 22.1.2

might not make all systems bootable in UEFI mode from this version.
You should work in Debian 8, Ubuntu 14.04 or newer
or a corresponding Ubuntu flavour (Kubuntu, Lubuntu, ... Xubuntu.)

Work done with /dev/sdi :-)

Tool used was guidus with the "usb-efi pack" (seems it was needed), dus-persistent V-22.1.2. Result SanUltra 32G:

PRETTY_NAME="Kaisen GNU/Linux 2.1 (rolling)"
NAME="Kaisen GNU/Linux"
VERSION_ID="2.1"
VERSION="2.1 (rolling)"
VERSION_CODENAME=rolling
ID=kaisen
ID_LIKE=debian
HOME_URL="https://kaisenlinux.org"
SUPPORT_URL="https://forum.kaisenlinux.org"
BUG_REPORT_URL="https://forum.kaisenlinux.org"


Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  5.8G     0  5.8G   0% /dev
tmpfs          tmpfs     1.2G  1.6M  1.2G   1% /run
/dev/sdb4      iso9660   4.5G  4.5G     0 100% /run/live/medium
/dev/loop0     squashfs  4.0G  4.0G     0 100% /run/live/rootfs/filesystem.squashfs
tmpfs          tmpfs     5.8G     0  5.8G   0% /run/live/overlay
/dev/sdb5      ext4       25G   51M   24G   1% /run/live/persistence/sdb5
overlay        overlay    25G   51M   24G   1% /
tmpfs          tmpfs     5.8G   84K  5.8G   1% /dev/shm
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     5.8G  8.0K  5.8G   1% /tmp
tmpfs          tmpfs     1.2G   52K  1.2G   1% /run/user/1000

Who ever that guy was that requested an Appimage should be banned here. ;) When needed this tool will come in handy for testing purpose's only. Note: should be said this is not the most secure method of an install, largely in part anyone with access to the drive can login and view, change, remove anything on drive.(Admin rights) The usb drive if one is used as permanent storage will die out within 3 to 6 months as you will burn through the program erase cycles on the flash. If you can use a SSD or portable SSD instead. Just a heads-up.

#1199

1fallen said: ... All good here for persistent debian install's from a non Debian OS, kaisen was one that was a bit of mystery for persisant on mkusb, but worked with some complaints that warned it might not work.

Tool used was guidus with the "usb-efi pack" (seems it was needed), dus-persistent V-22.1.2. Result SanUltra 32G:

PRETTY_NAME="Kaisen GNU/Linux 2.1 (rolling)"
NAME="Kaisen GNU/Linux"
VERSION_ID="2.1"
VERSION="2.1 (rolling)"
VERSION_CODENAME=rolling
ID=kaisen
ID_LIKE=debian
HOME_URL="https://kaisenlinux.org"
SUPPORT_URL="https://forum.kaisenlinux.org"
BUG_REPORT_URL="https://forum.kaisenlinux.org"

Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  5.8G     0  5.8G   0% /dev
tmpfs          tmpfs     1.2G  1.6M  1.2G   1% /run
/dev/sdb4      iso9660   4.5G  4.5G     0 100% /run/live/medium
/dev/loop0     squashfs  4.0G  4.0G     0 100% /run/live/rootfs/filesystem.squashfs
tmpfs          tmpfs     5.8G     0  5.8G   0% /run/live/overlay
/dev/sdb5      ext4       25G   51M   24G   1% /run/live/persistence/sdb5
overlay        overlay    25G   51M   24G   1% /
tmpfs          tmpfs     5.8G   84K  5.8G   1% /dev/shm
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     5.8G  8.0K  5.8G   1% /tmp
tmpfs          tmpfs     1.2G   52K  1.2G   1% /run/user/1000

I'm glad that you finally found a way to made a working persistent live Kaisen system (I guess you were running guidus in Arch). Congratulations :-)

Who ever that guy was that requested an Appimage should be banned here. ;) :-D > When needed this tool will come in handy for testing purpose's only. Note: should be said this is not the most secure method of an install, largely in part anyone with access to the drive can login and view, change, remove anything on drive.(Admin rights) The usb drive if one is used as permanent storage will die out within 3 to 6 months as you will burn through the program erase cycles on the flash. If you can use a SSD or portable SSD instead. Just a heads-up.

It is true that a persistent live system is *not* the most secure kind of system.

Compared to a normal installed system a persistent live system is typically writing less to the drive.

You can improve the situation by turning off journaling on the partition for persistence:use ext2 (by default without journaling or use ext4 and turn off journaling (which is done automatically by dus-persistent).

But still, I agree that it is a good idea to use an SSD: longer life and higher speed (but typically not as small and convenient as a pendrive). An alternative is to use the internal drive of the computer (if you have a separate computer for testing), or maybe run in a virtual machine and use a virtual disk (which resides on the host's internal drive).

Nowadays I use SATA-SSDs connected via a USB3 to SATA adapter most of the time when I test live and persistent live systems. They are so much faster and more reliable compared to pendrives, and rather cheap today.

#1200

sudodus said:

Compared to a normal installed system a persistent live system is typically writing less to the drive.

You can improve the situation by turning off journaling on the partition for persistence:use ext2 (by default without journaling or use ext4 and turn off journaling (which is done automatically by dus-persistent).

Automatic with "Tool used was guidus with the "usb-efi pack" (seems it was needed), dus-persistent V-22.1.2." Even with all your changes and dropped support for non debian/ubuntu systems. I just knew you have not broke this tool I use and depend on from time to time. Note the OS used is not a Debian system. I add that because my last visit to mkusb was a few years back now.

#1201

[SIZE=4]mkusb version 22.2.0 - 22.2.3[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. p_source: added p_sniff with sub-functions for crude estimate of possible mkusb tools/methods to create persistent live drive from the selected iso file

. minor bugfixes detected after p_sniff was added . p_toolsel: correct letters "(i/l/q)" for text mode, that is when "$manager" == "t" . p_sniff: zenity window when "$manager" == "z" and dialog paused when "$manager" == "d"

. minor bugfixes detected after p_sniff was added . p_snff: sudo --> p_calx

. 22.2.3-1ubuntu1: p_sniff: return when source not an iso file . 22.2.3-1ubuntu2: minor edit in dus: only updated version number [/td][/tr][/table]

  • mkusb 22.2.0
  • mkusb 22.2.1
  • mkusb 22.2.2
  • mkusb 22.2.3

[SIZE=3]Improvement in program package mkusb versions 22.2.0 - 22.2.3[/SIZE]

After a dialogue with 1fallen I made a function, that helps estimate which tools/methods of mkusb that are likely to work with the selected iso file. The [FONT=Courier New]file name[/FONT] and the content in **[FONT=Courier New]*.cfg[/FONT]** files (in the iso file) are used to identify the Linux distro (or Windows version).

The result is always written to the console window, and when particularly relevant also into a zenity window.

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 22.1.2 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1202

When running dus (mkusb-dus) version 22.2.1, it estimates which tools/methods of mkusb that are likely to work with the selected iso file. Here are some examples of the output to the mkusb console window (text mode so convenient to copy into this post).


[COLOR="#808080"]$ dus  candidate.iso
 dus 22.2.1 
live system or temporary superuser permissions
 p_toolsel starts here ...
-----  p_persistent:  make persistent live drive -----[/COLOR]
Crude estimate of possible mkusb tools/methods to create
persistent live drive from the selected iso file:
** candidate.iso **
menuentry "Try Xubuntu Core without installing" {
Works with  **dus-persistent**  according to content
Works with  **dus-iso2usb**  according to content
Persistent live by with  **mkusb-plug**  according to content
------------------------------------------------------------------

[COLOR="#808080"]$ dus opensuse/openSUSE-Tumbleweed-XFCE-Live-x86_64-Snapshot20220616-Media.iso 
 dus 22.2.1 
live system or temporary superuser permissions
 p_toolsel starts here ...
-----  p_persistent:  make persistent live drive -----[/COLOR]
Crude estimate of possible mkusb tools/methods to create
persistent live drive from the selected iso file:
** opensuse/openSUSE-Tumbleweed-XFCE-Live-x86_64-Snapshot20220616-Media.iso **
menuentry "openSUSE Tumbleweed XFCE Live" --class os --unrestricted {
Persistent live by  **cloning**  according to name
------------------------------------------------------------------

[COLOR="#808080"]dus arch/archlinux-2022.05.01-x86_64.iso 
 dus 22.2.1 
live system or temporary superuser permissions
 p_toolsel starts here ...[/COLOR]
-----  p_persistent:  make persistent live drive -----
Crude estimate of possible mkusb tools/methods to create
persistent live drive from the selected iso file:
** arch/archlinux-2022.05.01-x86_64.iso **

p_sniff  **cannot tell**  how to make persistent live system,
see details at the following links:
https://help.ubuntu.com/community/mkusb/gui#Linux_distros_where_mkusb_works
https://help.ubuntu.com/community/mkusb/minp/details
------------------------------------------------------------------

[COLOR="#808080"]$ dus debian/debian-live-11.3.0-amd64-standard.iso
 dus 22.2.1 
live system or temporary superuser permissions
-----  p_install: cloning ...
-----  p_live: cloning Linux or extracting Windows  -----[/COLOR]
Crude estimate of possible mkusb tools/methods to create
persistent live drive from the selected iso file:
** debian/debian-live-11.3.0-amd64-standard.iso **
menuentry "Debian GNU/Linux Live (kernel 5.10.0-13-amd64)" {
Works with  **dus-persistent**  according to name
Persistent live by  **mkusb-plug**  according to name
------------------------------------------------------------------

[COLOR="#808080"]$ dus windows/Windows11_InsiderPreview_Client_x64_en-us__22000.iso 
 dus 22.2.1 
live system or temporary superuser permissions
-----  p_winsel: extracting Windows installer  -----[/COLOR]
Crude estimate of possible mkusb tools/methods to create
persistent live drive from the selected iso file:
** windows/Windows11_InsiderPreview_Client_x64_en-us__22000.iso **
db_MSFTproductionWindowsSigningCA.cer
Only  **Windows installer**  can be created according to name
------------------------------------------------------------------
#1203

First run with Selected iso file rather long so tl;dr: /home/me/Downloads/1.All-DLs/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso


Cloning works with most linux distros to make live-only system.

Crude estimate of possible mkusb tools/methods for persistent live Linux system:

Persistent live by cloning according to name

You are trying to make a persistent live drive of an operating system,
 which is neither Debian nor Ubuntu. You must probably tweak it manually.


dus-persistent 22.1.2

might not make all systems bootable in UEFI mode from this version.
You should work in Debian 8, Ubuntu 14.04 or newer
or a corresponding Ubuntu flavour (Kubuntu, Lubuntu, ... Xubuntu.)

Work done with /dev/sdj :-)

The target device is ready to use. '/home/me/Downloads/1.All-DLs/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso' was installed

Result:


*** Ubuntu version not found ***
label on partition for persistence: '-rw'
tune2fs 1.46.5 (30-Dec-2021)
---------------------------------------------------------------------------
source=/home/me/Downloads/1.All-DLs/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
---------------------------------------------------------------------------
item 60
umount: /dev/sdj3: not mounted.
mount /dev/sdj3 /tmp/dus.VGDbFVWRT6
/dev/sdj3       241M   15M  226M   7% /tmp/dus.VGDbFVWRT6
item 65
umount: /dev/sdj1: not mounted.
/dev/sdj1        22G   66M   22G   1% /tmp/dus.aSIT4FGUH6
 use 'grub.img' so do not remove files:  
item 70
 UEFI Bootloader:  using grubimg (template image)
 BIOS Bootloader via 'grub.img':  
item 80
 Bootloaders via 'grub.img', skipping 'usb-pack_efi':  
set timeout=10
set default=0
menuname: openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
 keep current security upgrade settings 
umount: /dev/sdj4: not mounted.
umount: /dev/sdj5: not mounted.
---------------------------------------------------------------------------
do_n_show:
&lt; "/home/me/Downloads/1.All-DLs/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso" pv -ni2 | dd of=/dev/sdj4 bs=4096
 
( < "/home/me/Downloads/1.All-DLs/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso" pv -ni2 | dd of=/dev/sdj4 bs=4096 && echo 'Done' > /dev/stderr ) 2>&1 || ( echo '# failed';sleep 1 )
Please wait for sync (flushing file system buffers to the device)
until 'Done' is written ...
/usr/bin/watch-flush
----- cleanup after writing ------------------------------------------
 293807 pts/0    00:00:00 watch-flush
umount: /dev/sdj: not mounted.
umount: /dev/sdj2: not mounted.
umount: /dev/sdj4: not mounted.
umount: /dev/sdj5: not mounted.
'pv %'; 'dd final output'
28
30
32
34
36
39
41
43
46
48
50
53
55
57
59
60
61
62
63
65
66
67
68
69
70
71
72
73
75
76
77
78
79
80
81
83
84
85
86
87
88
90
91
92
93
94
96
97
98
99
100
do_n_show: Work done
---------------------------------------------------------------------------
Syncing the target device ...
item 90
Wait 5 seconds and a little more ...
<pre>
parted -s "/dev/sdj" print
Model: SanDisk Ultra (scsi)
Disk /dev/sdj: 61.5GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 2      1000kB  2000kB  1000kB               primary  bios_grub
 3      2000kB  258MB   256MB   fat32        primary  boot, esp
 4      258MB   4361MB  4103MB               primary
 5      4361MB  38.1GB  33.7GB  ext2         primary
 1      38.1GB  61.5GB  23.4GB  ntfs         primary  msftdata

lsblk -o MODEL,NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE "/dev/sdj"
MODEL NAME   FSTYPE  LABEL                            MOUNTPOINT   SIZE
Ultra sdj                                                         57.3G
      |-sdj1 ntfs    usbdata                                      21.8G
      |-sdj2                                                       977K
      |-sdj3 vfat    usbboot                                     244.1M
      |-sdj4 iso9660 openSUSE-Leap-15.4-DVD-x86_64243              3.8G
      `-sdj5 ext4    -rw                                          31.4G
</pre>
 Done :-) 
The target device is ready to use.
'/home/me/Downloads/1.All-DLs/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso'
was installed
item 100
Cleanup after dus-persistent finished :-)

Report back later

#1204

@1fallen,

I suggest that you simply *clone* the openSUSE iso file (I think Leap behaves like Tumbleweed) to make a persistent live system in the Ultra pendrive.

#1205

sudodus said: @1fallen,

I suggest that you simply *clone* the openSUSE iso file (I think Leap behaves like Tumbleweed) to make a persistent live system in the Ultra pendrive.

I know that, just wait I'm playing around now, I'm so close I just have to get the kernel in the right spot..:o But the Clone as suggested is the correct way. And Works as tested by both myself and sudodus.

#1206

Last one for tonite, Spiral Linux has been a challenge until now. (sudodus you need to try this one as persistent)

linux@SpiralLinux:~$ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  5.8G     0  5.8G   0% /dev
tmpfs          tmpfs     1.2G  1.4M  1.2G   1% /run
/dev/sdb4      iso9660   1.9G  1.9G     0 100% /run/live/medium
/dev/loop0     squashfs  1.7G  1.7G     0 100% /run/live/rootfs/filesystem.squashfs
tmpfs          tmpfs     5.8G   32M  5.8G   1% /run/live/overlay
overlay        overlay   5.8G   32M  5.8G   1% /
tmpfs          tmpfs     5.8G     0  5.8G   0% /dev/shm
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     5.8G  8.0K  5.8G   1% /tmp
tmpfs          tmpfs     1.2G   44K  1.2G   1% /run/user/1000

linux@SpiralLinux:~$ cat /etc/default/grub

GRUB_DISABLE_OS_PROBER=false

linux@SpiralLinux:~$ inxi -FzMzDz
System:    Kernel: 5.18.0-0.deb11.4-amd64 x86_64 bits: 64 Desktop: Xfce 4.16.0 
           Distro: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 20BFS3NJ00 v: ThinkPad T540p serial: <filter> 
           Mobo: LENOVO model: 20BFS3NJ00 v: 0B98401 WIN serial: <filter> UEFI: LENOVO 
           v: GMET91WW (2.39 ) date: 06/03/2021 
Battery:   ID-1: BAT0 charge: 84.9 Wh condition: 85.3/99.5 Wh (86%) 
CPU:       Info: Dual Core model: Intel Core i7-4600M bits: 64 type: MT MCP L2 cache: 4 MiB 
           Speed: 925 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 925 2: 911 3: 1292 4: 798 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel 
           Device-2: NVIDIA GK208M [GeForce GT 730M] driver: nouveau v: kernel 
           Device-3: Lite-On Integrated Camera type: USB driver: uvcvideo 
           Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.18.0-0.deb11.4-amd64 
Network:   Device-1: Intel Ethernet I217-LM driver: e1000e 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wireless 7260 driver: iwlwifi 
           IF: wlan0 state: down mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb 
           Report: ID: hci0 state: up running bt-v: 2.1 address: <filter> 
Drives:    Local Storage: total: 988.79 GiB used: 31.9 MiB (0.0%) 
           ID-1: /dev/sda vendor: PNY model: CS2311 1TB SSD size: 931.51 GiB 
           ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra size: 57.28 GiB 
Partition: ID-1: / size: 5.79 GiB used: 31.9 MiB (0.5%) fs: overlay source: ERR-102 
Swap:      ID-1: swap-1 type: zram size: 11 GiB used: 0 KiB (0.0%) dev: /dev/zram0 
Sensors:   System Temperatures: cpu: 38.0 C mobo: N/A gpu: nouveau temp: 34.0 C 
           Fan Speeds (RPM): cpu: 65535 fan-1: 0 fan-2: 
Info:      Processes: 187 Uptime: 2m Memory: 11.57 GiB used: 1.06 GiB (9.1%) Shell: Bash 
           inxi: 3.3.01 

It threw so many warnings, possibly due to Calamares as the installer.

#1207

Spiral Linux is based on Debian, but is different enough to create problems:

  • not recognized as Debian by dus-persistence
  • 'quiet' and 'splash' are not adjacent in the 'linux line' of grub and 'append line' of syslinux. This means mkusb-plug cannot make it persistent live. See details at this link.

I found an easy workaround to help mkusb-plug:

Inspection:


$ strings SpiralLinux_Cinnamon_11.220925_x86-64.iso |grep quiet
quiet
	linux	/live/vmlinuz-5.10.0-18-amd64 boot=live config quiet loglevel=0 splash findiso=${iso_path}
	linux	/live/vmlinuz-5.10.0-18-amd64 boot=live config quiet loglevel=0 splash findiso=${iso_path}
	linux	/live/vmlinuz-5.18.0-0.deb11.4-amd64 boot=live config quiet loglevel=0 splash findiso=${iso_path}
# linux /live/vmlinuz-5.10.0-18-amd64 boot=live config quiet loglevel=0 splash findiso=${iso_path} custom options here
quiet
%u (128=quiet, ..., 254=fast, recommended=%u)
(0=off, 128=quiet, ..., 254=fast).
quiet
quiet
quiet
%u (128=quiet, ..., 254=fast, recommended=%u)
(0=off, 128=quiet, ..., 254=fast).
quiet
quiet
quiet
quiet
quiet
quiet
	append boot=live config quiet loglevel=0 splash
f.d/l00__dp U"hellbtODO:3.3:sn-`["quiet"]`voidxcity`[_vel=0"]DidoifT: 5swapgiP
file is updaMartBammer <mrbm74Iniematiof--time--quietPr Engelkinker42'sprio_gsyscall detecg32bit
%be/gA)l, = gkiasc)im (")nanu ,s,yLoIquietDCimPoidod job>ni
@quietapple.orgWA
quiet
quiet
quiet

Checking how to replace the correct number of bytes:


$ echo -n 'quiet loglevel=0 splash'|wc -c
23
$ echo -n 'loglevel=0 persistence '|wc -c
23

Preprocessing with sed:


$ pv SpiralLinux_Cinnamon_11.220925_x86-64.iso | sed 's/quiet loglevel=0 splash/loglevel=0 persistence /' > persistent-SpiralLinux_Cinnamon_11.220925_x86-64.iso
1,96GiB 0:00:04 [ 405MiB/s] [================================================================================================================>] 100%            

$ ls -l
totalt 4116680
-rw-rw-r-- 1 olle olle 2107736064 okt 24 11:32 persistent-SpiralLinux_Cinnamon_11.220925_x86-64.iso
-rw-rw-r-- 1 olle olle 2107736064 okt 24 10:58 SpiralLinux_Cinnamon_11.220925_x86-64.iso

Running mkusb-plug with the output of the preprocessing:


$ mkusb-plug persistent-SpiralLinux_Cinnamon_11.220925_x86-64.iso
...

Now it works with mkusb-plug to create a persistent live drive. I verified that it works both in BIOS mode and UEFI mode


linux@SpiralLinux:~$ ( test -d /sys/firmware/efi && echo efi || echo bios ) >> bootmode
linux@SpiralLinux:~$ cat bootmode 
bios
efi
linux@SpiralLinux:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             16G     0   16G   0% /dev
tmpfs           3.2G  1.5M  3.2G   1% /run
/dev/sdb1       2.0G  2.0G     0 100% /run/live/persistence/sdb1
/dev/loop0      1.8G  1.8G     0 100% /run/live/rootfs/filesystem.squashfs
tmpfs            16G     0   16G   0% /run/live/overlay
[COLOR="#cc0000"]/dev/sdb3       109G   35M  103G   1% /run/live/persistence/sdb3
overlay         109G   35M  103G   1% /[/COLOR]
tmpfs            16G     0   16G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs            16G  4.0K   16G   1% /tmp
tmpfs           3.2G   40K  3.2G   1% /run/user/1000
linux@SpiralLinux:~$ 
#1208

sudodus said: Spiral Linux is based on Debian, but is different enough to create problems:

  • not recognized as Debian by dus-persistence
  • 'quiet' and 'splash' are not adjacent in the 'linux line' of grub and 'append line' of syslinux. This means mkusb-plug cannot make it persistent live. See details at this link.

I found an easy workaround to help mkusb-plug: Thanks for verifying it was just me. (Due to diffs in OS's used) I found an easy workaround to help mkusb-plug:

Checking how to replace the correct number of bytes:


$ echo -n 'quiet loglevel=0 splash'|wc -c
23
$ echo -n 'loglevel=0 persistence '|wc -c
23

Brilliant, I like it>>>>And about my kernels with other try's mentioned earlier, I can get so hyper-focused on a task that I want to accomplish that I fail to see the obvious, there just is no way I can see to put the kernel in on a read only file system, without using the Clone method>>>That was waste of a couple hours....LOL Verdict sudodus I really like the new verbiage, and it should help with a user's experience using mkusb, my preference will always be dus-plus.

#1209

@1fallen,

Thanks for the inspiration to add a feature to mkusb and thanks for testing it :-)

I'm glad that mkusb is useful for you. You like [FONT=Courier New]dus-plus[/FONT]. Maybe in the future you will find [FONT=Courier New]mkusb-plug[/FONT] useful too or its 'doer' sub-script [FONT=Courier New]mkusb-sedd[/FONT] if you work in text mode.


$ mkusb-sedd
 Run 'mkusb-sedd' with sudo or as root 
-------- mkusb-sedd makes it safer to create a boot drive --------
Clone from iso or image file to target device (e.g. USB pendrive)
Usage:
 sudo /path/mkusb-sedd --<task> <source file> <target device> 
Cloning:
 sudo mkusb-sedd --cloner file.iso /dev/sdx  # cloning standard live
 sudo mkusb-sedd --cloner file.img /dev/sdx  # cloning general image
 sudo mkusb-sedd --vfat   file.iso /dev/sdx  # cloning with FAT32 usbdata
 sudo mkusb-sedd --exfat  file.iso /dev/sdx  # cloning with exFAT usbdata
 sudo mkusb-sedd --ntfs   file.iso /dev/sdx  # cloning with NTFS  usbdata
Special tasks for Ubuntu 19.10+ and Debian 10+
 sudo mkusb-sedd --puer ubuntu.iso /dev/sdx  # persistent live drive
 sudo mkusb-sedd --pder debian.iso /dev/sdx  # persistent live drive
 sudo mkusb-sedd --nper ubuntu.iso /dev/sdx  # live-only drive
Press the Enter key to continue
Help:
mkusb-sedd -h
Version:
mkusb-sedd -v
Available devices 
NAME      SIZE TRAN   MODEL
sda     238,5G sata   SanDisk SD6SB1M2
sdb       3,7T sata   WDC WD4002FYYZ-0
nvme0n1 232,9G nvme   KINGSTON SA2000M8250G                  
#1210

I ran [FONT=Courier New]mkusb-plug[/FONT] with Kaisen Linux System Rescue and selected persistence according to Debian:


$ mkusb-plug kaisenlinuxrolling2.2RC2-amd64-SR.iso 
live system or temporary superuser permissions
source file: 'kaisenlinuxrolling2.2RC2-amd64-SR.iso'
--{puer|pder}
*** srctst ***
mount: /tmp/tmp.oruYSanCwJ: VARNING: enhet skrivskyddad, monterad som endast läsbar.
 ***** Neither Ubuntu nor Debian ***** 
Try persistence according to Ubuntu or Debian or live-only? (u/d/L)? d
 mkusb-plug might fail to create a persistent live drive 
 from kaisenlinuxrolling2.2RC2-amd64-SR.iso 
 You can try with regular mkusb 
Do you want to continue anyway? (y/N) y
...
         task: '--pder'
  source file: 'kaisenlinuxrolling2.2RC2-amd64-SR.iso'
target device:  /dev/sdc
...
Finally, please wait for a few more seconds ...
--------------------------------------------------------------------------------
NAME MODEL            FSTYPE  LABEL                  MOUNTPOINT   SIZE NAME
sdc  00SSD1           iso9660 Kaisen Linux SR 2.2RC2            111,8G sdc
sdc1                  iso9660 Kaisen Linux SR 2.2RC2              2,8G sdc1
sdc2                  vfat    Kaisen Linux SR 2.2RC2              896K sdc2
sdc3                  ext2    persistence                         109G sdc3
 Done :-) 

Using the option 'English' and then 'persistence' in the boot menu works as expected both in BIOS mode and UEFI mode.

[hr][/hr] I also ran [FONT=Courier New]dus[/FONT] with Kaisen Linux System Rescue and selected persistence according to [FONT=Courier New]dus-persistent[/FONT], but get no persistence. The problem is that it does not recognize Kaisen Linux as a Debian based distro.

It works after two tweaks:

  • set the label of the partition for persistence to [FONT=Courier New]persistence[/FONT]
  • create the file [FONT=Courier New]persistence.conf[/FONT] with the content [FONT=Courier New]/ union[/FONT] in the partition for persistence.

sudo tune2fs -L persistence /dev/sdx5
sudo bash -c "echo '/ union' > mountpoint/of/sdx5/persistence.conf"

So I would prefer mkusb-plug (or mkusb-sedd in text mode) with Kaisen Linux, because it works without tweaks.

#1211

sudodus said: Maybe in the future you will find [FONT=Courier New]mkusb-plug[/FONT] useful too or its 'doer' sub-script

Absolutely, as soon as I get a good feel for it. ;) I told you we would interact more. :)

Additional Feature: mkusb-plug

mkusb-plug is a bash shellscript, that wraps a graphical user interface around

[*]xorriso-dd-target to identify the target device via a plug-in test method. This is a very safe way to identify the target device.

[*]mkusb-sedd to create standard cloned live and installer drives and also persistent live drives.

[*]mkusb-tow to create Windows installer drives.

See details at /plug - wrapper shell-script with a GUI, can make persistent live drives via a new plug-in test method. I think at one time we even had a maintainer for Arch https://aur.archlinux.org/packages/mkusb

#1212

1fallen said: Absolutely, as soon as I get a good feel for it. ;)

I told you we would interact more. :)

Additional Feature: mkusb-plug

mkusb-plug is a bash shellscript, that wraps a graphical user interface around

[*]xorriso-dd-target to identify the target device via a plug-in test method. This is a very safe way to identify the target device.

[*]mkusb-sedd to create standard cloned live and installer drives and also persistent live drives.

[*]mkusb-tow to create Windows installer drives.

See details at /plug - wrapper shell-script with a GUI, can make persistent live drives via a new plug-in test method. :-)

I think at one time we even had a maintainer for Arch https://aur.archlinux.org/packages/mkusb This refers to github.com/lilyinstarlight/mkusb which is a different project with the same name :-P

"NOTE: This project is unrelated to the project at https://help.ubuntu.com/community/mkusb"

#1213

sudodus said: :-)

This refers to github.com/lilyinstarlight/mkusb which is a different project with the same name :-P

"NOTE: This project is unrelated to the project at https://help.ubuntu.com/community/mkusb"

Well at least in the link you show, it clearly states that difference. This could be confusing to sort out.

#1214

I have updated the mkusb PPA with packages for the next version, Lunar Lobster.


tester@april-2013:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu Lunar Lobster (development branch)
Release:        23.04
Codename:       lunar

tester@april-2013:~$ LANG=C apt-cache policy mkusb
mkusb:
  Installed: 22.2.3-1ubuntu2
  Candidate: 22.2.3-1ubuntu2
  Version table:
 *** 22.2.3-1ubuntu2 500
        500 https://ppa.launchpadcontent.net/mkusb/unstable/ubuntu lunar/main amd64 Packages
        500 https://ppa.launchpadcontent.net/mkusb/unstable/ubuntu lunar/main i386 Packages
        100 /var/lib/dpkg/status
tester@april-2013:~$ 
#1215

[SIZE=4]mkusb version 22.2.4 - 23.0.1[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. p_sniff: added kaisen to array dist_plug waiting for more edits, so not yet uploaded ...

. dus-iso2usb: increased size of partition for iso file 5G --> 7G [/td][/tr][/table]

  • mkusb 22.2.4
  • mkusb 23.0.1

[SIZE=3]Improvement in program package mkusb versions 22.2.4[/SIZE]

A function helps estimate which tools/methods of mkusb that are likely to work with the selected iso file. The [FONT=Courier New]file name[/FONT] and the content in **[FONT=Courier New]*.cfg[/FONT]** files (in the iso file) are used to identify the Linux distro (or Windows version). Another Linux distro is added to the array containing those distros that work with mkusb-plug.

[SIZE=3]Improvement in program package mkusb versions 23.0.1[/SIZE]

The version is updated to 23... to indicate that mkusb is updated during 2023. The size of the partition labeled 'isodevice', where dus-iso2usb stores the iso file, is increased from 5G to 7G because the Lunar Ubuntu Desktop iso file exceeds 5G.

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 23.0.1 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (if you don't care about mkusb-11, mkusb-nox, mkusb-bas)

sudo apt install dus
sudo apt install guidus

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1216

I just purchased a 128 Gb Sandisk USB 3.0 flash drive. Loaded it and Dolphin tells me it is only 114.6 Gb. The same issue is reported at https://forums.sandisk.com/t/new-128-gb-ultra-fit-only-reads-114-gb-in-computer/33882/2

As I'm only going to use this on Kubuntu, are there any special parameters I should use with mkusb to get the most media size out of this ?

There are a few install type files there which I don't need. They are certainly not 13.4 Gb

du -sh /media/********/6F5C-59ED/

1.7M /media/********/6F5C-59ED/

..Later: - The thread at https://forums.sandisk.com/t/sandisk-ultra-usb-3-0-only-114-gb-of-119-gb-available/33729/7 is a lot more informative. Oh well, looks like I only get 114.6 Gb :(

#1217

@oygle,

Before you start to optimize your system there are two issues to consider.

  • The size of drives are reported in two different units, GB = 10^9 bytes and GiB = 2^30 bytes

$ bc
bc 1.07.1
Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006, 2008, 2012-2017 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'. 
scale=2
128*10^9/2^30
119.20
114.6*2^30/10^9
123.05
  • The size of a flash drive is seldom exactly the nominal size.

So a drive with the nominal size 128 GB is 119.2 GiB (still nominal size).

A drive measured to have 114.6 GiB has 123.05 GB. If the nominal size is 128 GB it is 'slightly undersized', and this is rather common. (It happens that drives are slightly oversized too, but according to my experience USB pendrives are more often undersized.)

[hr][/hr] When you intend to run a persistent live system, you should consider how much drive space you need for storage in the 'usbdata' partition with NTFS, that can be read and written by Windows too. The default in 'dus-persistent' is to use half of the available space [after making the system] for 'usbdata' and half for persistence, the partition labeled 'writable'.

If you need more or less space for 'usbdata', increase or reduce the percentage for it. You can even select 100% of the available space [after making the system] for persistence, the partition labeled 'writable'.

Edit: See this link: the window 'select space for persistence (percent)'

#1218

@sudodus , thanks very much for your reply, much appreciated. I forgot to mention that I was wanting to wipe the drive only. I did that with mkusb, then of course I couldn't mount it. So I had to take the other option, to create a MSDOS partition table and FAT file system . Just started to copy files and it is going to take 90 minutes to copy only 4 Gb. I don't know why it is so slow, this is usb 3.0 usb stick and a usb 3.0 port ??

#1219

@oygle,

Some USB 3 sticks have a USB 3 interface, but are limited by slow memory cells or other internal electronics in the sticks. See this link and links from it.

#1220

@sudodus - thanks. The copy to the usb was SO much faster when I formatted it to EXT4. Previously it was MSDOS, incredibly slow. As long as Windows 10 can read the (ext4) formatted usb contents.

...Later - Win10 didn't like the usb, but looks like it is wsl to the rescue - https://www.bleepingcomputer.com/news/microsoft/windows-10-now-lets-you-mount-linux-ext4-filesystems-in-wsl-2/

#1221

@oygle,

Please share your experience with wsl.

#1222

sudodus said: Please share your experience with wsl.

I tried many methods from articles and still couldn't get it to mount the EXT4 usb. I had an appointment and had to rush, so just threw all the commands in a file. So the following are all bits and pieces ..

  1. After a few attempts at this and that, I realised one has to be running power shell as admin, so that seems a 'must'..
  1. This is what happened when I installed Ubuntu

PS C:\Windows\system32> wsl --install -d Ubuntu-22.04

Installing: Ubuntu 22.04 LTS Ubuntu 22.04 LTS has been installed. Launching Ubuntu 22.04 LTS... Installing, this may take a few minutes... WslRegisterDistribution failed with error: 0x80370102 Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/enablevirtualization Press any key to continue... The installation process for distribution 'Ubuntu-22.04' failed with exit code: 1. Error code: Wsl/InstallDistro/WSL_E_INSTALL_PROCESS_FAILED PS C:\Windows\system32>

I doubt virtualization was enabled in BIOS.

  1. The version I had installed of wsl seems to fit the requirements

PS C:\Windows\system32> wsl --version

WSL version: 1.2.0.0 Kernel version: 5.15.90.1 WSLg version: 1.0.51 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2846 PS C:\Windows\system32>

  1. It seemed this had to be wsl version 2, as version 1 i the default. This worked ..

PS C:\Windows\system32> wsl --set-default-version 2

For information on key differences with WSL 2 please visit https://aka.ms/wsl2 The operation completed successfully.

  1. Once the drive was plugged in, this worked fine ..

PS C:\Windows\system32> wmic diskdrive list brief

Caption DeviceID Model Partitions Size SAMSUNG MZVLW256HEHP-000L7 \\.\PHYSICALDRIVE0 SAMSUNG MZVLW256HEHP-000L7 3 256052966400 USB SanDisk 3.2Gen1 USB Device \\.\PHYSICALDRIVE1 USB SanDisk 3.2Gen1 USB Device 1 123041963520

  1. These 2 attempts at a mount failed, even though I had previously set the version to 2

PS C:\Windows\system32> wsl --mount .PHYSICALDRIVE0

This operation is only supported by WSL2. Error code: Wsl/Service/AttachDisk/WSL_E_WSL2_NEEDED PS C:\Windows\system32> wsl --mount \\.\PHYSICALDRIVE1 --partition 1 This operation is only supported by WSL2. Error code: Wsl/Service/AttachDisk/WSL_E_WSL2_NEEDED

  1. Show the available distros

PS C:\Windows\system32> wsl --list --online

The following is a list of valid distributions that can be installed. Install using 'wsl.exe --install <Distro>'.

NAME FRIENDLY NAME Ubuntu Ubuntu Debian Debian GNU/Linux kali-linux Kali Linux Rolling Ubuntu-18.04 Ubuntu 18.04 LTS Ubuntu-20.04 Ubuntu 20.04 LTS Ubuntu-22.04 Ubuntu 22.04 LTS OracleLinux_8_5 Oracle Linux 8.5 OracleLinux_7_9 Oracle Linux 7.9 SUSE-Linux-Enterprise-Server-15-SP4 SUSE Linux Enterprise Server 15 SP4 openSUSE-Leap-15.4 openSUSE Leap 15.4 openSUSE-Tumbleweed openSUSE Tumbleweed

  1. The "optional" requirement issues ...

PS C:\Windows\system32> wsl --mount .PHYSICALDRIVE0

This application requires the Windows Subsystem for Linux Optional Component. The system may need to be restarted so the changes can take effect. Error code: Wsl/WSL_E_WSL_OPTIONAL_COMPONENT_REQUIRED PS C:\Windows\system32> dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

Deployment Image Servicing and Management tool Version: 10.0.19041.844

Image Version: 10.0.19045.2788

Enabling feature(s) [==========================100.0%==========================]

In general there were prompts to suggest a restart was all that was needed to get it all going, yet after a restart , still the "mount" did not work.

The more I delved into wsl, I realised it was going to be a _total overkill_ for me, as all I wanted to do was mount an EXT4 formatted usb in Windows 10 and read the files.

I had the usb formatted as EXT4 because I noticed that MS-DOS formatted usb's seemed very slow at writing files in Kubuntu. I had nearly 128 Gb to put on the usb, so 'time' was an issue. Then I remembered I was using a GUI (Beyond Compare, because it does sychronising very neatly) to copy and that was why it was slow. So, with it formatted as EXT4 I copied a 1 Gb file to the usb - 12 seconds. Then formatted the usb with ..

sudo mkfs.ntfs -F --fast -v --label usb_backup /dev/sdb

so now it was NTFS. The copy only took 13 seconds, which I was surprised. So it was the GUI copy that gave a false impression of real time for a copy. Sometimes we have to walk down a path to then realise it's not ideal at this stage, and such it is for wsl for now. I'll leave the usb as NTFS and Win 10 will be as happy as a bumble bee on a fine spring day ..lol :)

I did find what does seem to be very good depth of support for wsl though, see https://github.com/microsoft/WSL , so if I do venture down the wsl path again, I will endeavour to ask the developers.

That's about it, sorry it's not more of a tutorial type format. :)

#1223

@oygle,

Thanks for sharing your experience with wsl :KS

#1224

@sudodus - you are welcome :)

#1225

@sudodus - The saga continues. Formatting the usb may make Win10 'happy', but for any file copying on Kubuntu, there are many files being skipped

cp: cannot create regular file '/media/******/usb_backup/home/****/Documents/********************_ 8029557642'$'\n''_20170330_1.pdf': Invalid argument

So now I will have to reformat to EXT4 for the copy/backup. On Win10, it was much easier than one would imagine. Once I enabled VM support in the BIOS, I can now see "Ubuntu 22.04 LTS" and if I go to file explorer there is a "Linux" icon. Click on that and there is a full Ubuntu system. So, I'm assuming all the problems/errors I found previously with wsl would not appear when one enables VM in the BIOS.

#1226

Hmm, so a few hours still trying to get wsl to mount the usb, and then noticed it was a "feature request" on the wsl issues on https://github.com/microsoft/WSL.

If I use NTFS or MS-DOS/VFAT etc for it can be read on Windows 10, there are far too many errors on Kubuntu with the copy. If I format it to EXT4 on Kubuntu, the copy works perfectly, but I can't mount that usb on Windows 10.

BTW, for anyone reading this, this is _NOT_ a mkusb problem/issue. :)

Would be great if there was a format that was completely inter-changeable between the 2 OS's. Yes, there are a few tools for reading EXT4 usb drives on Windows, but I noted there were concerns here and there the tools had a virus in them, and one note about the software searching in the registry,etc.

#1227

@oygle,

I think you have found a general problem, and it is worthwhile to find a reliable solution.

Right now I would suggest that you use networking: Install openssh-server into your Ubuntu guest system and for example Filezilla or WinSCP into Windows. Make sure that both the Windows host and the Ubuntu guest have working networks (easiest via a router). Then you can use Filezilla or WinSCP from Windows to read or write all file systems in Ubuntu, also ext4, because it is managed by openssh-server.

#1228

@sudodus , thanks for your help.

sudodus said: I think you have found a general problem, and it is worthwhile to find a reliable solution.

Yes, and the solution may only fit my needs of course. The best solution for all who wish to mount a EXT4 formatted usb on Windows would be for the WSL team to modify the software. It seems that will be some time coming.

sudodus said: Right now I would suggest that you use networking: Install openssh-server into your Ubuntu guest system and for example Filezilla or WinSCP into Windows. Make sure that both the Windows host and the Ubuntu guest have working networks (easiest via a router). Then you can use Filezilla or WinSCP from Windows to read or write all file systems in Ubuntu, also ext4, because it is managed by openssh-server.

I do actually have Samba going between the Kubuntu box and the Win10 box now, after having played around a bit with openssh, WinSCP,etc. It works but only setup for a few files. Of course I can extend that, yet the main objective was to have a usb backup (from Kubuntu/EXT4) that is portable. Meaning whilst travelling. So the Samba now relies on a router/LAN, but on travel don't have that luxury.

Of what I have read/learnt with wsl, mounting another drive that is _NOT_ usb is no problem though.

..Later - There is a very comprehensive article on how to access usb storage from WSL2 - https://github.com/jovton/USB-Storage-on-WSL2 . The conclusion comment in the article - > Using iSCSI, we were able to "fool" WSL2 into thinking it had a physical USB block device attached under "/dev".

#1229

@sudodus - you may be interested ..

After watching a few Youtube videos on how to connect a usb in wsl, I used the article at https://learn.microsoft.com/en-us/windows/wsl/connect-usb , and installed USBIPD-WIN ( see the section "Install the USBIPD-WIN project" ) , plus the tools and hardware database,etc. Windows power shell (as admin) still could not attach, as follows ..

usbipd wsl attach --busid 1-16

usbipd: error: WSL 'usbip' client not correctly installed. See https://github.com/dorssel/usbipd-win/wiki/WSL-support for the latest instructions.

So, followed the github instructions, and with a bit of fiddling, windows now sees it as attached

usbipd wsl list

BUSID VID:PID DEVICE STATE

1-2 046d:c077 USB Input Device Not attached 1-6 1199:907b Sierra Wireless EM7430 Qualcomm Snapdragon X7 LTE-A Not attached 1-7 8087:0a2b Intel(R) Wireless Bluetooth(R) Not attached 1-8 04f2:b5ab Integrated Camera Not attached 1-15 0bda:0316 Realtek USB 3.0 Card Reader Not attached 1-16 0781:5567 USB Mass Storage Device Attached - Ubuntu-22.04

yet even though I install dolphin, nautilus and an app called 'files' I don't think the Ubuntu side of things has it "mounted" ? Although a mount command reveals this ..

/dev/sdc on / type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)

So, it seems it is nearly there ??

#1230

[SIZE=4]Problems to make persistent live drives for standard Ubuntu 23.04 Desktop[/SIZE]

mkusb-dus had problems to make persistent live drives from the standard Ubuntu 23.04 'Lunar' Desktop iso file. The reason is that the 'linux line in grub' that is the 'cmdline' is modified compared to the previous versions. This Lunar version has a new installer and the boot structure was also modified.

Working alternatives:

  1. Cloning is still working in order to make live-only drives.

1a. Use mkusb-plug to make your persistent live drive. It works because it is 'almost cloning' and therefore manages the modified linux line in grub.

1b. Use dus-iso2usb in mkusb-dus 23.1.0, it works after an upgrade (or if you wish, a bug-fix).

1c. Use dus-persistent in mkusb-dus 23.1.1, it works after an upgrade (or if you wish, a bug-fix).

Now mkusb-dus works with the Ubuntu 23.04 Desktop iso file with the new installer.

  1. Use the legacy iso file.

cdimage.ubuntu.com/releases/lunar/release/ubuntu-23.04-desktop-legacy-amd64.iso

with the following sha256sum:


0cef2280b3d8710733231d1ad1c72474e6bbc41a0d8d2ea69f7728f3d60fb786 *ubuntu-23.04-desktop-legacy-amd64.iso

This iso file has the old installer 'Ubiquity' which is well-known by older versions of mkusb-dus.

It is a good idea to get the file via torrent:

**cdimage.ubuntu.com/releases/lunar/release/ubuntu-23.04-desktop-legacy-amd64.iso.torrent**

I have verified that mkusb-dus can make a persistent live drive from this legacy iso file.

  1. Use Ubuntu community flavours, that have not modified the boot structure. I have verified that mkusb-dus can make persistent live drives from the iso files of
  • Lubuntu 23.04, verified during the lunar iso testing cycle (uses the installer 'Calamares')
  • Xubuntu 23.04, verified now (uses the installer 'Ubiquity')
  • Kubuntu 23.04, verified now (uses the installer 'Ubiquity')
#1231

[SIZE=4]mkusb version 23.1.0 -- 23.1.5[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. dus-iso2usb: read_params, tweak_grub: check for 'layerfs' in grub in the iso file, when found modify the linux-line to match the boot structure of the new installer in standard Ubuntu 23.04 'Lunar' Desktop iso file.

. dus-persistent: probe_source, grub_n_iso tweak 5: check for 'layerfs' in grub in the iso file, when found modify the linux-line to match the boot structure of the new installer in standard Ubuntu 23.04 'Lunar' Desktop iso file. -mkusb-nox 23.1.2 . mktst: livedrive from df can list whole nvme device

. dus-iso2usb: read_params: minor fix to improve output when target drive size >= 128GB

. dus: p_snff & p_sniff: Modifications to show that only mkusb-plug works well to make persistent live drives with Debian 12 (drives by dus-persistent work only in UEFI mode)

. dus-persistent: partitioner: if [ "$part_type" == "gpt" ] then use template to avoid mismatch with grub versions > 2.04 (only workaround, new version of grub should be added to mkusb) . dus: p_sniff: Modification to show that also dus-persistent works well to make persistent live drives with Debian 12

. dus: p_usb_pack_manage: or (not and) condition for updating usb-pack and grub image (fixing old bug) [/td][/tr][/table]

  • mkusb 23.1.0
  • mkusb 23.1.1
  • mkusb 23.1.2
  • mkusb 23.1.3
  • mkusb 23.1.4
  • mkusb 23.1.5

[SIZE=3]Improvement in program package mkusb versions 23.1.0[/SIZE]

In dus-iso2usb, function read_params, the file [FONT=Courier New]grub.cfg[/FONT] in the iso file is inspected, and if it contains the string [FONT=Courier New]layerfs-path[/FONT], a logical variable is set and used by function tweak_grub to modify the linux-lines (cmd-lines) to match what is used in Ubuntu 23.04 Desktop (the iso file with the new installer). This matches what should also be used in grub-n-iso alias iso-boot setups.

[SIZE=3]Improvement in program package mkusb versions 23.1.1[/SIZE]

The corresponding tweaks (as in 23.1.0) were made in dus-persistent: function probe_source and function grub_n_iso at tweak 5. Now mkusb-dus works with the Ubuntu 23.04 Desktop iso file with the new installer.


linux (loop)/casper/vmlinuz boot=casper layerfs-path=minimal.standard.live.squashfs iso-scan/filename=$isofile quiet splash persistent
# and
linux (loop)/casper/vmlinuz boot=casper layerfs-path=minimal.standard.live.squashfs iso-scan/filename=$isofile quiet splash nopersistent

[SIZE=3]Improvement in program packages mkusb-nox and mkusb versions 23.1.2[/SIZE]

In mkusb-nox, a minor modification to make it able to list the content of an internal nvme drive

In mkusb: dus-iso2usb, a minor modification to improve the output when the target drive is big, size >= 128GB

[SIZE=3]Improvement in program package mkusb versions 23.1.3[/SIZE]

In dus, functions p_snff & p_sniff show what different parts of mkusb can do, and the output is modified to show that there are problems for dus-persistent with Debian 12. Only mkusb-plug works well to make persistent live drives with Debian 12 (drives by dus-persistent work only in UEFI mode).

[SIZE=3]Improvement in program package mkusb versions 23.1.4, 23.1.5[/SIZE]

Modification to minimize the risk for mismatch within grub (between the bootloader and the other parts of the grub package, which can stop booting in BIOS mode with the error message "'grub_disk_get_size' not found". This makes it work to make persistent live drives with Debian 12 (drives by dus-persistent work also in BIOS mode). It was a mistake that 'only' Debian 12 was affected, the problem was caused by a mismatch with the bootloader in the host operating system and independent of the iso file (and its operating system).

Finally, the links to usb-packs and grub images were not updated when grub was upgraded to a new version. This was fixed by replacing 'and' with 'or' in the controlling 'if' statement (a year-old bug, not recognized until now). [hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 23.1.1 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1232

Another change for booting the Ubuntu 23.04 ISO off a disk file with persistence is the casper-rw file no longer works, the file name needs to be "writable". No other changes, just change the name. Not sure if the partition name casper-rw still works.

#1233

ubfan1 said: Another change for booting the Ubuntu 23.04 ISO off a disk file with persistence is the casper-rw file no longer works, the file name needs to be "writable". No other changes, just change the name. Not sure if the partition name casper-rw still works.

Thanks for this heads up about disk file with persistence :-)

I re-labeled a 'writable' partition and Ubuntu 23.04 is still working as a persistent live drive. See the attached screenshot.

Edit: I tested later on with a system booted via grub and an iso file, 'iso-boot' alias 'grub-n-iso', when the external drive was connected, and it could use the casper-rw partition for persistence. So I found no difference there.

#1234

[SIZE=4]Tool to check that cloning was successful[/SIZE]

Edit { The original version of the shellscript is shown in this post. A major upgrade is shown in Post #1237. You may want to try both versions and select the original simpler version or the upgraded version. The main difference is that a second check may be performed on the content except the head and tail ends, where there is a partition table (and in case of gpt a backup partition table). }

Cloning from an image file, typically an iso file, to a USB drive is considered a robust process, but sometimes it fails. Maybe this is caused by problems with buffering when a big iso file is cloned to a pendrive with slow memory cells, maybe caused by flaky memory cells.

Anyway, I see that we need a convenient way to check that cloning was successful, so I created a small shellscript.

[SIZE=3][FONT=Courier New]diff-image-drive[/FONT] makes it easy to check by means of comparing the sha256sums[/SIZE]


#!/bin/bash

LANG=C
inversvid="\0033[7m"
resetvid="\0033[0m"
#redback="\0033[1;37;41m"
redback="\0033[97;41m"
#greenback="\0033[1;37;42m"
greenback="\0033[97;42m"
#faintvid="\0033[2m"
faintvid="\0033[90m"

function usage {

echo "usage:    sudo ${0##*/} <image-file> <device>
examples: sudo ${0##*/} ubuntu.iso /dev/sdc
          sudo ${0##*/} myfile.img /dev/sdc
version:  1.1"
exit 1
}
########################################################################
function checksum {

chksum=$(pv -Ss $size "$1" | sha256sum)
}
########################################################################

# main

########################################################################

if [ "$EUID" != "0" ] || [ $# -ne 2 ] || [ "$1" == "-h" ] || ! test -s "$1" || ! test -b "$2"
then
 usage
fi
echo -e "$inversvid Comparing content of '$1' and '$2' $resetvid"
echo -en "$faintvid"
echo -e "partprobe: "
partprobe
sleep 1
echo -e "umount ${2}*: "
if umount ${2}* 2>&1 | grep 'busy'
then
 echo -e "$resetvid$redback umount: could not unmount all partitions on $2 $resetvid"
 exit 1
else
 echo -e "done - no partition mounted on $2 $resetvid"
fi

echo -e "$inversvid calculating sha256sums ...$resetvid"
size=$(stat --format %s "$1")
checksum "$1"
chk1=$chksum
echo "file:   $chk1"
checksum "$2"
chk2=$chksum
echo "device: $chk2"
if [ "$chk1" == "$chk2" ]
then
 echo -e "$greenback content of iso/img file and device match $resetvid"
else
 echo -e "$redback content of iso/img file and device differ $resetvid"
fi

[SIZE=3]Demo:[/SIZE]

You need [FONT=Courier New]pv[/FONT] to run this script, install if not already installed


sudo apt update
sudo apt install pv

At first there is some previous content in the target device, an SSD connected via a USB to SATA adapter:


$ **sudo diff-image-drive mantic-desktop-amd64.iso /dev/sdc**
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdc' 
partprobe: 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
2,92GiB 0:00:18 [ 163MiB/s] [================================================================>] 100%            
file:   cdfaafb6be7b4b183b43bf395f7a1e12b14bcc6914c13ca8246a4cb00254ef6e  -
2,92GiB 0:00:14 [ 203MiB/s] [================================================================>] 100%            
device: ac65f5bb93207976cf59e4440147ffdda40e6e0ac3a3f964f525c0063660b51d  -
 content of iso/img file and device differ 

After cloning from the mantic iso file to the target device:


$ **sudo diff-image-drive mantic-desktop-amd64.iso /dev/sdc**
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdc' 
partprobe: 
Warning: Not all of the space available to /dev/sdc appears to be used, you can fix the GPT to use all of the space (an extra 462737388 blocks) or continue with the current setting? 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
2,92GiB 0:00:14 [ 208MiB/s] [================================================================>] 100%            
file:   cdfaafb6be7b4b183b43bf395f7a1e12b14bcc6914c13ca8246a4cb00254ef6e  -
2,92GiB 0:00:14 [ 204MiB/s] [================================================================>] 100%            
device: cdfaafb6be7b4b183b43bf395f7a1e12b14bcc6914c13ca8246a4cb00254ef6e  -
 content of iso/img file and device match 

In this case you need not worry about the warning from partprobe. A drive cloned from an [FONT=Courier New]iso[/FONT] file does not care about what is behind the cloned field.

[hr][/hr] However, a cloned image of a drive with a GPT (GUID partition table) should have its backup partition table at the tail end of the drive fixed. This is done with [FONT=Courier New]mkusb-dus[/FONT] when cloning an [FONT=Courier New]img[/FONT] file or extracting and cloning an [FONT=Courier New]img.gz[/FONT] or [FONT=Courier New]img.xz[/FONT] file. But it will also modify the main partition table at the head end of the drive, so [FONT=Courier New]diff-image-drive[/FONT] will find that content of the file and device differ.

If it is important to check the cloning of an [FONT=Courier New]img[/FONT] file, you can do it with another tool, for example the [FONT=Courier New]Ubuntu Startup Disk Creator[/FONT] or [FONT=Courier New]mkusb-nox[/FONT], check with [FONT=Courier New]diff-image-drive[/FONT] and after that use gpt-fix


$ **dus jammy-preinstalled-server-amd64.img**     # dus modifies the partition table after cloning an img file

$ **sudo diff-image-drive jammy-preinstalled-server-amd64.img /dev/sdc**
 Comparing content of 'jammy-preinstalled-server-amd64.img' and '/dev/sdc' 
partprobe: 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
3,50GiB 0:00:17 [ 208MiB/s] [================================================================>] 100%            
file:   cf51e240b865c94d72ad3b7b8c2c79c7f814092c775231a47648306e7f7df269  -
3,50GiB 0:00:17 [ 202MiB/s] [================================================================>] 100%            
device: 654d25bf029f8c7e83e340a0709c7640342c91a1ef6ba0b07597e8b7e2d43246  -
 content of iso/img file and device differ 

$ **usb-creator-gtk**                          # Ubuntu Startup Disk Creator does not modify, is only cloning also img files
# or
$ **sudo mkusb-nox jammy-preinstalled-server-amd64.img all**     # mkusb-nox does not modify, is only cloning also img files
 
$ **sudo diff-image-drive jammy-preinstalled-server-amd64.img /dev/sdc**
 Comparing content of 'jammy-preinstalled-server-amd64.img' and '/dev/sdc' 
partprobe: 
Warning: Not all of the space available to /dev/sdc appears to be used, you can fix the GPT to use all of the space (an extra 461522096 blocks) or continue with the current setting? 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
3,50GiB 0:00:17 [ 206MiB/s] [================================================================>] 100%            
file:   cf51e240b865c94d72ad3b7b8c2c79c7f814092c775231a47648306e7f7df269  -
3,50GiB 0:00:17 [ 202MiB/s] [================================================================>] 100%            
device: cf51e240b865c94d72ad3b7b8c2c79c7f814092c775231a47648306e7f7df269  -
 content of iso/img file and device match 

$ **gpt-fix**

Usage:   sudo /home/sudodus/bin/gpt-fix <device>

Example: sudo /home/sudodus/bin/gpt-fix /dev/sdx

/home/sudodus/bin/gpt-fix needs 'gdisk'

$ **sudo /home/sudodus/bin/gpt-fix /dev/sdc**
Problem: The secondary header's self-pointer indicates that it doesn't reside
umount: /dev/sdc1: inte monterad.
--------------------------------------------------
Do you want to fix the GPT on '/dev/sdc'? (y/N) y
GPT fdisk (gdisk) version 1.0.8

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): 
Problem: The secondary header's self-pointer indicates that it doesn't reside
at the end of the disk. If you've added a disk to a RAID array, use the 'e'
option on the experts' menu to adjust the secondary header's and partition
table's locations.

Identified 1 problems!

Command (? for help): 
Expert command (? for help): Relocating backup data structures to the end of the disk

Expert command (? for help): 
Recovery/transformation command (? for help): 
Recovery/transformation command (? for help): 
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdc.
The operation has completed successfully.

$ **sudo /home/sudodus/bin/gpt-fix /dev/sdc**      # only checking
The GPT seems fine or there is no GPT on '/dev/sdc'

$ **sudo diff-image-drive jammy-preinstalled-server-amd64.img /dev/sdc**
 Comparing content of 'jammy-preinstalled-server-amd64.img' and '/dev/sdc' 
partprobe: 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
3,50GiB 0:00:17 [ 208MiB/s] [================================================================>] 100%            
file:   cf51e240b865c94d72ad3b7b8c2c79c7f814092c775231a47648306e7f7df269  -
3,50GiB 0:00:17 [ 202MiB/s] [================================================================>] 100%            
device: 654d25bf029f8c7e83e340a0709c7640342c91a1ef6ba0b07597e8b7e2d43246  -
 content of iso/img file and device differ 

Conclusion: The main purpose of [FONT=Courier New]diff-image-drive[/FONT] is to check cloning of [FONT=Courier New]iso[/FONT] files to USB pendrives.

Cloning to HDDs and SSDs is much more reliable, so checking is not as important, and it is also more complicated if there is a GPT.

#1235

Question asked at https://askubuntu.com/questions/1467825/validating-an-iso-write-directly-after-writing

If you want to change the question; just edit/change as appropriate.

FYI: The tool works well..

I used it first grabbing a Lubuntu thumb-drive & used the tool to compare with what I believed it would be (ie. 23.04 daily)


guiverc@d7050-next:/de2900/lubuntu_64$   sudo diff_image_drive lunar-desktop-amd64.iso /dev/sdb
[sudo] password for guiverc: 
 Comparing content of 'lunar-desktop-amd64.iso' and '/dev/sdb' 
partprobe: 
umount /dev/sdb*:                                                                                                                       
done - no partition mounted on /dev/sdb                                                                                                 
 calculating sha256sums ...
2.89GiB 0:00:40 [72.7MiB/s] [========================================================================================>] 100%            
file:   92c1659668baab47269725a05a46115628801b5a464e2860b65edce50c9d0fcf  -
2.89GiB 0:03:29 [14.1MiB/s] [========================================================================================>] 100%            
device: 9b59a1dd41b245f176fc99af47c40e9c1fbe486f8558dcf82abbf78d197acd29  -
 content of iso/img file and device differ 

Alas it said they differed, but I was guessing about what was on it.

I wrote the mantic daily to thumb-drive, then re-ran the ^ command


guiverc@d7050-next:/de2900/lubuntu_64$ sudo diff_image_drive mantic-desktop-amd64.iso /dev/sdb
[sudo] password for guiverc: 
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdb' 
partprobe: 
Warning: Not all of the space available to /dev/sdb appears to be used, you can fix the GPT to use all of the space (an extra 24161036 blocks) or continue with the current setting?                                                                                            
umount /dev/sdb*:                                                                                                                       
done - no partition mounted on /dev/sdb                                                                                                 
 calculating sha256sums ...
2.92GiB 0:00:21 [ 141MiB/s] [========================================================================================>] 100%            
file:   a0ee778df45fed50bfd6d1bafe008b716ec211dffe2249a00efaaf88899e4c92  -
2.92GiB 0:03:32 [14.1MiB/s] [========================================================================================>] 100%            
device: a0ee778df45fed50bfd6d1bafe008b716ec211dffe2249a00efaaf88899e4c92  -
 content of iso/img file and device match 

I may boot the ISO/thumb-drive on a few boxes & compare again..

As I recall we noted some changes to a thumb-drive on usage in one bug report... (*maybe why the validation failed I'm wondering in my first exploration*)

#1236

guiverc said:

I may boot the ISO/thumb-drive on a few boxes & compare again..

As I recall we noted some changes to a thumb-drive on usage in one bug report... (*maybe why the validation failed I'm wondering in my first exploration*)

The written thumb-drive from my prior post/comment was booted on

  • hp prodesk 400 g1 sff (i5-4570, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)

a short play of the system, then shutdown.. and I returned to the thumb-drive to my primary box & again run

guiverc@d7050-next:/de2900/lubuntu_64$   sudo diff_image_drive mantic-desktop-amd64.iso /dev/sdb
[sudo] password for guiverc: 
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdb' 
partprobe: 
umount /dev/sdb*:                                                                                                                       
done - no partition mounted on /dev/sdb                                                                                                 
 calculating sha256sums ...
2.92GiB 0:00:19 [ 155MiB/s] [========================================================================================>] 100%            
file:   a0ee778df45fed50bfd6d1bafe008b716ec211dffe2249a00efaaf88899e4c92  -
2.92GiB 0:03:32 [14.1MiB/s] [========================================================================================>] 100%            
device: 821c6e85d8ebdeb907bf02109390cdb50516af92763a6c6039c2aed4570b66c7  -
 content of iso/img file and device differ 

This time the thumb-drive fails.. just as my attempt to test the *lunar* thumb-drive..

It's a near tool @sudodus, and I do LOVE the bright GREEN/RED indicator.. It'll almost always be run (I'd expect) post-ISO write though (*if it used an unknown by likely thumb-drive like I grabbed initially; the ISO date on the thumb-drive is possibly wanted **I suspect*).

#1237

@guiverc,

I'm glad that you find diff_image_drive useful :-)

Intuitively I did not expect that running a live (live-only) system would modify the cloned part of its boot drive.

But after some thinking, yes, it will write behind the cloned part (create a partition labeled 'writable' and write log files and possible crashdumps there). And when creating the partition there will be an entry in the partition table at the head of the drive (otherwise the partition would not be detected), and this will modify the sha256sum, so that the drive will no longer match the iso file.

This might/should be avoid when using the boot option nopersistent. I intend to check this.

Is it a big problem for you, that the sha256sum check works only before the drive is booted from?

  • Would you want some other tool, for example that would check on the file level, that all the files in the iso file and in the cloned part of the target drive match? I think it should be possible using rsync with the option -c (--checksum).
  • Would it be an option to skip the first few bytes, where the partition table resides, and compare the rest of the content of the iso file and drive?
#1238

sudodus said: @guiverc,

I'm glad that you find diff_image_drive useful :-)

Intuitively I did not expect that running a live (live-only) system would modify the cloned part of its boot drive.

But after some thinking, yes, it will write behind the cloned part (create a partition labeled 'writable' and write log files and possible crashdumps there). And when creating the partition there will be an entry in the partition table at the head of the drive (otherwise the partition would not be detected), and this will modify the sha256sum, so that the drive will no longer match the iso file.

This might/should be avoid when using the boot option nopersistent. I intend to check this.

Is it a big problem for you, that the sha256sum check works only before the drive is booted from?

  • Would you want some other tool, for example that would check on the file level, that all the files in the iso file and in the cloned part of the target drive match? I think it should be possible using rsync with the option -c (--checksum).
  • Would it be an option to skip the first few bytes, where the partition table resides, and compare the rest of the content of the iso file and drive?

I have no experience with any *nopersistent* option, so I'm skipping that in this reply.

For most usage of the tool, it doesn't matter that I can only check the ISO that was just written to the thumb-drive, as that's when I can see it being used most of the time. So it's NOTa big problem for me; covering 90%+ (*guessing the %, it maybe higher*) usage of the tool!

I went and used it (*or at least attempted to*) to check my '*grey-white*' Lubuntu thumb-drive contained the Lubuntu 23.04 *final* image, as I was convinced that was what was last written to it. I believe such a tool I'd find useful, however that is a feature I'd not use that often... but I could see myself using it on occasion (eg. I grab my Ubuntu-MATE thumb-drive & I could use the script to confirm the thumb-drive contains the *latest *ISO I see in my /de2900/ubuntu_mate_64/ directory; using the tool as it's quick & easy for me to start (*ignore & check up soon)*, instead of mounting & exploring the ISO & files on the thumb-drive; it also confirms the media hasn't been corrupted which I think would be useful).

If it's an option (-flag) that skips the first few bytes, or partition table (*but on the current diff_image_drive script*), that would probably be my choice I suspect... but that's just my personal preference. I can imagine me forgetting to add the flag; running the script & getting the bright red diff.warning, so I can just hit <UP> arrow & run the command again with the option to skip the first few bytes... I suspect that would be quicker than changing the script name & possibly less error prone, however that's just my opinion & either would be workable.

Thank you for the great tool, and effort/skill in creating diff_image_drive. It's greatly appreciated.

Chris g.

#1239

[SIZE=4]Tool to check that cloning was successful, new versions[/SIZE]

[SIZE=3][FONT=Courier New]diff-image-drive version 1.2 and 1.3[/FONT].[/SIZE]

Here are new versions of [FONT=Courier New]diff-image-drive[/FONT]. When the general check with sha256sum fails, it will check the content except the partition table (and backup table in case of img).

Version 1.2:


#!/bin/bash

LANG=C
inversvid="\0033[7m"
resetvid="\0033[0m"
#redback="\0033[1;37;41m"
redback="\0033[97;41m"
#greenback="\0033[1;37;42m"
greenback="\0033[97;42m"
#faintvid="\0033[2m"
faintvid="\0033[90m"
size=
skip=
chksum=
skpsum=

########################################################################

function usage {

echo "usage:    sudo ${0##*/} <image-file> <device>
examples: sudo ${0##*/} ubuntu.iso /dev/sdc
          sudo ${0##*/} myfile.img /dev/sdc
version:  1.2"
exit 1
}
########################################################################
function checksum {

chksum=$(pv -Ss $size "$1" | sha256sum)
}
########################################################################

function skiphead {

skpsum=$(pv -Ss $size "$1" | \
 dd bs=512 skip="$skip" 2>/dev/null | sha256sum)
}
########################################################################

# main

########################################################################

if [ "$EUID" != "0" ] || [ $# -ne 2 ] || [ "$1" == "-h" ] || ! test -s "$1" || ! test -b "$2"
then
 usage
fi
echo -e "$inversvid Comparing content of '$1' and '$2' $resetvid"
echo -en "$faintvid"
echo -e "partprobe: "
partprobe
sleep 1
echo -e "umount ${2}*: "
if umount ${2}* 2>&1 | grep 'busy'
then
 echo -e "$resetvid$redback umount: could not unmount all partitions on $2 $resetvid"
 exit 1
else
 echo -e "done - no partition mounted on $2 $resetvid"
fi

echo -e "$inversvid calculating sha256sums ...$resetvid"
size=$(stat --format %s "$1")
checksum "$1"
chk1=$chksum
echo "file:   $chk1"
checksum "$2"
chk2=$chksum
echo "device: $chk2"
if [ "$chk1" == "$chk2" ]
then
 echo -e "$greenback content of iso/img file and device match $resetvid"
else
 echo -e "$redback content of iso/img file and device differ $resetvid"
 echo "systems cloned from Ubuntu iso files are modified when used and
mkusb-dus fixes the partition table and its backup of img files with gpt
so trying again ..."
 echo -e "$inversvid skipping head/tail where the partition table resides $resetvid"
 if [ "${1##*.}" == "iso" ] || [ "${1##*.}" == "ISO" ]
 then
  skip=4
 else
  skip=33
  size=$((size-33*512))
 fi
 skiphead  "$1"
 chk1=$skpsum
 echo "file except head/tail:   $chk1"
 skiphead  "$2"
 chk2=$skpsum
 echo "device except head/tail: $chk2"
 if [ "$chk1" == "$chk2" ]
 then
  echo -e "$greenback except head/tail iso/img file and device match $resetvid"
 else
  echo -e "$redback except head/tail iso/img file and device differ $resetvid"
 fi 
fi

Version 1.3:


#!/bin/bash

LANG=C
inversvid="\0033[7m"
resetvid="\0033[0m"
redback="\0033[97;41m"
greenback="\0033[97;42m"
faintvid="\0033[90m"
size=
skip=
chksum=
skpsum=
str=
########################################################################

function usage {

echo "usage:    sudo ${0##*/} <image-file> <device>
examples: sudo ${0##*/} ubuntu.iso /dev/sdc
          sudo ${0##*/} myfile.img /dev/sdc
version:  1.3"
exit 1
}
########################################################################
function checksum {

chksum=$(pv -Ss $size "$1" | sha256sum)
}
########################################################################

function skiphead {

skpsum=$(pv -Ss $size "$1" | \
 dd bs=512 skip="$skip" 2>/dev/null | sha256sum)
}
########################################################################

function tablecmp {

tmp1=$(mktemp)
tmp2=$(mktemp)
echo -e "${faintvid}fdisk:"
fdisk "$1" -lu -o start,end,sectors,size,type | sed -e '1,/^$/'d | tr -s ' ' ' ' > "$tmp1"
fdisk "$2" -lu -o start,end,sectors,size,type | sed -e '1,/^$/'d | tr -s ' ' ' ' > "$tmp2"
echo -en "$resetvid"
str0=$(head -n1 "$tmp1")
str=$(diff "$tmp1" "$tmp2")
ret1=$?
str=$(echo "$str" |grep -v 'not in disk order' |sed -ne '/^[<>] /p' \
 |cut -d ' ' -f 1,5- |grep -v '^>$' |sed -e 's/^</file:/' -e 's/^>/device:/'| sort -k1 )
rm "$tmp1" "$tmp2"
return $ret1
}
########################################################################

# main

########################################################################

if [ "$EUID" != "0" ] || [ $# -ne 2 ] || [ "$1" == "-h" ] || ! test -s "$1" || ! test -b "$2"
then
 usage
fi
echo -e "$inversvid Comparing content of '$1' and '$2' $resetvid"
echo -en "$faintvid"
echo -e "partprobe: "
partprobe
sleep 1
echo -e "umount ${2}*: "
if umount ${2}* 2>&1 | grep 'busy'
then
 echo -e "$resetvid$redback umount: could not unmount all partitions on $2 $resetvid"
 exit 1
else
 echo -e "done - no partition mounted on $2 $resetvid"
fi
echo -n "target device: "
lsblk -ndo model "$2"
lsblk -o name,size,fstype,label,uuid "$2" | sed 's/writable.*/writable/'

echo -e "$inversvid calculating sha256sums ...$resetvid"
size=$(stat --format %s "$1")
if [ "${1##*.}" == "iso" ] && ! tablecmp "$1" "$2"
then
 echo "unmatched partition(s) :
$str"
 chk1=1
 chk2=2
else
 checksum "$1"
 chk1=$chksum
 echo "file:   $chk1"
 checksum "$2"
 chk2=$chksum
 echo "device: $chk2"
fi
if [ "$chk1" == "$chk2" ]
then
 echo -e "$greenback content of iso/img file and device match $resetvid"
else
 echo -e "$redback content of iso/img file and device differ $resetvid"
 echo "systems cloned from Ubuntu iso files are modified when used and
mkusb-dus fixes the partition table and its backup of img files with gpt
so trying ..."
 echo -e "$inversvid skipping head/tail where the partition table resides $resetvid"
 if [ "${1##*.}" == "iso" ] || [ "${1##*.}" == "ISO" ]
 then
  skip=4
 else
  skip=33
  size=$((size-33*512))
 fi
 skiphead  "$1"
 chk1=$skpsum
 echo "file except head/tail:   $chk1"
 skiphead  "$2"
 chk2=$skpsum
 echo "device except head/tail: $chk2"
 if [ "$chk1" == "$chk2" ]
 then
  echo -e "$greenback except head/tail iso/img file and device match $resetvid"
 else
  echo -e "$redback except head/tail iso/img file and device differ $resetvid"
 fi 
fi

[hr][/hr] [SIZE=3]Demo with [FONT=Courier New]diff-image-drive version 1.2[/FONT].[/SIZE]

Testing with a [maybe old now] Ubuntu Server Jammy compressed image daily iso file and USB SSD drive where it is cloned. The check fails because the partition table (and backup partition table) is fixed bus mkusb-dus and the modified partition table affects the checksum. Then a second check is performed where the partition table is skipped, and this check succeeds.


$ **sudo diff-image-drive jammy-preinstalled-server-amd64.img /dev/sdc**
[sudo] password for sudodus: 
 Comparing content of 'jammy-preinstalled-server-amd64.img' and '/dev/sdc' 
partprobe: 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
3,50GiB 0:00:17 [ 207MiB/s] [=================================>] 100%            
file:   cf51e240b865c94d72ad3b7b8c2c79c7f814092c775231a47648306e7f7df269  -
3,50GiB 0:00:17 [ 205MiB/s] [=================================>] 100%            
device: 654d25bf029f8c7e83e340a0709c7640342c91a1ef6ba0b07597e8b7e2d43246  -
 content of iso/img file and device differ 
systems cloned from Ubuntu iso files are modified when used and
mkusb-dus fixes the partition table and its backup of img files with gpt
so trying again ...
 skipping head/tail where the partition table resides 
3,50GiB 0:00:17 [ 200MiB/s] [=================================>] 100%            
file except head/tail:   2eda9fb2dd8564a7d810d7fba08eade3ee8927d0aaba51456bef1ed53db017ff  -
3,50GiB 0:00:17 [ 199MiB/s] [=================================>] 100%            
device except head/tail: 2eda9fb2dd8564a7d810d7fba08eade3ee8927d0aaba51456bef1ed53db017ff  -
 except head/tail iso/img file and device match 

Testing a [maybe old now] Lubuntu Mantic daily iso file and USB SSD drive where it is cloned. The check fails because the drive is used (booted from) and a partition labeled 'writable' was created at boot, and this modified the partition table. Then a second check is performed where the partition table is skipped, and this check succeeds.

See also the first screenshot matching this demo example, where the high-lighting colours are shown. (You may notice that the speed and times differ a little, and this is because I repeated the command to get the screenshot.)


$ **sudo diff-image-drive mantic-desktop-amd64.iso /dev/sdc**
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdc' 
partprobe: 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
2,92GiB 0:00:14 [ 207MiB/s] [=================================>] 100%            
file:   a0ee778df45fed50bfd6d1bafe008b716ec211dffe2249a00efaaf88899e4c92  -
2,92GiB 0:00:24 [ 123MiB/s] [=================================>] 100%            
device: 724e192f0c65e39fd9fdc233d5d2966421f4196102b4424485030db8b1666273  -
 content of iso/img file and device differ 
systems cloned from Ubuntu iso files are modified when used and
mkusb-dus fixes the partition table and its backup of img files with gpt
so trying again ...
 skipping head/tail where the partition table resides 
2,92GiB 0:00:15 [ 197MiB/s] [=================================>] 100%            
file except head/tail:   14ba2da53e11c2619cef7656c8b7b5011027ef444e423251f070b3db0739d7db  -
2,92GiB 0:00:24 [ 122MiB/s] [=================================>] 100%            
device except head/tail: 14ba2da53e11c2619cef7656c8b7b5011027ef444e423251f070b3db0739d7db  -
 except head/tail iso/img file and device match 

Next I tested with 'the wrong USB drive', so also checking 'except head/tail' (alias except the partition table) fails.


$ **sudo diff-image-drive mantic-desktop-amd64.iso /dev/sdc**
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdc' 
partprobe: 
umount /dev/sdc*: 
done - no partition mounted on /dev/sdc 
 calculating sha256sums ...
2,92GiB 0:00:14 [ 209MiB/s] [=================================>] 100%            
file:   a0ee778df45fed50bfd6d1bafe008b716ec211dffe2249a00efaaf88899e4c92  -
2,92GiB 0:00:14 [ 204MiB/s] [=================================>] 100%            
device: e7629228960239dbef5f76fb7893a7c0ed691efa8a75b6a38a6ded24c75c0323  -
 content of iso/img file and device differ 
systems cloned from Ubuntu iso files are modified when used and
mkusb-dus fixes the partition table and its backup of img files with gpt
so trying again ...
 skipping head/tail where the partition table resides 
2,92GiB 0:00:14 [ 199MiB/s] [=================================>] 100%            
file except head/tail:   14ba2da53e11c2619cef7656c8b7b5011027ef444e423251f070b3db0739d7db  -
2,92GiB 0:00:14 [ 202MiB/s] [=================================>] 100%            
device except head/tail: 336f1555ffd8846788737bc106e6b0680c4e1fc548ada39e3428666ad1b2d16f  -
 except head/tail iso/img file and device differ 

[SIZE=3]Demo with [FONT=Courier New]diff-image-drive version 1.3[/FONT].[/SIZE]

See the second and third screenshots, where the high-lighting colours are shown. Please notice that the calculation of sha256sums is only made once in the file and once in the device when checking iso files. This will save time when iso-testing, particularly when using slow USB pendrives.

  1. Directly after cloning, [FONT=Courier New]diff-image-drive_demo-1.3-1.png[/FONT]
  1. After the drive was booted, so that a partition was created, [FONT=Courier New]diff-image-drive_demo-1.3-2.png[/FONT]
#1240

guiverc said: I have no experience with any *nopersistent* option, so I'm skipping that in this reply.

I checked running the Lubuntu Mantic live with the boot option [FONT=Courier New]nopersistent[/FONT], and as I expected, the USB drive was not modified at all so that the first check by [FONT=Courier New]diff-image-drive[/FONT] found a match also after booting into the drive.


...
 content of iso/img file and device match 

But adding [FONT=Courier New]nopersistent[/FONT] at the grub menu is not convenient during iso-testing, so you can use the upgraded version and let it check the content except for the locations of the partition table.

#1241

I LOVE it.

Inserted my primary Lubuntu thumb-drive; the one that has yesterday's *mantic daily* on it, was used in a simple QA-test (*thus altered* *slightly outside of image itself*) and


guiverc@d7050-next:/de2900/lubuntu_64$   sudo ~/diff_image_drive.sh mantic-desktop-amd64.iso /dev/sdb
[sudo] password for guiverc: 
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdb' 
partprobe: 
umount /dev/sdb*: 
done - no partition mounted on /dev/sdb 
 calculating sha256sums ...
2.92GiB 0:00:30 [97.7MiB/s] [========================================================================================>] 100%            
file:   a0ee778df45fed50bfd6d1bafe008b716ec211dffe2249a00efaaf88899e4c92  -
2.92GiB 0:03:31 [14.1MiB/s] [========================================================================================>] 100%            
device: 821c6e85d8ebdeb907bf02109390cdb50516af92763a6c6039c2aed4570b66c7  -
 content of iso/img file and device differ 
systems cloned from Ubuntu iso files are modified when used and
mkusb-dus fixes the partition table and its backup of img files with gpt
so trying again ...
 skipping head/tail where the partition table resides 
2.92GiB 0:00:25 [ 119MiB/s] [========================================================================================>] 100%            
file except head/tail:   14ba2da53e11c2619cef7656c8b7b5011027ef444e423251f070b3db0739d7db  -
2.92GiB 0:03:31 [14.1MiB/s] [========================================================================================>] 100%            
device except head/tail: 14ba2da53e11c2619cef7656c8b7b5011027ef444e423251f070b3db0739d7db  -
 except head/tail iso/img file and device match 

This *confirms *the thumb-drive contains the ISO I want it to contain, PLUS from that report I can see I've actually used it in a QA-test of some sort due to the partition table change(s). That output makes perfect sense to me & my usage. The RED & GREEN highlight makes it super easy (*for me*) to use !

Thank you !

#1242

For the record.. My favorite & used tool will be version 1.3

It provides the *detail* I liked with the version 1.2 tool, but also uses fewer cycles (*power & hardware usage*), even if the saved time I'll rarely notice (*given I start it off & then covering most of the qterminal window with my browser or other windows; though as my window positioning means I can read the two left most characters of the terminal, the color highlighting used will let me see results & know when I can return & its done*).

*Note: I've not run it today; this is what I recall of yesterday's testing as I try & complete stuff I didn't get done as hoped yesterday.*

#1243

[SIZE=4]mkusb version 23.1.6[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. dus: p_toolsel: "$source ... --> "\"$source\" ... to allow file names with spaces to be transferred to dus-iso2usb [/td][/tr][/table]

  • mkusb 23.1.6

[SIZE=3]Improvement in program package mkusb version 23.1.6[/SIZE]

A user was affected by a classical bug: spaces in the source file name made dus fail to call dus-iso2usb correctly. I had overlooked one step in the transfer of the file name.

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 23.1.6 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1244

This is mostly FYI @Sudodus

I just had a write of daily & diff error (*I included the last bit of the zsync_mantic script; as the last issue I had was actually after a failed zsync, alas I didn't notice it fast enough*).


Read mantic-desktop-amd64.iso. Target 95.7% complete.      *************************************************
downloading from http://cdimage.ubuntu.com/lubuntu/daily-live/current/mantic-desktop-amd64.iso:
#################### 100.0% 1158.0 kBps DONE      

verifying download...checksum matches OK
used 2894548992 local, fetched 130198938
-rw------- 1 guiverc guiverc 3.2G Jul 20 17:03 mantic-desktop-amd64.iso.2023-07-20
-rw-rw-r-- 1 guiverc guiverc  57K Jul 21 02:53 mantic-desktop-amd64.manifest.2023-07-20
-rw------- 1 guiverc guiverc 3.2G Jul 26 17:03 mantic-desktop-amd64.iso.2023-07-26
-rw-rw-r-- 1 guiverc guiverc  57K Jul 27 02:54 mantic-desktop-amd64.manifest.2023-07-27
-rw------- 1 guiverc guiverc 3.2G Jul 29 16:02 mantic-desktop-amd64.iso.20230729
-rw-rw-r-- 1 guiverc guiverc  57K Jul 30 02:52 mantic-desktop-amd64.manifest.20230729
-rw------- 1 guiverc guiverc 2.9G Sep 18 16:57 mantic-desktop-amd64.iso.zs-old
-rw------- 1 guiverc guiverc 2.9G Sep 18 16:57 mantic-desktop-amd64.iso.old
-rw-rw-r-- 1 guiverc guiverc  57K Sep 19 02:51 mantic-desktop-amd64.manifest.old
-rw-rw-r-- 1 guiverc guiverc 5.7M Sep 19 02:58 mantic-desktop-amd64.zsync.old
-rw------- 1 guiverc guiverc 2.9G Sep 19 23:55 mantic-desktop-amd64.iso
-rw-rw-r-- 1 guiverc guiverc  57K Sep 20 09:08 mantic-desktop-amd64.manifest
-rw-rw-r-- 1 guiverc guiverc 5.7M Sep 20 09:57 mantic-desktop-amd64.iso.zsync
** linux-generic
linux-generic    6.5.0.5.7
** prior ISO
calamares    3.3.0-alpha2-0ubuntu5
calamares-settings-lubuntu    1:23.10.3
calamares-settings-ubuntu-common    1:23.10.3
casper    1.482
lubuntu-default-settings    23.10.1
** latest ISO
calamares    3.3.0-alpha2-0ubuntu5
calamares-settings-lubuntu    1:23.10.3
calamares-settings-ubuntu-common    1:23.10.3
casper    1.482
lubuntu-default-settings    23.10.1
** diff
guiverc@d7050-next:/de2900/lubuntu_64$   sudo mkusb-nox mantic-desktop-amd64.iso all
[sudo] password for guiverc: 
The iso file SHOULD BE loop mounted on a temporary file READ-ONLY:
mount: /tmp/tmp.OmEi8RslTT: WARNING: source write-protected, mounted read-only.
disk_name_type=debian
Ubuntu mantic 23.10 amd64 i386  _found_ in iso-file
Ubuntu mantic 23.10 amd64 i386  _found_ in /dev/sdb
MODEL      NAME FSTYPE  LABEL                SIZE
STORE N GO sdb  iso9660 Lubuntu 23.10 amd64 14.4G
           sdb1 iso9660 Lubuntu 23.10 amd64  2.8G
           sdb2 vfat    ESP                  4.9M
           sdb3                              300K
           sdb4 ext4    writable            11.6G
 Final checkpoint 
Install to /dev/sdb? (y/n)
y
dd if="mantic-desktop-amd64.iso" of=/dev/sdb bs=1M status=progress oflag=dsync ...
3024537600 bytes (total size to be cloned)
3024093184 bytes (3.0 GB, 2.8 GiB) copied, 1118 s, 2.7 MB/s
2884+1 records in
2884+1 records out
3024537600 bytes (3.0 GB, 2.8 GiB) copied, 1117.86 s, 2.7 MB/s
The Ubuntu mantic 23.10 amd64 i386  USB device is re-cloned  :-)
guiverc@d7050-next:/de2900/lubuntu_64$   sudo diff_image_drive mantic-desktop-amd64.iso /dev/sdb
[sudo] password for guiverc: 
 Comparing content of 'mantic-desktop-amd64.iso' and '/dev/sdb' 
partprobe: 
Warning: Not all of the space available to /dev/sdb appears to be used, you can fix the GPT to use all of the space (an extra 24378716 blocks) or continue with the current setting? 
Error: Partition(s) 2, 3, 4 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.
umount /dev/sdb*: 
done - no partition mounted on /dev/sdb 
 calculating sha256sums ...
2.82GiB 0:00:26 [ 106MiB/s] [===================================================================================================================================================================>] 100%            
file:   c07e6b5b4215a04b721871ab9437f1b240c126aed5aab0456ac096af37248f6d  -
2.82GiB 0:03:23 [14.2MiB/s] [===================================================================================================================================================================>] 100%            
device: 96ea87de289d2dbb026cf8a36e8bb9b97307c361f559e43e77ce538ab908f77e  -
 content of iso/img file and device differ 
systems cloned from Ubuntu iso files are modified when used and
mkusb-dus fixes the partition table and its backup of img files with gpt
so trying again ...
 skipping head/tail where the partition table resides 
2.82GiB 0:00:26 [ 107MiB/s] [===================================================================================================================================================================>] 100%            
file except head/tail:   746ed316d2f58f6a33b568c946e4335beb5869f5c4dcc6b8a178581437af6e5c  -
2.82GiB 0:03:24 [14.1MiB/s] [===================================================================================================================================================================>] 100%            
device except head/tail: d64d8255cbb7f858f2f64c80ac166b1ce5de0d71c4c3ee6922cbaf70902be150  -
 except head/tail iso/img file and device differ 

These issues are now extremely rare, but I'm writing fewer ISOs to media now than I used to, thus my *hitting* these issues will be less often.

#1245

@guiverc,

Thanks for the feedback :-)

I'm glad that most of your cloning is successful nowadays. Anyway, [FONT=Courier New]diff_image_drive[/FONT] works and can detect when there are issues.

I notice that the average write speed (during cloning) is very low, 2.7 MB/s. Has it been constant for this 'STORE N GO' pendrive? Or has it been gradually decreasing? If it has been decreasing, it might get faster and more reliable, if you wipe the whole device (overwrite with zeros), which is an option of dus as well as of mkusb-nox.

#1246

[SIZE=4]mkusb version 23.2.0[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. modications in dus, dus-iso2usb and a new file .. dd_grub-boot-template-for-uefi-n-bios_grub-new.img.xz: . new template with grub 2.12-rc1 (replacing 2.0.6) . new grub menuentries: .. 'live-only with toRAM' and .. new memtest86+ v6.20 that works also in UEFI mode [/td][/tr][/table]

  • mkusb 23.2.0

[SIZE=3]Improvement in program package mkusb version 23.2.0[/SIZE]

This upgrade of dus-iso2usb was triggered by problems to boot in UEFI mode with secure boot in a Dell Latitude 3520 with 11th generation Intel i3 CPU.

  • A USB drive with Ubuntu (and Ubuntu flavours) version 23.10 *cloned* from the iso file boots. A drive by [FONT=Courier New]mkusb-plug[/FONT] boot too, also persistent live drives (because they are semi-cloned by [FONT=Courier New]sed[/FONT]).
  • But drives made by [FONT=Courier New]dus-persistent[/FONT] and [FONT=Courier New]dus-iso2usb[/FONT] failed to boot. After some tests I concluded that it would be easiest to upgrade and maintain [FONT=Courier New]dus-iso2usb[/FONT]. I made a new template file,

dd_grub-boot-template-for-uefi-n-bios_grub-new.img.xz

that should be fairly easy to upgrade with future versions of grub, when necessary to make it boot in computers with even stricter policies.

When working with a new template, it was easy to add a new menuentry (live-only with toRAM), which allows unplugging the boot drive.

It was also possible to add menuentries for [FONT=Courier New]memtest86+ v6.20[/FONT], which can work in UEFI mode (but not with secure boot).

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 23.2.0 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1247

I use this on a regular basis, it works well.

At the very end, an information box pops up with a font that is so tiny it is unreadable. It does not affect usage, but I wonder if anyone else has noticed it.

Keep up the good work. Tony

#1248

@vidtek,

Thanks for the feedback :-)

Please tell me what you have (flavour and version of Ubuntu) and what you did (how you used mkusb), and what mkusb wrote before and if possible, attach a screenshot of the information box that pops up.

#1249

Will do, next available spare time to do it will be Sunday! Equipment and ubuntu flavour in my signature. Tony.

#1250

OK well I had a go today with an 8gb microsd through a trancend usb adaptor.

My system:-``` $ inxi -F System: Host: linuxmint Kernel: 5.15.0-84-generic x86_64 bits: 64 Desktop: KDE Plasma 5.24.7 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: ASUSTeK model: STRIX Z270E GAMING v: Rev 1.xx serial: <superuser required> UEFI: American Megatrends v: 1501 date: 07/13/2021 CPU: Info: quad core model: Intel Core i7-7700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 4500 min/max: 800/4500 cores: 1: 4500 2: 4500 3: 4500 4: 4500 5: 4500 6: 4500 7: 4500 8: 4500 Graphics: Device-1: NVIDIA TU116 [GeForce GTX 1660] driver: nouveau v: kernel Device-2: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb driver: cx23885 v: 0.0.4 Device-3: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb driver: cx23885 v: 0.0.4 Device-4: GEMBIRD Generic UVC 1.00 camera [AppoTech AX2311] type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: nouveau resolution: 1920x1080 OpenGL: renderer: NV168 v: 4.3 Mesa 23.0.4-0ubuntu1~22.04.1 Audio: Device-1: Intel 200 Series PCH HD Audio driver: snd_hda_intel Device-2: NVIDIA TU116 High Definition Audio driver: snd_hda_intel Device-3: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb driver: cx23885 Device-4: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb driver: cx23885 Sound Server-1: ALSA v: k5.15.0-84-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel Ethernet I219-V driver: e1000e IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 10:7b:44:f2:50:51 IF-ID-1: lxcbr0 state: down mac: 00:16:3e:00:00:00 IF-ID-2: vmnet1 state: unknown speed: N/A duplex: N/A mac: 00:50:56:c0:00:01 IF-ID-3: vmnet8 state: unknown speed: N/A duplex: N/A mac: 00:50:56:c0:00:08 Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 00:1A:7D:DA:71:03 bt-v: 2.1 Drives: Local Storage: total: 9.34 TiB used: 7.47 TiB (80.0%) ID-1: /dev/nvme0n1 vendor: Sabrent model: Rocket Q size: 1.82 TiB ID-2: /dev/nvme1n1 vendor: Crucial model: CT2000P3PSSD8 size: 1.82 TiB ID-3: /dev/nvme2n1 vendor: SK Hynix model: PC401 HFS256GD9TNG-62A0A size: 238.47 GiB ID-4: /dev/nvme3n1 vendor: Crucial model: CT2000P3SSD8 size: 1.82 TiB ID-5: /dev/sda vendor: Toshiba model: HDWE140 size: 3.64 TiB ID-6: /dev/sdf type: USB vendor: Transcend model: TS-RDF5A Transcend size: 7.42 GiB Partition: ID-1: / size: 48.3 GiB used: 33.64 GiB (69.7%) fs: ext4 dev: /dev/nvme2n1p5 ID-2: /boot/efi size: 96 MiB used: 35.4 MiB (36.9%) fs: vfat dev: /dev/nvme2n1p1 ID-3: /home size: 109.44 GiB used: 42.98 GiB (39.3%) fs: ext4 dev: /dev/nvme2n1p6 Swap: ID-1: swap-1 type: file size: 2 GiB used: 324.8 MiB (15.9%) file: /swapfile Sensors: System Temperatures: cpu: 57.0 C mobo: N/A gpu: nouveau temp: 35.0 C Fan Speeds (RPM): N/A gpu: nouveau fan: 0 Info: Processes: 338 Uptime: 1h 1m Memory: 15.55 GiB used: 6.17 GiB (39.7%) Shell: Bash inxi: 3.3.13


Here are the results, 
[LIST=1]
[*]I first chose install make a boot device
[*]then again as it was repeated
[*]the next box I chose the second option, "Live only"
[*]the next item was critical, I chose the first item which turned out to be incorrect "dus ISO2grub"
[*]the second attempt after the first failed was the second choice "dus live" cloning method  this worked.
[*]the next box asked to confirm the install location the trancend usb device
[*]then a stop/go box choice
[*]a pop up information progress box appeared then disappeared as "done" was written in the terminal.
[*]Immediately the finish box with the tiny fonts came up.
[*]
[/LIST]

That's it, check out the pictures I took.

Hope this helps, Tony.[ATTACH=CONFIG]292904[/ATTACH][ATTACH=CONFIG]292905[/ATTACH][ATTACH=CONFIG]292906[/ATTACH][ATTACH=CONFIG]292907[/ATTACH][ATTACH=CONFIG]292908[/ATTACH]
#1251

@vidtek,

I notice that four of the five pop-up windows have very small text font. I guess that is what you want to me see, and if possible, fix.

This depends on the screen resolution. [FONT=Courier New]zenity[/FONT] is used to create the pop up windows (messages, dialogues etc). In some of the zenity windows, it is possible to select font, but I have not discovered how to change the font of all zenity windows.

How many pixels: [FONT=Courier New]width x height[/FONT] do you use? [FONT=Courier New]3840 x 2160[/FONT] or higher resolution? How big is the monitor?

I notice that there is no problem with the terminal window. You can run dus with the option -d


dus -d file.iso

and get most of the dialogue with the TUI program [FONT=Courier New]dialog[/FONT] (replacing the GUI dialogue of [FONT=Courier New]zenity[/FONT]).

[hr][/hr]

I might try with [FONT=Courier New]yad[/FONT] to make it easy to control the font size (and get more options) according to this link

www.linuxquestions.org/questions/linux-newbie-8/custom-zenity-menu-how-to-increase-font-size-4175653829

I am afraid, that it will be a lot of tweaking until mkusb is stable using [FONT=Courier New]yad[/FONT], but it might be necessary in the near future, when also relatively small screens have very high resolution (and small pixel size).

#1252

How many pixels: width x height do you use? 3840 x 2160 or higher resolution? How big is the monitor?

1920 x 1080 It is screened on a 55" Samsung tv Model no. QE55QN95BATXXU in my living room (I live in a grandad/granny flat). All the rest of the gear is in the loft. It is piped via HDMI (arc2) and switched for various inputs through my Yamaha RX-V781 home theatre amp. Two computers and HD homerun are the sources. I do not use the Samsung for off-air or streaming, just Mythtv through my main computer. I can't stand Samsung's crappy interface where they throw all their advertising and streaming stuff at you. I just use it as a monitor and it's great for that. At 1920 x 1080 I can read text and watch stuff without glasses (I'm 73 btw).

I have seen the term Zenity pop up when starting Dus, but I have no idea what it is, googling is the thing I suppose.

The issue does not detract from the programmes usefulness, just a minor irritation. I'll give TUI a go, although once again haven't a clue what it is! The same applies to YAD!

Cheers Tony.

#1253

@vidtek,

Thanks for the details :-) We are about the same age, I'm 76.

  • Zenity is the name of the linux program, that creates the pop-up windows to create the graphical user interface (GUI) of mkusb. Zenity is included in the main repository of Ubuntu and used by many GUI programs (not only mkusb).
  • Dialog is the name of a corresponding program that creates a text user interface (TUI) with similar functions as the GUI made by zenity.
  • Yad is is the name of the linux program, that creates the pop-up windows to create a graphical user interface (GUI). It is similar to zenity, but has more 'bells and whistles', so I think it can be used to create windows with text that is suitable also on screens with high resolution or when you need extra big text. (But I am afraid that it is a lot of work to modify the program code of mkusb to use yad instead of zenity.)

[hr][/hr] It is also possible to work around the problem with small fonts in the pop-up windows temporarily while using mkusb and reset to your favourite setting afterwards. See how to do it via the settings menu according to the attached screenshot: 200% means that the width and height of everything, including text, are twice as big as before. I don't know how to do it in Kubuntu, but there should be a tool that can do the same job as the settings menu of [FONT=Courier New]gnome-control-center[/FONT] in standard Ubuntu Desktop.

Edit: I modified the fonts in Kubuntu, which had an influence on most but not all pop-up windows of dus. See the second attached screenshot.

I think Kubuntu uses Xorg (not Wayland), and then it should be possible to change the resolution of the screen (how many pixels that are sent to the screen), and it can also be a workaround to increase the size of the text in the pop-up windows. It should be easy to change back to the full resolution of the screen.

#1254

sudodus said: @vidtek,

Thanks for the details :-) We are about the same age, I'm 76.

  • Zenity is the name of the linux program, that creates the pop-up windows to create the graphical user interface (GUI) of mkusb. Zenity is included in the main repository of Ubuntu and used by many GUI programs (not only mkusb).
  • Dialog is the name of a corresponding program that creates a text user interface (TUI) with similar functions as the GUI made by zenity.
  • Yad is is the name of the linux program, that creates the pop-up windows to create a graphical user interface (GUI). It is similar to zenity, but has more 'bells and whistles', so I think it can be used to create windows with text that is suitable also on screens with high resolution or when you need extra big text. (But I am afraid that it is a lot of work to modify the program code of mkusb to use yad instead of zenity.)

[hr][/hr] It is also possible to work around the problem with small fonts in the pop-up windows temporarily while using mkusb and reset to your favourite setting afterwards. See how to do it via the settings menu according to the attached screenshot: 200% means that the width and height of everything, including text, are twice as big as before. I don't know how to do it in Kubuntu, but there should be a tool that can do the same job as the settings menu of [FONT=Courier New]gnome-control-center[/FONT] in standard Ubuntu Desktop.

Edit: I modified the fonts in Kubuntu, which had an influence on most but not all pop-up windows of dus. See the second attached screenshot.

I think Kubuntu uses Xorg (not Wayland), and then it should be possible to change the resolution of the screen (how many pixels that are sent to the screen), and it can also be a workaround to increase the size of the text in the pop-up windows. It should be easy to change back to the full resolution of the screen.

I did do a Googling of zenity TUI and YAD. I haven't done any programming since writing my own service programme in Database3 + in the 1980's for my Video wall/projector repair and installation business in Australia, so I am a bit rusty to say the least. It's been years since I used Gnome, so I have no idea what tools are available there. Kubuntu with plasma is just so much better than anything else I have tried that it's been my default for years now.

Kubuntu gives a choice on the login screen of xorg, wayland and something else I can't remember the name of at the moment (don't get old - oh dear sorry too late for you as well as I!). I use xorg with nouveau. I had too many issues with Nvidia's proprietary drivers and the latest Nouveau driver works just fine for my purposes.

I'll give your latest build a go when it has the new options added, I'll look out for it, actually I'll do the PPA thing so it comes automatically, and let you know how it turns out on my system. Cheers Tony.

#1255

[SIZE=4]mkusb version 24.0.1, 24.0.2, 24.0.3[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. modications in dus-iso2usb: .. tweak_grub: tweak 5: no persistent option when 'persistent is false'

. modications in dus: .. p_menudz, p_zensize: increased height of window to keep the whole menu list within the window (without scrolling) for new version of zenity .. p_source, p_target, p_setting, p_checkpoint, p_lisdz: The window width is increased .. t_dus_p: 'dus-persistent ... problem with secure boot' [/td][/tr][/table]

  • mkusb 24.0.1
  • mkusb 24.0.2,3

[SIZE=3]Improvement in program package mkusb version 24.0.1[/SIZE]

This upgrade of dus-iso2usb removes the menuentry for persistence, when a live-only system is created. (Nothing is modified when a persistent live system is created.)

[SIZE=3]Improvement in program package mkusb version 24.0.2[/SIZE]

This is a minor upgrade that takes care of a modification in the new version of zenity: increased height of window to keep the whole menu list within the window (without scrolling).

[SIZE=3]Improvement in program package mkusb version 24.0.3[/SIZE]

This is a minor upgrade that takes care of a modification in the new version of zenity: increased height and width [of some windows] to keep the whole menu list within the window (without scrolling).

An info text is added: 'dus-persistent ... problem with secure boot' because of problems in computers with newer versions of 'secure boot'. Please notice that dus-iso2usb and mkusb-plug can make persistent live systems that work also with secure boot in such computers.

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 24.0.1 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1256

I've been busy elsewhere, but sudodus this version shows how nice it has matured.

 mkusb-dus --version
 mkusb-dus - Do USB Stuff 
mkusb-dus needs superuser permissions (sudo) for some tasks,
in order to prepare and write to the target, a block device.
 dus 24.0.1 
live system or temporary superuser permissions
--version is neither an iso file nor an img.{gz,xz} file
 Press Enter to finish mkusb-dus 

Also this is on Arch, nice to have choices. ;)

#1257

@1fallen,

mkusb and its components do not use [FONT=Courier New]--options[/FONT], only the simple ones, like [FONT=Courier New]-v[/FONT] and [FONT=Courier New]-h[/FONT].

Do you think that I should add [FONT=Courier New]--version[/FONT] and [FONT=Courier New]--help[/FONT]?

[hr][/hr]


$ mkusb -v
mkusb-dus:  dus 24.0.1
mkusb-plug: mkusb-plug 2.8.7
mkusb-nox:  mkusb-nox 23.1.2
mkusb-bas:  mkusb version 7.4.3
mkusb-11:   mkusb 11.2.2
$ mkusb -h
---------------------------------------------------------------------
Usage: mkusb [input-file]      # optional parameter
---------------------------------------------------------------------
d:  dus , guidus, mkusb-dus    - Classic, easy to use
p: Plug,   mkusb-plug          - New, easy to use
n: NoX,    sudo mkusb-nox      - original text mode
b: Bas,    sudo mkusb-bas      - basic text mode for old/basic linux
e: Eleven, sudo -H mkusb-11    - Old user interface
q: Quit
---------------------------------------------------------------------
Select version of mkusb (d/p/n/b/e/q) d
dus 24.0.1
Usage:
---- Make USB or memory card install drive from ISO or image file ---
dus
dus file.iso
dus "quote file name (1) with special characters.iso"
dus file.img
dus file.img.gz
dus file.img.xz
dus file.tar       # if an mkusb tarfile for Windows
---- Clone a device (typically a CD drive or USB drive) -------------
dus /dev/sr0       # example of CD drive
---- Wipe or restore a USB drive or memory card ---------------------
dus
---- Options --------------------------------------------------------
dus -d [file.iso]  # dialog (text mode menus)
dus -t [file.iso]  # plain text mode interface
dus -h             # usage text
dus -v             # version
#1258

Not for me....I'm good as is. :)

I just needed to see the version from the tarball when installing.

After thought, it might help others though. So it's your call sudodus.

Thanks for your continued contributions....

#1259

Can I use mkusb to format an external 1Tb SSD and then make it a Kubuntu boot disk ? I have used mkusb to do this to a usb, and in essence the SSD, being connected by a usb cable is _nearly_ the same device.

The SSD is new, so only 3 files on it, I think there is a quick wipe option ? Will the process take a long time, as it is 1 Tb ??

#1260

@oygle,

If 'format' means create a partition *and* a suitable file system for Kubuntu, I'd say no, not [FONT=Courier New]mkusb[/FONT]. [SIZE=3]

I would use [FONT=Courier New]gparted[/FONT] for that task, and create a partition with an ext4 file system.[/SIZE]

[hr][/hr] [FONT=Courier New]mkusb-dus[/FONT] can be used to wipe a drive (overwrite it with zeros), and to create a partition with a basic FAT32 file system, which used to be the main file system in USB pendrives. Today, in big USB drives, > 32 GB, and with big files, > 4GB, you may prefer to use some other file system, NTFS, exFAT, for portability to Windows, or ext4 if used only within Linux. See also this link.

([FONT=Courier New]mkusb-plug[/FONT] can create live drives with NTFS or exFAT or ext4, but only 'behind' the cloned iso9660 file system.)

[hr][/hr] Edit: I'm assuming here that you want to *install* Kubuntu into the USB drive.

If you want to create a live or persistent live drive, you need not format it, but can let [FONT=Courier New]mkusb[/FONT] create the live system directly without pre-formatting.

#1261

oygle said: Can I use mkusb to format an external 1Tb SSD and then make it a Kubuntu boot disk ? I have used mkusb to do this to a usb, and in essence the SSD, being connected by a usb cable is _nearly_ the same device.

The SSD is new, so only 3 files on it, I think there is a quick wipe option ? Will the process take a long time, as it is 1 Tb ??

You don't say if you want to use the ssd as a boot install drive for installing to other devices or if you want an installed version of Kubuntu on this drive.

Until we know it's uses we cannot properly advise you.

Cheers Tony

#1262

@sudodus, thanks for your reply.

sudodus said: If 'format' means create a partition *and* a suitable file system for Kubuntu, I'd say no, not [FONT=Courier New]mkusb[/FONT]. [SIZE=3]

I would use [FONT=Courier New]gparted[/FONT] for that task, and create a partition with an ext4 file system.[/SIZE]

Ok, so I do the gparted first, then mkusb to put Kubuntu OS on it. I use EXT4 mostly, the SSD is formatted to msdos I think, so it definitely needs formatting first.

sudodus said:

See also this link.

I wanted to make it EXT4, so I have to assume any files greater than 4Gb are okay. Is an SSD still considered a "usb-flash-drive" ?? It has a usb connection.

sudodus said: Edit: I'm assuming here that you want to *install* Kubuntu into the USB drive.

Yes

sudodus said: If you want to create a live or persistent live drive, you need not format it, but can let [FONT=Courier New]mkusb[/FONT] create the live system directly without pre-formatting.

As I think the HDD on this (old) Dell laptop is showing signs of possible fail ( see https://ubuntuforums.org/showthread.php?t=2497062&goto=newpost ), my thinking was to put Kubuntu on the SSD and run it from a Lenovo laptop, as an external boot. The Lenovo Windows10 on it and I'd prefer not to format, besides the SSD on that is not large enough.

The old Dell has had display problems for years, so the plan is to use the external SSD on another computer. I hope this makes sense.

vidtek said: You don't say if you want to use the ssd as a boot install drive for installing to other devices or if you want an installed version of Kubuntu on this drive.

An installed version of Kubuntu on the SSD. Do it all from the Dell. Then use the SSD in a Lenovo as a boot option/device, as the lenovo has Win10 on it. I use Kubuntu 99% of the time, so the new SSD will be on at least 10 to 12 hours/day. Not a lot of file 'work', just 'on'.

#1263

@oygle,

The best way is to use 2 USB drives,

  1. A USB pendrive, and you use [FONT=Courier New]mkusb[/FONT] to put a live Kubuntu system there.
  1. The target USB-SSD, and you can use [FONT=Courier New]gparted[/FONT] to format it. You need not (should not) use mkusb on this drive.

[HR][/HR] I don't know which version of Kubuntu you intend to install.

A. If 24.04 LTS, I think there is the installer Calamares. In that case boot into the USB pendrive and use the installer to install Kubuntu into it.

B. If 22.04 LTS, I think there is the installer Ubiquity, and if you run in UEFI mode, it will put the EFI system partition onto the internal drive of the computer, unless you disable it (for example unplug or remove the internal drive from the computer during the installation process). So this can cause problems unless you get everything right.

An alternative is to install by extraction/cloning Ubuntu Server from a compressed image of an already installed system, and then boot in the target computer (the Lenovo) into Ubuntu Server and install the meta package [FONT=Courier New]kubuntu-desktop[/FONT]. You may have to turn off secure boot. After reboot you will have Kubuntu. See more details about this alternative. Please read the whole thread before starting to use this method.

#1264

Thanks @sudodus

sudodus said: The best way is to use 2 USB drives,

  1. A USB pendrive, and you use [FONT=Courier New]mkusb[/FONT] to put a live Kubuntu system there.
  1. The target USB-SSD, and you can use [FONT=Courier New]gparted[/FONT] to format it. You need not (should not) use mkusb on this drive.

Great, thanks. I can do all that from the Dell/Kubuntu.

sudodus said:

I don't know which version of Kubuntu you intend to install.

I hadn't given it much thought, as yet. But now realising, as I have no wish to modify BIOS in either the Dell or the lenovo, I had better see if the Lenovo has UEFI or not. See attached dump of the Dell partitiions now.

sudodus said:

A. If 24.04 LTS, I think there is the installer Calamares. In that case boot into the USB pendrive and use the installer to install Kubuntu into it.

B. If 22.04 LTS, I think there is the installer Ubiquity, and if you run in UEFI mode, it will put the EFI system partition onto the internal drive of the computer, unless you disable it (for example unplug or remove the internal drive from the computer during the installation process). So this can cause problems unless you get everything right.

I'm using 22.04 now and it doesn't seem like 24.04 is stable yet, as it's only in the nightly builds. I was going to do that only from the Dell/Kubuntu, so should be safe, right ?

sudodus said: An alternative is to install by extraction/cloning Ubuntu Server from a compressed image of an already installed system, and then boot in the target computer (the Lenovo) into Ubuntu Server and install the meta package [FONT=Courier New]kubuntu-desktop[/FONT]. You may have to turn off secure boot. After reboot you will have Kubuntu. See more details about this alternative. Please read the whole thread before starting to use this method.

Hmm, .. maybe a bit too challenging for me at present. :)

#1265

@oygle,

When booted into the computers from the live Kubuntu USB drive, you can run the following command in order to find the boot mode,


test -d /sys/firmware/efi && echo efi || echo bios

The version 24.04 LTS will probably be released within this month, so maybe you can wait a while. But even after the release, it will not be fully debugged. If you want a smooth ride, you should stay with 22.04 LTS until the first point release, 24.04.1 LTS (late July or early August).

#1266

Thanks @sudodus, I tried that command on the Dell/Kubuntu

$ test -d /sys/firmware/efi && echo efi || echo bios

efi

sudodus said: The version 24.04 LTS will probably be released within this month, so maybe you can wait a while. But even after the release, it will not be fully debugged. If you want a smooth ride, you should stay with 22.04 LTS until the first point release, 24.04.1 LTS (late July or early August).

Okay, a smooth ride I will take. :)

#1267

sudodus said: @oygle,

The best way is to use 2 USB drives,

  1. A USB pendrive, and you use [FONT=Courier New]mkusb[/FONT] to put a live Kubuntu system there.
  1. The target USB-SSD, and you can use [FONT=Courier New]gparted[/FONT] to format it. You need not (should not) use mkusb on this drive.

Step 1 was easy. Now, with step 2, does it matter if I connect the external SSD to the Dell/Kubuntu or the Lenovo/Win10 when installing from the USB pendrive ??

Do the BIOS settings of the 'host' computer matter ? In terms of installing ? I would assume as it is the Lenovo/Win10 computer that I will be having the external SSD connected all the time, it makes no sense doing it from the Dell, is that correct ? Plus the Dell is failing more now, the video issues are worse.

#1268

oygle said: Step 1 was easy. Now, with step 2, does it matter if I connect the external SSD to the Dell/Kubuntu or the Lenovo/Win10 when installing from the USB pendrive ??

Do the BIOS settings of the 'host' computer matter ? In terms of installing ? I would assume as it is the Lenovo/Win10 computer that I will be having the external SSD connected all the time, it makes no sense doing it from the Dell, is that correct ? Plus the Dell is failing more now, the video issues are worse.

Yes, particularly when there are graphics chips/cards that need different drivers and one of them needs a proprietary driver, and if they boot in different modes (UEFI mode or BIOS mode alias CSM alias legacy mode).

But you must be aware that installing Ubuntu 22.04.x LTS with the installer Ubiquity in UEFI mode will touch the EFI system partition on the internal drive, which means that the external SSD will not have a complete boot system. This is good, if you intend to use the SSD only on that computer.

But if you want a portable system, you had better unplug or otherwise disable the internal drive during the installation (and later on boot into the SSD via a temporary boot menu started via some hotkey). Or create the portable system via the alternative method via a compressed image of Ubuntu Server.

#1269

sudodus said: Yes, particularly when there are graphics chips/cards that need different drivers and one of them needs a proprietary driver, and if they boot in different modes (UEFI mode or BIOS mode alias CSM alias legacy mode).

Okay thanks @sudodus

sudodus said: But you must be aware that installing Ubuntu 22.04.x LTS with the installer Ubiquity in UEFI mode will touch the EFI system partition on the internal drive, which means that the external SSD will not have a complete boot system. This is good, if you intend to use the SSD only on that computer.

I had intended to use 23.10, and assume it is going to use Ubiquity as the installer in UEFI mode. By "*touching the EFI system on the internal drive*", I hope that excludes any Windows 10 boot issues. Just checked the partitions on that (an internal SSD) and it has a 100Mb EFI system partition, showing as 100% free space. I don't need a portable system, the external SSD will be connected all the time.

#1270

I *think* Ubuntu Desktop 23.10 is using the new installer that is not acting like Ubiquity, but 24.04 LTS is released now, and will get much more attention concerning debugging and polishing. I would not install 23.10 now, unless there would be a very specific reason because it will be supported only 3 months from now (a total of 9 months from the release date October 2023).

The only alternatives for me would be 22.04.4 LTS (for a smooth ride) or 24.04 LTS (to get newer software).

#1271

Thanks @sudodus

sudodus said: The only alternatives for me would be 22.04.4 LTS (for a smooth ride) or 24.04 LTS (to get newer software).

It has to be done in the next few days, so as you say 22.04.4 LTS is a smooth ride. If 24.04 LTS is only just released, I'd prefer to wait a few months, less bugs. Even though 23.10 has only 3 months of support, it may have the new installer, and in 3 months time, I can do a fresh install of 24.04 LTS

Edit: Whilst I couldn't find anything to do with Kubuntu and Calamares, Lubuntu makes it clear at https://lubuntu.me/mantic-released/

System Installer

We are once again utilizing Calamares 3.3 Alpha 2 in Lubuntu 23.10, as it has proven to be highly reliable since its initial use in Lubuntu 22.10.

Another edit: Found this article, it explains it is only Lubuntu up until now that has Calamares, and Kubuntu will also have that installer in 24.04 - https://9to5linux.com/kubuntu-24-04-lts-is-switching-to-the-calamares-installer-by-default

#1272

The Kubuntu 23.10 install 'sort of' went okay, but .... https://ubuntuforums.org/showthread.php?t=2497207

#1273

Now the mkusb PPAs are extended to Oracular, so you can use mkusb during testing the current development of Ubuntu Desktop, Server and the community flavours of Ubuntu, and also test that mkusb works correctly.

#1274

[FONT=&quot]If I make a [/FONT][FONT=&quot]live USB with persistence (Ubuntu 22.04) with mkusb-plug on a [/FONT][FONT=&quot]BIOS PC (not UEFI mode capable PC) will it work on another computer UEFI and BIOS capable?[/FONT] [FONT=&quot] [/FONT] [FONT=&quot]If I understand well, I could use compressed image of Ubuntu Server on a BIOS PC to extract and clone it to USB/external SSD. Then this SSD will be portable and could be used on any PC?[/FONT] [FONT=&quot]Is there a problem with such a system, I think I read that it is not stable after performing updates? [/FONT][FONT=&quot][/FONT] Thank you

#1275

jelena011 said: [FONT=&quot]If I make a [/FONT][FONT=&quot]live USB with persistence (Ubuntu 22.04) with mkusb-plug on a [/FONT][FONT=&quot]BIOS PC (not UEFI mode capable PC) will it work on another computer UEFI and BIOS capable?[/FONT]

Yes

[FONT=&quot]If I understand well, I could use compressed image of Ubuntu Server on a BIOS PC to extract and clone it to USB/external SSD. Then this SSD will be portable and could be used on any PC?[/FONT]

Yes

[FONT=&quot]Is there a problem with such a system, I think I read that it is not stable after performing updates? [/FONT][FONT=&quot][/FONT] Thank you An installed system created from a compressed image of Ubuntu Server will work both in BIOS mode and UEFI mode the first time you run it, but after updating it might (or might not) 'narrow down' to the hardware and boot mode that it is running in.

#1276

Thank you very much for your prompt response!

#1277

[SIZE=4]mkusb version 24.1.0, 24.1.1[/SIZE]

[TABLE="class: cms_table"][tr] [td="bgcolor: #CCFF99"]

. mkusb-plug: .. p_zentest: added zver (storing zenity main version) .. get_action: using zver to add window height for version >= 4

. t_plug: 'works also with secure boot' when Ubuntu flavour [/td][/tr][/table]

  • mkusb 24.1.0
  • mkusb 24.1.1

[SIZE=3]Improvement in program package mkusb version 24.1.0[/SIZE]

Modications in mkusb-plug: increased height of window to keep the whole menu list within the window (without scrolling) for new version of zenity ('catching up' with recent updates in dus)

[SIZE=3]Improvement in program package mkusb version 24.1.1[/SIZE]

Modications in dus: t_plug: added test to make a difference between Ubuntu flavours and other distros or respins, where we can expect Ubuntu flavours to work with secure boot in newer computers.

[hr][/hr] Unstable: You get/update this new version of mkusb from the unstable PPA via the following commands

sudo add-apt-repository universe     # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**unstable**
sudo apt update
sudo apt install mkusb           # to install
# sudo apt full-upgrade          # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install mkusb guidus dus mkusb-common  # to upgrade all mkusb basic components including dus

sudo apt install usb-pack-efi    # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Alternative way to get mkusb: There are tarballs at

[hr][/hr] Stable: mkusb version 24.1.1 is in the stable PPA. The policy is to test mkusb for a long time and in several environments before it is uploaded to the stable PPA (unless there are minor tweaks or bug-fixes).

You get/update this version via the following commands

sudo add-apt-repository universe      # this line only for standard Ubuntu

sudo add-apt-repository ppa:mkusb/**ppa**
sudo apt update
sudo apt install mkusb            # to install
# sudo apt full-upgrade           # upgrade to current version (with all other upgrades), only for installed systems

sudo apt install usb-pack-efi     # for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files

You get only the version dus (alone or with guidus) via one of the following commands (without the whole set of mkusb tools). [FONT=Courier New]dus[/FONT] and [FONT=Courier New]mkusb-nox[/FONT] are useful for systems without a graphic environment, for example Ubuntu Server.

sudo apt install dus
sudo apt install guidus
sudo apt install mkusb-nox

You get only the version mkusb-plug via [the update command and] the following command,

sudo apt update
sudo apt install mkusb-plug

Usually there is drive space enough to install all the following mkusb packages explicitly:


sudo apt update
sudo apt install mkusb guidus mkusb-plug usb-pack-efi 

Please notice that if you have already installed mkusb-plug or dus/guidus from a tarball, you had better remove that version when you install via PPA. The advantage with the PPA version is that it gets updated/upgraded automatically along with other program packages that are installed from the Ubuntu repositories.

#1278

Wanting to create a bootable usb with DBAN on it. Having problems with booting to usb and it seems the usb won't show on the boot list if the usb is not formatted properly. This is what I did

sudo add-apt-repository ppa:mkusb/ppa
sudo apt-get update
sudo apt-get install mkusb mkusb-nox usb-pack-efi

then ``` mkusb dban-2.3.0_i586.iso


I used these options, as this is how I use **mkusb** to create a bootble Kubuntu usb drive

> 
  take option 'p' , then option 'c'  (clone)

                At "Do you expect the drive to contain filesystems other than VFAT and ISO9660 ? , select "D"  (I don't know)

                At "Do you expect the drive to contain an ISO9660 filesystem ? , select "d"  (I don't know)



Kubuntu 23.10

Any ideas please ?
#1279

@oygle,

In order to use DBAN on a USB drive, you need to treat [FONT=Courier New]dban-2.2.7_i586.iso[/FONT] with [FONT=Courier New]isohybrid[/FONT] according to my answer at the following link,

How can I permanently erase data on INTERNAL HDD?


isohybrid dban-2.2.7_i586.iso

After that it will be possible to make a bootable drive by cloning (using mkusb).

[HR][/HR] In order to install isohybrid, See this link.

#1280

@sudodus, Thank you so much, that worked fine, was able to boot to usb and DBAN is running now. :)

I downloaded 2.3.0 ; I see reference that you have used 2.2.7 as it worked for you on several computers.

You write great tutorials.

#1281

Interesting, I went to use the DBAN usb again today and it failed to boot. Then realised after the DBAN "wipe" it also must have wiped the usb. Loaded it on another computer, and there was nothing on it. Just a FYI :)

#1282

@sudodus

After the move to Ubuntu Discourse next month, how will we access your *mkusb* tutorials

#1283

@him610,

I intend to create a corresponding thread at Ubuntu Discourse in order to continue the mkusb tutorial.