[SOLVED] Can't run kernel 3.10: fsck.ext4 reports exec error

RandomTroll · 07-01-2013, 02:11 AM

When I boot with kernel 3.10 it halts with:

Quote:

fsck.ext4: exec format error

I go into administrative mode, e2fsck reports no problems with my boot volume. I reboot into 3.9.8 without problem.

Anyone else with a problem with 3.10? Or is this a problem with disk utilities?

TobiSGD · 07-01-2013, 04:35 AM

Running kernel 3.10 (built with the standard "huge" config files and make oldconfig) with the radeon power-management patches from Alex Deucher on Slackware -current (32 and 64 bit) without any problems.

RandomTroll · 07-01-2013, 10:47 AM

What does 'exec format error' mean? I would think it meant that the program was compiled with an unsupported format, like 64-bit for a 32-bit system.

I can run fsck.ext4 in kernel 3.10 when I log into administrative mode when this happens: why can't it run during boot?

TobiSGD · 07-01-2013, 07:27 PM

Are you using an initrd? If so, may it be possible that your initrd somehow is not the right one for your kernel? That would explain why fsck behaves different at boot time (running from the initrd).

RandomTroll · 07-02-2013, 01:39 AM

I'm not using an initrd. I boot with the same kernel I run. 'fastboot', bypassing running fsck at startup, works.

RandomTroll · 07-03-2013, 08:30 PM

Uninstalling the e2fsprogs package then building it (same version) solved this problem. I used the default configuration, which builds in more libraries than the package version.