No more message and the restart doesn’t give anymore info either. Always the same message in the journal to which is the same in the status of the process. « Cannot read journal data »
But did you intentionally activate hibernate capabilities on your system?
Since there a resume paramater on your command args. As long as I understand the resume args is uses for pointing to boot to last stored session and this stored session usually on swap partition—disk partition and not zram things on RAM.
If the resume parameter pointing to wrong partition or pointing to zram things on RAM (that the stored session gone on power off) it could give an error messages on ABRT.
But I’m not sure with your case. Since I mentioned before that I don’t have experiences with LVM and RAID.
No it was at installation by default on fedora server installation.
So i’m not even sure why they are putting it by default
And i still don’t see the link with the cannot read logs error. You are focusing on the general fact that the service stop immediately and not the error message
In case you want to take a time for troubleshooting, you could temporarily change boot command args and this change will back to previous state when it’s reboot.
For a test, if you never did it before below are safest task to temporary remove Fedora loading screen on on boot and show running task by systemd.
When you are presented with boot list on start up, press e on keyboard on one of any boot list presented.
You’ll get some text. Find word rhgb and remove this rhgb only word.
After that read at the very end line on your screen. It’s should mention to continue the boot by pressing CTRL+x.
After that Fedora loading screen will gone and your display will show list of tasks by systemd.
After you login and reboot you pc, your Fedora loading screen should be back again and rhgb parameter will present again.
If you comfortable with above method you could do the same by removing resume=/dev/mapper/fedora-swap and try to booting with above steps.
If your ABRT warning messages not present again by removing resume=/dev/mapper/fedora-swap, you could make it permanent with:
# Open with text editor with sudo
$ sudo nano /etc/default/grub
# Find and delete `resume=/dev/mapper/fedora-swap` part
# Save it with ctrl + x if you're using `nano` editor
# Update your grub
# For legacy bios system
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
# For UEFI bios
$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Be careful with this advice!
For fedora 33 and earlier this is correct for an efi booting system.
For fedora 34 and later the command should be one of:
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
or
$ sudo grub2-mkconfig -o /etc/grub2.cfg
or
$ sudo grub2-mkconfig -o /etc/grub2-efi.cfg
All 3 commands have exactly the same effect regardless of whether booting in legacy mode or efi mode. Fedora 34 and later use a standard grub.cfg location.
I read about proposal to changes the grub.cfg path like what you mentioned, but from official doc for Fedora 34 & 35 my terminal command still relevant.