Fedora :: FC13 Upgrade Stops After Reboot With LVM Error
May 14, 2011
I have a problem with LVM. My installation of Fedora 13 is on 2 SATA hard disks, which are set as /dev/sda and /dev/sdb. On sda there are two partitions (boot and a physical part of the volume group) and on sdb is only one partition (other physical part of the volume group). Both physical parts of the volume group are used for one volume group and the VG is splittet into multiple logical groups. The system works and all seems to be ok. But I saw a strange thing on last reboot:
The device /dev/sda was not recognized during the boot sequence, instead the system has build a device /dev/md126p1 with the same geometry and partitions and it has the same disk id as sda.
The volume group is also ok, the system boots into the desktop environment, but the system-config-lvm says that /dev/sda is not initialized and the volume group consists of sdb and md126p1. fdisk -l knows three devices (sda, sdb and md126p1). I think, that is the reason for my problems with preupgrade, which stops after the reboot with a LVM problem (root not found). Can I correct that without data loss?
Code: $ su -c 'yum install wine' this forum won't let me put all the text in Transaction Check Error: package openldap-2.4.21-6.fc13.x86_64 (which is newer than openldap-2.4.21-4.fc13.i686) is already installed package nss-softokn-freebl-3.12.4-19.fc13.x86_64 (which is newer than nss-softokn-freebl-3.12.4-17.fc13.i686) is already installed
Last nights upgrade of java-1.6.0-openjdk-1.6.0.0-43.1.8.2.fc13.i686 and java-1.6.0-openjdk-plugin-1.6.0.0-43.1.8.2.fc13.i686 prevent the loading of Ameritrades Command Center.Downgrading to version 1.6.0.0-37 fixes the problem. I'll post the bugzilla number as soon as I get the chance to file it.
got my upgraded fedora 14 partition to boot, but I find out that I had to reinstall my nvidia driver, no big deal. seemed to go ok, but now when I go applications->system tools -> terminal I get the "starting terminal" thing on the bar, and then nothing. Can't figure out whats up.
I upgraded from FC11 to FC13 last night. The desktop has not been stable since. It will run for anything from 5 to 30 minutes before it locks up. Interesting, if I am already ssh'd in, I can perform commands, but a new SSH will hang, and if I try to SU to root in an already logged in ssh, it hangs.
However, I did finally manage to get the messages that were logged to /var/log/messages at the time of the desktop freeze.
Here are the messages. The first 3 about high speed usb may or may not be relevant. The freeze appeared to happen around the 4th message in the log below.
Code: Sep 2 13:16:57 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6 Sep 2 13:26:38 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6 Sep 2 13:31:20 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6 Sep 2 13:38:03 starbug kernel: INFO: task jbd2/dm-0-8:558 blocked for more than 120 seconds.
Took an FC12 system to FC13 via 'preupgrade'There was a REALLY old version of gimp-print-cups in RPM, and the installer announced "a fatal error occurred". However, everything else seemed to download properly and I allowed the upgrader to reboot the system.
a) grub boots the kernel, then the kernel can't find root and panics. It does this because it can't root file system with root=UUID= kernel option. If I manually tweek the grub line to use root=/dev/sdx, kernel finds its root and boots up to the next problem.
b) GUI environment not launched. Init scripts die on "error loading modules.dep". Sure enough - one is not there. Ran "depmod" to generate it ,and rebooted. System reboots into GUI, where I login to find the next problem.
c) Evolution won't start. Reason turns out the evolution-data-server from FC12 is still present. Did a check on just how many other FC12 RPM's are present: 1100. Yeah - over 1000. About 850 of the FC12 RPM's also had FC13 replacements installed. Did an "rpm -e" on these. Also had to do some remove action on mkinitrd, nash, plymouth-scripts-0.8.0, and parted-1.9.0 as there are replacements for these utilities under different package names. That cleaned up the system some, to present me with the next problem.
d) yum package repository still linked into FC12. Removed fedora-release-12-2.noarch and then I could "yum install" evolution and a few other packages properly.
I've done one other FC12->FC13 upgrade today, and that went flawlessly. So, I think in general the upgrade works fine. It just looks like if preupgrade finds anything amiss, it doesn't take care of a lot of things and generally leaves you with an unbootable mess to clean up.
I was having a job in /etc/event.d. It was working fine upto FC12. With upgrade to Fedora 13, it stopped working . Searching the internet, It looks like /etc/event.d is obsolete and I need to use /etc/init. Also the filename has to have a '.conf' extension. So I have renamed my job as /etc/init/svscan.conf.However, it fails to start automatically on reboot . It works if I manually issue the command % sudo /sbin/initctl emit qmailstartBut fails to start automatically on reboot. Is there anything wrong in my script below ? Let me know if I have missed out anything?
% cat /etc/init/svscan.conf # svscan - runlevel compatibility # WARNING: This file was auto-generated. Do not edit!
I am unable to login to kde after upgrade to fc14 from fc13 as user , the splash screen works for seconds and returns back to login screen, but I am able to do as root I also managed to login to KDE (failsafe session) and also I am able to login as normal user to gnome desktop
I managed to successfully upgrade FC11 to FC13. While doing the post upgrade steps, I made a HUGE mistake. After identifying the unsupported packages, I used "yum remove package1 package2" command to remove the obsoleted ones without realizing the yum was also removing many FC13 packages! Here are the cmd sequence used:
I simply typed Yes and left unattended for a few minutes after yum prompted there were # of packages to be removed as I blindly believed it would do the job. After returning to the computer, I found many installed icons were disappearing, the wireless suddenly turned off etc. I killed the yum process right away but it was too late.
-Is there anything I could do to undo the yum remove process?
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
Following the instructions, I get to a little after "setting software channels" and a blcr-dkms_0.8.2-13 blacklist error pops-up and ends the installation.
Code: # yum update Loaded plugins: presto, refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package evolution.i686 0:2.30.2-1.fc13 set to be updated --> Processing Dependency: libedataserver-1.2.so.11 for package: nautilus-sendto-2.28.4-1.fc13.i686
[Code]...
Error: Package: empathy-2.30.1.1-1.fc13.i686 (@updates) Requires: libedataserver-1.2.so.11 Removing: evolution-data-server-2.30.1-2.fc13.i686 (@fedora)Error: Package: gnome-panel-2.30.0-1.fc13.i686 (@fedora) Requires: libedataserver-1.2.so.11 Removing: evolution-data-server-2.30.1-2.fc13.i686 (@fedora)Error: Package: nautilus-sendto-2.28.4-1.fc13.i686 (@fedora) Requires: libedataserver-1.2.so.11 Removing: evolution-data-server-2.30.1-2.fc13.i686 (@fedora) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Googled this and found the same problem mentioned in the yum site: [root@plouton ~]# yum update kernel Loaded plugins: refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.6-147.fc13 set to be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.4-95.fc13 set to be erased --> Finished Dependency Resolution Dependencies Resolved
I have install fedora11 live and the mouse work well when installing.When you reboot the mouse works ok until the welcome screen apears then the mouse stops working and I cannot continue with the postinstall. I have a 1TB usb externalHD that I am installing fedora11 and have partitioned it so that I have 500Gb free for fedora, system is doucore 2.4,4gb RAm, I tryed doing this with three differend mice and connectting the mouse to different usb ports
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.
At the end of preupgrade & upgrade a reboot was called for. After reboot, the only choice that appears in the boot screen is ... Upgrade to Fedora 12 (Constantine). The only thing to edit after typing 'e' is ... kernel /upgrade/vmlinuz preupgrade Repo=HD::/var/cache/yum/preupgrade->
initrd /upgrade/initrd.img
If I allow it to boot to "Upgrade" it tries to do a fresh install.
Recently I have been having issues with wifi. I can connect for about an hour and then after that the computer stays connected to the network but wont allow me to go anywhere on the internet.
I am trying to upgrade from F11 to F12.Using Preupgrade, everything went well and then it asked me to Reboot. Anaconda started then says something about updating some files then the screen goes blank.
I tried to upgrade Fedora 13 to Fedora 14 using preupgrade. The upgrade seem to go OK, I didn't see any errors. But when it did the final reboot all I get is a blank screen. I rebooted in single user mode and saw that /etc/rc5.d/S99local -> ../rc.local is the last script executed. I edited rc.local and added 'echo "got here"' at the end and rebooted. It did print "got here" so I know all scripts were executed for init 5, it didn't get hung anywhere along the bootup. Why I'm not getting the login screen?
I have an issue on a few servers where IPv6 stops working after a reboot. I can ping anything within the same subnet but anything outside of that it gives me host unreachable. I believe that it is not routing for some reason, but I am not sure why. I have tried adding a default Ipv6 route for Eth3 but nothing seems to work.
uname -a Linux server-1 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/Linux Code: route -A inet6 Kernel IPv6 routing table .....
I've recently decided to migrate the infrastructure in my workplace from ubuntu to fedora, every thing except the printers went perfectly. When I try to print as an user It just throws an generic error and stops, as a root it doesn't even show the error.
This is the debug log: Code: D [28/Apr/2010:04:22:03 +0200] cupsdSetBusyState: Dirty files D [28/Apr/2010:04:22:03 +0200] cupsdReadClient: 12 POST / HTTP/1.1 D [28/Apr/2010:04:22:03 +0200] cupsdSetBusyState: Active clients and dirty files D [28/Apr/2010:04:22:03 +0200] cupsdAuthorize: No authentication data provided. D [28/Apr/2010:04:22:03 +0200] cupsdReadClient: 12 1.1 Get-Jobs 1 D [28/Apr/2010:04:22:03 +0200] Get-Jobs ipp://localhost/printers/ .....
It worked fine in debian and ubuntu, so we can assume that the drivers are ok, any ideas?
I upgraded from fedora 14 to fedora 15 yesterday. I live in India (IST) which is GMT +05:30. Every time I boot, my system clock increases its time by 5 and a half hours. For example, system clock on my machine is now Wednesday May 26,2011 22:44. If I were to reboot now, the time I would get is Thursday May 27, 2011 04:14. How do I correct this?
I am using sda1 as /, which is a bootable drive. I do not know if my problem is that I did not create a /boot drive. After removing the iso dvd, I tried to reboot and I get this back: -bash: /sbin/reboot: input/output error Then it returns me to the terminal prompt.
So I'm in need of VM'ing a couple OS's to keep from repartitioning and dual booting my desktop. The first I'm trying to boot is a 64bit version of windows (have XP and 7 disc, trying XP for now) as I need to convert some of my work's ancient programs that still use DOS functions.
I choose Virtualbox over VMware just for the sake of VB being in the repos. Install and initial config went fine, but when I try to start (run) the VM the screen goes black, then the computer completely stops responding and needs a hard reboot. Pasting what I believe to be the error part in the log. If you need the entire log I can email or host it - too big for a post. Kernel Version - 2.6.32-trunk-amd64. Debian Sid
