Changing from SSD to nvme issues [Solved]

[tone2]

All this time you have been trying to install an image of your old system, right? I think that you need to eliminate it as the point of failure by trying to install the default XFCE version of MX 21. If this default version of MX 21 installs without a hitch, then you will know that the problem lies with your snapshot and if it encounters the same problem, I think that you should be looking at hardware failure You can prove hardware failure by installing your snapshot on the old SSD.

Hi again, as a follow up, I'm on the old SSD now, it boots up much faster.

the log says:

Code: Select all

Begin: Mounting root file system ... Begin: Running /scripts/local-top ...   Reading all physical volumes.  This may take a while...
done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1 
rootMX19: clean, 603283/31129600 files, 9377819/124494336 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.93 booting
[info] Using makefile-style concurrent boot in runlevel S.
[ ok ] Starting hotplug events dispatcher: systemd-udevd.
[ ok ] Synthesizing the initial hotplug events (subsystems)...done.
[ ok ] Synthesizing the initial hotplug events (devices)...done.
[ ok ] Waiting for /dev to be fully populated...done.
[ ok ] Setting up keyboard layout...done.

any thoughts?

Cheers

[j2mcgreg]

Two thoughts come to mind:
1) thoroughly check your bios if either the SSD or the NVME can be toggled off. Your long boot time could be accounted for if the bios was looking for, but not locating the SSD (which you had removed).

2) you NVME is faulty.

[tone2]

Two thoughts come to mind:
1) thoroughly check your bios if either the SSD or the NVME can be toggled off. Your long boot time could be accounted for if the bios was looking for, but not locating the SSD (which you had removed).

2) you NVME is faulty.

Thanks anyway, but the nvme is brand new, health is good.

I've tried everything in the BIOS. I'm confident it's a Linux issue. I don't have a good understanding of the Linux boot process.

Best regards,. Rob

[j2mcgreg]

tone2 wrote:

but the nvme is brand new

With NVMEs that is no guarantee of health. It could have a manufacturing or handling defect before you purchased or been damaged during shipping. As mass storage devices go, they are the least robust of the lot.

[Buck Fankers]

You have to configure Live USB Maker to use GPT and you do it this way:
4. Click on Show advanced options and then under the Advanced Options title, select GPT partitioning

Wau, I installed MX countless times, always using GPT/EFI and I had no clue about this option in Live USB Maker. I always set partition table and partitions manually with gparted. Cool, that MX tool can do this for you. Thank you for the info!

[tone2]

tone2 wrote:

but the nvme is brand new

With NVMEs that is no guarantee of health. It could have a manufacturing or handling defect before you purchased or been damaged during shipping. As mass storage devices go, they are the least robust of the lot.

Especially now that they've stopped manufacturing MLC. So useless for cold storage over a couple years too.


Btw when I disabled SATA it wouldn't boot at all.

[tone2]

Does anyone have any experience with efibootmgr?
I was wondering if this could help

[j2mcgreg]

tone2 wrote:

Btw when I disabled SATA it wouldn't boot at all.

That's not what I said to do. What you want to do is prevent the bios from trying to boot from a non-existent or non-operational device. It can be as simple as adjusting the boot order so that the NVMe is given first priority and the SSD last priority. On some bioses you have to set all four boot device slots to the same device because if you don't, the bios will bypass your choice and use its own default hard coded boot order. Consider the scenario where you are trying to install MX on a new computer, but the target computer repeatedly ignores the USB drive and boots straight into Windows. It does this because you have left open options in the bios instead of forcing it to use your choice.

When you initially installed your NVMe, if you didn't prioritize it in the boot order and effectively delist the SSD and the other boot devices as well, the bios is going to try to boot from the SSD first and then all the other devices until it gets to the NVMe. This easily could account for your boot delay.

[tone2]

tone2 wrote:

Btw when I disabled SATA it wouldn't boot at all.

That's not what I said to do. What you want to do is prevent the bios from trying to boot from a non-existent or non-operational device. It can be as simple as adjusting the boot order so that the NVMe is given first priority and the SSD last priority. On some bioses you have to set all four boot device slots to the same device because if you don't, the bios will bypass your choice and use its own default hard coded boot order. Consider the scenario where you are trying to install MX on a new computer, but the target computer repeatedly ignores the USB drive and boots straight into Windows. It does this because you have left open options in the bios instead of forcing it to use your choice.

When you initially installed your NVMe, if you didn't prioritize it in the boot order and effectively delist the SSD and the other boot devices as well, the bios is going to try to boot from the SSD first and then all the other devices until it gets to the NVMe. This easily could account for your boot delay.

I wish it were the case. Changing the boot order was the first thing I tried

[Huckleberry Finn]

With this one it's 40 posts and it'll be page 5 with the next post, still we don't have the QSI .


If there's an option in Bios like "Intel SpeedStep® Technology" , enable it, save, exit.


If no (or if still the same):

Code: Select all

echo RESUME=none | sudo tee /etc/initramfs-tools/conf.d/resume ; sudo update-initramfs -uk all

Reboot . (This will overwrite the previous one which was set to swap partition).


If still not: start the pc with systemd (select an entry with systemd on Grub Menu, if you can't see: look under "Advanced Options") and :

Code: Select all

systemd-analyze critical-chain ; systemd-analyze blame