Page 82 of 82 FirstFirst ... 3272808182
Results 811 to 820 of 820

Thread: Howto make USB boot drives

  1. #811
    Join Date
    Dec 2009
    Beans
    6

    Re: Howto make USB boot drives

    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?

  2. #812
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    @khbkhb,

    0. Something goes very wrong when you get

    Code:
    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)?

    2. Please describe with more details your custom iso file.

    3. I run dus directly without sudo as

    Code:
    dus custom.iso
    Please try if that works better.



    4. Please run the following commands (with your USB pendrive, the SanDisk_Cruzer_Glide, connected).

    Code:
    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)

    [code]
    output
    [/code]

    to get output like this

    Code:
    output


    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.

    Code:
    tester@tester-desktop:/mnt/home/tester/Downloads$ dus ubuntu-18.10-desktop-amd64.iso 
     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
                     ├─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
    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
                     ├─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
    /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$ lsb_release -a
    No LSB modules are available.
    Distributor ID:	Ubuntu
    Description:	Ubuntu 18.10
    Release:	18.10
    Codename:	cosmic
    
    tester@tester-desktop:/mnt/home/tester/Downloads$ uname -a
    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$
    Last edited by sudodus; March 2nd, 2019 at 03:21 PM. Reason: mkusb works for me (today in Ubuntu 18.10 that is up to date)

  3. #813
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    Problem with the 4 GiB max file size in FAT32

    Several (but not all) Windows 10 iso files released in October 2018,

    Code:
    Win10_1809Oct_Language_x64.iso
    contain a version of the file install.wim with size > 4 GiB. It means that mkusb's method does not work because the FAT32 file system cannot manage it. Until this is fixed in mkusb, you can

    - use woeusb according to this link. This works in both BIOS and UEFI mode but not with secure boot.

    - do it yourself with detailed help at help.ubuntu.com/community/Installation/iso2usb/diy/windows-installer-for-big-files. This works in both BIOS and UEFI mode also with secure boot.

  4. #814
    Join Date
    Apr 2007
    Location
    Brussels, Belgium
    Beans
    262
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Howto make USB boot drives

    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-bootabl...om-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.

  5. #815
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    @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).



    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.

  6. #816
    Join Date
    Apr 2007
    Location
    Brussels, Belgium
    Beans
    262
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Howto make USB boot drives

    Quote Originally Posted by sudodus View Post
    @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...

  7. #817
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    Quote Originally Posted by jdeca57 View Post
    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)!

  8. #818
    Join Date
    Mar 2017
    Location
    Gubertino
    Beans
    1,006
    Distro
    Xubuntu 18.04 Bionic Beaver

    Re: Howto make USB boot drives

    Quote Originally Posted by sudodus View Post
    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.
    Attached Images Attached Images
    Last edited by guber2; March 6th, 2019 at 06:48 AM.

  9. #819
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    mkusb version 12.3.2 for version 19.10, Eoan Eanimal

    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.



    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.

    Code:
    sudo add-apt-repository universe  # this line only for standard Ubuntu
    Code:
    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

  10. #820
    Join Date
    May 2019
    Beans
    2

    Re: Howto make USB boot drives

    Thank you very much!

Page 82 of 82 FirstFirst ... 3272808182

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •