Date: Fri, 08 Oct 1999 15:26:08 -0400 From: Dan Diephouse <dragon.s@ix.netcom.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Compaq Proliant 2500 file corruptions Message-ID: <37FE4550.2492421C@ix.netcom.com> References: <37FE2031.DF16E119@ix.netcom.com> <199910081832.LAA03972@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I brought the computer home with me. Below is some of the system information. I'm still stumped as to what to next...The disklabel all matches up correctly. Anyone have any more ideas? Thanks Again -- Dan Diephouse disklabel wd0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 153600 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 9*) b: 512000 153600 swap # (Cyl. 9*- 41*) c: 16354170 0 unused 0 0 # (Cyl. 0 - 1017) e: 204800 665600 4.2BSD 1024 8192 16 # (Cyl. 41*- 54*) f: 15483770 870400 4.2BSD 1024 8192 16 # (Cyl. 54*- 1017*) (This was trying to boot non-smp) Preloaded elf kernel "kernel.old" at 0xc037b000. Pentium Pro MTRR support enabled eisa0: <CPQ551 (System Board)> Probing for devices on the EISA bus Probing for devices on PCI bus 0: Correcting Natoma config for non-SMP chip0: <Intel 82440FX (Natoma) PCI and memory controller> rev 0x02 on pci0.0.0 chip1: <IBM 82351 PCI-PCI bridge> rev 0x01 on pci0.13.0 chip2: <IBM 82351 PCI-PCI bridge> rev 0x01 on pci0.15.0 chip3: <PCI to EISA bridge (vendor=0e11 device=0001)> rev 0x07 on pci0.20.0 Probing for devices on PCI bus 1: vga0: <Cirrus Logic GD5430 SVGA controller> rev 0x22 int a irq 255 on pci1.6.0 tl0: <Compaq Netelligent 10/100 Proliant> rev 0x10 int a irq 10 on pci1.7.0 tl0: Ethernet address: 00:80:5f:a6:29:6f tl0: autoneg not complete, no carrier ncr0: <ncr 53c875 fast20 wide scsi> rev 0x03 int a irq 11 on pci1.9.0 xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x24 int a irq 5 on pci1.13.0 xl0: Ethernet address: 00:10:4b:66:b4:3b xl0: autoneg complete, link status good (half-duplex, 100Mbps) Probing for devices on PCI bus 2: ida0: <Compaq SMART-2/P array controller> rev 0x02 int a irq 9 on pci2.0.0 ida0: drvs=2 firm_rev=1.36 ida0: unit 0 (id0): <Compaq Logical Drive> id0: 8024MB (16434495 total sec), 1023 cyl, 255 head, 63 sec, bytes/sec 512 ida0: unit 1 (id1): <Compaq Logical Drive> id1: 4257MB (8719950 total sec), 953 cyl, 183 head, 50 sec, bytes/sec 512 ida: wdc vector stealing on (mode = always, boot major = 0) Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard Matthew Dillon wrote: > :1. I was wondering if anyone knew of any such problems, or what other > :info I could provide to help figure this out. > :2. There are no panics or anything. I can't seem to find an isolated > :case to look at. Anyone have any idea how I would go about debugging > :this? > :3. Would I be better off running the newer driver in current? I keep > :tabs with whats going on in the current list, I just need a somewhat > :stable machine. It's only going to get light usage. > : > :Thanks for any help. Sorry this is so vauge. I'd really like you to > :get a dmesg. Below is the kernel config.... > > The very first think I would do is look at the disklabel for the drive > and make sure that none of the offset/sizes overlap (except for the > 'c' whole-disk partition, of course). > > e.g. take the offset, add the size, make sure the result is the offset > for the next partition, and repeat. The final offset+size should of course > not exceed the size of the disk. Partitions can slice up the disk > out of order, but if they overlap (except for c) you will get file > corruption. > > Also look for error messages in /var/log/messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37FE4550.2492421C>