Fedora Installation :: Fc11 First Boot Hangs On "Verifying DMI Pool Data"
Oct 18, 2009
I had Fedora11 (default layout) running on a separate hard drive (winXP on the other drive). After the FC drive failure I replaced the drive and did a fresh install again. This time I tried a custom layout to keep the /home on a separate partition. The installation went without a hitch, but on first boot the system hangs with "Verifying DMI Pool Data......"
XP boots fine though. Looks like grub doesn't get loaded. I can boot with the installation cd and get into recovery mode, everything seems fine on the fedora disk. Fdisk result:
I installed ubuntu 10.10 on a machine that had windows 7 x64. itts installed on a seperate HD, but now when I boot to the harddrive with windows 7 all i get is "verifying DMI pool data" how do I fix this so I can get back to windows 7 as well?
I was dual-booting Windows 7 and Ubuntu 10.10 till recently. Then I had to reinstall Windows. After re-installation of Windows I did not try to restore Grub and deleted Ubuntu partitions on disk thinking that I'll install newer Natty version. But now when I try to install Ubuntu 11.04 using pen drive it gets stuck in bios showing message "Verifying DMI pool data ....". I also tried to boot GParted, memtest and Windows 7 with the same pen drive. Same thing occurred with GParted and memtest but Windows 7 installation did not stuck and went as usual. So I guess it's not hardware.
I was a windows XP user and one fine day my windows crashed and blue screen of death appeared. I have downloaded Ubuntu and created an ISO image on my pendrive with the help of the another computer as per the steps mentioned on the linux website. Now when am tryin to boot my corrupt PC with pendrive i cannot move beyond the comment " verifying DMI pool data" nothing happens later.
1 is the first partition so windows finds it nicely. Before install, i unplugged my hdds so that grub wouldn't get confused. I told the installer to put the full install on sda3 with no swap space. I checked (advanced button on summary page) that bootloader is being installed to the usb on dev/sda (sda since no other drives attached). This should put it in the MBR (i think?)
Seems like I pressed all the right buttons huh? Is there a way to diagnose grub and see what's wrong? is there a reason grub may not initialize properly from a usb drive?
I recently removed windows 7 from my computer and am now only using ubuntu. I used a live cd to grow the partition to use the new available space, but now the system just hangs at the Verifying DMI pool data section of bios. This is usually the first thing before grub loads.
I am trying to install fc11 on an intel mb with pentium4 and ati graphics the install always hangs at the point where the sw packages have been selected and the install is checking dependencies.
I have tried the regular install the basic video install, and text install with the same symptoms each time
the dvd drive lite is on and the hard disk activity lite is on and the system is frozen. have to power off.
I have fc11 installed on another system (amd) and had install issues also but that was with the preview.
I upgraded from FC10 to FC11 yesterday.I had no problems using FC11 after I looked into the bootloader (not intuitive - Ha!).Tried to boot up this morning; and things seemed to work well until I tried to call up Firefox (added a few themes yesterday).The window pops open; but the computer freezes on the spot with an alarm (generic "beep", w/o the finishing "p").Tried it with Epiphany; and I get the same results with the exception of actually getting to the Home Page.Yum works for the most part - I reinstalled Firefox (no effect); but couldn't reinstall epiphany (keeps saying "there is no such package - did you mean 'epiphany'". No typos on my part - go figure). Doing Software/Package Updates (via System Menu) freezes the box as well.Did it with the system monitor on. It doesn't appear to be related to CPU Usage.
Had a FC10 liveUSB and used it for awhile (e.g. to check out the forums). After giving my ISP some grief about downloading speed, immediately received a note from their Abuse Department, saying that my machine had been infected with a virus and had been sending spam emails (post upgrade to FC11).
I have a Dell Optiplex 760 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
running:
I tried to upgrade to FC11 via download and DVD and in both cases the install hangs on bootstrap right after remounting the root filesystem in read/write mode.
Since it hangs in this manner, I have not been able to gather any logs...
I am trying to install Ubuntu 10.10 on a Dell Latitude 1001 laptop which has XP installed. I have selected the option for Ubuntu to run alongside Windows but, on selecting the Ubuntu option at boot up, the installation stalls at "Verifying the Installation Configuration". Before this window came up, a very brief text message flashed on the screen - something like "getpwuid failed" (it was on the screen for only a second or less, so I didn't have chance to note it down. Does anyone have any suggestions as to what may be wrong (I have never used Ubuntu so please make any suggestions very simple).
I've lost my boot manager ,can't boot from harddisk ! I've installed F11 x86_64 kde livecd on a partition aside with FC10 and windows xp, created a /boot ext3 partition + a " / " ext4 root partition and a swap partition shared with F10.I've tried to restore booting windows xp with the windoze restore cd with the "fixmbr" tool, but it did'nt fix i
I just upgraded via preupgrade-cli (from FC10), rebooted, the upgrade process completed, then the system rebooted and I just see a blinking white cursor now.I was able to boot up from a live cd of FC11, but I'm not sure how I can repair the system.
I created my data pool using /dev/disk/by-id and things went well. a recent view of zpool status however showed /dev/sdb and /dev/sdc being used instead. how can I be sure a rearrangement of my disks wont cause error?
I'm running into this issue after installing Fedora Core 11 off DVD. Anaconda install the first part of the installation, then after reboot it goes into run level 3 (I think, where you have to login as root) I noticed that it said xserver failed to load before it actually boots Anaconda.
Maybe I should pull a graphic's card? I have logged in as root after the base install and did a lspci, and you can see the two Nvidia Quadro FX1700's and you can tell it is an intel board with the Intel Corp 6311ESB/6321ESB PCI Express ports. Also you can navigate through the linux directories via ls \. I tried YUM to find/install the graphics drivers but it says something about metadata not being configured. I checked the IP address with ifconfig and had to manually assign an ip.
I have just completed a dual boot installation of FC10. The install was done from CD's I downloaded from the Fedora website. The installation (seemed to have) went fine, and the machine still boots into XP if selected from the menu. The Fedora installation does not complete the boot process. I have three bars that move across the bottom of the screen, and the Fedora 10 graphic tuns white, and then the system hangs. I have let it sit at this screen for as long as 30 minutes. The screen will blank occasionally, but returns to the same place if I hit a key on the keyboard.
I have it installed on an old HP E800 netserver, running dual P3-866mHz processors, 2GB ram, a ATI Radeon 7000 video card, and three 36GB SCSI drives, non-raid. I know FC10 will run on this machine, as I have a friend running it on another E800 without any problems. This machine does have on-board video that is disabled only by plugging a different video card in (Phoenix BIOS).
This is one of those newbie questions about where I look to find error messages so that I can understand what the issues might be. My Fedora 12 setup invariably always hangs whenever I login following a cold boot. I login to x/g-nome, the screen clears and the initial background appears and then that's it.
I've been getting out of this by switching to another TTY (CTRL + ALT + 2), login as root and issue "shutdown -r now". System re-boots and I can login normally. I can see a stream of messages, I think relating to x scroll up the screen rapidly after the shutdown command. I'm not fast enough on the Pause button to read them. My question(s) then is... is there somewhere I can look to see what those messages might be? From the symptoms described initially, anyone have any thoughts on what the issue is likely to be?
I have just upgraded my F11 x86_64 system using the DVD ISO.
After rebooting as requested: 1) Cupsd fails to start - it can't find libaudit.so.1 (this doesn't worry me in itself). 2) Boot process proceeds until starting hald. This gets an OK response, but then the process hangs. No further output appears on the console. Pressing [ENTER] just causes a blank line to appear on the console. Pressing CTRL-ALT-DEL causes a reboot, and the same symptoms re-occur.
I'm tempted to boot with the rescue disk, save a few critical data directories, then start afresh with a clean install, but is there anything I can do to salvage the upgrade?
I currently dual-boot Windows Vista and Suse 11.2 on my Gateway desktop machine. I'd like to try out Fedora in a triple-boot situation.
My trouble is that the F13 Live CD hangs during boot. I've checked the hashes of the downloaded ISO files, and done burns on multiple media. During booting with the Live CD, my box hangs and I have to use the physical power button to turn off the box.
I've tried the 64-bit KDE spin (my preferred choice), the 64-bit GNOME version, and also the 32-bit KDE spin, and all of them hang at the same point. Removing the "quiet" boot option shows that it hangs after setting up my built-in card reader. When I installed Suse 10.3 on this same machine, I had to use the flags "acpi=off" and "brokenmodules=pata_it821x". Would the syntax be the same if I wanted to try with those boot options with the F13 Live CD?
Using the ISO files in VirtualBox inside my working Suse install works just fine.
I recently upgraded through 'YUM' from Fedora 14 to Fedora 15. The upgrade appeared to be successful until it re booted, ever since then it hangs at Code: Started SYSV: Enable monthly update of smolt. I have downloaded the ISO and burned it to DVD on another system which I used to try to rescue the installation, so far to no avail. My system specs are in my signature below (Laughlin is what I upgraded from).
I installed fedora on my second hdd, the other one had xp before fedora, now in grub it shows xp as other and wont boot into it, just hangs there. SDC is an external drive and sdb is the xp drive as you can tell by the filesystem.
Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x836db2c4 .....
I'm attempting to install F12 64 bit. I currently have F10 running on this system. I'd like to do a clean install. I'm using the DVD. I boot the computer with the DVD in. I choose the first option (Install or upgrade). It starts the boot process and then it hangs. [URL]
After asking at #Fedora I was given the advice to boot with `intel_iommu=off`. That gets me slightly further in the process. It gets to the point where anaconda is starting. Then all heck breaks loose. It appears the monitor loses the signal from the computer (power light turns red just like if the computer was off). The caps lock and the scroll lock lights on the keyboard blink about once a second. The DVD drive continues to spin for about a minute and then stops. Since I have no display, I have no idea what's going on.
I was using Ubuntu 9.10, until I got a new graphics card (Nvidia GeForce 9800 GT). After I got that upgrade, Ubuntu no longer supported that card for some reason, so I decided to try Linux Mint since it was a close relative to Ubuntu. Still no support for the video card.
I've always wanted to try Fedora so I decided to grab the x86_64 live cd and burn it. I stick it into my disk drive and it boots where it shows me the options to "Boot" "Verify and Boot" "Boot from Hard Disk" and one other option.
I tried the Boot option, and after selecting that, everything stalls, and my display turns off (not the entire monitor, just the display). I tried Verify and Boot, and still no luck.
I have also tried the i686 live cd and the same issue. It can not be the way I am burning it, cause I've gotten other live cd's to work with the same method of burning. Is it that Fedora does not support the card?
I am trying to get the GNOME version up and running.
I was on version 2.6.29.6-217.2.3.fc11.x86_64 and it asked me to update so I did. When I restarted I chose this version to install and after a brief loading screen it goes to a black screen with a cursor prompt and pretty much stays there. So I go back to 2.6.29.6-217.2.3.fc11.x86_64 which boots up just fine. But after a while I get some updates that won't install because it says that Packages are not compatible:Install - Linux Kernal 2.6.30.5-43.fc11(x86_64)
ERROR with rpm_check_debug vs depsolve: kernel-uname-r = 2.6.27.19-170.2.35.fc10.x86_64 is needed by kmod-nvidia-2.6.27.19-170.2.35.fc10.x86_64-180.29-1.fc10.1.x86_64
Have had a clean perfectly working copy of 2.6.31.6-166 for months and after two updates to 2.6.31.12-174.2.3 and 2.6.31.12-174.2.19, neither of the newer kernel versions will allow machine to boot properly. Start-up hangs at the preload daemon with a flickering screen. To use machine, must use grub chooser and choose the original base kernel.
Running on Tyan h2000m board, opteron 2356, Nvidia 9800 GTX+ and 12GB of dram with SELinux security enabled.
I have installed last updates about 3 days ago. After this Fedora kernel 2.6.30.9-99.fc11.x86_64 does not start.booting it the last message I see"ADDRCONF(NETDEV_UP):wlan0: link is not ready" then it stops. I have to boot with a previous kernel version 2.6.30.9-96.fc11.x86_64.
I'm planing to upgrade from FC11 to FC14 using a preupgrade. I've read about some ways to overcome the problem of my /boot partition being only 200MB in size while the newer versions require 500MB. The option of "filling the free space on the boot partition to be less than 100MB to cause preupgrade to download the loader" appeals to me. But what I don't understand is: is the 500MB requirement of the new versions is transient during the install or a permanent requirement? If I do this trick of first filling up the free space on /boot then freeing it up before the reboot, what will be the permanent disk space requirement of FC14?
Are there any safe (and prefarably simple) ways to increase the size of the /boot partition after decreasing the size of other partition? Here is the output of "df" relevant to the /dev/sda disk:
I performed a clean install of Fedora 15 from DVD and it goes fine until the end when the install program says to reboot the computer. Once I do that, the computer hangs before Grub loads, i.e. just after all of the BIOS messages, so there isn't any error message to indicate what is wrong. I had no issues with Fedora 14.
