[SOLVED] A start job is running 1min30sec boot

[Chosneck]

Hello

I've seen this problem before on Mint forum threads as well as on other forums but couldn't find solution for this, my system is looking for some partition that is not there for 1m30s before it starts.
In most threads the solution was changing SWAP partition UUID for the correct one in FSTAB, the problem is i have plain simple partition setup for my Linux installation and there's no SWAP or boot partition, just one NTFS partition i made to read files on both Linux and Windows so i decided to make a new thread.

That's my FSTAB content:

# /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/sda2 during installation
UUID=ef5c6463-47c7-4e86-85c0-3ce2613171c1 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
#UUID=6E88-456F /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
#UUID=1823-9011 /boot/efi vfat defaults 0 1
/dev/disk/by-id/wwn-0x5001b444a7f3a336-part3 /mnt/wwn-0x5001b444a7f3a336-part3 auto nosuid,nodev,nofail,x-gvfs-show 0 0
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=6E88-456F /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
UUID=6E88-456F /boot/efi vfat defaults 0 1

This is what comes up when i boot:


That's my discs, as you can see no SWAP partition just Linux and NTFS for files:

Thanks for help in advance

[Larry78723]

Please post the results of the following command:

Code: Select all

blkid

[Chosneck]

/dev/sda1: UUID="1823-9011" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="54b82f49-f32d-4770-a74e-186d7d3f7045"
/dev/sda2: UUID="ef5c6463-47c7-4e86-85c0-3ce2613171c1" TYPE="ext4" PARTUUID="12253f02-560a-4619-9835-bee452275b5e"
/dev/sda3: UUID="5E2686F979A45CDA" TYPE="ntfs" PTTYPE="dos" PARTUUID="c0f86337-cb58-40d0-909a-93f6e5c81744"
/dev/nvme0n1p1: UUID="0A28-7ECA" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="3820f6c0-1c76-4870-b98b-b41c732dc62a"
/dev/nvme0n1p3: UUID="36B42AE1B42AA37B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="b2f92bd4-5cab-4083-9e1f-13035650d945"
/dev/nvme0n1p4: UUID="8E9CBA2A9CBA0D29" TYPE="ntfs" PARTUUID="37e4abce-8253-4752-9f2b-3b5ae943aa3d"
/dev/nvme0n1p5: UUID="ffbb66c8-2159-4b83-968a-b7d9117191b1" TYPE="ext4" PARTUUID="5f78f95a-f63c-43d2-aba1-21a21a74f13c"
/dev/nvme0n1p6: UUID="52a71998-30d8-4eff-a398-9c002aed56a3" TYPE="ext4" PARTUUID="8e3c5711-401d-410a-b0aa-5855ec6cfbc1"

[Larry78723]

Other than the fact that you have 2 EFI System partitions, neither of which is properly identified in fstab,

FROM blkid:

/dev/sda1: UUID="1823-9011" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="54b82f49-f32d-4770-a74e-186d7d3f7045"
/dev/nvme0n1p1: UUID="0A28-7ECA" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="3820f6c0-1c76-4870-b98b-b41c732dc62a"

FROM fstab:
UUID=6E88-456F /boot/efi vfat defaults 0 1

The problem appears to be this line in fstab:

/dev/disk/by-id/wwn-0x5001b444a7f3a336-part3 /mnt/wwn-0x5001b444a7f3a336-part3 auto nosuid,nodev,nofail,x-gvfs-show 0 0

I'd suggest you determine the UUID for that partition and use that instead of /dev/disk/by-id. Do you want it auto mounted at boot? If not, take auto out of the options.

[Chosneck]

this is my NTFS partition i made to be visible both on Linux and Windows - that's where i store all my files so i decided to put automount on it ant it worked quite well for some time untill it started booting for this long.
I just tried to turn off autoboot and switch it to default settings but that didn't solve the problem.
I know that you can somehow change the time it's waiting for the partition to load where the "nosuid,nodev,nofail,x-gvfs-show" is, maybe that wold be of help.
I just noticed shortcuts i made for the mounted partition doesn't match as well:

That's the setup i've usually used:

Edit: i will just try changing the "identify as" to the correct UUID and report if it worked

[Flemur]

this is my NTFS partition i made to be visible both on Linux and Windows

Here's a line from my /etc/fstab:

Code: Select all

LABEL=BU_NTFS  /mnt/BU_NTFS  ntfs-3g defaults,noauto,noatime,user,rw,utf8,umask=007,uid=1000,gid=1000,windows_names 0 1

Note:
-- the LABEL makes it easy to keep track of, no more messing with UUIDs. Use gparted to give it a label.

-- the noauto makes it not mount until you do it by hand (I made setup so I just type sudo mo *NTFS)
(but if you get things setup properly, you'll be able to mount it at boot and won't need noauto)

-- reduce the timeout from 1.5 minutes to 10s by editing /etc/systemd/system.conf

Code: Select all

#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

Edit: note the windows_names param in the fstab line: that prevents linux from writing illegal filenames (windows can't handle them) to the partition.

[Chosneck]

Just to make sure, you want me to change

/dev/disk/by-id/wwn-0x5001b444a7f3a336-part3 /mnt/wwn-0x5001b444a7f3a336-part3 auto nosuid,nodev,nofail,x-gvfs-show 0 0

to

/dev/disk/by-id/5E2686F979A45CDA /mnt/5E2686F979A45CDA auto nosuid,nodev,nofail,x-gvfs-show 0 0

?
"5E2686F979A45CDA" being the correct UUID

[AndyMH]

No, to

Code: Select all

UUID=5E2686F979A45CDA /mnt/5E2686F979A45CDA auto nosuid,nodev,nofail,x-gvfs-show 0 0

or use the label as suggested by flemur.

This assumes that sda3 is your shared data partition, you have a number of ntfs partitions?

Personally I wouldn't mount it in /mnt, I'd mount it somewhere more useful, like in home, e.g. /home/you/data (you can mount it wherever you want). Create the folder first, and I would use

Code: Select all

UUID=5E2686F979A45CDA /home/you/data  ntfs  uid=1000,gid=1000,defaults,windows_names 0 0

ntfs does not support linux file permissions/attributes, uid=1000,gid=1000 is faking it. windows_names stops linux saving files on the partition with characters in the filename that are invalid in win.

[Chosneck]

this is my NTFS partition i made to be visible both on Linux and Windows

Here's a line from my /etc/fstab:

Code: Select all

LABEL=BU_NTFS  /mnt/BU_NTFS  ntfs-3g defaults,noauto,noatime,user,rw,utf8,umask=007,uid=1000,gid=1000,windows_names 0 1

Note:
-- the LABEL makes it easy to keep track of, no more messing with UUIDs. Use gparted to give it a label.

-- the noauto makes it not mount until you do it by hand (I made setup so I just type sudo mo *NTFS)
(but if you get things setup properly, you'll be able to mount it at boot and won't need noauto)

-- reduce the timeout from 1.5 minutes to 10s by editing /etc/systemd/system.conf

Code: Select all

#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s

Edit: note the windows_names param in the fstab line: that prevents linux from writing illegal filenames (windows can't handle them) to the partition.

Unfortunately reducing timeout in /etc/systemd/system.conf did not work, it's still waiting 90s to boot.
So i can try changing auto in

/dev/disk/by-id/wwn-0x5001b444a7f3a336-part3 /mnt/wwn-0x5001b444a7f3a336-part3 auto nosuid,nodev,nofail,x-gvfs-show 0 0

to noauto? I guess that would make it not to automount the partition i want to be mounted but it can be bypassed by some command on startup i think

[Chosneck]

No, to

Code: Select all

UUID=5E2686F979A45CDA /mnt/5E2686F979A45CDA auto nosuid,nodev,nofail,x-gvfs-show 0 0

or use the label as suggested by flemur.

This assumes that sda3 is your shared data partition, you have a number of ntfs partitions?

Personally I wouldn't mount it in /mnt, I'd mount it somewhere more useful, like in home, e.g. /home/you/data (you can mount it wherever you want). Create the folder first, and I would use

Code: Select all

UUID=5E2686F979A45CDA /home/you/data  ntfs  uid=1000,gid=1000,defaults,windows_names 0 0

ntfs does not support linux file permissions/attributes, uid=1000,gid=1000 is faking it. windows_names stops linux saving files on the partition with characters in the filename that are invalid in win.

Number of ntfs partitions? What do you mean by that?I have only one ntfs partition on this SSD.
I've tried both of your suggested options for boot in fstab and it still gives the same result.

[Chosneck]

No, to

Code: Select all

UUID=5E2686F979A45CDA /mnt/5E2686F979A45CDA auto nosuid,nodev,nofail,x-gvfs-show 0 0

or use the label as suggested by flemur.

This assumes that sda3 is your shared data partition, you have a number of ntfs partitions?

Personally I wouldn't mount it in /mnt, I'd mount it somewhere more useful, like in home, e.g. /home/you/data (you can mount it wherever you want). Create the folder first, and I would use

Code: Select all

UUID=5E2686F979A45CDA /home/you/data  ntfs  uid=1000,gid=1000,defaults,windows_names 0 0

ntfs does not support linux file permissions/attributes, uid=1000,gid=1000 is faking it. windows_names stops linux saving files on the partition with characters in the filename that are invalid in win.

You wanted me to change

/dev/disk/by-id/wwn-0x5001b444a7f3a336-part3 /mnt/wwn-0x5001b444a7f3a336-part3 auto nosuid,nodev,nofail,x-gvfs-show 0 0

to

UUID=5E2686F979A45CDA /home/ml/data ntfs uid=1000,gid=1000,defaults,windows_names 0 0

which is what i did.


But i can see during the boot it has problem with the

UUID=6E88-456F /boot/efi vfat defaults 0 1

which is line just before (and it's UUID is non present anywhere in disks):

# /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/sda2 during installation
UUID=ef5c6463-47c7-4e86-85c0-3ce2613171c1 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
#UUID=6E88-456F /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=6E88-456F /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
UUID=6E88-456F /boot/efi vfat defaults 0 1
UUID=5E2686F979A45CDA /home/ml/data ntfs uid=1000,gid=1000,defaults,windows_names 0 0

[AndyMH]

You have two EFI partitions, one on sda and the other on your nvme drive.

The UUID for sda1 is 1823-9011, the UUID for nvme0n1p1 is 0A28-7ECA. One of those is the right answer. You currently have 6E88-456F, Larry picked this up earlier, I didn't spot it. That is the problem (the modifications to fstab for your shared data partition are still better than what you had).

As you have ext4 partitions on both drives, not easy to tell which one is correct - which drive is mint booting from?

Boot into mint, open a terminal and df. You are looking for the partition mounted as /, e.g.

Code: Select all

andy@T432 ~ $ df
df: /run/user/1000/doc: Operation not permitted
Filesystem                  1K-blocks       Used Available Use% Mounted on
udev                          7986192          0   7986192   0% /dev
tmpfs                         1606720       3388   1603332   1% /run
/dev/sdc1                    32549628   24524868   6348272  80% /   <<<<<<

This is not conclusive, you should mount both sda1 and nvme0n1p1 (you can do this with disks) and have a look at the contents. You should see an EFI folder and then inside that folder, folders for windows and ubuntu. That should be your EFI partition.

[Chosneck]

Yes, i just realised the problem with 90 second boot started happening after installed Linux Mint in the internal drive next to Windows (i did it because that's the only way i found to install GRUB on internal drive along Windows) and booted my SSD Linux from internal drive GRUB instead of the default one.
Now no matter which GRUB (internal, or default SSD one) i use i have the same 90s problem.

ml@ml:~$ df
df: /run/user/1000/doc: Operation not permitted
Filesystem 1K-blocks Used Available Use% Mounted on
udev 12190532 0 12190532 0% /dev
tmpfs 2447460 1944 2445516 1% /run
/dev/sda2 362176524 227120760 116588488 67% /
tmpfs 12237284 103120 12134164 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
tmpfs 12237284 0 12237284 0% /sys/fs/cgroup
/dev/sda3 607217660 273245572 333972088 45% /home/ml/data
tmpfs 2447456 112 2447344 1% /run/user/1000

sda2 partition is ext4 and is part of my SSD disk which im trying to boot from and in disks shows UUID ef5c6463-47c7-4e86-85c0-3ce2613171c1.

So if i change in my fstab in 3 places from

# /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/sda2 during installation
UUID=ef5c6463-47c7-4e86-85c0-3ce2613171c1 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
#UUID=6E88-456F /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=6E88-456F /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
UUID=6E88-456F /boot/efi vfat defaults 0 1
UUID=5E2686F979A45CDA /home/ml/data ntfs uid=1000,gid=1000,defaults,windows_names 0 0

to

# /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/sda2 during installation
UUID=ef5c6463-47c7-4e86-85c0-3ce2613171c1 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
#UUID ef5c6463-47c7-4e86-85c0-3ce2613171c1 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID ef5c6463-47c7-4e86-85c0-3ce2613171c1 /boot/efi vfat defaults 0 1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
UUID ef5c6463-47c7-4e86-85c0-3ce2613171c1 /boot/efi vfat defaults 0 1
UUID=5E2686F979A45CDA /home/ml/data ntfs uid=1000,gid=1000,defaults,windows_names 0 0

it should work?
Should i give it a try?

Edit: I noticed you told me to use sda1 UUID which is FAT instead of sda2 which is my ext4 partition. Should i change it to sda1 UUID instead then?

[AndyMH]

So if i change in my fstab in 3 places from

No, that will probably be a good way of borking your system.

Edit: I noticed you told me to use sda1 UUID which is FAT instead of sda2 which is my ext4 partition. Should i change it to sda1 UUID instead then?

No (and I'll leave it to others to correct, not an expert in UEFI boot). When you boot in UEFI mode, the firmware (BIOS in old-speak) in your PC looks for EFI partition(s). It knows what is an EFI partition because it is formatted fat32 and has the flags esp & boot set. It reads the contents looking for bootloaders, e.g. grub. If it finds a bootloader that is top of the boot list it will load and run it. For linux, grub then looks for your / partition (using the UUID) and continues the boot process from that (like loading the kernel and passing control to it). A long winded way of saying that what gets mounted at /boot/efi is your EFI partition, sda1.

Probably time to wind back to what are you trying to achieve? Because it sounds like you have tried to install mint to your nvme drive as well as to sda?

On the basis that that is what you have done...

Have a look inside your EFI partitions and report what you find. This tells you how to mount them using disks:
viewtopic.php?p=2126026#p2126026

Also look in BIOS, do you have two entries in your boot list for 'ubuntu' - one for mint on sda and one for the nvme drive?

You could just change the UUID in fstab to point at one of the EFI partitions, and see if it works but I'd rather try and find out which EFI partition is pointing at which mint install.

More info - you can use code markers to make terminal output easier to read instead of using quotes:
viewtopic.php?f=42&t=364929&p=2119362&h ... l#p2119362

[Chosneck]

Probably time to wind back to what are you trying to achieve? Because it sounds like you have tried to install mint to your nvme drive as well as to sda?

On the basis that that is what you have done...

Yes, i already had Linux that i use on daily basis installed on SSD but as i wrote before i recently installed Linux in the internal drive along Windows as well so that i could have working GRUB and could launch Windows after detaching my SSD which is where my GRUB was installed by default.

This is what i found in EFI partitions.
SSD:

Internal drive:

You could just change the UUID in fstab to point at one of the EFI partitions, and see if it works but I'd rather try and find out which EFI partition is pointing at which mint install.

That's what i asked if i can do and i thought you said it could bork my system so i'm a bit confused now.

[Flemur]

[Unfortunately reducing timeout in /etc/systemd/system.conf did not work, it's still waiting 90s to boot.

It always works for me; I do that mod on every install.

[AndyMH]

That's what i asked if i can do and i thought you said it could bork my system so i'm a bit confused now.

This may have started as 'why is the system hanging for 90s', but I'm trying to sort out which EFI partition is booting what before you make any changes to fstab.

Top of your BIOS boot list is ubuntu (intel SSDPEKNW512GB) - I assume this is your nvme drive? But it appears to be booting mint off your external drive, not your nvme drive, from your previous output of df:

Code: Select all

/dev/sda2 362176524 227120760 116588488 67% /

This suggests that if you installed mint to the external drive after you had installed mint to the nvme drive, it has overwritten grub on the nvme drive.

What happens if you boot from the last entry in the BIOS boot list ubuntu(SanDiskPortable SSD). I would either expect it to hang or if it boots, run df again and look for the line showing what is mounted as /. I would expect it to show the same as above:

Code: Select all

/dev/sda2 362176524 227120760 116588488 67% /

This is what i found in EFI partitions.

In your file manager you need to double click on the EFI folder to see what is inside. On your nvme drive I'm expecting a boot, windows and ubuntu folder, in the EFI folder on the external drive probably just a boot and ubuntu folder, or maybe empty.

[Chosneck]

Top of your BIOS boot list is ubuntu (intel SSDPEKNW512GB) - I assume this is your nvme drive? But it appears to be booting mint off your external drive, not your nvme drive, from your previous output of

Normally i open boot menu and choose my Linux on SSD with arrows which was installed before i installed Linux on internal drive.
It is booting internal nvme drive Mint as default as planned as a workaround so i could access Windows without errors and be able to access my SSD after detaching and attaching it again.(normally Windows would load it's own bootloader or show Grub 2.0 error)

What happens if you boot from the last entry in the BIOS boot list ubuntu(SanDiskPortable SSD). I would either expect it to hang or if it boots, run df again and look for the line showing what is mounted as /. I would expect it to show the same as above:

That's the Linux i'm always booting which has the booting problem, indeed df gives the same results.

In your file manager you need to double click on the EFI folder to see what is inside. On your nvme drive I'm expecting a boot, windows and ubuntu folder, in the EFI folder on the external drive probably just a boot and ubuntu folder, or maybe empty.

Sorry, it should be correct now.
SSD:

Internal drive (nvme):

[AndyMH]

Then back to your original question, change the line

Code: Select all

UUID=6E88-456F /boot/efi vfat defaults 0 1

to

Code: Select all

UUID=1823-9011 /boot/efi vfat defaults 0 1

in fstab.
that is the UUID for your EFI partition on sda.

[Chosneck]

Just to make sure so i don't brick my system, you want me to replace the last line or all 3 of them containing 456F?:

Code: Select all

#UUID=6E88-456F  /boot/efi       vfat    umask=0077      0       1

Code: Select all

#UUID=6E88-456F  /boot/efi       vfat    defaults      0       1

Code: Select all

UUID=6E88-456F  /boot/efi       vfat    defaults      0       1

If i replace all of them it will look like this:

Code: Select all

# /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/sda2 during installation
UUID=ef5c6463-47c7-4e86-85c0-3ce2613171c1 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
#UUID=1823-9011 /boot/efi vfat defaults 0 1
/swapfile                                 none            swap    sw              0       0
#UUID=1823-9011  /boot/efi       vfat    defaults      0       1
#UUID=1823-9011  /boot/efi       vfat    defaults      0       1
#UUID=1823-9011  /boot/efi       vfat    defaults      0       1
#UUID=1823-9011 /boot/efi vfat defaults 0 1
#UUID=1823-9011  /boot/efi       vfat    defaults      0       1
UUID=1823-9011 /boot/efi vfat defaults 0 1
UUID=5E2686F979A45CDA /home/ml/data  ntfs  uid=1000,gid=1000,defaults,windows_names 0 0

Is that correct?