You are not logged in.

#1 2024-10-04 22:17:50

Vityou
Member
Registered: 2016-07-15
Posts: 36

Wake-on-lan outwardly wakes up computer but OS is unresponsive

Apologies if this is hard to diagnose since there is a lack of logs, but occasionally my computer will fail to resume from suspend with seemingly no explanation or logs, when using wake-on-lan. That is, the lights are on and the gpu fans are spinning but nothing is displayed to the monitor, I can't ssh in, and nothing seems to respond. I do see the computer on the network with arp-scan though.

Eventually I have to hold the power button to shut down, and looking at the logs with journalctl, there is nothing between when my computer successfully suspended the night before to the most recent boot. During the boot I do get some errors about a newer ssd I installed a few months ago.

Oct 04 18:02:09 Arch-Desktop systemd[1]: Mounted /boot.
Oct 04 18:02:09 Arch-Desktop systemd[1]: Finished File System Check on /dev/disk/by-uuid/de6ab4e9-e3f4-4081-b4c8-2c105002ffdc.
Oct 04 18:02:09 Arch-Desktop systemd[1]: Mounting /home...
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9196257
Oct 04 18:02:09 Arch-Desktop kernel: fbcon: Taking over console
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=4832, block=36700178) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9440028
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=2843, block=37748752) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9196535
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=5110, block=36700178) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9440002
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=2817, block=37748752) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9440026
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=2841, block=37748752) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 24775807
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=3198, block=99090448) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9440027
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=2842, block=37748752) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9440008
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=2823, block=37748752) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 9440032
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=2847, block=37748752) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs error (device nvme1n1p1): ext4_orphan_get:1420: comm mount: bad orphan inode 24775799
Oct 04 18:02:09 Arch-Desktop kernel: ext4_test_bit(bit=3190, block=99090448) = 0
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs (nvme1n1p1): recovery complete
Oct 04 18:02:09 Arch-Desktop kernel: EXT4-fs (nvme1n1p1): mounted filesystem de6ab4e9-e3f4-4081-b4c8-2c105002ffdc r/w with ordered data mode. Quota mode: none.
Oct 04 18:02:09 Arch-Desktop kernel: Console: switching to colour frame buffer device 240x67
Oct 04 18:02:09 Arch-Desktop systemd[1]: Mounted /home.
Oct 04 18:02:09 Arch-Desktop systemd[1]: Reached target Local File Systems.

So I wonder if it may be a disk issue.

I'd also note that this typically happens after long sleep periods like overnight, if that gives any clues.

Last edited by Vityou (2024-10-04 22:18:57)

Offline

Board footer

Powered by FluxBB