Garuda on USB

I agree with SGS and Bluish, I don't think Garuda developers are supporting your specific use case. That's the beauty of Linux, developers can choose what use case they want to support. Garuda has been optimized very well for the use cases chosen by the developers.

Garuda has its own objectives and unfortunately for you it seems yours is not on the list. :frowning: Just like my own use cases are not on the list of some other distros than Garuda...

6 Likes

I will check on usb by reinstalling what about bootloader GRUB reinstallation

Tried boot repair but

Error showedwed chroot not found while reinstallin grub

garuda -inxi from installation media
System:
  Kernel: 5.15.35-1-lts arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=garuda misolabel=GARUDA_XFCE_TALON quiet
    systemd.show_status=1 systemd.unified_cgroup_hierarchy=1 driver=nonfree
    nouveau.modeset=0 i915.modeset=1 radeon.modeset=1
  Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel wm: xfwm
    v: 4.16.1 vt: 7 dm: LightDM v: 1.30.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2
    serial: <superuser required> Chassis: Oracle Corporation type: 1
    serial: <superuser required>
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required>
    BIOS: innotek GmbH v: VirtualBox date: 12/01/2006
CPU:
  Info: model: Intel Pentium G2010 bits: 64 arch: Ivy Bridge family: 6
    model-id: 0x3A (58) stepping: 9 microcode: 0xFFFFFFFF
  Topology: cpus: 1x cores: 1 smt: <unsupported> cache: L1: 64 KiB
    desc: d-1x32 KiB; i-1x32 KiB L2: 256 KiB desc: 1x256 KiB L3: 3 MiB
    desc: 1x3 MiB
  Speed (MHz): 2794 min/max: N/A core: 1: 2794 bogomips: 5587
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.19.0.0 ports:
    active: Virtual-1 empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5,
    Virtual-6, Virtual-7, Virtual-8
    bus-ID: 00:02.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.3 compositor: xfwm v: 4.16.1 driver:
    X: loaded: vmware unloaded: modesetting alternate: fbdev,vesa gpu: vmwgfx
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x975 s-dpi: 96 s-size: 508x257mm (20.00x10.12")
    s-diag: 569mm (22.41")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1920x975 hz: 60 size: N/A
    modes: max: 1920x975 min: 640x480
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0
    v: kernel bus-ID: 00:05.0 chip-ID: 8086:2415 class-ID: 0401
  Sound Server-1: ALSA v: k5.15.35-1-lts running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.50 running: yes
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020
    bus-ID: 00:03.0 chip-ID: 8086:100e class-ID: 0200
  IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge
    driver: piix4_smbus v: N/A modules: i2c_piix4 port: N/A bus-ID: 00:07.0
    chip-ID: 8086:7113 class-ID: 0680
Drives:
  Local Storage: total: 57.77 GiB used: 6.14 GiB (10.6%)
  ID-1: /dev/sda maj-min: 8:0 type: USB vendor: HP model: v236w
    size: 57.77 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 3.07 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Info:
  Processes: 178 Uptime: 5m wakeups: 26 Memory: 3.07 GiB
  used: 746.3 MiB (23.8%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 Packages: pacman: 1203 lib: 308 Shell: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.15
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'chaotic-aur' does not exist (use '-Sy' to download)
Garuda (2.6.2-1):
  System install date:     2022-05-18
  Last full system update: 2022-05-18 ↻
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       <superuser required>
  Snapshots:               Snapper
  Failed units:            bluetooth-autoconnect.service




Perhaps it is not worth repeating, but I will anyway: I think this will work badly.

  • USB 2.0 is too slow for this kind of system. This is not an insignificant detail; USB 3.0 is ten times faster than USB 2.0, and a USB 3.0 bus speed is still a higher latency than you would get with a proper drive on the metal. If you get this installation up, it is going to be a dog.

  • Between taking proper weekly updates and Btrfs snapshots, you will be taking a lot of read/writes to the flash media and it will not last long. A system that does not call for such an aggressive update routine would be a more practical choice if it is going to live on flash media.

If you insist on doing this anyway, you will have to go into your native BIOS menu and disable secure boot to be able to bring up this system. Have you done that?

Please explain what you mean by this (what system, what partition) and list the directory path if possible.

You have informed the boot repair tool you are using the MBR partition table. If you have an EFI partition you will have to select ESP.

1 Like

performance and other issues arw pater the boot
I cannot boot no boot option
I have insyalled mbr partition and i vannot repair it also

Again, it's a pointless exercise.
Even if it works, you won't enjoy it.

This thread will be closed tomorrow.

3 Likes

I understand you want to create a Persistent Arch system on a USB drive and you selected ViirtualBox as a Linux system to accomplish that.
I regret to inform you that this is not possible. If you or anyone else thinks I am wrong, provide proof.
You have been told several times that this is not working...

Your alternative require 2 USB drives:

Use your current OS (WinOS?) to create a bootable Live ISO of any Linux distribution you want. Boot with that and install the system to the 2nd USB drive.

A special program that is developed for this exact reason is alma, available for archlinux and on Github.

I have used alma successfully and I strongly suggest it for this type of project.

I wish you success with your goals!

7 Likes

What the user wants cannot be accomplished and there are language difficulties, so either he cannot understand, or he refuses to.

There is nothing more we can help with in this topic.