Description of problem: anaconda coredumps while detecting storage on a PPC system. This currently prevents any progress in getting F16 on PPC installable. Version-Release number of selected component (if applicable): anaconda-16.14.6-1.fc16 parted-3.0-2.fc16 How reproducible: always Steps to Reproduce: 1. install a PPC machine with p.e. http://ppc.koji.fedoraproject.org/scratch/karsten/iso/Fedora-20110825-ppc64-netinst.iso 2. observe the anaconda abort during storage detection 3. grab core file from /root Additional info: I can provide a machine for debugging the core file if necessary. If absolutely required I can even provide a machine at a stage directly after the failure, but as that's the only machine I currently have I'd try to avoid that.
Created attachment 520603 [details] gdb backtrace of the core file
The first few sectors of the disk may help as well. dd if=/dev/whatever of=disk.img bs=512 count=34 And the logs from /tmp/*log attached as individual files.
Created attachment 520634 [details] fist few sectors of /dev/sda
Created attachment 520635 [details] fist few sectors of /dev/sdb
Created attachment 520636 [details] anaconda.log
Created attachment 520637 [details] program.log
Created attachment 520638 [details] storage.log
Created attachment 520639 [details] syslog
Are one or both of these devices really short? ped_geometry_read_alloc (geom=0x172589a8, buffer=0xfffe46dda28, offset=-8, count=1) There's a bug in some of the probing code where it doesn't properly check for the length before calculating the offset, ending up with a negative value on very small devices. *** This bug has been marked as a duplicate of bug 728949 ***
There are small partitions on this system, but no partition is as small as the 8 blocks that are mentioned in bug 728949: bash-4.2# parted -l Model: ATA Maxtor 6Y160M0 (scsi) Disk /dev/sda: 164GB Sector size (logical/physical): 512B/512B Partition Table: mac Number Start End Size File system Name Flags 1 512B 32.8kB 32.3kB Apple 2 32.8kB 1081kB 1049kB hfs untitled boot 3 134MB 14.9GB 14.8GB hfs+ Apple_HFS_Untitled_1 4 14.9GB 15.1GB 210MB ext4 untitled 5 15.1GB 164GB 149GB untitled lvm Model: ATA SAMSUNG HD103SJ (scsi) Disk /dev/sdb: 1000GB Sector size (logical/physical): 512B/512B Partition Table: mac Number Start End Size File system Name Flags 1 512B 32.8kB 32.3kB Apple 2 32.8kB 1000kB 968kB ext3 hfs boot 3 1000kB 500MB 499MB 83 4 500MB 50.0GB 49.5GB ext3 83 5 50.0GB 100GB 50.0GB ext3 83 6 100GB 1000GB 900GB ext3 83 Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_macg5-LogVol02: 124GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 124GB 124GB ext4 Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_macg5-LogVol03: 10.5GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 10.5GB 10.5GB ext4 Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_macg5-lv_swap: 4295MB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 4295MB 4295MB linux-swap(v1) Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/vg_macg5-lv_root: 10.5GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End Size File system Flags 1 0.00B 10.5GB 10.5GB ext4
btw, what's messing up all those strings in the DEBUG storage output: 'DEVLINKS': '/dev/scd0 /dev/disk/by-id/ata-IPNOEE_RVD-DWR_VD-R01D7_D ..... ^^^^^^^^^^^^^^^^^^^^^^^ 'ID_MODEL': 'IPNOEE_RVD-DWR_VD-R01D7' ^^^^^^^^^^^^^^^^^^^^^^^ .............. udev has it correct: # udevadm info --query=all --name=/dev/sr0| grep ID_MODEL= E: ID_MODEL=DVD-RW_DVR-107D