Install Grub On Usb Mac
Gema Shisila
And you chose this topic as your first post? I'm flattered... But you really should make your own topic (or you know, google "grub2 error 17" because it's more common than you think), instead of hijacking this one.
This part sounds very dumb: "If you installed GRUB2, install it to the hard disk containing your boot partition." Come on. Install it with pacstrap then install it with grub-install? These two should be merged together, in one segment. One for GRUB, one for Syslinux, somewhere after the "arch-chroot /mnt" command. If nobody changes it in the next day or so I'll take a stab at it. Because it really doesn't make any sense (to me), why you need to install GRUB (with pacstrap), then install GRUB again (with grub-install). These commands should be consecutive, instead of split:
Just a random guess. Pacstrap can install in /mnt which would become your root folder, I am not sure if you could simply use pacman -S to install in a desired directory. You may be right their, once you arch-chroot, it shouldn't matter. This is more of a forum and wiki section thread than installation.
This part sounds very dumb: "If you installed GRUB2, install it to the hard disk containing your boot partition." Come on. Install it with pacstrap then install it with grub-install? These two should be merged together, in one segment. One for GRUB, one for Syslinux, somewhere after the "arch-chroot /mnt" command. If nobody changes it in the next day or so I'll take a stab at it.
from here =Installation
But it reports "/usr/sbin/grub-setup: Fehler: hdo enthält ein ufs2-Dateisystem, welches bekanntermaßen keinen Platz für einen DOS-Betriebssystemstart bereithält"....blabla
I think it stutters on the constellation of MBR/GPT, BIOS and UEFI.
I tried to ctreate the installmedia (USB-Stick) with rufus as MBR partition scheme fpr BIOS Computers. In BIOS I changed "PCI ROM-Priority" to "antiqated ROM" (alternative: EFI).
But it didn't work.
I also tried to erase the SSD with PartedMagic and create a MSDOS partitiontable. Also didn't work.
What am I doing wrong?
What do I need to do, to create the GRUB-Bootloader?
detach all data disk and keep only boot disk (sda), for my experience grub failed only if try to install whith my data disk connected, once grub is installed, you can atach data disk and all works / boot fine.
I have removed all data disks, as it is recommended in several howtos. Only SATA0=Crucial M4, USB= InstallMedia.
I tried to connect a USB CD-drive and install from that - same issue.
Then I took the DVD-Drive from my main PC and connected it to the Server via SATA-port to use it as a normal SATA drive - but the same issue again.
It reminds me on an attempt to install Debian on the same machine. Back then, I only managed to install Debian Jessie while running everything as UEFI. SSD as GPT, Boot settings to UEFI and creating the install media with rufus, using GPT for UEFI computers. Only then I was able to install GRUB. But since the OMV image ist NOT UEFI compatible, this will not work in this case.
I had the same issue; simply install as you normally would from the USB with all other data disks detached, and when you get to that failure message, there should be an option to cancel or go to the installation menu (I don't know the exact wording). Simply remove the USB installation drive at this time, and choose the option in the installation menu that corresponds with installing GRUB, and it should complete the installation successfully.
Is it possible to make grub install (and later on update) to all disks, and not just /dev/sda? I have no idea which disk is the one that bios wants to boot (all disks are the same, and since I have raid over it, I can't remove them at will), so the only solution I see is to make grub install on all sda-sdg.
You didn't write anything like, which distro you use (Am I blind?). Today I almost destroyed my server, because I was really pi**ed off of not working grub-install. I used to have GRUB error 17, when trying to do that.
So I have better solution, how to install very easily and very quickly grub to multiple drives in raid.If you can boot your system (after install or from live distro), and have Debian Wheezy (in my case ver 7.2), you can just type following command:
I was pressing just enter, enter, enter and last screen, there was a question, into which devices I want to install the GRUB! :-) Just by your space choose all physical drives (do not choose /dev/md devices, just /dev/sdb /dev/sdc and so on and neither don't choose /dev/sdb1 or /dev/sdb2, just only devices without numbers!) In my example /dev/sdb /dev/sdc dev/sdd /dev/sde not /dev/sdb1... Then you go next and wait few seconds (about 30 or 45 seconds to finish) and get a next bier for a celebretion, because YOU DID IT! ;-)
Please replace all instances of /dev/sda with your actual drive. You can find this by using the lsblk or fdisk -l command. Also, keep in mind that installing a bootloader can be a risky operation if not done properly. Always ensure that you have a backup of any important data before proceeding.
If you ever find yourself in a situation where Grub refuses to boot your Linux system, try booting into a live Linux environment and reinstalling Grub. Remember, you can chroot into your installed system from the live environment, and run the same commands as before to install Grub.
I wish to triple boot. sda with Arch, sdb with Mint (where grub actually is) and sdc with Windows (grub chainloads it). I have both Mint and Windows currently installed on their separate hard disks (sdb and sdc) but wish to install Arch onto sda via chainloading. How am I going to do this with installing grub anywhere else.? Thank you
Hi,
I have an older computer -Thinkpad X61s, with BIOS and MBR. I have Haiku OS installed to first partition but as it's quite buggy I want a different daily driver, hence - Solus, as I really liked what I saw running it from USB stick. I installed Solus to second partition and all went fine but I chose not to install new, Solus boot loader to disk, as I already have a boot loader (by Haiku). Now Solus on my HDD is unbootable. Is there a way to install boot loader to Solus PARTITION from Solus Live (running from USB)?
gohlip I have a similar issue and I am confused with this. Should you chroot or not before grub-install? I think if you specify the boot-directory you can install grub from live media but if you are in the chroot /dev/sda is sufficient or (/boot).
(hdx,y) being the solus partition; in above example (hd0,3) and /dev/sdxy is /dev/sda3
And in the event (unlikely) solus did not generate the symlinks (vmlinuz,initrd.img), manually enter the kernels;
first find out the kernels installed in your system.
I would like to reinstall EndeavorOS grub, which was accidentally installed in BIOS mode, in UEFI mode to the ESP partition without having to reinstall EndeavourOS. EOS was installed last after Kubuntu. According to the current setup, using multiboot, Kubuntu UEFi Grub has so far started various operating systems, including EOS. The problem with this is that Ubuntu uses initrd instead of initramfs in the EOS Grub entry for the kernel, so EOS cannot be booted. After every Kubuntu kernel update, I have to manually correct the EOS kernel entries from initrd to initramfs and this is quite a dirty method. In addition, EndeavorOS installed in legacy BIOS mode cannot start Windows 10 that is also installed. The goal is to not have to change in the BIOS whether I start the system in UEFI or legacy BIOS, i.e. only UEFI Grub remains. If the EndeavorOS UEFI grub will be installed on the ESP partition, I would think that it will overwrite the Kubuntu UEFI grub used so far. My question is, is this possible without reinstalling EndeavorOS, and if so, how?
In the meantime, I checked the settings. In any case, the ESP EFI system partition is automatically mounted to /boot/efi in EndeavorOS, as in Kubuntu, according to fstab.
This line is included in etc/default/grub, I think for compatibility reasons.
During the original offline EOS installation, the problem was probably that the installer gave a warning that a small DOS partition was needed to boot with the legacy BIOS, and although the installation was done in EFI mode, I created the partition in question, so the EOS grub installed in MBR. Kubuntu was installed in EFI mode, and the EOS entry was included in its grub, so its own grub started the system by default if UEFI was selected as the boot in the BIOS.
Assuming you keep your system booting bios/mbr those grub settings are enough. That nixos-install command is what will actually install nixos to your drive. The manual has a good step-by-step once you boot from a nix USB. Remember to save Arch files beforehand.
The guy here said, he had to mount first the whole root partition, or better, the whole disk, before he could mount something on a certain folder. Where i think, only the root partition should be enough.
-manjaro-chroot-command-does-not-detect-my-installed-manjaro/97181/7
Ok, changing the UUID is maybe not the best idea.
When you mount your hdd like at this steps decribed,
and then do the grub-install command from above again?
-chroot-from-or-into-any-linux-distribution/34071
&
=GRUB/Restore_the_GRUB_Bootloader