Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
Hi Guys I am running RAID 10. Here is the dmesg output: $ dmesg Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Fri Aug 29 13:42:13 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/KERNEL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5450 @ 3.00GHz (2995.54-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 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 Features2=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 4 usable memory = 17166688256 (16371 MB) avail memory = 16619601920 (15849 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL PE_SC3 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci4: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci4 pci5: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib3 pcib4: PCI-PCI bridge at device 0.0 on pci6 pci7: PCI bus on pcib4 bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) mem 0xf400-0xf5ff irq 16 at device 0.0 on pci7 miibus0: MII bus on bce0 brgphy0: BCM5708C 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bce0: Ethernet address: 00:1e:c9:d5:88:f0 bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x04000305); Flags( MFW MSI ) pcib5: ACPI PCI-PCI bridge at device 1.0 on pci5 pci8: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 0.3 on pci4 pci9: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on pcib7 mfi0: Dell PERC 6 port 0xec00-0xecff mem 0xfc68-0xfc6b,0xfc64-0xfc67 irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 2.00 mfi0: 2145 (279883150s/0x0020/info) - Shutdown command received from host mfi0: 2146 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) mfi0: 2147 (boot + 3s/0x0020/info) - Firmware version 1.11.52-0396 mfi0: 2148 (boot + 3s/0x0008/info) - Battery Present mfi0: 2149 (boot + 3s/0x0020/info) - Package version 6.0.2-0002 mfi0: 2150 (boot + 21s/0x0004/info) - Enclosure (SES) discovered on PD 20(c None/p0) mfi0: 2151 (boot + 21s/0x0002/info) - Inserted: Encl PD 20 mfi0: 2152 (boot + 21s/0x0002/info) - Inserted: PD 20(c None/p0) Info: enclPd=20, scsiType=d, portMap=09, sasAddr=5001e0f03d0c6f00, mfi0: 2153 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) mfi0: 2154 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=5000cca00904b705, mfi0: 2155 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) mfi0: 2156 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) Info: enclPd=20, scsiType=0, portMap=01, sasAddr=5000cca009024231, mfi0: 2157 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) mfi0: 2158 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) Info: enclPd=20, scsiType=0, portMap=02, sasAddr=5000cca00904d92d, mfi0: 2159 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) mfi0: 2160 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) Info: enclPd=20, scsiType=0, portMap=03, sasAddr=5000cca009048865, mfi0: 2161 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) mfi0: 2162 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5000cca009048d2d, mfi0: 2163 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) mfi0: 2164 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) Info: enclPd=20, scsiType=0, portMap=05, sasAddr=5000cca009048f31, mfi0: 2165 (279879506s/0x0020/info) - Time established as 11/13/08 8:18:26; (26 seconds since power on) mfi0: 2166 (279879548s/0x0008/info) - Battery temperature is normal mfi0: [ITHREAD] pcib8: ACPI PCI-PCI bridge at device 4.0 on pci0 pci10: ACPI PCI bus on pcib8 pcib9: PCI-PCI bridge at device 5.0 on pci0 pci11: PCI bus on pcib9
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 02:16:58PM +0100, VeeJay wrote: I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... I've CC'd Scott Long, who is the author of the mfi(4) driver. He should be able to explain what the error messages mean. Scott, check out the URL below. On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
The sense data in the screen shot boils down to an ASC/ASCQ pair of 0x35/0x05. Looking this up in the ASC table found at t10.org gives the following: 35h/05h ENCLOSURE SERVICES CHECKSUM ERROR What this basically means is that the disk enclosure that you're using has some sort of an unknown defect or failure. It has nothing to do with the OS. Dell needs to send you a new enclosure, plain and simple. Scott Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 02:16:58PM +0100, VeeJay wrote: I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... I've CC'd Scott Long, who is the author of the mfi(4) driver. He should be able to explain what the error messages mean. Scott, check out the URL below. On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? Regards VJ On Thu, Nov 13, 2008 at 9:49 AM, VeeJay [EMAIL PROTECTED] wrote: Hi Guys I am running RAID 10. Here is the dmesg output: $ dmesg Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Fri Aug 29 13:42:13 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/KERNEL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5450 @ 3.00GHz (2995.54-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 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 Features2=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF Cores per package: 4 usable memory = 17166688256 (16371 MB) avail memory = 16619601920 (15849 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: DELL PE_SC3 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci4: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci4 pci5: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib3 pcib4: PCI-PCI bridge at device 0.0 on pci6 pci7: PCI bus on pcib4 bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) mem 0xf400-0xf5ff irq 16 at device 0.0 on pci7 miibus0: MII bus on bce0 brgphy0: BCM5708C 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bce0: Ethernet address: 00:1e:c9:d5:88:f0 bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x04000305); Flags( MFW MSI ) pcib5: ACPI PCI-PCI bridge at device 1.0 on pci5 pci8: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 0.3 on pci4 pci9: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on pcib7 mfi0: Dell PERC 6 port 0xec00-0xecff mem 0xfc68-0xfc6b,0xfc64-0xfc67 irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 2.00 mfi0: 2145 (279883150s/0x0020/info) - Shutdown command received from host mfi0: 2146 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028) mfi0: 2147 (boot + 3s/0x0020/info) - Firmware version 1.11.52-0396 mfi0: 2148 (boot + 3s/0x0008/info) - Battery Present mfi0: 2149 (boot + 3s/0x0020/info) - Package version 6.0.2-0002 mfi0: 2150 (boot + 21s/0x0004/info) - Enclosure (SES) discovered on PD 20(c None/p0) mfi0: 2151 (boot + 21s/0x0002/info) - Inserted: Encl PD 20 mfi0: 2152 (boot + 21s/0x0002/info) - Inserted: PD 20(c None/p0) Info: enclPd=20, scsiType=d, portMap=09, sasAddr=5001e0f03d0c6f00, mfi0: 2153 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) mfi0: 2154 (boot + 21s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=5000cca00904b705, mfi0: 2155 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) mfi0: 2156 (boot + 21s/0x0002/info) - Inserted: PD 01(e0x20/s1) Info: enclPd=20, scsiType=0, portMap=01, sasAddr=5000cca009024231, mfi0: 2157 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) mfi0: 2158 (boot + 21s/0x0002/info) - Inserted: PD 02(e0x20/s2) Info: enclPd=20, scsiType=0, portMap=02, sasAddr=5000cca00904d92d, mfi0: 2159 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) mfi0: 2160 (boot + 21s/0x0002/info) - Inserted: PD 03(e0x20/s3) Info: enclPd=20, scsiType=0, portMap=03, sasAddr=5000cca009048865, mfi0: 2161 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) mfi0: 2162 (boot + 21s/0x0002/info) - Inserted: PD 04(e0x20/s4) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5000cca009048d2d, mfi0: 2163 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) mfi0: 2164 (boot + 21s/0x0002/info) - Inserted: PD 05(e0x20/s5) Info: enclPd=20, scsiType=0, portMap=05, sasAddr=5000cca009048f31, mfi0: 2165 (279879506s/0x0020/info) - Time established as
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
Thanks guys... I have forwarded the comments from Scott to the Dell and hope for the best Thank you again. VJ On Thu, Nov 13, 2008 at 2:51 PM, Scott Long [EMAIL PROTECTED] wrote: The sense data in the screen shot boils down to an ASC/ASCQ pair of 0x35/0x05. Looking this up in the ASC table found at t10.org gives the following: 35h/05h ENCLOSURE SERVICES CHECKSUM ERROR What this basically means is that the disk enclosure that you're using has some sort of an unknown defect or failure. It has nothing to do with the OS. Dell needs to send you a new enclosure, plain and simple. Scott Jeremy Chadwick wrote: On Thu, Nov 13, 2008 at 02:16:58PM +0100, VeeJay wrote: I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... I've CC'd Scott Long, who is the author of the mfi(4) driver. He should be able to explain what the error messages mean. Scott, check out the URL below. On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- Thanks! BR / vj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
I have asked the system manufacturers (Dell) but they don't provide support for FreeBSD based systems [?] Thats why I have only hope here with FreeBSD List... On Thu, Nov 13, 2008 at 1:41 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 01:29:11PM +0100, VeeJay wrote: If it looks healthy, why there are these errors on the screen? Is it controller problem or disk? SCSI normally reports 3 things when it encounters an error (particularly disk errors): Sense Key (SK), Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ). What appears in the below screenshot is a large amount of sense data, but I can't make heads or tails out of it, because it's written in a driver-centric manner (Encl PD means nothing to me). I can read part of the CDB data, but it doesn't tell me much. Scott Long might know. http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png You should try asking the system manufacturer if they know what any of the data means. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | -- Thanks! BR / vj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Wed, 2008-11-12 at 16:01 +0100, VeeJay wrote: There seemed to be a problem related to RAID controller on one server. Screw Dell's diagnostics tools. Those are there to help psychology majors who got their MCSE and RHCE after they realized that all you can do with a psychology degree is teach psychology or serve coffee. Send us your screenshot. Nothing was attached. -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
Hello I have used the PERC on dells 2900 2950 they are trick pieces of hardware and can easyly wipe out the contents of your disk drive on the CTRL-R screen (setup screen). the best configuration I used is to use RAID-0 (no raid) on the controller and g mirror on the FreeBSD (that is I use the mirror in software) mainly because the Freebsd kernel is, in this manner, can detect problems with the drivers and so, can act on it so 1) attach a new drive on your controller (this drive will be erased...) 2) put the drive in another VD (on the control-r screen) 3) attach the drive... 4) format it in the running freebsd 5) put your data on the drive (using tar) 6) shutdown the computer, save the drive 7) mount the other drivers using raid-0 8) re-install freebsd using g-mirror (see freebsd documentation...) 9) remount the saved drive on the controller now using the Foreing option 10) boot freebsd, mount the drive restore the sistem and be happy Hope that it can help ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Wednesday 12 November 2008 11:35:33 Jeremy Chadwick wrote: On Wed, Nov 12, 2008 at 11:05:44AM +0100, VeeJay wrote: Hello Guys I am in a situation here. I am running couple of Dell 2950 Servers with FreeBSD 7.0 amd. There seemed to be a problem related to RAID controller on one server. From Dell support, I was told to download a troubleshooting tool called DSET. ( http://support.dell.com/support/topics/global.aspx/support/en/dell_system _tool?c=usl=ens=gen ) But that is for Linux distributions. So, I am just in middle of no where :( Could you guys guide me that how to install and run this tool on my server in order to diagnose problem? This question should have gone to -hardware or -stable. Actually, the better one would be -emulation, since they might be able to answer if Dell's linux troubleshooting tool would yield any useful information on freebsd and how to install/run it in the first place. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Wed, 2008-11-12 at 19:39 +0100, VeeJay wrote: Hi Brian Thanks. I sent the attachment but FreeBSD List would not allow me to First order of business is to _not_ send it as a BMP. Use PNG instead, and post the URL and not the actual file: http://digitalfreaks.org/~lavalamp/20081023_server3_screen_dump.png --- Second order of business: Unexpected sense code on a PD (Physical Disk) suggests that one of your disks is bad / becoming bad. Check the enclosure -- likely it is flashing. Install MegaCli from ports, if you can. You can always reboot and use the BIOS menu to check the event log. If its not a bad disk, then something bizarre is happening. We'll want to know what firmware revision you're running on the controller, and on the disks (Dell disk firmware updates run from DOS) ~~BAS send email of more than 200K in size. So, here it is... I hope you can figure out how to solve this issue... With best wishes VJ On Wed, Nov 12, 2008 at 4:25 PM, Brian A. Seklecki [EMAIL PROTECTED] wrote: On Wed, 2008-11-12 at 16:01 +0100, VeeJay wrote: There seemed to be a problem related to RAID controller on one server. Screw Dell's diagnostics tools. Those are there to help psychology majors who got their MCSE and RHCE after they realized that all you can do with a psychology degree is teach psychology or serve coffee. Send us your screenshot. Nothing was attached. -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. -- Thanks! BR / vj -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Wed, Nov 12, 2008 at 11:05:44AM +0100, VeeJay wrote: Hello Guys I am in a situation here. I am running couple of Dell 2950 Servers with FreeBSD 7.0 amd. There seemed to be a problem related to RAID controller on one server. From Dell support, I was told to download a troubleshooting tool called DSET. ( http://support.dell.com/support/topics/global.aspx/support/en/dell_system_tool?c=usl=ens=gen ) But that is for Linux distributions. So, I am just in middle of no where :( Could you guys guide me that how to install and run this tool on my server in order to diagnose problem? This question should have gone to -hardware or -stable. It depends on what RAID controller is installed in the box, and what problem you're actually having (There seemed to be a problem with the RAID controller tells us nothing). I believe others have some experience with PERC controllers, but as I said, we don't know what hardware you have. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 12:20 AM, Sérgio de Almeida Lenzi [EMAIL PROTECTED]wrote: Hello snip the best configuration I used is to use RAID-0 (no raid) on the controller and g mirror on the FreeBSD (that is I use the mirror in software) mainly because the Freebsd kernel is, in this manner, can detect problems with the drivers and so, can act on it snip Do not use RAID-0! What you want is JBOD and freebsd's software raid. RAID-0 does striping over both drives...if one drive is dead you're screwed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any help about FreeBSD Dell's Troubleshooting Tool DSET
On Thu, Nov 13, 2008 at 01:43:46PM +0800, TJ Varghese wrote: On Thu, Nov 13, 2008 at 12:20 AM, Sérgio de Almeida Lenzi [EMAIL PROTECTED]wrote: Hello snip the best configuration I used is to use RAID-0 (no raid) on the controller and g mirror on the FreeBSD (that is I use the mirror in software) mainly because the Freebsd kernel is, in this manner, can detect problems with the drivers and so, can act on it snip Do not use RAID-0! What you want is JBOD and freebsd's software raid. RAID-0 does striping over both drives...if one drive is dead you're screwed. There is nothing inherently wrong with RAID-0. For example, prior to having a machine that supported more than 3 disks, I used gstripe(8) heavily on my home FreeBSD box. I was **very** well-aware of the negative aspects of RAID-0 (one disk dies, you lose the entire filesystem). Which is why I performed backups. Daily. My point: RAID-0 is fine to use, as long as you're doing backups often, and accept what will happen if one of your disks goes bad. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
