Slow mounting of SSD

[Mte90]

I bought a new SSD with more capacity then the previous one and copied with dd.
So after that I removed the swap partition that was on that and enlarged the partition, execute a trimmer, made an update-initramfs, update-grub, add in /etc/sysctl.conf to disable swap, an e2fsck, removed also the reference on fstab of the swap partition.The only difference that i swat that the start block on the previous ssd vas 2048 and on the new one is 2049.I was thinking that was systemd the problem on launching the system because there is like a prompt for like 30 seconds and later start systemd.
This is the output of dmesg https://pastebin.com/KJaVmSUN and you can see that (apart the random issue that I saw that writing random characters on that moment of boot remove that warnings) take 33 seconds to mount my drive.
I am using the latest kernel available and I have no idea how to fix this very slow starting time.
PS: this is what journalctl -b say: https://pastebin.com/kzGHkrzp

[devil]

Wat does

Code Auswählen Erweitern

systemd-analyze blame tell you

[der_bud]

I notice some network activity/waiting in the logs. Do you have NetworkManager-wait-online.service enabled. If yes, does disabling that make your boot faster?

[Mte90]

Systemd-analyze blame report -> https://pastebin.com/DwUSwZU0
As I can see nothing helpful to understand why is so slow before starting systemd itself.
For network manager I am not sure but I think that is executed after the mounting of the ssd so with systemd and I have the problem that slow is before systemd starting itself.
When I boot the laptop, after the choosing of the kernel in grub I have a black screen with a blink prompt dash (where i can write stuff without any effect). after 30 seconds systemd is executed and in less of 3 seconds the operative system is ready.

[absolut]

when was the last file system check on the ssd partitions?

[Mte90]

I made one this morning

[unklarer]

I bought a new SSD with more capacity then the previous one and copied with dd.

To transfer an existing system to an SSD (solid-state drive), dd should only be used with extreme caution. In the default settings, dd uses a block size of 512 bytes, which leads to unnecessary write processes with modern SSDs. If, using the parameter bs=, a block size specification corresponding to the block size or a multiple thereof of the SSD is used, this danger does not exist. Furthermore one should consider that the alignment is kept, which is most probably not the case without further parameters.

Source:

Now the question is, what was your dd command like?

[Mte90]

Code Auswählen Erweitern

dd if=/dev/sdi of=/media/mte90/ADATA/laptop.img bs=64 status=progress
The blocksize was 64
[/code]

[absolut]

that command represents only the "backup" of the original ssd, with all partitions, etc.
personally, i find the block size to be very small for the task... i would have used bs=8M or bs=16M

i think it is quite interesting to check the command that was used to "restore" the image to the new ssd
checking with gparted the alignment of partitions after that makes sense

[Mte90]

Code Auswählen Erweitern

dd if=/media/mte90/ADATA/portatile.img of=/dev/sdi bs=64 status=progress
This is the other one but I am not sure what can do the bs, probably the speed on that but now I don't think that is a big problem.

[dibl]

Sounds like this may be too late to help, but you can use gparted, working on the gui desktop, to copy and paste partitions from one hdd/ssd to another.  Then later you can resize the partitions on the target device, again with gparted.

[absolut]

actually, checking the partitions with gparted (and making sure these are aligned) can still be done.

[Mte90]

I copied with dd and with gparted enlarged the partition so I already made that step.

[unklarer]

Did you also check the alignment (of all partitions)?

Code Auswählen Erweitern

# parted /dev/sda align-check opt

[Mte90]

Report that is not aligned :-/
Checking how to fix that