I've tried all the tricks on this list a/o the troubleshooting site, over and over. I finally gave up : downloaded and burned a DVD -- and *still* hit the catch-22 error, with too little space in mnt/sysimage/ boot.
Now what?
Can I simply delete all of /boot, or everything in it? All of grub.conf? Or what? It's going to be a royal pain if I have to burn all my data to media, and then sneakermail that back onto each machine, instead of just upgrading f11 ....
On 11/24/2009 11:32 PM, Beartooth wrote:
I've tried all the tricks on this list a/o the troubleshooting site, over and over. I finally gave up : downloaded and burned a DVD -- and *still* hit the catch-22 error, with too little space in mnt/sysimage/ boot.
Now what?
Can I simply delete all of /boot, or everything in it? All of grub.conf? Or what? It's going to be a royal pain if I have to burn all my data to media, and then sneakermail that back onto each machine, instead of just upgrading f11 ....
A backup of your data is always a good idea. Also refer to
http://fedoraproject.org/wiki/PreUpgrade#Troubleshooting
Rahul
On Tue, 24 Nov 2009 23:31:33 +0530, Rahul Sundaram wrote:
On 11/24/2009 11:32 PM, Beartooth wrote:
I've tried all the tricks on this list a/o the troubleshooting site, over and over. I finally gave up : downloaded and burned a DVD -- and *still* hit the catch-22 error, with too little space in mnt/sysimage/ boot.
Now what?
Can I simply delete all of /boot, or everything in it? All of grub.conf? Or what? It's going to be a royal pain if I have to burn all my data to media, and then sneakermail that back onto each machine, instead of just upgrading f11 ....
A backup of your data is always a good idea. Also refer to
That url is the "troubleshooting site" I meant. I've tried both ways. The first fails because I can't get enough cruft out of /boot; the second, because my installer never pauses to give me the message it's supposed to. I've tried deleting the filler both before and after.
I have $ rpm -q preupgrade preupgrade-1.1.3-1.fc11.noarch and $ rpm -q anaconda anaconda-11.5.0.59-1.fc11.i586
(I did the bit with temporarily enabling the extra repo and updating preupgrade.)
On 11/25/2009 09:11 PM, Beartooth wrote:
That url is the "troubleshooting site" I meant. I've tried both ways. The first fails because I can't get enough cruft out of /boot;
Ok. So whats the size of your /boot and how much space is left? How many kernels do you have installed? You can use something like the Live CD to resize your boot partition as well, I guess.
Rahul
On Wed, 25 Nov 2009 22:08:58 +0530, Rahul Sundaram wrote:
On 11/25/2009 09:11 PM, Beartooth wrote:
That url is the "troubleshooting site" I meant. I've tried both ways. The first fails because I can't get enough cruft out of /boot;
Ok. So whats the size of your /boot and how much space is left? How many kernels do you have installed?
I'll have to post that one machine at a time; somehow (whether because of Pan 0.133, or my local access provider, or what, I don't know) it makes trouble to have multiple newsreaders running at once.
Meanwhile, there is a new development. I had burned the install DVD on the first disk that came handy, which happened to be double-sided. I thought to try a well-used DVD-RW instead, and put that into #4 machine. It seems to be working. Stay tuned.
You can use something like the Live CD to resize your boot partition as well, I guess.
I did try both gparted and qtparted on one machine, and just got snarled up; I haven't tried the live CD yet, but will -- unless the new DVD really does succeed.
On Wed, 25 Nov 2009 20:19:49 +0000, I Beartooth wrote: [....]
Meanwhile, there is a new development. I had burned the install DVD on the first disk that came handy, which happened to be double-sided. I thought to try a well-used DVD-RW instead, and put that into #4 machine. It seems to be working. Stay tuned.
PC #4, my oldest and slowest, is now running F12!
Gnat in ointment: I could swear I told it to upgrade existing (and got suspicious when it let me "customize now"), but it didn't. However, that machine and all it had were expendable.
What's more, that same DVD-RW, now in my Thinkpad T42, is installing F12 again. It also just offered me the customization choice -- and wouldn't let me go back, except by terminating the install; but again, its data was expendable.
Meanwhile, preupgrade still fails on PC #2 and #3 (and I have yet to try on #1 or the T30 Thinkpad), and on the EeePC running Omega. I'll try again, probably tomorrow (It's Thanksgiving here, and I'm the cook.), and report further.
On Thu, 26 Nov 2009 17:31:40 +0000, Beartooth wrote:
PC #4, my oldest and slowest, is now running F12!
Gnat in ointment: I could swear I told it to upgrade existing (and got suspicious when it let me "customize now"), but it didn't. However, that machine and all it had were expendable.
What's more, that same DVD-RW, now in my Thinkpad T42, is installing F12 again. It also just offered me the customization choice -- and wouldn't let me go back, except by terminating the install; but again, its data was expendable.
It did do a complete install -- but it evaporated all of my tweaks and data, including even my innumerable choices of apps to install or remove, on the T42 as well as on PC #4.
I tried it in PC #3, which is *not* nearly so expendable, and noticed this time that when it gets to partitioning, one choice is to "replace existing linux installation" -- which might mean putting either an upgrade or a fresh install into the space now used. What became of the choice we used to have??
Btw, I also find, every time I hit the partitioner, it refuses to let me increase /boot beyond 200 MB.
On Fri, 27 Nov 2009 20:12:38 +0000, I Beartooth wrote: [....]
I tried it in PC #3, which is *not* nearly so expendable, and noticed this time that when it gets to partitioning, one choice is to "replace existing linux installation" -- which might mean putting either an upgrade or a fresh install into the space now used. What became of the choice we used to have??
Btw, I also find, every time I hit the partitioner, it refuses to let me increase /boot beyond 200 MB.
I gave up for now on PC #3, and tried the same DVD-RW in PC #2. It did hit a choice of upgrading, which I took -- whereupon it hung. I let it go a long long time, thinking it might yet manage, then finally hit Ctrl-Alt-Bs. There were two messages there saying that 30-second timeouts had been exceeded, and one admitting failure.
I hit Ctrl-Alt-Delete, and it restarted Anaconda -- but went yet again only to the screen without the upgrade option. <sigh>
Beartooth wrote:
I've tried all the tricks on this list a/o the troubleshooting site, over and over. I finally gave up : downloaded and burned a DVD -- and *still* hit the catch-22 error, with too little space in mnt/sysimage/ boot.
Now what?
Can I simply delete all of /boot, or everything in it? All of grub.conf? Or what? It's going to be a royal pain if I have to burn all my data to media, and then sneakermail that back onto each machine, instead of just upgrading f11 ....
How about this: - mount a USB drive - copy /boot to the drive - remount the USB as /boot in fstab - upgrade - do the obvious reversal of the process
On Tue, 24 Nov 2009 14:43:37 -0500, Bill Davidsen wrote: [....]
How about this:
- mount a USB drive
- copy /boot to the drive
- remount the USB as /boot in fstab
- upgrade
- do the obvious reversal of the process
I *like* this idea -- and apologize for not discovering it till now. But the latter half is Geek to me: what I know about fstab is how to spell it. And the man page is totally opaque, depending as usual on umpteen other things I can't even spell. I gather it's a plain text file, and I think the one I need is /etc/fstab; I presume I edit it somehow.
Konqueror (which I run, under Gnome, almost entirely because it makes man pages so much more legible than my command line on a terminal) finds no man page for "remount". I presume I just do umount and -- what? The man pages jump from mergecap to multi (and from remap_file_pages to remque). How do I (re)mount something *in* a file??
As for your last line: obvious to whom? Has anyone recounted the classic definition of "obvious" here lately? The one about the Nobel laureate teaching postdocs?
On Sun, 2010-12-19 at 15:17 +0000, Beartooth wrote:
I *like* this idea -- and apologize for not discovering it till now. But the latter half is Geek to me: what I know about fstab is how to spell it. And the man page is totally opaque, depending as usual on umpteen other things I can't even spell. I gather it's a plain text file, and I think the one I need is /etc/fstab; I presume I edit it somehow.
Yes, /etc/fstab is *the* fstab (File System Table) that we refer to when configuring mounting things onto the file system.
Konqueror (which I run, under Gnome, almost entirely because it makes man pages so much more legible than my command line on a terminal) finds no man page for "remount". I presume I just do umount and -- what? The man pages jump from mergecap to multi (and from remap_file_pages to remque). How do I (re)mount something *in* a file??
Remounting could be using a remount option with the mount command, or unmount something with the umount command (notice it's not unmount command) then mount it with the mount command. It could also be issuing the "mount -a" command line, which will go through all the entries in the fstab file, and mount them.
It's the mount command you want look into.
As for your last line: obvious to whom?
Obvious to meeeeeeee.... (thought process of the writer) ;-)
At the end of the process, unmount the new special boot partition, change the fstab file back to using the original boot partition, mount the (original) boot partition.