Seagate 200GB/ST3200822A, was Re: problems with RAID0 ...
Is there any know problems with this disk (Seagate 200gb/ata) + FreeBSD + Promise/RAID0? Im asking, since a similar configuration but with smaller disk works fine. I keep getting - after several hours of populating a huge data base: /kernel: ad4: hard error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) trying PIO mode /kernel: ad4: hard error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) status=59 error=10 /kernel: ar0: ERROR - array broken why would the kernel want to read ad4 fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) when the filesystem is ar0? /kernel: ar0: 381564MB ATA RAID0 array [48642/255/63] status: READY subdisks: /kernel: 0 READY ad4: 190782MB ST3200822A [387621/16/63] at ata2-master UDMA100 /kernel: 1 READY ad6: 190782MB ST3200822A [387621/16/63] at ata3-master UDMA100 danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serious vinum bug in 4-10 RELEASE?-solved?
On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote: I see no drives. Ideas? I have concluded that this is the result of somekind of vinum/hardware incompatibility. The problem in question occured during the upgrade to faster disks, specifically, Seagate Cheetah ST318453LC on a DELL 2450. If I swap back the old Quantum Atlas 36G disk, the problem entirely disappears. The new disks function ok with UFS partitions but not vinum. It is 100% repeatable. Don't know why. thanx - steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Fairly regular crash with usb disk backup
Hi, $ uname -a FreeBSD corona.sequestor.lan 4.10-STABLE FreeBSD 4.10-STABLE #0: Sat Jul 10 14:24:06 BST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CORONA i386 I have a USB enclosure with a 200 GB disk which I use for backups using RVM. 4 times out of 5 (approximately) all goes well. The 5th time it hard crashes the system. It's a bit annoying, but I can live with it. However, I'm sure someone would like details of the problem. I am also a bit worried about the state of my disk volumes after the crash. There is absolutely nothing in /var/log/messages or redirected stdin/err for the job. What, if anything, should I do so as I can provide debugging material if required? -- Experience is directly proportional to the cost of the equipment ruined. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Stable on Supermicro server?
Hi, I am planning on building a FreeBSD server with a Supermicro 5013C-T 1U server. It has a Supermicro P4SCE motherboard, with a P4 of around 2.8 GHz, and 512MB or 1 GB memory. I am planning on adding two Western Digital Raptor 74 GB SATA drives in mirror. It will be mainly used as a web server for 5-10 sites, running Apache with php and mySql, and a (probably not heavily loaded) mail server. Perhaps the disks are a bit overkill for this, but I like the 5 year warranty, and the server will be located in a data center where I can't easily go. Will this combination work with -stable? Is it truly stable? Are there any known problems? Thanks for any info, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [TEST/REVIEW/HEADSUP] tty drivers mega-patch
http://phk.freebsd.dk/patch/tty.patch This patch removes 2500 lines of copypaste insanity in tty drivers and generally tries to get things to be less confused confusing. I need testers for all the different kinds of serial hardware we support. Please help test! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serious vinum bug in 4-10 RELEASE?-solved?
Steve Shorter wrote: On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote: I see no drives. Ideas? I have concluded that this is the result of somekind of vinum/hardware incompatibility. The problem in question occured during the upgrade to faster disks, specifically, Seagate Cheetah ST318453LC on a DELL 2450. If I swap back the old Quantum Atlas 36G disk, the problem entirely disappears. The new disks function ok with UFS partitions but not vinum. It is 100% repeatable. Don't know why. We have had issues with Cheetah U320 harddrives (at least the 10K 80-pin varieties on our Supermicro boxes) with a high percentage of drive failures ( 10%) and communications errors across the scsi bus. These errors disappear when we reverted back to IBM/Hitachi drives. The Seagate issues occur with both FreeBSD 4.x and 5.x series so there is something in the Seagate firmware (I believe) that is interacting poorly with FreeBSD. We have experienced these issues with vinum setups and other configurations where the there are either multiple Seagate drives or multiple drives where one of them is a Seagate. Firmware updates did not help. I have not had this problem where there is only one drive and it occupies da0. Sven ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stable on Supermicro server?
On Tue, 13 Jul 2004, Ben Stuyts wrote: I am planning on building a FreeBSD server with a Supermicro 5013C-T 1U server. It has a Supermicro P4SCE motherboard, with a P4 of around 2.8 GHz, and 512MB or 1 GB memory. I am planning on adding two Western Digital Raptor 74 GB SATA drives in mirror. It will be mainly used as a web server for 5-10 sites, running Apache with php and mySql, and a (probably not heavily loaded) mail server. Perhaps the disks are a bit overkill for this, but I like the 5 year warranty, and the server will be located in a data center where I can't easily go. Will this combination work with -stable? Is it truly stable? Are there any known problems? dmesg provided below. The SATA RAID controller, although it provides a 'legacy' option which should expose the RAID as an ordinary device, doesn't work despite the fact that both disk drives' LEDs flash when RAID 1 is enabled ;-( The RAID isn't supported by almost any operating system. We're using these boxes in combination with the relatively low cost 3ware 8006-2LP SATA raid card: http://www.3ware.com/products/serial_ata8000.asp and they work really nicely with FreeBSD and Linux. Chris Foote [EMAIL PROTECTED] _ _ _Jabber: [EMAIL PROTECTED] (_)| | | | Director - INETD PTY LTD _ _ __ ___ | |___| | Level 2, 132 Franklin St | | | '_ \ / _ \ | __| / _` | Adelaide SA 5000 | | | | | | | __/ | |_ | (_| | Web: http://www.inetd.com.au |_| |_| |_| \___| \__| \__,_| Phone: (08) 8410 4566 Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-STABLE #3: Mon May 31 12:22:58 CST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ACS Timecounter i8254 frequency 1193182 Hz CPU: Intel(R) Celeron(R) CPU 2.40GHz (2395.92-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 536805376 (524224K bytes) avail memory = 516558848 (504452K bytes) Preloaded elf kernel kernel at 0xc059e000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 11 entries at 0xc00fde90 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: Intel 82875P host to AGP bridge mem 0xe000-0xefff at device 0.0 on pci0 pcib1: PCI to PCI bridge (vendor=8086 device=2579) at device 1.0 on pci0 pci1: PCI bus on pcib1 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xbc00-0xbc1f irq 5 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xb000-0xb01f irq 9 at device 29.1 on pci0 usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xb400-0xb41f irq 11 at device 29.2 on pci0 usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0xb800-0xb81f irq 5 at device 29.3 on pci0 usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: USB controller at 29.7 irq 12 pcib2: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 pci2: ATI Mach64-GR graphics accelerator at 9.0 irq 5 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.25 port 0xa400-0xa43f mem 0xf200-0xf201 irq 10 at device 10.0 on pci2 em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.25 port 0xa800-0xa83f mem 0xf202-0xf203 irq 12 at device 11.0 on pci2 em1: Speed:N/A Duplex:N/A isab0: PCI to ISA bridge (vendor=8086 device=24d0) at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 SATA150 controller port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 11 at device 31.2 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: unknown card (vendor=0x8086, dev=0x24d3) at 31.3 irq 11 orm0: Option ROM at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 vga0: Generic ISA VGA at
Re: Stable on Supermicro server?
On 14 Jul 2004, at 02:12, Chris Foote wrote: On Tue, 13 Jul 2004, Ben Stuyts wrote: I am planning on building a FreeBSD server with a Supermicro 5013C-T 1U server. It has a Supermicro P4SCE motherboard, with a P4 of around 2.8 GHz, and 512MB or 1 GB memory. I am planning on adding two Western Digital Raptor 74 GB SATA drives in mirror. The SATA RAID controller, although it provides a 'legacy' option which should expose the RAID as an ordinary device, doesn't work despite the fact that both disk drives' LEDs flash when RAID 1 is enabled ;-( The RAID isn't supported by almost any operating system. So I'm not sure I understand fully: is there a way to connect the sata drives to the onboard ich5 controller, and make them work as separate (not raid) devices? In that case I could use vinum. Thanks, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stable on Supermicro server?
On Wed, 14 Jul 2004, Ben Stuyts wrote: On 14 Jul 2004, at 02:12, Chris Foote wrote: On Tue, 13 Jul 2004, Ben Stuyts wrote: I am planning on building a FreeBSD server with a Supermicro 5013C-T 1U server. It has a Supermicro P4SCE motherboard, with a P4 of around 2.8 GHz, and 512MB or 1 GB memory. I am planning on adding two Western Digital Raptor 74 GB SATA drives in mirror. The SATA RAID controller, although it provides a 'legacy' option which should expose the RAID as an ordinary device, doesn't work despite the fact that both disk drives' LEDs flash when RAID 1 is enabled ;-( The RAID isn't supported by almost any operating system. So I'm not sure I understand fully: is there a way to connect the sata drives to the onboard ich5 controller, and make them work as separate (not raid) devices? In that case I could use vinum. If you enable 'legacy' mode in the BIOS settings for the RAID, and select 'IDE' mode rather than 'RAID', then you end up with 2 simulated ata drives which you can access with any operating system: ad0: 114473MB WDC WD1200JD-00GBB0 [232581/16/63] at ata0-master UDMA100 ad1: 114473MB WDC WD1200JD-00GBB0 [232581/16/63] at ata0-slave UDMA100 so you could use vinum on them. Chris Foote [EMAIL PROTECTED] _ _ _Jabber: [EMAIL PROTECTED] (_)| | | | Director - INETD PTY LTD _ _ __ ___ | |___| | Level 2, 132 Franklin St | | | '_ \ / _ \ | __| / _` | Adelaide SA 5000 | | | | | | | __/ | |_ | (_| | Web: http://www.inetd.com.au |_| |_| |_| \___| \__| \__,_| Phone: (08) 8410 4566 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10-stable self eating
Am Samstag, 10. Juli 2004 03:53 schrieb Doug White: [...] Here is what I saw on the console: spec_getpages:(#da/0x2) I/O read failure: (error=5) bp 0xcbb0 vp 0xcd3bdec0 looks like your disk went to lunch. You might check connections, then consider how much you like the data on that disk since it might be dying. Today I saw this error again. Is there any reason why a 4.9-module shouldn't work on 4.10 the exactly same way as it does on 4.9? Here's the console output after I tried to login via the console (not before that!): spec_getpages:(#da/0x20005) I/O read failure: (error=5) bp 0xc640cbb0 vp 0xcd3bc9c0 size: 22016, resid: 22016, a_count: 21024, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcaount: 6 Again, you can find the screenshot(s) here: http://www.schmalzbauer.de/document.php?id=17 The kernel konfiguration can be downloaded at: The machines describtion is at: http://www.schmalzbauer.de/articles.php?mode=commentsid=3 it's dmesg: http://www.schmalzbauer.de/document.php?id=7 If somebody is interested in the kernel config: http://www.schmalzbauer.de/download.php?get=Li91cGxvYWRzL0tPUlNP The machines describtion is at: http://www.schmalzbauer.de/articles.php?mode=commentsid=3 it's dmesg: http://www.schmalzbauer.de/document.php?id=7 Seems like the HighPoint 4.9-module isn't working with 4.10-stable (Don't even think about discussing the native ataraid) Thanks, -Harry pgpXx7mQG1Ecf.pgp Description: signature
