| 1 |
On Sat, Mar 28, 2020 at 12:13 PM Mark Knecht <markknecht@×××××.com> wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> |
| 5 |
> On Sat, Mar 28, 2020 at 8:41 AM Mike Gilbert <floppym@g.o> wrote: |
| 6 |
> > |
| 7 |
> > On Sat, Mar 28, 2020 at 5:06 AM <tuxic@××××××.de> wrote: |
| 8 |
> > > ...because I have experienced neither any restrictions nor any |
| 9 |
> > > fragilities in the last 12 years of using a MTB setup with that |
| 10 |
> > > "MS-DOS" setup (technically it is more a MTB-setup. MSDOS refers |
| 11 |
> > > to V/FAT, which needs to be used with UEFI in the first partition |
| 12 |
> > > as far as I know...isn't it?) |
| 13 |
> > > |
| 14 |
> > > In short: Never chance a runnig system. |
| 15 |
> > > |
| 16 |
> > > But let us better discuss on a more technical level, since I asked |
| 17 |
> > > for technical help and not for more rethorical given question as |
| 18 |
> > > an answer. |
| 19 |
> > |
| 20 |
> > Here's a technical reason to prefer GPT universally: it stores 2 |
| 21 |
> > copies of the partition table, one at the start of the disk and one at |
| 22 |
> > the end of the disk. If either copy gets destroyed, you should be able |
| 23 |
> > to recover the partition table from the other copy. |
| 24 |
> |
| 25 |
> Mike, |
| 26 |
> What's the process for doing that in general? I assume it's fundamentally to copy the one at the end (what tools) and then to place it back at the beginning? (what tools? |
| 27 |
|
| 28 |
The top hit on Google is this: https://www.rodsbooks.com/gdisk/repairing.html |
| 29 |
|
| 30 |
It documents recovery options using the "gdisk" tool (sys-apps/gptfdisk). |
Archives