Hi: This box is running f16. It has been upgraded in stages from f10.
Two disks, and when last tried could boot Win Vista, Vista recovery,
f12 and f16. It usually runs MythTV under f16, 24/7.
Preupgrade appeared to run ok, with the expectation of downloading the
installer on reboot, as
g 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=Tr
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 re
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
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
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
On Thu, Dec 27, 2012 at 20:01:09 +0100,
Frank Zimmermann 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.
T
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 CURRE
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 "F
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
On an FC16 box i just ran preupgrade-cli.
It ends on a down note:
Spawning worker 0 with 1682 pkgs
Workers Finished
Gathering worker results
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Preparing system to boot into
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'.
>
No, preupgrade only up to Fedora 17. For Fedora 18 go with yum and when
functional 'fedup'.
--- Em seg, 19/11/12, Christopher Svanefalk
escreveu:
De: Christopher Svanefalk
Assunto: Re: Preupgrade vs other upgrade methods, caveats?
Para: "Community support for Fedora users&
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 wrote:
> On 11/18/2012 05:45 AM,
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
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
differ
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
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 Svanefalk
mob: +46762628251
skype: csvanefalk
--
users mailing list
users@lists.fedoraproject.org
To
Gordon Messmer wrote:
On 11/03/2012 10:07 PM, Bill Davidsen wrote:
The bottom line appears to be 13->15->17, at most two versions at a
time.
I don't know of any reason you can't go from 13->16. Going directly to 17 is
only problematic because of the /usr merge, since anaconda needs to handle
On 11/03/2012 10:07 PM, Bill Davidsen wrote:
The bottom line appears to be 13->15->17, at most two versions at a
time.
I don't know of any reason you can't go from 13->16. Going directly to
17 is only problematic because of the /usr merge, since anaconda needs
to handle that.
And it's goi
Bill Davidsen wrote:
Preupgrade used to be quite limited in capability, and restricted to a single
version upgrade at a time. I have some systems I would rather not upgrade by
hand if possible, but they need to go from fc13 to fc17, and I'm sure doing it
insteps would take more effort on my
On 10/30/2012 03:48 PM, Bill Davidsen wrote:
Preupgrade used to be quite limited in capability, and restricted to a
single version upgrade at a time. I have some systems I would rather not
upgrade by hand if possible, but they need to go from fc13 to fc17, and
I'm sure doing it insteps
Quoting Bill Davidsen :
Preupgrade used to be quite limited in capability, and restricted to
a single version upgrade at a time. I have some systems I would
rather not upgrade by hand if possible, but they need to go from
fc13 to fc17, and I'm sure doing it insteps would take more e
Preupgrade used to be quite limited in capability, and restricted to a single
version upgrade at a time. I have some systems I would rather not upgrade by
hand if possible, but they need to go from fc13 to fc17, and I'm sure doing it
insteps would take more effort on my part than a single
On 09/18/2012 09:55 AM, bha...@bhanks.net wrote:
Message: 7
Date: Mon, 17 Sep 2012 16:35:58 +0200
From: Reindl Harald
To: Community support for Fedora users
Cc: bha...@bhanks.net
Subject: Re: F16 => F17 PreUpgrade Invalid Device ID Dumps to dracut
Shell
Message-ID: <50
unsupported at
the top of this page. However Fedora 17 is very special. You should
seriously consider stopping now and just using anaconda via. DVD or
preupgrade, unlike all previous releases it's what the yum/rpm developers
recommend. Continue at your own risk.
Despite the reports every relea
Message: 7
Date: Mon, 17 Sep 2012 16:35:58 +0200
From: Reindl Harald
To: Community support for Fedora users
Cc: bha...@bhanks.net
Subject: Re: F16 => F17 PreUpgrade Invalid Device ID Dumps to dracut
Shell
Message-ID: <5057354e@thelounge.net>
Content-Type: text/plain
Am 17.09.2012 16:30, schrieb bha...@bhanks.net:
> I delayed the upgrade of my main Fedora machine after reading all of the
> issues that were happening with the
> preupgrade process. I've done several fresh installs without issue, so I
> suspected that my delay would have
>I had grub issues after an upgrade (DVD-based, though), and mine
was down
(among *many* other things) to a stuffed /boot/grub2/device.map,
which I
then had to re-create from grub2-mkdevicemap (all done from a
recovery-boot
off an install DVD, chroot'ed into /mnt/sysimage).
I learnt (&
Around about 17/09/12 15:30, bha...@bhanks.net typed ...
I've searched all over and not found any reference to this exact
problem. Any ideas?
I had grub issues after an upgrade (DVD-based, though), and mine was down
(among *many* other things) to a stuffed /boot/grub2/device.map, which I
t
I delayed the upgrade of my main Fedora machine after reading all of
the issues that were happening with the preupgrade process. I've done
several fresh installs without issue, so I suspected that my delay would
have provided enough time for the preupgrade issues to be worked out. I
On 08/22/2012 01:43 PM, Tim wrote:
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 whe
In preparation for trying preupgrade from my existing f14,
I duplicated the f14 on another partition.
This copy of f14 boots, boot messages all OK.
But I can't login to it,
either in the graphical login window
or going to text screen.
Both just endlessly recycle me back to the login.
I
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 rebo
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
On Tue, 2012-08-07 at 20:04 +0930, Tim wrote:
> On Mon, 2012-08-06 at 09:24 -0500, Aaron Konstam wrote:
> > If you include the update repo when you are finished with the update
> > you will have installed the latest versions of all the software.
>
> ... as I'd already said.
>
You are right . You
On Mon, 2012-08-06 at 09:24 -0500, Aaron Konstam wrote:
> If you include the update repo when you are finished with the update
> you will have installed the latest versions of all the software.
... as I'd already said.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private
evice: 8f24…blahblah
> Entering rescue mode …
> grub rescue
I had previously interpreted this fail message
as coming from the grub2 of the failed preupgrade f14->f16
But now I am not at all sure;
it might have been from the legacy grub of the f14.
Does anyone know if the message
On 04.08.2012, jackson byers wrote:
> I am now stuck in an unresponsive grub2: ]
> grub rescue >
[]
> One difficulty is that my f14 is installed to external usb,
> but my bios won't boot from usb, so the boot files have to
> be put somewhere on my two internal scsi disks,
> which works fo
On Mon, 2012-08-06 at 14:32 +0930, Tim wrote:
> On Mon, 2012-08-06 at 00:44 -0400, Eddie G. O'Connor Jr. wrote:
> > I'd go "old school" and get a DVD burned iso image and install it THAT
> > way, at least THIS way, you'd be assured of getting the LATEST version
> > of Fedora without any glitches to
On Mon, Aug 06, 2012 at 12:44:30AM -0400, Eddie G. O'Connor Jr. wrote:
>
> EGO II
Could you trim your posts to the relevant bits in the future? It makes
for easier reading.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
--
users mailing list
users@lists.fedoraproject.org
To u
On Mon, 2012-08-06 at 00:44 -0400, Eddie G. O'Connor Jr. wrote:
> I'd go "old school" and get a DVD burned iso image and install it THAT
> way, at least THIS way, you'd be assured of getting the LATEST version
> of Fedora without any glitches to your install.
To avoid being misleading, I'll point
error: no such device: 8f24…blahblah
Entering rescue mode …
grub rescue >
So I have no way to boot my other f14.
That 8f24… is the UUID of the f14 partition on USB
that I was trying to preupgrade to f16.
presumably, "no such device" because that partition
is sda2 on externa
escue mode …
grub rescue >
So I have no way to boot my other f14.
That 8f24… is the UUID of the f14 partition on USB
that I was trying to preupgrade to f16.
presumably, "no such device" because that partition
is sda2 on external USB, which grub2 can't see.
That original f14
I am now stuck in an unresponsive grub2: ]
grub rescue >
it responds to a few commands, such as 'ls'
but in particular it fails on
exit
which is supposed to quit, instead says
unknown command 'exit'.
I was attempting a preupgrade from one of my two f14 install
On Fri, Jun 8, 2012 at 12:48 PM, Steve Dowe wrote:
> I'm unsure whether to make this an issue in bugzilla, given my unorthodox
> route here, but it seems like there is an issue with the F17 initrd being
> created while running in F16's 3.3 kernel. Could anyone comment on this?
>
> Anyway, I hope
On 07/06/12 17:08, Steve Dowe wrote:
On 07/06/12 15:55, Michael Cronenworth wrote:
> Preupgrade takes care of the /usr move automatically. It occurs
> when you boot into the preupgrade anaconda.
Superb - thank you both for that info.
Looks like an interesting evening ahead!
An inter
racut. I'm assuming these steps are not required before
> running preupgrade in F16?
>
> Thanks,
> Steve
>
Well I successfully upgraded to Fedora 17 using the net install
method from a bootable USB flash
drive, so that definitely handles the directory rearrangements. The o
On 07/06/12 15:55, Michael Cronenworth wrote:
Preupgrade takes care of the /usr move automatically. It occurs when
you boot into the preupgrade anaconda.
Superb - thank you both for that info.
Looks like an interesting evening ahead!
Cheers,
Steve
--
Steve Dowe
Warp Universal Limited
http
Steve Dowe wrote:
> I can't seem to find the definitive (or any) answer on the web site.
> The 'Upgrading Fedora using yum' section goes through the necessary
> steps using dracut. I'm assuming these steps are not required before
> running preupgrade in F16?
P
On 06/07/2012 10:07 AM, Steve Dowe wrote:
I can't seem to find the definitive (or any) answer on the web site.
The 'Upgrading Fedora using yum' section goes through the necessary
steps using dracut. I'm assuming these steps are not required before
running preupgrade
Hi folks,
Pretty much as the subject says, I guess...
I can't seem to find the definitive (or any) answer on the web site.
The 'Upgrading Fedora using yum' section goes through the necessary
steps using dracut. I'm assuming these steps are not required before
runni
On Mon, 2012-06-04 at 21:54 +0300, jarmo wrote:
> Mon, 04 Jun 2012 08:19:42 -0430
> Patrick O'Callaghan kirjoitti:
>
> > I recently upgraded F16->F17 using preupgrade. I booted into F17 and
> > everything seemed to work until I tried rebooting, whereupon I got a
&
Mon, 04 Jun 2012 08:19:42 -0430
Patrick O'Callaghan kirjoitti:
> I recently upgraded F16->F17 using preupgrade. I booted into F17 and
> everything seemed to work until I tried rebooting, whereupon I got a
> Kernel panic with a lot of stuff about missing files (mdadm, sh,
> c
On Mon, Jun 4, 2012 at 2:49 PM, Patrick O'Callaghan
wrote:
> I recently upgraded F16->F17 using preupgrade. I booted into F17 and
> everything seemed to work until I tried rebooting, whereupon I got a
> Kernel panic with a lot of stuff about missing files (mdadm, sh,
> c
Patrick O'Callaghan wrote:
>On a related note: how does one capture the console output when a panic
>like this occurs? It isn't in any log files (maybe by this time there
>isn't a filesystem) and it's a chore to have to copy it all by hand,
>which is why I haven't bothered in this case.
I use a
Patrick O'Callaghan wrote:
> I recently upgraded F16->F17 using preupgrade. I booted into F17 and
> everything seemed to work until I tried rebooting, whereupon I got a
> Kernel panic with a lot of stuff about missing files (mdadm, sh,
> cat, ...) and a panic backtrace.
On 06/04/2012 08:49 AM, Patrick O'Callaghan wrote:
So it looks like the issue was that grub.cfg should have been changed
during the preupgrade, but wasn't. Has anyone else seen this?
Yep. Happened to me, too. I saw it mentioned somewhere in a bugzilla
issue about the kernel
I recently upgraded F16->F17 using preupgrade. I booted into F17 and
everything seemed to work until I tried rebooting, whereupon I got a
Kernel panic with a lot of stuff about missing files (mdadm, sh,
cat, ...) and a panic backtrace. This was completely reproducible.
I then noticed that
On Wed, May 30, 2012 at 5:44 PM, jarmo wrote:
> When closing comp kernel panic, again
> can't produce message here, but remember, that can't find shutdown.sh
> script was one of messages...
Ok, so I think I just went through this same path yesterday.
I noticed the upgrade did not correctly set t
Wed, 30 May 2012 18:12:13 +0200
suvayu ali kirjoitti:
> If copying text to the email is not possible, you could take a picture
> with a camera and put it up on some service like imagebin and link
> from your email. In short, more information helps, just complaining
> doesn't.
>
> GL
>
I sure b
it 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,
> >
> > Preup
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:
&
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
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
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 h
Hi all,
What grub2 secret sauce do I need to upgrade remote servers to F17 using
vnc?
This is the first step, clearly:
preupgrade-cli --vnc=apassword --ip=192.168.0.240
--gateway=192.168.0.128 --netmask=255.255.255.0 --dns=192.168.0.2
"Fedora 17 (Beefy Miracle)"
However, thi
On Wed, May 30, 2012 at 5:44 PM, jarmo wrote:
> If you do distro for people, make sure u understand, that
> persons like me, 60 old want to use it.
I realise it can be difficult to do things precisely with age, but
still I would like to say if you want help with your issue, you need
to provide co
First, preupgrade-cli does not work, stops in some .py stuff. Can't get
info, b'cause another comp. No problem, pure preupgrade went smoothly
trough, new 17 all ok, so far. When closing comp kernel panic, again
can't produce message here, but remember, that can't find shutdown.
On Wednesday, May 30, 2012, Alan Cox wrote:
> > So my question is: Is preupgrade supported on efi systems or should I
> just
> > use yum to upgrade to F17?
>
> You don't have that option either really because of the great
> rearrangement of /bin and /usr/bin etc.
> So my question is: Is preupgrade supported on efi systems or should I just
> use yum to upgrade to F17?
You don't have that option either really because of the great
rearrangement of /bin and /usr/bin etc.
Alan
--
users mailing list
users@lists.fedoraproject.org
To unsubscrib
Hi,
I have a ThinkPad X220 with F16 booting with efi, so my grub.conf is
located in /boot/efi/EFI/redhat/grub.conf.
But preupgrade makes changes to /boot/grub2/grub.cfg which (of course) is
not taken into account while booting.
I have not found any parameter to tell preupgrade that it's wo
On Tue, 06 Mar 2012 08:01:19 +1000
"Michael D. Setzer II" 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) Gr
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.
I was able to get the older grub to boot the new kernel, by
manually editing the grub.conf file, but have not been able to
On Sun, Mar 4, 2012 at 13:23, Martín Marqués wrote:
> Just ran yum upgrade --downloadonly, and saw that yum wants to install
> a bunch of i686 packages, even though I don't have any packages with
> that arch (all x86_64 or noarch).
>
> preupgrade was doing the same.
Are you
El día 4 de marzo de 2012 09:07, Martín Marqués
escribió:
> 2012/3/2 Alan Cox :
>> On Fri, 2 Mar 2012 17:01:12 -0300
>> Martín Marqués wrote:
>>
>>> That's all I want (what's in the subject).
>>>
>>> I've had some headaches with pre
2012/3/2 Alan Cox :
> On Fri, 2 Mar 2012 17:01:12 -0300
> Martín Marqués wrote:
>
>> That's all I want (what's in the subject).
>>
>> I've had some headaches with preupgrade, basically, I guess, because I
>> have /var on another partition.
>
&g
On Sat, 2012-03-03 at 01:36 +0100, suvayu ali wrote:
> On Fri, Mar 2, 2012 at 22:19, Jim wrote:
> > I have tried preupgrade a number of times and it never works right after
> > upgrade.
>
> And it worked every time I tried it! F13->F14, F13->F15, F14->F16 :)
Sam
On Fri, Mar 2, 2012 at 22:19, Jim wrote:
> I have tried preupgrade a number of times and it never works right after
> upgrade.
And it worked every time I tried it! F13->F14, F13->F15, F14->F16 :)
--
Suvayu
Open source is the future. It sets us free.
--
users mai
usually it's as simple as running updatedb, then locate .rpmnew and fixing up
any config file changes that didn't get applied automatically. then run
preupgrade, and once the system is up repeat the same procedure to find new
.rpmnew files.
when a package being updated discovers that
On 03/02/2012 03:59 PM, Alan Cox wrote:
On Fri, 2 Mar 2012 17:01:12 -0300
Martín Marqués wrote:
That's all I want (what's in the subject).
I've had some headaches with preupgrade, basically, I guess, because I
have /var on another partition.
Preupgrade randomly fails anyway.
On Fri, 2 Mar 2012 17:01:12 -0300
Martín Marqués wrote:
> That's all I want (what's in the subject).
>
> I've had some headaches with preupgrade, basically, I guess, because I
> have /var on another partition.
Preupgrade randomly fails anyway. Its great when i
Martín Marqués wrote:
> That's all I want (what's in the subject).
>
> I've had some headaches with preupgrade, basically, I guess, because I
> have /var on another partition.
https://fedoraproject.org/wiki/How_to_use_PreUpgrade
https://fedoraproject.org/wiki
That's all I want (what's in the subject).
I've had some headaches with preupgrade, basically, I guess, because I
have /var on another partition.
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador
--
use
ra 16 preupgrade with grub2 failure.
From: Julius Smith
To: "Michael D. Setzer II"
Copies to: Community support for Fedora users
> Thanks for your info - I finally punched through - here's what mine
> needed to look l
le Fedora16
> root (hd0,0)
> kernel /vmlinuz-3.2.7-1.fc16.i686
> root=/dev/mapper/VolGroup00-LogVol00
> initrd /initramfs-3.2.7-1.fc16.i686.img
>
>
> On 26 Feb 2012 at 17:03, Julius Smith wrote:
>
> Date sent: Sun, 26 Feb 2012 17:03:19 -0800
&
2012 17:03:19 -0800
Subject:Re: Fedora 16 preupgrade with grub2 failure.
From: Julius Smith
To: Community support for Fedora users
> I just did a preupgrade from F15 to F16 and fell into this trap, or
> something similar.
>
> F
I just did a preupgrade from F15 to F16 and fell into this trap, or
something similar.
From a rescue disk boot (F12 is the latest I had lying around), I can
see both grub and grub2 directories in /boot. The grub2 dir looks set
up, but when booting grub/grub.conf is accessed, and it points to the
I've don't a number of upgrades from Fedora 14 to 16 with no
problems, but just had a very bad issue with grub2 not working.
Preupgrade process seemed to go fine, then rebooted.
Screen came up, but was in a very dark gray with slightly lighter
gray letters that were not very readab
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
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 insta
grades, 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://fedora
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
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 bri
t 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) r
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.
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.fedoraproj
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 c
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.
--
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
1 - 100 of 550 matches
Mail list logo
