Created attachment 974168 [details] anaconda-tb-fATN71 Description of problem: Version-Release number of selected component (if applicable): How reproducible: Just trying to install live usb media to a new SSD hard drive. Same errors if I install after choosing "Try Fedora" or if I choose "Install to Hard Drive" from the beginning. Steps to Reproduce: 1. Boot to LiveUSB (x86_64) on Dell M6600 laptop with NVIDIA graphics 2. Click "Install to Hard drive" option to install to hard drive. 3. Immediately an Anaconda error shows in the message bar. 4. Shortly after the error message, the install starts, showing the keyboard selection screen which is defaulted to US which is what I want. 5. Multiple message boxes pop up (3 of them) and I can have to choose Quit and the whole install process is closed. Actual results: The Keyboard selections shows, but only briefly before 3 error boxes pop up and I can only choose "quit" that closes the installation process and never completes. Expected results: The installation should continue and install Fedora 21 to the hard drive. Additional info: Per request, submitting here. Reference 1169019 for background and other detil.
Created attachment 974169 [details] anaconda.log
Created attachment 974170 [details] Anaconda-tb-ZthMbm
Created attachment 974171 [details] anaconda-tb-dwEpnM
Created attachment 974172 [details] storage.log
If you still have the SSD disk in a state that allows you to reproduce this bug, can you please provide the output of the 'lsblk' command? Thanks!
[liveuser@localhost ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk └─sda1 8:1 0 223.6G 0 part sdb 8:16 0 223.6G 0 disk └─sdb1 8:17 0 223.6G 0 part sdc 8:32 1 29.1G 0 disk └─sdc1 8:33 1 29.1G 0 part /run/initramfs/live sr0 11:0 1 1024M 0 rom loop0 7:0 0 12K 1 loop loop1 7:1 0 1.8M 1 loop └─live-osimg-min 253:2 0 6G 1 dm loop2 7:2 0 1.3G 1 loop loop3 7:3 0 6G 1 loop ├─live-rw 253:0 0 6G 0 dm / ├─live-base 253:1 0 6G 1 dm └─live-osimg-min 253:2 0 6G 1 dm loop4 7:4 0 8G 0 loop └─live-rw 253:0 0 6G 0 dm /
On a chance, I removed the second hard drive (sdb) and then the installer ran perfectly. I'm using Fedora 21 on the new SSD drive to type this. Not sure why, but I'm happy to "break" the installer again if you need me to test more.
(In reply to John Love from comment #7) > On a chance, I removed the second hard drive (sdb) and then the installer > ran perfectly. I'm using Fedora 21 on the new SSD drive to type this. > Not sure why, but I'm happy to "break" the installer again if you need me to > test more. That's why I wanted the lsblk output -- the sdb disk seems to be weird in some way. However, the lsblk output doesn't contain anything weird. Can you please try 'parted /dev/sdb p' and attach the output?
Granted, I'm now running on the drive and mounted the second disk, but here's the output: [john@puddy DbVisualizer]$ sudo parted /dev/sdb p Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used. OK/Cancel? OK/Cancel? ok Model: ATA SanDisk SDSSDX24 (scsi) Disk /dev/sdb: 240GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 240GB 240GB ext4 If you want me to run off the live USB and do the same, let me know I can provide that as well.
(In reply to John Love from comment #9) > Error: The backup GPT table is corrupt, but the primary appears OK, so that > will be used. That's why. The backup GPT table is corrupt. A fix to handle this sort of situation is being worked on in bug 1157657. *** This bug has been marked as a duplicate of bug 1157657 ***