On Mon, 14 May 2007, Joachim Schipper wrote:

> > We have done a low level disk format using an ultimate
> > boot cd.  Didn't output any errors.  Did this on both
> > drives in the system.  Took a very long time.
> > 
> > Then, tried to install the OS.  Received a panic on
> > installing the comp set, ffs_valloc dup alloc.
> > Reconfigured to have all install go to one drive.
> > Same error, different inode.  Tried all on other drive,
> > same error, different inode.  Kept trying it over and
> > over.  Always panicked on comp set.  Always same error
> > of ffs_valloc dup alloc.  Always a different inode.
> > 
> > I am unable to copy in the actual error.  I just have
> > this on a monitor in the room.  No console capability.
> > 
> > Same dmesg as before in this thread.  I can post again
> > if needed.
> > 
> > My question is, to debug this, or fix it, do I need
> > to start swapping out cables, hard disks, motherboard,
> > etc?  Any hints or suggestions are appreciated.
> 
> Running memtest86 is pretty painless, so that's usually a good first
> step.

Already done that.  No errors.
See previous thread, subject 'openbsd 4.0 server, new setup,
getting panics', dated 5/1-5/3.

JohnM

-- 
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services

Reply via email to