Bug 585918 - DeviceError: ('device has not been created', 'sda3')
Summary: DeviceError: ('device has not been created', 'sda3')
Status: CLOSED DUPLICATE of bug 583290
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-26 12:29 UTC by Daniel Qarras
Modified: 2010-05-10 12:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-10 12:17:54 UTC
Type: ---

Attachments (Terms of Use)
anaconda crash dump (316.59 KB, text/plain)
2010-04-26 12:29 UTC, Daniel Qarras
no flags Details

Description Daniel Qarras 2010-04-26 12:29:09 UTC
Created attachment 409165 [details]
anaconda crash dump

Description of problem:
When installing Fedora 13 Beta Anaconda crashed during partitioning and generated the attached crash dump. I'm not able to check from the dump whether this issue has been reported already before or not.

Comment 1 Daniel Qarras 2010-04-26 12:29:51 UTC
It should be mentioned that after the crash I manually created the partitions and the next installation finished normally.

Comment 2 Chris Lumens 2010-04-27 14:52:45 UTC
anaconda 13.37.2 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/devices.py", line 607, in setup
    raise DeviceError("device has not been created", self.name)
  File "/usr/lib/anaconda/storage/deviceaction.py", line 264, in execute
  File "/usr/lib/anaconda/storage/devicetree.py", line 672, in processActions
  File "/usr/lib/anaconda/storage/__init__.py", line 290, in doIt
  File "/usr/lib/anaconda/packages.py", line 109, in turnOnFilesystems
  File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
  File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked
DeviceError: ('device has not been created', 'sda3')

Comment 3 Chris Lumens 2010-04-30 19:45:15 UTC
Can you explain what you were trying to do during partitioning?  Is RAID involved at all?

Comment 4 Daniel Qarras 2010-05-03 18:59:11 UTC
> Can you explain what you were trying to do during partitioning?  Is RAID
> involved at all?

No RAID or even LVM involved at all. I have a laptop with two Windows related partitions and before installation attempt I had /boot, swap and / and I was from the installer GUI deleting those three partitions and trying to create two new primary partitions, swap and /.

After the installer crashed I created those partitions by hand with fdisk and on the next attempt the installer managed to format them. fdisk -l now gives:

root@localhost:~# fdisk -l

Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa1dfa2ed

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         383     3076416   12  Compaq diagnostics
/dev/sda2             384       10870    84236827+   7  HPFS/NTFS
/dev/sda3           10871       11003     1068322+  82  Linux swap / Solaris
/dev/sda4   *       11004       12161     9301635   83  Linux

When I used fdisk few megabytes were shown as unallocated/free space by the installer during the second attempt but when the installer was trying to do partitioning all the space was used (so fdisk and anaconda create slightly different kind of partition layout).


Comment 5 Hans de Goede 2010-05-10 12:17:54 UTC
Looking at the log, this is caused by to aggressive pruning of device actions, which is fixed by this commit:

*** This bug has been marked as a duplicate of bug 583290 ***

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