Re: Preupgrade fc15-fc16
On 02/20/2013 12:40 PM, Reindl Harald wrote: Am 20.02.2013 18:35, schrieb Tod Thomas: I just completed upgrading a FC14 virtual machine running under virtual box and it went pretty well. Now I am trying to do the same upgrade only on a FC15 standalone machine to FC16. It looks like it can't find any of the FC15 repos which is odd since FC14 went so well. Should I expect this to work or is the FC15 release just too old? F16 is EOL now F15 and F14 are EOL since a very long time Why did the FC14 upgrade go so well? luck by selected a mirror which not deleted the files As it turns out there are a lot of mirrors that have quite an extensive inventory of Fedora releases. The trick is to find one and: - login as root - download the current releases.txt (http://mirrors.fedoraproject.org/releases.txt) - hack it for the version you want to upgrade to, removing all others - comment out both the mirrorlist and installmirrorlist lines - insert baseurl and installurl lines pointing them to your mirror repo - run preupgrade (not preupgrad-cli) Here's my uncommented fc15-fc16 release.txt: [Fedora 16 (Verne)] stable=True preupgrade-ok=True version=16 baseurl=http://mirror.us.leaseweb.net/fedora/linux/releases/16/Fedora/$basearch/os/ installurl=http://mirror.us.leaseweb.net/fedora/linux/releases/16/Fedora/$basearch/os/ Both my machines are rolled by hand. I upgraded from fc14 on one machine and fc15 on another to fc16 without a problem. It seems that preupgrade-cli doesn't read the releases.txt from the current directory (in my case root), I'm not sure that's consistent or an error on my part but running preupgrade worked fine. I was kind of concerned reading all the problems with preupgrade but everything went without a problem. I'll be trying fc16-fc17 if I can this weekend. Oh, and something reactived my Caps Lock key along the way. Grrr :) - Tod -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade fc15-fc16
Am 20.02.2013 18:35, schrieb Tod Thomas: I just completed upgrading a FC14 virtual machine running under virtual box and it went pretty well. Now I am trying to do the same upgrade only on a FC15 standalone machine to FC16. It looks like it can't find any of the FC15 repos which is odd since FC14 went so well. Should I expect this to work or is the FC15 release just too old? F16 is EOL now F15 and F14 are EOL since a very long time Why did the FC14 upgrade go so well? luck by selected a mirror which not deleted the files signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade fc15-fc16
On Wed, Feb 20, 2013 at 12:35:26PM -0500, Tod Thomas wrote: I just completed upgrading a FC14 virtual machine running under virtual box and it went pretty well. Now I am trying to do the same upgrade only on a FC15 standalone machine to FC16. It looks like it can't find any of the FC15 repos which is odd since FC14 went so well. Should I expect this to work or is the FC15 release just too old? Why did the FC14 upgrade go so well? I don't know the answer to this offhand, but are you doing this as an academic exercise or for some purpose? I think backing up data and config and then doing a clean F18 install is probably your best bet. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade does not find F18
Am 27.12.2012 19:40, schrieb Frank Zimmermann: Hi, I'm traying to upgrade my F17 to F18 with preugrade. However, launching the GUI leaves me with no options to choose (yes I've ticked show unstable test versions) and a preupgrade-cli Fedora 18 (Spherical Cow) results in No version with the name Fedora 18 (Spherical Cow) available. I've downloaded the releases.txt to folder I'm launchign preugrade from with no avail. there is no preupgrade for F18 as discussed often here there is a new tool called fedup throw away all this cap and follow exactly the instructions for yum-upgrade but keep in mind there is CURRENTLY no stable F18 http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18 signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade does not find F18
Am Donnerstag, den 27.12.2012, 19:50 +0100 schrieb Reindl Harald: there is no preupgrade for F18 as discussed often here there is a new tool called fedup throw away all this cap and follow exactly the instructions for yum-upgrade but keep in mind there is CURRENTLY no stable F18 http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18 Hm, ok I must confess that I've only recently subscribed to this list due to my issue with preupgrade. I've been search the web and my understandign of the docs was that fedup will be used from F18 on for upgrades. Therefore I thought preupgrade is still in use. What is the official way to upgrade from F17 to F18 if preupgrade is already deprecated? KR Frank -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade does not find F18
On Thu, Dec 27, 2012 at 20:01:09 +0100, Frank Zimmermann frank.zimmermann.ber...@freenet.de wrote: ok I must confess that I've only recently subscribed to this list due to my issue with preupgrade. I've been search the web and my understandign of the docs was that fedup will be used from F18 on for upgrades. Therefore I thought preupgrade is still in use. What is the official way to upgrade from F17 to F18 if preupgrade is already deprecated? fedup will be used for upgrading to F18 and higher. If you are upgrading from f16 or f17 to f18 you should use fedup. From f17, doing a yum upgrade should be relatively easy, though it isn't supported. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade does not find F18
On Thu, 2012-12-27 at 20:01 +0100, Frank Zimmermann wrote: Am Donnerstag, den 27.12.2012, 19:50 +0100 schrieb Reindl Harald: there is no preupgrade for F18 as discussed often here there is a new tool called fedup throw away all this cap and follow exactly the instructions for yum-upgrade but keep in mind there is CURRENTLY no stable F18 http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18 Hm, ok I must confess that I've only recently subscribed to this list due to my issue with preupgrade. I've been search the web and my understandign of the docs was that fedup will be used from F18 on for upgrades. Therefore I thought preupgrade is still in use. What is the official way to upgrade from F17 to F18 if preupgrade is already deprecated? F18 is as yet unreleased. That means that the appropriate list to ask about it is the Test list. The Users list (this one) is for released versions, which are currently F16 and F17. Do *not* assume that members of the Test list also read this one (or vice versa). poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade vs other upgrade methods, caveats?
On 11/18/2012 05:45 AM, Sergio wrote: Preupgrade isn't supported any more, AFAIK. That's only true for Fedora 18 and later releases. For the current release, PreUpgrade is still the recommended upgrade path: https://fedoraproject.org/wiki/How_to_use_PreUpgrade?rd=PreUpgrade For Fedora 18, yum is currently the only upgrade option. Fedora should be getting a new upgrade tool called fedup: http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade vs other upgrade methods, caveats?
Thanks everyone for the replies. So, for going 17-18, I should still be using Preupgrade, and after that this new Fedup application? Best, Christopher Svanefalk mob: +46762628251 skype: csvanefalk On Mon, Nov 19, 2012 at 10:15 AM, Gordon Messmer yiny...@eburg.com wrote: On 11/18/2012 05:45 AM, Sergio wrote: Preupgrade isn't supported any more, AFAIK. That's only true for Fedora 18 and later releases. For the current release, PreUpgrade is still the recommended upgrade path: https://fedoraproject.org/**wiki/How_to_use_PreUpgrade?rd=**PreUpgradehttps://fedoraproject.org/wiki/How_to_use_PreUpgrade?rd=PreUpgrade For Fedora 18, yum is currently the only upgrade option. Fedora should be getting a new upgrade tool called fedup: http://ohjeezlinux.wordpress.**com/2012/11/13/fedup-a-little-**background/http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade vs other upgrade methods, caveats?
No, preupgrade only up to Fedora 17. For Fedora 18 go with yum and when functional 'fedup'. --- Em seg, 19/11/12, Christopher Svanefalk christopher.svanef...@gmail.com escreveu: De: Christopher Svanefalk christopher.svanef...@gmail.com Assunto: Re: Preupgrade vs other upgrade methods, caveats? Para: Community support for Fedora users users@lists.fedoraproject.org Data: Segunda-feira, 19 de Novembro de 2012, 8:13 Thanks everyone for the replies. So, for going 17-18, I should still be using Preupgrade, and after that this new Fedup application? Best, Christopher Svanefalk mob: +46762628251skype: csvanefalk On Mon, Nov 19, 2012 at 10:15 AM, Gordon Messmer yiny...@eburg.com wrote: On 11/18/2012 05:45 AM, Sergio wrote: Preupgrade isn't supported any more, AFAIK. That's only true for Fedora 18 and later releases. For the current release, PreUpgrade is still the recommended upgrade path: https://fedoraproject.org/wiki/How_to_use_PreUpgrade?rd=PreUpgrade For Fedora 18, yum is currently the only upgrade option. Fedora should be getting a new upgrade tool called fedup: http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -Anexo incorporado- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade vs other upgrade methods, caveats?
I see, thanks! Best, Christopher Svanefalk mob: +46762628251 skype: csvanefalk On Mon, Nov 19, 2012 at 11:47 AM, Sergio sergiocmailbox-userl...@yahoo.com.br wrote: No, preupgrade only up to Fedora 17. For Fedora 18 go with yum and when functional 'fedup'. --- Em *seg, 19/11/12, Christopher Svanefalk christopher.svanef...@gmail.com* escreveu: De: Christopher Svanefalk christopher.svanef...@gmail.com Assunto: Re: Preupgrade vs other upgrade methods, caveats? Para: Community support for Fedora users users@lists.fedoraproject.org Data: Segunda-feira, 19 de Novembro de 2012, 8:13 Thanks everyone for the replies. So, for going 17-18, I should still be using Preupgrade, and after that this new Fedup application? Best, Christopher Svanefalk mob: +46762628251 skype: csvanefalk On Mon, Nov 19, 2012 at 10:15 AM, Gordon Messmer yiny...@eburg.comhttp://mc/compose?to=yiny...@eburg.com wrote: On 11/18/2012 05:45 AM, Sergio wrote: Preupgrade isn't supported any more, AFAIK. That's only true for Fedora 18 and later releases. For the current release, PreUpgrade is still the recommended upgrade path: https://fedoraproject.org/**wiki/How_to_use_PreUpgrade?rd=**PreUpgradehttps://fedoraproject.org/wiki/How_to_use_PreUpgrade?rd=PreUpgrade For Fedora 18, yum is currently the only upgrade option. Fedora should be getting a new upgrade tool called fedup: http://ohjeezlinux.wordpress.**com/2012/11/13/fedup-a-little-**background/http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/ -- users mailing list users@lists.fedoraproject.orghttp://mc/compose?to=users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -Anexo incorporado- -- users mailing list users@lists.fedoraproject.orghttp://mc/compose?to=users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade vs other upgrade methods, caveats?
Am 18.11.2012 13:58, schrieb Christopher Svanefalk: I was just wondering if there are any known downsides to upgrading via preupgrade, as opposed to using the more familiar upgrade methods (CD/DVD etc)? fedoraproject.org/wiki/Upgrading_Fedora_using_yum read the gints for the exact version careful and you are safe i did some hundret fedora-upgrades on all sort of machines with yum incldudign some where productive work was done on a KDE desktop (NOT recommended) while the update was running anaconda/preupgrade are the same crap both left me the few times with a lot of troubles up to non booting systems witha yum upgrade you can verify bootloader, kernel and use package-cleanup BEFORE reboot instead pray to a blackbox in F18 preupgrade is replaced by something else because anaconda is pre-alpha after the rewrite - so no do not tuch anaconda after the intial setup the argumentation anaconda/preupgrade are better supported because exakt known versions is bullshit - only the target versions are known but not the installed ones after some weeks of updates on the old version - so the anaconda-update is NOT tested against the installed versions starting three days after the fedora-release signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade vs other upgrade methods, caveats?
Preupgrade isn't supported any more, AFAIK. I upgraded via yum. Apart from the usual clean up before-hand (remove uneeded packages so less to download and I also uninstalled the compiled apps and recompiled them afterwards), run rpmconf before and after the upgrade (and look at the differences), fetch all repo keys before upgrade or run the distro-sync with --nogpgcheck, just make sure to re-enable your display manager as pref.dm was removed. In my case I had to '# systemctl enable lightdm.service'. In my case (about ten days ago, IIRC) the X keyboard wasn't properly migrated. If it's your case just run localectl (check its options) to fix it. Other changed configs: http://fedora.12.n6.nabble.com/HEADS-UP-several-very-old-sysconfig-files-are-being-deprecated-td4991826.html If you use Google Chrome, you need to re-install it after the upgrade (I think it re-links with the proper libraries). --- Em dom, 18/11/12, Christopher Svanefalk christopher.svanef...@gmail.com escreveu: De: Christopher Svanefalk christopher.svanef...@gmail.com Assunto: Preupgrade vs other upgrade methods, caveats? Para: Community support for Fedora users users@lists.fedoraproject.org Data: Domingo, 18 de Novembro de 2012, 10:58 Hello everyone, I was just wondering if there are any known downsides to upgrading via preupgrade, as opposed to using the more familiar upgrade methods (CD/DVD etc)? Best, Christopher Svanefalkmob: +46762628251skype: csvanefalk -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade F16 F17: duplicate dhcp entry?
On Wed, 2012-08-22 at 12:29 -0400, sean darcy wrote: I've got a running F16. The DHCP server gives it an address of 10.10.10.100 based on the MAC address. I'm trying to use preupgrade-cli to upgrade to F17. Preupgrade-cli works fine on F16. Then when I reboot into the upgrade, it fails saying it finds a duplicate entry for the dhcp address of 10.10.10.100. Same MAC. What's the problem? Sounds like the prior lease wasn't released while shutting down and rebooting. How's your DHCP server assigning the IP, have you fixed it to that IP, or that's just the currently used one? If you fix an IP to a MAC, then it should assign the same IP to that MAC, every time. But, if it's auto-assigning some IP to some MAC, booting up with a different OS may be seen by the server as a different device. The MAC isn't the only unique-identifier used by a DHCP server. What's your DHCP server running on? What says it finds a duplicate entry? (The DHCP server, the DHCP client in the upgrade?) -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade failure F15-F17, cannot find an Adobe related file on any mirror.
Quicksort writes: Platform: F15 x64 (—F17) Hello everybody, Preupgrade aborts upon the following: “Failure: repodata/filelists.xml.gz from preupgrade-adobe-linux-i386 (Errno 256). No more mirrors to try” I am wondering if this file is actually needed on a x64 install. If it’s not, preupgrade will have a hard time finding it. Thanks, in advance, for your help. This file does not exist at all. It's a figment of the script's imagination. Not sure what this preupgrade-adobe-linux-i386 repository is all about. No such thing exists. I'm guessing you have Adobe's yum repository enabled. Turn it off. pgp9HdHZBzeZh.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade failure F15-F17, cannot find an Adobe related file on any mirror.
Thank you, Sam, but how should I proceed ? Also, if I disable Adobe' s Yum repository can I re-enable it later (how ?) so as to get flashplayer updates. Thanks. Le mercredi 30 mai 2012 à 18:02 -0400, Sam Varshavchik a écrit : Quicksort writes: Platform: F15 x64 (—F17) Hello everybody, Preupgrade aborts upon the following: “Failure: repodata/filelists.xml.gz from preupgrade-adobe-linux-i386 (Errno 256). No more mirrors to try” I am wondering if this file is actually needed on a x64 install. If it’s not, preupgrade will have a hard time finding it. Thanks, in advance, for your help. This file does not exist at all. It's a figment of the script's imagination. Not sure what this preupgrade-adobe-linux-i386 repository is all about. No such thing exists. I'm guessing you have Adobe's yum repository enabled. Turn it off. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade failure F15-F17, cannot find an Adobe related file on any mirror.
do not top-post, however, now it does no longer matter... one major rule for dist-upgrades is to remove/disbale all packages and repos which may introduce troubles before you can install anything after the sucessful upgrade and have only to care not remove packages needed by the basesystem (needs sometimes knowledge) __ i had dist-upgrades where i simply had to rpm -e --nodpes whatever for packages knowing to be not rellay important and even in such cases most of them are pulled as dep while the upgrade is running this may happen if you are up-to-date with your installation and the target dist-version or mirror is behind in some cases never used DVD/ANaconda/Preupgrade except two messed up upgrades compared with some hundret successful dist-upgrades via yum in the last 4 years (yes the some hundret is true) Am 31.05.2012 00:17, schrieb Quicksort: Thank you, Sam, but how should I proceed ? Also, if I disable Adobe' s Yum repository can I re-enable it later (how ?) so as to get flashplayer updates. Thanks. Le mercredi 30 mai 2012 à 18:02 -0400, Sam Varshavchik a écrit : Quicksort writes: Platform: F15 x64 (—F17) Hello everybody, Preupgrade aborts upon the following: “Failure: repodata/filelists.xml.gz from preupgrade-adobe-linux-i386 (Errno 256). No more mirrors to try” I am wondering if this file is actually needed on a x64 install. If it’s not, preupgrade will have a hard time finding it. Thanks, in advance, for your help. This file does not exist at all. It's a figment of the script's imagination. Not sure what this preupgrade-adobe-linux-i386 repository is all about. No such thing exists. I'm guessing you have Adobe's yum repository enabled. Turn it off. -- Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / CISO / Software-Development p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade failure F15-F17, cannot find an Adobe related file on any mirror.
Quicksort writes: Thank you, Sam, but how should I proceed ? Also, if I disable Adobe' s Yum repository can I re-enable it later (how ?) so as to get flashplayer updates. You should find the repository file in /etc/yum.repos.d Look for something that refers to Adobe's stuff. Edit it, and change it to enabled=0 After you upgrade, you can set it back to enabled=1. Thanks. Le mercredi 30 mai 2012 à 18:02 -0400, Sam Varshavchik a écrit : Quicksort writes: Platform: F15 x64 (—F17) Hello everybody, Preupgrade aborts upon the following: “Failure: repodata/filelists.xml.gz from preupgrade-adobe-linux-i386 (Errno 256). No more mirrors to try” I am wondering if this file is actually needed on a x64 install. If it’s not, preupgrade will have a hard time finding it. Thanks, in advance, for your help. This file does not exist at all. It's a figment of the script's imagination. Not sure what this preupgrade-adobe-linux-i386 repository is all about. No such thing exists. I'm guessing you have Adobe's yum repository enabled. Turn it off. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org pgpeOmM1jrcd1.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade to Fedora 16 with grub2 upgrade failure?
On Tue, 06 Mar 2012 08:01:19 +1000 Michael D. Setzer II mi...@kuentos.guam.net wrote: Did a preupgrade from Fedora 14 to Fedora 16 on a system, and everything seemed to go fine except the grub was not updated to the grub2 as other upgrades I had done had. Welcome to Fedora 16 hell 8) Grub2 can handle this fine but it needs to be told to do it via a map file which it won't do by default and which preupgrade is apparently too dim to offer you as a choice. I seem to remember grub-install or grub2-install docs contained the relevant incantation to tell it STFU and do what it was told. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On Fri, 2012-02-10 at 12:25 -0700, don fisher wrote: 3. Why do they force a boot partition? As far as I know using /boot has worked since Fedora2. Because the boot process can only start from certain filing systems, it's more restricted than other things. But the system, once booted, can make use of better filing systems. And it does use a better one, by default. Also, *some* computers can only boot from the low cylinders on the disc, this issue has *always* been the case. With a boot partition, it's relatively easy to always ensure that the boot partition is readable by the BIOS. But when boot is just files in /, then they could be placed anywhere in the disc, including unreadable places. Even if the system was initially bootable, that's no guarantee that your system can continue to boot up without a boot partition. Any updates that get installed might put newer files that are used by the boot processes into an unreadable location. 4. Why is the starting group number 1000? I was assigned the ID/group of 239 back in 1994. All of my systems know me by that number, which is very convenient when you NFS mount many disks. I exited /etc/login.defs to allow 239 and have had many mysterious problems. system-config-users does not appear to work! How did you manage that? As far as I know, the default lowest ID for users has been 500, since the early Red Hat Linux days, long before Fedora existed. So, in the normal run of things, you'd have to have manually selected that ID, you wouldn't get assigned it. There's a division that regards IDs below 500 as being system users, and above 499 as actual users, and treats them differently in various ways, some of which *might* cause you a problem if you try to do something different. Other distros use 1000 as the dividing line. And now Fedora is falling into line with them, for consistency's sake across all *ix distros. Not that I can forsee a need for 999 system users, but then I do not do any large scale kind of computing (e.g. lots of services installed for lots of users). Is there a place where the logic for these changes would be documented? The release notes, as each release comes out...? -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On Wed, Feb 8, 2012 at 6:57 PM, Greg Woods wo...@ucar.edu wrote: All in all, the upgrade to F16 was by far the most difficult Fedora upgrade I have ever done. I agree ! F15 and F16 were terrible upgrades for me. However, if you used the Install DVD, it goes very smoothly. Because of the last 2 upgrades, I've become leary of the preupgrade process. I think I'll use the DVD for F17 as well. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On 02/10/12 16:25, linux guy wrote: On Wed, Feb 8, 2012 at 6:57 PM, Greg Woodswo...@ucar.edu wrote: All in all, the upgrade to F16 was by far the most difficult Fedora upgrade I have ever done. I agree ! F15 and F16 were terrible upgrades for me. However, if you used the Install DVD, it goes very smoothly. Because of the last 2 upgrades, I've become leary of the preupgrade process. I think I'll use the DVD for F17 as well. Hi, I have had many problems, as seen by the number of times I have posted in the past week. There are some things that just make no sense. 1. In the install DVD the provide the option to make your own partition layout, but there is no provision in the pull down menu to make the bios-grub partition. 2. Why do they make a /home partition be default. That should be a choice for those that do not like partitions. (I usually have just a root partition and a swap partition). 3. Why do they force a boot partition? As far as I know using /boot has worked since Fedora2. 4. Why is the starting group number 1000? I was assigned the ID/group of 239 back in 1994. All of my systems know me by that number, which is very convenient when you NFS mount many disks. I exited /etc/login.defs to allow 239 and have had many mysterious problems. system-config-users does not appear to work! Is there a place where the logic for these changes would be documented? Is there a place where system management from command line is documented? Some of us do not like sluggish window managers. The old fvwm does everything I desire, and more. Don -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On 02/07/12 22:05, linux guy wrote: I got around all this mess by upgrading from the full install DVD. I found the problem to exist only when updating from the live CDs or pre upgrading. If I did my upgrade from the full install DVD, everything worked out OK. If you need more information, I could go back and look at my notes. Linux guy, My question was different but related to this thread. since Redhat-3 I have been able to duplicate by systems using fdisk, mkfs, and rsync. In those days it was easy to install lilo on the replicated system disk to be. I am still trying to do the same thing using F16. I had an rather unfortunate experience with Ubuntu and wish to convert all of my machines to F16. I cannot find a discussion describing why the current F16 distribution uses such a complicated partition scheme. I generally opt for two partitions, a / partition and a swap partition. /boot lives under /. My current system, working great, is (from fdisk): Device Boot Start End Blocks Id System /dev/sda1 *2048 935733247 467865600 83 Linux /dev/sda2 935733248 97677311920519936 82 Linux swap / Solaris I purchased a couple of disks so I could replicate this system to my other machines. First problem was that the disks are GPT, so fdisk will not work (please fix it!). I used parted to make the partitions with the first partition starting at 2048 (I didn't know why at the time, I just copied what the full distribution disk had done on install). The partitions on the new disk are (from parted --list): Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start EndSizeFile system Name Flags 1 1049kB 730GB 730GB ext4primary boot 2 730GB 750GB 20.2GB linux-swap(v1) primary But now I cannot find a method to make the disk bootable. I found the following web page: http://www.dedoimedo.com/computers/grub-2.html which describes a tool called grub2-mkrescue F16. As I understand, it will make a bootable CD that contains grub2 that will boot the system on you hard drive. One can then us the grub2-mkconfig, or maybe grub2-install to make the new drive bootable. But the grub2-mkrescue fails looking for xorriso: grub2-mkrescue -o bootableGrub.iso Enabling BIOS support ... /usr/bin/grub2-mkrescue: line 310: xorriso: command not found Should this work? Please advise. Thanks, Don -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
Greg Woods wrote: This is the area at the beginning of the disk, before the first partition. Grub2 needs the first partition to start at 2048, but default partition layouts from Grub-1 systems start at 63. I have run into this several times and it is a royal pain. There may be some games you can play with gparted (shrink the partition, then move it), or you can do like I did, which is to dump the first partition, change it to start at 2048 (shrinking it a bit), making a new file system on the new partition, and restoring it. There is a way to force grub2 to install on systems with small starting areas. I have a system with only 64 sectors (0-63) running grub2 just fine. Yes, preupgrade should catch these cases before doing any work. Since I've gone through all the pain on several systems I'm too tired to file an RFE. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On 02/08/2012 12:48 PM, Michael Cronenworth wrote: Greg Woods wrote: This is the area at the beginning of the disk, before the first partition. Grub2 needs the first partition to start at 2048, but default partition layouts from Grub-1 systems start at 63. I have run into this several times and it is a royal pain. There may be some games you can play with gparted (shrink the partition, then move it), or you can do like I did, which is to dump the first partition, change it to start at 2048 (shrinking it a bit), making a new file system on the new partition, and restoring it. There is a way to force grub2 to install on systems with small starting areas. I have a system with only 64 sectors (0-63) running grub2 just fine. Yes, preupgrade should catch these cases before doing any work. Since I've gone through all the pain on several systems I'm too tired to file an RFE. The more I think about this the more bizarre it is that preupgrade doesn't catch this. Almost all (all?) users of preupgrade are using grub1. As I understand it, most (all?) grub1 systems have the first partition starting at 63. Any system with a first partition starting at 63 will be bricked if it runs preupgrade to F16. Therefore, most systems using preupgrade to F16 will be bricked. Am I missing something? sean -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
Am 08.02.2012 19:36, schrieb sean darcy: On 02/08/2012 12:48 PM, Michael Cronenworth wrote: Greg Woods wrote: This is the area at the beginning of the disk, before the first partition. Grub2 needs the first partition to start at 2048, but default partition layouts from Grub-1 systems start at 63. I have run into this several times and it is a royal pain. There may be some games you can play with gparted (shrink the partition, then move it), or you can do like I did, which is to dump the first partition, change it to start at 2048 (shrinking it a bit), making a new file system on the new partition, and restoring it. There is a way to force grub2 to install on systems with small starting areas. I have a system with only 64 sectors (0-63) running grub2 just fine. Yes, preupgrade should catch these cases before doing any work. Since I've gone through all the pain on several systems I'm too tired to file an RFE. The more I think about this the more bizarre it is that preupgrade doesn't catch this. Almost all (all?) users of preupgrade are using grub1. yes As I understand it, most (all?) grub1 systems have the first partition starting at 63. no, only the one who survived fedora some time :-) with F14 a new install started at 2048 (my currently physical hardware) but i have no understanding for changes / replacemenets brikcing well running systems installed years ago because for me the main benefit of a OS with package-managment is that it does not die slowly if upgrade on perfect running virtual servers installed 2008 with F9 and survived until F15 will be bricked with F16 (GRUB2) or F17 (usrMove) then the contributors should start to be much more careful or they will sooner or later left alone and then they can do and brick what they want but i have a little hope this is not the intention yes i am not soo positive becasue the quality of the distribution at release state is going down with each new version instead better signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On Wed, 2012-02-08 at 13:36 -0500, sean darcy wrote: Almost all (all?) users of preupgrade are using grub1. As I understand it, most (all?) grub1 systems have the first partition starting at 63. Any system with a first partition starting at 63 will be bricked if it runs preupgrade to F16. This last part seems not to be true. Someone else pointed out that there is a way to force grub2 to install on a disk with only 63 free blocks at the beginning, as that was the case with my desktop that I upgraded F14-F15-F16. It initially booted into F16 just fine. The problem was that I could then not modify the grub configuration; whenever I tried, I got the embedding area is too small error. Even something as simple as increasing the grub timeout was not possible. I expect the way to force it to install in a 63 block embedding area will be kludgy in some way and sooner or later it will bite you in the ass, so I think eventually you will want to repartition the disk so that it has a 2048 block embedding area. My experience with doing that was variable. When I tried this on my wife's desktop, where the first partition was root, I was able to dump and restore and complete the upgrade, but I ended up with a system that I could not update. I got a lot of bizarre errors from yum update saying you should report these errors. But I'm using at least one third-party repo (rpmfusion) so I expect my system is considered tainted for this. On my Dell laptop, where the first partition is a small partition that just has some Dell utilities for Windoze on it, it was easy to dump, repartition, and restore, and everything worked after that. Except for one more problem. I have always created /var as a separate partition, so if something goes bonkers logging (which I have seen more than once), it won't fill up the root partition. That's what /var is for, right? And yet, upgrading from F15 to F16 always fails if /var is a separate partition; you get an error about not being able to find the RPM database. In every case, I had to put the /var files back onto the root partition to get the upgrade to work. All in all, the upgrade to F16 was by far the most difficult Fedora upgrade I have ever done. --Greg -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On Wed, 2012-02-08 at 18:57 -0700, Greg Woods wrote: This last part seems not to be true. Someone else pointed out that there is a way to force grub2 to install on a disk with only 63 free blocks at the beginning Which brings up another related question. Is it possible to install grub2 into a partition? In the past I have done this so that I can have the main disk boot block reference a grub.conf which is only chainloader declarations (boot Linux, or boot Windows), and then I have another partition that has grub on it that presents the usual choice of Linux kernels that are currently installed. The reason I do this is so that I can hibernate Linux, then boot Windows, then come back to my hibernated Linux. Without the chainloading, what happens after hibernation is that, upon restart, it immediately launches into restoring the hibernated configuration and I lose the ability to save a hibernated Linux while running Windows. I'm just wondering how I can accomplish this in grub2. --Greg -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On Mon, 06 Feb 2012 18:49:19 -0700 Greg Woods wo...@ucar.edu wrote: On Mon, 2012-02-06 at 19:48 -0500, sean darcy wrote: grub2-install --no-floppy /dev/sdg /sbin/grub2-setup: warn: Your embedding area is unusually small. core.img won't fit in it.. /sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /sbin/grub2-setup: error: will not proceed with blocklists. What do I do now! Embedding area??? This is the area at the beginning of the disk, before the first partition. Grub2 needs the first partition to start at 2048, but default partition layouts from Grub-1 systems start at 63. I have run into this several times and it is a royal pain. There may be some games you can play with gparted (shrink the partition, then move it), or you can do like I did, which is to dump the first partition, change it to start at 2048 (shrinking it a bit), making a new file system on the new partition, and restoring it. Welcome to grub2 - it's as you've discovered completely awful (and a look through the huge pile of crap scripts Fedora has spewed to try and hide it is even more painful). You can do two things 1. Replace it with the old grub, which will need you to hand set up the /boot/grub* files as before and just work. 2. Mess around backing up the entire system, repartitioning and the like. 3. Tell it to STFU and use blocklists, in which case it'll work fine in my experience but has the same limits as grub1 (*don't* try things like defragging /boot or putting /boot on btrfs) The fact Fedora didn't properly test such basic upgrades in FC16 is a symptom of how bad the Fedora QA has become unfortunately. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On 02/06/2012 08:49 PM, Greg Woods wrote: On Mon, 2012-02-06 at 19:48 -0500, sean darcy wrote: grub2-install --no-floppy /dev/sdg /sbin/grub2-setup: warn: Your embedding area is unusually small. core.img won't fit in it.. /sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /sbin/grub2-setup: error: will not proceed with blocklists. What do I do now! Embedding area??? This is the area at the beginning of the disk, before the first partition. Grub2 needs the first partition to start at 2048, but default partition layouts from Grub-1 systems start at 63. I have run into this several times and it is a royal pain. There may be some games you can play with gparted (shrink the partition, then move it), or you can do like I did, which is to dump the first partition, change it to start at 2048 (shrinking it a bit), making a new file system on the new partition, and restoring it. --Greg Wow! Not to belabor the obvious, but why doesn't preupgrade check this at the beginning. Or reinstall grub1. Anything would be better than leaving you with an unbootable brick. I've created a grub1 stanza that boots F16. In fact, the ubuntu grub2 wiki shows how to chainload grub2 from grub1 - which is pretty neat but probably useless. Interestingly, the kernel upgrade to 3.2.3 changed grub.conf as well as grub.cfg! Can I just stay with grub1? I really don't want to mess with gparted wizardry on my boot partition. Unless there are some really clear instructions on how to move the beginning address. As I remember, you shrink by moving the ending address. sean -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
I went through the same thing back in early January. My sympathies. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On Tue, Feb 07, 2012 at 18:23:55 -0500, sean darcy seandar...@gmail.com wrote: Can I just stay with grub1? I really don't want to mess with gparted wizardry on my boot partition. Unless there are some really clear instructions on how to move the beginning address. As I remember, you shrink by moving the ending address. I am still using grub1 and it works just fine. Once it gets messed up it might be a pain to put back again though. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On 02/05/12 22:31, sean darcy wrote: preupgrade failed for some reason to install the grub2 bootloader. /boot/grub2 exists. I made an F16 livecd. edited /boot/grub/grub.conf: default=0 timeout=2 title 3.2.2 kernel /vmlinuz-3.2.2-1.fc16.x86_64 root=UUID=017cd53d-21ae-43b5-b8ce-b23b15092273 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 initrd /initramfs-3.2.2-1.fc16.x86_64.img all taken from grub2/grub.cfg. It booted, but then died with a dracut prompt - and I had no clue what to do then. Running grub2-install from the livecd doesn't work. Ubuntu seems to have a tool boot-repair on their livecd, but I can't find anything like that on Fedora. So, How do I boot the using grub - so I can run grub2-install natively? OR how do I install grub2 from the livecd - or otherwise? sean Is there any way so install grub2 on a disk? I have seen there is supposed to be a grub-rescue application that will make a bootable rescue disk. I cannot find this on Fedora-16. My goal is to copy updated distribution I have made to other machines. I wish to partition the drive, copy my executing system to the drive, and make it bootable. Should not this be easy? Don -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
I got around all this mess by upgrading from the full install DVD. I found the problem to exist only when updating from the live CDs or pre upgrading. If I did my upgrade from the full install DVD, everything worked out OK. If you need more information, I could go back and look at my notes. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On 02/06/2012 12:31 AM, sean darcy wrote: preupgrade failed for some reason to install the grub2 bootloader. /boot/grub2 exists. I made an F16 livecd. edited /boot/grub/grub.conf: default=0 timeout=2 title 3.2.2 kernel /vmlinuz-3.2.2-1.fc16.x86_64 root=UUID=017cd53d-21ae-43b5-b8ce-b23b15092273 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 initrd /initramfs-3.2.2-1.fc16.x86_64.img all taken from grub2/grub.cfg. It booted, but then died with a dracut prompt - and I had no clue what to do then. Running grub2-install from the livecd doesn't work. Ubuntu seems to have a tool boot-repair on their livecd, but I can't find anything like that on Fedora. So, How do I boot the using grub - so I can run grub2-install natively? OR how do I install grub2 from the livecd - or otherwise? sean Used the ubuntu boot-repair program. That installed the grub2 bootloader. Didn't go any further with the ubuntu tool since I wasn't sure how it fit with fedora. But now how do I get up the grub2/grub prompt described in the wiki?? sean -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On 02/06/2012 05:10 PM, sean darcy wrote: On 02/06/2012 12:31 AM, sean darcy wrote: preupgrade failed for some reason to install the grub2 bootloader. /boot/grub2 exists. I made an F16 livecd. edited /boot/grub/grub.conf: default=0 timeout=2 title 3.2.2 kernel /vmlinuz-3.2.2-1.fc16.x86_64 root=UUID=017cd53d-21ae-43b5-b8ce-b23b15092273 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 initrd /initramfs-3.2.2-1.fc16.x86_64.img all taken from grub2/grub.cfg. It booted, but then died with a dracut prompt - and I had no clue what to do then. Running grub2-install from the livecd doesn't work. Ubuntu seems to have a tool boot-repair on their livecd, but I can't find anything like that on Fedora. So, How do I boot the using grub - so I can run grub2-install natively? OR how do I install grub2 from the livecd - or otherwise? sean Used the ubuntu boot-repair program. That installed the grub2 bootloader. Didn't go any further with the ubuntu tool since I wasn't sure how it fit with fedora. But now how do I get up the grub2/grub prompt described in the wiki?? sean So now: grub2-install --no-floppy /dev/sdg /sbin/grub2-setup: warn: Your embedding area is unusually small. core.img won't fit in it.. /sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /sbin/grub2-setup: error: will not proceed with blocklists. What do I do now! Embedding area??? sean -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
On Mon, 2012-02-06 at 19:48 -0500, sean darcy wrote: grub2-install --no-floppy /dev/sdg /sbin/grub2-setup: warn: Your embedding area is unusually small. core.img won't fit in it.. /sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /sbin/grub2-setup: error: will not proceed with blocklists. What do I do now! Embedding area??? This is the area at the beginning of the disk, before the first partition. Grub2 needs the first partition to start at 2048, but default partition layouts from Grub-1 systems start at 63. I have run into this several times and it is a royal pain. There may be some games you can play with gparted (shrink the partition, then move it), or you can do like I did, which is to dump the first partition, change it to start at 2048 (shrinking it a bit), making a new file system on the new partition, and restoring it. --Greg -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade grub2 failed: now can't boot
Am 07.02.2012 02:49, schrieb Greg Woods: On Mon, 2012-02-06 at 19:48 -0500, sean darcy wrote: grub2-install --no-floppy /dev/sdg /sbin/grub2-setup: warn: Your embedding area is unusually small. core.img won't fit in it.. /sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. /sbin/grub2-setup: error: will not proceed with blocklists. What do I do now! Embedding area??? This is the area at the beginning of the disk, before the first partition. Grub2 needs the first partition to start at 2048, but default partition layouts from Grub-1 systems start at 63. I have run into this several times and it is a royal pain. There may be some games you can play with gparted (shrink the partition, then move it), or you can do like I did, which is to dump the first partition, change it to start at 2048 (shrinking it a bit), making a new file system on the new partition, and restoring it. WTF and how you will upgrades older systmes in the future if GRUB1 is dropped? jesus christ here are runnign 20 virtual machines installed 2008 and there is no need for GRUB2 at all nor for GPT nice that my new physical F14 setups last summer started at 2048 but this does not change existing systems signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade, F15 - F16 anaconda hangs.
Never mind answering this. I got it upgraded another way. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade: Anaconda can't find upgrade root?
On Sat, Dec 31, 2011 at 11:29 AM, T.C. Hollingsworth tchollingswo...@gmail.com wrote: Is your /var on another partition? If so, you're probably hitting this bug: https://bugzilla.redhat.com/show_bug.cgi?id=748119 There's an updates.img in comment 42 that should fix it. That must be it! Thanks! Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Preupgrade: Anaconda can't find upgrade root?
On Fri, Dec 30, 2011 at 2:21 PM, Richard Shaw hobbes1...@gmail.com wrote: I tried using preupgrade to upgrade my F15 64bit to F16 and ran into an issue with anaconda. It gave me a somewhat confusion error: https://plus.google.com/photos/112912133662927916698/albums/5692032713007961425?authkey=CJmNmIWD6M7WHQ Or, if you want to skip the picture link: --- Title: Upgrade root not found The root for the previously installed system was not found --- So which is it? The title says the upgrade root isn't found but the contents say the root of the previously installed system was not found... The latter. ;-) Is your /var on another partition? If so, you're probably hitting this bug: https://bugzilla.redhat.com/show_bug.cgi?id=748119 There's an updates.img in comment 42 that should fix it. -T.C. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: preupgrade or netinstall from i686 to x86_64
On 09/01/2011 09:05 PM, Robert Arkiletian wrote: I don't see an option in preupgrade to go from F13 i686 to F14 x86_64. Is it possible? Yes, it is possible, but (for me at least) it entauked a whole bunch of grief. What I did was to use the F14 x86_64 install DVD, and do an upgrade. This is not an officially supported upgrade path (and I think it even tells you that and gives you the option to either abort or continue). I chose to continue, and it upgraded a whole bunch of RPMs, but, in the process, I ended up with a lot of duplicate RPMs of mixed architecture (F13.i686 F14.x86_64) for some set of RPMs. I ended up going through my RPM list by hand and fixing up what I could using various techniques (yum update, rpm -i --force, rpm --erase --justdb, a couple of scripts which removed both versions and then re-installed the x86_64 version, whatever I could get to achieve what I wanted. It was very time consuming, and the yum error messages would take a long time to print out, and in a virtual console, I often could not see the entire output (the graphical UI was not initially working, and was one of the last things I was able to get working). Or is it possible with an F14 x86_64 netinstall iso disk? Fedora should provide a better upgrade path for changing architectures (at least for i686-x86_64, I'm not sure it makes much sense between incompatible architectures), but, their official suggestion is to just re-install from scratch to avoid the grief that I went through. -- Kevin J. Cummings kjch...@verizon.net cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F14 - F15 Fails
On 21 June 2011 23:06, Dj YB syehi...@t2.technion.ac.il wrote: On Tuesday June 21 2011 23:36:51 Dave Cross wrote: I have two Dell PCs - a Dimension desktop and an XPS laptop. They are both running Fedora 14 and I have tried to upgrade them both to Fedora 15 using preupgrade. In both cases, when I reboot and select the upgrade to Fedora 15 option, I'm just presented with a blinking cursor in the top left-hand corner of the screen. Can anyone suggest where I should start to debug this issue? Hi, Dave had the same problem the solution as was suggested to me and worked, was to wait. I had to wait for my flash drive installation for few hours, for the desktop installation had to wait several minutes. Oh, bloody hell. You're absolutely right. I was just being impatient. Both systems now upgraded. Thanks, Dave... -- Dave Cross :: d...@dave.org.uk http://dave.org.uk/ @davorg -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F14--F15
-Original message- From: Benjamin benjami...@gmx.at Date: Mon, 06 Jun 2011 08:17:58 -0400 To: Community support for Fedora users users@lists.fedoraproject.org Subject: Preupgrade F14--F15 Hello everyone! I encountered the following problem when trying to upgrade my system: After preupgrade has downloaded all the packages and the system has shutdown to establish the new system, while the installation process there came the failure: Too less space on / (or something similar) So i guess that my /boot partition is too small to perform the preupgrade, which is a problem a can´t solve alone. I need your help. Thx. Benjamin. Try a wired connection if you haven't already, and ignore warnings. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On Sun, Jun 5, 2011 at 5:01 PM, Michael H. Warfield m...@wittsend.com wrote: You'll get a lot of bitch about packages already installed but anything missing will get installed or you will get an error. Currently, it looks like avidmux from rpmfusion isn't reinstalling for me. Oh well. It eventually will. Just an FYI, the avidemux package was broken by the move from js 1.70 to 1.8.5 in Fedora 15. I'm working around it by re-enabling the bundled js while I try to fix it. There is already a new build available but hasn't made it into ...-testing yet. Thanks, Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F14--F15 [Solved]
Am 06.06.2011 15:20, schrieb echapin: -Original message- From: Benjamin benjami...@gmx.at Date: Mon, 06 Jun 2011 08:17:58 -0400 To: Community support for Fedora users users@lists.fedoraproject.org Subject: Preupgrade F14--F15 Hello everyone! I encountered the following problem when trying to upgrade my system: After preupgrade has downloaded all the packages and the system has shutdown to establish the new system, while the installation process there came the failure: Too less space on / (or something similar) So i guess that my /boot partition is too small to perform the preupgrade, which is a problem a can´t solve alone. I need your help. Thx. Benjamin. Try a wired connection if you haven't already, and ignore warnings. Thanks a lot echapin! That helped. Beside: Why did this help? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On Mon, 2011-06-06 at 09:05 -0500, Richard Shaw wrote: On Sun, Jun 5, 2011 at 5:01 PM, Michael H. Warfield m...@wittsend.com wrote: You'll get a lot of bitch about packages already installed but anything missing will get installed or you will get an error. Currently, it looks like avidmux from rpmfusion isn't reinstalling for me. Oh well. It eventually will. Just an FYI, the avidemux package was broken by the move from js 1.70 to 1.8.5 in Fedora 15. I'm working around it by re-enabling the bundled js while I try to fix it. There is already a new build available but hasn't made it into ...-testing yet. That's very interesting. Very interesting indeed and explains a lot. Yeah, js was at the heart of the other packages I had to uninstall and manually reinstall like elinks as well. And, sigh, this appears to also be at the core of what blew preupgrade / anaconda out of the water on the machine where it did run and that I'm working to recover now. I found that on MtKing in emergency mode I could manually start up the network using ifup (service network (re)start was an epic fail thanks to the god's be damned systemctl command) and bring that up to a functioning level other than the dain bramaged bug in the networking code that's shutting down IPv6 router advertisements on bridges but that's a known problem and outside the scope of this mess. IAC, I got the box talking on the network and communicating with my package cache server once I had v6 back up. Ran yum update just to see if anything was missed or messed up in the install. That told the tale. Of the close to 4,000 packages (that's according to what get cached for fc15 on my cacher) that should have been installed or updated, it was still missing almost 60 packages, had almost a dozen and a half rpm database check errors (mostly missing requires) and it still had avidmux-* dependency errors that could not be resolved. That made sense. The two machines were equivalent in the installed databases. Why didn't anaconda stop and bitch about THAT if it couldn't resolve it? It appears that Anaconda got past whatever made it blow up with the unhandled exception in the case of the Forest machine and it continued on even with an unreconcilable dependency error. It then failed catastrophically near the end of the install phase but before any of the postinstall scripts where run (which is why initramfs was never created even though the kernel rpm was installed). So, I cleaned up avidmux-*, elinks, and one other package by doing a yum erase on js. Then I was able to install the remaining missing packages (which had already all been downloaded, they just hadn't gotten installed) and then reinstall the other packages I had removed other than avidmux. That update also cleaned up the preexisting errors mess in the rpm database. Everything is now installed but, still, none of the original 4000 some odd postinstall scripts were run. Still dumps me into emergency mode and systemctl default still complains about Transaction would be destructive. So that still leaves me with a steaming pile I'm trying to clean up. Progress forward but not quite there yet. Not sure what the best path is to follow at this point. Downgrade to F14 and back up to F15? Try rerunning preupgrade again (I don't think so)? The good news is that, with the network back up this far, I can also move the two LXC based virtual machines (one of which is my master DNS server) off of that host and over to the alternate host, Forest, and I only have one machine flat on its rear out of this mess. That's doable. To the preupgrade devs - I would strongly recommend you test with a known broken machine that has dependency problems that anaconda can NOT resolve and make sure it gracefully stops and generates sane, intelligible error messages... The current avidmux is a good place to start. Thanks, Richard Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F14--F15 [Solved]
-Original message- From: Benjamin benjami...@gmx.at Date: Mon, 06 Jun 2011 10:27:41 -0400 To: echapin echa...@teksavvy.com, Community support for Fedora users users@lists.fedoraproject.org Subject: Re: Preupgrade F14--F15 [Solved] Am 06.06.2011 15:20, schrieb echapin: -Original message- From: Benjamin benjami...@gmx.at Date: Mon, 06 Jun 2011 08:17:58 -0400 To: Community support for Fedora users users@lists.fedoraproject.org Subject: Preupgrade F14--F15 Hello everyone! I encountered the following problem when trying to upgrade my system: After preupgrade has downloaded all the packages and the system has shutdown to establish the new system, while the installation process there came the failure: Too less space on / (or something similar) So i guess that my /boot partition is too small to perform the preupgrade, which is a problem a can´t solve alone. I need your help. Thx. Benjamin. Try a wired connection if you haven't already, and ignore warnings. Thanks a lot echapin! That helped. Beside: Why did this help? I don't know. This notion has been around for a version or two, and I don't remember the technicalities. Maybe someone else can fill them in. In any case I'm waiting 'til the general complaint level has died down a bit more and some packages I use catch up. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F14--F15 [Solved]
On 06/06/2011 01:59 PM, echapin wrote: Try a wired connection if you haven't already, and ignore warnings. Thanks a lot echapin! That helped. Beside: Why did this help? I don't know. This notion has been around for a version or two, and I don't remember the technicalities. Maybe someone else can fill them in. In any case I'm waiting 'til the general complaint level has died down a bit more and some packages I use catch up. http://fedoraproject.org/wiki/PreUpgrade#Not_enough_space_in_.2Fboot (Method 2) Cheers, Raman -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On 06/06/2011 10:11 AM, Michael H. Warfield wrote: To the preupgrade devs - I would strongly recommend you test with a known broken machine that has dependency problems that anaconda can NOT resolve and make sure it gracefully stops and generates sane, intelligible error messages... The current avidmux is a good place to start. It's good to see that you're making progress and, if not out of the tunnel yet you can at least tell that the light isn't an on-coming train. If you haven't yet, I'd suggest putting in a bug report against preupgrade because AFAIK none of the appropriate devs are on this list. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On Mon, 2011-06-06 at 12:37 -0700, Joe Zeff wrote: On 06/06/2011 10:11 AM, Michael H. Warfield wrote: To the preupgrade devs - I would strongly recommend you test with a known broken machine that has dependency problems that anaconda can NOT resolve and make sure it gracefully stops and generates sane, intelligible error messages... The current avidmux is a good place to start. It's good to see that you're making progress and, if not out of the tunnel yet you can at least tell that the light isn't an on-coming train. If you haven't yet, I'd suggest putting in a bug report against preupgrade because AFAIK none of the appropriate devs are on this list. I have not as yet, as I thought I might extract more from the corpse. Unfortunately, seems twas not to be (though I haven't totally given up quite yet). My latest effort... I did the following... rpm -qa --qf | sort -u rpm.list Then yum reinstall `cat rpm.list` (I even turned off my cacher forcing it to re-download everything from the net from scratch.) Re-downloaded over 3800 packages. It then began to rerun the install phase and blew its brains out after about 2400 of the packages were installed with the stupid Transaction would be destructive error and landed me back at the ^D emergency mode prompt jail. Sigh. Here we go again. I know the drill... My entire domain is named after caves in Colossal Caverns Adventure. You're in a maze of twisty little passages all different. I know the drill all too well. Logged back in. Ran yum-complete-transaction. It had a lot to do with just about 1000 packages to rum after the LAST time systemctl committed harri karri and, this time, ran to completion with no errors. Still no joy... Rebooting still lands me back in the emergency mode hell. Running systemctl default still results in Transaction would be destructive. I think systemd / systemctl is what's destructive on first principle. PoS. Right now, I'm beginning to believe it's this whole systemd systemctl garbage that's a crock of shit that stinks to high heaven. That's where the crashes are. The old SYSV scripts at least WORKED and didn't screw you over. That yum reinstall is telling me exactly what's broken and why anaconda hurled chunks earlier. It's that systemd setup that's hosed and blew up with no warning. It blew up in the middle of the recovery. If it did something like that in the middle of anaconda it's no wonder the machine is a steaming pile of molten RAM and disk. And still... THAT even took less time that preupgrade took on the first pass, even with the entire fresh redownload. Someone has done something seriously wrong in preupgrade. It may work in 99.99% of the cases but a single case of destroying a machine like this is simply inexcusable. Something that critical must be failsafe, and it's apparent to me this is not failsafe. Even if the ultimate fault in this case is systemd / systemctl, the bottom line at the end of the day is that preupgrade / anaconda did not detect / resolve the conflict / failure before you gave up control of the machine and before it was too late and irrecoverable. As much of a hassle as it has been at times over the years, the yum upgrade path has never, EVER left me with a machine that would not run. I can no longer say the same for preupgrade. Unfortunately, once THAT trust is lost, it can never be regained. Still trying to recovery the smoldering pieces but now getting very VERY close to just saying screw it and saving all 3TB off to another system and rebuilding this thing from scratch and restoring the data. That will take me a fraction of the time this has already even though the diagnostic data will be lost. Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On Sat, 2011-06-04 at 12:33 +0100, Timothy Murphy wrote:
Michael H. Warfield wrote:
Classically, for those servers (some of which originally started out on
FC1) have been upgraded using the yum upgrade method.
As a matter of interest, what exactly is _the_ yum upgrade method?
I've seen the term used by several people,
but as far as I can see they refer to different methods.
And don't all upgrade methods use yum in some way?
http://fedoraproject.org/wiki/YumUpgradeFaq
This is a pure yum upgrade from F{x} to F{x+1} (some people have
reported success with x+2 but I would personally avoid that like the
plague) on a live running system without taking it down for the upgrade
process..
So (in very shortened abbreviated summary form), to upgrade from F14 to
F15 you run...
yum update
yum clean all
rpm --import https://fedoraproject.org/static/069C8460.txt
yum --releasever=15 --disableplugin=presto distro-sync
(After a half an hour or so you'll probably complete this and reboot)
yum groupupdate Base
Now, I'm not quite sure exactly why that FAQ page recommends running
yum update yum since the first yum update should take care of that.
I have not been doing that step and it's never burned me (in fact, when
I have done that step, it's done nothing).
You should also read the caveats in that FAQ about cleaning up config
files and looking for any strange .rpmsave or .rpmorg types of things.
I think, in the past, squid was notorious for changing configuration
file formats and you have to port.
Also if you use Postgres, PAY CAREFUL ATTENTION TO DUMPING THE DATABASE
TO AN SQL DUMP FILE FIRST! That is not mentioned on that page but
almost every Fedora click has taken Postgres through and upgrade click
which can not automagically migrate the databases. I don't think
preupgrade or disk upgrades to any better here so it's not the fault of
yum upgrade.
Mike
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it!
signature.asc
Description: This is a digitally signed message part
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On Sun, 2011-06-05 at 17:31 -0400, Michael H. Warfield wrote:
On Sat, 2011-06-04 at 12:33 +0100, Timothy Murphy wrote:
Michael H. Warfield wrote:
Classically, for those servers (some of which originally started out on
FC1) have been upgraded using the yum upgrade method.
As a matter of interest, what exactly is _the_ yum upgrade method?
I've seen the term used by several people,
but as far as I can see they refer to different methods.
And don't all upgrade methods use yum in some way?
http://fedoraproject.org/wiki/YumUpgradeFaq
This is a pure yum upgrade from F{x} to F{x+1} (some people have
reported success with x+2 but I would personally avoid that like the
plague) on a live running system without taking it down for the upgrade
process..
So (in very shortened abbreviated summary form), to upgrade from F14 to
F15 you run...
yum update
yum clean all
rpm --import https://fedoraproject.org/static/069C8460.txt
yum --releasever=15 --disableplugin=presto distro-sync
Ok... My apologies. That really wasn't playing fair and very bad of me
over simplifying things a bit too much. That summarizes the process
described on the FAQ page (which I strong, STRONGLY recommend reading)
but there's gotcha's in there.
First off, I should mention, this is the newer process. The
--releasever option and the distro-sync command are relatively new
additions to yum. You use to have to manually download the release rpm,
the release-notes rpm, and the GPG key and install them using rpm then
run a yum update or yum upgrade (which are actually identical
functions - they don't do anything different now, if they ever did
anything different every in the past).
You will often run into dependency failures and it may recommend using
--skip-broken or something like that. I've had terrible luck with
that where yum would enter in to infinite dependency resolution loops!
The procedure I use is to start off with this command:
rpm -qa --qf '%{NAME}\n' | sort -u rpm.list
Then do the steps above. If things slam into a dependency error, run
yum erase to remove the trouble makers, provided it doesn't try to
remove your entire system (saw that once around F11, iirc, that was fun
to work around). Once the above workflow runs to completion with no
dependency problems, then you run this:
yum install `cat rpm.list`
You'll get a lot of bitch about packages already installed but anything
missing will get installed or you will get an error. Currently, it
looks like avidmux from rpmfusion isn't reinstalling for me. Oh well.
It eventually will.
So this isn't necessarily a fire and forget process and it use to be
worse. But... Then again... Neither is preupgrade.
(After a half an hour or so you'll probably complete this and reboot)
yum groupupdate Base
Now, I'm not quite sure exactly why that FAQ page recommends running
yum update yum since the first yum update should take care of that.
I have not been doing that step and it's never burned me (in fact, when
I have done that step, it's done nothing).
You should also read the caveats in that FAQ about cleaning up config
files and looking for any strange .rpmsave or .rpmorg types of things.
I think, in the past, squid was notorious for changing configuration
file formats and you have to port.
Also if you use Postgres, PAY CAREFUL ATTENTION TO DUMPING THE DATABASE
TO AN SQL DUMP FILE FIRST! That is not mentioned on that page but
almost every Fedora click has taken Postgres through and upgrade click
which can not automagically migrate the databases. I don't think
preupgrade or disk upgrades to any better here so it's not the fault of
yum upgrade.
Mike
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it!
signature.asc
Description: This is a digitally signed message part
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
Michael H. Warfield wrote: Classically, for those servers (some of which originally started out on FC1) have been upgraded using the yum upgrade method. As a matter of interest, what exactly is _the_ yum upgrade method? I've seen the term used by several people, but as far as I can see they refer to different methods. And don't all upgrade methods use yum in some way? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On Sat, Jun 04, 2011 at 12:33:50 +0100, Timothy Murphy gayle...@eircom.net wrote: As a matter of interest, what exactly is _the_ yum upgrade method? I've seen the term used by several people, but as far as I can see they refer to different methods. yum update --releasever=f?? And don't all upgrade methods use yum in some way? No exactly. Preupgrade downloads some stuf for and I think does a more robust rebuild of the boot images. (Sometimes it hasn't been possible to build the initrd for a new release while running under the old kernel.) I believe anaconda (I'm don't know about preupgrade) does the updates in a way that they aren't blocked by (some) dependencies. This is especially relevant if you use third party repos. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
[...] Regards, Mike My experience was exactly opposite. I upgraded from F13 to F15 without a hitch. While I was working at my workstation at home, I started preupgrade from the terminal and it downloaded the new packages. Once it was done, I rebooted it and made sure the upgrade process had started and left for my University. About an hour later from the university, I tried to login to my home workstation and walla! preupgrade had finished and booted to a working F15 machine, running with all my services just the way it was as if nothing had changed. FWIW, I think all the preupgrade headache arises when people don't realise it downloads the latest packages, creates a temporary repo and then uses anaconda for the upgrade. IMHO, if uptime and lack physical access to the machine is what is the prime concern, then an upgrade path via yum should be the prefered option. Just my 2 cents. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On 06/03/2011 11:34 AM, Michael H. Warfield wrote: Well, that tells me right there that preupgrade is still not deployment grade yet. Not for remote servers at least. So let me get this straight: preupgrade failed for you and therefor it's not ready to be used (at least on remote servers) by anybody. Isn't that a rather small sample size for such a sweeping generalization? I'd expect that kind of response (and have seen it here, recently) from some shallow, self-centered kid with little if any Linux experience. Having it come from somebody who's been using Linux professionally as long as you clearly have is a Bad Thing because it encourages beginners to react badly to upgrade problems even more than they already do. You have, of course, my sympathy. I'd offer whatever help I could, but you seem to have things well in hand already and I hope everything turns out OK. Quite frankly, I'm beginning to wonder if the issue is with F15 and not the upgrade methods. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade and first thoughts
On Fri, Jun 3, 2011 at 3:13 PM, Mark Eggers mdegg...@gmail.com wrote: --snip Also, updates are listed twice when running yum from the command line. For example: --- Package parted.i686 0:2.3-8.fc15 will be updated --- Package parted.i686 0:2.3-9.fc15 will be an updated Perhaps too verbose but not erroneous. Examine the output again. The first entry lists the installed package that is to be updated. The second entry lists its potential replacement. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade and first thoughts
On Fri, Jun 3, 2011 at 3:26 PM, Kam Leo kam@gmail.com wrote: On Fri, Jun 3, 2011 at 3:13 PM, Mark Eggers mdegg...@gmail.com wrote: --snip Also, updates are listed twice when running yum from the command line. For example: --- Package parted.i686 0:2.3-8.fc15 will be updated --- Package parted.i686 0:2.3-9.fc15 will be an updated Perhaps too verbose but not erroneous. Examine the output again. The first entry lists the installed package that is to be updated. The second entry lists its potential replacement. I forgot to mention you have a typo in the second line; i.e. will be an updated should be will be an update. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade and first thoughts
On Fri, 03 Jun 2011 15:33:31 -0700, Kam Leo wrote: On Fri, Jun 3, 2011 at 3:26 PM, Kam Leo kam@gmail.com wrote: On Fri, Jun 3, 2011 at 3:13 PM, Mark Eggers mdegg...@gmail.com wrote: --snip Also, updates are listed twice when running yum from the command line. For example: --- Package parted.i686 0:2.3-8.fc15 will be updated --- Package parted.i686 0:2.3-9.fc15 will be an updated -- snip -- I forgot to mention you have a typo in the second line; i.e. will be an updated should be will be an update. Those lines were copy-pasted from an actual update. Hmm, however a quick grep through /usr/lib/python2.7/site-packages/yum*/*.py doesn't show that phrase. I suspect it's constructed somehow. Time to read the code. And yes, I now see that the version number does change. So while verbose it is correct. . . . . just my two cents. /mde/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
On Fri, 2011-06-03 at 14:47 -0700, Joe Zeff wrote: On 06/03/2011 11:34 AM, Michael H. Warfield wrote: Well, that tells me right there that preupgrade is still not deployment grade yet. Not for remote servers at least. So let me get this straight: preupgrade failed for you and therefor it's not ready to be used (at least on remote servers) by anybody. Isn't that a rather small sample size for such a sweeping generalization? No... It's not the fact that it failed. It's the way that it failed. If failed in a way that is not recoverable in that situation. That's the problem. The fact that it did not resolve all the issues before the commit. The fact that once you commit you stepped blindly down that road there was no going back. Those were the problems. It's not the failure. It's the lack of a recovery. I'll admit. Probably in the VAST majority of the cases it will succeed, and that's wonderful, but the fact remains you can not predict when it will fail and, therefore, you can not trust it in cases where you lose control of the machine (the anaconda phase). This is unacceptable in the remote case. My failures are only examples of why it's not deployment grade. Not reasons, per se, not absolutes that all will fail, only examples of how catastrophic the failures, when the occur, will be. I'd expect that kind of response (and have seen it here, recently) from some shallow, self-centered kid with little if any Linux experience. Having it come from somebody who's been using Linux professionally as long as you clearly have is a Bad Thing because it encourages beginners to react badly to upgrade problems even more than they already do. You have, of course, my sympathy. I'd offer whatever help I could, but you seem to have things well in hand already and I hope everything turns out OK. Quite frankly, I'm beginning to wonder if the issue is with F15 and not the upgrade methods. And on that point you and I may well concur. Certainly the problems with the mistakes in bridging and routing wrt IPv6 have nothing to do with the upgrade process. As I have always done, I shall fill bug reports on what I find. That is, after all, why I continue to test things like this even when they have failed for me. I do not give up and I do try and get things to improve. And, sometimes, I'm known for my bad day rants. Thank you for your tolerance. Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade still sucks. Maybe sucks less, maybe sucks more.
Update... And now a real request for help... On Fri, 2011-06-03 at 14:34 -0400, Michael H. Warfield wrote: Ok... ITMT... I rebooted MtKing into the preupgrade process and turned it loose. Strangely, it DIDN'T run into the unhandled exception like Forest had. The machines should have been the same. Oh well. Something like two HOURS later, though, and it's still grinding on the disk. WTH? Why is preupgrade taking 4 times longer to upgrade a system and that's with the system down and out of service during the entire process. Well, it finally finished and I rebooted into the F15 kernel and was almost immediately greeted with a kernel panic unable to mount root fs on unknown block(0,0). Sigh... This would be real great at a remote location. Ok, I'm screwed. Yum upgrade worked over on Forest where preupgrade demonstrated an epic fail, and now MtKing has succumbed to another failure. Tried booting into one of the F14 kernels that were still on the system. You can forget that noise as well. I ended up at the Welcome to emergency mode. Use systemctl default or ^D to activate the default mode. Grrr... Log in and tried that systemctl default... No joy. Failed to issue method call: Transaction is destructive. Great. That's a delightfully spooky error that tells you absolutely nothing. Looks like it burned my bridges on the way out the door. Sigh... Poking around in emergency mode revealed that the F15 kernel had been install but no initramfs had been created for it and no initramfs line existed in grub.com. Now THAT is really weird. HTH did THAT happen? Seriously! Think about this. If it installed the kernel and the initrd command failed, why is the record even in grub.conf. If something failed there, don't touch anything. It's like something got half way there and threw up it's little cybernetic hands and said we're done. That's not really a preupgrade fsckup per se but an F15 fsckup in my book somehow... Problem #2 Manually created the initramfs while in emergency mode. Amazing what you can do in what is suppose to be sub-single user mode, but it worked and I could edit and fix grub and I could manually create an initramfs for that 2.6.38 kernel... Cool... Sigh... Not so fast grasshopper... But now... The F15 kernel is doing exactly the same damn thing the F14 kernels are and dumping me in Emergency mode and systemctl default is bitching about Failed to issue method call: Transaction is destructive. Sigh... So now I'm really screwed, although it looks much less like preugrade and more like a major screwup with the F15 install. Still boils down to the fact that I've got no recorded errors and no remote control of the machine and still not clue what screwed this whole mess up or how to get out of it. It's not the 2.6.35 (F14) kernel vs 2.6.38 kernel (F15) then what is it? It's not a preupgrade problem per se but the problem still exists and that blood machine is still dead. Just based on the flavor of the behavior it seems like something failed silently during the anaconda phase and something end up cross-wise as a consequence. I hate jumping to conclusions here but that's my working premise and I'm try to recover the machine from that. OTOH... My son, who is another skilled developer and Linux enthusiast, has used preupgrade successfully on one of his 64 bit stations but he also noticed that the upgrade took seemingly forever. Like hours. So that's not just me. Well, I've got a dead machine to try and recover from now. I've heard all the arguments about how preupgrade should be so much better because you're running anaconda on an install kernel. That has simply NOT been my experience at all. On the contrary - exactly to the opposite. Preupgrade fails to do the necessary disk space checking and dependency checking that ultimately causes these failures, all of which could be resolved remotely on a live running system without requiring repeated reboots. I have no idea what anaconda is doing that is so broken that it takes over 4 times longer to upgrade a system than yum, but the yum upgrade path has worked flawlessly (not always effortlessly, but flawlessly) for years. For now - preupgrade = epic fail * 2. If anyone has any thoughts on what has caused either of the two remaining problems (the kernel panic on the F15 kernel or the failure to run on the F14 kernel) I'd be happy to hear them. ITMT, I guess I'll start building a recovery CD to try and fix this mess. Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part -- users mailing list users@lists.fedoraproject.org To unsubscribe or
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
On 06/02/2011 10:13 AM, GeeKer Wang wrote: Hello, guys, I used preupgrade to upgrade fc14 to fc15, and everything seemed fine. But when I reboot, I just find that kernel-fc15 is not installed. I can't tell from what you written above, but, pre-upgrade is a multi step process. Here are the steps in a nut-shell: 1) run preupgrade and have it download packages to a local repository on your machine. It should also modify your /etc/grub.conf file to add an entry which will continue the upgrade in step 2. When this step completes, it should ask you to reboot your computer. 2) when you reboot, it should automatically select the F15 upgrade entry and boot into the second stage installer and start installing the downloaded packages on to your system. This is the step that fails for many people. Places to look for problems are in /etc/grub.conf and in /boot/upgrade/. In the latter you should have at least 3 files: initrd.img, ks.cfg, and vmlinuz. If not, something else has gone wrong for you to look into. If everything goes right, when the packages are finished installing (and yet another change is made to your /etc/grub.conf file), the system will reboot yet again 3) The final reboot will run a script called firstboot which should clean up from the upgrade process, and remove the old kernel versions from your system. It will also check to make sure that any new packages are configured properly (or prompt you for their configuration) so that F15 will run correctly for you upon subsequent reboots. If you get this far, preupgrade has done its job correctly and you should be all set. There are no vmlinuz-xxx.fc15.i686 and initramfs--fc15.i686.img in /boot, no entry about fc-15 written in grub.conf, and nothing related to fc15 is found in /lib/modules. I just try to download kernel and install it manually. But I don't know whether there are any other packages forgotten. What does rpm -qa | grep fc15 tell you? (there should be *lots* of hits). If it can't find any fc15 packages installed, you haven't upgraded yet. -- Bob -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
On 06/02/2011 01:41 PM, Kevin J. Cummings wrote: I can't tell from what you written above, but, pre-upgrade is a multi step process. Here are the steps in a nut-shell: 0) Install preupgrade using yum or yumex if you haven't ever used it before. (AFAIK it's not part of the default install.) 2.5) Before rebooting, check grub.conf (You can find it in /etc or in /boot because the first one is only a link to the other.) and make sure it's been properly modified. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
Hello, Kevin I can't enter my system now, however, I check the upgraded system using livecd. After login in my system by chroot in livecd, by checking rpm -qa |grep fc15 , I am sure that many fc15 packages have installed. And all the 3 steps you mentioned have passed, which takes a couple of hours. So at least most fc15 packages have installed. I just found a empty upgrade directory in /boot, and nothing related to fc15 there. I guess preupgrade must forget to install kernel. So what I should do to rescue it is to upgrade/install kernel in chroot environment. But I don't know how to upgrade kernel with a kernel RPM file. Any advice? On Thu, Jun 2, 2011 at 4:41 PM, Kevin J. Cummings cummi...@kjchome.homeip.net wrote: On 06/02/2011 10:13 AM, GeeKer Wang wrote: Hello, guys, I used preupgrade to upgrade fc14 to fc15, and everything seemed fine. But when I reboot, I just find that kernel-fc15 is not installed. I can't tell from what you written above, but, pre-upgrade is a multi step process. Here are the steps in a nut-shell: 1) run preupgrade and have it download packages to a local repository on your machine. It should also modify your /etc/grub.conf file to add an entry which will continue the upgrade in step 2. When this step completes, it should ask you to reboot your computer. 2) when you reboot, it should automatically select the F15 upgrade entry and boot into the second stage installer and start installing the downloaded packages on to your system. This is the step that fails for many people. Places to look for problems are in /etc/grub.conf and in /boot/upgrade/. In the latter you should have at least 3 files: initrd.img, ks.cfg, and vmlinuz. If not, something else has gone wrong for you to look into. If everything goes right, when the packages are finished installing (and yet another change is made to your /etc/grub.conf file), the system will reboot yet again 3) The final reboot will run a script called firstboot which should clean up from the upgrade process, and remove the old kernel versions from your system. It will also check to make sure that any new packages are configured properly (or prompt you for their configuration) so that F15 will run correctly for you upon subsequent reboots. If you get this far, preupgrade has done its job correctly and you should be all set. There are no vmlinuz-xxx.fc15.i686 and initramfs--fc15.i686.img in /boot, no entry about fc-15 written in grub.conf, and nothing related to fc15 is found in /lib/modules. I just try to download kernel and install it manually. But I don't know whether there are any other packages forgotten. What does rpm -qa | grep fc15 tell you? (there should be *lots* of hits). If it can't find any fc15 packages installed, you haven't upgraded yet. -- Bob -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- Bob -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
On 06/02/2011 09:00 PM, GeeKer Wang wrote: Hello, Kevin I can't enter my system now, however, I check the upgraded system using livecd. After login in my system by chroot in livecd, by checking rpm -qa |grep fc15 , I am sure that many fc15 packages have installed. And all the 3 steps you mentioned have passed, which takes a couple of hours. So at least most fc15 packages have installed. OK, so while looking at the live system chrooted to your system, what is the response to: rpm -q kernel Let's find out if the proper kernel got installed. If so, then we'll have a look at your /etc/grub.conf (which is just a symlink to: /boot/grub/grub.conf). And then we'll try and figure out how to install it by running grubby by hand I just found a empty upgrade directory in /boot, and nothing related to fc15 there. I guess preupgrade must forget to install kernel. Not likely, though its possible in some bizarre set of circumstances. Are you 100% sure that preupgrade didn't stop prematurely with some sort of error message? So what I should do to rescue it is to upgrade/install kernel in chroot environment. But I don't know how to upgrade kernel with a kernel RPM file. Any advice? Let's find out if it got installed first. If it did, and it didn't install an entry in the grub menu, then it was a script-let of the kernel RPM which errored. If it did not get installed, it should be easy enough to install one by hand (with RPM) and see if it installs without any errors (and correctly modifies your /etc/grub.conf file). If it requires dependencies to install, then you will have other problems. What I've ended up doing in circumstances like these is to plow ahead and continue the upgrade in pieces, by hand after ensuring that: 0) I have read the Fedora release notes for the version I am installing, looking for gotcha's that I may have tripped over! 1) I have a proper kernel installed and working (bootable), and the fedora-release RPM is the proper version and architecture. 2) yum and rpm (and all of their dependants) are up-to-date. 3) my network is up and running so I can do (yum) updates over the network. 4) essentially finish the upgrade by updating all of the remaining out-of-date RPMs on the system. Yes, you could try and continue from that point with yum -y update, but you would most likely need to do it in pieces (to get around all of the broken packages) and also use the --skip-broken option to yum. I like to try it alphabetically (ie yum -y update a*), but usually end up breaking down each leading letter looking for packages that update nicely, and then figure out what's wrong with the packages that don't. This is not a quick and easy process. I've sometimes spent weeks cleaning up my server or my laptop from a failed upgrade in this fashion, but, in the end, my system has been upgraded, and not re-installed (for some reason, an updated system seems to me to be less likely to have some necessary local configuration lost than an installed update, but, I could be wrong). In the end, I learn a *lot* about Fedora, how it works (and how it sometimes doesn't work B^), and how to fix it. What doesn't work in this process is if some new set of packages obsoletes an installed set of packages, this method may not properly install the new set of packages. That's ultimately because Anaconda failed during preupgrade, but didn't leave a sufficient amount of information to properly fix the upgrade. If you are not able to install/boot a proper f15 kernel, let us know, there are ways (even more nefarious that a yum upgrade) to update your system piecemeal, even from an f14 kernel On Thu, Jun 2, 2011 at 4:41 PM, Kevin J. Cummings cummi...@kjchome.homeip.net mailto:cummi...@kjchome.homeip.net wrote: On 06/02/2011 10:13 AM, GeeKer Wang wrote: Hello, guys, I used preupgrade to upgrade fc14 to fc15, and everything seemed fine. But when I reboot, I just find that kernel-fc15 is not installed. I can't tell from what you written above, but, pre-upgrade is a multi step process. Here are the steps in a nut-shell: 1) run preupgrade and have it download packages to a local repository on your machine. It should also modify your /etc/grub.conf file to add an entry which will continue the upgrade in step 2. When this step completes, it should ask you to reboot your computer. 2) when you reboot, it should automatically select the F15 upgrade entry and boot into the second stage installer and start installing the downloaded packages on to your system. This is the step that fails for many people. Places to look for problems are in /etc/grub.conf and in /boot/upgrade/. In the latter you should have at least 3 files: initrd.img, ks.cfg, and vmlinuz. If not, something else has gone wrong for you to look into. If everything goes right, when the
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
When I tried rpm -ivh kernel-2.6.38.6-27.fc15.i686 in chroot environment, it complains grubby fatal error: unable to find a suitable template. I guess preupgrade get the same problem and just skip the kernel install. On Thu, Jun 2, 2011 at 9:00 PM, GeeKer Wang wwthu...@gmail.com wrote: Hello, Kevin I can't enter my system now, however, I check the upgraded system using livecd. After login in my system by chroot in livecd, by checking rpm -qa |grep fc15 , I am sure that many fc15 packages have installed. And all the 3 steps you mentioned have passed, which takes a couple of hours. So at least most fc15 packages have installed. I just found a empty upgrade directory in /boot, and nothing related to fc15 there. I guess preupgrade must forget to install kernel. So what I should do to rescue it is to upgrade/install kernel in chroot environment. But I don't know how to upgrade kernel with a kernel RPM file. Any advice? On Thu, Jun 2, 2011 at 4:41 PM, Kevin J. Cummings cummi...@kjchome.homeip.net wrote: On 06/02/2011 10:13 AM, GeeKer Wang wrote: Hello, guys, I used preupgrade to upgrade fc14 to fc15, and everything seemed fine. But when I reboot, I just find that kernel-fc15 is not installed. I can't tell from what you written above, but, pre-upgrade is a multi step process. Here are the steps in a nut-shell: 1) run preupgrade and have it download packages to a local repository on your machine. It should also modify your /etc/grub.conf file to add an entry which will continue the upgrade in step 2. When this step completes, it should ask you to reboot your computer. 2) when you reboot, it should automatically select the F15 upgrade entry and boot into the second stage installer and start installing the downloaded packages on to your system. This is the step that fails for many people. Places to look for problems are in /etc/grub.conf and in /boot/upgrade/. In the latter you should have at least 3 files: initrd.img, ks.cfg, and vmlinuz. If not, something else has gone wrong for you to look into. If everything goes right, when the packages are finished installing (and yet another change is made to your /etc/grub.conf file), the system will reboot yet again 3) The final reboot will run a script called firstboot which should clean up from the upgrade process, and remove the old kernel versions from your system. It will also check to make sure that any new packages are configured properly (or prompt you for their configuration) so that F15 will run correctly for you upon subsequent reboots. If you get this far, preupgrade has done its job correctly and you should be all set. There are no vmlinuz-xxx.fc15.i686 and initramfs--fc15.i686.img in /boot, no entry about fc-15 written in grub.conf, and nothing related to fc15 is found in /lib/modules. I just try to download kernel and install it manually. But I don't know whether there are any other packages forgotten. What does rpm -qa | grep fc15 tell you? (there should be *lots* of hits). If it can't find any fc15 packages installed, you haven't upgraded yet. -- Bob -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- Bob -- Bob -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
On Thu, Jun 2, 2011 at 9:29 PM, Kevin J. Cummings cummi...@kjchome.homeip.net wrote: On 06/02/2011 09:00 PM, GeeKer Wang wrote: Hello, Kevin I can't enter my system now, however, I check the upgraded system using livecd. After login in my system by chroot in livecd, by checking rpm -qa |grep fc15 , I am sure that many fc15 packages have installed. And all the 3 steps you mentioned have passed, which takes a couple of hours. So at least most fc15 packages have installed. OK, so while looking at the live system chrooted to your system, what is the response to: rpm -q kernel Let's find out if the proper kernel got installed. If so, then we'll have a look at your /etc/grub.conf (which is just a symlink to: /boot/grub/grub.conf). And then we'll try and figure out how to install it by running grubby by hand There is no fc15 kernel, only kernel-2.6.35.12-88.fc14.i686 kernel-2.6.35.12-90.fc14.i686 kernel-2.6.35.13-91.fc14.i686 I just found a empty upgrade directory in /boot, and nothing related to fc15 there. I guess preupgrade must forget to install kernel. Not likely, though its possible in some bizarre set of circumstances. Are you 100% sure that preupgrade didn't stop prematurely with some sort of error message? It halted halfway because of installing openjpeg-devel. I renamed related files and preupgrade continued without other problem. So what I should do to rescue it is to upgrade/install kernel in chroot environment. But I don't know how to upgrade kernel with a kernel RPM file. Any advice? Let's find out if it got installed first. If it did, and it didn't install an entry in the grub menu, then it was a script-let of the kernel RPM which errored. If it did not get installed, it should be easy enough to install one by hand (with RPM) and see if it installs without any errors (and correctly modifies your /etc/grub.conf file). If it requires dependencies to install, then you will have other problems. When I tried rpm -ivh kernel-2.6.38.6-fc15.i686.rpm, it failed with grubby fatal error: unable to find a suitable template. But it created some files(eg. vmlinuz-xxx-fc15, initramfs-xxx.img) in /boot and /lib/modules. However, grub-install didn't recognize these files. What I've ended up doing in circumstances like these is to plow ahead and continue the upgrade in pieces, by hand after ensuring that: 0) I have read the Fedora release notes for the version I am installing, looking for gotcha's that I may have tripped over! 1) I have a proper kernel installed and working (bootable), and the fedora-release RPM is the proper version and architecture. 2) yum and rpm (and all of their dependants) are up-to-date. 3) my network is up and running so I can do (yum) updates over the network. 4) essentially finish the upgrade by updating all of the remaining out-of-date RPMs on the system. Yes, you could try and continue from that point with yum -y update, but you would most likely need to do it in pieces (to get around all of the broken packages) and also use the --skip-broken option to yum. I like to try it alphabetically (ie yum -y update a*), but usually end up breaking down each leading letter looking for packages that update nicely, and then figure out what's wrong with the packages that don't. This is not a quick and easy process. I've sometimes spent weeks cleaning up my server or my laptop from a failed upgrade in this fashion, but, in the end, my system has been upgraded, and not re-installed (for some reason, an updated system seems to me to be less likely to have some necessary local configuration lost than an installed update, but, I could be wrong). In the end, I learn a *lot* about Fedora, how it works (and how it sometimes doesn't work B^), and how to fix it. What doesn't work in this process is if some new set of packages obsoletes an installed set of packages, this method may not properly install the new set of packages. That's ultimately because Anaconda failed during preupgrade, but didn't leave a sufficient amount of information to properly fix the upgrade. If you are not able to install/boot a proper f15 kernel, let us know, there are ways (even more nefarious that a yum upgrade) to update your system piecemeal, even from an f14 kernel On Thu, Jun 2, 2011 at 4:41 PM, Kevin J. Cummings cummi...@kjchome.homeip.net mailto:cummi...@kjchome.homeip.net wrote: On 06/02/2011 10:13 AM, GeeKer Wang wrote: Hello, guys, I used preupgrade to upgrade fc14 to fc15, and everything seemed fine. But when I reboot, I just find that kernel-fc15 is not installed. I can't tell from what you written above, but, pre-upgrade is a multi step process. Here are the steps in a nut-shell: 1) run preupgrade and have it download packages to a local repository on your machine. It should also modify your
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
On 06/02/2011 10:31 PM, GeeKer Wang wrote: On Thu, Jun 2, 2011 at 9:29 PM, Kevin J. Cummings cummi...@kjchome.homeip.net mailto:cummi...@kjchome.homeip.net wrote: OK, so while looking at the live system chrooted to your system, what is the response to: rpm -q kernel Let's find out if the proper kernel got installed. If so, then we'll have a look at your /etc/grub.conf (which is just a symlink to: /boot/grub/grub.conf). And then we'll try and figure out how to install it by running grubby by hand There is no fc15 kernel, only kernel-2.6.35.12-88.fc14.i686 kernel-2.6.35.12-90.fc14.i686 kernel-2.6.35.13-91.fc14.i686 OK, so the f15 kernel never got installed. That would bring into question a whole raft of other potential problems that you will probably need to clean uop from as well Are you 100% sure that preupgrade didn't stop prematurely with some sort of error message? It halted halfway because of installing openjpeg-devel. I renamed related files and preupgrade continued without other problem. Except that it seemed to miss installing the kernel If it did not get installed, it should be easy enough to install one by hand (with RPM) and see if it installs without any errors (and correctly modifies your /etc/grub.conf file). If it requires dependencies to install, then you will have other problems. When I tried rpm -ivh kernel-2.6.38.6-fc15.i686.rpm, it failed with grubby fatal error: unable to find a suitable template. But it created some files(eg. vmlinuz-xxx-fc15, initramfs-xxx.img) in /boot and /lib/modules. However, grub-install didn't recognize these files. We can always add the proper lines to /etc/grub.conf by hand if we have to What is the contents of your current /etc/grub.conf file? What and where are the f15 kernel files? (you are looking for at least a vmlinuz- file and possibly an initramfs- file and possibly a System.map- file as well) I have the following on my botched f15 upgrade: /boot config-2.6.35.12-90.fc14.i686 efi initramfs-2.6.35.12-90.fc14.i686.img initrd-plymouth.img System.map-2.6.35.13-91.fc14.i686 vmlinuz-2.6.35.12-90.fc14.i686 config-2.6.35.13-91.fc14.i686 elf-memtest86+-4.10 initramfs-2.6.35.13-91.fc14.i686.img memtest86+-4.10 System.map-2.6.38.6-27.fc15.i686 vmlinuz-2.6.35.13-91.fc14.i686 config-2.6.38.6-27.fc15.i686 grub initramfs-2.6.38.6-27.fc15.i686.img System.map-2.6.35.12-90.fc14.i686 upgradevmlinuz-2.6.38.6-27.fc15.i686 and my grub.conf contains this entry for f15 (which boots for me): title Fedora (2.6.38.6-27.fc15.i686) root (hd0,0) kernel /boot/vmlinuz-2.6.38.6-27.fc15.i686 ro root=UUID=f3299b81-9fc4-46eb-9189-a79591e894a1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM vga=0x123 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us noiswmd initrd /boot/initramfs-2.6.38.6-27.fc15.i686.img You will need to change the UUID to match your disk, and whether or not you need all of the boot options that I have, you can compare to your f14 kernel entries in your grub.conf file. All of the options on my f15 kernel line appear verbatim on my f14 kernel lines. And my test system is currently booted in f15 (or some subset of it. B^) -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
On Fri, Jun 3, 2011 at 10:59 AM, Kevin J. Cummings cummi...@kjchome.homeip.net wrote: On 06/02/2011 10:31 PM, GeeKer Wang wrote: On Thu, Jun 2, 2011 at 9:29 PM, Kevin J. Cummings cummi...@kjchome.homeip.net mailto:cummi...@kjchome.homeip.net wrote: OK, so while looking at the live system chrooted to your system, what is the response to: rpm -q kernel Let's find out if the proper kernel got installed. If so, then we'll have a look at your /etc/grub.conf (which is just a symlink to: /boot/grub/grub.conf). And then we'll try and figure out how to install it by running grubby by hand There is no fc15 kernel, only kernel-2.6.35.12-88.fc14.i686 kernel-2.6.35.12-90.fc14.i686 kernel-2.6.35.13-91.fc14.i686 OK, so the f15 kernel never got installed. That would bring into question a whole raft of other potential problems that you will probably need to clean uop from as well Are you 100% sure that preupgrade didn't stop prematurely with some sort of error message? It halted halfway because of installing openjpeg-devel. I renamed related files and preupgrade continued without other problem. Except that it seemed to miss installing the kernel If it did not get installed, it should be easy enough to install one by hand (with RPM) and see if it installs without any errors (and correctly modifies your /etc/grub.conf file). If it requires dependencies to install, then you will have other problems. When I tried rpm -ivh kernel-2.6.38.6-fc15.i686.rpm, it failed with grubby fatal error: unable to find a suitable template. But it created some files(eg. vmlinuz-xxx-fc15, initramfs-xxx.img) in /boot and /lib/modules. However, grub-install didn't recognize these files. We can always add the proper lines to /etc/grub.conf by hand if we have to What is the contents of your current /etc/grub.conf file? What and where are the f15 kernel files? (you are looking for at least a vmlinuz- file and possibly an initramfs- file and possibly a System.map- file as well) I have the following on my botched f15 upgrade: /boot config-2.6.35.12-90.fc14.i686 efi initramfs-2.6.35.12-90.fc14.i686.img initrd-plymouth.img System.map-2.6.35.13-91.fc14.i686 vmlinuz-2.6.35.12-90.fc14.i686 config-2.6.35.13-91.fc14.i686 elf-memtest86+-4.10 initramfs-2.6.35.13-91.fc14.i686.img memtest86+-4.10 System.map-2.6.38.6-27.fc15.i686 vmlinuz-2.6.35.13-91.fc14.i686 config-2.6.38.6-27.fc15.i686 grub initramfs-2.6.38.6-27.fc15.i686.img System.map-2.6.35.12-90.fc14.i686 upgradevmlinuz-2.6.38.6-27.fc15.i686 and my grub.conf contains this entry for f15 (which boots for me): title Fedora (2.6.38.6-27.fc15.i686) root (hd0,0) kernel /boot/vmlinuz-2.6.38.6-27.fc15.i686 ro root=UUID=f3299b81-9fc4-46eb-9189-a79591e894a1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM vga=0x123 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us noiswmd initrd /boot/initramfs-2.6.38.6-27.fc15.i686.img You will need to change the UUID to match your disk, and whether or not you need all of the boot options that I have, you can compare to your f14 kernel entries in your grub.conf file. All of the options on my f15 kernel line appear verbatim on my f14 kernel lines. And my test system is currently booted in f15 (or some subset of it. B^) I have these files in /boot, and I tried to revise entry in grub.conf. Unfortunately, It complains cannot find /proc/cmdline when booting... -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- Bob -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade fc14 to fc15 failed, kernel is not installed
On 06/02/2011 11:08 PM, GeeKer Wang wrote: On Fri, Jun 3, 2011 at 10:59 AM, Kevin J. Cummings cummi...@kjchome.homeip.net mailto:cummi...@kjchome.homeip.net wrote: I have the following on my botched f15 upgrade: /boot config-2.6.35.12-90.fc14.i686 efi initramfs-2.6.35.12-90.fc14.i686.img initrd-plymouth.img System.map-2.6.35.13-91.fc14.i686 vmlinuz-2.6.35.12-90.fc14.i686 config-2.6.35.13-91.fc14.i686 elf-memtest86+-4.10 initramfs-2.6.35.13-91.fc14.i686.img memtest86+-4.10 System.map-2.6.38.6-27.fc15.i686 vmlinuz-2.6.35.13-91.fc14.i686 config-2.6.38.6-27.fc15.i686 grub initramfs-2.6.38.6-27.fc15.i686.img System.map-2.6.35.12-90.fc14.i686 upgradevmlinuz-2.6.38.6-27.fc15.i686 and my grub.conf contains this entry for f15 (which boots for me): title Fedora (2.6.38.6-27.fc15.i686) root (hd0,0) kernel /boot/vmlinuz-2.6.38.6-27.fc15.i686 ro root=UUID=f3299b81-9fc4-46eb-9189-a79591e894a1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM vga=0x123 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us noiswmd initrd /boot/initramfs-2.6.38.6-27.fc15.i686.img I hate wrapping in email programs! Everything on your kernel line appears on ONE LINE, right? Not wrapped as it appears above? You will need to change the UUID to match your disk, and whether or not you need all of the boot options that I have, you can compare to your f14 kernel entries in your grub.conf file. All of the options on my f15 kernel line appear verbatim on my f14 kernel lines. And my test system is currently booted in f15 (or some subset of it. B^) I have these files in /boot, and I tried to revise entry in grub.conf. Unfortunately, It complains cannot find /proc/cmdline when booting... Exact error message please. The /proc filesystem doesn't get mounted until sometime after the booted kernel gets running. Why is there a reference to it when booting. Originally I thought it might be some reference in your initramfs image, but now I'm not so sure. Exactly when does this message occur? Have you removed the quiet and rhgb options from your kernel line in grub? Its nice to know exactly what's going on during the boot process when messages like that appear. How far into the kernel boot process do you actually get? Please describe in great detail. B^) Ideally I'd like to be there next to you so I can see for myself. The next best thing would be to capture it in video and post a link to the .mpg file. Its not more than a few seconds long, right? B^) B^) -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade questions
On Mon, 25 Apr 2011 14:13:39 + (UTC) Beartooth bearto...@comcast.net wrote: Even with F15 abandoning metacity, and possibly also whatever is causing the other minor issues, my guess is that I'll be better off doing all fresh installs this time, except perhaps on one brand new PC.. In fact, I'm already in process of copying all my data to an external USB hard drive. I'm copying my home directory, /etc, /usr/bin (though not /bin), / usr/sbin, and /usr/share from each PC. Are those the ones I need? (Are any of them superfluous?) /home (and /etc) should be everything you need. If you have installed stuff locally, then backing up (or making a list of the stuff in) /usr/local and /opt might be a good idea. /usr/bin, /usr/sbin and /usr/share are directories used by the distribution's RPM packages. If you're not intending to backup the installed system as well, then you should do a full backup. -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: preupgrade problem on X86_64
On Mon, Dec 13, 2010 at 3:26 PM, L yuan...@gmail.com wrote: On Mon, Dec 13, 2010 at 3:10 PM, stan gr...@q.com wrote: On Mon, 13 Dec 2010 14:13:06 +1100 L yuan...@gmail.com wrote: On Mon, Dec 13, 2010 at 2:06 PM, L yuan...@gmail.com wrote: Hi, I have a PC with Fedora 13 (x86_64). I want to upgrade to Fedora 14 via preupgrade. after following steps [snip] The steps look OK. but there is no packages from fedora 14 downloaded, except VirtualBox etc from outside of fedora were download. After reboot, it started upgrade, but boot back to fedora 13. I tried a few times, the results are the same, No fedora 14 packages downloaded. any one have fix? thanks It sounds like you aren't able to connect to the F14 repos. Are you able to access a F14 repo from the fedora site with a web browser? this is /boot/grub/grub.conf after finished preupgrade process default=1 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Upgrade to Fedora 14 (Laughlin) kernel /boot/upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/ks.cfg stage2=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/install.img initrd /boot/upgrade/initrd.img content list of /var/cache/yum/preupgrade sudo ls -lat /var/cache/yum/preupgrade/*/ /var/cache/yum/preupgrade/repodata/: total 2240 drwxr-xr-x 2 root root 4096 Dec 13 14:01 . drwxr-xr-x 4 root root 4096 Dec 13 14:01 .. -rw-r--r-- 1 root root 1827888 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml -rw-r--r-- 1 root root 416267 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml.gz -rw-r--r-- 1 root root 588 Dec 13 14:01 filelists.sqlite.bz2 -rw-r--r-- 1 root root 1233 Dec 13 14:01 primary.sqlite.bz2 -rw-r--r-- 1 root root 3383 Dec 13 14:01 repomd.xml -rw-r--r-- 1 root root 173 Dec 13 14:01 filelists.xml.gz -rw-r--r-- 1 root root 569 Dec 13 14:01 other.sqlite.bz2 -rw-r--r-- 1 root root 169 Dec 13 14:01 other.xml.gz -rw-r--r-- 1 root root 182 Dec 13 14:01 primary.xml.gz Looks like it's trying. Is there anything in /var/log/messages after the preupgrade failure? Does it tell you why you can't connect to a Fedora repo with some error message? Yes, I can access fedora mirror repo via web broweser here is command line output during preupgrade process preupgrade Loaded plugins: blacklist, fs-snapshot, local, post-transaction-actions, : priorities, protectbase, refresh-updatesd, upgrade-helper, : versionlock, whiteout Detected in-progress upgrade to Fedora 14 (Laughlin) preupgrade-main (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-14arch=$basearch now: http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-14arch=x86_64 preupgrade (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?path=pub/fedora/linux/releases/14/Fedora/$basearch/os now: http://mirrors.fedoraproject.org/mirrorlist?path=pub/fedora/linux/releases/14/Fedora/x86_64/os preupgrade-Dropbox (baseurl) url: http://linux.dropbox.com/fedora/14/ now: http://linux.dropbox.com/fedora/14/ unknown metadata being downloaded: repomdiv1kEstmp.xml preupgrade-_local (baseurl) url: file:/var/lib/yum/plugins/local now: file:/var/lib/yum/plugins/local unknown metadata being downloaded: repomdcxzBXKtmp.xml preupgrade-fedora (mirrorlist) url: https://mirrors.fedoraproject.org/metalink?repo=fedora-14arch=x86_64 now: https://mirrors.fedoraproject.org/metalink?repo=fedora-14arch=x86_64 Can't set up new repo preupgrade-fedora - removing preupgrade-rpmfusion-free (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-14arch=x86_64 unknown metadata being downloaded: repomdLW15Tntmp.xml preupgrade-rpmfusion-free-updates (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-released-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-released-14arch=x86_64 unknown metadata being downloaded: repomdjDybdRtmp.xml preupgrade-rpmfusion-nonfree (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-14arch=x86_64 unknown metadata being downloaded: repomdcN5VAttmp.xml preupgrade-rpmfusion-nonfree-updates (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-updates-released-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-updates-released-14arch=x86_64 unknown metadata being downloaded: repomdfmOtL6tmp.xml preupgrade-updates (mirrorlist) url: https://mirrors.fedoraproject.org/metalink?repo=updates-released-f14arch=x86_64
Re: preupgrade problem on X86_64
On Mon, 13 Dec 2010 15:26:58 +1100 L yuan...@gmail.com wrote: Yes, I can access fedora mirror repo via web broweser here is command line output during preupgrade process preupgrade Loaded plugins: blacklist, fs-snapshot, local, post-transaction-actions, : priorities, protectbase, refresh-updatesd, upgrade-helper, : versionlock, whiteout This is valuable. I think you should disable some (all) of these plugins until after you have preupgraded. Just in case. You will find the configuration files in /etc/yum/pluginconf.d/ Edit them and turn them off individually or edit /etc/yum.conf and set plugins=0 instead of plugins=1. When you are finished preupgrading, you can turn them back on if you want. Detected in-progress upgrade to Fedora 14 (Laughlin) preupgrade-main (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-14arch=$basearch now: http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-14arch=x86_64 preupgrade (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?path=pub/fedora/linux/releases/14/Fedora/$basearch/os now: http://mirrors.fedoraproject.org/mirrorlist?path=pub/fedora/linux/releases/14/Fedora/x86_64/os preupgrade-Dropbox (baseurl) url: http://linux.dropbox.com/fedora/14/ now: http://linux.dropbox.com/fedora/14/ unknown metadata being downloaded: repomdiv1kEstmp.xml preupgrade-_local (baseurl) url: file:/var/lib/yum/plugins/local now: file:/var/lib/yum/plugins/local unknown metadata being downloaded: repomdcxzBXKtmp.xml This seems to indicate that at least the local plugin is interfering with getting the F14 preupgrade repo information. preupgrade-fedora (mirrorlist) url: https://mirrors.fedoraproject.org/metalink?repo=fedora-14arch=x86_64 now: https://mirrors.fedoraproject.org/metalink?repo=fedora-14arch=x86_64 Can't set up new repo preupgrade-fedora - removing Here is your failure preupgrade-rpmfusion-free (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-14arch=x86_64 unknown metadata being downloaded: repomdLW15Tntmp.xml another failure preupgrade-rpmfusion-free-updates (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-released-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-released-14arch=x86_64 unknown metadata being downloaded: repomdjDybdRtmp.xml another failure preupgrade-rpmfusion-nonfree (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-14arch=x86_64 unknown metadata being downloaded: repomdcN5VAttmp.xml preupgrade-rpmfusion-nonfree-updates (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-updates-released-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-updates-released-14arch=x86_64 unknown metadata being downloaded: repomdfmOtL6tmp.xml another failure, again probably a plugin caused failure preupgrade-updates (mirrorlist) url: https://mirrors.fedoraproject.org/metalink?repo=updates-released-f14arch=x86_64 now: https://mirrors.fedoraproject.org/metalink?repo=updates-released-f14arch=x86_64 Can't set up new repo preupgrade-updates - removing preupgrade-virtualbox (baseurl) url: http://download.virtualbox.org/virtualbox/rpm/fedora/14/x86_64 now: http://download.virtualbox.org/virtualbox/rpm/fedora/14/x86_64 unknown metadata being downloaded: repomd3bZGRntmp.xml 0 packages excluded due to repository protections unknown metadata being again, here is a failure, probably due to one of the plugins downloaded: MEMORY Fetched treeinfo from http://mirror.aarnet.edu.au/pub/fedora/linux/releases/14/Fedora/x86_64/os//.treeinfo treeinfo timestamp: Fri Oct 22 05:27:17 2010 /boot/upgrade/vmlinuz checksum OK /boot/upgrade/initrd.img checksum OK /boot/upgrade/install.img checksum OK Downloading 42.7MB Available disk space for /var/cache/yum/preupgrade: 3.6GB Upgrade requires 500.0MB Available disk space for /usr: 3.5GB Kernel requires 26.0MB Available disk space for /boot: 3.5GB Generating metadata for preupgrade repo DEBUG /sbin/grubby --title=Upgrade to Fedora 14 (Laughlin) --remove-kernel=/boot/upgrade/vmlinuz --add-kernel=/boot/upgrade/vmlinuz --initrd=/boot/upgrade/initrd.img --args=preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/ks.cfg stage2=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/install.img there is nothing from /var/log/messages It seems the preupgrade messages aren't logged. But no matter, your clever capture above caught what was needed. You should probably open a bugzilla, https://bugzilla.redhat.com/ , to have preupgrade abort with an appropriate error message when it can't download repo information or ignore plugins during the preupgrade
Re: preupgrade problem on X86_64
On Mon, Dec 13, 2010 at 2:06 PM, L yuan...@gmail.com wrote: Hi, I have a PC with Fedora 13 (x86_64). I want to upgrade to Fedora 14 via preupgrade. after following steps yum clean all yum update yum update preupgrade preupgrade the process started, it seems did Download release info Download installer images Determine which packages to download Download packages Prepare and test upgrade but there is no packages from fedora 14 downloaded, except VirtualBox etc from outside of fedora were download. After reboot, it started upgrade, but boot back to fedora 13. I tried a few times, the results are the same, No fedora 14 packages downloaded. any one have fix? thanks this is /boot/grub/grub.conf after finished preupgrade process default=1 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Upgrade to Fedora 14 (Laughlin) kernel /boot/upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/ks.cfg stage2=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/install.img initrd /boot/upgrade/initrd.img content list of /var/cache/yum/preupgrade sudo ls -lat /var/cache/yum/preupgrade/*/ /var/cache/yum/preupgrade/repodata/: total 2240 drwxr-xr-x 2 root root4096 Dec 13 14:01 . drwxr-xr-x 4 root root4096 Dec 13 14:01 .. -rw-r--r-- 1 root root 1827888 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml -rw-r--r-- 1 root root 416267 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml.gz -rw-r--r-- 1 root root 588 Dec 13 14:01 filelists.sqlite.bz2 -rw-r--r-- 1 root root1233 Dec 13 14:01 primary.sqlite.bz2 -rw-r--r-- 1 root root3383 Dec 13 14:01 repomd.xml -rw-r--r-- 1 root root 173 Dec 13 14:01 filelists.xml.gz -rw-r--r-- 1 root root 569 Dec 13 14:01 other.sqlite.bz2 -rw-r--r-- 1 root root 169 Dec 13 14:01 other.xml.gz -rw-r--r-- 1 root root 182 Dec 13 14:01 primary.xml.gz /var/cache/yum/preupgrade/packages/: total 8 drwxr-xr-x 4 root root 4096 Dec 13 14:01 .. drwxr-xr-x 2 root root 4096 Dec 13 13:39 . -- Linux Toys http://linuxishbell.wordpress.com/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: preupgrade problem on X86_64
On Mon, 13 Dec 2010 14:13:06 +1100 L yuan...@gmail.com wrote: On Mon, Dec 13, 2010 at 2:06 PM, L yuan...@gmail.com wrote: Hi, I have a PC with Fedora 13 (x86_64). I want to upgrade to Fedora 14 via preupgrade. after following steps [snip] The steps look OK. but there is no packages from fedora 14 downloaded, except VirtualBox etc from outside of fedora were download. After reboot, it started upgrade, but boot back to fedora 13. I tried a few times, the results are the same, No fedora 14 packages downloaded. any one have fix? thanks It sounds like you aren't able to connect to the F14 repos. Are you able to access a F14 repo from the fedora site with a web browser? this is /boot/grub/grub.conf after finished preupgrade process default=1 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Upgrade to Fedora 14 (Laughlin) kernel /boot/upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/ks.cfg stage2=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/install.img initrd /boot/upgrade/initrd.img content list of /var/cache/yum/preupgrade sudo ls -lat /var/cache/yum/preupgrade/*/ /var/cache/yum/preupgrade/repodata/: total 2240 drwxr-xr-x 2 root root4096 Dec 13 14:01 . drwxr-xr-x 4 root root4096 Dec 13 14:01 .. -rw-r--r-- 1 root root 1827888 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml -rw-r--r-- 1 root root 416267 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml.gz -rw-r--r-- 1 root root 588 Dec 13 14:01 filelists.sqlite.bz2 -rw-r--r-- 1 root root1233 Dec 13 14:01 primary.sqlite.bz2 -rw-r--r-- 1 root root3383 Dec 13 14:01 repomd.xml -rw-r--r-- 1 root root 173 Dec 13 14:01 filelists.xml.gz -rw-r--r-- 1 root root 569 Dec 13 14:01 other.sqlite.bz2 -rw-r--r-- 1 root root 169 Dec 13 14:01 other.xml.gz -rw-r--r-- 1 root root 182 Dec 13 14:01 primary.xml.gz Looks like it's trying. Is there anything in /var/log/messages after the preupgrade failure? Does it tell you why you can't connect to a Fedora repo with some error message? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: preupgrade problem on X86_64
On Mon, Dec 13, 2010 at 3:10 PM, stan gr...@q.com wrote: On Mon, 13 Dec 2010 14:13:06 +1100 L yuan...@gmail.com wrote: On Mon, Dec 13, 2010 at 2:06 PM, L yuan...@gmail.com wrote: Hi, I have a PC with Fedora 13 (x86_64). I want to upgrade to Fedora 14 via preupgrade. after following steps [snip] The steps look OK. but there is no packages from fedora 14 downloaded, except VirtualBox etc from outside of fedora were download. After reboot, it started upgrade, but boot back to fedora 13. I tried a few times, the results are the same, No fedora 14 packages downloaded. any one have fix? thanks It sounds like you aren't able to connect to the F14 repos. Are you able to access a F14 repo from the fedora site with a web browser? this is /boot/grub/grub.conf after finished preupgrade process default=1 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Upgrade to Fedora 14 (Laughlin) kernel /boot/upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/ks.cfg stage2=hd:UUID=3680f081-fa85-44d9-9d34-a7915f0f976c:/boot/upgrade/install.img initrd /boot/upgrade/initrd.img content list of /var/cache/yum/preupgrade sudo ls -lat /var/cache/yum/preupgrade/*/ /var/cache/yum/preupgrade/repodata/: total 2240 drwxr-xr-x 2 root root 4096 Dec 13 14:01 . drwxr-xr-x 4 root root 4096 Dec 13 14:01 .. -rw-r--r-- 1 root root 1827888 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml -rw-r--r-- 1 root root 416267 Dec 13 14:01 1d46a2073097bdb6b7b6f6fba60e4525ca0bf2d1165026a3e1c87b0b2abaf07f-Fedora-14-comps.xml.gz -rw-r--r-- 1 root root 588 Dec 13 14:01 filelists.sqlite.bz2 -rw-r--r-- 1 root root 1233 Dec 13 14:01 primary.sqlite.bz2 -rw-r--r-- 1 root root 3383 Dec 13 14:01 repomd.xml -rw-r--r-- 1 root root 173 Dec 13 14:01 filelists.xml.gz -rw-r--r-- 1 root root 569 Dec 13 14:01 other.sqlite.bz2 -rw-r--r-- 1 root root 169 Dec 13 14:01 other.xml.gz -rw-r--r-- 1 root root 182 Dec 13 14:01 primary.xml.gz Looks like it's trying. Is there anything in /var/log/messages after the preupgrade failure? Does it tell you why you can't connect to a Fedora repo with some error message? Yes, I can access fedora mirror repo via web broweser here is command line output during preupgrade process preupgrade Loaded plugins: blacklist, fs-snapshot, local, post-transaction-actions, : priorities, protectbase, refresh-updatesd, upgrade-helper, : versionlock, whiteout Detected in-progress upgrade to Fedora 14 (Laughlin) preupgrade-main (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-14arch=$basearch now: http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-14arch=x86_64 preupgrade (mirrorlist) url: http://mirrors.fedoraproject.org/mirrorlist?path=pub/fedora/linux/releases/14/Fedora/$basearch/os now: http://mirrors.fedoraproject.org/mirrorlist?path=pub/fedora/linux/releases/14/Fedora/x86_64/os preupgrade-Dropbox (baseurl) url: http://linux.dropbox.com/fedora/14/ now: http://linux.dropbox.com/fedora/14/ unknown metadata being downloaded: repomdiv1kEstmp.xml preupgrade-_local (baseurl) url: file:/var/lib/yum/plugins/local now: file:/var/lib/yum/plugins/local unknown metadata being downloaded: repomdcxzBXKtmp.xml preupgrade-fedora (mirrorlist) url: https://mirrors.fedoraproject.org/metalink?repo=fedora-14arch=x86_64 now: https://mirrors.fedoraproject.org/metalink?repo=fedora-14arch=x86_64 Can't set up new repo preupgrade-fedora - removing preupgrade-rpmfusion-free (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-14arch=x86_64 unknown metadata being downloaded: repomdLW15Tntmp.xml preupgrade-rpmfusion-free-updates (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-released-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-released-14arch=x86_64 unknown metadata being downloaded: repomdjDybdRtmp.xml preupgrade-rpmfusion-nonfree (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-14arch=x86_64 unknown metadata being downloaded: repomdcN5VAttmp.xml preupgrade-rpmfusion-nonfree-updates (mirrorlist) url: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-updates-released-14arch=x86_64 now: http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-updates-released-14arch=x86_64 unknown metadata being downloaded: repomdfmOtL6tmp.xml preupgrade-updates (mirrorlist) url: https://mirrors.fedoraproject.org/metalink?repo=updates-released-f14arch=x86_64 now: https://mirrors.fedoraproject.org/metalink?repo=updates-released-f14arch=x86_64 Can't
Re: Preupgrade with multiboot: can't find right target (solved?)
On 12/11/10 22:04, John Pilkington wrote: Hi: I'm new to this list and haven't found a searchable archive, but I haven't seen this topic in Google. My box came with MS Vista and I initially added f10, which was fully updated until near EOL. Later I added a second disk and f12, and recently I used preupgrade for f12-to-f13. That went well, and I decided to try f10-to-f14. The packages were identified and put into cache and after I had copied the new lines in grub.conf from disk 1 to disk 2 the upgrade entry appeared in the Grub menu. The kernel boots but I don't think it sees the preupgrade cache and the only option offered is to upgrade the f13 system. I don't want to do that. I've tried various modifications to grub.conf without success. One recent iteration is below. The f10final and f13 entries, and the MS related ones, all work and I've left the f10release entry in case it holds useful data. I downloaded the f14 installer and when I specify its location on disk 2, (/dev/sdb1 /install.img) it runs. Again, the location specified in grub.conf apparently doesn't get used, although it's there too. TIA, John P. - # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd1,1) # kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root # initrd /initrd-[generic-]version.img #boot=/dev/sda default=1 timeout=15 splashimage=(hd1,1)/grub/splash.xpm.gz # hiddenmenu title Upgrade to Fedora 14 (Laughlin) root (hd0,2) kernel /upgrade/vmlinuz preupgrade root=UUID=db9d32af-2d48-42bc-beed-2ed149eb21a1 repo=/var/cache/yum/preupgrade stage2=/var/cache/yum/install.img initrd /upgrade/initrd.img title Fedora (2.6.34.7-61.fc13.x86_64) root (hd1,1) kernel /vmlinuz-2.6.34.7-61.fc13.x86_64 ro root=/dev/mapper/VolGroup-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk rhgb quiet elevator=deadline initrd /initramfs-2.6.34.7-61.fc13.x86_64.img title Fedora10final (2.6.27.41-170.2.117.fc10.x86_64) root (hd0,2) kernel /vmlinuz-2.6.27.41-170.2.117.fc10.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet elevator=deadline initrd /initrd-2.6.27.41-170.2.117.fc10.x86_64.img title Fedora10release (2.6.27.5-117.fc10.x86_64) root (hd0,2) kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=db9d32af-2d48-42bc-beed-2ed149eb21a1 rhgb quiet initrd /initrd-2.6.27.5-117.fc10.x86_64.img title Vista_sp1 rootnoverify (hd0,1) makeactive chainloader +1 title GatewayRecovery rootnoverify (hd0,0) makeactive chainloader +1 --- I had several responses to this, all essentially saying that skipping releases in preupgrade was likely to cause grief. That's probably true, but I thought I would persevere and tried f10 f12; in doing so I found the reason why my previous attempt had failed when it did, which was, as I suspected, that the right partitions were not being accessed. Partly I wasn't clear which system was active at each stage. The box has two /boot partitions, one on each disk. Preupgrade writes to only one, and in this case the active version of grub.conf was the other one, so some editing was needed. The f10 f12 preupgrade created different addressing information and I was able to piece together a working grub.conf entry as follows: title Upgrade to Fedora 12 (Constantine) root (hd0,2) kernel /upgrade/vmlinuz preupgrade repo=hd:UUID=db9d32af-2d48-42bc-beed-2ed149eb21a1:/var/cache/yum/preupgrade stage2=hd:UUID=1421679d-390e-4d2a-9fe9-9bc5c4701721:/upgrade/install.img ks=hd:UUID=1421679d-390e-4d2a-9fe9-9bc5c4701721:/upgrade/ks.cfg initrd /upgrade/initrd.img - Here the repo UUID was that of the target /root partition, and the stage2 and ks UUIDs were that of the target /boot partition (aka (hd0,2)), which this time also (just) held the downloaded install.img. I hadn't been able to create a working syntax for the earlier attempt, and it rather looks as if ks.cfg got lost somewhere. The system booted and the upgrade went ahead, but didn't update either of the grub.conf files, so I modified the old f10 entries to identify the new kernel. The new system works, but not yet perfectly - I still have some nouveau/nvidia conflicts to sort out. It looks hopeful but there may still be trouble ahead. I shall never know whether f10 f14 could have worked! John P -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users
Re: Preupgrade with multiboot: can't find right target
On 11/12/2010 02:04 PM, John Pilkington wrote: Hi: I'm new to this list and haven't found a searchable archive, but I haven't seen this topic in Google. My box came with MS Vista and I initially added f10, which was fully updated until near EOL. Later I added a second disk and f12, and recently I used preupgrade for f12-to-f13. That went well, and I decided to try f10-to-f14. The packages were identified and put into cache and after I had copied the new lines in grub.conf from disk 1 to disk 2 the upgrade entry appeared in the Grub menu. The kernel boots but I don't think it sees the preupgrade cache and the only option offered is to upgrade the f13 system. I don't want to do that. I've tried various modifications to grub.conf without success. One recent iteration is below. The f10final and f13 entries, and the MS related ones, all work and I've left the f10release entry in case it holds useful data. I downloaded the f14 installer and when I specify its location on disk 2, (/dev/sdb1 /install.img) it runs. Again, the location specified in grub.conf apparently doesn't get used, although it's there too. I don't think a preupgrade which skips three releases (10-14) is supported. Single upgrades (10-11, 11-12, 12-13, 13-14) generally work, but skipping intermediate stages is quite problematic. There's a lot of stuff that changed significantly between F10 and F14. -- - Rick Stevens, Systems Engineer, C2 Hosting ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - Grabel's Law: 2 is not equal to 3--not even for large values of 2. - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade with multiboot: can't find right target
On Fri, 12 Nov 2010 22:04:30 + John Pilkington j.p...@tesco.net wrote: My box came with MS Vista and I initially added f10, which was fully updated until near EOL. Later I added a second disk and f12, and recently I used preupgrade for f12-to-f13. That went well, and I decided to try f10-to-f14. The packages were identified and put into cache and after I had copied the new lines in grub.conf from disk 1 to disk 2 the upgrade entry appeared in the Grub menu. The kernel boots but I don't think it sees the preupgrade cache and the only option offered is to upgrade the f13 system. I don't want to do that. This isn't really answering your question, just giving you what I hope is a helpful suggestion. Don't try to preupgrade f10 to f14. From F11 to F12 the format of rpm changed and isn't backward compatible. So you have to do F10 - F11, then F11 - F12, then F12 - F14. You are better off just saving any irreplaceable information from the F10 installation, and doing a fresh install of F14 on those partitions (use custom on the DVD menu to select them). Don't believe me. See the trials and tribulations of a poor soul named Patrick Dupre in the links below. (Ctrl-F, search on Dupre). http://lists.fedoraproject.org/pipermail/users/2010-November/author.html http://lists.fedoraproject.org/pipermail/users/2010-November/author.html -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade with multiboot: can't find right target
On 12/11/10 22:11, Rick Stevens wrote: snip I don't think a preupgrade which skips three releases (10-14) is supported. Single upgrades (10-11, 11-12, 12-13, 13-14) generally work, but skipping intermediate stages is quite problematic. There's a lot of stuff that changed significantly between F10 and F14. Thanks for the quick reply, Nick. That did seem a likely explanation but I thought the wiki said it could (or perhaps might) be done. If no other ideas come up I'll try f10 to f12 as a first step - before f12 goes EOL. John P -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade with multiboot: can't find right target
On Fri, Nov 12, 2010 at 2:33 PM, John Pilkington j.p...@tesco.net wrote: On 12/11/10 22:11, Rick Stevens wrote: snip I don't think a preupgrade which skips three releases (10-14) is supported. Single upgrades (10-11, 11-12, 12-13, 13-14) generally work, but skipping intermediate stages is quite problematic. There's a lot of stuff that changed significantly between F10 and F14. Thanks for the quick reply, Nick. That did seem a likely explanation but I thought the wiki said it could (or perhaps might) be done. If no other ideas come up I'll try f10 to f12 as a first step - before f12 goes EOL. Pre-upgrade is not all that perfected in Fedora land. Give the F14 physical media a try. It's faster than doing 3 upgrades If you have installed a large number of packages you may want to use the netinst CD. John P -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade problem
On 10/11/10 12:57, Steve Berg wrote: I just attempted using preupgrade on a Fedora 11 system. It ran fine on the system, downloaded all the packages, set up grub.conf and all the other things it normally does. I rebooted into the upgrade kernel and then it tells me that it can't upgrade the system because it's too old. You can only jump one release not two. If preupgrade is smart enough to know that limitation once the upgrade starts, why isn't it smart enough to warn me about that before it downloads and sets everything up? Maybe it figured you would do that yourself in advance. -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade problem
On 10/11/10 12:57, Steve Berg wrote: If preupgrade is smart enough to know that limitation once the upgrade starts, why isn't it smart enough to warn me about that before it downloads and sets everything up? Maybe it figured you would do that yourself in advance. -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora There's no mention of that limitation anywhere I've seen so far. From the Fedora wiki: Preupgrade provides an upgrade directly to the latest version of Fedora. It is not necessary to upgrade to intermediate versions. For example, it is possible to go from Fedora 12 to Fedora 14 directly. The wiki and preupgrade itself should warn users that a (ReleaseVer +2) upgrade is possible but (ReleaseVer +3) is not. -- * Stephen Berg * * sb...@mississippi.com * * Sinners can repent, * * But stupid is forever. * -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade problem
On Wed, 10 Nov 2010 07:05:11 -0600 (CST) Steve Berg sb...@mississippi.com wrote: On 10/11/10 12:57, Steve Berg wrote: If preupgrade is smart enough to know that limitation once the upgrade starts, why isn't it smart enough to warn me about that before it downloads and sets everything up? There's no mention of that limitation anywhere I've seen so far. From the Fedora wiki: Preupgrade provides an upgrade directly to the latest version of Fedora. It is not necessary to upgrade to intermediate versions. For example, it is possible to go from Fedora 12 to Fedora 14 directly. The wiki and preupgrade itself should warn users that a (ReleaseVer +2) upgrade is possible but (ReleaseVer +3) is not. I think you're running into the problem that between F11 and F12, rpm was modified in ways that weren't backward compatible. So I suspect if you upgrade to F12 from F11 it will take care of the incompatibility and you will then be able to jump to F14 from F12. Maybe you have to use the older version of preupgrade so it knows about that change, the one that was released with F12? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: preupgrade from FC12 to FC14 issues?
On Sat, 2010-11-06 at 18:35 +1000, Michael D. Setzer II wrote: I've just used preupgrade to upgrade some systems in my clasroom lab that has XP and Fedora 12. I had earlier done a test with fedora 13, but it had some issues the upgrade. The upgrade from 12 to 14 seems to have handled the problem with the older Nvidia cards these machines have, but there are a few issues. I saw the same issue with system-config-display that has been mentioned, and also found that vim-common and vim-enhanced where still the fc12 version? It also left the 3 fc12 kernels and kmods nvidias for the 3. I removed those and then installed the fc14 versions of the vim rpms. The one issue that I'm have trouble with is Flash and firefox. Google chrome works fine, and I was able to it working with firefox after I did a number of things. I then tried to figure out exactly what I did, and it didn't work on another machine? Even the machine I got it working on, I then logged in with another user, and it didn't work for that user? Hello, It's always a good idea to first remove 3rd party packages before attempting to preupgrade. Have a look at this, it might help: http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup/ -- Thanks! Regards, Ankur https://fedoraproject.org/wiki/User:Ankursinha FranciscoD -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade doesn't work
On 9/11/10 12:52 PM, Marcel Rieux wrote: On Sat, Sep 11, 2010 at 4:09 AM, JBjb.1234a...@gmail.com wrote: Hi, it is a state of flux. I always managed to move to next Fedora with either preupgrade or 'yum upgrade' methods, but other people are not always so lucky and hit an air pocket. In my case hitting air pockets could mean catastrophe. I'm beginning to grasp much better why some people advise non-geeks against using Fedora. I don't recommend to ANYONE using BETA software for anything other than testing. That is what RedHat states Fedora is (in a LOT of words.) For those who do not need or desire hand holding through a constant technical support, there is CentOS, the Community based version of RHEL. If you wish to stay on the bleeding edge, there's Fedora. I'm trying to get CentOS with Wine working on a Thinkpad A22p. No happiness so far, even with the excellent and very knowledgeable folks here. I would suggest to Fedora boyz and girls to ease, smell some flowers - life is not about constantly running ahead, without a pause, reflection, and enjoyment. I hope they hear us. Common! If Microsoft comes up with a new version of their OS every 5 years, I can't imagine the Red Hat boys not coming up with theirs every 6 months. Let's see RHEL 5.4 to 5.5 time period looks something like six months. However, there are updates to CentOS and RH products on a regular basis. Different audience for those products. PreUpgrade is a process that is being looked at for the 'selling' versions of RedHat products. This has been demanded by those who need a fast way to upgrade hundreds of systems. James McKenzie -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade doesn't work
On Sat, Sep 11, 2010 at 4:09 AM, JB jb.1234a...@gmail.com wrote: Hi, it is a state of flux. I always managed to move to next Fedora with either preupgrade or 'yum upgrade' methods, but other people are not always so lucky and hit an air pocket. In my case hitting air pockets could mean catastrophe. I'm beginning to grasp much better why some people advise non-geeks against using Fedora. Right now there is a hectic time for Fedora devs due to F14 testing, so we have to be patient with fixes to prior versions. Yes, next December, F14 will be out, so I suppose it would be a nice time to upgrade to F13. To be honest I read pretty heated reports about instability of kernels etc on tests mailing list and people saying Fedora is moving too much stuff too fast to be able to digest it properly. Yeah... kernels. Does the instability of preupgrade have anything to do with kernels? I'm beginning to consider alternatives. I tried CentOS' LiveCD yesterday but it ended on a blank screen. Of course, I could get desktop Red Hat support for only $300/year. For professional support, it's really cheap. Do you believe they would have solutions while they're developing RHEL 6? Another possibility would be adopting Ubuntu LTS, 6 months after upgrade but I make so many goods friends all over the place giving my frank opinion that I wonder how long its security would withstand the attacks :) Based on my recent observation of my F13 problems and other people's reports I would agree. Maybe I didn't check closely enough before going for an upgrade... I just thought 3 months after the release, the bugs would be ironed out. Maybe the development of F14 began the day after the F13 release? Which would mean we will never get a stable upgrade process? I mean every dev knows that even in an agreed-upon fast-moving software dev environment it can reach a critical point that can make people (devs and testers) frustrated and demoralized. Demoralized? You've got to be kidding! You know the motto is Have fun!, don't you? I would suggest to Fedora boyz and girls to ease, smell some flowers - life is not about constantly running ahead, without a pause, reflection, and enjoyment. I hope they hear us. Common! If Microsoft comes up with a new version of their OS every 5 years, I can't imagine the Red Hat boys not coming up with theirs every 6 months. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade doesn't work
Marcel Rieux m.z.rieux at gmail.com writes: ... Hi, if you just care about upgrading to next Fedora, try this method: http://fedoraproject.org/wiki/YumUpgradeFaq JB -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade doesn't work
On Fri, Sep 10, 2010 at 11:40 AM, JB jb.1234a...@gmail.com wrote: Marcel Rieux m.z.rieux at gmail.com writes: ... Hi, if you just care about upgrading to next Fedora, try this method: http://fedoraproject.org/wiki/YumUpgradeFaq Thanks for the suggestion but, I always thought preupgrade was the recommended way for upgrading and, whereas many people had problems upgrading with yum from F11 to F12, I had none at all with preupgrade. Has the recommendation for upgrading changed? Is this the reason preupgrade hasn't been fixed 3 months after F13 release? Thanks! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: LVMs and Real Partitions (was Re: Preupgrade F11 --- F12 ?)
Patrick Bartek wrote: --- On Tue, 7/27/10, Bill Davidsen david...@tmr.com wrote: Patrick Bartek wrote: [snip] I never could see any advantage to LVMs (over real partitions) other than being able to resize them while they are mounted. They do make it easy to move stuff to new hardware, that can be important as a time saving if you have to do it often. Easier than using cp or dd or rsync, etc.? How much easier can it get? Having done moves, way easier. Even I think it's easier, and I use a more manual toolset such as you mentioned. But a single command to move an LV from one PV to another PV, without editing boot scripts and such really is as simple as it can get. I guess it all depends on what you're accustomed to. The process of creating a partition, creating the filesystem, moving the data, and changing at least fstab and maybe grub.conf has a lot more steps, and usually requires editing config files as well. I trust I'll never be doing that so often I get accustomed to it, it usually means either bad initial configuration or hardware problems. Note usually in that. I just don't like one more layer I have to trust, although I really haven't had trouble with it in some years on other people's systems. -- Bill Davidsen david...@tmr.com We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: LVMs and Real Partitions (was Re: Preupgrade F11 --- F12 ?)
On 07/27/2010 06:01 PM, Patrick Bartek wrote: --- On Tue, 7/27/10, Bill Davidsendavid...@tmr.com wrote: Patrick Bartek wrote: [snip] I never could see any advantage to LVMs (over real partitions) other than being able to resize them while they are mounted. They do make it easy to move stuff to new hardware, that can be important as a time saving if you have to do it often. Easier than using cp or dd or rsync, etc.? How much easier can it get? I guess it all depends on what you're accustomed to. If you set them up properly, the snapshot bit can be very useful, too. Saved my bacon a couple of times. -- - Rick Stevens, Systems Engineer, C2 Hosting ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - Physics is like sex ... it may give some practical results, but - -that's not why we do it. -- Richard Feynman -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
re: preupgrade failure problem with swap Solved
-- Message: 15 Date: Tue, 27 Jul 2010 09:10:30 + (UTC) From: JB jb.123...@yahoo.com Subject: fc13 preupgrade failure on swap To: users@lists.fedoraproject.org Message-ID: loom.20100727t105136-...@post.gmane.org Content-Type: text/plain; charset=us-ascii Don Vogt dnvot at yahoo.com writes: I have been using fedora since fedora 4 with great satisfaction. I tried to do an fc12 to fc13 preupgrade. All went fine until I was running anaconda ( I believe) with the install.img. I got a pop-up that said the swap device has not been created and that The /etc/fstab on your upgrade partition does not reference a valid swap device When I click OK the system reboots and the upgrade fails. I have checked my swaps in the fc12 system and they seem OK, Top shows the swap partitions are there I actually have three swap partition on two different drives. I checked the swaps in fstab on fc12 using findfs and they seem OK, UIIDs and /dev entries. I suspect that the upgrade partition it refers to is in the install.img. I have another partition with fc13, on which I used preupgrade to upgrade from fc12 It was a very smooth procedure. That kind of rules out hard drive problems. Unless something changed. Does anyone have a suggestion on how to fix fstab, or what the problem might be? Also, is there a way to undo the preupgrade attempt, so I can try again? Any other suggestions will be welcome. Hi, please give us more info (do not cut/edit the output). Layout of both disks: # fdisk -l /dev/sda # fdisk -l /dev/sdb For F12 (the one you try to preupgrade) log in and get an output: # cat /etc/fstab For F13 (the one you already preupgrade-ed) log in and get an output: # cat /etc/fstab By the way: when you run preupgrade the next time (2nd, 3rd, etc) you are asked whether you want to continue from the point of previous stop/failure point or from the very beginning. IMPORTANT: I would advise you to stop changing anything on your machine (disk layout, swaps, /etc/fstab, etc) so that the data I ask you for above is true from that point on and we can help you ! JB -- I found an easy solution and completed the preupgrade last night. First i tried adding a swap file, because the message said my fstab does not have a valid swap file. I thought it might be making a distinction between swap partitions and a swap file. That didn't make any difference. I then commented out my swap partitions in the fc12 fstab and tried preupgrade again and it worked. Sorry, I didn't get your message about not changing things until this morning. In case you still want here are the outputs you asked for sudo fdisk -l Disk /dev/sda: 13.6 GB, 13601193984 bytes 255 heads, 63 sectors/track, 1653 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000bbbf3 Device Boot Start End Blocks Id System /dev/sda1 * 1 261 20964516 FAT16 /dev/sda2 262165311181240f W95 Ext'd (LBA) /dev/sda5 262 522 20964516 FAT16 /dev/sda6 523 783 20964516 FAT16 /dev/sda7 7841000 17430216 FAT16 /dev/sda810011576 4626688+ 83 Linux /dev/sda916211653 265041 82 Linux swap / Solaris Disk /dev/sdb: 4303 MB, 4303272960 bytes 255 heads, 63 sectors/track, 523 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000c786b Device Boot Start End Blocks Id System /dev/sdb1 * 1 409 3285261 83 Linux /dev/sdb2 410 523 915705 82 Linux swap / Solaris Disk /dev/sdc: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000d0450 Device Boot Start End Blocks Id System /dev/sdc1 1 127 1020096 83 Linux /dev/sdc2 128267720482875b W95 FAT32 /dev/sdc32678650130716280 83 Linux /dev/sdc46502 19237 1023019205 Extended /dev/sdc56502 1032530716248+ 83 Linux /dev/sdc6 10326 10580 2048256 82 Linux swap / Solaris /dev/sdc7 * 10581 1898767529196 83 Linux /dev/sdc8 18988 19237 2008093+ 82 Linux swap / Solaris from the upgraded system. cat /etc/fstab # # /etc/fstab # Created by anaconda
Re: Preupgrade F11 --- F12 ?
Patrick Bartek wrote:
--- On Mon, 7/19/10, Bill Davidsen david...@tmr.com wrote:
Patrick Bartek wrote:
--- On Tue, 7/13/10, Peter Diercks di-lis...@jls-hh.de
wrote:
I am running a server under F11. It is a remote
machine
which I have no
physical access to. It has a network connection. I
wanted
to upgrade to
F12 using preupgrade again, but this time I am
afraid I'll
run into
problems due to the size of /boot (194M, 153M free
space).
Does anybody know if this issue has been fixed?
Not that I've heard. 500MB is still the safe
minimum (from what I've read) for /boot for preupgrading.
Maybe, this will help:
http://fedoraproject.org/wiki/PreUpgrade
FWIW: I've never had good luck with upgrading
Fedora. For that reason, I've always done clean
installs on separate partitions keeping the previous install
and setting up a dual boot in case things go wrong.
I normally hand configure storage, but on one old (FC6)
machine I had let the
installer do it, and a bunch of LVM stuff was used instead
of partitions. This
worked until I decided to replace the 64 bit FC6 with 64
bit FC13. The install
went fine, and the old LVM stuff was still there, but it
wouldn't boot any more.
I copied the appropriate stanzas from the x86_FC6, and the
kernel gets loaded,
then it says it can't find the LVM parts to finish
booting.
The pv (one partition) has x86_{boot,root}_fc6 and
x86_64_{boot,root}_fc13 LVs
on it. I can mount the fc6 LVs just fine, just can't boot.
The moral of this story is that the O.P. really means
separate partitions not
some spare LVs you have. Very sad, I really wanted to run
both, since I have
some software which was not upgraded past FC6. Today's
warning. ;-)
I don't use LVMs for the same reasons I don't upgrade. After using Linux
for 10 years, I've got partition sizes pretty much dialed-in, at least, for
me, and always custom partition. I never let the installer decide. It
always decides wrongly anyway.
I never could see any advantage to LVMs (over real partitions) other than
being able to resize them while they are mounted.
They do make it easy to move stuff to new hardware, that can be important as a
time saving if you have to do it often.
--
Bill Davidsen david...@tmr.com
We have more to fear from the bungling of the incompetent than from
the machinations of the wicked. - from Slashdot
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
LVMs and Real Partitions (was Re: Preupgrade F11 --- F12 ?)
--- On Tue, 7/27/10, Bill Davidsen david...@tmr.com wrote: Patrick Bartek wrote: [snip] I never could see any advantage to LVMs (over real partitions) other than being able to resize them while they are mounted. They do make it easy to move stuff to new hardware, that can be important as a time saving if you have to do it often. Easier than using cp or dd or rsync, etc.? How much easier can it get? I guess it all depends on what you're accustomed to. B -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F11 --- F12 ?
Patrick Bartek wrote:
--- On Tue, 7/13/10, Peter Diercks di-lis...@jls-hh.de wrote:
I am running a server under F11. It is a remote machine
which I have no
physical access to. It has a network connection. I wanted
to upgrade to
F12 using preupgrade again, but this time I am afraid I'll
run into
problems due to the size of /boot (194M, 153M free space).
Does anybody know if this issue has been fixed?
Not that I've heard. 500MB is still the safe minimum (from what I've read)
for /boot for preupgrading.
Maybe, this will help:
http://fedoraproject.org/wiki/PreUpgrade
FWIW: I've never had good luck with upgrading Fedora. For that reason, I've
always done clean installs on separate partitions keeping the previous
install and setting up a dual boot in case things go wrong.
I normally hand configure storage, but on one old (FC6) machine I had let the
installer do it, and a bunch of LVM stuff was used instead of partitions. This
worked until I decided to replace the 64 bit FC6 with 64 bit FC13. The install
went fine, and the old LVM stuff was still there, but it wouldn't boot any
more.
I copied the appropriate stanzas from the x86_FC6, and the kernel gets loaded,
then it says it can't find the LVM parts to finish booting.
The pv (one partition) has x86_{boot,root}_fc6 and x86_64_{boot,root}_fc13 LVs
on it. I can mount the fc6 LVs just fine, just can't boot.
The moral of this story is that the O.P. really means separate partitions not
some spare LVs you have. Very sad, I really wanted to run both, since I have
some software which was not upgraded past FC6. Today's warning. ;-)
--
Bill Davidsen david...@tmr.com
We have more to fear from the bungling of the incompetent than from
the machinations of the wicked. - from Slashdot
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F11 --- F12 ?
--- On Mon, 7/19/10, Bill Davidsen david...@tmr.com wrote:
Patrick Bartek wrote:
--- On Tue, 7/13/10, Peter Diercks di-lis...@jls-hh.de
wrote:
I am running a server under F11. It is a remote
machine
which I have no
physical access to. It has a network connection. I
wanted
to upgrade to
F12 using preupgrade again, but this time I am
afraid I'll
run into
problems due to the size of /boot (194M, 153M free
space).
Does anybody know if this issue has been fixed?
Not that I've heard. 500MB is still the safe
minimum (from what I've read) for /boot for preupgrading.
Maybe, this will help:
http://fedoraproject.org/wiki/PreUpgrade
FWIW: I've never had good luck with upgrading
Fedora. For that reason, I've always done clean
installs on separate partitions keeping the previous install
and setting up a dual boot in case things go wrong.
I normally hand configure storage, but on one old (FC6)
machine I had let the
installer do it, and a bunch of LVM stuff was used instead
of partitions. This
worked until I decided to replace the 64 bit FC6 with 64
bit FC13. The install
went fine, and the old LVM stuff was still there, but it
wouldn't boot any more.
I copied the appropriate stanzas from the x86_FC6, and the
kernel gets loaded,
then it says it can't find the LVM parts to finish
booting.
The pv (one partition) has x86_{boot,root}_fc6 and
x86_64_{boot,root}_fc13 LVs
on it. I can mount the fc6 LVs just fine, just can't boot.
The moral of this story is that the O.P. really means
separate partitions not
some spare LVs you have. Very sad, I really wanted to run
both, since I have
some software which was not upgraded past FC6. Today's
warning. ;-)
I don't use LVMs for the same reasons I don't upgrade. After using Linux for
10 years, I've got partition sizes pretty much dialed-in, at least, for me, and
always custom partition. I never let the installer decide. It always decides
wrongly anyway.
I never could see any advantage to LVMs (over real partitions) other than
being able to resize them while they are mounted.
B
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F11 --- F12 ?
On Tue, 13 Jul 2010 16:49:26 -0700 Dave Stevens g...@uniserve.com wrote: Quoting Peter Diercks di-lis...@jls-hh.de: Hello List, I am running a server under F11. It is a remote machine which I have no physical access to. It has a network connection. I wanted to upgrade to F12 using preupgrade again, but this time I am afraid I'll run into problems due to the size of /boot (194M, 153M free space). Does anybody know if this issue has been fixed? Greetings, Peter I just upgraded F11 top F12 using preupgrade and had a too-small /boot, it doesn't seem to have been a problem, as I recall the installer figured out that there wasn't enough space and used a workaround, no intervention on my part needed. Pretty nice. Dave Likewise. I upgraded from F11-F12 with a boot size of 190M. I got messages about boot being to small but I continued and it all worked out. Good luck. Steve -- Changing lives one card at a time http://www.send1cardnow.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F11 --- F12 ?
--- On Tue, 7/13/10, Peter Diercks di-lis...@jls-hh.de wrote: I am running a server under F11. It is a remote machine which I have no physical access to. It has a network connection. I wanted to upgrade to F12 using preupgrade again, but this time I am afraid I'll run into problems due to the size of /boot (194M, 153M free space). Does anybody know if this issue has been fixed? Not that I've heard. 500MB is still the safe minimum (from what I've read) for /boot for preupgrading. Maybe, this will help: http://fedoraproject.org/wiki/PreUpgrade FWIW: I've never had good luck with upgrading Fedora. For that reason, I've always done clean installs on separate partitions keeping the previous install and setting up a dual boot in case things go wrong. B -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Preupgrade F11 --- F12 ?
Quoting Peter Diercks di-lis...@jls-hh.de: Hello List, I am running a server under F11. It is a remote machine which I have no physical access to. It has a network connection. I wanted to upgrade to F12 using preupgrade again, but this time I am afraid I'll run into problems due to the size of /boot (194M, 153M free space). Does anybody know if this issue has been fixed? Greetings, Peter I just upgraded F11 top F12 using preupgrade and had a too-small /boot, it doesn't seem to have been a problem, as I recall the installer figured out that there wasn't enough space and used a workaround, no intervention on my part needed. Pretty nice. Dave -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- It is no measure of health to be well adjusted to a profoundly sick society. Krishnamurti -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
