[SOLVED] After unclean shutdown I get orphaned inodes

AngelBePro · 2024-07-12 20:10:20

After let's say a power outage or I hold down the power button for a forced shutdown, when I launch into Arch I get a kernel panic with this:

9.7287031 EXT4-fs error (device numein1p3): ext4_mark_recovery_complete:6243: comm mount: Orphan file not empty on read-only fs.

I did a fsck but that didn't do anything.

My temporary workaround for this problem is just forcefully shutting down the PC again and starting it again

Last edited by AngelBePro (2024-07-13 09:59:38)

seth · 2024-07-12 21:08:32

"numein1p3" - "nvme0n1p3"
You probably also got "write access unavailable, skipping orphan cleanup", the more interesting question is why the partition is tried to be mounted read-only, ie. in doubt the logs *before* that line.

AngelBePro · 2024-07-12 22:02:40

I got only this line from the log by pressing enter after the kernel panic https://i.imgur.com/4uEXg5i.jpg. I'm not sure how to retrieve a log since using journalctl -b -1 shows only last successful boot, which is understandable since the fs is read-only and log can't be saved. How am I meant to retrieve more debug info. just in case these are my kernel launch parameters:

GRUB_DEFAULT="saved"
GRUB_TIMEOUT="3"
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/nvme0n1p2 quiet splash loglevel=3 nvidia-drm.modeset=1 nvidia_drm.fbdev=1"
GRUB_CMDLINE_LINUX=""

Last edited by AngelBePro (2024-07-12 22:06:35)

seth · 2024-07-12 22:20:14

remove quiet and splash - the kernel panic itself (ie, why do we enter the emergency target) is certainly more relevant and interesting than that the FS can't clean up when mounted ro in the emergency target.

AngelBePro · 2024-07-13 09:35:46

Well after trying to change the default grub kernel parameters, nothing changed and I decided to opened the /boot/grub/grub.cfg to see what happened after using grub-mkconfig. Only thing that changed after that command was the Advanced options boot entries. When I opened grub customizer, I noticed that the script was custom instead of linux. In the deleted entries tab I saw the original boot entry. The difference between the main and the custom one (~~which I didn't make but was probably created by a theme for grub script~~ Which I created so it says loading Linux instead of loading linux linux-zen) was that the custom one had ro

linux	/vmlinuz-linux-zen root=UUID=7b447a03-5a42-441e-ac42-40eb2dbba923 rw ro resume=/dev/nvme0n1p2 quiet splash loglevel=3 nvidia-drm.modeset=1 nvidia_drm.fbdev=1

Last edited by AngelBePro (2024-07-13 09:54:33)

AngelBePro · 2024-07-13 09:59:14

I changed to the linux (grub-created) boot entry which didn't have ro, which fixed the issue, since now the filesystem was being repaired. The grub created boot entry also changes based on the grub-mkconfig command. Marking this as solved.

Arch Linux

#1 2024-07-12 20:10:20

[SOLVED] After unclean shutdown I get orphaned inodes

#2 2024-07-12 21:08:32

Re: [SOLVED] After unclean shutdown I get orphaned inodes

#3 2024-07-12 22:02:40

Re: [SOLVED] After unclean shutdown I get orphaned inodes

#4 2024-07-12 22:20:14

Re: [SOLVED] After unclean shutdown I get orphaned inodes

#5 2024-07-13 09:35:46

Re: [SOLVED] After unclean shutdown I get orphaned inodes

#6 2024-07-13 09:59:14

Re: [SOLVED] After unclean shutdown I get orphaned inodes

Board footer