Skip to main content ↑ ↓
Topic: My system won't boot, telling me that /proc isn't mounted (Read 339 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

My system won't boot, telling me that /proc isn't mounted

Hello!
I'm using dinit. When I try booting to my Artix installation I am greeted with this text:
init: line 16: can't open /proc/cmdline: no such file
running early hook [udev]
proc is not mounted, but required for successful operation of systemd-tmpfiles. Please mount /proc/. Alternatively, consider using the --root= or --image= switches.
Failed to parse kernel command line, ignoring: No such file or directory
Starting udevd version 257.1-1-artix
:: running hook [udev]
:: Triggering uevents...
Running in chroot, ignoring request
Running in chroot, ignoring request
Running in chroot, ignoring request
:: running hook [keymap]
Loading keymap...done.
Waiting 10 seconds for device /dev/disk/by-uuid/6dacd9ca ... d31
:: running hook [openswap]
/dev/disk/by-uuid/32260384 ... 0fe does not exist or access denied.
:: running hook [resume]
ERROR: resume: no device specified for hibernation
ERROR: device '' not found. Skipping fsck.
:: mounting '' on real root.
:: running cleanup hook [udev]
Running in chroot, ignoring request.
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.

sh: can't access tty: job control turned off.

Then there's a prompt [rootfs ~]# but I can't type.

I have managed to find some posts on this forum and the arch forum from people with the same problem, but nothing that worked for them seems to have worked for me. I have tried reinstalling every package and remounting proc (along with boot and some other stuff that was suggested) from an iso, but to no avail. Also, anytime I mount the SSD (the device on which my root and boot directories live) in the iso, /mnt/proc and /mnt/sys empty, even after having mounted these to the mounted SSD before unmounting the SSD. To mount /proc, I followed the instructions for a luks partition (because my root and home partition is encrypted) from this post: https://forum.artixlinux.org/index.php/topic,103.0.html.

Any help would be appreciated.

Hugh

Re: My system won't boot, telling me that /proc isn't mounted

Reply #1 –
/proc is the Processor! Of cause it's empty on Disk.

What's your fstab?

Re: My system won't boot, telling me that /proc isn't mounted

Reply #2 –

# /etc/fstab: static file system information
# <file-system>                        <mount point>     <type>       <options>       <dump>       <pass>
UUID=CF68-3422                         /boot/efi             vfat        defaults,umask=0077 0 2
/dev/mapper/luks-6dacd9ca ... d31      /                 ext4           defaults           0 1
/dev/mapper/luks-32260384 ... 0fe      swap               swap        defaults            0 0
tmpfs                                    /tmp                 tmpfs                defaults,noatime,mode=1777 0 0
 

Also the first and second long strings from my original post are 6dacd9ca... and 32260384... respectively.

Re: My system won't boot, telling me that /proc isn't mounted

Reply #3 –
That looks ok for me. But I have no experience with full disk encryption.

I'm using an encrypted Home-Partition with runit, witch was the only were it works, when I startet with Artix 2020.

Edit: I'm not using UEFI, because it makes to much trouble for me. I'm booting in BIOS-Mode/CSM.

my fstab:
Code: [Select]
# <file system>                  <mount point> <type> <options>       <dump> <pass>
UUID=3bab5d41-420e-4104-bcdc-83dee87beccf /     xfs   noatime              0 0
/dev/mapper/Home                          /home xfs   noatime              0 0
memory                                    /tmp  tmpfs nosuid,size=90%      0 0
memory                                    /tmph tmpfs huge=always,size=90% 0 0
"huge=always" ist better for big files (i. e. DVB-S Videocutting) but very bad a lot of small files (like the Linux System-Partition), so I'm using both.

the crypttab:
Code: [Select]
# <name> <device>                                  <password> <options>
Home     UUID=7f836d83-e064-48cd-bb04-6078c8517499 none       luks,discard

And instead a Swap I'm using zram in /etc/rc.local:
Code: [Select]
#!/bin/sh
modprobe zram && echo lz4 > /sys/block/zram0/comp_algorithm && echo $(($(grep 'MemTotal:' /proc/meminfo|awk '{print $2}')*1/1))K > /sys/block/zram0/disksize && mkswap -qU clear /dev/zram0 && swapon -p100 /dev/zram0
exit 0

Re: My system won't boot, telling me that /proc isn't mounted

Reply #4 –
My crypttab:
Code: [Select]
# <name>                             <device>                    <password>                   <options>
luks-6dacd9ca-1b45-4fcd-9b83-3573b1d38d31 UUID=6dacd9ca-1b45-4fcd-9b83-3573b1d38d31    none luks
luks-32260384-71d9-48e4-bd8b-0dd0793020fe UUID=32260384-71d9-48e4-bd8b-0dd0793020fe    none luks
I'm asked for my passphrase before booting fails if that helps narrow it down...
 

Re: My system won't boot, telling me that /proc isn't mounted

Reply #5 –
@1st you should add ",discard" to your crypttab-entries, to enable trim-Support (that is *not* online-discard, like ",discard" in fstab).

2nd: If you use luks2, you should enable trim-Support there too (again it is *not* online-discard), so it's automatically enabled, when open it from "outside" (i. e. Livesystem):

Code: [Select]
sudo cryptsetup --allow-discards --persistent open /dev/sdXX ctmp && cryptsetup close ctmp

3rd: You should use usful Names in crypptab & fstab (like me), to make your Configuration easyer to understand.

That wont help with your /proc/ Problem: I don't know, how that could be: When your PC has a CPU, there must be a /proc/

I thought that you had a wrong /proc/ in your fstab, but there was no, so it could be a wrong configured initramfs - As said: I have no experience with that.

Because /tmp/ is in RAM, there are no personal Data on the Systempartition, so IMO it is a useless waste of CPU-Time, to encrypt it. It just makes it difficult, as you see.

I try to keep my System as simple as possible. So I encpryt the Homepartition and use runit, because for me its most straight forward and 2020 it was the only where the encrpted /home/ works: All other Initsystems failed.