Bug 1053281 - IOException: Input/output error during read on /dev/sda [NEEDINFO]
Summary: IOException: Input/output error during read on /dev/sda
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:04bcc6eff86cdc2b71b0d371968...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-14 22:17 UTC by revcoyote
Modified: 2014-03-17 18:44 UTC (History)
13 users (show)

Fixed In Version:
Clone Of: 1009612
Environment:
Last Closed: 2014-03-17 18:44:02 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)

Description revcoyote 2014-01-14 22:17:13 UTC
+++ This bug was initially created as a clone of Bug #1009612 +++

Version-Release number of selected component:
anaconda-20.15-1

The following was filed automatically by anaconda:
anaconda 20.15-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/parted/disk.py", line 213, in commit
    return self.__disk.commit()
  File "/usr/lib64/python2.7/site-packages/parted/decorators.py", line 41, in new
    ret = fn(*args, **kwds)
  File "/usr/lib/python2.7/site-packages/blivet/formats/disklabel.py", line 292, in commit
    self.partedDisk.commit()
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 1605, in _destroy
    self.disk.originalFormat.commit()
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 822, in destroy
    self._destroy()
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 318, in execute
    self.device.destroy()
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 237, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 310, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 169, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 142, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run
    threading.Thread.run(self, *args, **kwargs)
IOException: Input/output error during read on /dev/sda

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img ramdisk_size=9216 root=live:http://192.168.1.13/squashfs.img repo=http://192.168.1.13/fc20/os BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.11.0-300.fc20.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        20-Alpha

Potential duplicate: bug 973747

--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:11 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:16 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:19 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:23 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:26 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:29 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:32 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:37 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:41 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:45 EDT ---



--- Additional comment from Chuck Forsberg on 2013-09-18 13:22:51 EDT ---



--- Additional comment from David Shea on 2013-09-18 13:26:50 EDT ---

There appears to be a problem with your drive. In syslog:

17:18:08,361 ERR kernel:[   48.148036] ata6.00: failed command: READ FPDMA QUEUED
17:18:08,361 ERR kernel:[   48.148041] ata6.00: cmd 60/08:08:10:28:d0/00:00:09:00:00/40 tag 1 ncq 4096 in
17:18:08,361 ERR kernel:[   48.148041]          res 40/00:f0:f8:28:d0/00:00:09:00:00/40 Emask 0x1 (device error)
17:18:08,361 ERR kernel:[   48.148044] ata6.00: status: { DRDY }

--- Additional comment from  on 2013-10-12 14:00:23 EDT ---

this is a bug, i have the exact same error message.
my drive is monitored by SMART and has no error.
closing bugs as "not a bug" will prevent others in reporting the same behaviour as the reporting tool in f20 only checks the state of the existing one and then aborts without sending the relevant data.

fedora goes more and more into an unstable state where i think about switching to another distri, even if i liked fedora a lot.

Comment 1 revcoyote 2014-01-14 22:20:34 UTC
I am afraid this is a bug. It's happening to me too. You might want to keep it open and see how many hits you get. Because of the this error I am going to have to try the install with a different distro.

Comment 2 Vratislav Podzimek 2014-01-15 16:17:38 UTC
Then consider moving this to kernel because anaconda can hardly do anything with such errors.

Comment 3 Justin M. Forbes 2014-02-24 14:00:54 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.13.4-200.fc20.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 4 Justin M. Forbes 2014-03-17 18:44:02 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.


Note You need to log in before you can comment on or make changes to this bug.