fsck -b

[LinArte]

fsck -y in Single User Mode resultet in the message, that there was a Bad superblock and the magic number was wrong.

The advice followed that this was a case for fsck -b plus a certain number.

Any idea what this is supposed to mean? I heard that the superblock can be found at other places and all I need to know is how to direct the fsck to that spot.

Any ideas or any other suggestions as to how I could recover the data from that - until now - unmountable disk?

[stetner]

The problem is that fsck is expecting a UFS filesystem. An inteligent fsck should really involke fsck_hfs, as your filesystems are most likely HFS(+).

Have your friend try fsck_hfs instead

Doug