cgsecurity.org

I have a 6TB seagate back up hub that doesn't mount anymore.
No apparent reason.
In disk utility it shows the disk and also the partition with the correct name but greyed out.
Diskutil volume repair says:
Bestandssysteem herstellen.
Het volume is al gedeactiveerd.
fsck_hfs -fy -x /dev/rdisk3s1 uitvoeren
Eindcode bestandssysteem is 8.
De oorspronkelijke status wordt teruggezet naar gedeactiveerd.
Controle of herstel van bestandssysteem mislukt. : (-69845)

Testdisk sees het hfs Partition.
Running deep search now on rdisk3s1 but after 3 days it's only 22 % scanned.
Questions
1) Is it normal or worth it to have the deapscan going until 100 %, how long will it take.
2) Can I repair the disk to mount again after the deep scan? And how?
Need the data.

Thanks for useful advise...

Koekes wrote: ↑16 Jan 2021, 09:53 I have a 6TB seagate back up hub that doesn't mount anymore.
No apparent reason.
In disk utility it shows the disk and also the partition with the correct name but greyed out.
Diskutil volume repair says:
Bestandssysteem herstellen.
Het volume is al gedeactiveerd.
fsck_hfs -fy -x /dev/rdisk3s1 uitvoeren
Eindcode bestandssysteem is 8.
De oorspronkelijke status wordt teruggezet naar gedeactiveerd.
Controle of herstel van bestandssysteem mislukt. : (-69845)

Testdisk sees het hfs Partition.
Running deep search now on rdisk3s1 but after 3 days it's only 22 % scanned.
Questions
1) Is it normal or worth it to have the deapscan going until 100 %, how long will it take.

If there are no errors on your disk(s) according on your information given the total search time will be 3/0,22 =13,64 days.
After 3 days there will be 10,64 days left. Your information translates into roughly 5 Mbytes/second which is way below native continuous linear transfer speed. Something seems to be wrong.

2) Can I repair the disk to mount again after the deep scan? And how?

Unfortunately my crystal bal left for two weeks in Corona quarantine. Honestly I can never answer this question.

Need the data.

For higher recovery speed you might contact a professional recovery company.

The deep search is now at 36 % so yes, 13,64 days is logic.

But maybe I should refrase the question.
If we forget about the deep search and go with the information
we get running fsck_hfs -fy -x /dev/rdisk3s
Endcode 8
and sysytem check and repair failed: -69845

What can I do to mount the disk again using Testdisk, without reformatting it?

Sorry, can't help you with Apple computers.