On 05/01 03:59, [email protected] wrote:
> On 04/30 08:32, antlists wrote:
> > On 30/04/2020 18:04, [email protected] 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
>
>
>
Hi Wol,
data copied ! :)
I did a
mdadm --examine /dev/sdb
on one of the damaged partitions and this was print
on the console
host:/root>mdadm --examine /dev/sdb
/dev/sdb:
MBR Magic : aa55
Partition[0] : 1953458175 sectors at 1 (type ee)
Cheers!
Meino
