Hello
My old laptop broke down and I got a new one. But there are some files on it that I would like to have access to.
It’s an NVMe ssd. I was thinking of installing my old NVMe ssd in my new laptop, then chroot into it from a live usb, then copy my home directory to a new usb.
Will it be possible, or is there a better method?
You could do this.
Except you won’t be needing to chroot into the system ( if the sole purpose is to retrieve the data).
You could just mount the partition(s) either from a terminal or using the file manager, navigate to the locations you want to copy your data from and copy it over to another medium.
OK thanks.
So that means I use a liv usb so I can access a terminal or a file browser. Where should I mount my NVMe? Should it be mounted to my empty USB drive?
I don’t have any NVMe adapter for usb, so I only have my laptop’s NVMe slot I can use.
That’s fine.
Yes.
If you use the file manager, you should be able to see both your NVMe disk and your empty usb in the left pane. You could then click on them to be mounted into the filesystem of the live session.
Or, as an example: sudo mount /dev/nvme0n1p1 /mnt (adapt the numbers to accord with the actual situation; you could run lsblk -f to see what partitions there are). Then use the file manager to navigate.
Perfect and thanks, it’s easier than my own suggestion.
I’ll try a little later today. And thanks again.
You are welcome! Let us know how things will play out. If you encounter any issue ( hopefully not), just post about it on the forum.
Good luck!
Everything is perfect so far. The only challenge is that people talk a lot about nvidia drivers and that there are things that don’t work.
But so far everything is working. I have no idea about laptops with nvidia gpu. But I will probably find out how to handle nvidia cards on linux.
I am not using Nvidia cards so I am not the appropriate person to give you some suggestions.
There are however a few articles about Nvidia in EnOS’ wiki that may help you to get started:
https://discovery.endeavouros.com/?s=nvidia
You could also check with inxi -aG to see what drivers are already installed and in use
Thanks, I’m in the process of reading the articles you link to. And inxi -aG shows that it is nvidia driver.
I happened to make a mistake.
I installed my ssd drive and made a backup. When I reinstalled my original drive with my new EOS installation, the systemd-boot menu was gone. I tried logging into my bios to log on to EOS that way, and the EOS boot entry also gone there.
I suspect that windows has overwritten it just like it does with grub.
What do I have to do to log on to EOS again and have access to systemd-boot again?
Is it the same procedure as when you repair grub? This means that I have to chroot into my EOS installation and rebuild systemd-boot again, just like described on these links?
https://support.system76.com/articles/bootloader/#systemd-boot
Depending on your filesystem, choose the appropriate instructions in the link here below to arch-chroot into your system:
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/
Once in chroot, if you are using systemd-boot, run: reinstall-kernels
When done, type exit followed by enter to quit chroot. Reboot.
If you feel you would need more specific instructions, post the output of the following commands:
sudo parted -l
efibootmgr
I managed to chroot into my EOS machine, and then I ran this command reinstall-kernels
Systemd-boot still not working.
I boot directly into windows, and I can’t find the EOS entry through the bios either.
Please post the output of the following commands from the live session:
[liveuser@eos-2023.05.28 ~]$ sudo parted -l
Model: ATA ST1000LM049-2GH1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 16.8MB 16.8MB Microsoft reserved partition msftres
2 16.8MB 1000GB 1000GB ntfs Basic data partition msftdata
Model: Sony Storage Media (scsi)
Disk /dev/sdb: 31.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 1933MB 2049MB 116MB primary fat16 esp
Model: HFM512GDHTNG-8310A (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Warning: failed to translate partition name
Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat32 EFI system partition boot, esp, no_automount
2 274MB 290MB 16.8MB Microsoft reserved partition msftres, no_automount
3 290MB 196GB 196GB ntfs Basic data partition msftdata
5 196GB 198GB 1049MB fat32 boot, esp
6 198GB 511GB 314GB ext4 endeavouros
4 511GB 512GB 1049MB ntfs hidden, diag, no_automount
[liveuser@eos-2023.05.28 ~]$ efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0004,0003,2001,2002,2003
Boot0000* EFI USB Device (Sony Storage Media) PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/HD(1,MBR,0xb15bb315,0x399a80,0x37800)RC
Boot0001* EFI PXE 0 for IPv4 (E8-6A-64-DA-BE-02) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(e86a64dabe02,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0002* EFI PXE 0 for IPv6 (E8-6A-64-DA-BE-02) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(e86a64dabe02,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager HD(5,GPT,868c26a1-24f7-4ce3-9af5-3c3b23c86cf3,0x16dfd000,0x1f4000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0004* Windows Boot Manager HD(1,GPT,67a242e2-f64a-4e86-ae61-7f55db2635fe,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000004f000100000010000000040000007fff0400
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
Let’s try to chroot once again and see how it goes.
In the live session, open a terminal and run:
- sudo mount /dev/nvme0n1p6 /mnt
- sudo mount /dev/nvme0n1p5 /mnt/efi
- sudo arch-chroot /mnt
Now in chroot, run:
reinstall-kernels
Check with efibootmgr to see if an EFI boot entry has been created or not.
If you get any error messages, post the whole of the output from the terminal.
[root@EndeavourOS /]# efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0004,0003,2001,2002,2003
Boot0000* EFI USB Device (Sony Storage Media) PciRoot(0x0)/Pci(0x14,0x0)/USB(19,0)/HD(1,MBR,0xb15bb315,0x399a80,0x37800)RC
Boot0001* EFI PXE 0 for IPv4 (E8-6A-64-DA-BE-02) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(e86a64dabe02,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0002* EFI PXE 0 for IPv6 (E8-6A-64-DA-BE-02) PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(e86a64dabe02,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager HD(5,GPT,868c26a1-24f7-4ce3-9af5-3c3b23c86cf3,0x16dfd000,0x1f4000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0004* Windows Boot Manager HD(1,GPT,67a242e2-f64a-4e86-ae61-7f55db2635fe,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000004f000100000010000000040000007fff0400
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
It has not made a new boot entry.
Maybe I should just reinstall everything and use grub?
I used systemd-boot because I thought windows couldn’t overwrite it like with grube.
In chroot install tree:
pacman -S tree
and then post the output of the following command:
tree /efi
[root@EndeavourOS /]# tree /efi
/efi
├── EFI
│ ├── BOOT
│ │ └── BOOTX64.EFI
│ ├── Linux
│ ├── Microsoft
│ │ ├── Boot
│ │ │ ├── BCD
│ │ │ ├── BCD.LOG
│ │ │ ├── BCD.LOG1
│ │ │ ├── BCD.LOG2
│ │ │ ├── bg-BG
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── bootmgfw.efi
│ │ │ ├── bootmgr.efi
│ │ │ ├── BOOTSTAT.DAT
│ │ │ ├── boot.stl
│ │ │ ├── cbmr_driver.efi
│ │ │ ├── CIPolicies
│ │ │ │ └── Active
│ │ │ │ ├── {5DAC656C-21AD-4A02-AB49-649917162E70}.cip
│ │ │ │ ├── {82443e1e-8a39-4b4a-96a8-f40ddc00b9f3}.cip
│ │ │ │ └── {CDD5CB55-DB68-4D71-AA38-3DF2B6473A52}.cip
│ │ │ ├── cs-CZ
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── da-DK
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── de-DE
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── el-GR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── en-GB
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── en-US
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── es-ES
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── es-MX
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── et-EE
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── fi-FI
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── Fonts
│ │ │ │ ├── chs_boot.ttf
│ │ │ │ ├── cht_boot.ttf
│ │ │ │ ├── jpn_boot.ttf
│ │ │ │ ├── kor_boot.ttf
│ │ │ │ ├── malgun_boot.ttf
│ │ │ │ ├── malgunn_boot.ttf
│ │ │ │ ├── meiryo_boot.ttf
│ │ │ │ ├── meiryon_boot.ttf
│ │ │ │ ├── msjh_boot.ttf
│ │ │ │ ├── msjhn_boot.ttf
│ │ │ │ ├── msyh_boot.ttf
│ │ │ │ ├── msyhn_boot.ttf
│ │ │ │ ├── segmono_boot.ttf
│ │ │ │ ├── segoen_slboot.ttf
│ │ │ │ ├── segoe_slboot.ttf
│ │ │ │ └── wgl4_boot.ttf
│ │ │ ├── fr-CA
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── fr-FR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── hr-HR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── hu-HU
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── it-IT
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── ja-JP
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── kd_02_10df.dll
│ │ │ ├── kd_02_10ec.dll
│ │ │ ├── kd_02_1137.dll
│ │ │ ├── kd_02_14e4.dll
│ │ │ ├── kd_02_15b3.dll
│ │ │ ├── kd_02_1969.dll
│ │ │ ├── kd_02_19a2.dll
│ │ │ ├── kd_02_1af4.dll
│ │ │ ├── kd_02_8086.dll
│ │ │ ├── kd_07_1415.dll
│ │ │ ├── kd_0C_8086.dll
│ │ │ ├── kdnet_uart16550.dll
│ │ │ ├── kdstub.dll
│ │ │ ├── ko-KR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── lt-LT
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── lv-LV
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── memtest.efi
│ │ │ ├── nb-NO
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── nl-NL
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── pl-PL
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── pt-BR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── pt-PT
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── qps-ploc
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── Resources
│ │ │ │ ├── bootres.dll
│ │ │ │ ├── da-DK
│ │ │ │ │ └── bootres.dll.mui
│ │ │ │ ├── en-US
│ │ │ │ │ └── bootres.dll.mui
│ │ │ │ └── fr-FR
│ │ │ │ └── bootres.dll.mui
│ │ │ ├── ro-RO
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── ru-RU
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── sk-SK
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── sl-SI
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── sr-Latn-RS
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── sv-SE
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── tr-TR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── uk-UA
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── winsipolicy.p7b
│ │ │ ├── zh-CN
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ └── zh-TW
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── Recovery
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ └── BCD.LOG2
│ └── systemd
│ └── systemd-bootx64.efi
├── f409e6ec402a4d6495e6828dc6ccdaa0
│ ├── 6.4.8-arch1-1
│ │ ├── initrd
│ │ ├── initrd-fallback
│ │ └── linux
│ └── 6.4.8-zen1-1-zen
│ ├── initrd
│ ├── initrd-fallback
│ └── linux
├── loader
│ ├── entries
│ │ ├── f409e6ec402a4d6495e6828dc6ccdaa0-6.4.8-arch1-1.conf
│ │ ├── f409e6ec402a4d6495e6828dc6ccdaa0-6.4.8-arch1-1-fallback.conf
│ │ ├── f409e6ec402a4d6495e6828dc6ccdaa0-6.4.8-zen1-1-zen.conf
│ │ └── f409e6ec402a4d6495e6828dc6ccdaa0-6.4.8-zen1-1-zen-fallback.conf
│ ├── entries.srel
│ ├── loader.conf
│ └── random-seed
└── System Volume Information
57 directories, 159 files
In chroot, run:
bootctl install
This should create an EFI boot entry for the systemd-boot. Check with efibootmgr.
If it doesn’t, run:
efibootmgr --create --disk /dev/nvme0n1 --part 5 --loader "\EFI\systemd\systemd-bootx64.efi" --label "Linux Boot Manager" --unicode
Check with efibootmgr.
thanks, this bootctl install command worked.