I am about to upgrade my 12.2 (64-bit) install which I did, at the time, as a fresh install and UEFI. When I did that I had to zero out the disk in order to get UEFI to work. I’m going to try to upgrade to 12.3 over the top of 12.2 and hope/expect that UEFI will continue to boot.
Does anyone have tips/suggests for such an upgrade scenario?
Thanks
On 03/30/2013 06:16 PM, jwomack wrote:
> I’m going to try to upgrade to 12.3 over the top of 12.2
i do not know precisely what that means…is it:
- http://tinyurl.com/35p966c
- http://tinyurl.com/93uemsr
- http://tinyurl.com/7l4m2td
- something else, like maybe:
a. backup data; format Linux partitions except /home; install 12.3
b. backup data; format all Linux partitions; install 12.3
c. what?
i ask because how you intend to “upgrade to 12.3 over the top of
12.2” could change the tips which might be given…
–
dd
http://tinyurl.com/DD-Caveat
Thanks for your reply. I used the offline method and chose Upgrade. Unfortunately, my /boot partition (which I had created separate from all other partitions) ran out of space and the installation failed. As I result I am in the very position I was concerned about when I created this post.
Since my 12.2 installation leveraged UEFI it was necessary, at that time, for me to zero out the disk in order for UEFI to install correctly. Now that I have a failed installation of 12.3 I’m not sure how to proceed. Can I somehow deal with the /boot partition easily and re-run the upgrade? I don’t mind doing a clean install (while retaining my /home partitions of course) but I’m not sure what to expect with UEFI will.
Any help would be appreciated.
How big is /boot?
In any case since you specified a special confuration did you also tell the partitioner to FORMAT /boot otherwise it will try keep any old files and simply add the new ones.
Try upgrade again and format /boot this time.
Thanks for the suggestion. I’m trying it now but not seeing an option to modify the partitions when I pick the “Upgrade an existing system” option.
EDIT: In addition, since /boot contains efi what should I expect by formatting /boot? Will the upgrade recreate the EFI partition?
On 03/30/2013 08:16 PM, jwomack wrote:
> Any help would be appreciated.
i am confused…you ask a question and then exactly two hours later
report that already (without waiting for an answer) you forged ahead
and have a problem??
personally, i’d be afraid to try to help more…because, i might
find again that whatever i wrote was a waste of my time.
–
dd
Okay, I think I worked around the /boot partition space issue. I booted up on the installation media, switched over to TTY2, mounted boot to a temp directory, cleaned up the old 3.4 kernel files and then reran the upgrade. Only apparently artifact is an error I get at boot and a text mode GRUB screen (see links below).
https://www.dropbox.com/s/n4f8djibh7xey85/IMG_20130330_125736.jpg
https://www.dropbox.com/s/88ui5mdp1ilbvyq/IMG_20130330_125747.jpg
If anyone knows how to fix that I think I’ll be able to call this troubled upgrade a success.
Thanks
I applied what information was provided by the responses I did receive and was able to move past that particular problem. My last post reflects a different problem. If you have a suggest for the latest problem I would very much appreciate whatever advise you have to offer.
What video card do you have?
Try booting into safe mode or use nomodeset as a boot parameter.
You make good point, I was playing with a clean installation 12.3 on a different hard drive so that I could test bumblebee. I have a Lenovo W520 with both the Intel and Nvidia chips. I had enabled Optimus mode and left it that way when i did the upgrade. I don’t intend to use Optimus mode since it won’t work with the external displays attached to my port replicator so I’ve not set it back to Discrete, which is what it was when I was running 12.2 however I am still seeing the Invalid Filter error which is presented before I even get to the grub2 screen. I am able to boot fine it just appears like grub is in text mode an not using Plymouth. Anyone now how to fix this?
Thanks