On a fresh installation of windows, I downloaded tuxboot to make a gparted live USB.
No matter what I do, every time the USB drive boots to the grub command line. Both Clonezilla and gparted do this, when I boot it on my EFI system I get the grub cli.
Using my brothers older PC doesn't work either, but I'm able to get it working in legacy MBR boot mode on there. No matter what I do though, if I boot with EFI i get the grub command line.]
Any advice? I've got no idea what I'm doing wrong. I've tried making it on two different PCs, booting it on two different PCs, nothing.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Weird. Mabye the issue is on the Clonezilla live or GParted live? Which version of Clonezilla live did you try?
What's the files list on your USB flash drive?
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't quite remember the version of Clonezilla, but I tried every available version of GParted live.
I also tried making the drive on both PCs, same result.
My drive had an MBR partition table. This let me boot clonezilla from tuxboot with legacy boot, but when using EFI boot it gave me the grub command line error.
Changing the partition table to GPT worked perfectly just straight up copying the files. However, if I ran tuxboot on the drive with a GPT table, it broke something and it was no longer recognised by my UEFI.
So my original issue I think was trying to use UEFI boot on a device with an MBR partition table, and there also seems to be an issue with tuxboot on a GPT table. Clearly tuxboot doesn't seem neccesary for a GPT drive since you can just copy the files over, but this is definitely what my issue was.
EDIT: Never mind, maybe not.
Clonezilla-alternative works fine just straight copying the files, as does Debian and Windows 10's installer. GParted Live however still gives me the GRUB command line issue.
On further investigation, I think this is actually an issue with the GRUB installations included with normal Clonezilla and GParted Live.
I copied /EFI/boot;
x86_64-efi
bootx64.efi
grubx64.efi
from the clonezilla-alternative installation to the GParted installation, and immediately GParted worked perfectly.
I have no knowledge of how GRUB works and only a very basic knowledge of EFI, so I'm not sure what's going on here.
Last edit: Jademalo 2018-11-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
from the clonezilla-alternative installation to the GParted installation, and immediately GParted worked perfectly." -> That makes secure boot work. GParted live so far does not work for secure booting because it's Debian-based. While alternative Clonezilla live is based on Ubuntu Linux, which supports secure boot.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was under the assumption that all I was doing was copying GRUB? I'm not sure what that would do to change secure boot.
In addition, both trying the alternate version and disabling secure boot didn't seem to work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On a fresh installation of windows, I downloaded tuxboot to make a gparted live USB.
No matter what I do, every time the USB drive boots to the grub command line. Both Clonezilla and gparted do this, when I boot it on my EFI system I get the grub cli.
Using my brothers older PC doesn't work either, but I'm able to get it working in legacy MBR boot mode on there. No matter what I do though, if I boot with EFI i get the grub command line.]
Any advice? I've got no idea what I'm doing wrong. I've tried making it on two different PCs, booting it on two different PCs, nothing.
Thanks
Weird. Mabye the issue is on the Clonezilla live or GParted live? Which version of Clonezilla live did you try?
What's the files list on your USB flash drive?
Steven
I can't quite remember the version of Clonezilla, but I tried every available version of GParted live.
I also tried making the drive on both PCs, same result.
Clonezilla 2.5.6-22 using Tuxboot 0.8.3
Files list is;
It works if I'm able to use legacy boot as I said, so I know it's almost installed correctly. It's just EFI boot that seems broken.
So I have a few theories now.
My drive had an MBR partition table. This let me boot clonezilla from tuxboot with legacy boot, but when using EFI boot it gave me the grub command line error.
Changing the partition table to GPT worked perfectly just straight up copying the files. However, if I ran tuxboot on the drive with a GPT table, it broke something and it was no longer recognised by my UEFI.
So my original issue I think was trying to use UEFI boot on a device with an MBR partition table, and there also seems to be an issue with tuxboot on a GPT table. Clearly tuxboot doesn't seem neccesary for a GPT drive since you can just copy the files over, but this is definitely what my issue was.
EDIT: Never mind, maybe not.
Clonezilla-alternative works fine just straight copying the files, as does Debian and Windows 10's installer. GParted Live however still gives me the GRUB command line issue.
On further investigation, I think this is actually an issue with the GRUB installations included with normal Clonezilla and GParted Live.
I copied /EFI/boot;
from the clonezilla-alternative installation to the GParted installation, and immediately GParted worked perfectly.
I have no knowledge of how GRUB works and only a very basic knowledge of EFI, so I'm not sure what's going on here.
Last edit: Jademalo 2018-11-22
"I copied /EFI/boot;
x86_64-efi
bootx64.efi
grubx64.efi
from the clonezilla-alternative installation to the GParted installation, and immediately GParted worked perfectly." -> That makes secure boot work. GParted live so far does not work for secure booting because it's Debian-based. While alternative Clonezilla live is based on Ubuntu Linux, which supports secure boot.
Steven
Apologies for the really slow reply
I was under the assumption that all I was doing was copying GRUB? I'm not sure what that would do to change secure boot.
In addition, both trying the alternate version and disabling secure boot didn't seem to work.