Fedora 16 Anaconda Error
Contents |
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Installation, Upgrades and Live Media [SOLVED] Can't install Fedora 22. Anaconda Error FedoraForum failed to scan disk sda fedora Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ
There Is A Problem With Your Existing Storage Configuration Failed To Scan Disk Sda
Today's Posts Search Installation, Upgrades and Live Media Help with Installation, FedUp & Live Media (Live CD, USB, DVD) problems. Google™ Search FedoraForum failed to scan disk sda centos Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 27th May 2015, 04:09 AM Chechare Offline Registered
Failed To Scan Disk Sdb
User Join Date: May 2014 Location: México Posts: 14 Can't install Fedora 22. Anaconda Error Hi guys! I was triying to install Fedora 22 from the scratch but I find an problem. After check for a while the new features and check that all were working ok I begin the installation, but I can't pass from select the language & keyboard when a window alerts that there is a unknown problem and it needs to quit or fedora 23 report the error. I have reported the error, but i can't remember my account of bugzilla so I sent the information anonymously. What it could be? My pc is a Lenovo Ideapad Y510P. Chechare View Public Profile Find all posts by Chechare #2 27th May 2015, 07:55 AM Ahmad Samir Offline Registered User Join Date: Aug 2011 Posts: 891 Re: Can't install Fedora 22. Anaconda Error Did you verify the ISO you downloaded? Ahmad Samir View Public Profile Find all posts by Ahmad Samir #3 27th May 2015, 12:32 PM lsatenstein Offline Banned Join Date: Jun 2005 Location: Montreal, Quebec, Canada Age: 75 Posts: 3,517 Re: Can't install Fedora 22. Anaconda Error After many months of testing anaconda, and my similar bug reports with F21 and F22, I can provide what I call a solution to the problem. After booting the system, the kernel driving anaconda has to scan the hard disk(s) to get a picture of all the partitions therein and the free space on each drive. That scan is slow in elapsed time. If you move forward in anaconda before that scan is completed, you may/will obtain what you experienced, a black screen thereafter, and "pane is dead". So, for a successful install boot your system, look at the disk activity light on your computer, and when flashing stops, indicating that the
Documentation EPEL Infrastructure Internationalization Localization Marketing Magazine Package Maintainers Quality Assurance Websites All projects Search Tools What links here Related changes Special pages Printable version Permanent link How to debug installation problems From FedoraProject Jump to: navigation, search Contents 1 Narrowing it Down 2 Types of Bugs 2.1 Loader Bugs 2.2 Kernel Bugs 2.3 X Bugs 2.4 Tracebacks 2.5 Hardware Errors 3 Other Potentially Useful Information 3.1 Log Files 3.2 Hardware 4 Kickstart File 4.1 Anaconda Stage 4.2 Previous Steps 4.3 http://forums.fedoraforum.org/showthread.php?t=304641 Attached Devices 4.4 Encryption 4.5 Partitioning Layout 5 Writing the Report 5.1 To Form or Not to Form? 5.2 Specificity 5.3 Tone 6 What Happens Next? Narrowing it Down Before doing anything else, please try to figure out if you're testing the latest version of anaconda - this goes for all software products. If you're running into a https://fedoraproject.org/wiki/How_to_debug_installation_problems problem in F10 while we're developing F12, a bug report will not be very helpful and the problem may even be fixed already. If you ever encounter a bug that is not in the latest anaconda, please locate the newest one and try that. To check which version of anaconda you're running, you need only watch the screen when anaconda starts up. It will print something like Greetings. anaconda installer init version 11.5.0.47 starting And that's your version of anaconda! The other useful number is the tree. If you're using an official release, all we need is which Fedora you're installing. If, on the other hand, you're using the development tree (Rawhide), there are two ways to discover which tree you're using. Often the installation source will have a date in the path, which will tell us which build to look at. If your install source does not have a date, its .treeinfo file should contain a timestamp and a version number. If you cannot remember what you were using when yo
'linux'? f24 anaconda multiboot centos bootloader asked 2016-07-05 02:17:33 +0000 jvegas 143 ●3 ●7 ●14 http://www.tcbc-tn.org/ updated 2016-07-07 21:44:41 +0000 EDITED, second time to reflect new information the problem is caused by the 30_os_prober script which is used by https://ask.fedoraproject.org/en/question/90308/f24-error-cant-find-command-linux/ Anaconda in installation. It also happens each time the grub2-mkconfig command is used in updating Grub. EDITED, to reflect the real nature of the problem. The original post is listed below this edit. The real problem is the Anaconda is using the commands linuxand initrd to start any OS other than Fedora 24. The correct command are linuxefi and initrdefi. Now that I have identified the real problem, maybe someone can help me fix failed to this. Each time grub is updated, the error will occur again. Original post starts here. Fedora 24 fresh install - After installing Fedora 24 and updating Grub files with > sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg None of my other OS's will boot correctly. If F24 bootloader is used only F24 boots, same CentOS. I have Ubuntu 16.04, and Mint Cinnamon installed. Ubuntu had always been my "GoTo" OS until I tried the latest versions of Fedora. failed to scan I prefer Fedora to all other OS's. My HDD is partioned with 8 partitions, as follows: sda1 /boot/efi sda2 Ubuntu 16.04 sda3 swap sda4 Data ##(used for symlinks to Documents, Downloads, Music and PIctures folders for all OS's sda5 Linux Mint Cinnamon sda7 CentOS sda8 Fedora 24 The only bootloader that works correctly is Ubuntu but it does not support quiet boot for other OS's Fedora and CentOS bootloaders will correctly boot only F24 or CentOS depending on which one created the bootloader. When selecting other OS's the boot process stops with two error messages: error: can't find command 'linux' error: can't find command 'initrd' After examining all of the grub2 config files, they appear to be identifying the HDD and Partitions correctly. I have spent several hours scouring the Wiki pages on Grub2 and all of the supporting files: /etc/default/grub and all files used to make grub.cfg including 00_headers,10_linux, 30_os-prober_proxy, 40_custom and 41_custom. Obviously, I do not have a clue as to why this is happening. For now, I am using the Ubuntu bootloader, but I would like to do away with Ubuntu and Mint to free of those partitions to be used for additional storage. Can anyone help with this issue? ` edit retag flag offensive close merge delete Comments@skytux would you have any thoughts on this problem?jvegas( 2016-07-05 15:38: