| 1 |
On 04/30 08:32, antlists wrote: |
| 2 |
> On 30/04/2020 18:04, tuxic@××××××.de wrote: |
| 3 |
> > I copied the first 230GB of that disk to an empty partition of my new |
| 4 |
> > system and run "testdisk" on it....after the analysis it came back |
| 5 |
> > with "this partition cannot be recovered" but did not sau. whether the |
| 6 |
> > reason is a partition table, which is broken beyond repair, or simply |
| 7 |
> > due to the incomplete image file... |
| 8 |
> |
| 9 |
> Just come up with another idea that will hopefully give us some clues... |
| 10 |
> |
| 11 |
> https://raid.wiki.kernel.org/index.php/Asking_for_help#lsdrv |
| 12 |
> |
| 13 |
> Ignore the fact that it's the raid wiki - this tool basically delves into |
| 14 |
> the drive and tries to find mbr, gpt, superblock, lvm and raid signatures, |
| 15 |
> everything ... |
| 16 |
> |
| 17 |
> So run that and see what it tells us ... |
| 18 |
> |
| 19 |
> Cheers, |
| 20 |
> Wol |
| 21 |
> |
| 22 |
|
| 23 |
Hi Wol, |
| 24 |
|
| 25 |
thank you for the link! I have installed mdadm (its on portage) but I |
| 26 |
have not used it, since there is another soultion for this, which I |
| 27 |
tried first. |
| 28 |
|
| 29 |
Andrea posted this wonderful line: |
| 30 |
|
| 31 |
mount -o ro,offset=512 /dev/sdb /mnt/xxx |
| 32 |
|
| 33 |
which mounts the filesystem by skipping the partitiontable completly. |
| 34 |
|
| 35 |
Currently I am rescueing the data. If all is safed, I will tru |
| 36 |
mdadm... |
| 37 |
|
| 38 |
Thank you very much for your help! |
| 39 |
|
| 40 |
As soon as there are more information, I will report back. |
| 41 |
Maybe this can also help others with similiar problems. |
| 42 |
|
| 43 |
Cheers! |
| 44 |
Meino |
Archives