Bug 490212
| Summary: | can't handle quirky partitioning table | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jarod Wilson <jarod> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | anaconda-maint-list, pjones, rmaximo, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | anaconda_trace_hash:05e7984cac22a661af178870d076520111137dacab03347de8b8989b11786c56 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-03-13 21:01:50 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: |
|
||||||
Created attachment 335156 [details]
Attached traceback automatically from anaconda.
Anaconda said it didn't like my partition table, and asked if it could reinitialize it. I told it to go ahead with it, and it appears it did indeed clear the partition table (post-mortem inspection of the drive shows no partition table now), but then the backtrace. fwiw, the partition table *was* a bit wonky, but not invalid... The drive originally had a 150G sda1, then an sda2 that started after it. The huge sda1 was deleted w/fdisk, and sda1 was recreated as a 200M partition (because grub was falling down trying to boot the 150G partition directly). So there was a big gap between sda1 and sda2 that anaconda apparently choked on. I've fixed this traceback, though the troubles handling a strange partitioning table is certainly still a problem. I'm going to dupe this one to the bug that I fixed about the partitioning table. Can you try again with the next build of anaconda and open a new bug if we still say your partition table is unreadable? Thanks. *** This bug has been marked as a duplicate of bug 489122 *** |
The following was filed automatically by anaconda: anaconda 11.5.0.28 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devices.py", line 852, in __init__ raise DeviceError("cannot find parted partition instance") File "/usr/lib/anaconda/storage/devices.py", line 197, in PartitionDeviceFactory return PartitionDevice(*args, **kwargs) File "/usr/lib/anaconda/storage/devicetree.py", line 1010, in addUdevDevice parents=[disk]) File "/usr/lib/anaconda/storage/devicetree.py", line 1272, in populate self.addUdevDevice(dev) File "/usr/lib/anaconda/storage/__init__.py", line 221, in reset self.devicetree.populate() File "/usr/lib/anaconda/storage/__init__.py", line 64, in storageInitialize anaconda.id.storage.reset() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() DeviceError: cannot find parted partition instance