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 A8EA7138350 for ; Fri, 1 May 2020 10:27:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 875C6E0CA2; Fri, 1 May 2020 10:27:22 +0000 (UTC) Received: from coleridge.oriole.systems (coleridge.oriole.systems [IPv6:2a00:1828:2000:35::dece:a5ed]) (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 2B4AFE0C5A for ; Fri, 1 May 2020 10:27:21 +0000 (UTC) Date: Fri, 1 May 2020 12:27:15 +0200 From: Wynn Wolf Arbor To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Trouble with backup harddisks Message-ID: <20200501102715.hoqaitsxvudhkqsm@nabokov.fritz.box> Mail-Followup-To: Wynn Wolf Arbor , 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> <20200501050705.cu3adpnkdaauqhdq@solfire> <180730dc-e061-e168-bc0f-3839497338ce@alyf.net> <20200501071810.h6qs7kgewwtbytqd@solfire> 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=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <20200501071810.h6qs7kgewwtbytqd@solfire> X-Archives-Salt: 247db6bd-236b-4996-8bbe-c1815705d1b4 X-Archives-Hash: a1db75b3c356abc3b0f41b21df498187 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