3 ms·

Took a looksy, doesn't seem to be doing the job :(. It's a Windows tool, I'm running Ubuntus so that's not making it more reliable I guess.. Did peak into the

Took a looksy, doesn't seem to be doing the job :(. It's a Windows tool, I'm running Ubuntus so that's not making it more reliable I guess.. Did peak into the source-code of the UEFI-beta version. Seems they are also using grub2 the way I am generally. (basically the grub-install --target=x86_64-efi type /boot & /EFI folders). That's the part that _is_ working for me. It seems that my casper/filesystem.squashfs is missing a few mystery 'things'. You have any cluess regarding that?

Senji 10y ago
It just works for me. As far as I know it uses recompiled linux tools to do its job on windows. Yumi used to have a linux version, but it seems to be under rewrite. You could try using wine I guess?
drvdevd 10y ago
Ok so what I'm reading is that: 1) you can get EFI to load grub but 2) actually loading the live system image isn't working So given those assumptions my next question is: Is the kernel and initramfs loading? If you're not sure try: * holding shift to display the grub boot menu on power up * hitting 'e' to edit the default boot menu * removing 'splash' from the kernel command line so you can observe boot messages * continue booting by hitting ctrl+x See if you can glean some more info from that
- drvdevd 10y ago
  also, if you can pastebin your boot/grub/grub.cfg file that'd be helpful too
  - Bluescreens 10y ago
    menuentry '[loopback]ubuntu-14.04.1-desktop-amd64' { set isofile='/ubuntu-14.04.1-desktop-amd64.iso' loopback loop (hd0,2)$isofile linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=$isofile locale=en_US.UTF-8 initrd (loop)/casper/initrd.lz } This works.
    - drvdevd 10y ago
      Ok so one immediate point that I notice here is that if you look closely at this grub configuration, you'll see that the EFI boot Kernel and initrd are not loaded from an EFI partition, but rather taken from the ISO itself: > loopback loop (hd0,2)$isofile > linux (loop)/casper/vmlinuz.efi Whereas above, for Ubuntu 16.04, you appear to be trying to use a separate fat32 EFI partition to load vmlinuz.efi So, just to test, you should try to do what Ubuntu 14.04 is doing, but keep your EFI parition to load grubx64.efi. Make sense? So your partiton layout on this USB stick will be as follows: Partlabel: gpt (hd0,gpt1): FAT32 (type: EFI system) - has path/to/grubx64.efi (hd0,gpt2): ext4 (type: Linux) - has boot/grub/grub.cfg - has ubuntu-16.04-WHATEVER-REALNAME-HERE.iso ---- And the grub.cfg now has a new menu entry as follows: menuentry '[loopback]ubuntu-16.04-desktop' { set isofile='/ubuntu-16.04-WHATEVER-REALNAME-HERE.iso' loopback loop (hd0,2)$isofile linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=$isofile locale=en_US.UTF-8 initrd (loop)/casper/initrd.lz } Let me know if that solution works for you? [Edit] I think the issue with all of this here is the other scripts/parts of Casper that get loaded normally using the ISO. Its annoying, but casper is the ubuntu way. There are better ways to boot a live system off EFI but this would be the quickest path
      - drvdevd 10y ago
        [Edit 2] where you put grub/grub.cfg in the above partition layout is also up to you. It could reside on the EFI parition. Its all about how you lay it out in the host system when putting this disk together and then how you run grub-install
        deleted 10y ago
        [deleted]
        deleted 10y ago
        [deleted]
        deleted 10y ago
        [deleted]
        Bluescreens 10y ago
- deleted 10y ago
  [deleted]
- deleted 10y ago
  [deleted]
- Bluescreens 10y ago
  Correct. Surprisingly all the grub2 parts seem to be in working order. The issue seems to lie somewhere with the vmlinuz.efi/initrd.lz... I can follow the grub entry to my custom.iso, but the system hangs with "error: no suitable video mode found. booting in blind mode" if I use the vmlinuz-version-generic and/or vmlinuz-version-generic.efi.signed from the host OS. (the regular ubuntu-16.iso also displays the same message, but then proceeds to but correctly. So that shouldn't be the issue here). But it does load when I copy over the /EFI and casper/{vmlinuz.efi,initrd.lz}. However it again eventually stalls with: BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) losetup: could not find any free loop devicet go on FAT32 partitions. [I somehow can´t seem to get the formatting to stick with this next part, sorry :S] After: Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done. Begin: Running /scripts/nfs-premount ... done. Begin: Running /scripts/casper-premount ... [ 10.177576] random: nonblocing pool is initialized [10.473862] SGI XFS with ACLs, security attributes, realtime, no debug enabled [10.479729] JFS: nTxBlock = 8192, nTxLock = 65536 [10.627678] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [10.776705] FAT-fs (sdb1): error, fat_get_cluster: invalid cluster chain (i_pos 1) [10.776720] FAT-fs (sdb1): Filesystem has been set read-only [11.029557] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null) done. Begin: ...waiting for devs... ... done. touch: /dev/.initramfs/lupin-waited-for-devs: No such file or directory stdin: Not a typewriter mount: mounting /dev/sdb1 on /isodevice failed: Input/output error warning: Cannot mount /dev/sdb1 on /isodevice stdin: Not a typewriter [11.689807] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fschk. [11.740150] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null) done. ioctl: LOOP_CLR_FD: No such device or adress [12.524128] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address stdin: Not a typewriter [13.247442] FAT-fs (loop0): error, fat_get_cluster: invalid cluster chain (i_pos 1) [13.870988] EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null) ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address stdin: Not a typewriter ioctl: LOOP_CLR_FD: No such device or address unable to open '/dev/sdc' ioctl: LOOP_CLR_FD: No such device or address [18.328866] EXT4-fs (loop1): INFO: recovery required on readonly filesystem [18.329151] EXT4-fs (loop1): write access will be enable during recovery [18.356624] EXT4-fs (loop1): recovery complete [18.367799] EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null) ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address /init: line7: can't open /dev/sr0: No medium found /dev/sr0: No medium found stdin: Not a typewriter ioctl: LOOP_CLR_FD: No such device or address [27.398618] hidraw: raw HID events driver (C) Jiri Kosina [27.401012] usbcore: registered new interface driver usbhid [27.401366] usbhid: USB HID core driver BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) losetup: could not find any free loop devicet go on FAT32 partitions. /dev/sdc is the location of my usb stick when I'm running my regular, hdd booted OS. The errors seem just... weird... It's not even technically out of loops for as far as I know, because those could go all the way up to device loop7.

Senji 10y ago

It just works for me. As far as I know it uses recompiled linux tools to do its job on windows. Yumi used to have a linux version, but it seems to be under rewrite. You could try using wine I guess?

drvdevd 10y ago

Ok so what I'm reading is that: 1) you can get EFI to load grub but 2) actually loading the live system image isn't working So given those assumptions my next question is: Is the kernel and initramfs loading? If you're not sure try: * holding shift to display the grub boot menu on power up * hitting 'e' to edit the default boot menu * removing 'splash' from the kernel command line so you can observe boot messages * continue booting by hitting ctrl+x See if you can glean some more info from that

drvdevd 10y ago
also, if you can pastebin your boot/grub/grub.cfg file that'd be helpful too
- Bluescreens 10y ago
  menuentry '[loopback]ubuntu-14.04.1-desktop-amd64' { set isofile='/ubuntu-14.04.1-desktop-amd64.iso' loopback loop (hd0,2)$isofile linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=$isofile locale=en_US.UTF-8 initrd (loop)/casper/initrd.lz } This works.
  - drvdevd 10y ago
    Ok so one immediate point that I notice here is that if you look closely at this grub configuration, you'll see that the EFI boot Kernel and initrd are not loaded from an EFI partition, but rather taken from the ISO itself: > loopback loop (hd0,2)$isofile > linux (loop)/casper/vmlinuz.efi Whereas above, for Ubuntu 16.04, you appear to be trying to use a separate fat32 EFI partition to load vmlinuz.efi So, just to test, you should try to do what Ubuntu 14.04 is doing, but keep your EFI parition to load grubx64.efi. Make sense? So your partiton layout on this USB stick will be as follows: Partlabel: gpt (hd0,gpt1): FAT32 (type: EFI system) - has path/to/grubx64.efi (hd0,gpt2): ext4 (type: Linux) - has boot/grub/grub.cfg - has ubuntu-16.04-WHATEVER-REALNAME-HERE.iso ---- And the grub.cfg now has a new menu entry as follows: menuentry '[loopback]ubuntu-16.04-desktop' { set isofile='/ubuntu-16.04-WHATEVER-REALNAME-HERE.iso' loopback loop (hd0,2)$isofile linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=$isofile locale=en_US.UTF-8 initrd (loop)/casper/initrd.lz } Let me know if that solution works for you? [Edit] I think the issue with all of this here is the other scripts/parts of Casper that get loaded normally using the ISO. Its annoying, but casper is the ubuntu way. There are better ways to boot a live system off EFI but this would be the quickest path
    - drvdevd 10y ago
      [Edit 2] where you put grub/grub.cfg in the above partition layout is also up to you. It could reside on the EFI parition. Its all about how you lay it out in the host system when putting this disk together and then how you run grub-install
      - deleted 10y ago
        [deleted]
      - deleted 10y ago
        [deleted]
      - deleted 10y ago
        [deleted]
      - Bluescreens 10y ago
deleted 10y ago
[deleted]
deleted 10y ago
[deleted]
Bluescreens 10y ago
Correct. Surprisingly all the grub2 parts seem to be in working order. The issue seems to lie somewhere with the vmlinuz.efi/initrd.lz... I can follow the grub entry to my custom.iso, but the system hangs with "error: no suitable video mode found. booting in blind mode" if I use the vmlinuz-version-generic and/or vmlinuz-version-generic.efi.signed from the host OS. (the regular ubuntu-16.iso also displays the same message, but then proceeds to but correctly. So that shouldn't be the issue here). But it does load when I copy over the /EFI and casper/{vmlinuz.efi,initrd.lz}. However it again eventually stalls with: BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) losetup: could not find any free loop devicet go on FAT32 partitions. [I somehow can´t seem to get the formatting to stick with this next part, sorry :S] After: Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done. Begin: Running /scripts/nfs-premount ... done. Begin: Running /scripts/casper-premount ... [ 10.177576] random: nonblocing pool is initialized [10.473862] SGI XFS with ACLs, security attributes, realtime, no debug enabled [10.479729] JFS: nTxBlock = 8192, nTxLock = 65536 [10.627678] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [10.776705] FAT-fs (sdb1): error, fat_get_cluster: invalid cluster chain (i_pos 1) [10.776720] FAT-fs (sdb1): Filesystem has been set read-only [11.029557] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null) done. Begin: ...waiting for devs... ... done. touch: /dev/.initramfs/lupin-waited-for-devs: No such file or directory stdin: Not a typewriter mount: mounting /dev/sdb1 on /isodevice failed: Input/output error warning: Cannot mount /dev/sdb1 on /isodevice stdin: Not a typewriter [11.689807] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fschk. [11.740150] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null) done. ioctl: LOOP_CLR_FD: No such device or adress [12.524128] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address stdin: Not a typewriter [13.247442] FAT-fs (loop0): error, fat_get_cluster: invalid cluster chain (i_pos 1) [13.870988] EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null) ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address stdin: Not a typewriter ioctl: LOOP_CLR_FD: No such device or address unable to open '/dev/sdc' ioctl: LOOP_CLR_FD: No such device or address [18.328866] EXT4-fs (loop1): INFO: recovery required on readonly filesystem [18.329151] EXT4-fs (loop1): write access will be enable during recovery [18.356624] EXT4-fs (loop1): recovery complete [18.367799] EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null) ioctl: LOOP_CLR_FD: No such device or address ioctl: LOOP_CLR_FD: No such device or address /init: line7: can't open /dev/sr0: No medium found /dev/sr0: No medium found stdin: Not a typewriter ioctl: LOOP_CLR_FD: No such device or address [27.398618] hidraw: raw HID events driver (C) Jiri Kosina [27.401012] usbcore: registered new interface driver usbhid [27.401366] usbhid: USB HID core driver BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) losetup: could not find any free loop devicet go on FAT32 partitions. /dev/sdc is the location of my usb stick when I'm running my regular, hdd booted OS. The errors seem just... weird... It's not even technically out of loops for as far as I know, because those could go all the way up to device loop7.