I guess this is the right forum category for this. Am using the preupgrade method to go from F10 to F11.Downloading packages now. Just wondering if anybody knows if Anaconda will give me options to set up separate (ext3) partition for boot? (Since current grub won't work in the new ext4 file system scheme.)
View 2 RepliesIt appears that the default boot partition is too small for F12 preupgrade:[URL].. Did anyone try to see if enough space is freed by following these steps? : http://fedoraproject.org/wiki/PreUpg...ace_in_.2Fboot
Namely,
1. Leave only 1 kernel
2. tune2fs -r 0 /dev/xxx
3. remove /boot/efi and splash.xpm.gz
"preupgrade now requires at least 167MB" means more space could be needed, and I'm unclear if the above is sufficient.
You probably know by heart the old tale of the guy who is preupgrading for as long as he can remember and eventually finds out /boot is too small for F13. Since removing old kernels didn't free enough space, I am now considering resizing /boot to 500MB. After reading stuff around the internet I have a rough idea of how to proceed (for instance, that I will need to install GRUB on the relocated /boot, etc. etc.), but since I do not want to run unnecessary risks I would like to ask you to do a sanity check on my plans. My HD is currently laid out like this:
/dev/sda1 : 128GiB, ntfs, contains a (broken) Windows installation and some other stuff.
/dev/sda2 : 131GiB, ntfs, holds the FLAC rips of my CDs and other important space-wasting stuff.
/dev/sda3 : 196 MiB, ext3, /boot of course.
[code]....
I was impressed to be asked on Fedora 10 if I want to upgrade to Fedora 11 but the first time I tried I had this error:
Not enough space in /boot/upgrade to download install.img.
My boot partition is 99MB and AFAIK that is not unusual so I tried tidying up a bit, uninstalling all except 2 kernels, and now have about 80MB for whatever needs to be downloaded in /boot/upgrade. But I get the same error. I can fix this by using wired instead of wireless networking but I want to know for planning purposes (next time I create a boot partition) how much space is required?
$ ls -l /boot/upgrade
total 21594
-rw-r--r-- 1 root root 18985802 2009-06-03 00:02 initrd.img
-rw-r--r-- 1 root root 3035056 2009-06-03 00:02 vmlinuz
Should I delete these? It looks like they might be left over from last time but I assume preupgrade knows what is junk and what isn't.
Going from Fedora 12 to 13. Got to the point where I have to reboot to install, system reboots to 12. This is a triple boot system with Open Suse and Mint, and the grub2 bootloader from Mint is the bootloader for the whole shebang. In the "how to use preupgrade" instructions there's a line that says "dentify the drive and partition of your Fedora /boot folder." How? If that sounds odd, consider that in my set up "computer" shows 4 partitions (and with just three operating systems..?). I can mount them, but have a problem telling which sytem is Fedora, Suse or Mint. And getting the FEDORA bootloader to find the PREUPGRADE kernel ... Momma said there'd be days like this.
cat /etc/fstab just returned /dev/sda1 on /boot. I installed Fedora first, before Suse or Mint, so being on the first drive or partition sounds right, but the multiple drives throws me, and "just guessing" doesn't seem like the way to go.
I'm trying to run preupgrade to upgrade to fedora 14 from fedora 12 and get a message saying there is not enough space in /boot/upgrade. I've found some instructions on how to make more room in the boot directory but I get an error near the last step as I have noted below:
Method 1: Free up space
First, try to remove any kernel packages not currently in use on your system. The kernel-prune.py script can be used to identify kernels that may be safely removed. If you choose to remove additional kernels, be prepared with installation media should you be unable to return to your previously installed system.
The installer will need approximately 26M of free space in /boot. Use the following command to determine the amount of free space in the /boot partition:
df -h /boot
To identify kernels that may be safely removed, run the following from a command line:
curl -O '[URL]'
chmod a+x kernel-prune.py
./kernel-prune.py
Now, to actually remove the kernel versions listed by the above command, run the following as root:
# PKGS=`./kernel-prune.py`
# echo $PKGS
# yum remove $PKGS
Next, adjust the number of reserved filesystem blocks using the command tune2fs. You'll first need to identify the block device for your /boot file system. In the example below, /dev/sda1 is the block device for the /boot filesystem.
# mount | grep "/boot"
/dev/sda1 on /boot type ext4 (rw)
I get this far and get the following Error:
[root@localhost ~]# mount | grep "/boot"
/dev/sda1 on /boot type ext3 (rw)
[root@localhost ~]# /dev/sda1 on /boot tupe ext3 (rw)
-bash: syntax error near unexpected token `('
[root@localhost ~]# mount | grep "/boot" /dev/sda1 on /boot/type ext3 (rw)
-bash: syntax error near unexpected token `('
[root@localhost ~]#
Now, adjust the number of reserved blocks for the /boot filesystem using the command tune2fs. Normally, a small amount of space on ext filesystem formatted partitions is 'reserved' and can only be used by the system administrator; this is to prevent an entirely full partition from rendering a system unbootable, and allow the administrator some space in which to work in order to clean up 'full' partitions. However, neither of this cases really applies to the /boot filesystem, so removing this reserved space is safe.
# tune2fs -r 0 /dev/sda1
I ran preupgrade - it took hours seemed ok it told me that the boot partition was not large enough but that it would install whatever at boot time provided my internet connection was "hard wired" - not exactly clear what that means but i have a ethernet connection to my dsl modem - which sounded hard wired to me - so i told it to go ahead at the end it told me to boot i did, but system hangs with cursor at top left corner booted again and interrupted the bootloader see i have the choice to boot the new fedora13 or the last fedora 12 fedora 13 does not boot fedora 12 does boot
View 2 Replies View Relatedi did a preupgrade from fedora 10, i have a new line in grub with the "preupgrade to fedora 11" ... when i choose this.. anaconda run with the normal blue screen running anaconda... but a blacks screen apper with the mouse... the installation not follow and only the black screen with the mouse i can see...some line add to the kernel line of preupgrade fedora 11 to run with another graphical configuration
View 1 Replies View Relatedi have just upgraded from f14 to f15 using preupgrade. i am now still waiting for the first boot to finish. the screen is stuck for more than an hour and the last line written was:
Started LSB: Start up the OpenSSH server daemon. and there is a blinking cursor.
I am trying to install Ubuntu 10.04 LTS on a Windows XP Media Centre Edition system.On the Step 4 of the installation which usually gives you the option to partition the disk but it only gives me the option to Erase the entire disk or specify partition manually, although this also doesn't allow anything other than totally erasing the disk. I'd ideally like to keep my Windows and I have installed Ubuntu before (but 9.10) on a different system.
View 9 Replies View RelatedI've just installed Fedora 14 over an old Ubuntu (heron, I think). The old install used a single partition for both / and /home; and I wanted to try to avoid reinstalling /home if possible (but yes, I did back it up). I chose the anaconda option to shrink the old Ubuntu /, and created a new LVM for the Fedora /. This seemed to work perfectly. I mounted the old / on '/host' (an old naming habit), and then mounted individual home dirs into /home using autofs. All seemed fine. However, on my first reboot after the autofs mounts fsck failed. The current situation is as follows:
# fsck /dev/sda6
fsck from util-linux-ng 2.18
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 15360000 blocks
The physical size of the device is 15359895 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes
# dumpe2fs /dev/sda6 | grep 'Block count'
dumpe2fs 1.41.12 (17-May-2010)
Block count: 15360000
# dumpe2fs -o superblock=32768 /dev/sda6 | grep 'Block count'
dumpe2fs 1.41.12 (17-May-2010)
Block count: 15360000
Same thing for all the other backup superblocks I've tried.
# echo '15360000 4 * p' | dc
61440000
# fdisk -s /dev/sda6
61439583
Resize2fs tells me to run fsck, and complains of a short read if I try to force. Fsck seems to run fine if I say 'no' to the abort prompt, but doesn't change the problem. Filesystem is ext3. Started with debugfs. First used icheck and ncheck to work out which file(s) had been written to the non-existent blocks past the partition size. Fortunately, there was only one. Deleted that file (can restore it from backup later). Quit debugfs. Now resize2fs -p -f worked perfectly. fsck after resizing was clean. Reboot seems happy. As for the origin of the problem, I would guess there's a rounding bug in the code anaconda uses to shrink partitions.
I'm not exactly sure that it goes in 'General' but hopefully it'll be alright here Anyways I'm trying to use 'preupgrade' to update my system but it's telling me I don't have enough space on /boot. I've already followed the instructions on the Fedora Wiki for removing unused Kernels and the like to try to free up more space. Here is what I have when I check the space on /boot :
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 198337 71584 126753 37% /boot
Is 126MB not enough? :s
What can I do? Should I be looking to expand the /boot partition's actual size? EDIT: I don't know if it affects anything, but I am running Fedora on an HP Mini 1000 with a 16GB SSD and have about 6.9GBs free overall.
I am trying to upgrade my F12 system ti F15 using the PreUgrade route. The initial package download goes Ok but on re-boot I can only access my old F12 system. df reports 44M avail in /boot which is on sdd1. Since I do have a multiboot system I checked that there was an "update" folder under "boot" and that it had the update versions of vmlinuz and initrd which it had. I edited "menu 1st" as described in the Pre-Upgrade notes setting the root entry to (hd0,0) as used for my working system and then did a re-boot. I selected the new upgrade entry in the GRUB menu but the system complained that it couldn't find a file. I have tried using root (hd3,0) but this does not work either. What am I doing wrong?
View 6 Replies View Relatedhow to use dual boot option?? i wanna use xp and federo.
View 1 Replies View RelatedI'm planing to upgrade from FC11 to FC14 using a preupgrade. I've read about some ways to overcome the problem of my /boot partition being only 200MB in size while the newer versions require 500MB. The option of "filling the free space on the boot partition to be less than 100MB to cause preupgrade to download the loader" appeals to me. But what I don't understand is: is the 500MB requirement of the new versions is transient during the install or a permanent requirement? If I do this trick of first filling up the free space on /boot then freeing it up before the reboot, what will be the permanent disk space requirement of FC14?
Are there any safe (and prefarably simple) ways to increase the size of the /boot partition after decreasing the size of other partition? Here is the output of "df" relevant to the /dev/sda disk:
Code:
upgraded from Fedora 10 to 11, had both KDE and Gnome desktops installed under 10 but now upgraded to 11 I get a boot error when truing to boot to KDE and most KDE apps that used to run under Gnome no longer do so
View 1 Replies View RelatedI have a brand new thinkpad X301 with 4GB of RAM and thinking of getting fedora 11 on it. The plan is to have it triple boot with vista/seven and hopefully OSx86. I am aware of the 4 primary partitions limit on an MBR disk. I was thinking of having a swap file instead of swap partition and not creating a boot partition as well. If I install the boot loader(GRUB?) on the root partition will I be able to boot it without any problems by using vista's boot loader?
Or Maybe I should install GRUB on the MBR and add all the other operating systems on it? Does anyone have any objections for not creating a swap partition or a boot partition? When comes to desktop environment I've been using KDE in the past, is there any major advantage of using Gnome over it? KDE seems to look really nice on fedora where Gnome is maybe more stable?
I have a /boot partition, and the online update process has downloaded the upgrade to /boot/upgrade. The problem is that grub is actually booting from a directory /boot which is in the root partition, but is invisible once the machine has booted, because the /boot partition is mounted over it. The result of all this is that the upgrade option does not appear in the boot menu, because that option has been inserted in the menu.lst (or grub.conf) in the /boot partition. is it ok for me to run:grub-install /dev/sda4(that's the device that contains the /boot partition where the upgrade menu option and data). Also, do I need the --root-directory option, given that the boot directory is the root directory of that partition.
View 3 Replies View RelatedI'm not an early adopter; i prefer to wait and see, and let others suffer the new distro's teething troubles. Finally, I decided to try preupgrade. I was a little astonished to find that it doesn't install itself to any menu, but that's OK. I ran it as root, and went on with what I was doing while it got ready. Eventually it prompted me to reboot and I did.
I'd like to say that everything went fine, and in about an hour, I had a working system with no glitches. Alas, that would be a lie. Not only did it change all my customized system sounds (with no apparent way of getting back what I want; the new sounds aren't selectable.) it replaced my carefully-tweaked fstab with one of its own. This mean that several partitions that I don't want mounted were. Not only that, in some cases right-click and unmount got a message that the partition wasn't mounted, even though I could browse it. I had to open a terminal and manually unmount them, followed by copying back my fstab to keep this from happening again.
While doing this, I learned that the arrow keys on my keyboard don't work right, with the up arrow mapped to screen shot, and the Enter key by the number pad disabled. I'm still working around that one.
Worst was that Firefox wouldn't open. Trying it from a terminal, I learned that it couldn't start XCOM. Weird.
I tried a system update, but the livna issue popped up. By good luck, I knew enough to locate the appropriate file and disable it. Yumex has been spending over four hours, downloading and installing more updates than preupgrade did, by almost 100%.
failure: repodata/3a2a6da78e69f9b2608b1c399561b99073baa86b5454618459 ceecb79d58da09-filelists.sqlite.bz2 from preupgrade-updates: [Errno 256] No more mirrors to try.
I receive this error when I run try to run preupgrade to go from F12 to F13.
It's definitely not an issue with my internet connection, I'm running this from a college campus with a 150mbps connection.
I've tried running it 3 times now, and get this every time. It also gives me the error about not enough space on the boot partition, so I press continue there to move on.
it's possible to use preupgrade to go directly from FC8 to FC11.
Also, I'm wondering if this will allow me to avoid formatting my hard drive or not. I'll have backups ready just in case, but was hoping maybe I could get away with not having to do the old two-step shuffle with all my data.
I went to upgrade my daughters machine that was running F9 using preupgrade-cli after having issues with mirrors timing out it finally completed the first part with the notification install will start once you reboot. so I rebooted the machine and when it rebooted the grub menu came up with the F9 install selected but with an option for the F11 Upgrade I choose the upgrade and it starts and I see the installation screen with the stop watch and all of a sudden the comp restarts now at the grub menu again and there is no option for F11 upgrade so I boot into F9 try to run it again and it throws a bunch of errors about the rpm database... Encountering this before i run
rm -f /var/lib/rpm/__db*
rpm -vv --rebuilddb
yum clean all
but yum just blows errors now and if I run rpm -qa it returns nothing. Is there any recovering from this? or should I back up the home dirs and do a fresh install? this is the output of the rebuild
Code:
D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.2367
D: creating directory /var/lib/rpmrebuilddb.2367
D: opening old database with dbapi 3
[code].....
I tried a pre-upgrade last night and after downloading 7GB of stuff over night, (don't ask me why it was that much) I rebooted.
Everything looked okay until I got an error message that said that /mnt/sysimage/... (I can't remember exactly what the error message was, sorry) what did not have enough space and needed 19MB more to install the upgrades.
Now, this system quad boots between Fedora, XP, Vista and 7 with grub being the intial boot loader giving me the option of Fedora or the Windows bootloader.
What I don't understand is why the installer (anaconda?) is having a fit about space when I have 8GB RAM and the system partitions are >10GB in size.
I upgraded to fedora 12 from fedora 11 with the preupgrade tool and all went very well at first try. But now I can't seem to get any sound from anything! I'm using KDE (for the past few years ) and my system in running on an ASUS Z91F.
View 2 Replies View RelatedI did have F11 on my laptop all running smoothly and everything which is good. But now I've updated from F11 using the preupgrade tool which for what I could see everything downloaded and installed ok, that was until the reboot after the install had completed after seemingly loading F12 it left me with a black screen with a blinking cursor so after a few more reboots with the same out come I decided to see what the loading was stopping at and this is what it came up with
Code:
Welcome to Fedora
Press 'I' to enter interactive startup.
Starting udev: [ OK ]
Setting Hostname Fireline.Yuki: [ OK ]
mdadm: No arrays found in config or automatically
[code]....
And it stops loading after "Starting atd: [ OK ]" I am going to try a CD install either tomorrow or the day after then I'll go back to F11 depending if it works or not.
I upgraded to Fedora 10 using preupgrade. It installed fine and everything loaded fine. Unfortunately the mouse would not work so I restarted my laptop. Now Fedora won't load at all the PC just turns on then keeps rebooting itself. I really want to avoid using the recovery disk. How to rectify?
View 1 Replies View RelatedI tried upgrade with dvd media and preupgrade from F12 but in both cases there is anaconda exception. I have dual boot windows xp (/dev/sda1) and F12 (/dev/sda2).
sudo fdisk -l /dev/sda:
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa070b627
[Code]...
I know this has been covered a lot but it seems as though there should be a definitive answer and I have yet to find one.How much free space in /boot is required to make preupgrade work? I have 173M, which according to the figures I've seen should be enough, but the preupdate client still complains. Any workarounds? I have already tunefs'ed and deleted old kernels.
View 5 Replies View RelatedI have downloaded all packages and prepared to update my laptop (Lenovo 3000 N200, F10 x86_64) from F10 to F13 via preupgrade. Everything works fine, until I reboot and go into the upgrade process.
The problem is at the screen which configs NetworkManager. It shows only two interfaces, eth0 and wlan0, but I use a 3G dongle to connect to the internet. I tried feeding random values for the fields, but it does not allow to go beyond without configuring NetworkManager first.
can I work around the upgrade process without configuring NetworkManager? ie. can I do that manually after installing the upgrade?
today i've tried to PreUpgrade from f12 to f14. In the past i preferred always begin with a fresh install, removing abruptly the preivious one with a CLEAN FRESH installation. (I think it's the best procedure). However i wanted exeperiment with this soution giving it one, two, three N+1 chances. So this is my first up-grade (or "double" upgrade).
My system is
CPU: INTEL P4
RAM 1024 MB
Video: NVidia
O.S. F12
Desktop: GNOME only (removed unused KDE app)
[Code]...