Hallo Svartis,
Wenn du im Post den Ablauf meinst, wo darüber “Pocedere” steht, dann ist da die efi-Partition:
nvme1n1p1 korrekt nach mnt/boot/efi gemountet und unmittelbar danach kommt der chroot-Aufruf:
[liveuser@eos-2024.01.25 ~]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/archiso/airootfs
sda
└─sda1 exfat 1.0 ED6B-FCBC
sdb iso9660 Joliet Extens EOS_202401 2024-01-25-18-25-14-00
├─sdb1 iso9660 Joliet Extens EOS_202401 2024-01-25-18-25-14-00 0 100% /run/archiso/bootmnt
└─sdb2 vfat FAT16 ARCHISO_EFI 8093-0377
nvme0n1
├─nvme0n1p1 vfat FAT32 8E7E-8790
├─nvme0n1p2
├─nvme0n1p3 ntfs E0EE7F33EE7F0158
└─nvme0n1p4 ntfs E05E3F035E3ED1D0
nvme1n1
├─nvme1n1p1 vfat FAT32 NO_LABEL 5B67-B36D 299M 0% /mnt/boot/efi
├─nvme1n1p2 ext4 1.0 30cfa078-83e8-4b7f-b705-e7cd4ae8e2c7 225G 17% /mnt
├─nvme1n1p3 ext4 1.0 0c84c663-31bb-4398-bb8c-b86cb762133d
└─nvme1n1p4 ntfs ZDatoz 60A1F79F59453CF0
[liveuser@eos-2024.01.25 ~]$ sudo efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0013,0003,0001,000E,0015,000D,0000,0010,0005,0004,0014
Boot0000* USB SanDisk 3.2Gen1 0101333cb019b41d3482e9a7750fb0ebe15d991d801b5a1ee8cf980ab06557f0cd3500000000000000000000b6387c94ff97320081558107a9aa8eaa PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(3,0)/USB(3,0)4eac0881119f594d850ee21a522c59b20800000049535048
Boot0001* Windows Boot Manager HD(1,GPT,15316bec-95f4-41ca-9925-0e44b5828a82,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff04001400000049535048
Boot0002 USB SanDisk 3.2Gen1 0101333cb019b41d3482e9a7750fb0ebe15d991d801b5a1ee8cf980ab06557f0cd3500000000000000000000b6387c94ff97320081558107a9aa8eaa PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/USB(3,0)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0003* Samsung SSD 980 1TB-S649NX0RB02384P PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-DB-11-B1-8F-A1)4eac0881119f594d850ee21a522c59b21000000049535048
Boot0004* SAMSUNG MZVLB512HAJQ-000H1-S3WTNA1M511576 BBS(HD,SAMSUNG MZVLB512HAJQ-000H1-S3WTNA1M511576,0x400)/PciRoot(0x0)/Pci(0x1b,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-85-91-11-50-D9)01001000000049535048
Boot0005* Samsung SSD 980 1TB-S649NX0RB02384P BBS(HD,Samsung SSD 980 1TB-S649NX0RB02384P,0x400)/PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-DB-11-B1-8F-A1)02001000000049535048
Boot0006 Realtek USB3.0 Card Reader XXXX20191030111004 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/Unit(2)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0007 Realtek USB3.0 Card Reader XXXX20191030111004 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/Unit(3)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0008 Realtek USB3.0 Card Reader XXXX20191030111004 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/Unit(4)4eac0881119f594d850ee21a522c59b20980000049535048
Boot000D* Misc Device PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)4eac0881119f594d850ee21a522c59b20800000049535048
Boot000E Network Boot:IPV4 PciRoot(0x0)/Pci(0x0,0x0)/IPv4(0.0.0.00.0.0.0,0,0)4eac0881119f594d850ee21a522c59b21b90000049535048
Boot0010 USB: BBS(65535,,0x0)/PciRoot(0x0)/Pci(0x14,0x0)ffff0b80000049535048
Boot0011* Harddisk BBS(HD,Harddisk,0x900)/PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(255,255)13001000000049535048
Boot0013* USB SanDisk 3.2Gen1 0901e0a9a9db73cc77b495cee25bcb658c0a61dab221d2ba666dd6faf483c1f052c300000000000000000000bcbb0dfcff095f2081558107a72a8938 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0014 NETWORK BOOT:PXE BBS(65535,,0x0)/PciRoot(0x0)/Pci(0x0,0x0)/IPv4(0.0.0.00.0.0.0,0,0)ffff1ba0000049535048
Boot0015 Network Boot:IPV6 PciRoot(0x0)/Pci(0x0,0x0)/IPv6([::]:<->[::]:,0,0)4eac0881119f594d850ee21a522c59b21b98000049535048
[liveuser@eos-2024.01.25 ~]$ sudo mount /dev/nvme1n1p2 /mnt
[liveuser@eos-2024.01.25 ~]$ sudo cat /mnt/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=5B67-B36D /boot/efi vfat defaults,noatime 0 2
UUID=30cfa078-83e8-4b7f-b705-e7cd4ae8e2c7 / ext4 defaults,noatime 0 1
UUID=0c84c663-31bb-4398-bb8c-b86cb762133d /home ext4 defaults,noatime 0 2
#________________________________________________________________________
**[liveuser@eos-2024.01.25 ~]$ sudo mount /dev/nvme1n1p1 /mnt/boot/efi**
**[liveuser@eos-2024.01.25 ~]$ sudo arch-chroot /mnt**
#_________________________________________________________________________
[root@EndeavourOS /]# grub-install
[root@EndeavourOS /]# efibootmgr:
bash: efibootmgr:: command not found
[root@EndeavourOS /]# efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0013,0003,0001,000E,0015,000D,0000,0010,0005,0004,0014
Boot0000* USB SanDisk 3.2Gen1 0101333cb019b41d3482e9a7750fb0ebe15d991d801b5a1ee8cf980ab06557f0cd3500000000000000000000b6387c94ff97320081558107a9aa8eaa PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(3,0)/USB(3,0)4eac0881119f594d850ee21a522c59b20800000049535048
Boot0001* Windows Boot Manager HD(1,GPT,15316bec-95f4-41ca-9925-0e44b5828a82,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff04001400000049535048
Boot0002 USB SanDisk 3.2Gen1 0101333cb019b41d3482e9a7750fb0ebe15d991d801b5a1ee8cf980ab06557f0cd3500000000000000000000b6387c94ff97320081558107a9aa8eaa PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/USB(3,0)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0003* Samsung SSD 980 1TB-S649NX0RB02384P PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-DB-11-B1-8F-A1)4eac0881119f594d850ee21a522c59b21000000049535048
Boot0004* SAMSUNG MZVLB512HAJQ-000H1-S3WTNA1M511576 BBS(HD,SAMSUNG MZVLB512HAJQ-000H1-S3WTNA1M511576,0x400)/PciRoot(0x0)/Pci(0x1b,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-85-91-11-50-D9)01001000000049535048
Boot0005* Samsung SSD 980 1TB-S649NX0RB02384P BBS(HD,Samsung SSD 980 1TB-S649NX0RB02384P,0x400)/PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-DB-11-B1-8F-A1)02001000000049535048
Boot0006 Realtek USB3.0 Card Reader XXXX20191030111004 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/Unit(2)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0007 Realtek USB3.0 Card Reader XXXX20191030111004 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/Unit(3)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0008 Realtek USB3.0 Card Reader XXXX20191030111004 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/Unit(4)4eac0881119f594d850ee21a522c59b20980000049535048
Boot000D* Misc Device PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)4eac0881119f594d850ee21a522c59b20800000049535048
Boot000E Network Boot:IPV4 PciRoot(0x0)/Pci(0x0,0x0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)4eac0881119f594d850ee21a522c59b21b90000049535048
Boot0010 USB: BBS(65535,,0x0)/PciRoot(0x0)/Pci(0x14,0x0)ffff0b80000049535048
Boot0011* Harddisk BBS(HD,Harddisk,0x900)/PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(255,255)13001000000049535048
Boot0013* USB SanDisk 3.2Gen1 0901e0a9a9db73cc77b495cee25bcb658c0a61dab221d2ba666dd6faf483c1f052c300000000000000000000bcbb0dfcff095f2081558107a72a8938 PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)4eac0881119f594d850ee21a522c59b20980000049535048
Boot0014 NETWORK BOOT:PXE BBS(65535,,0x0)/PciRoot(0x0)/Pci(0x0,0x0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)ffff1ba0000049535048
Boot0015 Network Boot:IPV6 PciRoot(0x0)/Pci(0x0,0x0)/IPv6([::],0,Static,[::],[::],0)4eac0881119f594d850ee21a522c59b21b98000049535048
[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
[root@EndeavourOS /]# exit
exit
[liveuser@eos-2024.01.25 ~]$
Aber Annahme, ich würde die grub.cfg bearbeiten wollen?
Ich dachte ich führe den Editor ( im LiveSystem Kwrite) als Administrator aus und öffne die grub.cfg und bearbeite sie, aber so scheint das nicht zu funktionieren.Wie also geht es dann?Kann ich über cat editieren?
Mit “vi” kenne ich mich nicht aus, aber geht etwa:
sudo nano /boot/grub/grub.cfg
???
OK. Für heute ist Schluss! Ich probier morgen weiter.
Gute Nacht EOZ