/bin/* : cannot execute binary file (and an openrc problem) [gentoo]

namish · 03-30-2012, 05:38 PM

I was getting the aforementioned error on my computer. Between when things were working and when I started getting this error, I had made no changes to the computer: no new packages installed, no new kernel, no changes to config files.

I decided to reboot, and now I can't even boot into the system. It starts OpenRC and then I get errors that mainly say "/lib64/rc/init.d/*: Read-only file system." I did an fsck on / and didn't see any issues. I can also mount all my partitions and read files from them in the rescue disk. I assume the two problems are related, since they popped up simultaneously. Any ideas?

bigrigdriver · 04-01-2012, 09:48 AM

In maintaining a functioning GNU/Linux system, it's vital that one learns to use a web browser to research answers to questions. Searching for "gentoo openrc errors", I found this in the Gentoo documentation which reveals the cause of the problem, and the solution.

Cause:

Quote:

2. Migration to OpenRC

Migration to OpenRC is fairly straightforward; it will be pulled in as part of your regular upgrade process by your package manager. The most important step actually comes after you install the new >=sys-apps/baselayout-2 and sys-apps/openrc packages. It is critical that you run dispatch-conf and ensure your /etc is up to date before rebooting. Failure to do so will result in an unbootable system and will require the use of the Gentoo LiveCD to perform the steps below to repair your system.

Solution: the full text from which the quote above is an excerpt.
http://www.gentoo.org/doc/en/openrc-migration.xml

Good luck with restoring your system to a bootable state.

namish · 04-02-2012, 12:38 PM

The 'solution' you googled does not apply in my circumstances, since I have done nothing to modify any of /etc, as I mentioned in my post. This is not a new installation. There are no changes that dispatch-conf picks up. So please, read things more carefully next time and hold back on the condescending remarks.

At any rate, here is my fstab and a dmesg inside the chrooted system. There seems the be some clashing of my windows partition (/dev/sda2) going on, but I can't quite tell what is going on.

fstab (excluding some network drives):

Code:

/dev/sda5		/boot		ext2		noauto,noatime	1 2
/dev/sda7		/		ext3		noatime		0 1
/dev/sda6		swap		swap		sw		0 0
/dev/cdrom		/mnt/cdrom	auto		noauto,ro,users	0 0
/dev/fd0		/mnt/floppy	auto		noauto,users	0 0

dmesg: http://pastebin.com/C8mXndzu

namish · 04-04-2012, 09:25 AM

bump.

TKH · 04-04-2012, 11:16 AM

Possibly, it is a problem with processor architechture. A 32-bit processor cannot run a 64-bit binary.

namish · 04-04-2012, 11:32 AM

Quote:

Originally Posted by TKH

Possibly, it is a problem with processor architechture. A 32-bit processor cannot run a 64-bit binary.

Yeah, that seems to be the most common cause with this particular error, but it isn't the case here. The installation had been working for months prior.

namish · 04-07-2012, 01:49 PM

bump...