FreeBSD 7.0 + проблемы с mpt0

Решение проблем связванных с работой железа. Проблемы программно-аппаратной совместимости.
Правила форума
Убедительная просьба юзать теги [code] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.
Аватара пользователя
Storoge
рядовой
Сообщения: 44
Зарегистрирован: 2007-09-19 12:04:14
Откуда: Брянск
Контактная информация:

FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение Storoge » 2009-05-05 16:18:13

Стоит FreeBSD 7.0

Код: Выделить всё

uname -a
FreeBSD cs.bgita2.ru 7.0-STABLE FreeBSD 7.0-STABLE #5: Thu Oct 23 19:42:41 MSD 2008     root@cs.bgita2.ru:/usr/obj/usr/src/sys/MYKERNEL  i386
Загрузка:

Код: Выделить всё

 cat /var/run/dmesg.boot
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.0-STABLE #5: Thu Oct 23 19:42:41 MSD 2008
    root@cs.bgita2.ru:/usr/obj/usr/src/sys/MYKERNEL
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU           E5335  @ 2.00GHz (1995.01-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6f7  Stepping = 7
  Features=0xbfebfbff<FPU,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=0x4e33d<SSE3,RSVD2,MON,DS_CPL,VMX,TM2,SSSE3,CX16,xTPR,PDCM,DCA>
  AMD Features=0x20100000<NX,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 4
real memory  = 3220176896 (3071 MB)
avail memory = 3151101952 (3005 MB)
ACPI APIC Table: <PTLTD  	 APIC  >
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 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
registered firmware set <isp_1040>
registered firmware set <isp_1040_it>
registered firmware set <isp_1080>
registered firmware set <isp_1080_it>
registered firmware set <isp_12160>
registered firmware set <isp_12160_it>
registered firmware set <isp_2100>
registered firmware set <isp_2200>
registered firmware set <isp_2300>
registered firmware set <isp_2322>
registered firmware set <isp_2400>
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
acpi0: <PTLTD 	 XSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 400, 100 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b 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
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci2
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 2.0 on pci2
pci4: <ACPI PCI bus> on pcib4
em0: <Intel(R) PRO/1000 Network Connection 6.9.5> port 0x2000-0x201f mem 0xc8200000-0xc821ffff irq 18 at device 0.0 on pci4
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:1d:60:d1:e7:bd
em1: <Intel(R) PRO/1000 Network Connection 6.9.5> port 0x2020-0x203f mem 0xc8220000-0xc823ffff irq 19 at device 0.1 on pci4
em1: Using MSI interrupt
em1: [FILTER]
em1: Ethernet address: 00:1d:60:d1:e7:bc
pcib5: <ACPI PCI-PCI bridge> at device 0.3 on pci1
pci5: <ACPI PCI bus> on pcib5
rl0: <RealTek 8139 10/100BaseTX> port 0x3000-0x30ff mem 0xc8314000-0xc83140ff irq 28 at device 2.0 on pci5
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> PHY 0 on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:80:48:25:60:0d
rl0: [ITHREAD]
mpt0: <LSILogic SAS/SATA Adapter> port 0x3400-0x34ff mem 0xc8310000-0xc8313fff,0xc8300000-0xc830ffff irq 26 at device 3.0 on pci5
mpt0: [ITHREAD]
mpt0: MPI Version=1.5.16.0
mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 )
mpt0: 0 Active Volumes (2 Max)
mpt0: 0 Hidden Drive Members (14 Max)
pcib6: <ACPI PCI-PCI bridge> at device 3.0 on pci0
pci6: <ACPI PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci7: <ACPI PCI bus> on pcib7
pcib8: <PCI-PCI bridge> at device 5.0 on pci0
pci8: <PCI bus> on pcib8
pcib9: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci9: <ACPI PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pci10: <ACPI PCI bus> on pcib10
pci0: <base peripheral> at device 8.0 (no driver attached)
pcib11: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
pci11: <ACPI PCI bus> on pcib11
uhci0: <Intel 631XESB/632XESB/3100 USB controller USB-1> port 0x1800-0x181f irq 17 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <Intel 631XESB/632XESB/3100 USB controller USB-1> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 631XESB/632XESB/3100 USB controller USB-2> port 0x1820-0x183f irq 19 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <Intel 631XESB/632XESB/3100 USB controller USB-2> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 631XESB/632XESB/3100 USB controller USB-3> port 0x1840-0x185f irq 18 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2: <Intel 631XESB/632XESB/3100 USB controller USB-3> on uhci2
usb2: USB revision 1.0
uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
uhci3: <Intel 631XESB/632XESB/3100 USB controller USB-4> port 0x1860-0x187f irq 16 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb3: <Intel 631XESB/632XESB/3100 USB controller USB-4> on uhci3
usb3: USB revision 1.0
uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
pci0: <serial bus, USB> at device 29.7 (no driver attached)
pcib12: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci12: <ACPI PCI bus> on pcib12
vgapci0: <VGA-compatible display> port 0x4000-0x40ff mem 0xd0000000-0xd7ffffff,0xc8400000-0xc840ffff irq 17 at device 2.0 on pci12
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel 63XXESB2 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <Intel 63XXESB2 SATA300 controller> port 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf mem 0xc8000400-0xc80007ff irq 19 at device 31.2 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
cpu0: <ACPI CPU> on acpi0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
p4tcc3: <CPU Frequency Thermal Control> on cpu3
cpu4: <ACPI CPU> on acpi0
p4tcc4: <CPU Frequency Thermal Control> on cpu4
cpu5: <ACPI CPU> on acpi0
p4tcc5: <CPU Frequency Thermal Control> on cpu5
cpu6: <ACPI CPU> on acpi0
p4tcc6: <CPU Frequency Thermal Control> on cpu6
cpu7: <ACPI CPU> on acpi0
p4tcc7: <CPU Frequency Thermal Control> on cpu7
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
fdc0: <floppy drive controller (FDE)> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <Parallel port> port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ppbus0: [ITHREAD]
plip0: <PLIP network interface> on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
ppi0: <Parallel I/O> on ppbus0
vpo0: <Iomega VPI0 Parallel to SCSI interface> on ppbus0
vpo0: EPP mode
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcafff,0xcb000-0xcbfff pnpid ORM0000 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ugen0: <American Power Conversion Back-UPS RS 1000 FW:7.g9a.I USB FW:g9a, class 0/0, rev 1.10/1.06, addr 2> on uhub0
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
ipfw2 initialized, divert enabled, nat enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default
acd0: DVDR <HL-DT-ST DVDRAM GSA-H62N/CL00> at ata2-master SATA150
da0 at mpt0 bus 0 target 0 lun 0
da0: <ATA ST3500320AS SD04> Fixed Direct Access SCSI-5 device 
da0: 300.000MB/s transfers
da0: Command Queueing Enabled
da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C)
da1 at mpt0 bus 0 target 4 lun 0
da1: <ATA ST3500320AS SD04> Fixed Direct Access SCSI-5 device 
da1: 300.000MB/s transfers
da1: Command Queueing Enabled
da1: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C)
da2 at vpo0 bus 0 target 6 lun 0
da2: <IOMEGA ZIP 100 J.03> Removable Direct Access SCSI-2 device 
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #4 Launched!
GEOM_MIRROR: Device mirror/gm0 launched (1/2).
GEOM_MIRROR: Device gm0: rebuilding provider da0.
Trying to mount root from ufs:/dev/mirror/gm0s1a
WARNING: /cache was not properly dismounted
WARNING: /home was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /usr/local/www was not properly dismounted
WARNING: /var was not properly dismounted
Стоит gmiror

Код: Выделить всё

gmirror list
Geom name: gm0
State: COMPLETE
Components: 2
Balance: round-robin
Slice: 4096
Flags: NONE
GenID: 1
SyncID: 2
ID: 4185776867
Providers:
1. Name: mirror/gm0
   Mediasize: 500107861504 (466G)
   Sectorsize: 512
   Mode: r7w7e8
Consumers:
1. Name: da0
   Mediasize: 500107862016 (466G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Priority: 0
   Flags: DIRTY
   GenID: 1
   SyncID: 2
   ID: 3243959621
2. Name: da1
   Mediasize: 500107862016 (466G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Priority: 0
   Flags: DIRTY
   GenID: 1
   SyncID: 2
   ID: 2622853877
> 
В последнее время из raid-массива стал регулярно выпадать один из дисков.Повторное добавление в массив проходит успешно.
Даже при исправном raid-массиве постоянно стали выскакивать такие сообщения, которые через некоторое время приводят к полному зависанию системы, помогает лишь перезагрузка

Код: Выделить всё

May  5 17:07:29 cs kernel: mpt0: request 0xc74f2850:28137 timed out for ccb 0xc9380800 (req->ccb 0xc9380800)
May  5 17:07:29 cs kernel: mpt0: attempting to abort req 0xc74f2850:28137 function 0
May  5 17:07:43 cs kernel: mpt0: mpt_wait_req(1) timed out
May  5 17:07:43 cs kernel: mpt0: mpt_recover_commands: abort timed-out. Resetting controller
May  5 17:07:43 cs kernel: mpt0: mpt_cam_event: 0x20
May  5 17:07:43 cs kernel: mpt0: completing timedout/aborted req 0xc74f2850:28137
May  5 17:07:43 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:07:43 cs last message repeated 2 times
May  5 17:07:43 cs kernel: mpt0: mpt_cam_event: 0x12
May  5 17:07:43 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:07:43 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:07:43 cs kernel: mpt0: mpt_cam_event: 0x12
May  5 17:07:43 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:07:43 cs last message repeated 2 times
May  5 17:08:55 cs kernel: mpt0: request 0xc74f97a4:31624 timed out for ccb 0xc8596c00 (req->ccb 0xc8596c00)
May  5 17:08:55 cs kernel: mpt0: request 0xc74f7618:31625 timed out for ccb 0xc7b74800 (req->ccb 0xc7b74800)
May  5 17:08:55 cs kernel: mpt0: attempting to abort req 0xc74f97a4:31624 function 0
May  5 17:08:55 cs kernel: mpt0: request 0xc74f2850:31629 timed out for ccb 0xc7583400 (req->ccb 0xc7583400)
May  5 17:09:09 cs kernel: mpt0: request 0xc74f9a50:31631 timed out for ccb 0xc967f400 (req->ccb 0xc967f400)
May  5 17:09:09 cs kernel: mpt0: mpt_wait_req(1) timed out
May  5 17:09:09 cs kernel: mpt0: mpt_recover_commands: abort timed-out. Resetting controller
May  5 17:09:09 cs kernel: mpt0: mpt_cam_event: 0x20
May  5 17:09:09 cs kernel: mpt0: completing timedout/aborted req 0xc74f97a4:31624
May  5 17:09:09 cs kernel: mpt0: completing timedout/aborted req 0xc74f7618:31625
May  5 17:09:09 cs kernel: mpt0: completing timedout/aborted req 0xc74f2850:31629
May  5 17:09:09 cs kernel: mpt0: completing timedout/aborted req 0xc74f9a50:31631
May  5 17:09:09 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:09:09 cs last message repeated 2 times
May  5 17:09:09 cs kernel: mpt0: mpt_cam_event: 0x12
May  5 17:09:09 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:09:09 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:09:09 cs kernel: mpt0: mpt_cam_event: 0x12
May  5 17:09:09 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:09:09 cs last message repeated 2 times
May  5 17:13:14 cs kernel: mpt0: request 0xc74f54d8:50112 timed out for ccb 0xc74bb800 (req->ccb 0xc74bb800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f5998:50113 timed out for ccb 0xc97a2800 (req->ccb 0xc97a2800)
May  5 17:13:14 cs kernel: mpt0: attempting to abort req 0xc74f54d8:50112 function 0
May  5 17:13:14 cs kernel: mpt0: request 0xc74f3008:50116 timed out for ccb 0xc9387800 (req->ccb 0xc9387800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f7794:50117 timed out for ccb 0xc7b40400 (req->ccb 0xc7b40400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f81ac:50120 timed out for ccb 0xc90e8c00 (req->ccb 0xc90e8c00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f8b78:50121 timed out for ccb 0xc7b47800 (req->ccb 0xc7b47800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f8bc4:50124 timed out for ccb 0xc7b64400 (req->ccb 0xc7b64400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f3be8:50125 timed out for ccb 0xc9395800 (req->ccb 0xc9395800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f7f00:50128 timed out for ccb 0xc8599000 (req->ccb 0xc8599000)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f6f44:50129 timed out for ccb 0xc9387400 (req->ccb 0xc9387400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74fb094:50132 timed out for ccb 0xc7b62400 (req->ccb 0xc7b62400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74fa08c:50133 timed out for ccb 0xc9395000 (req->ccb 0xc9395000)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f8ae0:50136 timed out for ccb 0xc90e9c00 (req->ccb 0xc90e9c00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f3644:50137 timed out for ccb 0xc85a2400 (req->ccb 0xc85a2400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f90d0:50140 timed out for ccb 0xc8598400 (req->ccb 0xc8598400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f6ad0:50141 timed out for ccb 0xc85bcc00 (req->ccb 0xc85bcc00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f50fc:50144 timed out for ccb 0xc97a2c00 (req->ccb 0xc97a2c00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f9f10:50145 timed out for ccb 0xc97a2400 (req->ccb 0xc97a2400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f321c:50148 timed out for ccb 0xc9674c00 (req->ccb 0xc9674c00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f2980:50149 timed out for ccb 0xc7b6d400 (req->ccb 0xc7b6d400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f53a8:50152 timed out for ccb 0xc90ecc00 (req->ccb 0xc90ecc00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74facb8:50153 timed out for ccb 0xc859cc00 (req->ccb 0xc859cc00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f39d4:50156 timed out for ccb 0xc85a2c00 (req->ccb 0xc85a2c00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f6578:50157 timed out for ccb 0xc7494800 (req->ccb 0xc7494800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f2ab0:50160 timed out for ccb 0xc7b3b800 (req->ccb 0xc7b3b800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f43a0:50161 timed out for ccb 0xc7b68400 (req->ccb 0xc7b68400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f9d94:50164 timed out for ccb 0xc967b800 (req->ccb 0xc967b800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f4db8:50165 timed out for ccb 0xc9392400 (req->ccb 0xc9392400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f8704:50168 timed out for ccb 0xc9393800 (req->ccb 0xc9393800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f9084:50169 timed out for ccb 0xc9383800 (req->ccb 0xc9383800)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f4010:50172 timed out for ccb 0xc7b83000 (req->ccb 0xc7b83000)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f4438:50173 timed out for ccb 0xc85a1c00 (req->ccb 0xc85a1c00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f2720:50176 timed out for ccb 0xc7b5f400 (req->ccb 0xc7b5f400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f3a6c:50178 timed out for ccb 0xc90eac00 (req->ccb 0xc90eac00)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f782c:50180 timed out for ccb 0xc7583400 (req->ccb 0xc7583400)
May  5 17:13:14 cs kernel: mpt0: request 0xc74f7d38:50182 timed out for ccb 0xc7b63000 (req->ccb 0xc7b63000)
May  5 17:13:27 cs kernel: mpt0: mpt_wait_req(1) timed out
May  5 17:13:27 cs kernel: mpt0: mpt_recover_commands: abort timed-out. Resetting controller
May  5 17:13:27 cs kernel: mpt0: mpt_cam_event: 0x20
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f54d8:50112
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f5998:50113
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f3008:50116
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f7794:50117
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f81ac:50120
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f8b78:50121
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f8bc4:50124
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f3be8:50125
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f7f00:50128
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f6f44:50129
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74fb094:50132
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74fa08c:50133
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f8ae0:50136
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f3644:50137
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f90d0:50140
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f6ad0:50141
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f50fc:50144
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f9f10:50145
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f321c:50148
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f2980:50149
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f53a8:50152
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74facb8:50153
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f39d4:50156
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f6578:50157
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f2ab0:50160
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f43a0:50161
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f9d94:50164
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f4db8:50165
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f8704:50168
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f9084:50169
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f4010:50172
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f4438:50173
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f2720:50176
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f3a6c:50178
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f782c:50180
May  5 17:13:27 cs kernel: mpt0: completing timedout/aborted req 0xc74f7d38:50182
May  5 17:13:27 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:13:27 cs last message repeated 2 times
May  5 17:13:27 cs kernel: mpt0: mpt_cam_event: 0x12
May  5 17:13:27 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:13:27 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:13:27 cs kernel: mpt0: mpt_cam_event: 0x12
May  5 17:13:27 cs kernel: mpt0: mpt_cam_event: 0x16
May  5 17:13:27 cs last message repeated 2 times
В чем проблема? Диск, контроллер....
Жду совета, с чего начать....

Хостинговая компания Host-Food.ru
Хостинг HostFood.ru
 

Услуги хостинговой компании Host-Food.ru

Хостинг HostFood.ru

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/

Аватара пользователя
Fastman
ст. лейтенант
Сообщения: 1236
Зарегистрирован: 2006-07-07 10:20:38
Откуда: Минск. РБ

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение Fastman » 2009-05-06 19:14:41

Я думаю надо поглядеть на свежую прошивку контроллера.
И порыть листы рассылки.
Главное в жизни здоровье и любовь, остальное я все куплю.

bu7cher
сержант
Сообщения: 220
Зарегистрирован: 2008-02-21 18:28:55
Откуда: Киров
Контактная информация:

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение bu7cher » 2009-05-07 7:20:08

Для начала проверьте SMART статус того диска, который выпадает.
нет ничего невозможного

Аватара пользователя
zingel
beastie
Сообщения: 6204
Зарегистрирован: 2007-10-30 3:56:49
Откуда: Moscow
Контактная информация:

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение zingel » 2009-05-07 10:08:29

Код: Выделить всё

sysctl -w kern.cam.scsi_delay=3000
Z301171463546 - можно пожертвовать мне денег

Аватара пользователя
Storoge
рядовой
Сообщения: 44
Зарегистрирован: 2007-09-19 12:04:14
Откуда: Брянск
Контактная информация:

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение Storoge » 2009-05-07 12:12:31

Можно поподробнее описание этой команды, почему именно 3000?

Аватара пользователя
zingel
beastie
Сообщения: 6204
Зарегистрирован: 2007-10-30 3:56:49
Откуда: Moscow
Контактная информация:

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение zingel » 2009-05-07 12:13:59

Z301171463546 - можно пожертвовать мне денег

Аватара пользователя
Storoge
рядовой
Сообщения: 44
Зарегистрирован: 2007-09-19 12:04:14
Откуда: Брянск
Контактная информация:

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение Storoge » 2009-05-08 18:21:48

я решил начать с проверки дисков, однако smartctl добраться до них не может (контроллер видит диски как scsi)
тогда я подключил эти диски к тому же серверу через sata-разъемы
система запустилась
опять пошли ошибки, но теперь вида

Код: Выделить всё

ad5: TIMEOUT - READ_DMA retrying ....
ad5: TIMEOUT - WRITE_DMA retrying...
Потом проверил smart:

Код: Выделить всё

>smartctl -A /dev/ad4
smartctl version 5.38 [i386-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   116   099   006    Pre-fail  Always       -       111165278
  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       108
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       42
  7 Seek_Error_Rate         0x000f   064   060   030    Pre-fail  Always       -       326604211851
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       9916
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   037   020    Old_age   Always       -       108
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   088   088   000    Old_age   Always       -       12
190 Airflow_Temperature_Cel 0x0022   064   048   045    Old_age   Always       -       36 (Lifetime Min/Max 31/36)
194 Temperature_Celsius     0x0022   036   052   000    Old_age   Always       -       36 (0 13 0 0)
195 Hardware_ECC_Recovered  0x001a   041   023   000    Old_age   Always       -       111165278
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
Если я все правильно понял, все дело в дисках и пришла пора их менять?

zeone
мл. сержант
Сообщения: 131
Зарегистрирован: 2010-01-29 11:51:02

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение zeone » 2011-02-07 10:36:14

Посоветуйте у меня аналогичная проблема 8(
Рейд масив апаратный Adaptec 2405, биос пару дней наад поставил новый.
Сама фря висит на виртуалке.

Код: Выделить всё

Feb  4 17:57:23 tehas kernel: mpt0: abort of req 0xc42febf0:0 completed
Feb  4 17:57:23 tehas kernel: mpt0: attempting to abort req 0xc4303420:2429 function 0
Feb  4 17:57:23 tehas kernel: mpt0: completing timedout/aborted req 0xc4303420:2429
Feb  4 17:57:23 tehas kernel: mpt0: abort of req 0xc4303420:0 completed
Feb  4 17:58:06 tehas kernel: mpt0: request 0xc42ff320:2430 timed out for ccb 0xc4e1b000 (req->ccb 0xc4e1b000)
Feb  4 17:58:06 tehas kernel: mpt0: attempting to abort req 0xc42ff320:2430 function 0
Feb  4 17:58:06 tehas kernel: mpt0: mpt_wait_req(1) timed out
Feb  4 17:58:06 tehas kernel: mpt0: mpt_recover_commands: abort timed-out. Resetting controller
Feb  4 17:58:06 tehas kernel: mpt0: mpt_cam_event: 0x80
Feb  4 17:58:06 tehas kernel: mpt0: completing timedout/aborted req 0xc42ff320:2430
Думаю все писать нету смысла так как оно практически идентичное 8(
посоветуйте что можно сделать
Я выполнил команду

Код: Выделить всё

sysctl -w kern.cam.scsi_delay=3000
но если не ошибаюсь эти команды работают до перезагрузки... а пока не проверял долгосрочность работы...

Аватара пользователя
manefesto
Группенфюррер
Сообщения: 6934
Зарегистрирован: 2007-07-20 8:27:30
Откуда: Пермь
Контактная информация:

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение manefesto » 2011-02-07 14:59:23

Код: Выделить всё

echo 'kern.cam.scsi_delay=3000' >> /boot/loader.conf
я такой яростный шо аж пиздеЦ
Изображение

zeone
мл. сержант
Сообщения: 131
Зарегистрирован: 2010-01-29 11:51:02

Re: FreeBSD 7.0 + проблемы с mpt0

Непрочитанное сообщение zeone » 2011-02-07 17:03:04

Может ли такое происходить из-за того что я пожже добавил винт на фрю и возможно както коряво его прикрутил?