From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trouble with backup harddisks
Date: Sat, 2 May 2020 04:03:05 +0200 [thread overview]
Message-ID: <20200502020305.bvnxxt2egw6evx6d@solfire> (raw)
In-Reply-To: <2530524.mvXUDI8C0e@peak>
On 05/01 05:32, Peter Humphrey wrote:
> On Friday, 1 May 2020 17:00:56 BST Andrea Conti wrote:
>
> > GPT is fine too, but for a 1TB disk with a single partition it has absolutely
> > zero advantage over MBR.
>
> I can think of one or two people who might demur there.
>
> --
> Regards,
> Peter.
>
>
>
>
Hi Wolf, hi Andrea, hi Peter,
*Partition type '83':
I changed the type to 83 using fdisk and this worked fine. Now
/dev/sdb1 is recognized again.
Just to confirm this...
I think, I feel better if I repartitioning/reformat both drives,
though.
*GPT/MBR
From a discussion based on a "GPT or MBR for my system drive" in
conjunction with UEFI it was said, that GPT is more modern and
save.
My question was meant not so much as "MBR or GPT?"
but more whether there are some variants of GPT (with
protected MBR for example -- which was completly new to me),
which I should use or avoid.
But: Are rescue systems for USB-stick more UEFI/GPT aware nowadays
or "traditionally" based on MBR/BIOS-boot?
One thing I found is really handy: An USB-stick with an rEfind
installation. As long as your PC supports UEFI (or can switched to it)
rEfind is able to boot "everything" without prior configuration.
Some rescue-system which really shines and with which you have made good
experiences?
Cheers!
Meino
next prev parent reply other threads:[~2020-05-02 2:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 9:32 [gentoo-user] Trouble with backup harddisks tuxic
2020-04-30 9:55 ` Wols Lists
2020-04-30 10:36 ` tuxic
2020-04-30 12:17 ` Wols Lists
2020-04-30 13:10 ` Wynn Wolf Arbor
2020-04-30 17:04 ` tuxic
2020-04-30 17:21 ` Wynn Wolf Arbor
2020-04-30 19:32 ` antlists
2020-05-01 1:59 ` tuxic
2020-05-01 8:03 ` tuxic
2020-05-01 20:27 ` antlists
2020-05-02 1:42 ` tuxic
2020-05-02 17:31 ` Wols Lists
2020-05-02 17:49 ` tuxic
2020-05-02 17:55 ` tuxic
2020-04-30 13:44 ` Andrea Conti
2020-04-30 18:08 ` tuxic
2020-04-30 19:27 ` Wynn Wolf Arbor
2020-04-30 19:46 ` tuxic
2020-04-30 19:59 ` Wynn Wolf Arbor
2020-04-30 20:21 ` Andrea Conti
2020-04-30 20:47 ` Wynn Wolf Arbor
2020-05-01 5:07 ` tuxic
2020-05-01 6:52 ` Andrea Conti
2020-05-01 7:18 ` tuxic
2020-05-01 10:27 ` Wynn Wolf Arbor
2020-05-01 16:00 ` Andrea Conti
2020-05-01 16:32 ` Peter Humphrey
2020-05-02 2:03 ` tuxic [this message]
2020-05-02 7:49 ` Andrea Conti
2020-05-02 8:39 ` tuxic
2020-05-02 9:23 ` Michael
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=20200502020305.bvnxxt2egw6evx6d@solfire \
--to=tuxic@posteo.de \
--cc=gentoo-user@lists.gentoo.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