ext4-fs error device sda1_find_entry:1454: inode #50202085:comm (e-config): reading directory lblock 0
Consistent results resuming from hibernate (not suspend). System goes to terminal mode with repeating errors. Error messages vary but the first listed is the ext4-fs error. Happened since upgrade from 16.04 2 months ago. sysrq (reisub) only option to reboot. Logs have multiple ACPI IO errors and suggest to not use native drivers. Working on method to flash bios. (gateway m-series laptop).
Have since erased disk and installed 18.04 then upgraded to 20. Problem persisted. Erased and installed 18.04 again problem still exists. Close lid or wait for time to expire same results. Definitely an upgrade issue as 16.04 worked great for a few years.
I have booted to a live (usb) system and ran the drive checks. Drive is ok and fairly new. fsck returns 0 errors I'm thinking it's a ubuntu config issue as the sysrq allowed the machine to reboot and it was running fine until the 18.04 upgrade.
12/31/19 After some informing myself about sysrq (reisub) I was able to get the machine to reboot from the error screen.
I attempted to change the 176 sysrq value to 438 using
# echo "438" > /proc/sys/kernel/sysrq
and make it permanent with
# echo "kernel.sysrq = 438" >> /etc/sysctl.d/99-sysctl.conf
but it did not change it. Permission denied
$ cat /proc/sys/kernel/sysrq
Permission granted by using.
Now returns 438...
So now that I can avoid a hard shutdown what course should I take to resolve the resume from hibernate fail?
My novice status shines.