Let’ go ahead and explore what choices we have and analyze their differences of the best USB persistent Linux distros! Almost any Linux Distro can be installed on a USB flash drive and made persistent, but we need to do some hacking and install software like TimeShift and a full install to get that done! Also they usually require large USB’s (64GB or 128GB) the price of which matches traditional external hard drives and SSDs. => Creating gzip-compressed initcpio image: '/boot/initramfs-6.2-x86_64-fallback.This article is for those of you looking for a Linux distro which is USB persistent so that you can run Linux using just your USB flash drive. > -k /boot/vmlinuz-6.2-x86_64 -c /etc/nf -g /boot/initramfs-6.2-x86_64-fallback.img -S autodetect -microcode /boot/amd-ucode.img -microcode /boot/intel-ucode.img => Building image from preset: /etc/mkinitcpio.d/linu圆2.preset: 'fallback' => Creating gzip-compressed initcpio image: '/boot/initramfs-6.2-x86_64.img' > -k /boot/vmlinuz-6.2-x86_64 -c /etc/nf -g /boot/initramfs-6.2-x86_64.img -microcode /boot/amd-ucode.img -microcode /boot/intel-ucode.img => Building image from preset: /etc/mkinitcpio.d/linu圆2.preset: 'default' => Creating gzip-compressed initcpio image: '/boot/initramfs-6.1-x86_64-fallback.img' > -k /boot/vmlinuz-6.1-x86_64 -c /etc/nf -g /boot/initramfs-6.1-x86_64-fallback.img -S autodetect -microcode /boot/amd-ucode.img -microcode /boot/intel-ucode.img => Building image from preset: /etc/mkinitcpio.d/linu圆1.preset: 'fallback' => Creating gzip-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img' => WARNING: consolefont: no font found in configuration => WARNING: Possibly missing firmware for module: 'aic94xx' => WARNING: Possibly missing firmware for module: 'wd719x' > -k /boot/vmlinuz-6.1-x86_64 -c /etc/nf -g /boot/initramfs-6.1-x86_64.img -microcode /boot/amd-ucode.img -microcode /boot/intel-ucode.img => Building image from preset: /etc/mkinitcpio.d/linu圆1.preset: 'default' HOOKS="base udev modconf block keyboard autodetect keymap consolefont plymouth filesystems fsck" MODULES="uas usb_storage xhci_pci xhci_hcd" Booting with "fallback" initramfs (which should not have autodetect enabled and every module baked in, right?)ĭirectly after being thrown into initramfs, atleast some of the modules seem to have been loaded $ lsmod.Rearranging HOOKS in /etc/nf as described in ( block and keyboard Hooks before the autodetect hook).Forcing load of modules uas usb_storage xhci_pci xhci_hcd in /etc/nf.Installing linux-firmware-qlogic and upd72020x-fw to reduce errors during mkinitcpio.PATH PTTYPE PARTTYPE FSTYPE PARTTYPENAME UUID $ lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME,UUID |_ Port 4: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000Mīus 004 Device 003: ID 152d:0583 JMicron Technology Corp. This is the device I'm using (while being plugged into the USB 3.0 port) $ lsusb -t the device and all partitions appear under /dev, $ blkid is now showing every correctly) and I can boot without any problems by manually doing mount /dev/disk/by-uuid/ new_root # OR: mount /dev/sda2 new_root When I un- and replug the USB device itself (while still being in the initramfs shell), suddenly everything's mounted properly (e.g. The block devices are missing entirely in /dev (should appear as /dev/sdaX and /dev/disk/by-uuid/b6c7). You are now being dropped into an emergency shell. Doing the same thing on a USB 3.0 port however, initramfs can not find the UUID defined in grub.cfg anymore. When using a USB 2.0 port, GRUB loads, automatically boots into my installation which itself starts up without any problems. I tried to achieve the same thing with an Arch Linux (Manjaro) installation. I'm using NVMe -> USB 3.0 converter enclosures to create some really snappy persistent USB mountable OS installations and so far had great success with some persistent Windows installation tool. Some custom persistent Windows Installation from another identical USB Device also bootable without any problems, regardless of using USB 2.0 or 3.0.īooting Arch Linux Installation using USB 3.0 only possible by being thrown into initramfs, manually unplugging and replugging the Device, manually typing the mount command for the specific UUID, and manually typing Exit. Booting Arch Linux from USB Device is possible without problems using a USB 2.0 port.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |