From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 22071138350 for ; Fri, 1 May 2020 05:07:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B722DE0BCB; Fri, 1 May 2020 05:07:10 +0000 (UTC) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3AFA1E0B58 for ; Fri, 1 May 2020 05:07:09 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 237D52400FB for ; Fri, 1 May 2020 07:07:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1588309627; bh=6CNszyjuaaK1kwaueESzwghWm29m/CBG5uXtWlWmz+g=; h=Date:From:To:Subject:From; b=hKuLYmxG04Wutm6JD2n0kayNxVJnfJL/uDez1UvGX7jjPSDjFcnYsam+ixnfyzGBs 414jEcZEt0NQ2+2+ZIfud7b8q7ytgN62oFlUuoKwP/ZAwF7dj4e2fEKGHr+oQZFFN/ ZPCXUkj8+l6KPEV+jg3GxjgLeE+EpKLXZe6Se0aYp/4mGHhs2g+Dww4poFgeljIarC NRynAaurtAldrMJUFCUGvzKPxvccTVx1p++7FGFQVykvCNQZKYyKC4ctspw/WYGdSy fzaFCByPuzFByncyjKv8P+6pnKF6SyFWRyMnEoke4T24kwoXfBXrWAEfVhQ8rSY5CN s7HpZFktNrTVg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 49D0bt35xbz9rxT for ; Fri, 1 May 2020 07:07:06 +0200 (CEST) Date: Fri, 1 May 2020 07:07:05 +0200 From: tuxic@posteo.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Trouble with backup harddisks Message-ID: <20200501050705.cu3adpnkdaauqhdq@solfire> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <20200430093217.efprkpt4kbvir7nr@solfire> <5EAAA0AB.3050505@youngman.org.uk> <22faa7cf-7291-b430-c646-b96c6d428f19@alyf.net> <20200430180839.iz4kxipst2i5stwp@solfire> <20200430192713.ptlo7crtwvskse7n@nabokov.fritz.box> <34ab0115-9336-ad41-5d30-7c8ce6ff1210@alyf.net> <20200430204754.hyh2xzeovsj23xdl@nabokov.fritz.box> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200430204754.hyh2xzeovsj23xdl@nabokov.fritz.box> X-Archives-Salt: dc6dcde7-cdd6-43d0-a758-528c9cf474d7 X-Archives-Hash: de250aca54f49990b20ec84719eedbc9 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