Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!network.ucsd.edu!sdd.hp.com!hp-cv!hp-pcd!hpcvmcdj!carlj From: carlj@hpcvmcdj.cv.hp.com (Carl Johnson) Subject: [386BSD] help: init FATAL error Message-ID: <1992Oct20.051614.24998@hpcvmcdj.cv.hp.com> Organization: Hewlett-Packard Company, Corvallis, Oregon USA Date: Tue, 20 Oct 1992 05:16:14 GMT Lines: 32 Does anybody know what would cause an init fatal error in bootup? I have been running my system successfully for about 3 weeks, but when I booted it up today it dies part way through the boot process after identifying all of the devices. So basically my startup looks like this: <identify all of devices> as0: attached tgt 0 <FUJITSU ... etc init FATAL error: console: Interrupted system call The init fatal error message repeats indefinitely, at about 30 second intervals. I have used the fixit disk to fsck the disk, and then mount it and everything looks all right. I checked the disklabel, and it looks all right, but I then re-wrote it with: disklabel -r /dev/ras0a >xx disklabel -R -r /dev/ras0a xx /usr/mdec/asboot /usr/mdec/bootas (at least I think I wrote those last parameters right here) The system still acted the same after that, so the boot section did not appear to be the problem. I also copied the device files from the fixit disk to the hard disk just in case one of them got them screwed up, but still nothing changed. If nobody comes up with any ideas, my next step will be to restore the full backup from tape and see if it works after that, but I am hoping to avoid that. Thanks in advance for any ideas. -- Carl Johnson carlj@cv.hp.com