[SOLVED] Searching and not finding /sbin/init after a clean install.

Raija · 2012-04-14 12:43:10

Hi there. I apologize if the solution is around here, somewhere, but since I'm just left with my mobile device and little time, I can't do much research on my own right now. With no camera and no tool to re-write the whole error message upon bootup, I can just say that it mounts encrypted root partition, but after that it fails to continue the process - /sbin/init is not found and there are errors about mounting /usr and a couple of other partitions (not all, though).

Here are some files that I extracted that could possibly help with solving the issue. It's pretty much related to encryption of HDD partitions, since unencrypted install works fine on the same machine.

menu.lst
http://dl.dropbox.com/u/9584211/arch/menu.lst
fstab
http://dl.dropbox.com/u/9584211/arch/fstab
crypttab
http://dl.dropbox.com/u/9584211/arch/crypttab

[edit] Forgot to mention that /sbin/init *is* where it should be. I've also run mkinitcpio successfully and generated the necessary files...

Last edited by Raija (2012-04-15 07:57:01)

65kid · 2012-04-14 12:54:08

I don't know if this is actually the cause of the problem, but a separate /usr partition is afaik not supported anymore (see http://freedesktop.org/wiki/Software/sy … -is-broken). You also have two /tmp entries in /etc/fstab...why do you need a seperate /tmp partiton, tmpfs should work fine!? You also have /lib separated...I don't know if this is unsupported but I personally don't see the point, especially since it is already planned to move everything from /lib to /usr/lib (see https://wiki.archlinux.org/index.php/De … ki:UsrMove). And a separate /var is afaik only neccessary if you want a read-only root.

my point is: get rid of all the useless separation, I bet this will fix it.

Last edited by 65kid (2012-04-14 12:56:08)

Raija · 2012-04-14 13:01:23

Thanks for the input. Got rid of the extra /tmp entry; I must have had been in autopilot mode when editing fstab... I'm going to wait a bit before trying to reinstall/rearrange partitions, but your suggestions will be kept in mind.

Gcool · 2012-04-14 14:11:30

Try using persistent naming in your /etc/crypttab. Could be that the device names are simply getting switched around and it's mounting the wrong partition.

Raija · 2012-04-14 15:29:19

By following the persistent naming tips, I've managed to get into a working environment, but the rest of the partitions still don't mount, for some reason... Here are my fstab, menu.lst & crypttab as they are now (note that crypttab won't allow "literal passwords" in it):

http://dl.dropbox.com/u/9584211/arch/arch2/crypttab
http://dl.dropbox.com/u/9584211/arch/arch2/fstab
http://dl.dropbox.com/u/9584211/arch/arch2/menu.lst

I tried reducing the number of partitions, which did make troubleshooting a bit easier, but did nothing to directly help with the problem.

karol · 2012-04-14 15:56:17

65kid wrote:

I don't know if this is actually the cause of the problem, but a separate /usr partition is afaik not supported anymore (see http://freedesktop.org/wiki/Software/sy … -is-broken).

Have you read https://wiki.archlinux.org/index.php/Mk … _partition ?
It is supported.

65kid · 2012-04-14 16:02:14

karol wrote:

65kid wrote:
I don't know if this is actually the cause of the problem, but a separate /usr partition is afaik not supported anymore (see http://freedesktop.org/wiki/Software/sy … -is-broken).
Have you read https://wiki.archlinux.org/index.php/Mk … _partition ?
It is supported.

I stand corrected. Nevertheless, is there any good reason to use a separate /usr when installing a new system ?

Gcool · 2012-04-14 16:08:59

Once you've booted, try if you can decrypt/mount one the of the other partitions manually.

So something among the lines of:

# cryptsetup luksOpen /dev/path/to/homepartition home
# mount /dev/mapper/home /home

Raija · 2012-04-14 16:13:52

I can. I've used luksOpen to chroot several times by now.

Gcool · 2012-04-14 16:36:51

Could you post the content of your /etc/rc.conf and /etc/mkinitcpio.conf?

Raija · 2012-04-14 16:52:29

I managed to fix crypttab by... reverting to /dev/sdX names in there. Why it had to be done, remains a mystery to me, but I will post my new, working settings as soon as I get done with cleaning up the system.

[edit] It seems that the sequence of /etc/crypttab matters, and initscripts are not mounting devices in the proper order - which could be why with two mountable partitions (usr & home; root is already unlocked and boot is unencrypted) I get to login screen and with six I don't.

Last edited by Raija (2012-04-14 18:31:11)

Arch Linux

#1 2012-04-14 12:43:10

[SOLVED] Searching and not finding /sbin/init after a clean install.

#2 2012-04-14 12:54:08

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#3 2012-04-14 13:01:23

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#4 2012-04-14 14:11:30

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#5 2012-04-14 15:29:19

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#6 2012-04-14 15:56:17

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#7 2012-04-14 16:02:14

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#8 2012-04-14 16:08:59

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#9 2012-04-14 16:13:52

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#10 2012-04-14 16:36:51

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

#11 2012-04-14 16:52:29

Re: [SOLVED] Searching and not finding /sbin/init after a clean install.

Board footer