🚀 go-pugleaf

	When I inserted the optical disk in, a panel would
come up telling me that the disk needs repair and asked 
me whether I would like to repair, initialize, or ignore it.
When I click on repair, the OD drive will spin up and down 
several times and then tell me that it can't repair.

	So I start reading the manuals.  I used fsck
interactively and with the -y option several times
with this optical disk.  the following is a transcript
produced by the various fsck commands.  It is consistently
reproducible.

cube# fsck -y /dev/rod0a

** /dev/rod0a

** Last Mounted on /benson2

** Phase 1 - Check Blocks and Sizes



CANNOT READ: BLK 205200

CONTINUE?  yes



THE FOLLOWING SECTORS COULD NOT BE READ: 205204,



CANNOT READ: BLK 218168

CONTINUE?  yes



THE FOLLOWING SECTORS COULD NOT BE READ: 218172,



CANNOT READ: BLK 218264

CONTINUE?  yes



THE FOLLOWING SECTORS COULD NOT BE READ: 218268,

** Phase 2 - Check Pathnames



CANNOT READ: BLK 187952

CONTINUE?  yes



THE FOLLOWING SECTORS COULD NOT BE READ: 187956,

** Phase 3 - Check Connectivity

** Phase 4 - Check Reference Counts

** Phase 5 - Check Cyl groups

BLK(S) MISSING IN BIT MAPS

SALVAGE?  yes





CANNOT WRITE: BLK 205432

CONTINUE?  yes



THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 205432, 205433,

2128 files, 200055 used, 33011 free (1299 frags, 3964 blocks, 0.6% fragmentation

)

File system not may not be clean!  Run fsck again to clean.


From the above transcript, I know that some sectors are just
not recoverable since they can't be read or written.
However, even after I ran fsck, the system still won't recognize
this optical disk.  

	I would appreciate any advice at this point.  Is there
any unix utilities out there that will recover files for you
like the Norton Utilities for the Mac or PC?  This is one program
I would be willing to shell out top $$$ for.  

	Best regards,

	Benson Wu
	bmwu@athena.mit.edu
	(No NeXTMail please)