Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!soma!concurrent-request
From: skivs!jmm@uunet.uu.net (Joel M. Miller)
Newsgroups: comp.sys.concurrent
Subject: Help me edit my superblock
Message-ID: <2488@gazette.bcm.tmc.edu>
Date: 1 Nov 90 02:27:46 GMT
Sender: usenet@bcm.tmc.edu
Reply-To: ski!jmm@uunet.UU.NET (Joel M. Miller)
Organization: Smith-Kettlewell Eye Research Institute, San Francisco, CA
Lines: 17
Approved: concurrent@soma.neusc.bcm.tmc.edu
Nntp-Posting-Host: cortex.neusc.bcm.tmc.edu


I have a somewhat scrambled Fujitsu-330 disk on an MC-5500/RTU-3.1,
which I want to mount in order to save what data I can.  However, "mount"
complains about a bad superblock and won't mount the disk.

Does anyone know what sanity checks "mount" makes, or perhaps more
importantly, which superblock fields are important to fix with "fsdb"
before trying to mount and read this disk?
-- 
Joel M Miller                    Internet: jmm@skivs.ski.org
Smith-Kettlewell Institute       Usenet:   fernwood!skivs!jmm
2232 Webster St                  Bitnet:   jmm%skivs.ski.org@fernwood.mpk.ca.us
San Francisco, CA 94115          Voice:    415/561-1703     Fax: 415/561-1610

Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent
Administrative stuff: concurrent-request@soma.bcm.tmc.edu
Stan Barber, Moderator