Bug 649378
| Summary: | AttributeError: 'NoneType' object has no attribute 'name' | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John F <johnhford> |
| Component: | parted | Assignee: | Brian Lane <bcl> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | alf, asaone1, awilliam, bcl, cameroncros, dlehman, donchurch, dzrudy, fedora, franta, giles, hdegoede, itzvasanth, jacquesstud04, jlaska, johnhford, jonathan, linux, mark, phil.pishioneri, reub2000, rhe, sanchoooo, tommy, vanmeeuwen+fedora |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | anaconda_trace_hash:1c9d6ac6d84cd602fb6c6edd6aca61c5e60712e844a01a7ec8f96e430c6ecb6d | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 639138 | Environment: | |
| Last Closed: | 2012-08-16 17:07:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
John F
2010-11-03 16:32:56 UTC
to be clear, this is happening with the X86-64 install dvd, not the livecd Also, this is with 'nodmraid' on the command line. I haven't ever had a raid on this system and none of these drives have been members in a raid volume this is *also* happening with the live cd! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers If you don't have a RAID array, this isn't the same as the bug you cloned, I don't think. Can you copy the backtrace over to this bug? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers i have tried: -setting ide controller to 'IDE' mode -combinations of nodmraid, libata.dma=0, acpi=off, nodma=ide -both dvd and livecd -pulling my hair out None of these work for me. https://bugzilla.redhat.com/attachment.cgi?id=457490 is from my system I'm changing the component to anaconda. I confirmed that the distribution DVD does include the correct parted version so given that and that this isn't a RAID we need to do some more digging to find the cause. Created attachment 457522 [details]
traceback from reporter
Some progress. This disk used to be a Windows 7 64Bit boot volume. Looking at my traceback, I saw part: parted.Partition instance -- disk: <parted.disk.Disk object at 0x15bf550> fileSystem: None number: 1 path: /dev/sda1 type: 0 name: Microsoft reserved partition active: True busy: False geometry: <parted.geometry.Geometry object at 0x7f4da9a92c50> PedPartition: <_ped.Partition object at 0x15cf0b0> in the area of the backtrace that caused this crash. I booted into the LiveCD and zero'd my mbr using dd if=/dev/zero of=/dev/sda bs=512 count=1 and again with bs=100M just to be sure to wipe the MBR and a potential GPT. After doing that, anaconda in the install DVD asked me to reinitialize the drive, which it hadn't done before. I am now able to get to the partitioning stage. It would seem like reusing a Win 7 64bit boot drive for Fedora is part of the problem here. Parted was showing an sda1 partition that was not detected by the kernel and/or udev. If parted and the kernel cannot agree about what's on the disk, anaconda is not going to be able to do much with the system. that sounds reasonable. if the kernel and udev don't find it, maybe throwing up an error that suggests putting a new partition table on the drive would help. Created attachment 457908 [details]
Attached traceback automatically from anaconda.
Created attachment 457914 [details]
Attached traceback automatically from anaconda.
Reassigning based on comment #11, though perhaps there's a better place for this one to go. Created attachment 458263 [details]
Attached traceback automatically from anaconda.
Anaconda from the install DVD threw up this error for me when telling the installer to use all free space and selected to review the partitions prior to creation. Using the 64 bit dvd. This error seems to not show up when installing via a Virtual Machine but is present when trying to install natively. I just remembered that the partition that seemed to cause this issue that I mentioned in comment 10 had been erased long before I tried to install fedora on the system. That would suggest that parted was picking up a partition that didn't exist on the disk but did a long time ago. I guess the steps to reproduce this would be: 1. install windows 7 64 bit using the entire disk 2. use another windows 7 system to erase the entire disk and create one large ntfs partition 3. try to install fedora 14. Created attachment 463291 [details]
Attached traceback automatically from anaconda.
Created attachment 463362 [details]
Attached traceback automatically from anaconda.
Created attachment 463421 [details]
Attached traceback automatically from anaconda.
Created attachment 463830 [details]
Attached traceback automatically from anaconda.
Created attachment 471008 [details]
Attached traceback automatically from anaconda.
Created attachment 477148 [details]
Attached traceback automatically from anaconda.
Created attachment 479837 [details]
Attached traceback automatically from anaconda.
Created attachment 493179 [details]
Attached traceback automatically from anaconda.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 |