Sunday, 1 April 2018

Latest improvements to ''

Ever wondered whether you are running the latest version of ''? I've now added a '--check' option that does exactly that. Starting with version 8.1.4 when you check and you are on the latest version you will get a message similar to:

linuxium@LINUXIUMONE:~$ --check
/usr/local/bin/ Version: 8.1.4 is the latest version.

otherwise you will get a message similar to:

linuxium@LINUXIUMONE:~$ ./ --check
./ Version: 8.1.3 should be upgraded as 8.1.4 is the latest version.

indicating that you should download the latest version from ''.

I've also added some additional checks to prevent common issues that have previously been reported.

Firstly you cannot respin an ISO on an OS that doesn't support 'systemd' if you want to use either the '--apollo' or the '-b Linuxium' options. Also you cannot respin an ISO if it doesn't support 'systemd' when using the '--atom', '--apollo' or '-b Linuxium' options:

linuxium@LINUXIUMONE:~$ -i ubuntu-14.04.5-desktop-amd64.iso --atom
Extracting ISO ...
Parallel unsquashfs: Using 4 processors
166333 inodes (175651 blocks) to write

[===========================================================/] 175651/175651 100%

created 105294 files
created 16104 directories
created 60921 symlinks
created 82 devices
created 0 fifos
/usr/local/bin/ The '--atom' option is only compatible with an ISO that uses 'systemd'.

Secondly you cannot respin an ISO that is EOL (End Of Life):

linuxium@LINUXIUMONE:~$ -i ubuntu-17.04-desktop-amd64.iso --atom
Extracting ISO ...
/usr/local/bin/ ISO is EOL.

Finally you cannot run the script on a 32-bit OS:

linuxium@LINUXIUMONE:~$ -i ubuntu-17.10.1-desktop-amd64.iso --apollo
/usr/local/bin/ This script can only be run on a 64-bit (amd64 or x86_64) OS.

Please donate if you find the script useful using the following link


  1. isorespin is telling me that lubuntu 19.04 is EOL. How do I change that?

    1. See - basically as 19.04 is EOL you should try respinning 19.10 or use an LTS release such as 18.04.3.

  2. my atom stick won't work with 19.10, can i trick this into still using 19.04?

    1. What is the problem with 19.10?

    2. Thought i would resping 19.04 and try it.

    3. Try respinning 19.10 and also include the '--upgrade' option and see if it makes any difference. You could also try modifying the boot parameters and include 'nomodeset' when booting. What device is it (exactly)?

    4. I am working with an Intel Compute Stick STCK1A8LFC, it came with ubuntu 14.04 on it. Will try the options you mention tomorrow.

    5. I've tested respinning Lubuntu 19.10 just with the '--atom' option on my Intel Compute Stick STCK1A8LFC and can confirm everything works (including wifi and audio). Try ' -i lubuntu-19.10-desktop-amd64.iso --atom' and write the resultant ISO to USB 'sudo dd if=linuxium-atom-lubuntu-19.10-desktop-amd64.iso of=/dev/sdX bs=4M' (where X is the relevant drive letter for your USB) and then boot by powering on followed by 'mashing' the F10 key and select 'USB'.

  3. No go, the 4gb drive is just not enough space. When I do actually get it to boot and run something - it is but a few minutes until the drive is full and the stick has crashed.
    So I tried something different. I put a 16gb sdxc card in, used the internal 4gb for /boot and swap space - used the 16gb card for / and it has been running lubuntu for a week straight now.

  4. I cant run isorespin with ubuntu minal version or ubuntu server. Why ? Thanks

    1. My '' script was never designed for server ISOs as it was specifically for respinning desktop Ubuntu flavoured ISOs. However see my latest post ( on how to respin a desktop ISO as a server ISO and then how to install the server ISO.

  5. Hi i'm trying to respin ubuntu 16.04 because touchscreen of my tablet doesn't work after (problem in goodix.c driver and i dont know how to change kernel ... yet).
    I manage to install ubuntu 20.04 with your version directly download on drive but i can't make 16.04 iso.
    isorespin.h tell me "The '--atom' option is only compatible with an ISO that uses 'systemd'"
    I dont understand why and how to make the iso.
    Can you help me please ?
    Thank you.

    1. Ubuntu 16.04 uses 'systemd' so are you sure you are trying to respin a 16.04 ISO?

      Also I have an 'atom' respun Ubuntu 16.04.6 ISO available from '' if it helps.

    2. Thank you for your anwer, i download the iso directly from ubuntu web site (ubuntu-16.04.4-desktop-amd64.iso) and i apply isorespin from ubuntu live session.
      If y try respin whithout --atom command, processed ended with several error but with an created iso.

      But thank you for the link ! i'm going to try.

    3. Use the option '--check' to make sure you are on the latest version (8.6.4) of ''. Can you explain more about how you are performing the respin (e.g. what OS and version you are using, what is the exact command, use 'pastebinit' to post a link to 'isorespin.log' output etc.)?

    4. Hi, i have the latest version of isorespin,
      i download ubuntu version 16.04.x 14.04.x

      isorespin -i ubuntu-16.04.7-desktop-amd64.iso --atom
      the job started but near 24% it stop with the previous message.
      I used ubuntu 20.04 live session launch from usb stick.
      I dont have log but i can do it again.

    5. I had missed that Canonical had released Ubuntu 16.04.7 so I've updated my ISOs ... see '' where you can download an 'atom' respun Ubuntu 16.04.7 ISO.

      Regarding your issue, do you get the same error message if you respin on an installed Ubuntu rather than using a liveUSB?

    6. Hi, it works with an installed ubuntu 20.04 without any error.
      now i have to solve boot issues with my tablet... install ok but uefi boot failed to install.
      I can start ubuntu but i have to write some command line in the uefi boot to start manualy
      (#linux (hdx,gptx)/vmlinuz root=/dev/mmcblk0p2
      #initrd (hdx,gptx)/initrd.img

      and upgrade-grub doesn't fix the issues.

      Thank you

    7. When you've successfully booted Ubuntu, run 'efibootmgr -v' and look at the entry for ubuntu. You will see the disk, partition and directory path that GRUB uses. Then run 'blkid' to match the returned UUIDs to the physical disk and partition. Now run 'df' to check that this disk and partition is mounted as '/boot/efi'. Then use the path from the first command and append to '/boot/efi' replacing the '.efi' file with 'grub.cfg' so you get something like '/boot/efi/EFI/ubuntu/grub.cfg'. Finally look at this file e.g. 'cat /boot/efi/EFI/ubuntu/grub.cfg' and check that the UUID and drive,partition match your actual root partition. This will be the drive,partition for the GRUB configuration file which is defined by the 'prefix' and 'configfile' definition e.g. '/boot/grub/grub.cfg'. Chances are that 'update-grub' is updating a GRUB configuration file which is different to the one actually used by GRUB when booting. Working backwards as I've described should show you what files are being used at each stage of the boot and which of them needs to be 'corrected' so that your device boots correctly.

    8. hi thank you,
      i tryied but efibootmgr show that no hdd boot entry exist,
      neither grub.cfg
      so i decided to reinstall and no all is working fine !
      thank you.