From: Wynn Wolf Arbor <wolf@oriole.systems>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trouble with backup harddisks
Date: Fri, 1 May 2020 12:27:15 +0200 [thread overview]
Message-ID: <20200501102715.hoqaitsxvudhkqsm@nabokov.fritz.box> (raw)
In-Reply-To: <20200501071810.h6qs7kgewwtbytqd@solfire>
On 2020-05-01 09:18, tuxic@posteo.de wrote:
> A very *#BIG THANK YOU#* for all the great help, the research and
> the solution. I myself am back in "normal mode" :)
Glad it helped!
> One thing remains...
> I want to prevent this kind of hassle in the future... ;)
The most important thing to keep in mind here is to _always_ partition
and format a drive yourself. That way, you know what is on there and how
it was partitioned.
> Perhaps it is a good idea to re-partitions the disk to get rid of
> any bogus bit, format the partition and copy back the data then.
Whilst you can definitely just change the partition type from EE to 83,
now that you can move the data around safely, I'd probably repartition
the drives fully, yeah.
> What is the most reasonable setup here:
> GPT without any hybrid magic and ext4 because it is so common?
> Any other, possible more robust configuration, which is also
> common with rescue tools and -distributions?
For external backup disks like these I'd go with GPT and ext4. Seems to
be the most robust configuration for that use case.
If by "hybrid magic" you mean the Protective MBR, that is not something
you can simply disable. The standard includes the Protective MBR, and
tools adhere to that.
Bottom line: Repartition the disks with GPT, then create the necessary
file systems. Don't turn on any special knobs, the tool's defaults are
all decent.
--
Wolf
next prev parent reply other threads:[~2020-05-01 10:27 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 [this message]
2020-05-01 16:00 ` Andrea Conti
2020-05-01 16:32 ` Peter Humphrey
2020-05-02 2:03 ` tuxic
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=20200501102715.hoqaitsxvudhkqsm@nabokov.fritz.box \
--to=wolf@oriole.systems \
--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