OP
skywalker00
Member
Obviously when I look for etc/ftsab the line cryptoswap has been removed
When I start my OS it takes long
- Thread starter skywalker00
- Start date
Can you provide a new boot journal and upload it again so that I can see anything different in it this time?
OP
skywalker00
Member
Untitled - L-T Paste
Paste can store text, source code or sensitive data for a set period of time.
paste.linux-tips.us
Thanks! Can you make a picture of what exactly you are seeing now what there is job running waiting to finish?
OP
skywalker00
Member
Still looks like the same job, can you try the following for me when your system is booted.
1. Open a terminal.
2. Run the following: sudo systemctl daemon-reload
3. Then reboot. What happens now, does is the start job still there during boot?
1. Open a terminal.
2. Run the following: sudo systemctl daemon-reload
3. Then reboot. What happens now, does is the start job still there during boot?
Condobloke
Well-Known Member
Are you certain it saved properly ?
OP
skywalker00
Member
Same job
OP
skywalker00
Member
Yes, thanks.
I'm having a hard time reading the journal because it cuts off near the end of each line.
Looks like it's still trying to decrypt something. When booted into your PopOS installation again, can you share the output of the following?
Code:
Aug 15 19:37:55 pop-os systemd[1]: Condition check resulted in Dispatch Passwor>
Aug 15 19:37:55 pop-os systemd[1]: Condition check resulted in Set Up Additiona>
Aug 15 19:37:55 pop-os systemd[1]: Condition check resulted in Store a System T>
Aug 15 19:37:55 pop-os systemd[1]: Condition check resulted in Rebuild Hardware>
Aug 15 19:37:55 pop-os systemd[1]: Condition check resulted in Commit a transie>
Aug 15 19:37:55 pop-os systemd[1]: Condition check resulted in Platform Persist>
Aug 15 19:38:00 pop-os systemd[1]: systemd-rfkill.service: Succeeded.
Aug 15 19:39:24 pop-os systemd[1]: dev-disk-by\x2duuid-fce8af9e\x2da3c3\x2d49e8>
Aug 15 19:39:24 pop-os systemd[1]: Timed out waiting for device /dev/disk/by-uu>
Aug 15 19:39:24 pop-os systemd[1]: Dependency failed for Cryptography Setup for>
Aug 15 19:39:24 pop-os systemd[1]: Dependency failed for Local Encrypted Volume>
Aug 15 19:39:24 pop-os systemd[1]: cryptsetup.target: Job cryptsetup.target/sta>
Aug 15 19:39:24 pop-os systemd[1]: [email protected]: Job sy>
Aug 15 19:39:24 pop-os systemd[1]: dev-disk-by\x2duuid-fce8af9e\x2da3c3\x2d49e8>
Aug 15 19:39:24 pop-os systemd[1]: Reached target Block Device Preparation for >
Code:
cat /etc/fstab
lsblk
sudo cat /etc/crypttab
OP
skywalker00
Member
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
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 498M 0 part /boot/efi
├─nvme0n1p2 259:2 0 4G 0 part /recovery
├─nvme0n1p3 259:3 0 465.7G 0 part /
├─nvme0n1p4 259:4 0 16M 0 part
└─nvme0n1p5 259:5 0 461.3G 0 part
[sudo] password for dom:
cryptswap UUID=fce8af9e-a3c3-49e8-972b-aaa64141a80d /dev/urandom swap,plain,offset=1024,cipher=aes-xts-plain64,size=512Pastebin doesn't let me upload more than a certain amount of Kbps
Can you do the following.
1. sudo gedit /etc/crypttab
2. Change this line: ( in short add a # at the front of the line)
4. Then run: sudo systemctl daemon-reload
5. Reboot and see if your system starts now without having to wait for a start job?
1. sudo gedit /etc/crypttab
2. Change this line: ( in short add a # at the front of the line)
3. Click save
4. Then run: sudo systemctl daemon-reload
5. Reboot and see if your system starts now without having to wait for a start job?
OP
skywalker00
Member
Done. Works.
OP
skywalker00
Member
well done really!
Would you mind to suggest me a book to understand linux better
Would you mind to suggest me a book to understand linux better
You can remove the line fully now from /etc/crypttab, so remove this line now.
You could start here and if you want a book you I would start with this because that author has a good and fun way of explaining things. I think that should get you started in understanding the basics and then you should be able to start to find your own way from there. Also have a look here as it may have some useful information.
linux.org
Lastly it's mostly about hands on experience that you learn GNU/Linux and a little bit about knowing how it works.
Adding a # to the front of a line disables it, making it a comment. The problems was that in your /etc/fstab /dev/mapper/cryptswap was causing systemd to to try and activate it during boot, /etc/crypttab makes systemd try to decrypt it first. So what was happening was that we had removed the /etc/fstab entry and then the /etc/crypttab entry was still trying to decrypt it. So now that we have disabled the entry by making it a comment systemd doesn't try to decrypt it anymore and you don't see a hanging startup job.
You could start here and if you want a book you I would start with this because that author has a good and fun way of explaining things. I think that should get you started in understanding the basics and then you should be able to start to find your own way from there. Also have a look here as it may have some useful information.
NEW TO LINUX? THIS IS A MUST READ
Good reads for prospective Linux Users. https://www.linux.com/what-is-linux http://linux.oneandoneis2.org/LNW.htm
linux.org
Lastly it's mostly about hands on experience that you learn GNU/Linux and a little bit about knowing how it works.
OP
skywalker00
Member
Oh interesting I will then thanks
I did type sudo /etc/crypttab in the terminal so I deleted the line I previously disabled and saved
I restarted the computer and it is still booting.. 8 mins minumum
thanks I did type sudo /etc/crypttab in the terminal so I deleted the line I previously disabled and saved
I restarted the computer and it is still booting.. 8 mins minumum
OP
skywalker00
Member
Looks more like a kernel thing, then problem of remove that line. Press the power button until your computer turns off and then turn it back on again. What happens then?
OP
skywalker00
Member
now it booted normally
OP
skywalker00
Member
doesn't sound an exact science anymore lol
