Swap causing very slow boot (and systemd says the swap partition became active after 500k years)
Swap causing very slow boot (and systemd says the swap partition became active after 500k years)
cross-posted from: https://lemmy.world/post/13313385
I'm dualbooting Fedora Kinoite (ublue-nvidia image) with Windows 11 and I have a boot time of over 1 minute (only on the Fedora side).
The output of
systemd-analyze critical-chainis:└─sddm.service @16.435s └─plymouth-quit.service @16.315s +107ms └─systemd-user-sessions.service @16.299s +12ms └─remote-fs.target @16.298s └─remote-fs-pre.target @16.298s └─nfs-client.target @16.298s └─gssproxy.service @16.288s +9ms └─network.target @16.285s └─wpa_supplicant.service @16.281s +4ms └─basic.target @14.798s └─dbus-broker.service @14.774s +22ms └─dbus.socket @14.760s └─sysinit.target @14.757s └─systemd-resolved.service @14.696s +61ms └─systemd-tmpfiles-setup.service @14.584s +96ms └─local-fs.target @14.569s └─run-user-1000-doc.mount @23.123s └─run-user-1000.mount @22.463s └─swap.target @1.410s └─dev-disk-by\x2duuid-819f25f8\x2daf77\x2d4d7b\x2daaf7\x2dadb07819a7b1.swap @1.276s +35ms └─dev-disk-by\x2duuid-819f25f8\x2daf77\x2d4d7b\x2daaf7\x2dadb07819a7b1.device @584542y 2w 2d 20h 46.792s +1min 3.997sFirst of all, I would like to know what the hell is going on with that 584542 years active time lol
Anyway, the
x2dadb07819a7b1UUID belongs to the swap partition.Output of
lsblk -f:NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS zram0 [SWAP] nvme0n1 ├─nvme0n1p1 vfat FAT32 EFI AAFB-90EA 553.6M 7% /boot/efi ├─nvme0n1p2 ext4 1.0 fedora-boot a1457f7b-c1fb-40da-9c6f-98356d9003e2 526.8M 39% /boot ├─nvme0n1p3 ext4 1.0 fedora-root 0e748e63-f5f5-42f1-babd-818054eb9ee5 40.8G 35% /var │ /sysroot/ostree/deploy/fedora/var │ /usr │ /etc │ / │ /sysroot ├─nvme0n1p4 swap 1 fedora-swap 819f25f8-af77-4d7b-aaf7-adb07819a7b1 [SWAP] ├─nvme0n1p5 crypto_LUKS 2 ea073ead-906c-4127-9555-efba204baabf │ └─luks-ea073ead-906c-4127-9555-efba204baabf ext4 1.0 fedora-home e37f299a-84f5-46ce-976c-507b8e8e25f8 1T 1% /var/home ├─nvme0n1p6 ntfs Extra 74FE8F25FE8EDF2C ├─nvme0n1p7 ├─nvme0n1p8 BitLocker 2 └─nvme0n1p9 ntfs C02807922807869EWhat should I do?
if you have zram enabled why do you have a swap partion on your ssd at all?
How much ram do you have?
if you have enough RAM, you only really need swap if you want to hybernate. i'm running without swap for >10 years now. the only times regular users hit OOM is when a weird error happens and in that case you want it to be OOM killed quickly instead of your system becoming super slow while it tries to swap gigabytes of what the broken program is allocating.
Just because it's worked for you doesn't mean it's the best option.
It’s an odd situation anyway since Fedora has used zram swap for a while.
I might actually end up disabling swap in the end. I wanted to update that apparently I “fixed” the problem (not sure if permanently) by turning off the pc, unplugging the PSU, and holding down the power button for 30 seconds. Normal reboots weren’t enough. I’ll take it for now.
Is this a known good partition layout for Kinoite? Both it and Silverblue have warnings about dual booting and manual partitioning because anaconda will happily accept a partition layout that is not actually compatible.
https://docs.fedoraproject.org/en-US/fedora-kinoite/installation/#known-limitations
swapoff, reformat, swapon?
Also make sure the drive isn't dying.
Could you upload the output of
systemd-analyze plot?Hopefully people with more of a clue than me will chime in... Meanwhile, my best swag is the filesystem had issues and had to do an fsck? If that's the case it would boot quickly next time assuming a clean shutdown.
Were there any errors during boot?
Fastboot enabled in BIOS or no? (Not sure if this has anything to do with anything I'm just trying to look useful)
PS: the weird active time could maybe somehow be related to the filesystem being borked needing fsck? I'm not sure.
Have you tried installing Linux? That usually fixes all my problems