Changing from SSD to nvme issues [Solved]

[tone2]

Then try this:

Code: Select all

idle=nomwait nvme_core.default_ps_max_latency_us=5500

If you can type manually (and correctly) press E on grub, type after ... ro quiet ... press F10 to go on boot (that will be temporary, just for that boot)

or just copy-paste with a space before it, into Kernel Parameters box in "MX Boot Options", Apply, reboot.

Hi All,

I have an update. I reinstalled using the advanced options for GPT, and pasted in

Code: Select all

idle=nomwait nvme_core.default_ps_max_latency_us=5500

in the Kernel parameters.

However the message about 'Reading all physical volumes' still exists for a minute or so. I did notice that it now says:
"gave up waiting for resumed/suspended device"

Is this relevant? And are there any more ideas to resolve this?

Thanks again!

[j2mcgreg]

Reboot and remove those kernel parameters. I think that HF meant those as a fix for your previous install. If you followed my instructions on creating your USB drive, you shouldn't need them this time round.

[Huckleberry Finn]

Code: Select all

lsblk -f | grep swap

[tone2]

Code: Select all

lsblk -f | grep swap

When I enter that I get a huge amount of like search results, it greps into vim docs and heaps of things.

So just the lsblk results:

Code: Select all

Rob@Rob:~
$ lsblk -f
NAME        FSTYPE LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINT
nvme0n1                                                                           
├─nvme0n1p1 vfat   EFI System A042-FA4D                             251.8M     0% /boot/efi
├─nvme0n1p2 ext4   rootMX19   eeb68368-40fb-4cc7-8dff-ea85235b59dd  418.7G     4% /
└─nvme0n1p3 swap   swapMX     fe797927-c0e9-400d-905e-be7fb41ae116                [SWAP]

Is that information about the swap of any importance?

@j2mcgreg Unfortunately, I did follow the instructions, and I think it took longer to write to the USB drive, than last time. However, the long boot time remains :-(

P.S. I removed that addition to the kernel parameters from MX boot options.


Thanks everyone.

[Huckleberry Finn]

Code: Select all

echo RESUME=UUID=fe797927-c0e9-400d-905e-be7fb41ae116 | sudo tee /etc/initramfs-tools/conf.d/resume ; sudo update-initramfs -uk all

Reboot.
_________________________________________

Normally it should grep just this:

└─nvme0n1p3 swap swapMX fe797927-c0e9-400d-905e-be7fb41ae116 [SWAP]

[tone2]

Code: Select all

echo RESUME=UUID=fe797927-c0e9-400d-905e-be7fb41ae116 | sudo tee /etc/initramfs-tools/conf.d/resume ; sudo update-initramfs -uk all

Reboot.
_________________________________________

Normally it should grep just this:

└─nvme0n1p3 swap swapMX fe797927-c0e9-400d-905e-be7fb41ae116 [SWAP]

Hi H. Finn, I ran the command, but on reboot I see it didn't update anything:

Code: Select all

Rob@Rob:~
$ lsblk -f
NAME        FSTYPE LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINT
nvme0n1                                                                           
├─nvme0n1p1 vfat   EFI System A042-FA4D                             251.8M     0% /boot/efi
├─nvme0n1p2 ext4   rootMX19   eeb68368-40fb-4cc7-8dff-ea85235b59dd  418.6G     4% /
└─nvme0n1p3 swap   swapMX     fe797927-c0e9-400d-905e-be7fb41ae116                [SWAP]

So what's the issue, tabs instead of spaces?


For what it's worth, here is the contents of the fstab file:

Code: Select all

 # Pluggable devices are handled by uDev, they are not in fstab
UUID=eeb68368-40fb-4cc7-8dff-ea85235b59dd / ext4 noatime 1 1
UUID=fe797927-c0e9-400d-905e-be7fb41ae116 swap swap defaults 0 0
UUID=A042-FA4D /boot/efi vfat noatime,dmask=0002,fmask=0113 0 0

Thanks very much

[Huckleberry Finn]

Just run the commands as a whole: click the SELECT ALL , then copy-paste press Enter.

[j2mcgreg]

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.

[tone2]

Just run the commands as a whole: click the SELECT ALL , then copy-paste press Enter.

That is exactly what I did....

[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.

I still have the old SSD with the OS on it, because I was going to put it in another PC. I'll plug it in and compare, and get back to you.