Message-ID: <691cdb96@news.ausics.net> From: not@telling.you.invalid (Computer Nerd Kev) Subject: Re: Taming The Data Destroyer Newsgroups: comp.os.linux.misc References: <10fe1ec$ipc8$1@dont-email.me> <87a50k5yt3.fsf@atr2.ath.cx> <691b8e3b@news.ausics.net> <691c12b7@news.ausics.net> <10fh6jl$1cvaf$1@dont-email.me> <10fh9it$1dmda$1@dont-email.me> <61luulxffm.ln2@Telcontar.valinor> <10fihq5$1p41c$6@dont-email.me> User-Agent: tin/2.6.5-20250707 ("Helmsdale") (Linux/2.4.31 (i586)) NNTP-Posting-Host: news.ausics.net Date: 19 Nov 2025 06:48:22 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 24 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:77731 Lawrence D'Oliveiro wrote: > On Tue, 18 Nov 2025 17:55:34 +0100, Carlos E.R. wrote: >> fdisk -l /dev/disk/by-id/$DISKID > $DISKNAME-partition_table_fdisk.out > > This does display actual sector numbers (along with rounded total > sizes), but I don't think this is a useful format for restoration. In the real world the replacement drive after one has died often isn't exactly the same size as the last one so I want to read the former partition layout manually then manually create something like it on the new drive, but with sizes adjusted to suit. >> dd if=/dev/disk/by-id/$DISKID of=$DISKNAME-mbr count=1 > > This I wouldn't bother with. Why? Because restoring it will wipe out > your bootloader. It should restore your bootloader, although if you've fiddled with the partitions on the new drive then that bootloader might not work anymore. -- __ __ #_ < |\| |< _#