On 22.07.2013 22:08, Fernando Lozano wrote:
> Hi,
>
> I don't know if those are related, but I had one system where fedup did
> not updated grub... It ended up booting and running F19 ok, but grub
> menu dsiplaying the old F17 entries. And it boots to the F1 kernel,
> although I could not find a t
Hi,
I don't know if those are related, but I had one system where fedup did
not updated grub... It ended up booting and running F19 ok, but grub
menu dsiplaying the old F17 entries. And it boots to the F1 kernel,
although I could not find a thing that didn't work so far.
Maybe anaconda "forgot" t
Am 20.07.2013 03:16, schrieb Vinny Onelli:
> Date: Fri, 19 Jul 2013 23:40:26 +0200
>> From: Heinz Diehl
>> To: users@lists.fedoraproject.org
>> Subject: Re: Fedora 19 did not install boot record
>> Message-ID: <20130719214026.ga7...@fritha.org>
>> Con
On 19.07.2013 22:58, Vinny Onelli wrote:
> Hello,
> Installed f19, during the prep didn't see any thing about boot so I
> proceeded with installation on reboot this is what I got:
> Booting from local disk ...
> error:no such device:fe0662f9-2f9b-4a9c-81ff-2d77f98c331b
> grub rescue>
> I tried to i
Date: Fri, 19 Jul 2013 23:40:26 +0200
> From: Heinz Diehl
> To: users@lists.fedoraproject.org
> Subject: Re: Fedora 19 did not install boot record
> Message-ID: <20130719214026.ga7...@fritha.org>
> Content-Type: text/plain; charset=us-ascii
>
> On 19.07.2013, Vinny
On 19.07.2013, Vinny Onelli wrote:
> grub-install: command not found
> did I missed some thing during the installation?
You want "grub2-install" ;-)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/list
Hello,
Installed f19, during the prep didn't see any thing about boot so I
proceeded with installation on reboot this is what I got:
Booting from local disk ...
error:no such device:fe0662f9-2f9b-4a9c-81ff-2d77f98c331b
grub rescue>
I tried to install grub by using rescue disk, shell and enter
"chro