Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!darkstar.UCSC.EDU!cats.ucsc.edu!buhrow From: buhrow@cats.ucsc.edu (Brian Buhrow) Newsgroups: comp.os.386bsd.questions Subject: HELP WITH NETBSD INSTALLATION ON RLL DISK DRIVE, READ-ONLY FILESYSTEM PROBLEM Date: 7 May 1993 00:28:44 GMT Organization: University of California; Santa Cruz Lines: 46 Distribution: world Message-ID: <1scaftINNqrp@darkstar.UCSC.EDU> NNTP-Posting-Host: hobbes.ucsc.edu Keywords: disk errors, bad144 problems, partitioning, I have been trying to install NetBSD on my computer system. The configuration is as follows: 80386sx with 4MB of memory 1 5.25 1.2MB floppy disk. 1 Micropolis Rll 1325 hard drive with an WD 1006 RLL controller. The geometry of the disk is: 1024 cylinders, 8 heads, 26 sec/track When NetBSD boots up it identifies the serial ports and reports the following on the disk drive. wdc0 at 0x1f0 - 0x1f7 irq 14 on isa wdc0 <KrUsTy DiSk> wd0on wdc0 slave 0 Actually, this is not a verbatim copy of what it puts on the screen, but it is pretty close. When I run the installation script, I tell it I have an St506 drive, 1024 cylinders, 8 heads, 26 sec/track. I say that it does not support automatic bad sector forwarding and then define my partitions. There is a DOS partition of 103584 sectors, the root partition of 8112 sectors, the swap partition of 16016 sectors, the usr partition of 85072 sectors, and the bad144 track of 208 sectors. The installation program then shows me a disktab entry and I approve it. It then asks me if I want to proceed with the installation, and if I want to overwrite the DOS partition table. I say no. It then says that it is initializing bad144 and then bad144 reports that it is trying to write on a read-only file system. Newfs then says that there are bogus superblocks for the / and /usr filesystems and that the bad sector table has been corrupted. I then, for the heck of it, proceed with the verbose installation. After about 20 devices have been installed and tar has complained about read-only filesystems, the system panics and reboots. If you could shed some light on these events, it would be most helpful. Specifically, how do I make bad144 work? Note that I don't have a different machine to use in order to get this one running. I believe the key is in the fact that bad144 cannot initialize its tables. Thank you in advance for any suggestions/hints. -Brian Buhrow <buhrow@nfbcal.org>