Closed edover2019 closed 4 years ago
might (or might not) help to sort it out - at least worth a try:
We more often see people at irc having issues with nvme .m2 ssds most of them using ubuntu-mint - where in most cases the ssds are not detected at all. The typical reason is, that the bios is set to sata/raid-mode instead of ahci. After switching to ahci-mode most (all?) people succeed in using the ssd.
The downside is - people using a dual-boot setup with windows being installed in sata-mode, people have to fix their windows-install additionally (missing ahci-drivers) to be able to switch to ahci-mode entirely
cheers orcus
@edover2019 can you show the summary screen and the terminal output (you can get that by launching the installer from the command line: sudo live-installer).
Actually, no need.. I can reproduce this here. The partition names aren't correct. It should be an easy fix.
I also had this indication once but after reboot everything worked fine.
Should be fixed by https://github.com/linuxmint/live-installer/commit/7ab8ed68724327f5a873c1dabbc1d811b7b03abb. I'll have to run tests again to make sure.
I attempted an install on a ZenBook today and ran into the same issues as noted above. I attempted a second install selecting the option to encrypt the disk option. In this case the install completed but would not boot. I made the changes in the above noted ticket, and this did not resolve the issue.
I can confirm this change fixes NVMe with simple automated installs (i.e. no LVM, no LUKS). Tested in EFI mode in Virtualbox.
I'll test LVM and LUKS now.
A new version of the installer is available in the repositories, containing this change.
Successful test also for EFI+NVME+Automated+LVM in Virtualbox.
Note that EFI is mandatory in Virtualbox when using NVME.
Successful test also for EFI+NVME+LVM+LUKS in Virtualbox.
I noticed race conditions issues between parted, sync and mkfs though, I'll fix that as well.
I downloaded a fresh install iso, performed an update and installed the live-installer update, and attempted to perform an install. It failed with the same low disk space error.
@barthohomeautomation can you start it from the terminal (sudo live-installer) and provide the output?
-Patrition creation takes a while when installing LMDE4 on an NVMe drive with LVM and LUKS options. Then it starts to proceed with the install. It copies some files, then shows an error that there is not enough disk space and that bootloader has to be installed manually. This happens when installing LMDE 4 on a disks with ample space available.
-Installing LMDE4 on an NVMe drive without LUKS and LVM options results in low disk space and bootloader install errors as well. OS does not install properly.
-Installing LMDE4 on a SATA drive with, or without LVM and LUKS is successful
-These problems all occur when installing LMDE4 on physical and virtual machines using NVMe drives.
-LMDE4 installer seems to have a problem with installing onto an NVMe drive.
-Other Linux operating systems install successfully onto the NVMe drive with, or without LVM and LUKS options.