Over the last 10 years I've enjoyed running Linux and still do today.
My friends and family that I've installed Linux for love their Linux too.
However; there are these 2 issues or problems, have you, that have been consistently occuring and I've grown very irritated with the situation. And, quite frankly, I'm pretty much fed up with having to keep editing the same file over and over again and have to explain myself.
It's my hope that someone knows the fix for what I'm about to explain.
OR> at the very least enlighten me on ideas where to dig into to find evidence to support what's happening and find who or what party profits (if any) from these things happening.
Afterall, something always comes before something else.
In other words something was in place before systemd. (just an example
Over this 10 year period I've installed various Linux distributions on a lot of people's pc's and the problem starts right after the fresh installation and first update to the system.
What happens is with most of the Debian based or Ubuntu based distro's that I've installed I've gotten:
" A start job is running for /dev/disk/by-uuid <number of device>"
It holds up the system at boot time for 1 minute and 30 seconds looking for something (I think a swap partition) and finally times out and the boot resumes.
-::::-This also creates drama with the /etc/fstab file which when compared to the output of blkid 'doesn't match'.-::::-
When that happens I almost always have to do one of 2 things.
Either edit and fix the uuid in the /etc/fstab file with the correct uuid from the output of blkid <or> comment out the whole partition string that doesn't exist from looking at all partitions in gparted.
Which btw, is even harder to fix on a triple booted Linux box.
I am suspicious that this is something that the installer is not getting right during the installation. The installer appears to somehow mis-configure all of the other swap partitions during a regeneration cycle of the other swaps on a rig that has other Linux os installed.
The other issue is boot times after fresh installs that take up to 3 to 5 min's before log in.
Is systemd to blame?
Is this another Nvidia strikes again issue?
Changing the default timeout that's set to 90 seconds sometimes helps and sometimes not.
I've seen folks disable services that were not necessary at boot time and it still hasn't helped.
Is this a hardware issue?
Looking at my signature line you can see I'm not a fan of fixing what's not broken but clearly something here is not right.
Any help, ideas, insight and assistance is greatly appreciated:-
Cheers,
Alex
My friends and family that I've installed Linux for love their Linux too.
However; there are these 2 issues or problems, have you, that have been consistently occuring and I've grown very irritated with the situation. And, quite frankly, I'm pretty much fed up with having to keep editing the same file over and over again and have to explain myself.
It's my hope that someone knows the fix for what I'm about to explain.
OR> at the very least enlighten me on ideas where to dig into to find evidence to support what's happening and find who or what party profits (if any) from these things happening.
Afterall, something always comes before something else.
In other words something was in place before systemd. (just an example
Over this 10 year period I've installed various Linux distributions on a lot of people's pc's and the problem starts right after the fresh installation and first update to the system.
What happens is with most of the Debian based or Ubuntu based distro's that I've installed I've gotten:
" A start job is running for /dev/disk/by-uuid <number of device>"
It holds up the system at boot time for 1 minute and 30 seconds looking for something (I think a swap partition) and finally times out and the boot resumes.
-::::-This also creates drama with the /etc/fstab file which when compared to the output of blkid 'doesn't match'.-::::-
When that happens I almost always have to do one of 2 things.
Either edit and fix the uuid in the /etc/fstab file with the correct uuid from the output of blkid <or> comment out the whole partition string that doesn't exist from looking at all partitions in gparted.
Which btw, is even harder to fix on a triple booted Linux box.
I am suspicious that this is something that the installer is not getting right during the installation. The installer appears to somehow mis-configure all of the other swap partitions during a regeneration cycle of the other swaps on a rig that has other Linux os installed.
The other issue is boot times after fresh installs that take up to 3 to 5 min's before log in.
Is systemd to blame?
Is this another Nvidia strikes again issue?
Changing the default timeout that's set to 90 seconds sometimes helps and sometimes not.
I've seen folks disable services that were not necessary at boot time and it still hasn't helped.
Is this a hardware issue?
Looking at my signature line you can see I'm not a fan of fixing what's not broken but clearly something here is not right.
Any help, ideas, insight and assistance is greatly appreciated:-
Cheers,
Alex
Last edited: