Welcome, Guest. Please login or register.

Author Topic: SFS problem  (Read 1019 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline FramigaTopic starter

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 4096
    • Show only replies by Framiga
SFS problem
« on: June 01, 2004, 02:59:44 PM »
Hi All,

yesterday i've lost a SFS 1.214 partition (2 GB).

With SFSSalv, i can see and restore quite all but i haven't ATM, enough free space, to make a full restore.

SFSCheck give me:

Partition start offset : 0x00000001:7a0fc000   End offset : 0x00000001:f7f82000
Surfaces         : 16      Blocks/Track  : 63
Bytes/Block      : 512     Sectors/Block : 1
Total blocks     : 4125744
Device interface : NSD (64-bit)

Checking RootBlocks
...okay
Checking AdminSpaceContainers at block 2
Block 5 is not a valid admin block but it is marked in use in AdminSpaceContainer at 2
Dump of first 64 bytes of block 5.
0x0000: 54524f4b bbadb0af 00000005 00000000 TROK»­°¯@@@E@@@@
0x0010: 00000000 00000000 00000000 00000000 @@@@@@@@@@@@@@@@
0x0020: 00000000 00000000 00000000 00000000 @@@@@@@@@@@@@@@@
0x0030: 00000000 00000000 00000000 00000000 @@@@@@@@@@@@@@@@
...damaged


I've noticed in the SFS archive a tool named "DumpBlock"

DumpBlock ?
DEVICE=DRIVE/A,BLOCK/N/A

Someone knows what's those tool is for?

Cheers
 

Offline Thomas

Re: SFS problem
« Reply #1 on: June 02, 2004, 11:32:21 AM »

The name suggests that it will read a block from disk and give you a hex dump of the contents. Just like above starting 0x0000: 54524f4b...

Bye,
Thomas

Offline FramigaTopic starter

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 4096
    • Show only replies by Framiga
Re: SFS problem
« Reply #2 on: June 02, 2004, 01:44:31 PM »
Hi Thomas,

so the damage is at block 5:

DumpBlock DEVICE=DATA: 5
Device is a new style device (NSD)
Device supports 64-bit commands
Dump of block 5.
0x0000: 54524f4b bbadb0af 00000005 00000000 TROK»­°¯

No way to fix it? (jump, shot . . .)

Cheers