You are not logged in.
Pages: 1
I've attempted to get away from MBR
and fdisk partioning.
This machine has a BIOS motherboard
ASrock G31M-S with Pentium dual-core
E5300 @ 2.6 GHz. We're moving to
x86_64.
Tried to find everything that has
to do on the GRUB page with BIOS
booting for GUID partioning.
for troubleshooting GRUB section:
Intel BIOS not booting GPT
states that if you decided to use
a GUID partitioning scheme GRUB
may not boot for want of a boot
flag "*" for the /boot partition.
Unfortunately the latest version of
fdisk refuses to execute the "a"
command after gdisk has done its thing.
My gdisk-created partioning scheme is
as follows:
Number Start End Size Code Name
1 2048 4095 1M EF02 BIOS boot partition
2 4096 1052671 512M 8300 Linux filesystem
3 1052672 2101247 512M 8200 Linux swap
4 2101248 976773134 450G 8304 Linux x86-64 root(/)
When fdisk shows this, it's essentially the same except
"Number" becomes /dev/sda1, /dev/sda2, etc.
My goal is to mark /dev/sda2 as "*" (bootable)
I think I can take the drive and put in a bench
test setting & use another version of fdisk,
but this might break something.
Has anyone taken this approach?
I'm going to mark this a SOLVED the moderators
may remove this thread if they want. The GUID
partiton scheme has become corrupted so
that I cannot answer questions about it
Last edited by erichf (2017-03-26 16:04:11)
Offline
What on earth is with your formatting? Why the ballistic approach to linebreaks?
Mod note: not an installation issue, moving to NC.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
What on earth is with your formatting? Why the ballistic approach to linebreaks?.
Text being copied/pasted in nn forums besides here seeking help?
EDIT: Smartphone text? (I don't own one, so I wouldn't know.)
Last edited by c00ter (2017-03-26 00:47:17)
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
have to start this x86_64 install all over
again. Running fdisk from an alien system
(no "w") may have corrupted the partition
layout/ table Have to do that again to
confirm
Offline
Pages: 1