I am trying to dual boot Linux on my laptop (Dell XPS 15) which is running Windows 10 Pro. I did not have any problem dual booting the two operating systems on my desktop. I cannot boot up **ANY** Linux Distro, I have tried Mint, Ubuntu and Elementary OS. Whenever I try to boot from a live USB, I get the this message on all attempts: **GNU GRUB version 2.02~beta2-9ubuntu1** **Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists are possible device or file completions.** **grub>** When I type in "boot" I get the error: **you need to load the kernel first.** Secure boot is disabled, and I have tried both in legacy and UEFI BIOS mode. I have never come across this error before, what causes it?

So I converted a usb live linux install (Tails) from USB to virtualbox using VBoxManage convertfromraw. For it to boot in virtualbox, I need to remove one thing from the boot commandline (live-media=removable). This option is not in the usual /etc/default/grub or grub.d locations. I did find it in: /lib/live/mount/medium/syslinux/live.cfg. I'm not sure how that ends up in the grub commandline. In fact, there is nothing in /boot/grub except unicode.pf2, so I think there is some other mechanism going on here. This is EFI, also. I'm reluctant to run update-grub in case this command line is being put together in a different manner.

Running Fedora 26 in a live environment almost feels like native speed to me, but when I install the OS to a thumb drive and boot into it, everything takes forever to startup. Once things start they're generally much faster but it's practically unusable. Is this considered normal?

I'm having this issue for a few months now...I was using fedora for a long time but it broke after an update and since then I can't install or run a live environment of almost no distro...so far only Linux mint will boot into the live environment but when I install it I get the same error at bootup and the PC turns off. I've tried other distros but no luck. I'm stuck on windows for the time being. The error(s): Could not create MokListRT: Volume Full Could not create MokListXRT: Volume Full Could not create SbatLevelRT: Volume Full Could not create MokListTrustedRT: Volume Full Something has gone seriously wrong: import_mok_state() failed: Volume Full I would really appreciate any help with this issue

I know this is a common problem that has likely been addressed here before, but thus far none of the obvious solutions have worked. I'm trying to install Debian on my laptop (currently running Ubuntu) from a USB flash drive. I have reformated the drive to the FAT32 file system and made sure it has only one partition, I have used Unebootin to create the proper files on my flash drive, installed the ISO image on my root directory and the USB drive, programmed my BIOS chip to boot from the USB (put the HD last in boot order), and disabled secure boot and fast boot; but it just won't boot from from the USB drive. Instead it just boots directly to Ubuntu as if that was the only choice available. I've even tried pressing F2 during the boot sequence and have also tried using both USB ports on my computer, but to no avail. If I have to, I suppose I can live with Ubuntu, but I've been married to Debbie over a decade now and really don't feel like getting to know a whole new OS - even if she's related. Any hints or suggestions would be much appreciated. Thanks.

AFAIK grub-mkconfig and grub-update/update-grub commands only run on the device that they are installed on. I want to run the commands on a usb drive, but - I don't know how to install them on the usb - I can't make the ones that are installed on my computer to run on usb(i.e they should update the usb's grub.cfg file) How can I do either of them? BTW I am using manjaro KDE

We're building a Debian based product. To simplify building these in the factory, I'm trying to build a live disk that will install the main OS. We have an older product that uses this processbut was based on Debian 7. I'm using Debian 11. I've based my Debian 11 recovery process and image on the Debian 7 one. Both use live-build. The Debian 11 system pulls the OS from mainline bullseye repos plus my repo for the one package that carries our bits. It's a multistep process where we run live-build to build the operational system's OS, squash it into a squashfs, then build a live OS around it with a script that does things like partition the driven, unsquash the squashfs file to the appropriate partition, and, most critically not working, apply GRUB. Part of the build does:

install -d /boot/seed
grub-mkimage -Ox86_64-efi -o /boot/seed/BOOTX64.EFI -p '(hd0,1)/EFI/BOOT/grub' \
	part_gpt part_msdos fat
grub-mkimage -Oi386-pc -o /boot/seed/mbr-core.img -p '(hd0,msdos1)/biosgrub' \
	part_msdos fat biosdisk
grub-mkimage -Oi386-pc -o /boot/seed/gpt-core.img -p '(hd0,gpt1)/biosgrub' \
	part_gpt fat biosdisk
cp -a /usr/lib/grub/i386-pc/boot.img /boot/seed/boot.img
cp -a /usr/lib/grub/i386-pc/modinfo.sh /boot/seed/modinfo.sh
grub-editenv /boot/seed/grubenv create

These files end up in the live OS and get copied to the ESP partition prior to attempting to install GRUB. Those files and all the various GRUB modules are copied midway through the install script. Later on in the script, we call grub-install.

grub-install \
    --directory /mnt/biosgrub \
    --boot-image boot.img \
    --core-image core_img \
    /dev/sda

The problem here is that the newer versions of grub-install no longer support core-image and boot-image switches like the version from Debian 7 did so that fails immediately. I took out the boot-image and core-image switches and now it fails with:

grub-install: error: failed to get canonical path of `overlay'.

And yes, there really is an opening backtick with a closing single quote on overlay. I've tried removing the GRUB step, letting it unsquash everything, then booting to a graphical live disk running Manjaro (had it laying about) to try to get more info on the GRUB situation. Running grub-install there fails in the same way. From googling, I've learned that this is because grub-install thinks the target device is using an overlayfs and can't figure out which actual device to use but I'm not really sure where to go from here nor am I certain what questions to ask. I'm happy to provide more details although somethings will have to be redacted for proprietary software reasons. If it matters, manually mounting the created OS partition off-system shows everything to be in the right place, our code is in place and would probably run well if there were a bootloader. ETA: I've made some progress here, mounting the unsquashed OS into a directory in the live disk, mounting /proc, /sys, and /dev into that directory, mounting my EFI partition into it, and chrooting into it. Then running grub-install /dev/sda but grub is still missing on startup.

I made a usb stick with a custom version of ubuntu, is a well know and people don't use to have troubles with this version. I used win32diskimage, rufus and HDDRaw and got the same result with all these programs. Everything seems fine but when start to boot up, I get: 32-bit relocation outside of Kernel! --System halted I am using hive os version: hive-0.5-76-20180924. My computer spec are: Motherboard: TB250-BTC CPU: Intel Pentium G4400 3.3GHz Box Ram: G.Skill Aegis DDR4 2133 PC4-17000 4GB CL15 Power Supply: Aerocool Xpredator 1000GM 1000W 80 Plus Gold Modular I've been using Windows 10 so far without issues.

I'm endeavoring to put Kali linux onto a USB stick - I know it's already written up , but I'd like to use only a portion of the total space (the aforementioned link will use the entire drive space). Let's have my 16GB usb stick mounted as sdb ... the goal is: 16 GB total, split like this... ---------------------------- | 11 | 01 | 04 | (GB) ---------------------------- sdb1 sdb2 sdb3 (partition ID) FAT32 FAT32 FAT32 (format) storage fatdog kalipart (label) - sdb1 is FAT32 and the main storage area (so that [windows can see it] along with any other OSes) - sdb2 is bootable and has Fatdog64 (6.3.0) and Precise Puppy (5.7.1) installed (multi-booting from one syslinux menu) - sdb3 is the target partition for Kali to use The objective is to multi-boot Fatdog64, Puppy, and Kali linux. Currently, sdb2 is bootable (syslinux) and successfully passes to Fatdog and Puppy, both on sdb2. Next I'd like to add chainloading to Kali on sdb3. It seems to me that the best way to do that is to load GRUB4DOS from syslinux (both on sdb2), map sdb3 and chainload to sdb3 from GRUB4DOS. So I ask: How do I install Kali onto an existing partition on this USB stick? Other options: - Install live Kali onto the USB stick/partition from the Kali distro itself - but this doesn't seem to be an option the same way it is with Fatdog/Puppy/Ubuntu - Boot direclty to sdb3, chainloading to sdb2 if necessary (not preferred, but an option) >Update: > >1. I have tried copying the files from a mounted iso to sdb3 using Fatdog64 and noticed several errors, mostly in copying the firmware files. Here's two examples: > Copying /mnt/+mnt+sda1+isos+kali-linux-1+0+6-i286+kali-linux-1+0+6-i286+iso/firmware/amd64/microcode_1.20120910-2_i386.deb as /mnt/sda3/firmware/amd64-microcode_1.20120910-2_i286.deb > ERROR: Operation not permitted > Copying /mnt/+mnt+sda1+isos+kali-linux-1+0+6-i286+kali-linux-1+0+6-i286+iso/debian as /mnt/sda3/debian > ERROR: Operation not permitted > These errors look like permissions errors, but I can't tell if they affect booting or not (I can troubleshoot other errors later, I'd prefer to keep this question to just multi-boot). > >2. I'm chainloading GRUB4DOS from the SYSLINUX installed by default via Fatdog64 ... > > label grub4dos > menu label grub4dos > boot /boot/grub/grldr > text help > Load grub4dos via grldr (in /boot/grub) > endtext > > ... and then once in GRUB4DOS, I have successfully chainloaded GRUB2 (on the kali partition) ... > > title Load GRUB2 inside of kali > find --set-root /g2ldr.mbr > chainloader /g2ldr.mbr > > ... but all this gives me is a grub> prompt, and I haven't figured out any proper combinations of GRUB4DOS commands to load GRUB2 with a GRUB2 config file - and to add to the confusion, I thought the live CD iso of Kali ran on syslinux. (@jasonwryan @user63921)

Using this awesome tutorial I was able to create a bootable Debian live USB with persistence. After some days using it, it's quite configured and I would like to be able to replicate it into another usb drive. Is there any way to do it? I was thinking of creating an ISO image of the configured USB flash drive, but since it has multiple partitions I don't even know if it is possible.

I'd like to test Qubes OS using the Live USB Option. I used Rufus in order to create a bootable USB, changing the image from ISO to DD after opening the iso image. Then I changed the Boot priority to Legacy First. Nothing happened. Qubes OS fails to start the live session. What should I do? (I use Ubuntu 16.04.1) Help much appreciated. Thank you.

I recently built myself a new computer, and I managed to extract the old HDD and SSD and put them into my new computer. When I changed the BIOS settings to boot into Linux, it showed a correct grub screen. However, it would not boot anything, including Windows, which I had previously confirmed worked on its own (It was complaining about my activation key, though). I have a Live USB that I could boot into, and I first mounted my Ubuntu drive and chrooted into it. I then ran grub-mkconfig and update-grub, and now it won't even boot into grub. Linux is on the HDD (/dev/sdb4), and windows is on the SSD (/dev/sdb?). Can you help me get linux to boot? (eg. give me commands to run in order to restore grub?)

I use Linux Mint mostly as OS. I wanted to try to use Fedora more. I wanted to boot liveUSB to ram, familiar toram option to pass to the kernel (although it is not kernel parameter, it AFAIK is passed further down the line of boot sequence) had not worked. I've tried web search and to my surprise most relevant (IMO) result for booting to ram was this post w/out any answers: https://forums.fedoraforum.org/showthread.php?324932-Fedora-33-boot-live-to-ram > the option rd.live.ram doesn't seem to work any more. Any idea how to > boot live image to ram? Is it definite - no boot to ram support for recent versions? Any historic reasons why has it been dropped? It was of particular surprise to me as I've found about swap to ram in Fedora, which I don't recall reading about for Linux Mint / Ubuntu.

I have a time-consuming program running in Lubuntu 18.04 Live. It will take around one day to finish. After the program finishes the computer shuts down. But since I am running Lubuntu Live, the computer asks me to > Please remove the installation medium then press enter after initiating the shutdown. I will be traveling away before the program can finish and will not be back in a few weeks. I don't want the computer to be powered on all that time. My question is: Is there a timeout after which the computer will eventually shut down, or is there any way to skip this prompt and completely shut down Lubuntu Live?

long time Windows user here. Last week I got fed up with Windows 10 and so I used YUMI to create a bootable Ubuntu 16.04 64 Bit USB stick. So far, I love what I see! I installed some software and tried a few things... Now my question is, can I buy myself a new SSD and install/transfer my YUMI USB Ubuntu on it... So that I do not need to install all the software again and setup all the things I have done so far on the USB Ubuntu... Any advise / help would be welcome! Thank you!

I've just gotten a new laptop (Acer Aspire A315-56), where I can't see my HDD from a Linux live boot. When I'm opening GParted, it's only showing one disk and it's the USB Drive from where I've live booted it. My laptop came preinstalled with Windows 10 Home. I've looked up Ask Ubuntu and similar forums, and according to the suggestions, I've tried out the following: Set the SATA Mode to "AHCI" from "Optane without RAID" Disabled Fast Boot from BIOS Disabled Secure Boot Disabled Fast Startup and Hibernate from Windows 10 Power Options Unfortunately, none of those turned out to work for me. As I'm not able to see the HDD from Linux, I'm not able to install it. Can anyone help me out with making the HDD visible from Linux? Using a Virtual Machine isn't really a solution. Also, I've checked that upon hitting

lshw

in the terminal, the SATA Controller shows up there. So, the SATA controller's driver is in the kernel. I'm live booting Ubuntu, if that helps.

I made a custom live system using the Debian FAI service . I can't boot it with secure boot as my laptop is not recognizing the signature somehow. But I can still boot my currently installed Debian system normally (and I have no MOK enrolled) Here is the FAI configuration as seen on the website:

cl=DEBIAN,DHCPC,DEMO,FAIBASE,BOOKWORM,BACKPORTS,SSH_SERVER,STANDARD,NONFREE,RECOMMENDS,KDE,FAIME,AMD64,LIVEISO
NIC1=eth0 fai dirinstall -v -u debian -c$cl /srv/live
fai-cd -s500 -MH -d none -g grub.cfg.live -n /srv/live live-.iso

I expected FAI to use the same signed Grub used by Debian. Apparently not?

I flashed the latest live boot iso of Kali Linux into my USB stick using Rufus. I then changed the boot order in my Bios and deactivated safe boot. When I boot using the USB stick I manage to enter GRUB and select how to start the system. The only way for me to proceed further is to add additional parameters to the Live Boot Amd option, such as **nvidia.modeset=0** and **acpi=off** Unless I do that, I get a black screen with a flashing underscore. When using the additional parameters I listed I manage to enter a text only Kali terminal. What should I do at this point? How can I start Xfce? I tried researching possible solutions, but not many of them reflected my problem. I apologize in advanced if I missed a solution and duplicated a post. Note: I'm using a recent Nvidia Graphics card, as far as I know Nvidia drivers can cause problems with Kali in particular.

A very strange and frustrating problem. I've a live Debian 12 USB for which the Calamares installer (and also the Debian installer) fail. Calamares is more verbose in it's explanation and spits out an installation failed, directory not found error with the following detail: > Could not create new random file \

/var/lib/urandom/random-seed\

. I tried creating /var/lib/urandom in the live system but that didn't work. It's really, really weird because I've used this exact live USB to install on this exact machine multiple times in the past. I also burned a new live USB using a fresh image from the Debian website and had the exact same problem. I'm baffled.

I want to boot Linux distros from GRUB 2.0 command line. I've tried to do so for couple of distros and at "best" I receive initramfs prompt, no GUI which starts if distro is run stardard way. Resulting file system seams to have files contained in initrd file (less then 100Mb), but not in filesystem.squashfs (which is larger than 1Gb). vmlinux, initrd and filesystem.squashfs files are in casper folder and linux command in menu entry in grub.cnf in distros contains boot=casper, I suspect folder name casper is not necessary for kernel option to work, casper is persistence something option related as far as I understood from wikipedia. Also as far as I understood the problem, when boot process tries to do unionfs thing it could not find SquashFS file with all except kernel distro stuff to add. How do I let it know its' location? Maybe the problem is of other root cause, please tell me so then. ADDED 0: I changed linux (hd0,msdos2)/casper/vmlinuz command adding root=UUID=what ls command gives for partition with distro and now starting, finally getting many lines stdin: Not a typewriter, then (initramfs) Unable to find a medium containing live file system and again CLI prompt. Was stdout on screen same lines as w/out root option... I just don't remember for sure, so many lines during boot. I far as understand from the GRUB manual and my try-and-error, root variable can point to device only, not path inside device, so I see setting it will not point to squashfs file inside casper folder. ADDED 1: I run grep -rnw 'initrd file loop mounted location' -e 'filesystem.squashfs' as per https://stackoverflow.com/questions/16956810/how-do-i-find-all-files-containing-specific-text-on-linux and got nothing, so have no idea how init process finds that squashfs file.