kernel panic input/output error

sknd · 2011-12-21 19:23:17

yesterday my laptop (Lenovo 3000 N100) suddenly turned off and was dead for few minutes (unable to turn it on, no baterry led). Then, i was able to turn it on, everything was ok for few seconds - GRUB window, decompressing linux... but few seconds later th computer freezes, with blinking A led (i think A means Alert but im not sure). Here's what's on the screen :

(...)
Booting the kernel.
:: Starting udevd...
done.
:: Running Hook [udev]
:: Triggering uevents...done.
:: Running Hook [uresume]
resume: libgcrypt version 1.5.0
switch_root: failed to execute /sbin/init: Input/output error
[      3.523901] Kernel panic - not syncing: Attempted to kill init!
[      3.523967] Pid: 1, comm: switch_root Not tainted 3.1.5-2-ck #1
[      3.524027] Call trace:
[      3.524088]   [<c0456315>] ? printk+0x1d/0x1f
[      3.524148]   [<c04561f0>] panic+0x66/0x16e
[      3.524221]   [<c013fd2d>] do_exit+0x72d/0x780
[      3.524294]   [<c0140018>] do_group_exit+0x72d/0x780
[      3.524366]   [<c0140098>] sys_exit_group+0x18/0x20
[      3.524439]   [<c045f05f>] sysenter_do_call+0x12/0x28

the same happens when i start other kernels or their fallbacks. I can start the system from cd (i tried archlinux iso) and it boots ok.

What's wrong? Is it hardware problem? Disc? Why grub starts then? Or is it something wrong with initspripts (i just saw on the other computer that there was initscripts upgrade yesterday?
Please help.

EDIT: i tried to chroot from livecd but still get the input/output error:

chroot: failed to run command '/bin/bash': Input/output error

Last edited by sknd (2011-12-21 20:07:56)

ls6678 · 2011-12-23 12:29:59

I have the exact same problem. I can't boot to my Linux system. Anyone? :\

falconindy · 2011-12-23 16:55:57

fsck the root partition from the live CD (before mounting it, of course). It seems like there's either corruption on the FS, or you might have a hardware issue.

Last edited by falconindy (2011-12-23 16:56:09)

ls6678 · 2011-12-23 17:57:21

falconindy wrote:

fsck the root partition from the live CD (before mounting it, of course). It seems like there's either corruption on the FS, or you might have a hardware issue.

Already did it (with fsck.ext4), nothing changed and no reported bad blocks. My machine is working fine with Windows. How can we trace de problem back?

matse · 2011-12-23 18:40:10

Try reinstalling "sysvinit" on your machine (chroot from a live cd to your arch installation, see here.
Greetings
matse

Edit: Forget what I said... didn't read you "edit" in your first post.

Edit2: Verify that your live cd is from which you try to chroot is not corrupted

Last edited by matse (2011-12-23 18:58:52)

ls6678 · 2011-12-23 20:29:21

I tried to chroot and had the same problem: chroot: failed to run command '/bin/bash': Input/output error

I even tried to pacman -r <temp root dir> -Sf sysvinit but it gives me the error:

"call to evecv failed (Input/output error)
error: command failed to execute correctly
call to evecv failed (Exec format error)
error: command failed to execute correctly!

matse · 2011-12-24 00:23:03

That's really a nightmare... just to be sure that we speak of the same thing:
with "/bin/bash" chroot means the "/bin/bash" in the new chroot environment, so according to the wiki this would be "/mnt/arch/bin/bash", not the "/bin/bash" of your live-cd. So is this file existent? You could also try to download the precompile bash package from a mirror, extract it and replace your /mnt/arch/bin/bash with the bash executable from this package, just in case that it might be corrupt... I guess that's really dirty...

ls6678 · 2011-12-24 13:19:05

matse wrote:

That's really a nightmare... just to be sure that we speak of the same thing:
with "/bin/bash" chroot means the "/bin/bash" in the new chroot environment, so according to the wiki this would be "/mnt/arch/bin/bash", not the "/bin/bash" of your live-cd. So is this file existent? You could also try to download the precompile bash package from a mirror, extract it and replace your /mnt/arch/bin/bash with the bash executable from this package, just in case that it might be corrupt... I guess that's really dirty...

Yes, the file exists. If I try to execute it it works without any problem. What a pain in the ass.

matse · 2011-12-24 16:06:01

Hmm that's indeed weird, can you post me a link to the live-cd you are using, I really would like to try to chroot my machine with it, too, just to exclude that there is a problem with the cd.

ls6678 · 2011-12-24 16:11:20

matse wrote:

Hmm that's indeed weird, can you post me a link to the live-cd you are using, I really would like to try to chroot my machine with it, too, just to exclude that there is a problem with the cd.

It's the last CD of ArchLinux: http://darkstar.ist.utl.pt/archlinux/is … x86_64.iso

I think the only way around it is to format root partition...

matse · 2011-12-24 18:07:31

chroot works fine for me with your posted live-cd. I don't know but I would first format root partition when I knew what is the cause of all the trouble. So let's have a look at the disk, does dmesg give any suspicious output when mounting (try mounting with verbose switch "-v") your root partition?

dmesg |grep sdX

Run e2fschk on the unmounted root partition

e2fsck -v -f /dev/sdX

Any output?
Greetings
matse

Last edited by matse (2011-12-24 18:18:07)

ls6678 · 2011-12-26 19:04:50

I know it's not the Arch Way to format the root partition, but I really couldn't afford spend more time without my Linux installation, I had to format it so I could work.

tjbp · 2011-12-31 03:56:12

I just installed Arch on a new system and am having the exact same problem. I receive an input/output error message on boot for /sbin/init, and when chrooting via the latest Arch ISO I get input/output error for /bin/bash. I have fscked the partition - it passed without issue, and I can mount the partition successfully too. I can also directly run /bin/bash on the ISO (so running /mnt/bin/bash) and it works without any errors. I'm really confused...

Last edited by tjbp (2011-12-31 03:59:42)

matse · 2012-01-05 15:09:12

Seems that someone with similiar issue could solve the problem by "manually reinstalling" glibc, since there are no other proposals, you maybe want to give it a try...

Last edited by matse (2012-01-05 15:10:54)

Arhat · 2012-01-22 11:50:56

Hi!

I'm experiencing a similar problem as the thread-starter.

Trying to chroot gave me the same error message:

chroot: failed to run command '/bin/bash': Input/output error

I then tried to manually reinstall glibc as mentioned in the thread with the similiar issue, but now I'm left with

Floating point exception

when I try to chroot.

messages.log tells me:

bash[......] trap divide error ip:.... sp:.... error:0 in libc-2.15.so[......]

Excerpt of last entries in pacman.log:

Running 'pacman -Syu'
...
upgraded linux-api-headers (3.1.4-1 -> 3.1.6-1)
...
upgraded glibc (2.14.1-2 -> 2.15-3)
upgraded libarchive (2.8.5-2 -> 3.0.3-2)
...
upgraded pacman (3.5.4-4 -> 4.0.1-4)

Any ideas what went wrong probably reinstalling glibc?
Any suggestions of other things to try to fix the system?

(Filesystem have been checked, no errors reported there.
Installation media was downloaded using this link:
http://www.archlinux.org/iso/2011.08.19 … so.torrent )

matse · 2012-01-22 12:35:16

Hello,
just to be sure, you didn't "reinstall" glibc with your pacman-cached version and you downloaded the right package for your system architecture?

Further have you seen this thread?

stracing your chroot command via

sudo strace -e trace=open chroot . /bin/bash

seems to have given valuable debugging output there, so you might give this a try.

Arhat · 2012-01-22 13:43:01

matse wrote:

Hello,
just to be sure, you didn't "reinstall" glibc with your pacman-cached version and you downloaded the right package for your system architecture?

The system architecture is correct.
However, yes I used the pacman-cached version to reinstall glibc.

matse wrote:

stracing your chroot command via
sudo strace -e trace=open chroot . /bin/bash
seems to have given valuable debugging output there, so you might give this a try.

Result of strace -e trace=open chroot . /bin/bash:

open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/locale/en_US.UTF-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en_US.utf8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en_US/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en.UTF-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en.utf8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libreadline.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libncursesw.so.5", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/dev/tty", O_RDWR|O_NONBLOCK)     = 3
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
--- {si_signo=SIGFPE, si_code=FPE_INTDIV, si_addr=0x7f6d662c1712} (Floating point exception) ---
+++ killed by SIGFPE +++
Floating point exception

The output is similar to the one in the thread you were referring to:

matse wrote:

Further have you seen this thread?

(Which I missed, thanks for pointing me towards it)

deleting ./usr/lib/locale/locale-archive allows me to chroot.

Thanks a lot.

matse · 2012-01-22 18:37:32

@Arhat: and can you also boot again?

Arhat · 2012-01-23 07:36:53

matse wrote:

@Arhat: and can you also boot again?

Yes, my system is booting again.

I had to reinstall two other packages manually:

pacman

and

libarchive

but now my system is up and running again.

tjbp · 2012-02-02 02:29:19

This also fixed it for me, thanks.

Rather than unpacking manually I used a live CD and mounted my root partition on /mnt, then ran:

# pacman -U /path/to/latest/glibc/package -r /mnt

MisterAnderson · 2012-08-12 13:16:46

Hey, I ran this instead after mounting root and other filesystems in /mnt from the live cd (I got a tonne of file still exists errors without -f):

# rm /mnt/usr/lib/locale/locale-archive
# pacman -r /mnt -Syf glibc
# pacman -r /mnt -S libarchive pacman

After that I could chroot/boot again. I didn't use --force when doing the glibc upgrade the first time (followed the wiki's instructions, worked on my other comps), the upgrade just failed halfway through then every command got a lovely "/usr/bin/[program] does not exist" with every command given. Thanks for this thread!

Arch Linux

#1 2011-12-21 19:23:17

kernel panic input/output error

#2 2011-12-23 12:29:59

Re: kernel panic input/output error

#3 2011-12-23 16:55:57

Re: kernel panic input/output error

#4 2011-12-23 17:57:21

Re: kernel panic input/output error

#5 2011-12-23 18:40:10

Re: kernel panic input/output error

#6 2011-12-23 20:29:21

Re: kernel panic input/output error

#7 2011-12-24 00:23:03

Re: kernel panic input/output error

#8 2011-12-24 13:19:05

Re: kernel panic input/output error

#9 2011-12-24 16:06:01

Re: kernel panic input/output error

#10 2011-12-24 16:11:20

Re: kernel panic input/output error

#11 2011-12-24 18:07:31

Re: kernel panic input/output error

#12 2011-12-26 19:04:50

Re: kernel panic input/output error

#13 2011-12-31 03:56:12

Re: kernel panic input/output error

#14 2012-01-05 15:09:12

Re: kernel panic input/output error

#15 2012-01-22 11:50:56

Re: kernel panic input/output error

#16 2012-01-22 12:35:16

Re: kernel panic input/output error

#17 2012-01-22 13:43:01

Re: kernel panic input/output error

#18 2012-01-22 18:37:32

Re: kernel panic input/output error

#19 2012-01-23 07:36:53

Re: kernel panic input/output error

#20 2012-02-02 02:29:19

Re: kernel panic input/output error

#21 2012-08-12 13:16:46

Re: kernel panic input/output error

Board footer