Increased reports since 6.15.3 of corruption within the log tree
Seems like a btrfs bug. Bunch of links in that thread with similar reports and screenshots. They also include the suggested fix.
Increased reports since 6.15.3 of corruption within the log tree
Seems like a btrfs bug. Bunch of links in that thread with similar reports and screenshots. They also include the suggested fix.
Thank, I will look at it!
Glad to see you got it fixed. Just out of curiousity, when was your last update before today and what kernel version were you on pre and post update?
Hi, I update today when I just wake up(it is my routine at this point). I am using Linux 6.15.8-zen1-1-zen. My kernel is the same pre/post because there isn't kernel update today.
Interesting. So it's still an issue on latest stable kernel but we don't know what the exact cause is.
I guess this is the fun of living on the bleeding edge side.
I wouldn't call Fedora bleeding edge and they were also affected.
I hate these Grub/boot errors. They are a pain to fix, not that it is hard, but I always have to read-up on how to do it properly. I am guessing you probably did an update maybe that caused this? Do you have a backup system to restore? That is the easiest fix. If not, next time get one in place. Here is a helpful 'how to fix' the issue.
You've got this! 👍
The I will take a look!
Not grub; that is a systemd error shell due to a failed mount (probably because the value in /etc/fstab is wrong)
I did a system update today and it deleted my entry in the UEFI Boot Manager so I had to manually re-add it.
I wonder if these are related. e: I also use Arch
What did you do before the reboot?
Surprisingly nothing. I mean I did do update with pacman -Syu today, but I did reboot after that and my system work fine. After the I reboot the second time and now my fstab disappears.
First
lsblk to get the list of block devices (you can use size to figure out your file system)
Then: mount -o remount,rw /dev/${name found in previous step} /
Then check for bad entries in your /etc/fstab and fix them
Then check for failed services: systemctl —failed
Then you should be able to:
systemctl set-default graphical.target to boot
Sorry,but I don't have lsblk for some reason.
How about blkid?
Yes I do have it.
Ok notice the uuids, then look in your /etc/fstab file to see if they match
This is the painful part I don't know why my fstab is nuked. It is completely empty. I am writing it rn and it is painful. I have a question to ask tho. After I finish writing it what do I do? Do I reboot?
Edit: Okay after I finish the fstab I do mount -a it did not work. ;). I am not sure if what I did is good though. I just copy fstab of a new installation of arch on my laptop and change the UUID
You don’t need to use the uuid for /etc/fstab (which should make it much easier)
You don’t need to reboot just set the run level via: systemctl set-default graphical.target
Sure, thankyou!
But you will want to clear out the failed systemd services first to ensure that you can boot.
systemctl --failed will list what failed
After you make your /etc/fstab
systemctl daemon-reload will regenerate the units files in /run/systemd/generator but doesn't start new automounts or stop ones removed from fstab.
systemctl start newmount.automount will start the mount. The .automount extension is required, as systemd assumes .service if not extension is specified.
systemctl stop oldmount.automount will remove a mount not longer in fstab
systemctl reset-failed will stop a previously failed removed mount from appearing in status messages
Ty, I fixed it. Turn out the issue was related to btrfs issue with newer kernel version.
Well done, happy to hear that you managed to fix it.
Ty!
can you post the config from /etc/fstab
If you have a usb with another distro (not arch) you can plug it in and boot into the live environment. Then from there you can look at the filesystem on your other drives. Or you can do it from the emergency shell whichever you prefer.
I checked my fstab to painfully found out that it is somehow empty. I am starting to losing my hope lol.
thats fine you can write a new one. Check the output of blkid or some command that lists drives. Then take a look at an example fstab config and copy it. If you can install genfstab from github that would be nice but idk if that cna be done from emergency shell.
After fstabs rebuilt try restarting
Hi, sorry to bother you again. I did rewrite my fstab but after that I reboot and it is still the same and the fstab is still empty. Am I doing something wrong?
Okay I will try. Thanks you!!!!
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0