Skip to main content ↑ ↓
Topic: can't boot /run/ directory got wiped (Read 430 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

can't boot /run/ directory got wiped

tried booting my artix-runit computer after a forced shutdown and it gets stuck on this error:

Code: [Select]
Starting cleanup
install: cannot create regular file '/run/runit/stopit' : No such file or directory
install: cannot create regular file '/run/runit/reboot' : No such file or directory
Initialization complete
-runit: leave stage: /etc/runit/1
-runit: enter stage: /etc/runit/2
runsvchdir: default: current.
ln: failed to create symbolic link '/run/runit/service' : No such file or directory

then it just stays there and I can't even access the ttys

I booted into a live usb and found out that the /run directory is completely empty. How did this suddenly happen and how can I fix it? I've been using this machine for a month and this just randomly happened now. I'm kind of new to artix and runit so I only know the basic stuff about using symbolic links to add services, but don't know which ones are required in order to be able to boot. I'm trying to fix this without having to reinstall because I have a lot of important files on this machine and I currently have no other hard drives to back up my data.

Re: can't boot /run/ directory got wiped

Reply #1 –

lol, this just gets better and better.
 
Just because you don't want to get your lazy ass out of the house to go buy a hard drive at the grocery shop next door, you want someone to write you an epically long, biblical-sized manual?
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: can't boot /run/ directory got wiped

Reply #2 –

 You have to chroot and reinstall runit.

When you boot the run directory gets populated with things when you shutdown it gets wiped it's normal. The problem is yours didn't get populated back properly while booting . You can try copy paste the run folder from the working live environment into the nuked one and try to boot. Once you manage to boot you can add again your services as previous.

If that doesn't work try reinstall runit in chroot.
 

Re: can't boot /run/ directory got wiped

Reply #3 –
As above but while your at it you could check for other packages with missing files and reinstall those as well if you find any.
Code: [Select]
pacman -Qk

Or you could just reinstall everything https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Reinstalling_all_packages
Code: [Select]
pacman -Qqn | pacman -S -

To make the chroot simple to do you can use artix-chroot which is available on the live iso's AFAIK. It's on the base versions that's for sure.
Simply
Code: [Select]
artix-chroot MOUNTPOINT


Re: can't boot /run/ directory got wiped

Reply #4 –
Quote from: gripped – on
As above but while your at it you could check for other packages with missing files and reinstall those as well if you find any.
Code: [Select]
pacman -Qk

Or you could just reinstall everything https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Reinstalling_all_packages
Code: [Select]
pacman -Qqn | pacman -S -

To make the chroot simple to do you can use artix-chroot which is available on the live iso's AFAIK. It's on the base versions that's for sure.
Simply
Code: [Select]
artix-chroot MOUNTPOINT



Thanks for the quick replies, I first tried copying the /run directory from the live environment but that did nothing. also reinstalling runit or just reinstalling all packages in chroot also did nothing.
when I check for missing files in any packages the command says everything is fine and that nothing is missing, but as soon as I reboot I end up getting the same error

Re: can't boot /run/ directory got wiped

Reply #5 –

  It can be a permission thing. Did you change any permissions that might prevent the init system to create necessary files? Go to var/log and check the logs and pacman log to see what looks strange in there. There's a  chance you'll need to downgrade the kernel to a previous version and will work.

Did you installed ucode and forgot to regenerate grub? After intel-ucode upgrade you need to
Code: [Select]
grub-mkconfig -o /boot/grub/grub.cfg

If you made some module changes you have to
Code: [Select]
mkinitcpio -P

My best guess is that you need to downgrade the kernel of course in artix-chroot