Bug 517603
| Summary: | anaconda failed in get_table | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Geoff Levand <geoffrey.levand> | ||||||
| Component: | python-pyblock | Assignee: | Peter Jones <pjones> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rawhide | CC: | awilliam, geoffrey.levand, hdegoede, iyanmv, jgranado, lorisdianna, nieland.fedde, petersen, pgueckel, pjones, ryniker, spacewar, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | ppc | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | anaconda_trace_hash:b22a25efa5e0ab59774ce6ad0b152777127204f394c8244987e37d02bca455e7 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-09-02 17:33:34 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 507678 | ||||||||
| Attachments: |
|
||||||||
Created attachment 357516 [details]
Attached traceback automatically from anaconda.
You _were_ installing to a multipath device. Or did anaconda confuse your storage setup with multipath? *** Bug 517634 has been marked as a duplicate of this bug. *** There is no multipath. This failure was on a PS3 game console. It has a standard block device /dev/ps3da, and a built-in USB card reader /dev/sd*. I had no media in the card reader at the time. -Geoff Can you pls go to tty2 and execute the following command: `udev --query=all --name=ps3da` and attache the output. Does this give you what you need? # udev --query=all --name=ps3da udev: command not found # udevadm info --query=all --name=ps3da P: /devices/ps3_system/sb_03/block/ps3da N: ps3da W: 30 S: block/252:0 E: UDEV_LOG=3 E: DEVPATH=/devices/ps3_system/sb_03/block/ps3da E: MAJOR=252 E: MINOR=0 E: DEVNAME=/dev/ps3da E: DEVTYPE=disk E: ANACBIN=/usr/sbin E: DEVLINKS=/dev/block/252:0 -Geoff (In reply to comment #6) > Does this give you what you need? > > # udev --query=all --name=ps3da oops, sorry :) I'm assuming that you executed this command while installing. If not, pls repeat. > --- Comment #7 from Joel Andres Granados <jgranado> 2009-08-19 06:04:12 EDT ---
> I'm assuming that you executed this command while installing. If not, pls
> repeat.
Yes, just after the error occurred I ran the command from tty2.
-Geoff
(In reply to comment #2) > You _were_ installing to a multipath device. Or did anaconda confuse your > storage setup with multipath? I suspect anaconda is confusing my storage setup, or not finding any at all. I have 2 sata drives and one pata (disabled in bios). My output is also attached. I thought I could simply unplug the second drive and try again, but it didn't work: anaconda still thinks I have a multipath setup. I am thus unable to install and test f12α. ditto been there... (hence still wondering how alpha got released ;) Created attachment 358769 [details]
Attached traceback automatically from anaconda.
*** Bug 519427 has been marked as a duplicate of this bug. *** *** Bug 519711 has been marked as a duplicate of this bug. *** *** Bug 520258 has been marked as a duplicate of this bug. *** 519427 includes several reports that the problem is an internal card reader. Petrus, I suspect if you unplug your internal card reader, install will work. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers This appears to be affecting large numbers of people with internal USB media card readers in their systems; setting critical and blocking F12Beta. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #16) > 519427 includes several reports that the problem is an internal card reader. > Petrus, I suspect if you unplug your internal card reader, install will work. > Thanks for the tip. I was very excited to give f12α and had hoped a solution would appear before f12ß. I'll keep you updated as to how it goes. Update: it went! I successfully installed f12α and did a round of updates. I removed the usb card reader that I had found in an alley - it had seemed like a great find, since I don't otherwise have one :-) I don't need it anyway. Thanks! Now I can experiment with the new system. once you've got the install done, you can plug the card reader back in and it'll work fine. You only have to disconnect it to get through the install. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #20) > once you've got the install done, you can plug the card reader back in and > it'll work fine. You only have to disconnect it to get through the install. > Thanks. I'm going to toss it, since one of the slots is defective. f12α is looking great, but there are a lot of dependency issues, preventing doing a full update. I had hoped I would be able to use it right away, but I cannot even get openoffice installed yet. With f11α, I did manage to move right in. Nevertheless, likely due to the inescapable maturity of kde, f12α looks to be more polished than previous αs. I will monitor the progress and shift as soon as it is ready to my needs. I like that I no longer have to use ext3 for / (all my partitions are ext4 and I never have a separate /boot). Adam Williamson, Thanks for the hint that it was usb card reader related. Having a way to reproduce often is more then half the work of fixing a bug :) Thanks to this hint I've been able to reproduce and fix this problem. Some usb card readers, use multiple lun's per slot, and usb card readers usually report a fake disk serial, and some report the same fake serial for all slots. This lead to us seeing multiple disks with the same serial, and thus assuming we had multiple paths to the same disk and thus trying to use multipath, after which things went boom. See this commit for my "elegant" workaround: http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=ef63316f047549a6e17212a2ac42d7a0ec8e6e03 Closing (As I've verified that this fixes the usb cardreader backtrace). *** Bug 528543 has been marked as a duplicate of this bug. *** dropping common bugs keyword as this is fixed for beta. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers so if i disable usb in my bios settings things shut by allright to install fedora? i try,d serveral times but halve way it freeses to deadt or no reply,s from keybord regards f.nieland |
The following was filed automatically by anaconda: anaconda 12.14 exception report Traceback (most recent call first): File "/usr/lib/python2.6/site-packages/block/device.py", line 454, in get_table table = apply(_dm.table, tableParts, {}) File "/usr/lib/python2.6/site-packages/block/device.py", line 337, in __init__ table = self.get_table() File "/usr/lib/anaconda/storage/devices.py", line 2836, in setup self._pyBlockMultiPath = block.device.MultiPath(*parents) File "/usr/lib/anaconda/storage/devicetree.py", line 1855, in populate mp.setup() File "/usr/lib/anaconda/storage/__init__.py", line 293, in reset self.devicetree.populate() File "/usr/lib/anaconda/storage/__init__.py", line 92, in storageInitialize storage.reset() File "/usr/lib/anaconda/dispatch.py", line 204, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 127, in gotoNext self.moveStep() File "/usr/lib/anaconda/text.py", line 548, in run anaconda.dispatch.gotoNext() File "/usr/bin/anaconda", line 981, in <module> anaconda.intf.run(anaconda) ValueError: size must be positive