[solved] after update - cant boot - /sbin/iinit does not exist

capoeira · 2013-06-05 12:37:09

I updated like was written here https://www.archlinux.org/news/binaries … ervention/
but I now see that the update comand now changed (my RSS reader didnt update this)

I updated with the old comand and updated bash afterwards.
reboot didn´t work so I made a hard reset.

now I got this error after grub:

 ERROR: Root device mounted successfully, but /sbin/init does not exist

please help

Last edited by capoeira (2013-06-05 17:35:26)

ball · 2013-06-05 12:41:32

Do you have init=/sbin/init as a boot parameter for the kernel? Then you should change it in the bootloader to init=/usr/lib/systemd/systemd. If systemd-sysvcompat is installed you can remove this parameter alltogether.

Edit: And which "old command" did you use to update?

Last edited by ball (2013-06-05 12:43:00)

capoeira · 2013-06-05 12:51:39

ball wrote:

Do you have init=/sbin/init as a boot parameter for the kernel? Then you should change it in the bootloader to init=/usr/lib/systemd/systemd. If systemd-sysvcompat is installed you can remove this parameter alltogether.

systemd-sysvcompat is installed, I think, because I made full switch to systemd. And there is no init parameter in the grub entry

ball wrote:

Edit: And which "old command" did you use to update?

I cant reproduce because obviously I cant access my RSS-reader now. The comand changed in the news-entry

nims11 · 2013-06-05 12:52:56

I also screwed up my update and ended up with the same error. I actually straightaway did a

# pacman -Syu --ignore filesystem,bash
# pacman -S bash

Also, my pacman was failing to download anything after this from the internet independent of the external downloader i used. So I rebooted and ended up this way.

I solved it by Booting from a LiveCD, chroot-ing into Arch root partition, Fixing packages in /bin, /sbin, downloaded the *.xz for filesystem 2013.05-2 from https://www.archlinux.org/packages/ and installed it with "pacman -U".

Last edited by nims11 (2013-06-05 12:54:23)

capoeira · 2013-06-05 13:07:36

one thing I didnt do is

# pacman -Su

can this be the issue?
how is filesystem supposed to be updated anyways, since it doesnt appear in the news article?

I still have the old filesystem package.

will try install filesystem with livecd if noone has another solution

nims11 · 2013-06-05 13:10:50

capoeira wrote:

one thing I didnt do is
# pacman -Su
can this be the issue?
how is filesystem supposed to be updated anyways, since it doesnt appear in the news article?
I still have the old filesystem package.

will try install filesystem with livecd if noone has another solution

Filesystem was supposed to updated via

# pacman -Su

ball · 2013-06-05 13:19:22

capoeira wrote:

how is filesystem supposed to be updated anyways, since it doesnt appear in the news article?

Did you actually read the news post? This is the very reason for this whole procedure.

capoeira wrote:

will try install filesystem with livecd if noone has another solution

I guess this is the canonical solution in your case. But before updating make sure that you follow the advices given in the news post: fix all packages which have files in the problematic directories. Otherwise filesystem will refuse to install.

scar · 2013-06-05 13:27:40

capoeira wrote:

how is filesystem supposed to be updated anyways, since it doesnt appear in the news article?

Filesystem is pretty much supposed to be updated, you will see it if you manage to have your system functional.
Just look at it with the command

# ls -la / 

and

# ls -la /usr/

and you will see that /bin /sbin and /usr/sbin became symlinks to /usr/bin.

capoeira · 2013-06-05 13:55:41

sorry, irelevant now. dificult to read some comands in the wiki without copy/paste

Last edited by capoeira (2013-06-05 15:20:50)

HalosGhost · 2013-06-05 14:05:27

capoeira wrote:

delete

Please don't do that.

All the best,

-HG

ewaller · 2013-06-05 14:52:31

Capoeira: HalosGhost is absolutely correct. We consider post blanking to be rude and inconsiderate of other's time and effort. If you want, change the text to strike through and leave a note as to why it is no longer relevant. Abuse of the forum rules can lead to a temporary ban.

capoeira · 2013-06-05 15:19:33

HalosGhost wrote:

capoeira wrote:
delete
Please don't do that.
All the best,
-HG

sorry, I cant find the right proceedure in the link

ball wrote:

capoeira wrote:
how is filesystem supposed to be updated anyways, since it doesnt appear in the news article?
Did you actually read the news post? This is the very reason for this whole procedure.
capoeira wrote:
will try install filesystem with livecd if noone has another solution
I guess this is the canonical solution in your case. But before updating make sure that you follow the advices given in the news post: fix all packages which have files in the problematic directories. Otherwise filesystem will refuse to install.

I have done the steps and only found e4rat-lite and uninstalled it

I now chrooted into the system but cant update filesystem

doing it again

pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
error:  No package owns /sbin
error: failed to read file ´/sbin´ : No such file or directory

in /bin there is only 1 file called install, I guess its from the livecd? since I am chrooted this shouldnt be there?

Scimmia · 2013-06-05 15:22:14

if you're chrooted, it's not from the install disk. What is it? try file /bin/install or cat /bin/install

capoeira · 2013-06-05 15:28:52

Scimmia wrote:

What is it? try file /bin/install

this informed me its a symbolic link to /usr/bin/install

can I delete the whole directory?

yungtrizzle · 2013-06-05 15:29:12

I ran through the commands as required by the news feed, I can see the symlinks but I can't boot. I have a folder called new_root hanging around

Last edited by yungtrizzle (2013-06-05 15:32:58)

ball · 2013-06-05 15:29:45

capoeira wrote:

HalosGhost wrote:
Please don't do that.
sorry, I cant find the right proceedure in the link

Then read it again. The paragraph clearly implicates that your blanking of posts is strongly undesirable.

capoeira wrote:

in /bin there is only 1 file called install, I guess its from the livecd? since I am chrooted this shouldnt be there?

Chrooting won't copy any files to your system. Investigate the file, it must have been created by you.

Scimmia · 2013-06-05 15:31:25

capoeira wrote:

Scimmia wrote:
What is it? try file /bin/install
this informed me its a symbolic link to /usr/bin/install
can I delete the whole directory?

If that's the only thing in /bin, then yes, delete the whole dir.

Scimmia · 2013-06-05 15:31:58

yungtrizzle wrote:

I ran through the commands as required by the news feed, I can see the symlinks both I can't boot. I have a folder called new_root hanging around

Interesting, why not? What errors are you getting?

Last edited by Scimmia (2013-06-05 15:32:45)

yungtrizzle · 2013-06-05 15:39:01

It gives me the same error as capoeira. I can run some commands but nothing of use except vi.

ball · 2013-06-05 15:41:38

yungtrizzle wrote:

It gives me the same error as capoeira. I can run some commands but nothing of use except vi.

Did you already do what has been suggested in this thread? If not, catch up and profit.

Last edited by ball (2013-06-05 15:42:35)

Scimmia · 2013-06-05 15:46:42

yungtrizzle wrote:

It gives me the same error as capoeira. I can run some commands but nothing of use except vi.

https://bbs.archlinux.org/viewtopic.php … 3#p1283343

yungtrizzle · 2013-06-05 15:54:21

ball wrote:

yungtrizzle wrote:
It gives me the same error as capoeira. I can run some commands but nothing of use except vi.
Did you already do what has been suggested in this thread? If not, catch up and profit.

nothing in the grub files to concerning the location of init binary and filesystem is installed

Scimmia wrote:

https://bbs.archlinux.org/viewtopic.php … 3#p1283343

that's just a rewrite of the news feed, there are'nt any unofficial/deprecated binaries or packages

Scimmia · 2013-06-05 15:57:09

yungtrizzle wrote:

Scimmia wrote:
https://bbs.archlinux.org/viewtopic.php … 3#p1283343
that's just a rewrite of the news feed, there are'nt any unofficial/deprecated binaries or packages

No, it's how to do it from an Arch Install Disk for those that couldn't follow directions the first time.

So did your filesystem package install correctly? Are the /bin and /sbin symlinks in place? If not, follow that guide.

If the symlinks are in place, tell us what you did to do the upgrade.

yungtrizzle · 2013-06-05 16:04:50

Scimmia wrote:

yungtrizzle wrote:
Scimmia wrote:
https://bbs.archlinux.org/viewtopic.php … 3#p1283343
that's just a rewrite of the news feed, there are'nt any unofficial/deprecated binaries or packages
No, it's how to do it from an Arch Install Disk for those that couldn't follow directions the first time.
So did your filesystem package install correctly? Are the /bin and /sbin symlinks in place? If not, follow that guide.
If the symlinks are in place, tell us what you did to do the upgrade.

The symlinks are in place running

 ls -la

shows up properly. When I ran the update pacman did its job but I couldn't run any other commands afterward. I did a hard reboot and landed in rootfs zone

Scimmia · 2013-06-05 16:07:38

so /sbin and /bin are both symlinked to usr/bin? If so, we need to know *exactly* what you did earlier.

ie, did you uninstall initscripts or sysvinit? If so, did you make sure you were using systemd or another solution before removing your init system?

Last edited by Scimmia (2013-06-05 16:10:41)

Arch Linux

#1 2013-06-05 12:37:09

[solved] after update - cant boot - /sbin/iinit does not exist

#2 2013-06-05 12:41:32

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#3 2013-06-05 12:51:39

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#4 2013-06-05 12:52:56

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#5 2013-06-05 13:07:36

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#6 2013-06-05 13:10:50

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#7 2013-06-05 13:19:22

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#8 2013-06-05 13:27:40

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#9 2013-06-05 13:55:41

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#10 2013-06-05 14:05:27

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#11 2013-06-05 14:52:31

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#12 2013-06-05 15:19:33

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#13 2013-06-05 15:22:14

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#14 2013-06-05 15:28:52

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#15 2013-06-05 15:29:12

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#16 2013-06-05 15:29:45

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#17 2013-06-05 15:31:25

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#18 2013-06-05 15:31:58

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#19 2013-06-05 15:39:01

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#20 2013-06-05 15:41:38

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#21 2013-06-05 15:46:42

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#22 2013-06-05 15:54:21

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#23 2013-06-05 15:57:09

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#24 2013-06-05 16:04:50

Re: [solved] after update - cant boot - /sbin/iinit does not exist

#25 2013-06-05 16:07:38

Re: [solved] after update - cant boot - /sbin/iinit does not exist

Board footer