Description of problem: During every boot I see the following messages. They didn't appear while I was still running F11, but I recently updated to rawhide and they started showing up. Scares me a bit. Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-307 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 122 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 123 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-0, logical block 124 Oct 28 08:41:13 t500 kernel: dracut: luksOpen /dev/sda2 luks-819e08b9-e376-4739-b943-12547fbaab57 Oct 28 08:41:13 t500 kernel: __ratelimit: 33 callbacks suppressed Oct 28 08:41:13 t500 kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-357 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 60 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 61 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 60 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 61 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 122 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 123 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 122 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 123 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 8 Oct 28 08:41:13 t500 kernel: Buffer I/O error on device dm-1, logical block 9 Version-Release number of selected component (if applicable): kernel-2.6.31.5-96.fc12.x86_64 How reproducible: always Steps to Reproduce: 1. boot 2. 3. Actual results: lots of I/O errors Expected results: no I/O errors Additional info:
Does the system work otherwise?
yes, I haven't experienced any problems
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Created attachment 369753 [details] buffer i/o errors, f12 release same here, f12 release on i386, LUKS root
Ditto, running an ext4 /boot partition with LVM of /dev/sda2 and a 28 GB partition for /usr at the back of it all. All possible partitions encrypted. Kernel is a little different for mine, I'm running 2.6.31.6-134.fc12.x86_64 so I can only assume this release didn't fix it for you. I was more than a little concerned my hard drive was failing since I've seen that message before on an Ubuntu 9.04 drive that was going south. Thankfully, it appears otherwise.
Same in here.. also hibernating does not work anymore with F12 with encrypted swap as the computer is unable to reboot after hibernation -> requires recovery on ext3. Buffer I/O error on device dm-3, logical block 124 device-mapper: ioctl: unable to remove open device temporary-cryptsetup-486 Buffer I/O error on device dm-3, logical block 124 Buffer I/O error on device dm-3, logical block 124 Buffer I/O error on device dm-3, logical block 124 Buffer I/O error on device dm-3, logical block 124 Buffer I/O error on device dm-3, logical block 124 Buffer I/O error on device dm-3, logical block 116 Buffer I/O error on device dm-3, logical block 117 Buffer I/O error on device dm-3, logical block 118 Buffer I/O error on device dm-3, logical block 119 EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery.
I've just run into this bug by chance... This should be solved with new version of dracut, I hope - dracut-003-1.fc12. Please try this one (..see also bug #527056).
It seems that this new version is not available in the updates-testing anymore.
Just want to state, that i run into it, too. Default install via anaconda with a luks lv as "/home". Seems that giving some time after the passwd input appears, help to avoid this (sometimes). dracut: dracut-002-13.4.git8f397a9b.fc12 udev: starting version 145 dracut: Starting plymouth daemon dracut: Scanning devices sda2 for LVM volume groups dracut: Reading all physical volumes. This may take a while... dracut: Found volume group "vg_hurricane" using metadata type lvm2 dracut: 3 logical volume(s) in volume group "vg_hurricane" now active dracut: luksOpen /dev/dm-1 luks-56f7753b-4677-4a13-af75-4efe3552cf45 Intel AES-NI instructions are not detected. padlock: VIA PadLock not detected. Buffer I/O error on device dm-3, logical block 64 device-mapper: ioctl: unable to remove open device temporary-cryptsetup-280 Buffer I/O error on device dm-3, logical block 65 Buffer I/O error on device dm-3, logical block 66 Buffer I/O error on device dm-3, logical block 67 Buffer I/O error on device dm-3, logical block 68 Buffer I/O error on device dm-3, logical block 69 Buffer I/O error on device dm-3, logical block 70 Buffer I/O error on device dm-3, logical block 71 Buffer I/O error on device dm-3, logical block 72 Buffer I/O error on device dm-3, logical block 73 EXT4-fs (dm-0): INFO: recovery required on readonly filesystem EXT4-fs (dm-0): write access will be enabled during recovery EXT4-fs (dm-0): barriers enabled kjournald2 starting: pid 334, dev dm-0:8, commit interval 5 seconds EXT4-fs (dm-0): delayed allocation enabled EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs (dm-0): recovery complete EXT4-fs (dm-0): mounted filesystem with ordered data mode dracut: Mounted root filesystem /dev/mapper/vg_hurricane-lv_root dracut: Loading SELinux policy
I see similar messages, although only for one of my two luks volumes: kernel-PAE-2.6.31.6-166.fc12.i686 dracut-002-13.4.git8f397a9b.fc12.noarch dracut: luksOpen /dev/sda2 luks-daea401a-8197-4bcf-9ddf-ce3f92a044b0 padlock: VIA PadLock not detected. Buffer I/O error on device dm-0, logical block 64 Buffer I/O error on device dm-0, logical block 65 Buffer I/O error on device dm-0, logical block 66 Buffer I/O error on device dm-0, logical block 67 Buffer I/O error on device dm-0, logical block 68 Buffer I/O error on device dm-0, logical block 69 Buffer I/O error on device dm-0, logical block 70 Buffer I/O error on device dm-0, logical block 71 Buffer I/O error on device dm-0, logical block 72 Buffer I/O error on device dm-0, logical block 73 device-mapper: ioctl: unable to remove open device temporary-cryptsetup-244 dracut: luksOpen /dev/sdb1 luks-b94a0dc2-b333-4196-9e15-0cd94b594473 dracut: Scanning devices dm-0 dm-1 for LVM volume groups As above, system functionality is not impacted.
I've been getting similar errors for some time. Version-Release number of selected component (if applicable): kernel-2.6.31.6-166.fc12.x86_64.rpm Actual results: Dec 17 11:01:16 hermes kernel: sr 6:0:0:0: Attached scsi generic sg4 type 5 Dec 17 11:01:16 hermes kernel: Intel AES-NI instructions are not detected. Dec 17 11:01:16 hermes kernel: padlock: VIA PadLock not detected. Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 97 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 98 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 99 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 100 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 101 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 102 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 103 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 104 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 105 Dec 17 11:01:16 hermes kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-280 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-0, logical block 10 6 Dec 17 11:01:16 hermes kernel: dracut: Scanning devices sda7 sda8 sda9 sdc1 for LVM volume groups Dec 17 11:01:16 hermes kernel: dracut: Reading all physical volumes. This may take a while... Dec 17 11:01:16 hermes kernel: dracut: Found volume group "hermesVG" using metadata type lvm2 Dec 17 11:01:16 hermes kernel: dracut: 9 logical volume(s) in volume group "hermesVG" now active Dec 17 11:01:16 hermes kernel: dracut: luksOpen /dev/dm-9 luks-4dd1e71c-3f75-4791-96d0-68ed147b1c9a Dec 17 11:01:16 hermes kernel: dracut: luksOpen /dev/dm-5 luks-096916a2-9d9e-4222-b360-75b33fe6ecbd Dec 17 11:01:16 hermes kernel: dracut: luksOpen /dev/dm-7 luks-0e78e067-b0a5-4f36-90ca-65e2bfee2599 Dec 17 11:01:16 hermes kernel: __ratelimit: 158 callbacks suppressed Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 34 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 35 Dec 17 11:01:16 hermes kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-465 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 36 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 37 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 38 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 39 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 40 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 41 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 42 Dec 17 11:01:16 hermes kernel: Buffer I/O error on device dm-12, logical block 43 Dec 17 11:01:16 hermes kernel: EXT4-fs (dm-1): INFO: recovery required on readonly filesystem Additional info: I don't know how to find out the corresponding partitions, but based on the output of "dmsetup info" and the content of /dev I think that dm-12 is a LUKS encrypted NTFS partition (/dev/sdd5), while dm-0 is a LUKS encrypted Logical Volume. Other encrypted LVs work fine. All my hard drives should be working fine, I've run a "smartctl -t long" test a couple of days ago without any errors. I have also run a quick dd test at the beginning of these partitions without any errors. In case it matter, I'm using dracut-002-13.4.git8f397a9b.fc12.noarch.rpm.
With dracut currently available in f12, i.e. dracut-002-13.4.git8f397a9b.fc12 my system (using dm-crypt on /home) displayed the previously mentioned I/O errors twice and then locked up. Updating to dracut-003-1.fc12.noarch from Koji fixed this. Is it possible to repush 003-1 to updates-testing and then to updates or is there another problem with that build?
I'm using kernel-2.6.31.9-174.fc12.x86_64.rpm with dracut-002-13.4.git8f397a9b.fc12.noarch.rpm and the problem seems to be gone. On the other hand I'm getting "remove ioctl failed: Device or resource busy" errors: dracut: luksOpen /dev/sdd5 luks-acbab528-412f-44cc-8f95-ed468704ec9f device-mapper: remove ioctl failed: Device or resource busy Key slot 1 unlocked. dracut: Scanning devices sda7 sda8 sda9 sdc1 for LVM volume groups dracut: Reading all physical volumes. This may take a while... dracut: Found volume group "hermesVG" using metadata type lvm2 dracut: 9 logical volume(s) in volume group "hermesVG" now active dracut: luksOpen /dev/dm-7 luks-0e78e067-b0a5-4f36-90ca-65e2bfee2599 No key available with this passphrase. device-mapper: remove ioctl failed: Device or resource busy Key slot 0 unlocked.
Created attachment 434246 [details] dmesg - buffer i\o errors Am getting this on an F12.x86 guest on an F13.x86_64 host. Fully updated f12 with updates-testing
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
kernel:2.6.32-220.el6.x86_64 dracut:dracut-004-256.el6.noarch [root@localhost ~]# dmesg | grep error gdm-smartcard-w[3015]: segfault at 7f0968aa1e40 ip 0000003895a57256 sp 00007f096 type=1400 audit(1368897554.709:4): avc: denied { create } for pid=3033 comm="ystem_u:object_r:admin_home_t:s0 tclass=file type=1400 audit(1368897554.709:5): avc: denied { create } for pid=3033 comm="context=system_u:object_r:admin_home_t:s0 tclass=file Buffer I/O error on device dm-0, logical block 1272549248 Buffer I/O error on device dm-0, logical block 1272549249 Buffer I/O error on device dm-0, logical block 1272549250 Buffer I/O error on device dm-0, logical block 1272549251 Buffer I/O error on device dm-0, logical block 1272549252 Buffer I/O error on device dm-0, logical block 1272549253 Buffer I/O error on device dm-0, logical block 1272549254 Buffer I/O error on device dm-0, logical block 1272549255 Buffer I/O error on device dm-0, logical block 1272549248 Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 1 Buffer I/O error on device dm-0, logical block 2 Buffer I/O error on device dm-0, logical block 3 Buffer I/O error on device dm-0, logical block 4 Buffer I/O error on device dm-0, logical block 5 Buffer I/O error on device dm-0, logical block 6 Buffer I/O error on device dm-0, logical block 7 Buffer I/O error on device dm-0, logical block 8 Buffer I/O error on device dm-0, logical block 9 Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 1 Buffer I/O error on device dm-0, logical block 2 Buffer I/O error on device dm-0, logical block 3 Buffer I/O error on device dm-0, logical block 4 Buffer I/O error on device dm-0, logical block 5 Buffer I/O error on device dm-0, logical block 6 Buffer I/O error on device dm-0, logical block 7 Buffer I/O error on device dm-0, logical block 8 Buffer I/O error on device dm-0, logical block 9