Hi.
My MOS partition became corrupted for the first time since i started to use it. It boots but when the Ambient screen opens, nothing happens when i click to icons.
So, i re-installed MOS with SFSDoctor v1.1 on another partition and i'm trying to repair the damaged one.
I start SFSDoctor, select "Check disk" and here is the log:

--------- START
Welcome to SFSDoctor - The Disk Recovery and Repair Suite
---
[22:34:49] Checking drive DH3:
[22:34:49] Checking root blocks
[22:34:49] Okay
[22:34:50] Checking admin space containers
[22:34:52] Okay
[22:34:52] Checking node containers
[22:34:52] Error: container at block 1755 doesn't contain node 17 (nc 26)
[22:34:52] Error: container at block 1755 doesn't contain node 112 (nc 574)
[22:34:52] Error: container at block 1755 doesn't contain node 126 (nc 574)
[22:34:52] Error: container at block 911 doesn't contain node 1452 (nc 1756)
[22:34:52] Error: container at block 911 doesn't contain node 2088 (nc 1234)
[22:34:52] Error: container at block 911 doesn't contain node 2342 (nc 1284)
[22:34:52] Error: container at block 911 doesn't contain node 2350 (nc 1284)
[22:34:52] Error: container at block 910 doesn't contain node 2351 (nc 1284)
[22:34:52] Error: container at block 910 doesn't contain node 2352 (nc 1284)
[22:34:52] There are errors in filesystem structure. It is advised to backup data and repair this partition
---
[22:35:11] Saving activity log to file Gift:check.log
------------- END

"... repair this partition"? Where is the repair option? I suppose it's the "scan disk" option?
I click on the "scan disk", but it starts to display some messages and then SFSDoctor quits itself!! No time to save the log or anything! It just quits like if i pressed the close gadget.
Bummer.. I need some help.

** EDIT **
I just remembered that "scan disk" always used to self-quit or even hang even when i was trying to scan a good partition for testing purposes.


[ Edited by AmigaMancer on 2007/7/30 1:36 ]

And here is what SFSCheck says:
Quote:

I suggest you to try to contact with March (author of SFSDoctor). When
this program was in beta stage, I have some problems with it a
few times. March was always helping me immediately. The only problem
is he could be on his holyday now.

Easiest (and maybe the fastest) repair is to back up files to other location and quick format the partition and copy them back :)

Right. But if you don't report the bug, it will still be there. :)
And one time a partition whose size is enough to make some troubles to
back it up could get broken.

@Kamul
Quote:
Good idea. I will send him a PM and see.


@jPV
Quote:
The problem is that the system doesn't let me to copy some of the files from the damaged partition. I suppose that a program like SFSDoctor could be able to repair the partition and make this files accessible again.

Before two months I try repair damaged sfs partition whit SFS Doctor v1.1 but no luck .. aftre this boot OS3.9 and using RDB-Salv...whit this progy copy all files to other partition...and after that qucik format Quote:

Quote:
If I remember correctly, there was some separate "recover lost files" option in sfssalv. To same or different partition. Of course I would recommend "different partition"

Directories, for which location/name is lost, will be put in lost+found.

I have had problems with SFS on MorphOS once, and I managed to rescue lost directories with SFSSalv, but for many of them, the directory name was lost.

@Jupp3
I don't have any lost directories or files. Just some files which are there but i get errors when i try to copy them.
Anyway, your suggestion to use SFSSalv was good! I was able to salvage these files to another partition. Thank you.

hey!

get a new round cable!!! i also got strange errors while copying, and hdd was okay, only the 80line cable was corrupted...

bye, MarK.

I wouldn't say rounded cables are better than the flat ones,
especially in case of little power consuming Pegasos. But, for sure,
it must be a 80 wire cable, and of course not broken one. ;)