Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!howland.reston.ans.net!ira.uka.de!news.dfn.de!rrz.uni-koeln.de!unidui!du9ds4!prang
From: prang@du9ds4.fb9dv.uni-duisburg.de (Juergen Prang)
Newsgroups: comp.os.386bsd.bugs
Subject: [NetBSD] Fine installation, NO base system boot (fsck failed)
Date: 26 Apr 93 12:05:49 GMT
Organization: Universitaet Duisburg GH
Lines: 66
Message-ID: <prang.735825949@du9ds4>
NNTP-Posting-Host: du9ds4.fb9dv.uni-duisburg.de
After some reinstallation sequences (thanks cgd & friends for this
installation procedure) I ran out of ideas to bring my completely
installed base system beyond the filesystem check. Every time it
aborts, but with different messages (mostly because of unexpected
inconsistencies in the filesystem on my /usr partition, but reporting
different signals (27, 26 and 11) each time, sometimes I did not even
see an output of fsck). I previously ran 386BSD 0.1.2.1 without problems.
Facts:
Hardware:
386SX-25, AMI BIOS (7/7/91), 4MB, no 387,
Conner CP3544 IDE HD (1053Cyl, 16Trk, 63 Sec),
ET4000 SVGA
DOS on the 1st partition (cyl 0-400)
BSD on the 2nd partition (cyl 401-1052)
Following the installation guidelines, everything works fine.
(Some minor inconsistencies I observed were:
- the mount point has to be usr (not /usr) for the install program
- disklabel shows type: ST506 (may be correct for IDE)
disk: *the label I gave my disk during install* !
label: (nothing) !
rest is the same as under 386BSD, except another
BSD partitioning and a blocksize of 4096 instead
of 8192 as under 386BSD)
With 386BSD I only had a swap partition of 61488 sectors and a large
root partition (the rest of 594720 sectors). Now I have a root partition
(14112 sectors), swap (61488) and usr (580208), each starting on cylinder
boundaries.
After extraction of the base system, the final reboot aborts each time
during the filesystem check. I observed nearly all possible problems
during this phase
- no problem checking /, aborts with unexpected inconsistencies in usr
(signals 27, 26, and 11). Manual fsck aborts with the same message
during phase 1 or with a Bus error or with a Memory fault.
- aborts before successful end of root check with symptoms like above. The
filesystem check during installation before copying the kernel worked fine.
- aborts without any message from fsck seen.
Next I tried the former partitioning scheme (594720 for /, 61488 for swap).
Now it was impossible to install the kernel during installation because fsck
failed with either 'profiling alarm' or 'bus error'.
At last I booted the 386BSD-pk0.2 fixit disk and used its fsck.
After reporting and salvaging some inconsistencies a second fsck ran
successfully. Now booting NetBSD kernel copy disk resulted in the same
symptoms as above !
Any hints what to do or what may be wrong ?
A problem in fsck ?
A problem with my hardware ? (but whole installation procedure works fine!)
A problem with my disk ? (but a HD readcheck with a DOS based utility up to
cylinder 1023 reported no problems!)
Thanx,
Juergen
--
Juergen Prang | prang@du9ds4.fb9dv.uni-duisburg.de
University of Duisburg |********************************************
Electrical Engineering | Logic is a systematic method of coming
Dept. of Dataprocessing | to the wrong conclusion with confidence