public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trouble with backup harddisks
Date: Fri, 1 May 2020 07:07:05 +0200	[thread overview]
Message-ID: <20200501050705.cu3adpnkdaauqhdq@solfire> (raw)
In-Reply-To: <20200430204754.hyh2xzeovsj23xdl@nabokov.fritz.box>

On 04/30 10:47, Wynn Wolf Arbor wrote:
> On 2020-04-30 22:21, Andrea Conti wrote:
> > It won't, as long as it recognizes it as a protective MBR. Which is the
> > right thing to do, as a disk with a protective MBR and no valid GPT is
> > inherently broken.
> 
> True. It was more my intention to depict what the system "should" do in
> order to access the file system.
> 
> > ... or just bypass the partition table altogether. The filesystem starts
> > at sector 1, i.e. 1*512B, so:
> > 
> > mount -o ro,offset=512 /dev/sdb /mnt/xxx
> 
> Interesting, thanks. I was initially considering something like this myself,
> but after a cursory check of the manual, I was under the assumption that
> 'offset' was only valid with loop devices and dismissed that solution.
> 
> Turns out if you mount a drive like this, the kernel uses a loop device in
> the background and you can use the 'offset' option with block devices as
> well. I feel the documentation could be improved here.
> 
> -- 
> Wolf
> 

Hi Andrea, hi Wolf

does my posting from this morning reached you ?
...I did not received anything back from the mailinglist...

Cheers!
Meino




  reply	other threads:[~2020-05-01  5:07 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 [this message]
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
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=20200501050705.cu3adpnkdaauqhdq@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