I installed F14 on my desktop yesterday. It booted fine right after DVD install. After that I did an upgrade and installed quite a lot of packages. But when I reboot the server, it stuck in a black screen. I did get the initial blueish screen with the F in the middle. But nothing after that, no error msgs, just stuck.
View 14 Repliescan 't boot fedora 12 from usb HDD after upgrade from fedora12 to fedora13 failed
View 6 Replies View RelatedI've just (finally!) gotten around to upgrading a couple of machines at a company I do some work for. One machine had a problem when I rebooted onto the new system. During the boot sequence, when it was checking and mounting the filesystems, it was unable to find the /boot partition. Now, this machine does run LVM on all but the /boot partition. The two SATA drives are mirrored, and they have the same partition layout:
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[code]....
I got the system to boot by commenting out the /boot partition in /etc/fstab, but this is certainly only a temporary solution. The other system that I upgraded came up just fine, as have several of my own. Unfortunately, I am doing these two systems by remote control via ssh as I have only limited plysical access to them. (I did have to get to it to figure out why it didn't boot up..)
I just upgraded to F15 and it went well. But at the next and each subsequent cold boot the BIOS reports "Your system last boot fail or post interrupted Please enter setup to load default and reboot". The board is an asus P5N-D. I press F1 to blow past the error and all is well until the next cold boot. Restarts are fine, no errors at all.
View 12 Replies View RelatedJust now, I finished upgrading from Fedora10 to Fedora11. But Now the Fedora 11 cannot boot, the screen just stay blue with 'fedora'.
btw, my computer is Dell Inspiron 1525.
I upgraded from f13 to f14 and now i get this message after booting up. I am at a loss as to what to do to clear it.
Code:
cat: /proc/self/attr/current: Invalid argument
Welcome to Fedora
Starting udev: udevd[478]: SYSFS{}= will be removed in a future udev version,
[Code].....
I upgraded from 12 using an x86_64 installation DVD on a Dell Poweredge 300. All seemed to go well until right at the end when it took over two hours not to 'finish' the upgrade. Cycling round into the shell prompt showed the machine was idle and there didn't seem to be anything waiting for anything to complete. In the end I was forced to re-boot.
I got a kernel panic saying it couldn't mount on unknown block (0,0).I re-ran the upgrade DVD and it said there was one rpm left to apply called upstart-[something I missed] and it successfully applied this and then claimed I had successfully completed the upgrade. Sadly, re-booting got the same.Using the older F12 kernel still works, so my server is operational, but believes it is still F12 (and these point to (0,0) as well so it isn't that). If I try to do a yum upgrade, it will only try to upgrade a few F12 packages that must have appeared in the last few days as it was fully patched a week ago.
I think the kernel panic may be due to missing disc drivers from what my googling reveals, or a missing initrd image. There is no initrd parameter in grub.conf, I've tried creating one manually but I get a load of errors saying the /lib/modules/2..../modules.dep file is missing. Another machine that I have upgraded has such an initrd parameter in grub.conf - so I may well need to put this in.
It's become a tradition since I've installed FC6 on my machine: after each Fedora upgrade, the PC hangs at reboot because of a badly make initrd !
I found this post a while ago that helped me to solve the problem by rebuilding the initrd with the right librairies in it: [url]
So for each upgrade I've done the last 2 years I had to follow again these instructions to rebuild the initrd.
I've just finished the upgrade from F9 to F10 and I faced the following friendly message:
Code:
Allright, not a surprise in fact. While rebuilding the initrd I discovered there's no more /lib/i686/nosegneg/ directory in Fedora10's initrd. Therefore I reinstalled the libm-2.9.so library as follows:
Code:
Once the initrd rebuilt, I rebooted and faced a second friendly message:
Code:
I searched for posts reporting problems with segfault in ld-2.9.so but didn't find anything. So now I'm with a successfully upgraded fedora 10 system that refuses to boot.
By the way, I've done the upgrade using the netinstall CD, all the packages have been retreived online without errors and I think I've therefore the latest versions.
How to making this F10 box to start ?
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've just updated my desktop to F13 using preupgrade but now grub won't boot it. The upgrade seemed to go OK, and none of the disk partitions should have changed as far as I'm aware, but now I get an error
VFS: Cannot open root device "UUID=xxx" or unknown block(0,0).
I'm not a complete newb, or a seasoned hacker. I can't figure out what's up with this, I keep getting this message when I try to apply updates. [('installing package kernel-2.6.35.12-88.fc14.i686 needs 17MB on the /boot filesystem', (9, '/boot', 16985088L))]
View 6 Replies View RelatedI 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 just upgraded to F11 from F10. Now it is unable to boot. I do not think my system is not seeing anything to boot from. I did bring it up on a rescue disk and was able to see all my file system. After it go thru the bios and I get past boot from dvd , it just stops.my /dev/sda1 and /dev/sdc1 show as boot drives. with fdisk -l Also fdisk show /dev/md0 ( raid ) not have a valid partition , but cat /proc/mdstat looks good. how I can get this fixed without a fresh install ?
View 1 Replies View RelatedI just upgraded my F9 system to F10 using they preupgrade method, and though nothing seems to have failed during the upgrade I can't boot my system any longer.I have a completly encrypted system, and so I need to enter a passphrase at boot. The new F10 system does boot and I do get a Password: prompt but the passphrase is not accepted.My passphrase doesn't contain any odd characters to prevent problems with keyboard mappings. Just plain letters (upper and lower case) and digits
View 9 Replies View RelatedI cant boot into Fedora 10 using the latest kernel. It just hangs after grub, I can still boot into an older kernel. The problem is its a fresh install that I ran a full update on straight away, and now I cant install videoaudio drivers because the kernel-header packages (and others) are installed for the latest kernel. Is there any boot parameters I can try to add when booting that might help?
View 5 Replies View RelatedI upgraded from F10 to F12 using preupgrade. The upgrade itself completed with no errors, but I'm unable to boot afterward.
Symptoms:...Grub starts, the initramfs loads, and the system begins to boot. After a few seconds I get error messages for buffer i/o errors on blocks 0-3 on certain dm devices (usually dm0 and dm2, but I can't get a shell to figure out what those are). An error appears from device-mapper that it couldn't read an LVM snapshot's metadata. I get the message to press "I" for interactive startup. UDEV loads and the system tries to mount all filesystems. Errors appear stating that it couldn't mount various LVM partitions. Startup fails due to the mount failure, the system reboots, and the steps repeat.
Troubleshooting done:...I have tried to run preupgrade again (the entry is still in my grub.conf file). The upgrade environment boots, but it fails to find the LVM devices and gives me a question to name my machine just like for a fresh install. I also tried booting from the full install DVD, but I get the same effect. Suspecting that the XFS drivers weren't being included, I have run dracut to create a new initramfs, making sure the XFS module was included. I have loaded the preupgrade environment and stopped at the initial GUI splash screen to get to a shell prompt. From there I can successfully assemble the raid arrays, activate the volume group, and mount all volumes -- all my data is still intact (yay!). I've run lvdisplay to check the LVM volumes, and most (all?) appear to have different UUIDs than what was in /etc/fstab before the upgrade -- not sure if preupgrade or a new LVM package somehow changed the UUIDs. I have modified my root partition's /etc/fstab to try calling the LVM volumes by name instead of UUID, but the problem persists (I also make sure to update the initramfs as well). From the device-mapper and I/O errors above, I suspect that either RAID or LVM aren't starting up properly, especially since prior OS upgrades had problems recognizing RAID/LVM combinations (it happened so regularly that I wrote a script so I could do a mkinitrd with the proper options running under SystemRescueCD with each upgrade).
I have tried booting with combinations of the rootfstype, rdinfo, rdshell, and rdinitdebug parameters, but the error happens so early in the startup process that the messages quickly scroll by and I just end up rebooting.
System details:4 1-TB drives set up in two RAID 1 pairs. FAT32 /boot partition RAIDed on the first drive pair. Two LVM partitions -- one RAIDed on the second drive pair and one on the remainder of the first drive pair. Root and other filesystems are in LVM; most (including /) are formatted in XFS.
I've made some progress in diagnosing the issue. The failure is happening because the third RAID array (md2) isn't being assembled at startup. That array contains the second physical volume in the LVM volume group, so if it doesn't start then several mount points can't be found.
The RAID array is listed in my /etc/mdadm.conf file and identified by its UUID but the Fedora 12 installer won't detect it by default. Booting the DVD in rescue mode does allow the filesystems to be detected and mounted, but the RAID device is set to be /dev/md127 instead of /dev/md2.
The arrays are on an MSI P35 motherboard (Intel ICH9R SATA chipset) but I'm using LInux software RAID. The motherboard is configured for AHCI only. This all worked correctly in Fedora 10.
I wanted to Upgrade from Fedora 13 to 14 and downloaded the Upgrade Image using the Pre_Upgrade Installer. My system downloads the upgrade just fine but when it starts to perform the it asks for the location of the new Fedora 14 ISO and I have no idea where that is or what to enter as a possible location which I have no doubt is in the default area.
View 3 Replies View RelatedI 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.
View 14 Replies View RelatedI have a /boot partition, and the online update process has downloaded the upgrade to /boot/upgrade. The problem is that grub is actually booting from a directory /boot which is in the root partition, but is invisible once the machine has booted, because the /boot partition is mounted over it. The result of all this is that the upgrade option does not appear in the boot menu, because that option has been inserted in the menu.lst (or grub.conf) in the /boot partition. is it ok for me to run:grub-install /dev/sda4(that's the device that contains the /boot partition where the upgrade menu option and data). Also, do I need the --root-directory option, given that the boot directory is the root directory of that partition.
View 3 Replies View RelatedI'm a long time Linux user. Finally got around to upgrading my Fedora 11 system to Fedora 12 by using the 'preupgrade' tool. The upgrade appeared to go well (downloaded packages, rebooted into installer, etc). However, now that the upgrade is complete, I'm unable to boot my system.
Here's my configuration:
/dev/sda (80Gb)
200Mb /boot partition (ext3)
52Gb / partition (ext4 - managed as logical volume)
2Gb swap partition (managed as logical volume)
20Gb /spare partition (ext3 - managed as logical volume) .....
All worked fine under Fedora 11 for the last few months. Grub now presents me with 'Fedora' and 'Windows XP' boot options. The /boot/grub/menu.lst file is essentially the same as it was for Fedora 11, except for the different kernel versions, etc. The boot sequence shows the Fedora bubble (??) and gets about 80% full when the screen goes black and the message displayed is:
No root device found
Boot has failed, sleeping forever
If I boot Windows, all works fine.
Am able to boot using a SystemRescueCD disk. The disks all look okay and I can mount/modify all partitions, etc. The grub menu.lst file read as follows (sorry, typed in, not copied):
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.32.11-99.fc12.i686.PAE)
root (hd0,0) .....
I have just upgraded my FC12 installation to FC13. The initial boot failed (just blank screen). Second time I received 'selinux targeted policy relabel is required'. I let that run, but still the boot did not suceed.
I then went in to verbose boot and saw that the boot would hang at libvirtd. So I disabled libvirtd for anything above run level 1. Next boot failed at atd, disabled atd. Next boot failed at 'monthly Smolt checkin'.
At that point and booted in to single user mode and dissabled SELinux, thinking that was the cause of all the problems. That did not help.
The update process has also removed my previous kernels, so I can't test a different kernel
Recently i've upgraded my fedora 11 to 12 using the preupgrade command and now I have a problem booting! when i start the interactive boot it hangs after trying to run the service local, it looks as if its trying to boot because the cursor blinks really fast then blinks normally after a few seconds. no error was stated during the event. what seems to be the problem here?
View 3 Replies View RelatedI tried to upgrade from Fedora 8 to Fedora 12, but after preupgrade got everything ready I rebooted. Anaconda searched for storage devices and then said "No upgrade root found". What can i do to continue the upgrade manually?
View 1 Replies View RelatedTrying to do the upgrade through "Software Updates", however because there are no current updates, I cannot click on the "Upgrade" button to begin the upgrade process to FC14.
Is there any other way to do this besides downloading the DVD and installing?
I downloaded recommended updates and restarted the computer (Lenovo G550). As I clicked my user name and typed in my password the video went haywire for a split second and it made a horrible audio sound.
Now when I try to boot up it just returns me to the login screen over and over I booted off of a liveCD and can see the folders on my hard drive but root and home have an X on them and I am denied permission to view them. I tried Ctrl+Alt+F1 and I am able to login in text mode. The folder I am trying to recover is on my desktop and it is named Jim Barfield (2 words). When I attempt to navigate to this folder it says that the folder or command does not exist. Does anyone have any ideas? I have replaced the hard drive and Win7 runs fine- I do not think it is a hardware problem. I really need those files- it is a customer's backup of all thing!
Today I've upgraded Ubuntu 10.10 to 11.04 and upgrade installed without errors but when I chose to boot in Win from grub menu screen goes black tries to boot and then goes back to grub menu. It just lets me boot in Ubuntu from grub. How can I repair this. Windows were first installed then Ubuntu 10.10. Here is boot info.
Boot Info Script 0.55 dated February 15th, 2010
Boot Info Summary:
=> Windows is installed in the MBR of /dev/sda
sda1:
File system: ntfs
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files/dirs: /boot.ini /ntldr /NTDETECT.COM .....
Here's the message I received:
init: ureadahead main process (2393) terminated with status 5 libudev: udev_monitor_new_from_netlink: error getting socket: invalid argument Mountall: mountall. c3206: assertion failed in main: udev_monitor=udev_monitor_ init: mountall main process (2396) killed by ABRT signal general error mounting filesystems. A maintenance shell will now be started Control-D will terminate this shell and reboot the system Give root password for maintenance(or type Control-D to continue.
I finally figured out what my root password was by dumb luck. It just takes me to a root prompt. I'm actually communicating through a live 10.04 installation disk.
I was happy with my Jaunty on my Asus X53 with ati radeon hd2600 and restricted driver, until two hours ago. I've started (after a long wait) to upgrade my Jaunty, everything was fine after upgrade, but I've noticed video was running with "ubuntu driver" and 3d wasn't available, so I started to install a fresh release of ati driver. But before I've saw in /usr/share/ati the previous copy of my restricted driver so before install the fresh copy I've run "sh ./fglrx-uninstall.sh" it had remove all telling me there wasn't any istance of fglrx (of course I thought...) ...and so before start with new installation I've thought about a reboot for first, but after it I'm unable to boot...
from normal boot it simply hang after a while, I think when it try to initialize video card. but more worse, also after choice recovery option at grub loader it hang after a bit, without give me any prompt.
I upgraded from Ubuntu 9.10x64 to 10.04x64 today (figuring I'd get in before the rush tomorrow). I rebooted, got past grub, and all I got was a flashing cursor... To get a better idea of what was going on, I edited the line I was booting in grub ('e' on the line) and removed the "nosplash quite" options. The machine began to boot and I got the standard stuff that you'd expect to find in kern.log. The system then mounts my drives and that's it, no more output at all. If, however, I plug in a USB device I do get the USB plugged in kern.log message, but the machine never boots into Ubuntu.I'd really like to not reload the machine, it isn't a horrible problem as /home is a separate partition, but I have a lot of stuff I'd hate to have to reinstall. Does anyone have any ideas on how I might get into my installation?
View 9 Replies View RelatedI upgraded my ubuntu to 10.4 the other night. Everything went well and 10.4 worked great. However, I tried to boot up Windows this morning and found that after selecting XP from the grub menu, all I got was a black screen. I can access the drive from linux and can save the music and photos I store on the HD with windows, I'm afraid I was not paying enough attention during the upgrade (late night!) when I got to the point where I was asked about installing grub on various drives and I may have installed it over the mbr/pbr? on the windows hd. Does anyone have an guess what I might have done?
Here is the output from fdisk -l