From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trouble with backup harddisks
Date: Fri, 1 May 2020 03:59:19 +0200 [thread overview]
Message-ID: <20200501015919.iy5q267vfbwyslz4@solfire> (raw)
In-Reply-To: <04005ef6-698f-e1de-139a-a87c8d92b151@youngman.org.uk>
On 04/30 08:32, antlists wrote:
> On 30/04/2020 18:04, tuxic@posteo.de wrote:
> > I copied the first 230GB of that disk to an empty partition of my new
> > system and run "testdisk" on it....after the analysis it came back
> > with "this partition cannot be recovered" but did not sau. whether the
> > reason is a partition table, which is broken beyond repair, or simply
> > due to the incomplete image file...
>
> Just come up with another idea that will hopefully give us some clues...
>
> https://raid.wiki.kernel.org/index.php/Asking_for_help#lsdrv
>
> Ignore the fact that it's the raid wiki - this tool basically delves into
> the drive and tries to find mbr, gpt, superblock, lvm and raid signatures,
> everything ...
>
> So run that and see what it tells us ...
>
> Cheers,
> Wol
>
Hi Wol,
thank you for the link! I have installed mdadm (its on portage) but I
have not used it, since there is another soultion for this, which I
tried first.
Andrea posted this wonderful line:
mount -o ro,offset=512 /dev/sdb /mnt/xxx
which mounts the filesystem by skipping the partitiontable completly.
Currently I am rescueing the data. If all is safed, I will tru
mdadm...
Thank you very much for your help!
As soon as there are more information, I will report back.
Maybe this can also help others with similiar problems.
Cheers!
Meino
next prev parent reply other threads:[~2020-05-01 1:59 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 [this message]
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
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=20200501015919.iy5q267vfbwyslz4@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