Bug 1146692 - OSError: [Errno 2] Ingen sådan fil eller filkatalog
Summary: OSError: [Errno 2] Ingen sådan fil eller filkatalog
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f219393a29d25a655e7a42d04d8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-25 18:55 UTC by Kris
Modified: 2015-05-16 23:23 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-25 19:06:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (1.67 MB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: anaconda.log (30.88 KB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: environ (538 bytes, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: journalctl (948.70 KB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: lsblk_output (4.22 KB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: nmcli_dev_list (1.95 KB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: os_info (377 bytes, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: program.log (75.72 KB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: storage.log (552.35 KB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: ifcfg.log (6.63 KB, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details
File: packaging.log (135 bytes, text/plain)
2014-09-25 18:55 UTC, Kris
no flags Details

Description Kris 2014-09-25 18:55:01 UTC
Description of problem:
I ran the installer.
Configured everything to my needs - automatic partition (encrypted), one user. Plain and simple.
When the installation was at about 18% it stalled for a little while and then crashed the installer.

Version-Release number of selected component:
anaconda-core-21.48.6-1.fc21.x86_64

The following was filed automatically by anaconda:
anaconda 21.48.6-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
    raise child_exception
  File "/usr/lib64/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iutil.py", line 137, in _run_program
    preexec_fn=chroot, cwd=root, env=env)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iutil.py", line 193, in execWithRedirect
    log_output=log_output, binary_output=binary_output)[0]
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iutil.py", line 171, in execInSysroot
    return execWithRedirect(command, argv, stdin=stdin, root=getSysroot())
  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 157, in install
    ["--rpmposttrans", kernel])
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 205, in doInstall
    payload.install()
  File "/usr/lib64/python2.7/threading.py", line 766, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)
OSError: [Errno 2] Ingen sådan fil eller filkatalog

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   initrd=/ubninit root=live:UUID=24C1-8F54 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=/ubnkern 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.16.1-301.fc21.x86_64
other involved packages: python-libs-2.7.8-4.1.fc21.x86_64
product:        Fedora
release:        Fedora release 21 (Twenty One)
type:           anaconda
version:        21

Comment 1 Kris 2014-09-25 18:55:10 UTC
Created attachment 941239 [details]
File: anaconda-tb

Comment 2 Kris 2014-09-25 18:55:12 UTC
Created attachment 941240 [details]
File: anaconda.log

Comment 3 Kris 2014-09-25 18:55:13 UTC
Created attachment 941241 [details]
File: environ

Comment 4 Kris 2014-09-25 18:55:35 UTC
Created attachment 941242 [details]
File: journalctl

Comment 5 Kris 2014-09-25 18:55:37 UTC
Created attachment 941243 [details]
File: lsblk_output

Comment 6 Kris 2014-09-25 18:55:38 UTC
Created attachment 941244 [details]
File: nmcli_dev_list

Comment 7 Kris 2014-09-25 18:55:39 UTC
Created attachment 941245 [details]
File: os_info

Comment 8 Kris 2014-09-25 18:55:41 UTC
Created attachment 941246 [details]
File: program.log

Comment 9 Kris 2014-09-25 18:55:45 UTC
Created attachment 941247 [details]
File: storage.log

Comment 10 Kris 2014-09-25 18:55:46 UTC
Created attachment 941248 [details]
File: ifcfg.log

Comment 11 Kris 2014-09-25 18:55:47 UTC
Created attachment 941249 [details]
File: packaging.log

Comment 12 David Shea 2014-09-25 19:06:17 UTC
Your hard drive is failing. The error occurred because the kernel remounted your filesystem as read-only part of the way through the install.

Sep 25 14:49:25 localhost kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 25 14:49:25 localhost kernel: sd 0:0:0:0: [sda]
Sep 25 14:49:25 localhost kernel: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 25 14:49:25 localhost kernel: sd 0:0:0:0: [sda] CDB:
Sep 25 14:49:25 localhost kernel: Write(10): 2a 00 08 a5 c0 00 00 00 08 00
Sep 25 14:49:25 localhost kernel: Buffer I/O error on device dm-6, logical block 0
Sep 25 14:49:25 localhost kernel: lost page write due to I/O error on dm-6
Sep 25 14:49:25 localhost kernel: EXT4-fs error (device dm-6): ext4_journal_check_start:56: Detected aborted journal
Sep 25 14:49:25 localhost kernel: EXT4-fs (dm-6): Remounting filesystem read-only
Sep 25 14:49:25 localhost kernel: EXT4-fs (dm-6): previous I/O error to superblock detected
Sep 25 14:49:25 localhost kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 25 14:49:25 localhost kernel: sd 0:0:0:0: [sda]
Sep 25 14:49:25 localhost kernel: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 25 14:49:25 localhost kernel: sd 0:0:0:0: [sda] CDB:
Sep 25 14:49:25 localhost kernel: Write(10): 2a 00 08 a5 c0 00 00 00 08 00
Sep 25 14:49:25 localhost kernel: Buffer I/O error on device dm-6, logical block 0

Comment 13 readdytop 2014-12-22 03:26:26 UTC
Another user experienced a similar problem:

I have been unable to completely run the fedora 21 installer on a new build system. The failure seems to be at different places each attempt. I get an error message anywhere from immediately upon starting the installer, to this instance, where the disk partitions seem to have completed and software installation had started. Each time I have to quit and restart the process.

My system is:
ASUS M5A99X EVO R.2 motherboard
AMD FX8350 CPU
32GB RAM
Samsung 840 EVO 250GB SSD

The SSD may be involved in the problem, but I'm not sure. I have repartioned it multiple ways with different, unsuccessful, results. It is not clear if these changes were the culprit as I have also gotten seemingly random installer errors without making changes to the SSD.

cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-21-5 ro rd.live.image quiet rhgb
hashmarkername: anaconda
kernel:         3.17.4-301.fc21.x86_64
other involved packages: python-libs-2.7.8-7.fc21.x86_64
package:        anaconda-core-21.48.21-1.fc21.x86_64
product:        Fedora"
reason:         OSError: [Errno 2] No such file or directory
release:        Fedora release 21 (Twenty One)
version:        Fedora

Comment 14 Paul Finnigan 2015-02-24 14:53:40 UTC
Another user experienced a similar problem:

Installing Fedora 21 Workstation into a Boxes VM

cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 
hashmarkername: anaconda
kernel:         3.17.4-301.fc21.x86_64
other involved packages: python-libs-2.7.8-7.fc21.x86_64
package:        anaconda-core-21.48.21-1.fc21.x86_64
product:        Fedora"
reason:         OSError: [Errno 2] No such file or directory
release:        Fedora release 21 (Twenty One)
version:        Fedora

Comment 15 Micah J. Kimbrough 2015-05-16 23:23:27 UTC
Another user experienced a similar problem:

installing Fedora 21 Workstation on a external hard drive.

cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-21-5 ro rd.live.image quiet rhgb nomodeset
hashmarkername: anaconda
kernel:         3.17.4-301.fc21.x86_64
other involved packages: python-libs-2.7.8-7.fc21.x86_64
package:        anaconda-core-21.48.21-1.fc21.x86_64
product:        Fedora"
reason:         OSError: [Errno 2] No such file or directory
release:        Fedora release 21 (Twenty One)
version:        Fedora


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