Cannot split /BOOT and / (root) while trying to install on multiple devices

Hi all!

I am trying to install Manjaro (manjaro-kde-21.1.5-211008-linux513.iso) on a SD card.
I know that my laptop (Lenovo D330-10igm) does not support booting of an SD card.
For that reason understood that I need to put the /BOOT on a device that is recognized on laptop start up, like internal SSD.
I was able to properly choose the correct destination for Linux Mint, i put the /BOOT on a FAT32 550MB partition and choose to put the Bootloader on the same.
Linux Mint would properly boot after the installation but I was not happy with general performance and choose to try Manjaro.

While installing Manjaro

  1. Choose Manual partitioning
  2. I created a FAT32 partition, mounted it as /BOOT/EFI and flagged it as BOOT and BIOS-GRUB on the internal storage
  3. On the SD card I created a EXT4 partition and mounted is a / (root) and flagged it as ROOT

After the installation the system would boot into GRUB rescue with the message that a certain device is missing (no such device). The ID would be where the ROOT should be, the SD card.

From my understanding is that the installation is not installing the /BOOT and GRUB properly, it looks like it is putting it in the root.

I tried to fix it with the help from few topics on this forum and after about 6 hours of trial-and-error I was able to get the proper GRUB to show but then I would get this kind of message:

In rage i re-installed the Manjaro again and I am once again am stuck on GRUB rescue…

So what did I do wrong while installing the OS?
How can i move the /BOOT from SD card to the FAT32 partition?
When I mount the FAT32 partition in Live I see 2 directories with “Manjaro” and “boot”.

Have you tried /boot respectively /boot/efi? Linux file systems are case sensitive…

Yes, i always wrote it in lowercases. Just wrote it in uppercases for readability here.

OK, then let’s start from the scratch by booting a LIVE ISO and posting output of

inxi -Fza
sudo fdisk -l
sudo blkid

Generally, installing Manjaro on a SD card not optimal, the SD card is not designed to be used to store a multitasking OS on it. Can’t you save some space on your internal disk to put Manjaro on it? 30 GiB could be enough for the beginning.

Flagging the ESP with

is not a good idea, this flag is dedicated for BIOS booting of a gpt parted disk, I guess you intend to boot in UEFI mode.

First of all, thank you for taking time for me.

Here are the results

inxi:

System:    Kernel: 5.13.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=de tz=UTC misobasedir=manjaro 
           misolabel=MANJARO_KDE_2115 quiet systemd.show_status=1 apparmor=1 security=apparmor driver=free nouveau.modeset=1 
           i915.modeset=1 radeon.modeset=1 
           Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux 
Machine:   Type: Detachable System: LENOVO product: 81H3 v: Lenovo ideapad D330-10IGM serial: <filter> Chassis: type: 32 
           v: Lenovo ideapad D330-10IGM serial: <filter> 
           Mobo: LENOVO model: LNVNB161216 v: SDK0J91196 WIN serial: <filter> UEFI: LENOVO v: 8NCN41WW date: 06/24/2021 
Battery:   ID-1: BAT0 charge: 30.0 Wh (86.2%) condition: 34.8/39.0 Wh (89.1%) volts: 8.2 min: 7.7 model: LENOVO L17M2PF3 
           type: Li-ion serial: <filter> status: Discharging cycles: 40 
CPU:       Info: Quad Core model: Intel Pentium Silver N5000 bits: 64 type: MCP arch: Goldmont Plus family: 6 
           model-id: 7A (122) stepping: 1 microcode: 36 cache: L2: 4 MiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8756 
           Speed: 981 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 981 2: 802 3: 871 4: 1173 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel GeminiLake [UHD Graphics 605] vendor: Lenovo driver: i915 v: kernel bus-ID: 00:02.0 
           chip-ID: 8086:3184 class-ID: 0300 
           Device-2: Realtek Intergrated Camera 5M type: USB driver: uvcvideo bus-ID: 1-3:2 chip-ID: 0bda:5876 class-ID: 0e02 
           serial: <filter> 
           Device-3: Realtek Integrated Camera 2M type: USB driver: uvcvideo bus-ID: 1-4:3 chip-ID: 0bda:5830 class-ID: 0e02 
           serial: <filter> 
           Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: modesetting alternate: fbdev,vesa 
           display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1200 s-dpi: 154 s-size: 317x508mm (12.5x20.0") s-diag: 599mm (23.6") 
           Monitor-1: DSI-1 res: 1920x1200 hz: 60 
           OpenGL: renderer: Mesa Intel UHD Graphics 605 (GLK 3) v: 4.6 Mesa 21.2.3 direct render: Yes 
Audio:     Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio vendor: Lenovo driver: snd_hda_intel 
           v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_apl bus-ID: 00:0e.0 chip-ID: 8086:3198 class-ID: 0403 
           Sound Server-1: ALSA v: k5.13.19-2-MANJARO running: yes 
           Sound Server-2: JACK v: 1.9.19 running: no 
           Sound Server-3: PulseAudio v: 15.0 running: yes 
           Sound Server-4: PipeWire v: 0.3.38 running: yes 
Network:   Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: 1040 bus-ID: 02:00.0 chip-ID: 8086:24fd 
           class-ID: 0280 
           IF: wlp2s0 state: down mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-7:5 chip-ID: 8087:0a2b 
           class-ID: e001 
           Report: rfkill ID: hci0 rfk-id: 3 state: up address: see --recommends 
Drives:    Local Storage: total: 145.82 GiB used: 0 KiB (0.0%) 
           ID-1: /dev/mmcblk0 maj-min: 179:24 vendor: SanDisk model: SD16G size: 14.49 GiB block-size: physical: 512 B 
           logical: 512 B type: SSD serial: <filter> scheme: GPT 
           SMART Message: Unknown smartctl error. Unable to generate data. 
           ID-2: /dev/mmcblk1 maj-min: 179:0 vendor: SanDisk model: DA4128 size: 116.48 GiB block-size: physical: 512 B 
           logical: 512 B type: SSD serial: <filter> rev: 0x8 scheme: GPT 
           SMART Message: Unknown smartctl error. Unable to generate data. 
           ID-3: /dev/sda maj-min: 8:0 type: USB model: USB Flash Disk size: 14.84 GiB block-size: physical: 512 B 
           logical: 512 B type: SSD serial: <filter> rev: 1100 scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: Message: No partition data found. 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 41.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 214 Uptime: 2m wakeups: 1 Memory: 7.58 GiB used: 1.55 GiB (20.5%) Init: systemd v: 249 tool: systemctl 
           Compilers: gcc: N/A Packages: pacman: 1234 lib: 333 flatpak: 0 Shell: Bash v: 5.1.8 running-in: konsole 
           inxi: 3.3.06 

fdisk:

Disk /dev/loop0: 71.03 MiB, 74477568 bytes, 145464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 583.29 MiB, 611622912 bytes, 1194576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.8 GiB, 1932173312 bytes, 3773776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 743.34 MiB, 779452416 bytes, 1522368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1: 116.48 GiB, 125069950976 bytes, 244277248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A913918E-0439-459E-9AB1-DD84E4662874

Device             Start       End   Sectors   Size Type
/dev/mmcblk1p1      2048    534527    532480   260M EFI System
/dev/mmcblk1p2    534528    567295     32768    16M Microsoft reserved
/dev/mmcblk1p3    567296 241100799 240533504 114.7G Microsoft basic data
/dev/mmcblk1p4 242227200 244275199   2048000  1000M Windows recovery environment
/dev/mmcblk1p5 241100800 242227199   1126400   550M BIOS boot

Partition table entries are not in disk order.


Disk /dev/mmcblk0: 14.49 GiB, 15560867840 bytes, 30392320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B81756C1-5DFB-D44B-A7D7-0939EC47B6E0

Device         Start      End  Sectors  Size Type
/dev/mmcblk0p1  2048 30392286 30390239 14.5G Linux filesystem


Disk /dev/sda: 14.84 GiB, 15938355200 bytes, 31129600 sectors
Disk model: Flash Disk      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sda1  *         64 6788171 6788108  3.2G  0 Empty
/dev/sda2       6788172 6796363    8192    4M ef EFI (FAT-12/16/32)

blkid:

/dev/loop1: TYPE="squashfs"
/dev/mmcblk0p1: UUID="633cf082-cfa8-4fb4-9b95-0ac6858ba4e6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="298269d2-9c2e-4f4c-9926-32f3153fce3c"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/mmcblk1p3: LABEL="Windows" BLOCK_SIZE="512" UUID="AAFAC418FAC3DEA7" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="66c57edf-6912-4a4a-8de9-c0a7caab08cd"
/dev/mmcblk1p1: LABEL="SYSTEM_DRV" UUID="92C0-1F60" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9bb0137b-7f1e-46e7-947c-df674a4d9788"
/dev/mmcblk1p4: LABEL="WINRE_DRV" BLOCK_SIZE="512" UUID="2CA0C500A0C4D18E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="02fa4c95-4635-4bd8-814c-edba113c08fd"
/dev/mmcblk1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="bcf4e7c3-89b3-4ba7-a640-1c2f8570f6c1"
/dev/mmcblk1p5: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="8443-03DD" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="2012746b-927a-f84f-82a8-843ad2261b91"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="C5CD-B119" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda1: BLOCK_SIZE="2048" UUID="2021-10-08-17-46-47-00" LABEL="MANJARO_KDE_2115" TYPE="iso9660"
/dev/loop3: TYPE="squashfs"

Unfortunately I do not really have storage to spare on this laptop and I am aware that installing it on SD is not optimal but at the moment it is my only option.

For setting the bios-grub flag, am i now forced to again do a re-installation?

EDIT: The screenshot provided is from yesterday, the UUID is different because of the re-install from today, i guess.

USB NVMe sticks are also available.

True but that is more like a work around than a solution for my problem.
I would also need to buy a stick.
I am trying to exhaust the provided hardware that i already have and learn how to properly perform an installation of Manjaro on multiple storage devices.

I still doubt installing on a USB stick is a good idea, but the only thing wrong I have seen is linked to your

/dev/mmcblk1p5

If you want to install Manjaro on the USB stick:

  1. delete /dev/mmcblk1p5
  2. format the USB stick in GPT and format one partition in ext4 (will be your / [“root”] partition).
  3. format /dev/mmcblk1p5 as vfat (512 MiB), set boot flag (only), will be your main ESP.
  4. Boot a live ISO in UEFI mode, run Calamares and place the bootloader into /dev/mmcblk1p5, / (i.e. root folder) assigned to the freshly installed partition of the USB stick.
  5. Reboot into your firmware and select to boot from /dev/mmcblk1p5.
  6. Boot into Manjaro, modify /etc/default/grub to allow os-prober and run sudo update-grub, then reboot.

If everything runs well you should be able to boot into grub’s boot menu and select the OS (Manjaro or Windoze) to boot from there.

I do not want to install on a USB.
I want to put the root on the SD card while having the /boot on “/dev/mmcblk1p5”

The “/dev/mmcblk1p5” is already vfat32 and was already marked as /boot and bios-grub.
The “/dev/mmcblk0p1” is where I want to place my root, on SD card. It was already format as ext4 and as GPT.
All the steps you provided I already did few times (even setting only /boot) and every time i was stuck on step 5 where it would load GRUB rescue.

I will re-install Manjaro again and only set boot flag for /boot:

root:

Summary:

Will write back after the installation.

The installation is done and I am again stuck on grub rescue:

Any suggestion on how to proceed from here?

Here is the new info:

blkid:

/dev/loop1: TYPE="squashfs"
/dev/mmcblk0p5: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="53E8-65FC" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="cd7d992e-f5f8-d645-a0a6-d7c6ab23dfdf"
/dev/mmcblk0p3: LABEL="Windows" BLOCK_SIZE="512" UUID="AAFAC418FAC3DEA7" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="66c57edf-6912-4a4a-8de9-c0a7caab08cd"
/dev/mmcblk0p1: LABEL="SYSTEM_DRV" UUID="92C0-1F60" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9bb0137b-7f1e-46e7-947c-df674a4d9788"
/dev/mmcblk0p4: LABEL="WINRE_DRV" BLOCK_SIZE="512" UUID="2CA0C500A0C4D18E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="02fa4c95-4635-4bd8-814c-edba113c08fd"
/dev/mmcblk0p2: PARTLABEL="Microsoft reserved partition" PARTUUID="bcf4e7c3-89b3-4ba7-a640-1c2f8570f6c1"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/mmcblk1p1: UUID="eab8be1b-7e72-4e29-ad27-0be522abcda4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b6b95094-7f45-1342-a5f7-f1bf3b6bb311"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="C5CD-B119" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda1: BLOCK_SIZE="2048" UUID="2021-10-08-17-46-47-00" LABEL="MANJARO_KDE_2115" TYPE="iso9660"
/dev/loop3: TYPE="squashfs"

fdisk:

Disk /dev/loop0: 71.03 MiB, 74477568 bytes, 145464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 583.29 MiB, 611622912 bytes, 1194576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.8 GiB, 1932173312 bytes, 3773776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 743.34 MiB, 779452416 bytes, 1522368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0: 116.48 GiB, 125069950976 bytes, 244277248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A913918E-0439-459E-9AB1-DD84E4662874

Device             Start       End   Sectors   Size Type
/dev/mmcblk0p1      2048    534527    532480   260M EFI System
/dev/mmcblk0p2    534528    567295     32768    16M Microsoft reserved
/dev/mmcblk0p3    567296 241100799 240533504 114.7G Microsoft basic data
/dev/mmcblk0p4 242227200 244275199   2048000  1000M Windows recovery environment
/dev/mmcblk0p5 241100800 242227199   1126400   550M EFI System

Partition table entries are not in disk order.


Disk /dev/mmcblk1: 14.49 GiB, 15560867840 bytes, 30392320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B81756C1-5DFB-D44B-A7D7-0939EC47B6E0

Device         Start      End  Sectors  Size Type
/dev/mmcblk1p1  2048 30392286 30390239 14.5G Linux filesystem


Disk /dev/sda: 14.84 GiB, 15938355200 bytes, 31129600 sectors
Disk model: Flash Disk      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sda1  *         64 6788171 6788108  3.2G  0 Empty
/dev/sda2       6788172 6796363    8192    4M ef EFI (FAT-12/16/32)

I think there is a conceptual error in how you are trying to achieve your result.

/boot

is part of the / filesystem

So, if you put just /boot on your ssd - there is no / (root) for it.
The (as for now) missing / on the ssd only becomes accessible once the system boots - which it doesn’t.
Likely because there is no / at that point in time.

This is (you want to put it) on the SD card.

I think you need to put at least / and /boot there - and the rest
like /usr and /home and everything else
on the SD card - and mount those via the / on your ssd

I think it would work that way - but it is a bit of work.
… that is how I would approach it.

Another way to explain my train of thought:
you can’t start from /boot
and later in the process mount / to /boot

/boot needs to be mounted to / - which is exactly the other way around

years ago I fiddled with OpenWRT and those routers had very little storage.
But some had an USB port.
There was a method/script that booted the system from internal storage
and then performed a chroot to the filesystem on the attached USB storage.
That may be the way you need to go …

You cannot do that - either it is EFI or it is BIOS.

A partition type can only be of one type either it is - in the context of booting - an $esp type 0xEF00 or bios-gpt type 0xEF02.

BIOS-GRUB as you call it - is for use when booting a BIOS system with a disk partitioned using GPT. In such case an unformatted 1M partition is required with the partition type 0xEF02 (GPT partition does not have a boot section like MBR).

You have tagged the topic with sd-boot - then you are using Calamares installer - which do not support systemd-boot.

It is clear to me what your goal is.

You will be much better off in your understanding of the process if you use a terminal to do an absolute minimal bootable installation on your SD card.

I am a little bit confused now.
A similar approach was successfully executed while installing Linux Mint, mentioned in original post.
I followed those instructions:

Don’t mess around with various bootloaders.
If the BIOS can’t read it the bootloader usually won’t either.
Essentially, you have to put your linux kernel
and initramfs somewhere where GRUB can read them outright,
preferably on the system drive:

  • You could shrink the Windows partition to make about 500 MB of space.
    Then use your distro installer’s Advanced formatting to create an ext4 formatted boot partition in that free space.
    Then put root (/) partition on the microSD.
    Alternatively, you can try setting up a partition there manually with fdisk and mkfs.ext4,
    then force the distro installer to use it as /boot.

From here:
https://forums.lenovo.com/topic/findpost/2713/4296738/4490643

Basically I shrunk my Windows and made a 550 MB partition.
There while Installing Mint was an option to select where to put boot and bootloader.
I chose the 550 MB partition and select whole SD card as / (root)
and Mint would boot properly without errors.

Is that not possible with Manjaro ?

It is possible - what is not possible is to mix BIOS and EFI. Unless you are very sure what you are doing it is easy to mix because even if the existing system is installed using EFI - Legacy mode may be enabled as well and it usually takes precendence over EFI making anything you try to install - install in MBR or BIOS/GPT.

Disable Legacy (MBR, CSM, Compatibility Mode) and boot your system using EFI.

When everything is working with Legacy disabled - then creating an install where the root is on SD card will work as well.

Remember that SDcard is not created for extensive io and as such you need to configure the system to accomodate for this.

On this laptop there is only EFI. I thought that the name BIOS-GRUB means that I could also select where to put bootloader like in Mint, now I know.

I already re-installed Manjaro with /boot and boot flag only on internal storage and put the / root to SD card but it does not boot. It boots to the GRUB rescue.
In post 9 you can see the new options I selected:

If it is possible, what did I do wrong?

You simply do not read or follow what is advised…

Like what?

I followed your advice from here:

And was stuck on part 5 where it boots to GRUB rescue.
What am i supposed to to from there?

Part 6 says to boot into Manjaro, you mean LIVE Manjaro?
If yes, how should I modify /etc/default/grub ?

If i do not read, i would not be here and would already have another OS installed.

It is impossible to guess on why you cannot make it work. There’s even a fair chance of an XY problem so you asking the community why you cannot make it work - is an impossible question.

As I suggested above - you need to find the underlying issue - and the only way of doing that is to know excatly how to create system from scratch.

So I took the time to do a short write-up on how to create a basic system on SD-card.

Please familiarize yourself with the procedure - and along the way you may even see the :bulb: :slight_smile:

Then you can easily substitute the efi partition on your primary disk with the efi partition in the write-up.

Thank you for this detailed tutorial.
I followed it and managed to execute it without errors but I still have problem booting.
My laptop does not support booting from SD card.
That is why i need to put /boot and GRUB on an internal device.
I really fail to see what I am doing wrong here and why this is not working.
This was extremely easy with Mint:

  • Create 550 MB FAT32 partition in internal drive
    • Mount it as /boot
    • In dropdown-menu select the same partition to put bootloader in
  • Create EXT4 partition on whole SD card
    • Mount it as / root
  • Perform installation
  • Restart and it automatically boots into Mint

I am really surprised that a simple installation of an supposed advanced OS is not possible while in other Linux is just few clicks…
The installation process in Calamares is lacking something.

And because of this I am dropping Manjaro.

Thank you for trying to help me.