/sbin/init does not exist - Bailing out, you are on your own. Good luck
I'm trying to install arch linux. When I boot up, it gives me the message found below.
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
arch-linux system-installation
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
asked Oct 19 '13 at 4:47
Chance Leachman
36113
|
show 8 more comments
I'm trying to install arch linux. When I boot up, it gives me the message found below.
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
arch-linux system-installation
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
asked Oct 19 '13 at 4:47
Chance Leachman
36113
init should be located in /usr/bin/init and not /sbin/init
– Jeight
Oct 19 '13 at 5:07
1
Did you use an old installation image and not-Syu?
– jasonwryan
Oct 19 '13 at 5:11
3
@Jeight/sbinand/binare symlinks to/usr/binon Arch Linux.
– strugee
Oct 19 '13 at 5:19
1
@strugee The question now is are the OP's Arch Linux /sbin and /bin using the sym links that it should have by default. That would cause the issue.
– Jeight
Oct 19 '13 at 5:23
4
@ChanceLeachman I really would recommend against using things like this. if you don't want to configure Arch the way the wiki recommends, or don't understand what you're doing, then Arch is probably not the right distribution for you (maybe try Mint or Debian). also, your link 404s. @Jeight FWIW, I suspect that he can just install thesystemdpackage. maybe his script wasn't updated for the transition to systemd as init.
– strugee
Oct 19 '13 at 5:32
|
show 8 more comments
I'm trying to install arch linux. When I boot up, it gives me the message found below.
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
arch-linux system-installation
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
asked Oct 19 '13 at 4:47
Chance Leachman
36113
I'm trying to install arch linux. When I boot up, it gives me the message found below.
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
arch-linux system-installation
arch-linux system-installation
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
asked Oct 19 '13 at 4:47
Chance Leachman
36113
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
asked Oct 19 '13 at 4:47
Chance Leachman
36113
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
edited Oct 19 '13 at 22:32
Gilles
528k12810581583
528k12810581583
asked Oct 19 '13 at 4:47
Chance Leachman
36113
asked Oct 19 '13 at 4:47
Chance Leachman
36113
asked Oct 19 '13 at 4:47
Chance Leachman
36113
36113
init should be located in /usr/bin/init and not /sbin/init
– Jeight
Oct 19 '13 at 5:07
1
Did you use an old installation image and not-Syu?
– jasonwryan
Oct 19 '13 at 5:11
3
@Jeight/sbinand/binare symlinks to/usr/binon Arch Linux.
– strugee
Oct 19 '13 at 5:19
1
@strugee The question now is are the OP's Arch Linux /sbin and /bin using the sym links that it should have by default. That would cause the issue.
– Jeight
Oct 19 '13 at 5:23
4
@ChanceLeachman I really would recommend against using things like this. if you don't want to configure Arch the way the wiki recommends, or don't understand what you're doing, then Arch is probably not the right distribution for you (maybe try Mint or Debian). also, your link 404s. @Jeight FWIW, I suspect that he can just install thesystemdpackage. maybe his script wasn't updated for the transition to systemd as init.
– strugee
Oct 19 '13 at 5:32
|
show 8 more comments
init should be located in /usr/bin/init and not /sbin/init
– Jeight
Oct 19 '13 at 5:07
1
Did you use an old installation image and not-Syu?
– jasonwryan
Oct 19 '13 at 5:11
3
@Jeight/sbinand/binare symlinks to/usr/binon Arch Linux.
– strugee
Oct 19 '13 at 5:19
1
@strugee The question now is are the OP's Arch Linux /sbin and /bin using the sym links that it should have by default. That would cause the issue.
– Jeight
Oct 19 '13 at 5:23
4
@ChanceLeachman I really would recommend against using things like this. if you don't want to configure Arch the way the wiki recommends, or don't understand what you're doing, then Arch is probably not the right distribution for you (maybe try Mint or Debian). also, your link 404s. @Jeight FWIW, I suspect that he can just install thesystemdpackage. maybe his script wasn't updated for the transition to systemd as init.
– strugee
Oct 19 '13 at 5:32
init should be located in /usr/bin/init and not /sbin/init
– Jeight
Oct 19 '13 at 5:07
init should be located in /usr/bin/init and not /sbin/init
– Jeight
Oct 19 '13 at 5:07
1
1
Did you use an old installation image and not
-Syu?– jasonwryan
Oct 19 '13 at 5:11
Did you use an old installation image and not
-Syu?– jasonwryan
Oct 19 '13 at 5:11
3
3
@Jeight
/sbin and /bin are symlinks to /usr/bin on Arch Linux.– strugee
Oct 19 '13 at 5:19
@Jeight
/sbin and /bin are symlinks to /usr/bin on Arch Linux.– strugee
Oct 19 '13 at 5:19
1
1
@strugee The question now is are the OP's Arch Linux /sbin and /bin using the sym links that it should have by default. That would cause the issue.
– Jeight
Oct 19 '13 at 5:23
@strugee The question now is are the OP's Arch Linux /sbin and /bin using the sym links that it should have by default. That would cause the issue.
– Jeight
Oct 19 '13 at 5:23
4
4
@ChanceLeachman I really would recommend against using things like this. if you don't want to configure Arch the way the wiki recommends, or don't understand what you're doing, then Arch is probably not the right distribution for you (maybe try Mint or Debian). also, your link 404s. @Jeight FWIW, I suspect that he can just install the
systemd package. maybe his script wasn't updated for the transition to systemd as init.– strugee
Oct 19 '13 at 5:32
@ChanceLeachman I really would recommend against using things like this. if you don't want to configure Arch the way the wiki recommends, or don't understand what you're doing, then Arch is probably not the right distribution for you (maybe try Mint or Debian). also, your link 404s. @Jeight FWIW, I suspect that he can just install the
systemd package. maybe his script wasn't updated for the transition to systemd as init.– strugee
Oct 19 '13 at 5:32
|
show 8 more comments
5 Answers
5
active
oldest
votes
You should need systemd-sysvcompat if you want to use init. The /sbin/init is a simple symbolic link to /lib/systemd/systemd (see PKGBUILD) provided by systemd-sysvcompat.
So if you want to boot your system you should add into grub kernel line (if you use grub):
init=/lib/systemd/systemd
If you don't want to use systemd-sysvcompat you should add the line above into your GRUB's configuration
answered Oct 19 '13 at 18:27
uzsolt
1,432714
add a comment |
I encountered this problem and solved it by re-installing arch base system and paying closer attention to the instructions given. Specifically under Syslinux - Installation on BIOS.
I chose to install syslinux and read the instructions too quickly and forgot to
Configure syslinux.cfg to point to the right root partition. This step is vital.
My root partition which was on /dev/sda2 in my case, and as you can see below it is not pointing to it.
...
LABEL arch
...
APPEND root=/dev/sda3 rw
...
It pointed to my home partition, /dev/sda3
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
add a comment |
Download the very latest install ISO (2013.10.1 currently) from the Arch Download page. Put that ISO on a CD or whatever and re-install.
Either you used an elderly installation ISO or something went wrong during your install. On my relatively up-to-date Arch server, /sbin/init is a symbolic link to /lib/systemd/systemd.
You could check that /sbin/init exists, and that either it's a real file or a symbolic link. If the latter, check to see if what the symbolic link says exists, is executable, is a file, etc etc. My guess is something in that process will show where the install went bad, but that you should probably re-do the install from a fresh download of the ISO image.
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
2
Arch does useinit, in the sense that the kernel wants a program called/sbin/init(unless the bootloader passes a different value via theinitoption), and that the program with PID 1 is conventionally calledinit. It doesn't matter to the kernel whether this is theinitfrom Systemd or from SysVinit or from Upstart or from BusyBox.
– Gilles
Oct 19 '13 at 22:34
add a comment |
This can happen if you used the wrong partition for root. Look up your loader entry (in /boot/loader/entries/arch.conf if you are using systemd-boot on Arch Linux like me), and ensure the 'root' UUID is your root partition.
answered Dec 24 '16 at 23:11
Daniel Guenther
213
add a comment |
I Know this post is old, but I have just encountered this problem, and I didn't find a good answer elsewhere, so here is my answer, hoping that this helps someone in the future.
In my case, when I was at the stage
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
There actually was a /sbin/init, which was nothing but a symbolic link to
busybox!
Here is what happened.
In Archlinux, the directory /sbin is a symbolic link to /usr/sbin. And, as say other people, /usr/sbin/init symlinks to /lib/systemd/systemd. But, in my case, I found out that the /usr directory was not mounted.
You basically need to mount the partition /usr as explained on this ArchWiki page. You may also want to verify /etc/fstab, especially if you use one generated by genfstab.
answered Dec 19 '18 at 7:09
user43326
1112
A related answer is unix.stackexchange.com/a/392223/5132 and a related question is unix.stackexchange.com/questions/247532 .
– JdeBP
Dec 19 '18 at 12:31
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f96720%2fsbin-init-does-not-exist-bailing-out-you-are-on-your-own-good-luck%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should need systemd-sysvcompat if you want to use init. The /sbin/init is a simple symbolic link to /lib/systemd/systemd (see PKGBUILD) provided by systemd-sysvcompat.
So if you want to boot your system you should add into grub kernel line (if you use grub):
init=/lib/systemd/systemd
If you don't want to use systemd-sysvcompat you should add the line above into your GRUB's configuration
answered Oct 19 '13 at 18:27
uzsolt
1,432714
add a comment |
You should need systemd-sysvcompat if you want to use init. The /sbin/init is a simple symbolic link to /lib/systemd/systemd (see PKGBUILD) provided by systemd-sysvcompat.
So if you want to boot your system you should add into grub kernel line (if you use grub):
init=/lib/systemd/systemd
If you don't want to use systemd-sysvcompat you should add the line above into your GRUB's configuration
answered Oct 19 '13 at 18:27
uzsolt
1,432714
add a comment |
You should need systemd-sysvcompat if you want to use init. The /sbin/init is a simple symbolic link to /lib/systemd/systemd (see PKGBUILD) provided by systemd-sysvcompat.
So if you want to boot your system you should add into grub kernel line (if you use grub):
init=/lib/systemd/systemd
If you don't want to use systemd-sysvcompat you should add the line above into your GRUB's configuration
answered Oct 19 '13 at 18:27
uzsolt
1,432714
You should need systemd-sysvcompat if you want to use init. The /sbin/init is a simple symbolic link to /lib/systemd/systemd (see PKGBUILD) provided by systemd-sysvcompat.
So if you want to boot your system you should add into grub kernel line (if you use grub):
init=/lib/systemd/systemd
If you don't want to use systemd-sysvcompat you should add the line above into your GRUB's configuration
answered Oct 19 '13 at 18:27
uzsolt
1,432714
answered Oct 19 '13 at 18:27
uzsolt
1,432714
answered Oct 19 '13 at 18:27
uzsolt
1,432714
answered Oct 19 '13 at 18:27
uzsolt
1,432714
1,432714
add a comment |
add a comment |
I encountered this problem and solved it by re-installing arch base system and paying closer attention to the instructions given. Specifically under Syslinux - Installation on BIOS.
I chose to install syslinux and read the instructions too quickly and forgot to
Configure syslinux.cfg to point to the right root partition. This step is vital.
My root partition which was on /dev/sda2 in my case, and as you can see below it is not pointing to it.
...
LABEL arch
...
APPEND root=/dev/sda3 rw
...
It pointed to my home partition, /dev/sda3
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
add a comment |
I encountered this problem and solved it by re-installing arch base system and paying closer attention to the instructions given. Specifically under Syslinux - Installation on BIOS.
I chose to install syslinux and read the instructions too quickly and forgot to
Configure syslinux.cfg to point to the right root partition. This step is vital.
My root partition which was on /dev/sda2 in my case, and as you can see below it is not pointing to it.
...
LABEL arch
...
APPEND root=/dev/sda3 rw
...
It pointed to my home partition, /dev/sda3
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
add a comment |
I encountered this problem and solved it by re-installing arch base system and paying closer attention to the instructions given. Specifically under Syslinux - Installation on BIOS.
I chose to install syslinux and read the instructions too quickly and forgot to
Configure syslinux.cfg to point to the right root partition. This step is vital.
My root partition which was on /dev/sda2 in my case, and as you can see below it is not pointing to it.
...
LABEL arch
...
APPEND root=/dev/sda3 rw
...
It pointed to my home partition, /dev/sda3
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
I encountered this problem and solved it by re-installing arch base system and paying closer attention to the instructions given. Specifically under Syslinux - Installation on BIOS.
I chose to install syslinux and read the instructions too quickly and forgot to
Configure syslinux.cfg to point to the right root partition. This step is vital.
My root partition which was on /dev/sda2 in my case, and as you can see below it is not pointing to it.
...
LABEL arch
...
APPEND root=/dev/sda3 rw
...
It pointed to my home partition, /dev/sda3
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
edited Dec 28 '16 at 10:16
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
answered Feb 6 '14 at 19:36
Pau Coma Ramirez
1313
1313
add a comment |
add a comment |
Download the very latest install ISO (2013.10.1 currently) from the Arch Download page. Put that ISO on a CD or whatever and re-install.
Either you used an elderly installation ISO or something went wrong during your install. On my relatively up-to-date Arch server, /sbin/init is a symbolic link to /lib/systemd/systemd.
You could check that /sbin/init exists, and that either it's a real file or a symbolic link. If the latter, check to see if what the symbolic link says exists, is executable, is a file, etc etc. My guess is something in that process will show where the install went bad, but that you should probably re-do the install from a fresh download of the ISO image.
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
2
Arch does useinit, in the sense that the kernel wants a program called/sbin/init(unless the bootloader passes a different value via theinitoption), and that the program with PID 1 is conventionally calledinit. It doesn't matter to the kernel whether this is theinitfrom Systemd or from SysVinit or from Upstart or from BusyBox.
– Gilles
Oct 19 '13 at 22:34
add a comment |
Download the very latest install ISO (2013.10.1 currently) from the Arch Download page. Put that ISO on a CD or whatever and re-install.
Either you used an elderly installation ISO or something went wrong during your install. On my relatively up-to-date Arch server, /sbin/init is a symbolic link to /lib/systemd/systemd.
You could check that /sbin/init exists, and that either it's a real file or a symbolic link. If the latter, check to see if what the symbolic link says exists, is executable, is a file, etc etc. My guess is something in that process will show where the install went bad, but that you should probably re-do the install from a fresh download of the ISO image.
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
2
Arch does useinit, in the sense that the kernel wants a program called/sbin/init(unless the bootloader passes a different value via theinitoption), and that the program with PID 1 is conventionally calledinit. It doesn't matter to the kernel whether this is theinitfrom Systemd or from SysVinit or from Upstart or from BusyBox.
– Gilles
Oct 19 '13 at 22:34
add a comment |
Download the very latest install ISO (2013.10.1 currently) from the Arch Download page. Put that ISO on a CD or whatever and re-install.
Either you used an elderly installation ISO or something went wrong during your install. On my relatively up-to-date Arch server, /sbin/init is a symbolic link to /lib/systemd/systemd.
You could check that /sbin/init exists, and that either it's a real file or a symbolic link. If the latter, check to see if what the symbolic link says exists, is executable, is a file, etc etc. My guess is something in that process will show where the install went bad, but that you should probably re-do the install from a fresh download of the ISO image.
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
Download the very latest install ISO (2013.10.1 currently) from the Arch Download page. Put that ISO on a CD or whatever and re-install.
Either you used an elderly installation ISO or something went wrong during your install. On my relatively up-to-date Arch server, /sbin/init is a symbolic link to /lib/systemd/systemd.
You could check that /sbin/init exists, and that either it's a real file or a symbolic link. If the latter, check to see if what the symbolic link says exists, is executable, is a file, etc etc. My guess is something in that process will show where the install went bad, but that you should probably re-do the install from a fresh download of the ISO image.
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
edited Oct 19 '13 at 22:59
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
answered Oct 19 '13 at 15:28
Bruce Ediger
34.7k566119
34.7k566119
2
Arch does useinit, in the sense that the kernel wants a program called/sbin/init(unless the bootloader passes a different value via theinitoption), and that the program with PID 1 is conventionally calledinit. It doesn't matter to the kernel whether this is theinitfrom Systemd or from SysVinit or from Upstart or from BusyBox.
– Gilles
Oct 19 '13 at 22:34
add a comment |
2
Arch does useinit, in the sense that the kernel wants a program called/sbin/init(unless the bootloader passes a different value via theinitoption), and that the program with PID 1 is conventionally calledinit. It doesn't matter to the kernel whether this is theinitfrom Systemd or from SysVinit or from Upstart or from BusyBox.
– Gilles
Oct 19 '13 at 22:34
2
2
Arch does use
init, in the sense that the kernel wants a program called /sbin/init (unless the bootloader passes a different value via the init option), and that the program with PID 1 is conventionally called init. It doesn't matter to the kernel whether this is the init from Systemd or from SysVinit or from Upstart or from BusyBox.– Gilles
Oct 19 '13 at 22:34
Arch does use
init, in the sense that the kernel wants a program called /sbin/init (unless the bootloader passes a different value via the init option), and that the program with PID 1 is conventionally called init. It doesn't matter to the kernel whether this is the init from Systemd or from SysVinit or from Upstart or from BusyBox.– Gilles
Oct 19 '13 at 22:34
add a comment |
This can happen if you used the wrong partition for root. Look up your loader entry (in /boot/loader/entries/arch.conf if you are using systemd-boot on Arch Linux like me), and ensure the 'root' UUID is your root partition.
answered Dec 24 '16 at 23:11
Daniel Guenther
213
add a comment |
This can happen if you used the wrong partition for root. Look up your loader entry (in /boot/loader/entries/arch.conf if you are using systemd-boot on Arch Linux like me), and ensure the 'root' UUID is your root partition.
answered Dec 24 '16 at 23:11
Daniel Guenther
213
add a comment |
This can happen if you used the wrong partition for root. Look up your loader entry (in /boot/loader/entries/arch.conf if you are using systemd-boot on Arch Linux like me), and ensure the 'root' UUID is your root partition.
answered Dec 24 '16 at 23:11
Daniel Guenther
213
This can happen if you used the wrong partition for root. Look up your loader entry (in /boot/loader/entries/arch.conf if you are using systemd-boot on Arch Linux like me), and ensure the 'root' UUID is your root partition.
answered Dec 24 '16 at 23:11
Daniel Guenther
213
edited Sep 3 '17 at 6:48
answered Dec 24 '16 at 23:11
Daniel Guenther
213
answered Dec 24 '16 at 23:11
Daniel Guenther
213
answered Dec 24 '16 at 23:11
Daniel Guenther
213
213
add a comment |
add a comment |
I Know this post is old, but I have just encountered this problem, and I didn't find a good answer elsewhere, so here is my answer, hoping that this helps someone in the future.
In my case, when I was at the stage
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
There actually was a /sbin/init, which was nothing but a symbolic link to
busybox!
Here is what happened.
In Archlinux, the directory /sbin is a symbolic link to /usr/sbin. And, as say other people, /usr/sbin/init symlinks to /lib/systemd/systemd. But, in my case, I found out that the /usr directory was not mounted.
You basically need to mount the partition /usr as explained on this ArchWiki page. You may also want to verify /etc/fstab, especially if you use one generated by genfstab.
answered Dec 19 '18 at 7:09
user43326
1112
A related answer is unix.stackexchange.com/a/392223/5132 and a related question is unix.stackexchange.com/questions/247532 .
– JdeBP
Dec 19 '18 at 12:31
add a comment |
I Know this post is old, but I have just encountered this problem, and I didn't find a good answer elsewhere, so here is my answer, hoping that this helps someone in the future.
In my case, when I was at the stage
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
There actually was a /sbin/init, which was nothing but a symbolic link to
busybox!
Here is what happened.
In Archlinux, the directory /sbin is a symbolic link to /usr/sbin. And, as say other people, /usr/sbin/init symlinks to /lib/systemd/systemd. But, in my case, I found out that the /usr directory was not mounted.
You basically need to mount the partition /usr as explained on this ArchWiki page. You may also want to verify /etc/fstab, especially if you use one generated by genfstab.
answered Dec 19 '18 at 7:09
user43326
1112
A related answer is unix.stackexchange.com/a/392223/5132 and a related question is unix.stackexchange.com/questions/247532 .
– JdeBP
Dec 19 '18 at 12:31
add a comment |
I Know this post is old, but I have just encountered this problem, and I didn't find a good answer elsewhere, so here is my answer, hoping that this helps someone in the future.
In my case, when I was at the stage
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
There actually was a /sbin/init, which was nothing but a symbolic link to
busybox!
Here is what happened.
In Archlinux, the directory /sbin is a symbolic link to /usr/sbin. And, as say other people, /usr/sbin/init symlinks to /lib/systemd/systemd. But, in my case, I found out that the /usr directory was not mounted.
You basically need to mount the partition /usr as explained on this ArchWiki page. You may also want to verify /etc/fstab, especially if you use one generated by genfstab.
answered Dec 19 '18 at 7:09
user43326
1112
I Know this post is old, but I have just encountered this problem, and I didn't find a good answer elsewhere, so here is my answer, hoping that this helps someone in the future.
In my case, when I was at the stage
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own now. Good luck.
sh: can't access tty: job control turned off
[rootfs /]# _
There actually was a /sbin/init, which was nothing but a symbolic link to
busybox!
Here is what happened.
In Archlinux, the directory /sbin is a symbolic link to /usr/sbin. And, as say other people, /usr/sbin/init symlinks to /lib/systemd/systemd. But, in my case, I found out that the /usr directory was not mounted.
You basically need to mount the partition /usr as explained on this ArchWiki page. You may also want to verify /etc/fstab, especially if you use one generated by genfstab.
answered Dec 19 '18 at 7:09
user43326
1112
answered Dec 19 '18 at 7:09
user43326
1112
answered Dec 19 '18 at 7:09
user43326
1112
answered Dec 19 '18 at 7:09
user43326
1112
1112
A related answer is unix.stackexchange.com/a/392223/5132 and a related question is unix.stackexchange.com/questions/247532 .
– JdeBP
Dec 19 '18 at 12:31
add a comment |
A related answer is unix.stackexchange.com/a/392223/5132 and a related question is unix.stackexchange.com/questions/247532 .
– JdeBP
Dec 19 '18 at 12:31
A related answer is unix.stackexchange.com/a/392223/5132 and a related question is unix.stackexchange.com/questions/247532 .
– JdeBP
Dec 19 '18 at 12:31
A related answer is unix.stackexchange.com/a/392223/5132 and a related question is unix.stackexchange.com/questions/247532 .
– JdeBP
Dec 19 '18 at 12:31
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f96720%2fsbin-init-does-not-exist-bailing-out-you-are-on-your-own-good-luck%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
init should be located in /usr/bin/init and not /sbin/init
– Jeight
Oct 19 '13 at 5:07
1
Did you use an old installation image and not
-Syu?– jasonwryan
Oct 19 '13 at 5:11
3
@Jeight
/sbinand/binare symlinks to/usr/binon Arch Linux.– strugee
Oct 19 '13 at 5:19
1
@strugee The question now is are the OP's Arch Linux /sbin and /bin using the sym links that it should have by default. That would cause the issue.
– Jeight
Oct 19 '13 at 5:23
4
@ChanceLeachman I really would recommend against using things like this. if you don't want to configure Arch the way the wiki recommends, or don't understand what you're doing, then Arch is probably not the right distribution for you (maybe try Mint or Debian). also, your link 404s. @Jeight FWIW, I suspect that he can just install the
systemdpackage. maybe his script wasn't updated for the transition to systemd as init.– strugee
Oct 19 '13 at 5:32