Forgive a Linux sinner? Hard drive alignment?

640rider · 04-30-2021, 05:15 PM

You may not want to bother reading this thread, mistakes and misfortune abound within! Look the other way, nothing to see here.

Oh forgive me for I have sinned oh great Linux wizards!
It seems I've installed a few (SSD) hard drives in my old T430 and she's developed a seriously slow start up issue.
As many years as I've stumbled through the Linux world I should be better at this, please be gentle!

As mentioned, Lenovo T430
256gb SSD installed about a month ago mSATA type I believe.
1tb SSD just installed today and she needed the whole (initraf?) grub update deal just to get booted up.

Booting LM 20.1 on the 256gb SSD takes about 2 minutes, this is not good!
Booting MX Linux 19.4 fresh download on the 1tb SSD takes around a minute I'd guess, not so good either I'd guess.

This might take some spoon feeding but help would be greatly appreciated.

df produces

Filesystem 1K-blocks Used Available Use% Mounted on
udev 7999640 0 7999640 0% /dev
tmpfs 1609204 1660 1607544 1% /run
/dev/sdb2 23899984 11178560 11484332 50% /
tmpfs 8046012 448660 7597352 6% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 8046012 0 8046012 0% /sys/fs/cgroup
/dev/sdb1 483048 310496 147620 68% /boot
/dev/sdb3 220562368 24456160 184832584 12% /home
tmpfs 1609200 24 1609176 1% /run/user/1000

lsblk produces

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 929.5G 0 part
└─sda2 8:2 0 2G 0 part
sdb 8:16 0 238.5G 0 disk
├─sdb1 8:17 0 487M 0 part /boot
├─sdb2 8:18 0 23.3G 0 part /
└─sdb3 8:19 0 214.7G 0 part /run/timeshift/backup
sr0 11:0 1 1024M 0 rom

Where might we go from here, I do some pretty mean ribs if you're in the area! ;0)

wpeckham · 04-30-2021, 06:45 PM

1. Your information "reads" better if you enclose it in code tags (or quote tags).

2. It might help if we had the /etc/fstab information, or 'mount' information, or something. Nothing in 'df' reads out the file system format detail.

3. We have no idea what planet, what continent, what country, or city you might be doing those ribs in, (And I recommend AGAINST revieling too much) but it was a nice offer.

Is the boot time you are providing from power-on, or from the start of OS loading? That can make a huge difference. One of my (OLD) machines takes 89 seconds to start loading, and then loads OS in 20 seconds from rotating rust. I suspect I would save 18 seconds by using an SSD, but that initial 89 second self-check will not be rushed.

michaelk · 04-30-2021, 07:48 PM

Just a little spoon feeding.

With Mint you can run systemd-analyze or systemd-analyze blame to see how fast your system actually boots and what step is taking the longest time.

MX 19 uses SySV init by default so you need to install/configure bootchart2 to actually compare timings.

It could be a disk alignment problem but you haven't posted the partition information so can not tell.

syg00 · 04-30-2021, 08:11 PM

Two systems, only one partition likely to be a swap. The first system is likely to be waiting 90 seconds as the UUID has changed. system-analyze doesn't show it - or didn't when I last had the issue.
Partition alignment is extremely unlikely:
i) to have occurred using the install partitioners, and
ii) affect only boot.

Much more info needed - go here and do as it says. Use [code] tag - not [quote] as the latter doesn't maintain table aligned data properly.

640rider · 04-30-2021, 08:12 PM

Thank you wpeckham!

I was pretty serious with the spoon feeding mention. /etc/fstab returns

"bash: /etc/fstab: Permission denied"

Gave it a sudo and got this return

"bash: sudo/etc/fstab: No such file or directory"

Well, I'm from earth, thanks for the concern!
From the time of hitting the power button till the LM in the circle shows is reasonable, OS loading is where the time is taken by the best of my guess although LM was starting quick before the install of the new SSD last night.

Previously LM took maybe 30 to 45 seconds to load from power button to OS loaded, reasonably quick anyway.

michaelk

Thank you too!
I am booted into LM at the moment and systemd-analyze returned

"Startup finished in 37.002s (kernel) + 1min 37.585s (userspace) = 2min 14.587s
graphical.target reached after 1min 37.307s in userspace"

michaelk · 04-30-2021, 08:30 PM

And from the output of systemd-analyze blame what steps are taking the longest to complete?

640rider · 04-30-2021, 08:37 PM

syg00
You may be right although I'm not following your link well.

michaelk

These are the time listings.
"6.562s NetworkManager-wait-online.service >
2.816s systemd-udev-settle.service >
1.294s dev-sdb2.device >
1.001s udisks2.service >
870ms vdr.service >
648ms ufw.service >
564ms networkd-dispatcher.service >
409ms ubuntu-system-adjustments.service >
390ms accounts-daemon.service >
364ms systemd-logind.service >
330ms lircd-setup.service >
282ms avahi-daemon.service >
280ms bluetooth.service >
275ms NetworkManager.service >
274ms tlp.service >
274ms polkit.service >
238ms upower.service >
226ms thermald.service >
218ms wpa_supplicant.service >
215ms ModemManager.service >
192ms gpu-manager.service >
184ms systemd-journal-flush.service >
160ms systemd-resolved.service >
lines 1-23"

syg00 · 04-30-2021, 08:42 PM

Go to the site, click the green "Code" button - perhaps easiest to download the zip. You then unzip it (which you may need to install on mint) and follow the instructions. For [code] tags hit the "Advanced" button at the bottom of the input box and hit "#".

640rider · 04-30-2021, 08:52 PM

I'm going to have to take a break from this for a while, my eyes are getting too blurry.

I appreciate your efforts and will be back a little later.

obobskivich · 04-30-2021, 10:20 PM

Quote:

Originally Posted by 640rider

Thank you wpeckham!

I was pretty serious with the spoon feeding mention. /etc/fstab returns

"bash: /etc/fstab: Permission denied"

Gave it a sudo and got this return

"bash: sudo/etc/fstab: No such file or directory"

There's a typo and missing command here (its interpreting the 'sudo' there as part of the file path) - should be input as:

Code:

sudo cat /etc/fstab

(you could open it in a text editor like nano or vi or whatever but cat will give you the output to terminal easy enough.

Overall I don't tend to worry too much about start-up times - some of my boxes boot faster than I am ready to start using them, some take a good minute or two as they wait for RAID controllers, NICs, whatever to come online. As long as the machine is responsive and productive when I actually mean to use it, that's basically my threshold. But I understand some folks like machines that boot up very fast - if this is a desktop you may consider instead suspending the machine, as resume from that state is usually near-instant on most newer hardware. That all said, if you had a machine that was working at X speed and that has slowed, hardware changes are probably a factor, but it may not be in the OS alone. For example if you added a bunch of new drives to a machine, and want to boot from one of those, but didn't set it up as the primary boot target in the BIOS the machine will 'hang' for a moment while it goes and checks through everything else in turn before finding a bootable device. On-board devices that have option ROMs can also slow start-up down, so if you aren't using something like PXE or a hardware RAID controller, disable it, as it will also 'speed up' the process (because you aren't initializing the device).

640rider · 04-30-2021, 11:01 PM

Still drawing a blank on your link syg00 but the "advanced" mention cleared up some of my posting issues. Thanks!

Edit: I got the file opened to read it and the colors are really messing with my eyes on a black background.

obobskivich

I'm concerned with start up time because the LM 256gb drive was starting quickly before I installed the MX 1tb drive last night. I didn't boot into the LM 256gb drive until today and it's acting like a crippled old HDD.

Your script did produce more info and it's showing a mounting error.

Quote:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb2 during installation
UUID=d801f6e7-f5e5-453c-bced-9e5dcd65ed7c / ext4 errors=remount-ro 0 1
# /boot was on /dev/sdb1 during installation
UUID=09fdb634-6d76-4a8b-8beb-635f133ac68b /boot ext2 defaults 0 2
# /home was on /dev/sdb3 during installation
UUID=3b209f28-92b8-4b7f-bc25-2ac750d7d9e8 /home ext4 defaults 0 2
# swap was on /dev/sda3 during installation
UUID=82d3a282-e12f-488e-8e52-52cb7afd600f none swap sw 0 0
/dev/sr0 /mnt/sr0 auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0

This may be of use too.

Quote:

/dev/sda1: LABEL="rootMX19" UUID="811feb5f-99d7-4bdf-b99b-68ded90b7ec7" TYPE="ext4" PARTUUID="4341defe-01"
/dev/sda2: LABEL="swapMX" UUID="f9aa434c-ea07-4283-baa6-71df490fd5d8" TYPE="swap" PARTUUID="4341defe-02"
/dev/sdb1: UUID="09fdb634-6d76-4a8b-8beb-635f133ac68b" TYPE="ext2" PARTUUID="7a91217b-01"
/dev/sdb2: UUID="d801f6e7-f5e5-453c-bced-9e5dcd65ed7c" TYPE="ext4" PARTUUID="7a91217b-02"
/dev/sdb3: UUID="3b209f28-92b8-4b7f-bc25-2ac750d7d9e8" TYPE="ext4" PARTUUID="7a91217b-03"

I'm beginning to think reinstalling LM on the 256gb drive may be my easiest route to clearing up the lagging boot times.

Dog with a bone some have said so I ran a few drive tests.

Quote:

$ sudo smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-72-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: Samsung SSD 870 EVO 1TB
Serial Number: S625NJ0R271010B
LU WWN Device Id: 5 002538 f3123fc2e
Firmware Version: SVT01B6Q
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat May 1 03:02:59 2021 MDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 85) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 17
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 12
177 Wear_Leveling_Count 0x0013 100 100 000 Pre-fail Always - 0
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0
183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0032 067 058 000 Old_age Always - 33
195 Hardware_ECC_Recovered 0x001a 200 200 000 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0
235 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 5
241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 25546424

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
256 0 65535 Read_scanning was never started
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

sdb test

Quote:

sudo smartctl -a /dev/sdb
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-72-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: DOGFISH SSD 256GB
Serial Number: AA000000000000001443
Firmware Version: T0420A0
User Capacity: 256,060,514,304 bytes [256 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: mSATA
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sat May 1 03:05:52 2021 MDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x0032 100 100 050 Old_age Always - 0
5 Reallocated_Sector_Ct 0x0032 100 100 050 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 050 Old_age Always - 434
12 Power_Cycle_Count 0x0032 100 100 050 Old_age Always - 35
160 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 0
161 Unknown_Attribute 0x0033 100 100 050 Pre-fail Always - 100
163 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 13
164 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 2218
165 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 6
166 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 1
167 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 4
168 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 7000
169 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 100
175 Program_Fail_Count_Chip 0x0032 100 100 050 Old_age Always - 0
176 Erase_Fail_Count_Chip 0x0032 100 100 050 Old_age Always - 0
177 Wear_Leveling_Count 0x0032 100 100 050 Old_age Always - 0
178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 050 Old_age Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 050 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 050 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always - 9
194 Temperature_Celsius 0x0022 100 100 050 Old_age Always - 30
195 Hardware_ECC_Recovered 0x0032 100 100 050 Old_age Always - 669
196 Reallocated_Event_Count 0x0032 100 100 050 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 050 Old_age Always - 0
198 Offline_Uncorrectable 0x0032 100 100 050 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always - 0
232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always - 100
241 Total_LBAs_Written 0x0030 100 100 050 Old_age Offline - 10579
242 Total_LBAs_Read 0x0030 100 100 050 Old_age Offline - 10378
245 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 4968

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

Mount info I missed earlier

Quote:

$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=7999640k,nr_inodes=1999910,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1609204k,mode=755)
/dev/sdb2 on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=152)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/sdb1 on /boot type ext2 (rw,relatime)
/dev/sdb3 on /home type ext4 (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1609200k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdb3 on /run/timeshift/backup type ext4 (rw,relatime)

I have read of an MX installer deal pushing for sda persistence and the msata was sda originally, now the SSD is.
I understand it's just UUID name change, it just seems to have some bearing.
My older desktop has 3gb ram and an Intel e2200, LM 19.3 on a 7200 rpm HDD and MX 19.4 on a 128gb USB flashdrive I set up for an HD, it starts fast than LM starts in the Netbook with 16gb ram and a i7 3520.

This just doesn't seem right and I'm not sure I could trust any large projects saved at this point.

yancek · 05-01-2021, 06:44 AM

If you have 16GB of RAM, I' not sure you would need a swap partition, depends on what you use the computer for.

Quote:

# swap was on /dev/sda3 during installation
UUID=82d3a282-e12f-488e-8e52-52cb7afd600f none swap sw 0 0

This is from your Mint fstab file and it points to a swap partition on the other drive. Does that partition with that UUID exist? The output you posted for the MX drive shows diffeent info below. Do you have both drives attached at all times?

Quote:

/dev/sda2: LABEL="swapMX" UUID="f9aa434c-ea07-4283-baa6-71df490fd5d8" TYPE="swap" PARTUUID="4341defe-02"

obobskivich · 05-01-2021, 07:12 AM

Yeah, agree with yancek - this is 'confusing' to follow becuase you're trying to troubleshoot two installs on a 'dual boot' system - that's probably a big part of why your startup times are 'longer.' A 'slow startup' (again, this is not a 'symptom' as such but I understand its all the rage today) wouldn't lead me to distrust a system - I get the sense this is a configuration issue where you've either got overlapping settings due to the dual-boot or settings at the system BIOS level where it has to look through multiple successive drives to find a bootable one (or both). You say this all 'started' after adding a second SSD and setting up dual-boot, so logically that is the nexus of the problem.

@yancek: Even with 16GB of RAM, I would not run with 'no swap' - but the more modern 1-2GB default swapfile that most newer distros will advocate is probably more than sufficient.

640rider · 05-01-2021, 07:38 AM

Swap files verses swap partitions may have got me here and a little spewtube video tossed in besides being human.

Gparted isn't very clear on this which doesn't help matters, not so good with sizes either. Gparted shows an unallocated 31mb on sba that doesn't make much sense.

I guess I could set up a swap on sdb and reinstall MX on sba with proper partitioning. I had issues with the partitioning during an MX install previous to this new SSD so I foolishly let the installer do the work I should have.

Sound worth a try?
Edit:
Maybe just some partitioning.

michaelk · 05-01-2021, 08:14 AM

You can try commenting out the swap line in your Mint /etc/fstab to see if that improves boot times.

Also try disabling network manager-wait-online.

sudo systemctl disable NetworkManager-wait-online.service