Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi I have recently upgraded from mint 18.1 to 20.1
When every thing was working ok , I swapped the Hdd to a SSD (Crucial 240gb) and reinstalled system from a Timeshift backup.
However I now find it takes 2min 28 seconds from power on to the login prompt when booting.
I didn't time it on the HDD but guess it was about 35 seconds.
I have checked Stacer and there are no startup apps running.
Any ideas please ?
hardware :-
Toshiba satellite laptop about 9 years old C870-17F , 4gb memory, external Seagate 2TB usb drive.
booting into Linux mint 20.1 cinnamon 64 bit only (no dual boot, windows partition deleted at last upgrade)
That will affect I/O any time, not just at boot - and yes is should definitely be checked. I'd be suspecting a mismatch of device(s) causing systemd to timeout. Was the SSD inserted into a different slot, or did it go into the same slot as the HDD was in ?.
systemd-analyze shows timing for the boot process and system-analyze blame sorts to show the longest boot process first. Although a setting or an alignment problem may not be apparent in the output.
That will affect I/O any time, not just at boot - and yes is should definitely be checked. I'd be suspecting a mismatch of device(s) causing systemd to timeout. Was the SSD inserted into a different slot, or did it go into the same slot as the HDD was in ?.
It is a laptop - only the one slot.
Reading the article on alignment - do I understand it is best to have 2mb unused before each partition ? Or is that just HDD ?
Here is output of systemd-analyze-blame & print all in parted :-
I dont quite understand the post by Jarret W Buse on "Solid State Drive (SSD) – Info and Alignment"
He states "For example, my system shows 'Sector size (logical/physical): 512B/512B' You also need to find the starting position for the partition. For example, mine shows partition 1 starting at 1.05 MB. So, I multiply the starting point by the sector size (105*512). The result is 53760 for the size of the boot record. Then, I divide the result by 4,096. If the result is not a whole number, then the drive is misaligned."
this gives a result of 13.125 ! not a whole number - he does not go on to rectify this - surely it would mean changing the sector to 1.12 or 1.04mb ?
I think I grasp the concept , just need a bit of clarity.
Help please !
I am getting used to resizing and moving my partitions in Gparted , but when I view the results in Parted, the start position and size differ from what Gparted states.
How then can I change anything to align my drive properly ?
For example :-
Gparted results :- too follow in edit
Parted results :-
I wouldn't trust Gparted, it is merely a frontend for command line tools, but what tools and how it is using them is not clear for me. Anyhow, gdisk and modern versions of fdisk both align partitions on 2048-sector boundaries, these are the tools to use.
I wouldn't trust Gparted, it is merely a frontend for command line tools, but what tools and how it is using them is not clear for me. Anyhow, gdisk and modern versions of fdisk both align partitions on 2048-sector boundaries, these are the tools to use.
Great that could save me a bit of time , the info on this subject seems limited or not available , seems there are tools available for Windows but not Linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.