Discussion:
no grub after installing fedora23
(too old to reply)
Walter Cazzola
2015-12-23 00:23:11 UTC
Permalink
Dear Fedora Experts,
I' ve recently bought a new Dell Precision m6800 and today I was trying to
install Fedora 23 in dual boot with windows 7 (this was the OS originally
on the machine).

I' ve run the installer from the live CD and after a couple of wrong
attempts I successfully finished the installation process without errors or
at least apparently without errors.

I' ve restarted the machine I got into the following error message:


*file "/boot/grub2/i386-pc/normal.mod" NOT FOUND grub rescue>*

neither windows nor fedora boot.

Booting again from the live cd I got that ever the partition are there:


Device Boot Start End Sectors Size Id Type
/dev/sda1 63 80324 80262 39.2M de Dell Utility
/dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS WinRE
/dev/sda3 25710592 201408511 175697920 83.8G 7 HPFS/NTFS/exFAT
/dev/sda4 201408512 1953523711 1752115200 835.5G 5 Extended
/dev/sda5 201410560 202776575 1366016 667M 83 Linux
/dev/sda6 202778624 307636223 104857600 50G 83 Linux
/dev/sda7 307638272 341192703 33554432 16G 82 Linux swap /
Solaris
/dev/sda8 341194752 351680511 10485760 5G 83 Linux
/dev/sda9 351682560 360071167 8388608 4G 83 Linux
/dev/sda10 360073216 368461823 8388608 4G 83 Linux
/dev/sda11 368463872 371609599 3145728 1.5G 6 FAT16
/dev/sda12 371611648 1953523711 1581912064 754.3G 83 Linux

where sda1-3 are the original windows partitions, sda5 is /boot and sda6 is
/

I' ve mounted the /boot partition and inside grub2 there is not i386-pc dir
nor the normal.mod file. I' ve tried to manually copy
/usr/lib/grub/i386-pc/normal.mod into /boot/grub2 but the only difference I
got is that the boot is stucked on

grub>

So what I have to do to fix the situation and be able to run both windows
and linux?

thank you in advance for your help.

Walter
--
maderios
2015-12-23 11:32:34 UTC
Permalink
Post by Walter Cazzola
Dear Fedora Experts,
I' ve recently bought a new Dell Precision m6800 and today I was trying
to install Fedora 23 in dual boot with windows 7 (this was the OS
originally on the machine).
I' ve run the installer from the live CD and after a couple of wrong
attempts I successfully finished the installation process without errors
or at least apparently without errors.
*file "/boot/grub2/i386-pc/normal.mod" NOT FOUND
grub rescue>*
neither windows nor fedora boot.
Device Boot Start End Sectors Size Id Type
/dev/sda1 63 80324 80262 39.2M de Dell Utility
/dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS WinRE
/dev/sda3 25710592 201408511 175697920 83.8G 7 HPFS/NTFS/exFAT
/dev/sda4 201408512 1953523711 1752115200 835.5G 5 Extended
/dev/sda5 201410560 202776575 1366016 667M 83 Linux
/dev/sda6 202778624 307636223 104857600 50G 83 Linux
/dev/sda7 307638272 341192703 33554432 16G 82 Linux swap /
Solaris
/dev/sda8 341194752 351680511 10485760 5G 83 Linux
/dev/sda9 351682560 360071167 8388608 4G 83 Linux
/dev/sda10 360073216 368461823 8388608 4G 83 Linux
/dev/sda11 368463872 371609599 3145728 1.5G 6 FAT16
/dev/sda12 371611648 1953523711 1581912064 754.3G 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and sda6
is /
I' ve mounted the /boot partition and inside grub2 there is not i386-pc
dir nor the normal.mod file. I' ve tried to manually copy
/usr/lib/grub/i386-pc/normal.mod into /boot/grub2 but the only
difference I got is that the boot is stucked on
grub>
Hi
Why an extended partitition? It should a gpt partitioning with efi. Your
'Dell Precision m6800' uses uefi but you have not any efi partition
http://www.manualslib.com/manual/563583/Dell-Precision-M6800.html?page=58
For me, your install is wrong. First, You have to disable uefi secure
boot in your bios, then install F23. Installer has to detect an efi
partition like '/boot/efi'
--
Maderios
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedor
Chris Murphy
2015-12-24 21:33:46 UTC
Permalink
Post by maderios
Why an extended partitition? It should a gpt partitioning with efi.
Nope, Windows 7 pre-installed. Dell enabled the CSM on those systems.
So it's got the faux-BIOS enabled and thus MBR is required. Windows 7
did support UEFI but it was crap so many vendors just opt to have the
CSM enabled.

Ideally he'd try to get a Windows 8.1 upgrade for free (?) and then
disable the CSM, sometimes perversely in the UI it's an option to
"enable UEFI" as if it's even possible to disable it.


Your
Post by maderios
'Dell Precision m6800' uses uefi but you have not any efi partition
http://www.manualslib.com/manual/563583/Dell-Precision-M6800.html?page=58
For me, your install is wrong. First, You have to disable uefi secure boot
in your bios, then install F23. Installer has to detect an efi partition
like '/boot/efi'
OK please definitely stop suggesting people disable UEFI Secure Boot,
it's bad advice and it's not necessary, Fedora supports Secure Boot
just fine. On any system that has Secure Boot enabled with Windows on
it, *especially* this is bad advice as it exposes the user
unnecessarily to bootloader malware and that's not good. It's a huge
PITA to get rid of those.
--
Chris Murphy
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraprojec
maderios
2015-12-24 22:50:28 UTC
Permalink
Post by Chris Murphy
Your
Post by maderios
'Dell Precision m6800' uses uefi but you have not any efi partition
http://www.manualslib.com/manual/563583/Dell-Precision-M6800.html?page=58
For me, your install is wrong. First, You have to disable uefi secure boot
in your bios, then install F23. Installer has to detect an efi partition
like '/boot/efi'
OK please definitely stop suggesting people disable UEFI Secure Boot,
it's bad advice and it's not necessary, Fedora supports Secure Boot
just fine. On any system that has Secure Boot enabled with Windows on
it, *especially* this is bad advice as it exposes the user
unnecessarily to bootloader malware and that's not good. It's a huge
PITA to get rid of those.
'Secure boot' is just a windows problem. In Linux world, nobody uses
'Secure Boot'. In Windows world, they need it and they use it because
Windows system is 'natively' insecured.
--
Maderios
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask a
Chris Murphy
2015-12-25 00:58:25 UTC
Permalink
Post by Chris Murphy
Your
Post by maderios
'Dell Precision m6800' uses uefi but you have not any efi partition
http://www.manualslib.com/manual/563583/Dell-Precision-M6800.html?page=58
For me, your install is wrong. First, You have to disable uefi secure boot
in your bios, then install F23. Installer has to detect an efi partition
like '/boot/efi'
OK please definitely stop suggesting people disable UEFI Secure Boot,
it's bad advice and it's not necessary, Fedora supports Secure Boot
just fine. On any system that has Secure Boot enabled with Windows on
it, *especially* this is bad advice as it exposes the user
unnecessarily to bootloader malware and that's not good. It's a huge
PITA to get rid of those.
'Secure boot' is just a windows problem. In Linux world, nobody uses 'Secure
Boot'. In Windows world, they need it and they use it because Windows system
is 'natively' insecured.
1. The OP says he's using Windows. And your advice for this Windows
user, was the disable Secure Boot. It's bad advice.

2. It's completely asinine to assert "nobody uses" Secure Boot in the
Linux world. Considering every new Windows 8+ preloaded computer has
Secure Boot enabled, and most every Linux distro supports Secure Boot
out of the box, it's just factually wrong to assert that no Linux
users use it. Of course they are. Tens of thousands are.

3. Bootloader malware takes control in the pre-boot environment.
That's what Secure Boot is designed to protect against. It hardly
matters how the system is infected. What matters is prevention and
what you're proposing is that people disable being protected against
it. And that's bad advice.
--
Chris Murphy
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? A
Tim
2015-12-25 14:28:25 UTC
Permalink
What matters is prevention and what you're proposing is that people
disable being protected against it. And that's bad advice.
I tend to view such hazardous advice with more than just suspicion that
the person doesn't fully appreciate the situation, I'm concerned that
they might be a black hat trying to make it easier for their mates.

I think, that as a matter of security, you have to be suspicious of
"turn off your firewall/malware-protection/etc.," advice, as coming from
someone with ulterior motives, or coming from someone who's been
unwittingly conditioned by those with ulterior motives.
--
All mail to my mailbox is automatically deleted, there is no point
trying to privately email me, I will only read messages posted to the
public lists.

I'd just like to say that vinyl record crackles and pops are far less
annoying than digigigigital mu-u-u-u-usic hiccicicicups and
yooo-----------------u tu-----be ....... pauses.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? A
Gordon Messmer
2015-12-25 21:00:48 UTC
Permalink
'Secure boot' is just a windows problem. In Linux world, nobody uses 'Secure
Boot'. In Windows world, they need it and they use it because Windows system
is 'natively' insecured.
Nonsense. Secure Boot secures Linux systems against rootkits, as
well, by prohibiting unsigned content in kernel mode.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? As
maderios
2015-12-25 21:29:44 UTC
Permalink
Post by Gordon Messmer
'Secure boot' is just a windows problem. In Linux world, nobody uses 'Secure
Boot'. In Windows world, they need it and they use it because Windows system
is 'natively' insecured.
Nonsense. Secure Boot secures Linux systems against rootkits, as
well, by prohibiting unsigned content
Its' Redhat point of view...
I'm not specialist but, historically, I know Redhat dev asked Linus
Torvalds patch kernel with 'secure boot'
Linus Torvalds answer (2013):
http://www.pcworld.com/article/2029542/linus-torvalds-speaks-out-with-a-secure-boot-plan.html
http://arstechnica.com/information-technology/2013/02/linus-torvalds-i-will-not-change-linux-to-deep-throat-microsoft/
http://www.networkworld.com/article/2224184/microsoft-subnet/microsoft-s-secure-boot--red-hat-request-ignites-linus-torvalds--nsfw-flame-war.html
--
Maderios
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Hav
Gordon Messmer
2015-12-26 07:02:18 UTC
Permalink
Post by maderios
Its' Redhat point of view...
I'm not specialist but, historically, I know Redhat dev asked Linus
Torvalds patch kernel with 'secure boot'
It's an interesting historical footnote, but I don't think you (or the
authors of those articles) understand the pull request or Linus'
response. At the time of that pull request, Linux had supported Secure
Boot for some time already. The pull request added a mechanism for
importing new keys. So, it's not particularly relevant to the question
of whether or not to use Secure Boot.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedorap
Chris Murphy
2015-12-26 22:26:01 UTC
Permalink
Post by maderios
Post by Gordon Messmer
'Secure boot' is just a windows problem. In Linux world, nobody uses 'Secure
Boot'. In Windows world, they need it and they use it because Windows system
is 'natively' insecured.
Nonsense. Secure Boot secures Linux systems against rootkits, as
well, by prohibiting unsigned content
Its' Redhat point of view...
I'm not specialist but, historically, I know Redhat dev asked Linus
Torvalds patch kernel with 'secure boot'
You need to read the whole thread. It wasn't about just secure boot
yes or no in general. It had to do with enabling the use of keys in
PEs instead of only depending on X509 support in the kernel:
http://thread.gmane.org/gmane.linux.kernel/1445369/focus=1445405

and

http://thread.gmane.org/gmane.linux.kernel/1445369/focus=1445405

Are good summaries.
--
Chris Murphy
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a
Chris Murphy
2015-12-27 00:58:27 UTC
Permalink
Post by Chris Murphy
Post by maderios
Post by Gordon Messmer
'Secure boot' is just a windows problem. In Linux world, nobody uses 'Secure
Boot'. In Windows world, they need it and they use it because Windows system
is 'natively' insecured.
Nonsense. Secure Boot secures Linux systems against rootkits, as
well, by prohibiting unsigned content
Its' Redhat point of view...
I'm not specialist but, historically, I know Redhat dev asked Linus
Torvalds patch kernel with 'secure boot'
You need to read the whole thread. It wasn't about just secure boot
yes or no in general. It had to do with enabling the use of keys in
http://thread.gmane.org/gmane.linux.kernel/1445369/focus=1445405
and
http://thread.gmane.org/gmane.linux.kernel/1445369/focus=1445405
Are good summaries.
Oops.
http://article.gmane.org/gmane.linux.kernel/1445516

http://article.gmane.org/gmane.linux.kernel/1447326

and
--
Chris Murphy
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.o
Walter Cazzola
2015-12-23 14:20:50 UTC
Permalink
hi
thanks for the prompt reply
Post by maderios
Hi
Why an extended partitition?
I just marked the normal partition flag instead of LVM, is there any
practical and related issue with my problem in this?
Post by maderios
It should a gpt partitioning with efi. Your 'Dell Precision m6800' uses
uefi but you have not any efi partition
http://www.manualslib.com/manual/563583/Dell-Precision-M6800.html?page=58
For me, your install is wrong. First, You have to disable uefi secure boot
in your bios, then install F23. Installer has to detect an efi partition
like '/boot/efi'
uhm, I' ve checked and in what should be the /boot dir I' ve

efi
|-->EFI
|-->BOOT
|-->BOOTX64.EFI
|-->fallback.efi
|-->fedora
|-->BOOT.CSV
|-->fonts
|-->unicode.pf2
|-->gcdx64.efi
|-->grubx64.efi
|-->MokManager.efi
|-->shim.efi
|-->shim-fedora.efi
|-->mach_kernel
|-->System
|-->Library
|-->CoreServices
|-->SystemVersion.plist

as far as I know everything is there or is it not?

I've also checked the options related to UEFI in my BIOS and seems that
UEFI and Secure boot are both disabled.
This are the related options:
General
Boot Sequence
Legacy (this flagged)
UEFI (this is not flagged)
Advanced Boot Options
Enable Legacy Option ROMS (this is selected and the note says "This
option is not allowed if secure boot is enabled")
System Configuration
Integrated NIC
Enabled UEFI Network Stack (this is not flagged)
Enabled w/PXE (this is flagged)
Secure Boot
Disabled (flagged)


Could be that I missed something? Any other idea?

Walter

--
Doug H.
2015-12-23 14:34:40 UTC
Permalink
 
   General
       Boot Sequence
           Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was
not set for your new /boot partition.  From your post, with lots of
snipping:


Device     Boot     Start        End    Sectors   Size Id Type
/dev/sda2  *         81920   25710591   25628672  12.2G 27 Hidden NTFS 
/dev/sda5       201410560  202776575    1366016   667M 83 Linux

where sda1-3 are the original windows partitions, sda5 is /boot and
sda6 is /
--
Doug H.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.
Walter Cazzola
2015-12-23 14:54:59 UTC
Permalink
Post by Doug H.
Post by Walter Cazzola
General
Boot Sequence
Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was
not set for your new /boot partition. From your post, with lots of
Device Boot Start End Sectors Size Id Type
/dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS
/dev/sda5 201410560 202776575 1366016 667M 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and
sda6 is /
Indeed you could be right. How I can change such a flag?

Second question: the error message said that no
/boot/grub2/i386-pc/normal.mod file is available and effectively I don' t
have such a file in that position but only it is in /usr/lib/grub/i386-pc/.
So changing the boot flag would be enough to solve the problem?

Walter

--
Doug H.
2015-12-23 15:12:48 UTC
Permalink
Post by Doug H.
 
   General
       Boot Sequence
           Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was
not set for your new /boot partition.  From your post, with lots of
Device     Boot     Start        End    Sectors   Size Id Type
/dev/sda2  *         81920   25710591   25628672  12.2G 27 Hidden
NTFS 
/dev/sda5       201410560  202776575    1366016   667M 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and
sda6 is /
Indeed you could be right. How I can change such a flag? 
Second question: the error message said that no /boot/grub2/i386-
pc/normal.mod file is available and effectively I don' t have such a
file in that position but only it is in /usr/lib/grub/i386-pc/. So
changing the boot flag would be enough to solve the problem?
Please don't try this unless others reply to support this, but...

If you can boot to a Fedora CD/DVD which is able to detect your Fedora
install then I think it should be something like this...

chroot /mnt/sysimage

fdisk /dev/sda
 Command (m for help): a
 Partition number ([snip] default x): 5
 Command (m for help): w
 The partition table has been altered.
 Calling ioctl() to re-read partition table.

grub2-install /dev/sda
--
Doug H.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a ques
Walter Cazzola
2015-12-23 16:48:29 UTC
Permalink
Hi
few more questions inline with your reply.
Post by Doug H.
Post by Walter Cazzola
Post by Doug H.
Post by Walter Cazzola
General
Boot Sequence
Legacy (this flagged)
In that case, I think your first post indicated that the boot flag was
not set for your new /boot partition. From your post, with lots of
Device Boot Start End Sectors Size Id Type
/dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS
/dev/sda5 201410560 202776575 1366016 667M 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and
sda6 is /
Indeed you could be right. How I can change such a flag?
Second question: the error message said that no /boot/grub2/i386-
pc/normal.mod file is available and effectively I don' t have such a
file in that position but only it is in /usr/lib/grub/i386-pc/. So
changing the boot flag would be enough to solve the problem?
Please don't try this unless others reply to support this, but...
ok I will wait
If you can boot to a Fedora CD/DVD which is able to detect your Fedora
install then I think it should be something like this..
what do you mean by " is able to detect your Fedora install"? I can boot
with the live cd and mount all the partitions but nothing is automatically
done.
Post by Doug H.
chroot /mnt/sysimage
what should sysimage be? is this a file in the /boot partition? I don' t
have any file with this name in /boot
Post by Doug H.
fdisk /dev/sda
Command (m for help): a
Partition number ([snip] default x): 5
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I' ve to change something?
what should this do?
Post by Doug H.
grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?

thanks for the help
Walter


--
Richard Shaw
2015-12-23 16:58:56 UTC
Permalink
I don't know if it was a rogue update or something but I had the same (or
similar) problem. Booting dropped me to the grub rescue prompt and my
i386-pc folder was also empty.

Only strange part of my setup is the main drive is GPT partitioned with
regular BIOS so I have a small bios_grub partition at the beginning of the
drive for the stage 2 bootloader.

Somehow my /boot filesystem got corrupted and after a fsck and copying the
files from /usr/lib/grub2/i386-pc to /boot/grub2/i386-pc I was able to boot
again.

Thanks,
Richard
Walter Cazzola
2015-12-23 17:15:12 UTC
Permalink
Post by Richard Shaw
I don't know if it was a rogue update or something but I had the same (or
similar) problem. Booting dropped me to the grub rescue prompt and my
i386-pc folder was also empty.
Only strange part of my setup is the main drive is GPT partitioned with
regular BIOS so I have a small bios_grub partition at the beginning of the
drive for the stage 2 bootloader.
Somehow my /boot filesystem got corrupted and after a fsck and copying the
files from /usr/lib/grub2/i386-pc to /boot/grub2/i386-pc I was able to boot
again.
I' ve tried to copy from /usr/lib/grub (I don' t have grub2 dir but just
grub) but the only result was to boot to the grub shell instead of the grub
rescue shell.

Can this help?

Walter

--
Doug H.
2015-12-23 18:08:01 UTC
Permalink
Post by Walter Cazzola
Hi 
few more questions inline with your reply.
 chroot /mnt/sysimage
what should sysimage be? is this a file in the /boot partition? I
don't have any file with this name in /boot
Historically (and currently I think), the rescue/repair option for the
Fedora CD & DVD is to look for a Fedora install and then mount it in
/mnt/sysimage.  So there would be a /mnt/sysimage/boot for example.
Thus you can do `chroot /mnt/sysimage` and the shell will act like you
are simply logged into the Fedora system.  Things would work as if you
had booted normally into the Fedora system.  That allows you to do
maintenance using the same full paths as "normal".
Post by Walter Cazzola
 fdisk /dev/sda
 Command (m for help): a
 Partition number ([snip] default x): 5
 Command (m for help): w
 The partition table has been altered.
 Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I've to change
something? what should this do?
I ran an fdisk on a temp loopfile and then altered the output to show
"5" since I think that is the partition that I think might need to be
bootable.  What that does is to make partition 5 the boot/bootable
partition.  I don't really know how that works at a deeper level and I
have little experience with efi so far.  My suggestions are based on
the idea that your bios setup is presenting a traditional/older system
type.
Post by Walter Cazzola
 grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?
The above assumes that your Windows boot utility has already been
messed with and is not usable at the moment.  If that is true then I am
not even sure you need to do the grub2-install but it seems like it
would not make it worse.

But again I don't feel comfortable suggesting these actions unless we
get some community support for it.
--
Doug H.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have
Walter Cazzola
2015-12-23 21:05:20 UTC
Permalink
Hi.
I've done some attempts and following a guide for ubunto I got some
improvements.

At the moment the normal.mod is in the boot partition and I'm not starting
with the grub2 rescue terminal but with still the selection menu doesn' t
appear and the system doesn' t boot.

At the moment the system get stuck on:
grub2>
prompt.

I dug a littel in the system and
- the boot flag still points to the sda2 (the dell recopvery partition)
instead of the one with /boot partition (sda5)
- in /etc there is a grub2.cfg file that it is a dangling link to
/boot/grub2/grub.cfg
probably both of these points are part of the problem.

Looking around I found some guides about ubunto (e.g.,
https://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-grub-2-on-linux/)
that uses an update-grub command to create the boot loader but I can' t
find anything like that for fedora. What I'm I doing wrong now?

Walter
Post by Doug H.
Post by Walter Cazzola
Hi
few more questions inline with your reply.
chroot /mnt/sysimage
what should sysimage be? is this a file in the /boot partition? I
don't have any file with this name in /boot
Historically (and currently I think), the rescue/repair option for the
Fedora CD & DVD is to look for a Fedora install and then mount it in
/mnt/sysimage. So there would be a /mnt/sysimage/boot for example.
Thus you can do `chroot /mnt/sysimage` and the shell will act like you
are simply logged into the Fedora system. Things would work as if you
had booted normally into the Fedora system. That allows you to do
maintenance using the same full paths as "normal".
Post by Walter Cazzola
Post by Doug H.
fdisk /dev/sda
Command (m for help): a
Partition number ([snip] default x): 5
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I've to change
something? what should this do?
I ran an fdisk on a temp loopfile and then altered the output to show
"5" since I think that is the partition that I think might need to be
bootable. What that does is to make partition 5 the boot/bootable
partition. I don't really know how that works at a deeper level and I
have little experience with efi so far. My suggestions are based on
the idea that your bios setup is presenting a traditional/older system
type.
Post by Walter Cazzola
Post by Doug H.
grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?
The above assumes that your Windows boot utility has already been
messed with and is not usable at the moment. If that is true then I am
not even sure you need to do the grub2-install but it seems like it
would not make it worse.
But again I don't feel comfortable suggesting these actions unless we
get some community support for it.
--
Doug H.
--
Walter Cazzola
2015-12-23 21:33:53 UTC
Permalink
Sorry for the flooding but my investigations is goin' further into the
problem.

Looking at the content of /boot
-rw-r--r--. 1 root root 160270 Oct 5 11:58 config-4.2.3-300.fc23.x86_64
drwxr-xr-x. 4 root root 4096 Oct 29 17:26 efi
-rw-r--r--. 1 root root 184380 Oct 21 2014 elf-memtest86+-5.01
drwxr-xr-x. 2 root root 4096 Oct 29 17:23 extlinux
drwxr-xr-x. 6 root root 4096 Dec 23 15:18 grub2
-rw-rw-r--. 1 root root 52373550 Dec 22 23:07
initramfs-0-rescue-4f585391395b40e3823bebd86a3e6c01.img
-rw-rw-r--. 1 root root 17771095 Dec 22 23:07
initramfs-4.2.3-300.fc23.x86_64.img
-rw-r--r--. 1 root root 571817 Oct 29 17:27 initrd-plymouth.img
drwx------. 2 root root 16384 Dec 22 23:01 lost+found
-rw-r--r--. 1 root root 182704 Oct 21 2014 memtest86+-5.01
-rw-------. 1 root root 3152021 Oct 5 11:58
System.map-4.2.3-300.fc23.x86_64
-rwxr-xr-x. 1 root root 5977368 Dec 22 23:07
vmlinuz-0-rescue-4f585391395b40e3823bebd86a3e6c01
-rwxr-xr-x. 1 root root 5977368 Oct 5 11:59 vmlinuz-4.2.3-300.fc23.x86_64

it seems that initrd for tmy kernel is missing and also tryin' to manually
boot from the grub menu let the system fail.

My impression is that the whole fedora installation tool failed and I' ve a
partial system but I can' t find more on this. I' m quite ready to give up
and try to install a different flavor of linux.

Walter
Post by Walter Cazzola
Hi.
I've done some attempts and following a guide for ubunto I got some
improvements.
At the moment the normal.mod is in the boot partition and I'm not
starting with the grub2 rescue terminal but with still the selection menu
doesn' t appear and the system doesn' t boot.
grub2>
prompt.
I dug a littel in the system and
- the boot flag still points to the sda2 (the dell recopvery partition)
instead of the one with /boot partition (sda5)
- in /etc there is a grub2.cfg file that it is a dangling link to
/boot/grub2/grub.cfg
probably both of these points are part of the problem.
Looking around I found some guides about ubunto (e.g.,
https://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-grub-2-on-linux/)
that uses an update-grub command to create the boot loader but I can' t
find anything like that for fedora. What I'm I doing wrong now?
Walter
Post by Doug H.
Post by Walter Cazzola
Hi
few more questions inline with your reply.
chroot /mnt/sysimage
what should sysimage be? is this a file in the /boot partition? I
don't have any file with this name in /boot
Historically (and currently I think), the rescue/repair option for the
Fedora CD & DVD is to look for a Fedora install and then mount it in
/mnt/sysimage. So there would be a /mnt/sysimage/boot for example.
Thus you can do `chroot /mnt/sysimage` and the shell will act like you
are simply logged into the Fedora system. Things would work as if you
had booted normally into the Fedora system. That allows you to do
maintenance using the same full paths as "normal".
Post by Walter Cazzola
Post by Doug H.
fdisk /dev/sda
Command (m for help): a
Partition number ([snip] default x): 5
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
do the numbers already refer to my partitions or I've to change
something? what should this do?
I ran an fdisk on a temp loopfile and then altered the output to show
"5" since I think that is the partition that I think might need to be
bootable. What that does is to make partition 5 the boot/bootable
partition. I don't really know how that works at a deeper level and I
have little experience with efi so far. My suggestions are based on
the idea that your bios setup is presenting a traditional/older system
type.
Post by Walter Cazzola
Post by Doug H.
grub2-install /dev/sda
if this doesn't work can I go back to the previous situation? if yes how?
The above assumes that your Windows boot utility has already been
messed with and is not usable at the moment. If that is true then I am
not even sure you need to do the grub2-install but it seems like it
would not make it worse.
But again I don't feel comfortable suggesting these actions unless we
get some community support for it.
--
Doug H.
--
--
maderios
2015-12-23 21:42:35 UTC
Permalink
Post by Walter Cazzola
My impression is that the whole fedora installation tool failed and I'
ve a partial system but I can' t find more on this. I' m quite ready to
give up and try to install a different flavor of linux.
I told you the base, your disk partitioning, is bad. A new/good fresh
install avoid wasting time... Normally, it takes only about 20 mn.
Dont forget efi partition.
Good luck
--
Maderios
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a questi
Doug H.
2015-12-23 21:46:36 UTC
Permalink
Post by Walter Cazzola
Sorry for the flooding but my investigations is goin' further into
the problem. 
Looking at the content of /boot
-rw-r--r--. 1 root root   160270 Oct  5 11:58 config-4.2.3-
300.fc23.x86_64
drwxr-xr-x. 4 root root     4096 Oct 29 17:26 efi
-rw-r--r--. 1 root root   184380 Oct 21  2014 elf-memtest86+-5.01
drwxr-xr-x. 2 root root     4096 Oct 29 17:23 extlinux
drwxr-xr-x. 6 root root     4096 Dec 23 15:18 grub2
-rw-rw-r--. 1 root root 52373550 Dec 22 23:07 initramfs-0-rescue-
4f585391395b40e3823bebd86a3e6c01.img
-rw-rw-r--. 1 root root 17771095 Dec 22 23:07 initramfs-4.2.3-
300.fc23.x86_64.img
-rw-r--r--. 1 root root   571817 Oct 29 17:27 initrd-plymouth.img
drwx------. 2 root root    16384 Dec 22 23:01 lost+found
-rw-r--r--. 1 root root   182704 Oct 21  2014 memtest86+-5.01
-rw-------. 1 root root  3152021 Oct  5 11:58 System.map-4.2.3-
300.fc23.x86_64
-rwxr-xr-x. 1 root root  5977368 Dec 22 23:07 vmlinuz-0-rescue-
4f585391395b40e3823bebd86a3e6c01
-rwxr-xr-x. 1 root root  5977368 Oct  5 11:59 vmlinuz-4.2.3-
300.fc23.x86_64
 it seems that initrd for tmy kernel is missing and also tryin' to
manually boot from the grub menu let the system fail. 
My impression is that the whole fedora installation tool failed and
I've a partial system but I can' t find more on this. I' m quite
ready to give up and try to install a different flavor of linux.
Re-install, Fedora or otherwise, might be the quick fix.  But I don't
Post by Walter Cazzola
ls -1 /boot
config-4.2.6-301.fc23.x86_64
config-4.2.7-300.fc23.x86_64
config-4.2.8-300.fc23.x86_64
elf-memtest86+-5.01
extlinux
grub2
initramfs-0-rescue-c10a26eb97b3451f95a20a792c5a897d.img
initramfs-4.1.7-200.fc22.x86_64.img
initramfs-4.2.6-301.fc23.x86_64.img
initramfs-4.2.7-300.fc23.x86_64.img
initramfs-4.2.8-300.fc23.x86_64.img
initrd-plymouth.img
lost+found
memtest86+-5.01
System.map-4.2.6-301.fc23.x86_64
System.map-4.2.7-300.fc23.x86_64
System.map-4.2.8-300.fc23.x86_64
vmlinuz-0-rescue-c10a26eb97b3451f95a20a792c5a897d
vmlinuz-4.2.6-301.fc23.x86_64
vmlinuz-4.2.7-300.fc23.x86_64
vmlinuz-4.2.8-300.fc23.x86_64


Notice that the init fs files are named as yours is.
--
Doug H.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.or
Doug H.
2015-12-23 22:34:05 UTC
Permalink
Post by Doug H.
Please don't try this unless others reply to support this, but...
If you can boot to a Fedora CD/DVD which is able to detect your Fedora
install then I think it should be something like this...
chroot /mnt/sysimage
fdisk /dev/sda
 Command (m for help): a
 Partition number ([snip] default x): 5
 Command (m for help): w
 The partition table has been altered.
 Calling ioctl() to re-read partition table.
grub2-install /dev/sda
As maderios has pointed out, this partitioning does not look
workable. I don't think you can toggle the boot flag on for an extended
partition.
--
Doug H.
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Ha
Walter Cazzola
2015-12-23 22:58:25 UTC
Permalink
As maderios has pointed out, this partitioning does not look
workable. I don't think you can toggle the boot flag on for an extended
partition.
Ok tomorrow I'll redo the installation.

But just to do the right thing since the beginning how should the the disk
be partitioned?

Considering that the windows installation is split over three partitions
(sda1-3) that I won't touch and I would like to have
-/var
-/tmp
-/
-/home
- swap
-/opt
-/boot
- and a vfat partition to exchange data with Windows
On separate partitions.

Also I don't know what this efi partition (that maderios is mentioning) is
and is for. And how I should create it.

Any help would be really appreciated on this matter.

Thank you
Walter
maderios
2015-12-24 13:04:25 UTC
Permalink
Post by Walter Cazzola
As maderios has pointed out, this partitioning does not look
workable. I don't think you can toggle the boot flag on for an extended
partition.
Ok tomorrow I'll redo the installation.
But just to do the right thing since the beginning how should the the
disk be partitioned?
Considering that the windows installation is split over three partitions
(sda1-3) that I won't touch and I would like to have
-/var
-/tmp
-/
-/home
- swap
-/opt
-/boot
- and a vfat partition to exchange data with Windows
On separate partitions.
Also I don't know what this efi partition (that maderios is mentioning)
is and is for. And how I should create it.
If you want only one system, F23, installed on hour hd, I suggest
simple partitionning
/dev/sda1 /boot/efi
/dev/sda2 swap
/dev/sda3 /
/dev/sda4 /home

If you want dual boot F23 + Windows, example
/dev/sda1 /boot/efi
/dev/sda2 W$
/dev/sda3 W$
/dev/sda4 swap
/dev/sda5 /
/dev/sda6 /home
--
Maderios
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have
Walter Cazzola
2015-12-24 22:15:48 UTC
Permalink
Hi,
thanks all for the help at end I missed to create a bootbios partion of
2MiB once I added that the system booted. The strange point is that I
didn't find it explained in any tutorial but thanks to your advice I
noticed that entry in the filesystem menu.

Walter
Post by Walter Cazzola
As maderios has pointed out, this partitioning does not look
workable. I don't think you can toggle the boot flag on for an extended
partition.
Ok tomorrow I'll redo the installation.
But just to do the right thing since the beginning how should the the
disk be partitioned?
Considering that the windows installation is split over three partitions
(sda1-3) that I won't touch and I would like to have
-/var
-/tmp
-/
-/home
- swap
-/opt
-/boot
- and a vfat partition to exchange data with Windows
On separate partitions.
Also I don't know what this efi partition (that maderios is mentioning)
is and is for. And how I should create it.
If you want only one system, F23, installed on hour hd, I suggest simple
partitionning
/dev/sda1 /boot/efi
/dev/sda2 swap
/dev/sda3 /
/dev/sda4 /home
If you want dual boot F23 + Windows, example
/dev/sda1 /boot/efi
/dev/sda2 W$
/dev/sda3 W$
/dev/sda4 swap
/dev/sda5 /
/dev/sda6 /home
--
Chris Murphy
2015-12-24 22:30:56 UTC
Permalink
Hi,
thanks all for the help at end I missed to create a bootbios partion of 2MiB
once I added that the system booted. The strange point is that I didn't find
it explained in any tutorial but thanks to your advice I noticed that entry
in the filesystem menu.
This is unexpected because BIOSBoot only exists on GPT. But Windows
requires MBR on BIOS (legacy) systems, and GPT on UEFI systems. It's
not possible to get it to do anything different. So if the
installation is GPT, that suggests UEFI installation, and there should
be an EFI System partition rather than BIOSBoot.

The fact there is an extended partition, and boot flags in earlier
reports, shows this is an MBR partitioned drive. Those things don't
exist with GPT drives.
--
Chris Murphy
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a questio
Walter Cazzola
2015-12-24 23:21:02 UTC
Permalink
Post by Chris Murphy
Post by Walter Cazzola
Hi,
thanks all for the help at end I missed to create a bootbios partion of
2MiB
Post by Walter Cazzola
once I added that the system booted. The strange point is that I didn't
find
Post by Walter Cazzola
it explained in any tutorial but thanks to your advice I noticed that
entry
Post by Walter Cazzola
in the filesystem menu.
This is unexpected because BIOSBoot only exists on GPT. But Windows
requires MBR on BIOS (legacy) systems, and GPT on UEFI systems. It's
not possible to get it to do anything different. So if the
installation is GPT, that suggests UEFI installation, and there should
be an EFI System partition rather than BIOSBoot.
The fact there is an extended partition, and boot flags in earlier
reports, shows this is an MBR partitioned drive. Those things don't
exist with GPT drives.
I don't know what to say, this is my current configuration:

/dev/sda1 63 80324 80262 39.2M de Dell Utility
/dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS WinRE
/dev/sda3 25710592 201408511 175697920 83.8G 7 HPFS/NTFS/exFAT
/dev/sda4 201408512 1953523711 1752115200 835.5G 5 Extended
/dev/sda5 201410560 201414655 4096 2M 83 Linux
/dev/sda6 201416704 202883071 1466368 716M 83 Linux
/dev/sda7 202885120 307742719 104857600 50G 83 Linux
/dev/sda8 307744768 358076415 50331648 24G 82 Linux swap / Sola
/dev/sda9 358078464 372758527 14680064 7G 83 Linux
/dev/sda10 372760576 383246335 10485760 5G 83 Linux
/dev/sda11 383248384 393734143 10485760 5G 83 Linux
/dev/sda12 393736192 396881919 3145728 1.5G 6 FAT16
/dev/sda13 396883968 1953523711 1556639744 742.3G 83 Linux

and for now the system boots correctly

Walter
--
Chris Murphy
2015-12-25 00:50:58 UTC
Permalink
Post by Walter Cazzola
Post by Chris Murphy
Hi,
thanks all for the help at end I missed to create a bootbios partion of 2MiB
once I added that the system booted. The strange point is that I didn't find
it explained in any tutorial but thanks to your advice I noticed that entry
in the filesystem menu.
This is unexpected because BIOSBoot only exists on GPT. But Windows
requires MBR on BIOS (legacy) systems, and GPT on UEFI systems. It's
not possible to get it to do anything different. So if the
installation is GPT, that suggests UEFI installation, and there should
be an EFI System partition rather than BIOSBoot.
The fact there is an extended partition, and boot flags in earlier
reports, shows this is an MBR partitioned drive. Those things don't
exist with GPT drives.
/dev/sda1 63 80324 80262 39.2M de Dell Utility
/dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS WinRE
/dev/sda3 25710592 201408511 175697920 83.8G 7 HPFS/NTFS/exFAT
/dev/sda4 201408512 1953523711 1752115200 835.5G 5 Extended
/dev/sda5 201410560 201414655 4096 2M 83 Linux
/dev/sda6 201416704 202883071 1466368 716M 83 Linux
/dev/sda7 202885120 307742719 104857600 50G 83 Linux
/dev/sda8 307744768 358076415 50331648 24G 82 Linux swap / Sola
/dev/sda9 358078464 372758527 14680064 7G 83 Linux
/dev/sda10 372760576 383246335 10485760 5G 83 Linux
/dev/sda11 383248384 393734143 10485760 5G 83 Linux
/dev/sda12 393736192 396881919 3145728 1.5G 6 FAT16
/dev/sda13 396883968 1953523711 1556639744 742.3G 83 Linux
and for now the system boots correctly
There is no BIOSBoot in that list though. And that list is using MBR
type codes. I'd say this listing is unreliable, I don't know the
source. Please post the complete, unedited listing from:

# parted /dev/sda u s p

That'll provide better info.
--
Chris Murphy
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Ha
Chris Murphy
2015-12-24 21:28:19 UTC
Permalink
Post by Walter Cazzola
Dear Fedora Experts,
I' ve recently bought a new Dell Precision m6800 and today I was trying to
install Fedora 23 in dual boot with windows 7 (this was the OS originally on
the machine).
I' ve run the installer from the live CD and after a couple of wrong
attempts I successfully finished the installation process without errors or
at least apparently without errors.
file "/boot/grub2/i386-pc/normal.mod" NOT FOUND
grub rescue>
That is a bootloader file, and it's a binary that's only ever found on
computers with BIOS firmware. On computers with UEFI firmware, it's
not needed.

So if this m6800 has UEFI, it must have legacy boot enabled... oh hell.
Post by Walter Cazzola
neither windows nor fedora boot.
Device Boot Start End Sectors Size Id Type
/dev/sda1 63 80324 80262 39.2M de Dell Utility
This is a huge red flag. Can you boot off live media, connect to wifi
if supported out of the box, or plug in an ethernet cable and run:

# parted /dev/sda u s p > parted.txt
# fpaste parted.txt

And you'll get a URL you can post. Like this: http://ur1.ca/ocxjd

I want to know if this is GPT or MBR and what the physical sector size
is, because LBA 63 on a 512e AF drive is bad news performance wise and
some companies did do this for a while including Dell and it's just...
really f'n annoyingly incompetent. I do have a work around that's
rather tedious but we get to that later.

If you're feeling brave, it's semi worthwhile poking around the
firmware setup (probably F2) to see if you can find the words Secure
Boot. I'm curious if this firmware supports it or not. Don't change
the setting, I just want to know if you can find it or not.
Post by Walter Cazzola
/dev/sda2 * 81920 25710591 25628672 12.2G 27 Hidden NTFS WinRE
/dev/sda3 25710592 201408511 175697920 83.8G 7 HPFS/NTFS/exFAT
/dev/sda4 201408512 1953523711 1752115200 835.5G 5 Extended
/dev/sda5 201410560 202776575 1366016 667M 83 Linux
/dev/sda6 202778624 307636223 104857600 50G 83 Linux
/dev/sda7 307638272 341192703 33554432 16G 82 Linux swap /
Solaris
/dev/sda8 341194752 351680511 10485760 5G 83 Linux
/dev/sda9 351682560 360071167 8388608 4G 83 Linux
/dev/sda10 360073216 368461823 8388608 4G 83 Linux
/dev/sda11 368463872 371609599 3145728 1.5G 6 FAT16
/dev/sda12 371611648 1953523711 1581912064 754.3G 83 Linux
where sda1-3 are the original windows partitions, sda5 is /boot and sda6 is
/
I' ve mounted the /boot partition and inside grub2 there is not i386-pc dir
nor the normal.mod file. I' ve tried to manually copy
/usr/lib/grub/i386-pc/normal.mod into /boot/grub2 but the only difference I
got is that the boot is stucked on
grub>
So what I have to do to fix the situation and be able to run both windows
and linux?
The easiest way to fix this and not change anything or reinstall? Is
to download netinstall media, ~400MB download. And change the boot
parameter line (use the tab key to show the boot param line at the
boot menu) and add at the end, inst.rescue. Choose the default option
in each, it should find all the parts of the system and assemble them
at /mnt/sysimage. Then you can do:

# chroot /mnt/sysimage
# grub2-install /dev/sda5 --force
# grub2-mkconfig -o /boot/grub2/grub.cfg

And then reboot. What I'm virtually certain has happened is because
partition 1 starts at LBA 63, and because Fedora defaults to using
LVM, the GRUB core.img is too big to be embedded in the MBR gap. And
therefore the installation of the bootloader actually failed during
the OS install.

Installing the bootloader by embedding to the VBR of /dev/sda5 is
suboptimal and not recommended by GRUB upstream, but it is supported
with --force which is what that command above will do. And it should
be pretty stable. And if it works, then you're done.
--
Chris Murphy
--
users mailing list
***@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask awa
Continue reading on narkive:
Loading...