Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!purdue!sample.eng.ohio-state.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!uunet!mcsun!fuug!funic!news.cs.hut.fi!cs.hut.fi!hsu
From: hsu@cs.hut.fi (Heikki Suonsivu)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD & AHA1542B & CDC94171-9 Disk problem
Message-ID: <HSU.92Jul20100551@laphroaig.cs.hut.fi>
Date: 20 Jul 92 08:05:50 GMT
Article-I.D.: laphroai.HSU.92Jul20100551
References: <1992Jul19.121003.27453@ulrik.uio.no> <14ca62INNhfr@agate.berkeley.edu>
<1992Jul20.011747.10954@ulrik.uio.no>
Sender: usenet@cs.hut.fi (Uutis Ankka)
Organization: Helsinki University of Technology, Finland
Lines: 53
In article <1992Jul20.011747.10954@ulrik.uio.no> toreh@bootes.sds.no (Tore Haraldsen) writes:
>> as0b: controller error 0x16 reading fsbn 0
>> scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Same problem, old (large) adaptek board, ST277N. The rom diagnostics give
errors, so I'm suspecting either my hardware or the controller. What is
weird that before I tried 386BSD, I had been running Mach 2.5 and Mach 3.0
in the same machine, same configuration, and did not have problems with
them. As my system is different, no-name singaporean clone (16MHz, quite
old, 287), it seems to have something to do with the Adaptek controller?
This is what happened with different configurations:
0.0: installed and loaded the files to the hard disk. When I booted from
the hard disk, it worked until I tried to load the files from the floppies,
result was a panic. nonfp and other versions I tried didn't work either.
0.1 (mfm disks): floppy boots, but install says there is 386BSD already
installed and then when I say yes, and it starts the install procedure, I
get disklabel error messages "partition a larger than disk" and similar
messages. Every time the install program is run, it corrupts the disk
label (partitions only, disk geometry of the label is ok). Tried doing the
disk label from the fix floppy, and as long as I didn't do install, it
seemed to work, I could copy stuff to the hard disk and boot it from there,
but then the files in the hard disk were corrupted (some of them, not all).
If I look at the disklabel after running install, it says 3 partitions, but
lists only 2, with all the values as garbage.
If I run bad144, it dumps me lots of sector 0 mapped to sector 0, and then
complains about duplicates (sn 0). How do I write a new, empty bad block
table? The file corruption problems may be because the bad block table is
not correct.
I managed to destroy the disk label so that the install floppy didn't say
"386BSD already installed" but installation failed similarly, error
messages and corrupted disk label.
0.1 (scsi disks): The same problem Tore Haraldsen has got.
The system has also been running Microport 386 unix and msdos with no
problems.
cpio would require find as its companion, copying boot disk to the hard
disk directory-by-directory is a bit weird? Am I missing something? I
guess the install program should do the work, if I could get it running.
-
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND,
hsu@{otax.tky.hut,cs.hut,clinet}.fi +385-0-8031121
/G=Heikki/S=Suonsivu/O=hut/OU=cs/PRMD=Inet/ADMD=Fumail/C=FI,
mcsun!hutcs!hsu, riippu SN, Email preferable.