Ask Your Question
1

Fedora 22 Won't Install

asked 2015-06-04 09:56:16 -0600

Robert M. Koretsky gravatar image

updated 2015-06-05 18:39:21 -0600

mether gravatar image

I have downloaded 3 different ISO's from the getfedora website in the last couple of days, one the 32-bit version, the remainig two the 64-bit amd version. I burned each of them successfully to DVD, and was able to get the live version to run on 3 different computers. But when I made the choice to install to the hard disk on any of the computers, there was a verbose error message right at the beginning of the installation procedure asking me to report a bug or quit. Same error message and long detailed explanation from the three DVD's and the three different computers. What is puzzling me is that I have successfully burned and installed from ISO DVD's 10 different UNIX and LINUX systems from their websites on those same three computers within the last week. None of them gave me any errors on complete system installation. All of them either wiped the hard disk clean before installing itself, or in the case of one of them, installed in an available partition. Has anyone tried to do a complete system installation from the 32-bit/64-bit amd ISO images lately and been successful? If necessary I could supply a text listing of the error message, but it's quite long. The error message is hundreds of lines long, my question is has anyone done a complete new install of the Desktop Fedora 22, 64-bit amd from the current ISO on getfedora? I can't include the entire error message as an attachment, I don't have enough points( 60 required)! But following are the first few lines-

anaconda 22.20.13-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 950, in addUdevPartitionDevice raise UnusableConfigurationError(msg) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1224, in addUdevDevice device = self.addUdevPartitionDevice(info) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2193, in _populate self.addUdevDevice(dev) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2127, in populate self._populate() File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 277, in reset self.devicetree.populate(cleanupOnly=cleanupOnly) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1116, in storageInitialize storage.reset() File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(self.__args, *self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 244, in run threading.Thread.run(self, args, *kwargs) UnusableConfigurationError: failed to scan disk sda

Local variables in innermost frame: info: Device(u'/sys/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda1') name: sda1 self: <blivet.devicetree.devicetree object="" at="" 0x7f7bb7765c90=""> sysfs_path: /sys/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda1 msg: failed to scan disk sda disk: existing 931.51 GiB disk sda (1) disk_name: sda

Thanks!

edit retag flag offensive close merge delete

Comments

Please edit your question to include the error message. (Don't make it an answer, you only get to give one answer to any question.) I don't know if I can help you or not, but I do know that nobody can solve your issue without that message. Welcome to ask.fedora, and good luck.

sideburns gravatar imagesideburns ( 2015-06-04 15:33:16 -0600 )edit

Did you run a memory test on those machines, I have a previous experience with installer crashing do to a memory error. On of those times on a machine that was running previous version of Fedora. Not sure if this will help. Hope it does.

aeperezt gravatar imageaeperezt ( 2015-06-04 20:40:34 -0600 )edit

Memory 6 GBytes, working OK. As I said, the live version runs. Just won't install to the hard drive. Funny that 10 other Linux systems installed off ISO DVD on this same machine with the same disk. And on 2 other machines as well!

Robert M. Koretsky gravatar imageRobert M. Koretsky ( 2015-06-04 21:52:19 -0600 )edit

3 Answers

Sort by ยป oldest newest most voted
2

answered 2015-06-05 10:28:03 -0600

michich gravatar image

It looks like this bug: https://bugzilla.redhat.com/show_bug.... Something on your harddisk confuses the installer. You could try wiping the disk clean (perhaps just its partition table) manually first using dd.

edit flag offensive delete link more

Comments

Yes, I looked at the bugzilla reports you show, and they do seem very similar. One of the comments is very telling- since I am doing a fresh install on the entire disk, there should be some mechanism to wipe the disk clean and partition it ( along with whatever boot sectors and other boot requirements it needs). The other 10 LINUX and UNIX distros I have installed on these three computers on the same disks do that every time for a fresh install on the entire disk. What I will do is, when running the live version from the DVD, attempt to format the hard drive. Thanks for the answer!

Robert M. Koretsky gravatar imageRobert M. Koretsky ( 2015-06-05 11:26:30 -0600 )edit

Thanks very much. Fixed my issue too. In my case, I just downloaded gparted and it said there was no partition table on the drive. I used gparted to put one there and installation worked.

scottmcgee gravatar imagescottmcgee ( 2015-09-20 02:56:23 -0600 )edit
0

answered 2015-06-05 23:36:33 -0600

Robert M. Koretsky gravatar image

The first answer given is correct, I formatted the hard disk using the live version running from the DVD. When you use the file system viewer in the live version, it sees the hard disk. If you click on it, you can format the long way, stripping it to zeros. Took a few hours for a 1TB SATA drive. Then when you use Activities from the live version to install F22 to that hard disk, it works! It might be prudent for someone at this project to include a step in the excellent and verbose installation docs that advises a new installer to take this answers procedure and apply it to a new disk for a fresh install of F22. I combed thru the installation docs, but could not find anything that pertained to this scenario. This scenario seems to me to be quite common and something a new user/installer would experience. As I mentioned in the original question statement, I installed the top 10 LINUX and UNIX systems from DVD, and all of them except F22 automatically did what the answer to this question did on 3 different computers with a variety of hard disks.

edit flag offensive delete link more
0

answered 2015-07-30 16:00:04 -0600

AdmiralFlush gravatar image

I upgraded from 21.5 to 22.3 and that got me to kernel 4.04

edit flag offensive delete link more

Comments

Actually, you went from 21 to 22 because all Fedora versions are whole numbers.

sideburns gravatar imagesideburns ( 2015-07-30 16:19:15 -0600 )edit

Question Tools

Stats

Asked: 2015-06-04 09:56:16 -0600

Seen: 5,846 times

Last updated: Jun 05 '15