> Does this indicate I have a bad drive?  Or, does it
> just need fsck run on it?  I just installed openbsd 4.0
> on this box a few days ago.  It rebuilt the file systems
> from scratch.  Do I need to redo everything?
> 
> Or, do I need to start looking at hardware problems with
> the drive or the motherboard?
> 
> Please let me know the next step to run that will help
> me get to a stable system.

I tried viewing the file in error.  I could run ls, but
not ls -l.
I went into single user mode and fscked the file system.
I removed the file.  I did not get the inode or anything else
before removing it.

I tried running the copy source command.
  cd /usr/src; tar xzf /mnt/src.tar.gz
Another panic.

panic #3:
-----
mode = 0100644, inum = 106368, fs = /usr
panic: ffs_valloc: dup alloc
Stopped at      Debugger+0x4:   leave   
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb>
Debugger(d0716864,5080,e9e21b40,d6bb671c,d1265000) at Debugger+0x4
panic(d06736fc,81a4,19f80,d12650d4,d1267e00) at panic+0x63
ffs_inode_alloc(d6ab69dc,81a4,d6c141e0,e9e21b94) at ffs_inode_alloc+0x11b
ufs_makeinode(81a4,d6ab8ea0,e9e21e28,e9e21e3c) at ufs_makeinode+0x78
ufs_create(e9e21d08,d6ab8ea0,d6b33710,d6c141e0,d07171c0) at ufs_create+0x26
VOP_CREATE(d6ab8ea0,e9e21e28,e9e21e3c,e9e21d58) at VOP_CREATE+0x34
vn_open(e9e21e18,e02,1a4,d6b33710) at vn_open+0xdf
sys_open(d6b33710,e9e21f68,e9e21f58,0,0) at sys_open+0xdb
syscall() at syscall+0x2ea
--- syscall (number 5) ---
0x1c00e3e1:
ddb>
   PID   PPID   PGRP    UID  S       FLAGS  WAIT       COMMAND         
 15475  20392  20392      0  3      0x4086  pipewr     gzip            
*20392   2075  20392      0  7      0x4006             tar             
 20997  15943  20997   1000  3      0x4086  ttyin      csh             
 15943   9609   9609   1000  3       0x184  select     sshd            
  9609  14206   9609      0  3      0x4084  netio      sshd            
 14658      1  14658      0  3      0x4086  ttyin      getty           
  4737      1   4737      0  3      0x4086  ttyin      getty           
 13556      1  13556      0  3      0x4086  ttyin      getty           
 30631      1  30631      0  3      0x4086  ttyin      getty           
  2075      1   2075   1000  3      0x4086  pause      csh             
  6223      1   6223      0  3        0x84  select     cron            
 14206      1  14206      0  3        0x84  select     sshd            
 14369  24346  24346     83  3       0x184  poll       ntpd            
 24346      1  24346      0  3        0x84  poll       ntpd            
  1115   7685   7685     73  2       0x184             syslogd         
  7685      1   7685      0  3        0x8c  netio      syslogd         
    13      0      0      0  3    0x100204  crypto_wa  crypto          
    12      0      0      0  3    0x100204  aiodoned   aiodoned        
    11      0      0      0  3    0x100204  syncer     update          
    10      0      0      0  3    0x100204  cleaner    cleaner         
     9      0      0      0  3    0x100204  reaper     reaper          
     8      0      0      0  3    0x100204  pgdaemon   pagedaemon      
     7      0      0      0  3    0x100204  pftm       pfpurge         
     6      0      0      0  3    0x100204  wait       wskbd_hotkey    
     5      0      0      0  3    0x100204  usbtsk     usbtask         
     4      0      0      0  3    0x100204  usbevt     usb0            
     3      0      0      0  3    0x100204  apmev      apm0            
     2      0      0      0  3    0x100204  kmalloc    kmthread        
     1      0      1      0  3      0x4084  wait       init            
     0     -1      0      0  3     0x80204  scheduler  swapper         
ddb>
-----

So, back to my real question.
Does this indicate a bad drive?
Does this indicate a bad cable?
Do I need to start swapping out parts to see where the problem is?
Or, is there somewhere else I should be looking?

Thanks in advance for any pointers.

JohnM





> panic #1:
> -----
> panic: kernel diagnostic assertion "(dirblock < dh->dh_nblk &&
> dh->dh_blkfree[dirblock] >= (((slotneeded) + ((4) - 1)) / (4)))" failed: file
> "/usr/src/sys/ufs/ufs/ufs_dirhash.c", line 510

> panic #2:
> -----
> panic: ufsdirhash_findslot: 'crash66.C' not found

> dmesg:
> -----
> OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
>     [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD Duron(tm) Processor ("AuthenticAMD" 686-class, 64KB L2 cache) 1.21
> GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,S
> SE
> real mem  = 528052224 (515676K)
> avail mem = 473726976 (462624K)
> using 4256 buffers containing 26505216 bytes (25884K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(00) BIOS, date 02/08/02, BIOS32 rev. 0 @ 0xfdb30,
> SMBIOS rev. 2.3 @ 0xf0630 (24 entries)
> bios0: ECS M821LR
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> apm0: flags 30102 dobusy 0 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf0000/0x10000
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf8860/112 (5 entries)
> pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C686 ISA" rev 0x00)
> pcibios0: PCI bus #1 is the last bus
> bios0: ROM list: 0xc0000/0xc000 0xcc000/0x5800 0xd1800/0x2800
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "VIA VT8361 PCI" rev 0x00
> ppb0 at pci0 dev 1 function 0 "VIA VT8361 AGP" rev 0x00
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "Trident CyberBlade i1" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
> pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel
> 0 configured to compatibility, channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0: <IC35L120AVV207-0>
> wd0: 16-sector PIO, LBA48, 117800MB, 241254720 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
> wd1 at pciide0 channel 1 drive 0: <WDC WD1200JB-00DUA3>
> wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
> atapiscsi0 at pciide0 channel 1 drive 1
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: <CD-ROM, CCD-52X6S, YSG1> SCSI0 5/cdrom
> removable
> wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x16: irq 12
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40
> auvia0 at pci0 dev 7 function 5 "VIA VT82C686 AC97" rev 0x50: irq 10
> ac97: codec id 0x49434511 (ICEnsemble ICE1232)
> ac97: codec features headphone, 18 bit DAC, 18 bit ADC, KS Waves 3D
> audio0 at auvia0
> "VIA VT82C686 Modem" rev 0x30 at pci0 dev 7 function 6 not configured
> rl0 at pci0 dev 10 function 0 "Realtek 8139" rev 0x10: irq 12, address
> 00:e0:06:f6:bf:3e
> rlphy0 at rl0 phy 0: RTL internal PHY
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0: <PC speaker>
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> biomask fb6d netmask fb6d ttymask fbef
> pctr: user-level cycle counter enabled
> mtrr: Pentium Pro MTRR support
> dkcsum: wd0 matches BIOS drive 0x80
> dkcsum: wd1 matches BIOS drive 0x81
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
> WARNING: / was not properly unmounted
> -----

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

Reply via email to