On Mon, 11 Nov 1996, Boris Boesler wrote:

> It happend again:

Hmm, it happens to me all the time... I've got used to it.
 
> ffs_update: bad indirect add(1): inode=98124 4194304/00400000
> ip=f14dd500 adr=f14dd5b0
> 
> inode vp: type VBLK, usecount 664, writecnt 0, refcount 27.
> tag VT_UFS: no 98 on dev 24 , 0
> ffs_update: bad indirect addr patched inode=98124
>
> Last time this happened the bootblock was gone with the wind
> and I had to reinstall BSD. I don't want to do this again !!

Try using fsck, see if it reports any probs on the disk.

hmm, normally I just find that my superblock salvage area is wrong on
/usr, but that seems to be permanent even after fsck, it reappears after
rebooting.
 
It occured normally when I was compiling something, and logged in on
another console window, I don't have X installed.  When did it happen to
you?

> The RPC's hardware:
> 20+2MB, connect32+cfp1080s, kernel #4626, 1.2-beta sets

I did have:
  12+1MB, internal IDE, kernal was the latest one, 1.2-beta sets.

I've yet got to test it on my new system:
  24+1Mb, internal IDE (hope to add rapIDE soon), and present SA kernal.

How is the RapIDE support going?  If you need a tester let me know, I
should have the card, and new HD soon :)


cheers,

Chris Gilbert