Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!solace!nntp.uio.no!news.cais.net!bofh.dot!news.mathworks.com!uunet!in2.uu.net!not-for-mail From: kyle@uunet.uu.net (Kyle Jones) Newsgroups: comp.sys.mac.hardware.storage,comp.sys.ibm.pc.hardware.storage,comp.unix.bsd.misc Subject: Re: what are the reserved sectors on 1GB Jaz disks Date: 14 May 1996 13:57:42 -0400 Organization: UUNET Technologies Inc, Falls Church VA USA Lines: 29 Message-ID: <4nahim$qin@wendy-fate.uu.net> References: <4n8ges$ou9@wendy-fate.uu.net> <MMEAD.96May14114259@Glock.COM> NNTP-Posting-Host: wendy-fate.uu.net Xref: euryale.cc.adfa.oz.au comp.sys.mac.hardware.storage:13431 comp.sys.ibm.pc.hardware.storage:59823 comp.unix.bsd.misc:1048 matthew c. mead <mmead@Glock.COM> wrote: > kyle@uunet.uu.net (Kyle Jones) writes: > > > Anyone know which sectors on a Jaz disk need to be left alone in > > order to avoid erasing geometry information that the drive > > (apparently) needs to recognize the disk? I think this is the > > reason why my drive suddenly stopped recognizing a disk after I > > put a UNIX filesystem on it and then ejected the disk. When I > > send a SCSI test unit ready command I get back "incompatible > > medium installed" (asc 30h, ascq 92h). The access light blinks > > for a while but the drive doesn't spin up. > > Whoa. I haven't seen this, and I've walked *all* over my JAZ > disks with FreeBSD. If the data doesn't need to be recovered, I'd try > lowlevel formatting it and starting over. What operating system and > version did you use to put the filesystem on it? BSD/OS 2.0. I'm now think the drive has died. I've tried three brand new disks: two give the above error and the third gives "not ready, manual intervention required". None of them even spin up, so formatting is out of the question. No matter, I only got as far as putting an empty filesystem on the disk before the drive stopped working. Thanks for the response. At least now I know that scragging the FDISK partition, boot blocks and other stuff at the beginning of the disk should not make the disk unusable. (Information, I note grimly, that I was not able to obtain from Iomega tech support after a 45 minute phone wait. :-( )