From: David T-G <davidtg-robot@justpickone.org>
To: Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: now that i've screwed up and apparently get to start over ...
Date: Sun, 23 Oct 2022 01:52:15 +0000 [thread overview]
Message-ID: <20221023015215.GS20480@jpo> (raw)
In-Reply-To: <87sfjjefsn.fsf@vps.thesusis.net>
Phillip, et al --
...and then Phillip Susi said...
%
% David T-G <davidtg-robot@justpickone.org> writes:
%
% > Then GRUB puked all over itself and I can't get the stupid thing running
...
% > /dev/sda and put /dev/sde back, and I get that GRUB can't boot from a GPT
% > disk ... except that /dev/sda has always been that!
%
% GRUB can boot from GPT just fine. Assuming you are booting in EFI mode,
% it just has to have an EFI system partition, and be registered with the
Ah, but I'm not. I only have four partitions
jpo:~ # parted /dev/sda unit MiB p free
Model: ATA SAMSUNG MZ7LN128 (scsi)
Disk /dev/sda: 122104MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_boot
Number Start End Size File system Name Flags
0.02MiB 1.00MiB 0.98MiB Free Space
1 1.00MiB 33793MiB 33792MiB linux-swap(v1) jpo-swap swap
2 33793MiB 66561MiB 32768MiB xfs jposuse
3 66561MiB 99329MiB 32768MiB xfs jpoalt legacy_boot
4 99329MiB 122104MiB 22775MiB xfs jpo-ssd
(taken from an identical machine) and do not use that UEFI stuff that I
don't know. Way simple.
% EFI firmware. You can't just copy the partitions to a new drive and
% remove the old drive and expect it to boot. You will need to
% grub-install on the new drive to register it with the EFI firmware.
Heck, I'd be happy to be booting from the old drive!
Thanks again & HANW
:-D
--
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
prev parent reply other threads:[~2022-10-23 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 4:52 now that i've screwed up and apparently get to start over David T-G
2022-10-19 20:07 ` Phillip Susi
2022-10-23 1:52 ` David T-G [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221023015215.GS20480@jpo \
--to=davidtg-robot@justpickone.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).