When I start my OS it takes long



It seems to be missing a lot, can you run this on your system.
Code:
journalctl -b > lastboot.txt
Then upload the contents of lastboot.txt to pastebin.
 
Sorry for the late answer,
I did copy and paste the code above but nothing came out ....
 
Can't see what's happening if your boot journal is empty. What do you get when you just run.
Code:
journalctl -b
What previously posted is only part of the boot journal but not everything.
 
Last edited:
I did copy and paste the code above but nothing came out ....

Nothing would come out. It should make a .txt file of that name and it should be in the directory where you ran the command, probably in the ~/ directory.
 
This is what comes out after the code
Code:
journalctl -b

 
That's better, I find it strange though when uploading it to pastebin it only showed part of the boot journal. The problem is here.
Aug 13 17:11:35 pop-os systemd[1]: dev-disk-by\x2duuid-fce8af9e\x2da3c3\x2d49e8\x2d972b\x2daaa64141a80d.device: Job dev-disk-by\x2duuid-fce8af9e\x2da3c3\x2d49e8\x2d972b\x2daaa64141a80d.devi>
Aug 13 17:11:35 pop-os systemd[1]: Timed out waiting for device /dev/disk/by-uuid/fce8af9e-a3c3-49e8-972b-aaa64141a80d.
Aug 13 17:11:35 pop-os systemd[1]: Dependency failed for Cryptography Setup for cryptswap.
Aug 13 17:11:35 pop-os systemd[1]: Dependency failed for /dev/mapper/cryptswap.
Aug 13 17:11:35 pop-os systemd[1]: Dependency failed for /dev/mapper/cryptswap.
Aug 13 17:11:35 pop-os systemd[1]: Dependency failed for Swap.
Aug 13 17:11:35 pop-os systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Aug 13 17:11:35 pop-os systemd[1]: dev-mapper-cryptswap.swap: Job dev-mapper-cryptswap.swap/start failed with result 'dependency'.
Aug 13 17:11:35 pop-os systemd[1]: dev-mapper-cryptswap.device: Job dev-mapper-cryptswap.device/start failed with result 'dependency'.
Aug 13 17:11:35 pop-os systemd[1]: Dependency failed for Local Encrypted Volumes.
Aug 13 17:11:35 pop-os systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Aug 13 17:11:35 pop-os systemd[1]: [email protected]: Job [email protected]/start failed with result 'dependency'.
Aug 13 17:11:35 pop-os systemd[1]: dev-disk-by\x2duuid-fce8af9e\x2da3c3\x2d49e8\x2d972b\x2daaa64141a80d.device: Job dev-disk-by\x2duuid-fce8af9e\x2da3c3\x2d49e8\x2d972b\x2daaa64141a80d.devi>
Aug 13 17:11:35 pop-os systemd[1]: Reached target Block Device Preparation for /dev/mapper/cryptswap.
Your fstab looks like this.
Code:
# /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>
PARTUUID=a79a0c20-9963-492f-8a8b-58d1002bedf4  /boot/efi  vfat  umask=0077  0  0
PARTUUID=910dfb52-5050-434a-bc0a-ff70fe8e6f45  /recovery  vfat  umask=0077  0  0
UUID=54136094-c1b5-4b6b-9444-b1bd7628a047  /  ext4  noatime,errors=remount-ro  0  0
/dev/mapper/cryptswap  none  swap  defaults  0  0
/etc/fstab (END)
And your actual devices look like this.
/dev/nvme0n1p3: UUID="54136094-c1b5-4b6b-9444-b1bd7628a047" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a2282d77-100c-4397-9093-aa55d45d4b55"
/dev/nvme0n1p1: UUID="0EB8-4A70" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="a79a0c20-9963-492f-8a8b-58d1002bedf4"
/dev/nvme0n1p2: UUID="0EB8-4FA6" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="recovery" PARTUUID="910dfb52-5050-434a-bc0a-ff70fe8e6f45"
/dev/nvme0n1p4: PARTLABEL="Microsoft reserved partition" PARTUUID="c27e74b9-17c0-4fc6-9bcb-efb3de759c49"
/dev/nvme0n1p5: BLOCK_SIZE="512" UUID="00007013007011C0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="b7b6d4fc-b873-40b2-b41f-af6f24171a78"
So you have an entry in your fstab that doesn't exist, so systemd waits for it until it gets a time-out and the continues to finish booting your system. Try adding a # in front of the following line so that it then looks like this.
Code:
#/dev/mapper/cryptswap  none  swap  defaults  0  0
Then reboot your system, this time I would expect it to boot normally without needing to wait for your swap to be activated and getting a time-out.
 
Last edited:
I was at work, sorry.

Pastebin didn't let me upload the data, it asks for the premium account after a certain limit...


Anyway I pasted the code above, still the same
Furthermore, I can give you another information which I don't know if it is related with the issue.
As I wrote earlier, I have dual boot system, but for some reason before I boot up if I press F12 my boot options come out, and these are not just pop os and windows, but a third option come out with the name of the ssd and if I choose that one I get into Pop os, and it is exactly as if I had chosen the Pop os option.
 
The screenshot you shared in your original post shows a job hanging, your boot journal points out that cryptswap is the problem. Can you share what your /etc/fstab looks like now?
 
Code:
# /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>
PARTUUID=a79a0c20-9963-492f-8a8b-58d1002bedf4  /boot/efi  vfat  umask=0077  0  0
PARTUUID=910dfb52-5050-434a-bc0a-ff70fe8e6f45  /recovery  vfat  umask=0077  0  0
UUID=54136094-c1b5-4b6b-9444-b1bd7628a047  /  ext4  noatime,errors=remount-ro  0  0
/dev/mapper/cryptswap  none  swap  defaults  0  0




^G Help          ^O Write Out     ^W Where Is      ^K Cut           ^T Execute       ^C Location      M-U Undo         M-A Set Mark     M-] To Bracket   M-Q Previous     ^B Back
^X Exit          ^R Read File     ^\ Replace       ^U Paste         ^J Justify       ^_ Go To Line    M-E Redo         M-6 Copy         ^Q Where Was     M-W Next         ^F Forward
 
1. Remove this line and save the file: /dev/mapper/cryptswap none swap defaults 0 0
2. Reboot to see if your system now boots normally without waiting for a job to finish.
And can you share the output of the following.
Code:
lsblk
 
1. Remove this line and save the file: /dev/mapper/cryptswap none swap defaults 0 0
2. Reboot to see if your system now boots normally without waiting for a job to finish.
And can you share the output of the following.
Code:
lsblk
I don't understand what "remove this line means", my bad.
 
1. Open this file with your favorite text editor with escalated privileges(sudo): /etc/fstab
2. Delete this line: /dev/mapper/cryptswap none swap defaults 0 0
3. Reboot your system and this time it should boot without having to wait for a job to finish.
 
When I open /etc/fstab in the terminal I delete/remove the line but I can't save the file in the terminal....
 
There are a few codes at the bottom of the tab in the terminal.... but I should open the file in the text editor.... that's what I don't know how to do
 
1. sudo gedit /etc/fstab
2. Remove the line: /dev/mapper/cryptswap none swap defaults 0 0
3. Click on save and exit gedit.
4. Reboot your system and now it should boot without having to wait for a start job during boot.
 


Top