I think you were right about the raid. I had a laptop with RST, and could not install linux to it. After removing the RST that problem was gone.
But the question is how to remove RST. On that laptop I had to use some Windows program to get rid of it. But don’t remember all the details, as it was a couple of years ago.
Exactly! It is my understanding these laptops come with windows preinstalled with RST software Raid and you have to remove it as it is like a partition with this written to the drive. I think if i remember correctly. It may work once changed to AHCI. Guess we will see as he was able to install Mint to it so Arch may be different.
sorry, i do not have the pastebin commands down pat yet.
here is effort 2
lsblk -fm output
http://ix.io/2P1t
fdisk -l | eos-sendlog
http://ix.io/2P1t
cat /etc/fstab
[root@archiso liveuser]# cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
[root@archiso liveuser]#
cat /boot/grub/grub.cfg
[root@archiso liveuser]# cat /boot/grub/grub.cfg
cat: /boot/grub/grub.cfg: No such file or directory
[root@archiso liveuser]# ^C
looks like i am still doing something wrong. sorry for my ignorance.
Those last two commands are meaningful only in the chrooted system.
I see the issue already with the arch-chroot. His partitions are reversed for efi and /
And they both are mounted to /mnt. No wonder nothing works.
@nals
Reboot and do the proper arch-chroot related commands as @ricklinux showed above.
So he needs to do this instead?
sudo su
mount /dev/nvme0n1p1 /mnt
mount /dev/nvme0n1p3 /mnt/boot/efi
arch-chroot /mnt
Yes, if he did the mountpoint to /boot/efi at install time.
But I think he doesn’t need the second mount command unless he is doing something with the efi partition.
So, this should be enough to arch-chroot:
sudo su mount /dev/nvme0n1p1 /mnt arch-chroot /mnt lsblk -fm | eos-sendlog sudo fdisk -l | eos-sendlog cat /etc/fstab | eos-sendlog sudo cat /boot/grub/grub.cfg | eos-sendlog
merci becoup,
2. sudo fdisk -l | eos-sendlog
http://ix.io/2P1k
3.cat /etc/fstab | eos-sendlog
http://ix.io/2P1E
4.sudo cat /boot/grub/grub.cfg | eos-sendlog
http://ix.io/2P1F
mucho gracias
@manuel
I notice another problem already. The disk label is DOS! Not GPT!
Edit: I have to hit the hay as early day tomorrow so hopefully you can look this over and give some advice what to do next.
Now we must know if the machine has UEFI support or only legacy BIOS support.
How do you start the installer? Does it show UEFI entries or BIOS entries?
Please show the install log in liveuser:
sudo mount /dev/nvme0n1p1 /mnt cat /mnt/var/log/Calamares.log | eos-sendlog
cat /mnt/var/log/Calamares.log | eos-sendlog
http://ix.io/2P1L
And in the liveuser, please show the result of
sudo pacman -S inxi inxi -Mz | eos-sendlog
inxi does not install
os-2021.02.03 ~]$ sudo pacman -S inxi
resolving dependencies...
looking for conflicting packages...
Packages (1) inxi-3.3.00.1-1
Total Download Size: 0.22 MiB
Total Installed Size: 0.79 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
error: failed retrieving file 'inxi-3.3.00.1-1-any.pkg.tar.zst' from mirror.alpix.eu : The requested URL returned error: 404
error: failed retrieving file 'inxi-3.3.00.1-1-any.pkg.tar.zst' from ftp.acc.umu.se : The requested URL returned error: 404
error: failed retrieving file 'inxi-3.3.00.1-1-any.pkg.tar.zst' from mirror.linux.pizza : The requested URL returned error: 404
error: failed retrieving file 'inxi-3.3.00.1-1-any.pkg.tar.zst' from mirrors.tuna.tsinghua.edu.cn : The requested URL returned error: 404
error: failed retrieving file 'inxi-3.3.00.1-1-any.pkg.tar.zst' from mirror.ghead.work : Connection timed out after 10001 milliseconds
error: failed retrieving file 'inxi-3.3.00.1-1-any.pkg.tar.zst' from raw.githubusercontent.com : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
[liveuser@eos-2021.02.03 ~]$ ^C
[liveuser@eos-2021.02.03 ~]$
~~~Could you try fetching it again, this time with command
sudo pacman -Sy inxi
Alpix just fixed a mirror certificate issue, so that might help.
yes, mirrors evos seems to be down
http://ix.io/2P1V
You seem to have UEFI system. But the disk is prepared with the dos partition table but it should be gpt. Maybe it is an old disk?
So, if possible, I suggest you reinstall EndeavourOS so that the partition table is gpt.
You can prepare the disk with gparted before installing. Gparted has a menu to create the partition table: Device --> Create Partition Table
Note that doing this will wipe everything from your disk. If you have anything worth keeping there, copy that stuff to another disk before doing anything else.
thank you. will do as per your instructions. is a new computer, so is as brand new disk. have not got it working yet, so nothing is on it.
will report back, and if get the same message again, revert with the info you need.
am grateful for your help
You might want to check the BIOS to make sure the boot settings are set to UEFI Only and not Legacy / BIOS which should be as Manuel mentioned your drive is set to DOS which would be for a legacy/BIOS boot and not GPT which is for UEFI. Hopefully this little explanation helps you understand what is happening and not just blindly typing commands.
Sorry, at this point I actually find that hard to believe.
The error (see below) you posted in another (now locked) thread typically occurs when residue from former installations or installation attempts gets in the way.
error: device UUID xxxx" not found
mount: /new root cannot find VOID=xxx
Scanning through these threads, I see multiple attempts to get you to create a new GPT partition table. At this point (this is the ~160th post here) I simply don’t understand why you haven’t followed this easy suggestion up till now.
Same problem with your chroot-attempts. There seems to be a problem with following instructions.
tldr;
I greatly suspect everything you need to fix your issue has been addressed here!
Knowing how to chroot is a useful skill but shouldn’t be necessary when installing through calamares.
So, please, just “empty” the storage device you want to install to by creating a new GPT partition table and then do an “automatic” install with the EndeavourOS installer. Basically what you should have tried days ago.