#archlinux32 | Logs for 2023-12-17
Back
[01:28:04] -!- bdju has joined #archlinux32
[07:21:09] -!- morriset has joined #archlinux32
[08:46:28] -!- clemens3 has quit [Quit: WeeChat 2.7]
[08:47:08] -!- clemens3 has joined #archlinux32
[11:20:31] -!- drathir_tor has quit [Ping timeout: 240 seconds]
[11:27:43] -!- drathir_tor has joined #archlinux32
[12:56:42] -!- n0tiz has quit [Quit: Bye]
[12:58:33] -!- n0tiz has joined #archlinux32
[13:00:26] -!- drathir_tor has quit [Remote host closed the connection]
[13:15:59] -!- drathir_tor has joined #archlinux32
[13:44:04] -!- epony has quit [Remote host closed the connection]
[16:49:20] -!- epony has joined #archlinux32
[18:37:32] <girls> Hi KitsuWhooa - what did I miss?
[19:12:04] -!- epony has quit [Remote host closed the connection]
[19:13:59] -!- epony has joined #archlinux32
[21:49:02] <KillerWasp> I normally turn off the device through the command and wait for the device to turn off by itself. The next day it turns out that errors are detected in the home partition and the kernel dies without entering root mode. I had to enter from the other system into another partition whose home was not mounted and run fsck, several broken or incorrect inodes, fix them and run the initial system again, everything working correctly again. What were
[21:49:02] <KillerWasp> the broken inodes? Files managed by firefox.
[21:49:10] <KillerWasp> i hate firefox....
[21:49:37] <KillerWasp> s/device/computer/
[21:53:20] <KitsuWhooa> girls: sorry, are you still around?