Boris Gjenero wrote:
> 

[...]
> They mean that the disklabel is wrong and NetBSD has figured out the
> correct parameters for the drive and is using them instead.  It seems
to
> me that you are labeling the drive with the standard MSCP RD53 label. 

You were right of course.

> You shouldn't be, because the VS2000 MFM controller isn't MSCP and it
> wants the physical geometry.  Here are the
> specifications: (look at the 1325 column)

Yup, no strange messages now.

[...]
> I didn't see any message that indicates that the drive isn't okay. 
> However, it'd better not have any bad sectors, or you will have
problems
> because there is no bad sector remapping.  Look out for messages like:
> Command 0xNN completed with result code 0xNN

Argh:


# newfs /dev/rrd0g
command 0xa0 completed with status 0x30
Warning: 92 sector(s) in last cylinder unallocated
/dev/rrd0g:     89940 sectors in 662 cylinders of 8 tracks, 17 sectors
        43.9MB in 42 cyl groups (16 c/g, 1.06MB/g, 512 i/g)
....


> Any such messages (besides those at startup which happen once for each
> non-existant drive during the probe) are bad... you are getting data
> corruption.

[...]
> Hmm... I wouldn't give up hope that easily.  It could just be
stiction. 
> Even if it is electronics, it may be something that is easily
> repairable. 

Right again. It was stiction. Hybelvax lives again! ;-)

Thanks!

Gunnar

--
Gunnar Helliesen   | Bergen IT Consult AS  | NetBSD/VAX on a uVAX II
Systems Consultant | Bergen, Norway        | '86 Jaguar Sovereign 4.2
gunnar@bitcon.no   | http://www.bitcon.no/ | '73 Mercedes 280 (240D)