Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!news.cs.indiana.edu!usenet.ucs.indiana.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!usenet From: cs101f87@eng-nxt05.cso.uiuc.edu (cs101 student) Subject: [386BSD] Problems with patched kernel, etc. Message-ID: <BwHpJt.3uK@news.cso.uiuc.edu> Sender: usenet@news.cso.uiuc.edu (Net Noise owner) Organization: University of Illinois at Urbana Date: Wed, 21 Oct 1992 21:11:50 GMT Lines: 74 Greetings to all fellow netters and BSDers... I have a couple questions relating to the patched kernel (Beta-1), as well as a couple questions about the pre-patchkit kernel. (1) I am running 386BSD off a Maxtor XT-8760E ESDI drive, which should support BAD144-style sector formatting, but when I use the install program off the TinyBSD disk (pre-patchkit), the disklabel that is written is missing the badsect flag. However, things seem to work pretty well. Now, if I decide to get ambitious, and disklabel the drive myself, with the "badsect" flag set, I run into problems.... I start getting files being corrupted, etc... Why is this, and should I just install without the badsect flag set [as install did]. Please explain the reasoning behind any answer you give me. More details on my disk sub-system: (a) WD-1007V ESDI controller with alternate sector mapping enabled (b) XT-8760E primary drive [1630 cyls, 15 heads, 53 sectors mapped to 1630/15/52 because of bad sector mapping] (c) XT-4380E secondary drive [1222 cyls, 15 heads, 35 sectors translated to 618/16/63 because of drive translation and bad sector mapping] 386BSD is installed in a partition on the primary drive... The second drive is reserved for DOS exclusively, therefore the translation should NOT play a role in anything. (2) After re-installing the system off a floppy running the patched kernel, NEWFS would report a "Cannot write to sector 537616, wtfs: I/O error", and would stop formatting my partition. I did this to fix it, but got the same results: bad144 wd0 0 bad144 -a wd0 537616 After trying to newfs the partition again, I got this same exact error. First, I think that NEWFS should be smart enough to do its own bad-sector handling, but barring that, at least BAD144 should work. This install was done using the "install" program on the TinyBSD install floppy with patched kernel. The drive WAS disklabel'ed to support bad-sector mapping. (3) After partitioning my drive so that the bad sector was in my "h" partition, I could NEWFS the "a" partition fine, and the install did not complain about anything. However, when I rebooted off the hard drive, my kernel would load, display all my configured devices, and then go into an endless drive-read loop. Thinking that the patched "init" could be the problem, I booted up off the TinyBSD floppy [with patched kernel and patched init], and re-installed the OLD UN-patched "init". The result was, that on my next hard-drive reboot, the kernel would load up, and display my system configuration, and then stop [NO drive access this time] I know that this must have been hell to read, but I have now re-installed 386BSD at least 6 times on the same machine [because of different reasons, some being my fault...], and that WAS hell, especially when it didn't work.... Any clues greatly appreciated... I would like to get some info, so that I can decide whether to re-install the pre-patchkit BSD, or whether there are some other problems that could be showing here [hardware, etc...]. Thanks, Rafal Boni -------------------------------------------------------------------------- Rafal Boni r-boni@uiuc.edu "Me have a .sig?? I don't even have a clue!" rkb55989@uxa.cso.uiuc.edu -Anonymous cs101f87@sumter.cso.uiuc.edu --------------------------------------------------------------------------