Page 31 of 126 FirstFirst ... 2129303132334181 ... LastLast
Results 301 to 310 of 1258

Thread: Howto make USB boot drives

  1. #301
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    Quote Originally Posted by ventrical View Post
    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,

    Code:
    sudo -H mkusb
    the corresponding output goes into the terminal window, it becomes 'the mkusb console', and there will be no ~/mkusb.log file.

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

    Re: Howto make USB boot drives

    Quote Originally Posted by ventrical View Post
    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'.
    Last edited by sudodus; November 30th, 2015 at 08:37 AM.

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

    Re: Howto make USB boot drives

    Quote Originally Posted by ventrical View Post
    Very well..

    Code:
    [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
                     ├─sdb1                                                 512B
                     ├─sdb2                                                   1M
                     ├─sdb3 vfat    xenial64                                122M
                     ├─sdb4 iso9660 Ubuntu-MATE 16.04 LTS amd64             1.2G
                     └─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
                     ├─sdb1                                                 512B
                     ├─sdb2                                                   1M
                     ├─sdb3 vfat    xenial64                                122M
                     ├─sdb4 iso9660 Ubuntu-MATE 16.04 LTS amd64             1.2G
                     └─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.

  4. #304
    Join Date
    Sep 2010
    Beans
    9,205
    Distro
    Ubuntu Budgie 17.10 Artful Aardvark

    Re: Howto make USB boot drives

    Quote Originally Posted by sudodus View Post

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

  5. #305
    Join Date
    Sep 2010
    Beans
    9,205
    Distro
    Ubuntu Budgie 17.10 Artful Aardvark

    Re: Howto make USB boot drives

    Just checked another install (trusty) and the mkusb.log is not there either.

  6. #306
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    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.


    2. 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.

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

    Re: Howto make USB boot drives

    Quote Originally Posted by ventrical View Post
    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'.


    2. 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.
    Last edited by sudodus; November 30th, 2015 at 10:39 AM.

  8. #308
    Join Date
    Sep 2010
    Beans
    9,205
    Distro
    Ubuntu Budgie 17.10 Artful Aardvark

    Re: Howto make USB boot drives

    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.

    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.
    Of course, as you suggested, just use:

    Code:
    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 pa.
    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..

  9. #309
    Join Date
    Sep 2010
    Beans
    9,205
    Distro
    Ubuntu Budgie 17.10 Artful Aardvark

    Re: Howto make USB boot drives

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

  10. #310
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Howto make USB boot drives

    Quote Originally Posted by ventrical View Post
    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.
    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.
    Of course, as you suggested, just use:

    Code:
    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 pa.
    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

    Code:
    sudo apt-get remove mkusb
    or if you have also mkusb-nox

    Code:
    sudo apt-get remove mkusb mkusb-nox
    but I think files created by mkusb when you run it will remain, for example ~/mkusb.log.



    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

    Code:
    sudo -H mkusb file.iso p  # to make a persistent live drive from 'file.iso'

Page 31 of 126 FirstFirst ... 2129303132334181 ... LastLast

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
  •