Description of problem: The upgrade installer download and install the mageia-prepare-upgrade package, shows the warning about having to reboot. I click on ok, then nothing, even after rebooting, the computer just boots normally, the option for preparing on boot does not show up! Version-Release number of selected component (if applicable): How reproducible: Every time I try to upgrade Steps to Reproduce: 1.Let MAGEIA 2 show there is an update 2.Select to upgrade 3.Select ok on the last window where it indicates that a preparation is done, and to select "Upgrade" from the menu Reproducible: Steps to Reproduce:
Forgot small detail, it is working in a domU Xen environment. MAGEIA 2 is a fresh install. I am unable to start the network install or the DVD from Xen, so I wanted to update my working domU.
did you started with the gui ? if yes, have you waited some minutes ? (you can see/modify how long is that time with launching mgaapplet-config)
Component: Release (media or process) => RPM PackagesVersion: 3 => 2Source RPM: (none) => mgaonline
Yes, logged in with my regular user in KDE, and I did wait a long time (in fact while writing this, MAGEIA 2 was still running in a VNC window).
Just tried the mageia-prepare-upgrade with urpmi, and there is an error about boot loader not being present. Tried to install one with grub, but it does not see the hard drive. I guess this is because of the emulated environment of Xen... Can I enter manually the lines in menu.lst, to try it? If so, where can I find this information?
"rw rd.convertfs" cf http://svnweb.mageia.org/packages/updates/2/mageia-prepare-upgrade/current/SOURCES/mageia-prepare-upgrade-bootloader-config?revision=413076&view=markup but iirc there you can use systemd directly too
CC: sysadmin-bugs => mageia, thierry.vignaudSource RPM: mgaonline => mageia-prepare-upgrade
Do you even use an initrd or bootloader in this system? I'm not too much of an expert in this area so not 100% sure. Can you access the filesystem of your guest from the host? If so, then the easiest way is just to run the script: /usr/lib/dracut/modules.d/30convertfs/convertfs.sh and convert the filesystem. e.g. if your guest is at /path/to/guest, you should just be able to run: /path/to/guest/usr/lib/dracut/modules.d/30convertfs/convertfs.sh /path/to/guest To do the preparation. I'm not sure why it doesn't work normally, but I'm guessing the initrd generation stage fails for some reason. Just make sure you have the latest dracut installed in the guest before continuing (and thus get the latest version of that script). HTHs
There is an initrd, but no bootloader. I tried to install it, but grub refuses to see xvda. This install of MAGEIA 2 does not have a bootloader, because originally, I could not make the installation start directly within Xen. So, I installed it under VirtualBox, then moved the vhd file over to Xen and copied the fs into an LVM partition. Since pygrub does not need a bootloader, nothing complained :). If I want convertfs to start, I need to create a new initrd with dracut? It will then get this new 30convertfs in it, so that the parameter "rw rd.convertfs" will be recognized? I guess it will then again not be able to modify the menu.lst with bootloader utility... I will try instead to run from the host the script, the fs can easily be accessible... Thank you for the fast responses!
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD