Bug 566722
Summary: | NotImplementedError: Support for reading AIX disk labels is is not implemented yet. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Banas <mbanas> | ||||
Component: | anaconda | Assignee: | Hans de Goede <hdegoede> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Banas <mbanas> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6.0 | CC: | kzak, mbanas | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | ppc64 | ||||||
OS: | Linux | ||||||
Whiteboard: | anaconda_trace_hash:31755314b9be8536fe59bc95bcbf48df796667e91fbab989449c49fc6499d96a | ||||||
Fixed In Version: | anaconda-13.21.21-1 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-07-02 20:44: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: | 582286 | ||||||
Attachments: |
|
Description
Martin Banas
2010-02-19 14:38:28 UTC
Created attachment 395110 [details]
Attached traceback automatically from anaconda.
Do any of the disks attached to this machine actually have an AIX disk label? This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Hi Chris, I managed to get the information you requested before the traceback is displayed. It seems there're no AIX disk labels (in man parted the disk label is defined as partition table). sh-4.1# parted /dev/sda print Model: IBM HUS103073FL3600 (scsi) Disk /dev/sda: 73.4GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 8225kB 8193kB primary boot, prep 2 8225kB 115MB 107MB primary ext3 3 115MB 73.4GB 73.3GB primary lvm sh-4.1# parted /dev/sdb print Model: IBM HUS103073FL3600 (scsi) Disk /dev/sdb: 73.4GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 73.4GB 73.4GB primary lvm sh-4.1# fdisk /dev/sda -l Disk /dev/sda: 73.4 GB, 73407488000 bytes 255 heads, 63 sectors/track, 8924 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: 0x65440a00 Device Boot Start End Blocks Id System /dev/sda1 * 1 1 8001 41 PPC PReP Boot /dev/sda2 2 14 104422+ 83 Linux /dev/sda3 15 8924 71569575 8e Linux LVM sh-4.1# sh-4.1# blkid /dev/loop0: TYPE="squashfs" /dev/sda2: LABEL="/boot" UUID="37731915-d63f-461f-8a34-1674d96aaf20" TYPE="ext3" /dev/sda3: UUID="pG3ROi-g2Bt-RuIm-iW0Q-IQ2R-09X1-4i0uoc" TYPE="LVM2_member" /dev/sdb1: UUID="cJrYRW-BXg6-RQW2-t3Vh-joHE-esSm-9R35G3" TYPE="LVM2_member" /dev/mapper/VolGroup00-LogVol00: UUID="7bb177ec-ccc7-4cf1-88f2-8f8001266b1e" TYPE="ext3" /dev/mapper/VolGroup00-LogVol01: TYPE="swap" sh-4.1# fdisk -l /dev/sdb Disk /dev/sdb: 73.4 GB, 73407488000 bytes 255 heads, 63 sectors/track, 8924 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: 0xdf160500 Device Boot Start End Blocks Id System /dev/sdb1 1 8924 71681998+ 8e Linux LVM Hello, I found also a second machine with the same behaviour. -bash-4.1# parted /dev/sda print Model: AIX VDASD (scsi) Disk /dev/sda: 172GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 8225kB 8193kB primary boot, prep 2 8225kB 115MB 107MB primary ext3 3 115MB 172GB 172GB primary lvm -bash-4.1# fdisk /dev/sda -l Disk /dev/sda: 171.8 GB, 171798691840 bytes 255 heads, 63 sectors/track, 20886 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: 0xeec20600 Device Boot Start End Blocks Id System /dev/sda1 * 1 1 8001 41 PPC PReP Boot /dev/sda2 2 14 104422+ 83 Linux /dev/sda3 15 20886 167654340 8e Linux LVM This is very strange. The error message you're getting comes straight out of parted, though we wrap it in an exception in pyparted. I wonder if parted's disk label detection is somehow busted. Please, try # od -N 4 -t x /dev/sda the AIX magic string is "\xC9\xC2\xD4\xC1". The fdisk should be able to detect AIX label as well. So, yes, it's very strange :-) (In reply to comment #7) > Hello, I found also a second machine with the same behaviour. > > -bash-4.1# parted /dev/sda print > Model: AIX VDASD (scsi) > Disk /dev/sda: 172GB > Sector size (logical/physical): 512B/512B > Partition Table: msdos > > Number Start End Size Type File system Flags > 1 32.3kB 8225kB 8193kB primary boot, prep > 2 8225kB 115MB 107MB primary ext3 > 3 115MB 172GB 172GB primary lvm > > -bash-4.1# fdisk /dev/sda -l > <snip> The model string is, well, the model string as reported by the device. It has nothing to do with what sort of paritioning the device is using. While the detect disklabel type is printed by parted after the "Partition Table: " and parted is correctly detecting an msdos table (if it was detecting a AIX label, you would once more get the not supported message, rather then parted printing a tabel). I believe when you originally hit this problem, you really had a disk with an AIX label on there. The correct thing to do here would be to make anaconda catch the NotImplementedError, and treat is as a disk without a label. Regards, Hans I've done a patch catching NotImplementedError and send it to the anaconda-devel-list. This will be fixed in anaconda-13.21.21-1, moving to modified. anaconda-13.37-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.37-1.fc13 anaconda-13.37-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. Hello, Verified on RHEL6.0-20100422.12 running tier1 tests on ibm-p5-185-01.rhts.eng.bos.redhat.com. Since there weren't any exact steps to reproduce and it doesn't happen anymore, I'm closing this bug as VERIFIED. RHTS results: http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=152214 http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=152213 http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=152212 http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=152211 http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=152208 http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=152207 http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=152206 Red Hat Enterprise Linux Beta 2 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |