Dropped into a GRUB shell after installation

Audio2u · 27 May 2023 07:52

Hi all.
I’ve been running, on my desktop machine, a dual boot system of windoze 10 and linux mint for the last 6 years or so.
For reasons we don’t need to go into here, I’ve decided it’s time to move on from Mint and have embraced Manjaro as my new OS of choice. It was recommended by a trusted source, and I’ve been running it for a week on my laptop (single OS environment) and love it.
So, this afternoon, I decided it was time to update the OS on my desktop machine.
Thankfully, I had taken a written description of my entire system before embarking on this mad adventure. This is how it looked:

NVMe0 (GPT, 256 GB, m.2)
nvme0n1p1. Windows Recovery (472 MB)
nvme0n1p2. EFI system (105 MB)
nvme0n1p3. Microsoft reserved (17 MB )
nvme0n1p4. Windows 10 (128 GB)
nvme0n1p5. Microsoft reserved (549 MB)
nvme0n1p6. Linux Mint (50 GB)

SDA (GPT, 4 TB HDD)
sda1. NTFS /Data 3 (3.6 TB)
sda2. Swap (8 GB)

SDB (GPT, 3 TB HDD)
sdb1. EXT4 /Photos (3 TB)

SDC (GPT, 120 GB SSD)
sdc1. NTFS /Working media (120 GB)

SDD (GPT, 250 GB SSD)
sdd1. EXT4 Linux /Home (250 GB)

boot loader on SSD where /home is located

When I went to install Manjaro, I chose the "manual partition’ option.
First, I removed partition #6 from the nvme drive (the mint partition).
I then created a new partition of 116,000 MB (btrfs) which was going to be my Manjaro partition.
On the next screen, I got a warning saying the boot efi partition SHOULD be at least 300 MB and that I should go and do something about that.
I grabbed my phone, googled the situation, and found a thread (I think on this very forum) where the general consensus was that it was not essential. So I went ahead with the installation with my existing 105 MB efi partition.
When I rebooted after installation, I did not get a grub menu that I recognised.
I get something that says:

GNU GRUB version 2.06
Minimal BASH-like editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.

Not sure how to proceed from here.
Since then, I’ve redone the installation a couple of times, and have tried creating a new boot efi partition
(at partition #6), and then another partition (#7) for Manjaro.
Again, no luck.
What I would ideally like is:
install manjaro /root on nvme
install /home on SDD (as I had it previously)

Is anyone here knowledgeable enough in the ways of GRUB and installing manjaro to help me out, please?
Oh, I’ve also taken a backup of my old home directory (from SDD), so we can blow that away and start again if we need to.
Many thanks in anticipation!

Moderator edit: corrected your formatting

Olli · 27 May 2023 08:14

hello,
i think this is a good start and thankfully you had been wise enough to do a backup. there are a lot of tutorials in the web. what i would recommend is the description and the video of the manjaro-wiki. there are some more hints at arch-wiki but i think if you playback the backup and start with the description/tutorial from manjaro wiki you’ll be safe.

https://wiki.archlinux.org/title/Dual_boot_with_Windows

stephane · 27 May 2023 12:02

can you boot with USB iso Manjaro ,
open a terminal , and a browser on this topic
an report

inxi -Fza
sudo parted -l
sudo lsblk -fs
sudo efibootmgr -v

Audio2u · 27 May 2023 17:18

Stephane,
Here are the outputs as requested:

inxi -Fza

System:
  Kernel: 6.1.29-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_KDE_2212 quiet
    systemd.show_status=1 splash driver=free nouveau.modeset=1 i915.modeset=1
    radeon.modeset=1
  Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: Micro-Star product: MS-7B79 v: 2.0
    serial: <superuser required>
  Mobo: Micro-Star model: X470 GAMING PLUS (MS-7B79) v: 2.0
    serial: <superuser required> UEFI: American Megatrends v: A.B0
    date: 07/04/2019
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ gen: 2
    level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
    model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 2268 high: 3700 min/max: 2200/3700 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 2200
    3: 2200 4: 1790 5: 2200 6: 2200 7: 2200 8: 2200 9: 3700 10: 2200 11: 2200
    12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 bogomips: 118431
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    disabled, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: ASUSTeK driver: nouveau
    v: kernel non-free: 530.xx+ status: current (as of 2023-05) arch: Ampere
    code: GAxxx process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
    active: HDMI-A-1,HDMI-A-2 empty: DP-1,DP-2,DP-3 bus-ID: 27:00.0
    chip-ID: 10de:2484 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
    s-diag: 1055mm (41.54")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: Dell SE2417HG
    serial: <filter> built: 2018 res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2
    size: 521x293mm (20.51x11.54") diag: 598mm (23.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: right model: BenQ G2420HD
    serial: <filter> built: 2010 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.5 Mesa 23.0.3 renderer: llvmpipe (LLVM 15.0.7 256 bits)
    direct-render: Yes
Audio:
  Device-1: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 27:00.1 chip-ID: 10de:228b
    class-ID: 0403
  Device-2: Focusrite-Novation Scarlett 18i20 USB driver: snd-usb-audio
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-4:4
    chip-ID: 1235:8201 class-ID: 0103 serial: <filter>
  API: ALSA v: k6.1.29-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 0.3.70 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 6.94 TiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLW256HEHP-000H1 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: CXB73H1Q temp: 16.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM004-2CV104
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3000DM008-2DM166
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC26 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 840 EVO 120GB
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: BB6Q scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 850 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-6: /dev/sde maj-min: 8:64 vendor: Kingston model: DT101 II
    size: 3.73 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
    spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.00
    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: 36.2 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 316 Uptime: 1m wakeups: 3 Memory: available: 31.29 GiB
  used: 1.9 GiB (6.1%) Init: systemd v: 252 default: graphical tool: systemctl
  Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman pkgs: 1211
  libs: 330 tools: pamac pm: flatpak pkgs: 0 Shell: Zsh v: 5.9 default: Bash
  v: 5.1.16 running-in: konsole inxi: 3.3.27

sudo parted -l

Model: ATA ST4000DM004-2CV1 (scsi)
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  3992GB  3992GB  ntfs            Data  msftdata
 2      3992GB  4001GB  8590MB  linux-swap(v1)        swap


Model: ATA ST3000DM008-2DM1 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name    Flags
 1      1049kB  3001GB  3001GB  ext4         Photos


Model: ATA Samsung SSD 840 (scsi)
Disk /dev/sdc: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name           Flags
 1      1049kB  120GB  120GB  ntfs         Working media  msftdata


Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sdd: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  249GB  249GB  ext4         Home


Model: Kingston DT101 II (scsi)
Disk /dev/sde: 4003MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 2      3915MB  3919MB  4194kB  primary               esp


Model: SAMSUNG MZVLW256HEHP-000H1 (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  473MB  472MB   ntfs         Basic data partition          hidden, diag
 2      473MB   578MB  105MB   fat32        EFI system partition          boot, esp
 3      578MB   595MB  16.8MB               Microsoft reserved partition  msftres
 4      595MB   128GB  128GB   ntfs         Basic data partition          msftdata
 5      128GB   129GB  549MB   ntfs                                       hidden, diag
 6      129GB   129GB  524MB   fat32                                      boot, esp
 7      129GB   245GB  115GB   btrfs

sudo lsblk -fs

NAME    FSTYPE FSVER LABEL          UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0   squash 4.0                                                             0   100% /run/miso/sfs/livefs
loop1   squash 4.0                                                             0   100% /run/miso/sfs/mhwdfs
loop2   squash 4.0                                                             0   100% /run/miso/sfs/desktopfs
loop3   squash 4.0                                                             0   100% /run/miso/sfs/rootfs
sda1    ntfs         Data 3         16617C9C553EA822
└─sda
sda2    swap   1                    d6a6be09-236e-4283-bf5e-47391939e1a0
└─sda
sdb1    ext4   1.0   Photos drive   51fa7ba2-a77f-4f23-8709-5f864bb3769c
└─sdb
sdc1    ntfs         Working media  63D660E0188C87D7
└─sdc
sdd1    ext4   1.0   Home           2816b89b-ccb5-4b96-a243-33da408a1d51
└─sdd
sde1    iso966 Jolie MANJARO_KDE_2212
                                    2023-05-18-20-31-34-00
└─sde   iso966 Jolie MANJARO_KDE_2212
                                    2023-05-18-20-31-34-00                     0   100% /run/miso/bootmnt
sde2    vfat   FAT12 MISO_EFI       6551-AC40
└─sde   iso966 Jolie MANJARO_KDE_2212
                                    2023-05-18-20-31-34-00                     0   100% /run/miso/bootmnt
sr0
nvme0n1p1
        ntfs         Recovery       BA2811C428118095
└─nvme0n1

nvme0n1p2
        vfat   FAT32 BOOT EFI       1814-70CD
└─nvme0n1

nvme0n1p3

└─nvme0n1

nvme0n1p4
        ntfs                        869204D19204C81F
└─nvme0n1

nvme0n1p5
        ntfs                        228CEA538CEA20D1
└─nvme0n1

nvme0n1p6
        vfat   FAT32 BOOT EFI       6755-0A3D
└─nvme0n1

nvme0n1p7
        btrfs        root           fadf3d18-5a1a-4b9c-9045-a33c9e2d1660
└─nvme0n1

sudo efibootmgr -v

BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0002,0000,0001,0005,0006
Boot0000* Windows Boot Manager  HD(2,GPT,91183d2c-d34e-4f84-a1c9-e7db7839548b,0xe1800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000034000100000010000000040000007fff0400
      dp: 04 01 2a 00 02 00 00 00 00 18 0e 00 00 00 00 00 00 20 03 00 00 00 00 00 2c 3d 18 91 4e d3 84 4f a1 c9 e7 db 78 39 54 8b 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 49 00 43 00 52 00 4f 00 53 00 4f 00 46 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 46 00 57 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 34 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* Manjaro       HD(6,GPT,53a994f2-efd0-0744-8fb2-960ca340469d,0xf000000,0xfa000)/File(\EFI\MANJARO\GRUBX64.EFI)
      dp: 04 01 2a 00 06 00 00 00 00 00 00 0f 00 00 00 00 00 a0 0f 00 00 00 00 00 f2 94 a9 53 d0 ef 44 07 8f b2 96 0c a3 40 46 9d 02 02 / 04 04 36 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 41 00 4e 00 4a 00 41 00 52 00 4f 00 5c 00 47 00 52 00 55 00 42 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0002* ubuntu        HD(2,GPT,91183d2c-d34e-4f84-a1c9-e7db7839548b,0xe1800,0x32000)/File(\EFI\UBUNTU\SHIMX64.EFI)
      dp: 04 01 2a 00 02 00 00 00 00 18 0e 00 00 00 00 00 00 20 03 00 00 00 00 00 2c 3d 18 91 4e d3 84 4f a1 c9 e7 db 78 39 54 8b 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 55 00 42 00 55 00 4e 00 54 00 55 00 5c 00 53 00 48 00 49 00 4d 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0005* UEFI OS       HD(6,GPT,53a994f2-efd0-0744-8fb2-960ca340469d,0xf000000,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
      dp: 04 01 2a 00 06 00 00 00 00 00 00 0f 00 00 00 00 00 a0 0f 00 00 00 00 00 f2 94 a9 53 d0 ef 44 07 8f b2 96 0c a3 40 46 9d 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot0006* UEFI: KingstonDT101 II 1.00   PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(10,0)/CDROM(1,0x74ad44,0x8000)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 03 01 / 01 01 06 00 00 00 / 03 05 06 00 0a 00 / 04 02 18 00 01 00 00 00 44 ad 74 00 00 00 00 00 00 80 00 00 00 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot0007* UEFI: KingstonDT101 II 1.00, Partition 2      PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(10,0)/HD(2,MBR,0x0,0x74ad44,0x2000)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 03 01 / 01 01 06 00 00 00 / 03 05 06 00 0a 00 / 04 01 2a 00 02 00 00 00 44 ad 74 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
    data: 00 00 42 4f

Audio2u · 27 May 2023 17:21

…And if we need to blow away partitions 6 and 7 from the nvme drive, so be it.
What I don’t want is to lose my existing windoze installation, simply because that is a nightmare to try and rebuild from scratch (much worse than rebuilding a linux installation from scratch!).

stephane · 27 May 2023 18:24

Audio2u:

 2      473MB   578MB  105MB   fat32        EFI system partition          boot, esp
 6      129GB   129GB  524MB   fat32                                                       boot, esp

you cant have 2 boot & esp partitions on same disk
i think 2 is( windows + ubuntu ) and 6 is linux manjaro

==> no place on sda / sdb / sdc / sdd

1 ) so idea is : ==> check space on p2 ,
you mount p2 and remove only /boot/efi/EFi/ubuntu

sudo  mount /dev/nvme0n1p2 /mnt/boot/efi
df -Th ( see space for /boot/efi )
sudo cd /boot/efi/EFI/Ubuntu
sudo rm -r /boot/efi/EFI/Ubuntu  
df -Th
sudo umount /mnt/boot/efi

remove entry from ubuntu UEFI

sudo efibootmgr -b 0002 -B

first chroot for changing UUID p6 to p2

sudo manjaro-chroot -a 
nano /etc/fstab ( Ctrl + X for save ) 
exit

remove flag & boot from p6 with gparted

sudo gparted

reboot in UEFI , create profile windows , and profile linux
==> windows with secure boot , etc …

recheck info for linux

in your UEFI

disable secure boot
disable fastboot
disks on AHCI
no legacy
no CSM
UEFI only or others ( not windows )

create profile for linux

you should see
UEFI < USB vendor name > < partition 1 > → boot in EFI

reboot on USB live manjaro and recheck all

inxi  -Mxa ( check for UEFI only , not UEFI[legacy] or Bios )
test -d /sys/firmware/efi && echo efi || echo bios
lsblk -fs ( p2 for boot /efi )
manjaro-chroot -a
cat /etc/fstab ( UUID should be p2 )
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck 
grub-mkconfig -o /boot/grub/grub.cfg 
mkinitcpio -P
sync
exit

reboot and check without USB

Audio2u · 27 May 2023 22:20

Stephane,
Thank you for these instructions.
Just a quick question before I commence…
In this section:

sudo  mount /dev/nvme0n1p2 /mnt/boot/efi
df -Th ( see space for /boot/efi )
cd /boot/efi/EFI
cd Ubuntu 
<suppress files>    
df -Th
unmount /mnt/boot/efi

…is < suppress files > something I type in, or was that just an explainer for the following line?

dragan · 28 May 2023 00:58

I’d go with what stephane said and clean up the mess.
But given your efibootmgr listout I’d personally always try adjusting that (order) first and see if by any chance that works (if your manjaro setup did go through properly)

sudo efibootmgr -o 0007,0001,0000,0002,0005,0006

i.e. leave kingston (live usb I guess) as first but remove it from the slot, put manjaro (0001) second, Windows etc. (I myself always put manjaro first and can bump up USB in BIOS if needed)
You can always change this from live USB if needed.

Audio2u · 28 May 2023 10:32

Stephane,
Looks like this might be a long drawn out process! After the first line, I got this:

sudo  mount /dev/nvme0n1p2 /mnt/boot/efi                                                        
mount: /mnt/boot/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
dmesg
dmesg: read kernel buffer failed: Operation not permitted

dmesg(1)
zsh: unknown file attribute: 1

stephane · 28 May 2023 10:48

may be before

sudo mkdir /mnt/boot/efi
sudo  mount /dev/nvme0n1p2 /mnt/boot/efi

Audio2u · 28 May 2023 10:54

sudo mkdir /mnt/boot/efi  1 ✘
mkdir: cannot create directory ‘/mnt/boot/efi’: No such file or directory

Audio2u · 28 May 2023 10:55

Just to be clear, I am currently running the live USB of manjaro…

cfinnberg · 28 May 2023 12:46

Given that you don’t care about the 6 and 7 partitions, I would recommend just installing from scratch but with manual partitioning, so:

Boot the Manjaro’s liveUSB in UEFI mode (be sure of this) and start the installer
When you get to the part where you have to select disk options, select manual partitioning.
In the manual partitioning window, delete partitions 6 & 7
With the free space you have now available, create a new partition that is going to be your root partition. You can mark it with the root flag, but it’s not necessary
Edit the ESP, that is, your partition number 2 (nvme0n1p2) and select /boot/efi as mount point. Make sure (and this is IMPORTANT) that in “Content” field, “Keep” is selected. You don’t want to lose your Windows Boot files. Make also sure that “boot” flag is selected
Edit your /dev/sdd1 partition and select the mount point as /home. Make also sure that content is kept (and not formatted)
Accept these settings, make the changes to the disk and you can proceed to install Manjaro to the end

If, for some reason you still don’t get to boot Manjaro, let us know.
This process will fix some of the redundant things you have in your system, but you can fix the rest after Manjaro is installed and running.
If you have any doubt about this process, please let us know. But I think it shouldn’t be quite difficult

Audio2u · 28 May 2023 17:42

Stephane,
After this failed, I mounted one of my data drives so that I could see where it was mounted.
The live USB seems to mount at this address:

/run/media/manjaro/...

So I thought "Maybe I need to do a mkdir at THAT location instead.
But alas, no, that didn’t work either. Got the same “cannot create the directory” error.

stephane · 28 May 2023 19:09

i think it should be

sudo mkdir /mnt

Audio2u · 28 May 2023 21:08

Which was what you had originally said, right? Or did I stuff something up?
Like I said, when I entered that command:

sudo  mount /dev/nvme0n1p2 /mnt/boot/efi

…what I got back was:

mkdir: cannot create directory ‘/mnt/boot/efi’: No such file or directory

Audio2u · 28 May 2023 21:09

So the issue doesn’t appear to be with the partition we’re trying to mount, but just the permission to create a mount point (if I understand it correctly).

dmt · 28 May 2023 22:56

All the parent directories have to exist. /mnt should already exist, presumably /mnt/boot doesn’t.

sudo mkdir /mnt/boot
sudo mkdir /mnt/boot/efi

# better yet, just tell it to create any non-existent parents
sudo mkdir -p /mnt/boot/efi

Audio2u · 29 May 2023 00:04

Thanks dmt. I’ll try this when I get home tonight.

Audio2u · 29 May 2023 11:44

Stephane,
I got the nvme0n1p2 mounted at /mnt/boot/efi at last!
The output of df -Th suggests the following:

Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/nvme0n1p2 vfat       96M   31M   66M  33% /mnt/boot/efi

But this:

cd /boot/efi/EFI/Ubuntu                                                                                                                                                                               
cd: no such file or directory: /boot/efi/EFI/Ubuntu

My guess is the cd command should have included /mnt at the beginning?
I then proceeded to the next command rm -r /boot/efi/EFI/Ubuntu to which I also added /mnt at the beginning.

rm: descend into write-protected directory '/mnt/boot/efi/EFI/Ubuntu'? y
rm: remove write-protected regular file '/mnt/boot/efi/EFI/Ubuntu/grubx64.efi'? y
rm: cannot remove '/mnt/boot/efi/EFI/Ubuntu/grubx64.efi': Permission denied
rm: remove write-protected regular file '/mnt/boot/efi/EFI/Ubuntu/shimx64.efi'? y
rm: cannot remove '/mnt/boot/efi/EFI/Ubuntu/shimx64.efi': Permission denied
rm: remove write-protected regular file '/mnt/boot/efi/EFI/Ubuntu/mmx64.efi'? y
rm: cannot remove '/mnt/boot/efi/EFI/Ubuntu/mmx64.efi': Permission denied
rm: remove write-protected regular file '/mnt/boot/efi/EFI/Ubuntu/BOOTX64.CSV'? y
rm: cannot remove '/mnt/boot/efi/EFI/Ubuntu/BOOTX64.CSV': Permission denied
rm: remove write-protected regular file '/mnt/boot/efi/EFI/Ubuntu/grub.cfg'? y
rm: cannot remove '/mnt/boot/efi/EFI/Ubuntu/grub.cfg': Permission denied

But permission was denied on all entries.
Any suggestions on how to get around that?
Many thanks again.