Hello guys,
I have ran into an Issue with my Artix system. This random “halt” when booting up.
*starting acpid ... [ok]
*starting cronie ... [ok]
*starting connecting manager ... [ok]
*mounting network filesystems ... [ok]
*setting up sddm ... [ok]
*starting local ...
The system stops at starting local it never “[ok]” and just stays there. I haven’t used the computer in about 2- 3 so it hasn’t been updated since then, don’t know if it has anything to do with it. Any help is appreciated
I'm assuming you use syslog-ng and installed the version that was in the gremlins repo. That syslog-ng is confirmed to be bad and freezes your machine. You have to get a liveiso, chroot into your machine and then disable it. The known bad version no longer exists in the repos so while you're at it, do a pacman -Syu and then reinstall syslog-ng.
thanks, im about to do that. Just to be precise, when you say “disable it” you mean syslog-ng?
Yeah syslog-ng is the offender here.
I’ve tried all day no success I can’t mount the partition.
# mount dev/sda2/mnt
mount: dev/sda2/mnt: can’t find in /etc/fstab.
Don’t want to be a noob anymore and reinstall :( wanna fix this
I think you should try tomorrow after getting some rest, there should be a space between /dev/sda2 and /mnt. ;)
Wow :l
Small brain struggles
Ok, I chrooted and I’m in the syslog-ng dir, what should I change ? The syslog-ng config?
Don't touch the config file. Just install the "good" package.
$ sudo pacman -S world/syslog-ng
Thank you guys all, the issue was fixed :D
I have just recently come upon the OP's exact problem.
Been racking my brain for a couple days trying to figure this out.
Do you reckon the fix might be something similar here?
Syslog-ng doesn't seem to be a package installed on my current installation, if my memory of last night's chroot troubleshooting is accurate.
For frame of reference, I had a hard-lock due to resource insufficiency on my laptop and had to do a hard reset. What resulted in the malfunction.
Other than that, my problem is identical to the OP, save for that it was noticed directly after the reboot the same day I was using it.
Not as advanced a user of unix-type systems as I'd like to be; any help would be greatly appreciated.
Please, don't necrobump; It's way better to start a new thread. You probably got metalog with your installation, use it.