![]() ![]()
#Install linux from grub on usb isoAfter that, it is entirely up to the booted kernel and init scripts to find the ISO if necessary and continue booting. The only purpose of loopback on grub2 is to allow one to extract the kernel and init image (initrd or freebsd_module). It is opening the iso file you provide it and allowing grub2 (and only grub2) to access files inside of it. It's not creating a device that either Linux or FreeBSD kernels can see. There seems to be a lot of confusion in this thread about what Grub2 is doing. Grub has a different format and doesn't support loopback. Also, this won't work on Grub, only Grub2. You should be able to leave off everything after "kernel". Actually, I think "noeject", "noprompt", and "splash" are also meaningless for FreeBSD. Have you tested? Does this work? Obviously "boot=casper" and "iso-scan/filename" have no meaning as BSD kernel arguments. It looks like you've copy/pasted the required Ubuntu parameters. Whereas when booting from my already working hdd, the command grub is using is kfreebsd. Unrelated but for the record, grub did not recognize the kfreebsd command but worked alright with the freebsd command. Question is: Given that grub has completed its job and passed command the FreeBSD bootloader, what would be the correct menu entry for successful boot to the setup menu? Of course, I may also be missing a line in grub like ramdisk= or such. The ? option at the command line does list available slices on the USB stick! In my menu entry I have also tried to change Here it drops to the mountroot> prompt where " ? = list valid disk boot devices". }Boot process moves along fine until it gets to mounting root (/). Uns ist nicht bekannt, dass es zu einem permanenten Defekt kommen kann, schließen aber jede Haftung in so einem Fall aus.Search -no-floppy -fs-uuid -015e657c-etc. Unter Umständen muss der USB-Stick mit einem speziellen Verfahren neu dann initialisiert werden. Leider steht sowas nie auf der Packung.ĭas oben beschriebene Verfahren kann dazu führen, dass es bei solchen USB-Sticks zu Fehlern kommt. implizit davon aus, dass der USB-Stick mit einem Windows-Dateisystem beschrieben wird, was man aus unserer Sicht durchaus als "Bug" bezeichnen kann. ![]() Sie missbrauchen scheinbar bestimmte Speicherbereiche, um Information zur Verwaltung des Flashspeichers abzulegen. Manche USB-Sticks verhalten sich gegenüber Linux nicht transparent. Die Bezeichnung für die Partition /dev/sda1 ist bei Grub ( hd0,0). Das Vorgehen ist aber exakt wie bei der Festplatte. Jetzt fehlt natürlich noch der Kernel, eine initial Ramdisk und eine Konfiguration für GRUB unter /boot/grub/menu.lst. [ Minimal BASH-like line editing is supported. If successful, you will be greeted by the prompt from GRUB: GNU GRUB version 0.96 (640K lower / 3072K upper memory) #Install linux from grub on usb PcIf so far you have done everything correctly, and nothing wrong, you should now be able to boot a PC from this USB stick. Important: Do not forget to unmount: umount /mnt Test #Install linux from grub on usb installNow you can install GRUB in the MBR on the USB disk: grub-install -root-directory=/mnt /dev/sda Since GRUB names hard disks differently to the Linux kernel, we have to create a file by telling GRUB that /dev/sda is its first hard disk: echo '(hd0) /dev/sda' > /mnt/boot/grub/device.map We create this directory and copy the bootloader parts into it, most easily from our development system’s hard drive – which hopefully also boots with GRUB: mkdir -p cp /boot/grub/*stage* /mnt/boot/grub Grub is stored in the directory /boot/grub. First we mount the new partition after /mnt: mount /dev/sda1 /mnt Now we prepare a directory structure for GRUB and install it on the USB stick. of type ext2: mkfs.ext2 /dev/sda1 Install GRUB On this partition we create a file system, e.g. Important: For the kernel to really interpret the new partition table correctly, it may be necessary to unplug and re-plug the USB stick once. ![]() This can be done with fdisk /dev/sda or cfdisk /dev/sda, for example. Now we create a partition table with one partition and activate it (bootable flag). In the following we assume that /dev/sda is the same as the USB key.Īttention: the following command irretrievably deletes all data on this device! Make sure beforehand which device file your USB stick really addresses! cat /dev/zero > /dev/sdaĬat: write error: No space left on device If there are no SCSI, SATA or other USB storage devices connected to the system, the device used for the USB stick is usually /dev/sda. #Install linux from grub on usb how toThe following procedure illustrates how to install a working bootloader on a USB stick:įirst we overwrite the complete stick with zero bytes. You want to boot a Linux system from a USB stick. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |