Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: No disks found Date: 8 Jun 1995 09:37:37 GMT Organization: University of California, Berkeley Lines: 36 Message-ID: <3r6gd1$1rd@agate.berkeley.edu> References: <3r609i$7e5@news.bu.edu> NNTP-Posting-Host: violet.berkeley.edu In article <3r609i$7e5@news.bu.edu>, Mikhail Teterin <mi@cs.bu.edu> wrote: >Install, however, told me, that installation was succesfull, and I >rebooted (I did remove the boot-floppy first). Both of my harddrives were >probed correctly. Then Install menu came up again. I was surprised by >that and went to check out the partitions again: "No disks found", was a "Eek" I'm afraid that sysinstall is only meant to be run in single-user mode when you're using it to play with disks after installation. Yes, it's not right, but the current probing expects that anything it can open is there, and otherwise not. There are some flaws to this technique, the first 2 of which are at least documented in the installation guide: 1. If a CDROM isn't in the drive at sysinstall time, it doesn't see it as there. 2. If a tape isn't in the drive, same thing. 3. If a disk has things mounted on it then the open will fail and it will treat the error the same way. For now, I really recommend treating sysinstall as a "one shot" for installing the system and not for post-install configuration. This WILL be fixed for 2.1, I just need to go to a totally different kernel device discovery method and that's going to take a little time.. :( As to your other problems, I'm not sure. Does it still happen if you disable your cache? If so, I suspect misconfiguration or bad cache/DMA invalidation on your motherboard. Jordan