Бунт дисковой подсистемы

У вас сложности? Наши специалисты постараются помочь вам. Если вы сами сталкивались с похожими проблемами - поделитесь опытом.

Модераторы: Trinity admin`s, Free-lance moderator`s

Ответить
Rikk
Junior member
Сообщения: 4
Зарегистрирован: 10 апр 2010, 22:56
Откуда: SPb

Бунт дисковой подсистемы

Сообщение Rikk » 10 апр 2010, 23:02

Помогите советом. На сервере стоят SATA диски, и последнее время сыплятся в лог такие строчки:

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

Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 10 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 10 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 10 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 10 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall root: ZFS: vdev I/O failure, zpool=rpool path=/dev/label/rpool2 offset=246837428224 size=114688 error=5
Apr 10 22:51:36 waterwall root: ZFS: vdev I/O failure, zpool=rpool path=/dev/label/rpool2 offset=246837690368 size=114688 error=5
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 10 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retries Exhausted
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 11 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 11 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 11 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 11 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 11 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retries Exhausted
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): READ(10). CDB: 28 0 0 60 0 10 0 0 1 0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status Error
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): SCSI Status: Check Condition
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): HARDWARE FAILURE asc:44,0
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Internal target failure
Apr 10 22:51:36 waterwall kernel: (da2:mpt0:0:3:0): Retrying Command (per Sense Data)
Что происходит с железом? Кто может пояснить? Будьте добры.

Аватара пользователя
DeadMazay
Advanced member
Сообщения: 1743
Зарегистрирован: 20 сен 2007, 15:07
Откуда: Новосибирск, Мск
Контактная информация:

Re: Бунт дисковой подсистемы

Сообщение DeadMazay » 11 апр 2010, 12:24

Rikk писал(а): Что происходит с железом? Кто может пояснить? Будьте добры.
может озвучите тогда полный конфиг железа
с уважением Сергей.
ICQ: 365984224

Rikk
Junior member
Сообщения: 4
Зарегистрирован: 10 апр 2010, 22:56
Откуда: SPb

Re: Бунт дисковой подсистемы

Сообщение Rikk » 11 апр 2010, 13:36

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

Copyright (c) 1992-2009 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.2-RELEASE-p4 #1: Thu Oct 22 23:05:22 MSD 2009
------------------------------------------------------------------------
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2667.99-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0xf64  Stepping = 4
  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=0xe4bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,CNXT-ID,CX16,xTPR,PDCM>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 2
  Logical CPUs per core: 2
usable memory = 2126852096 (2028 MB)
avail memory  = 2050531328 (1955 MB)
ACPI APIC Table: <INTEL  S5000PAL>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  2
 cpu2 (AP): APIC ID:  4
 cpu3 (AP): APIC ID:  6
This module (opensolaris) contains code covered by the
Common Development and Distribution License (CDDL)
see http://opensolaris.org/os/licensing/opensolaris_license/
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
lapic0: Forcing LINT1 to edge trigger
kbd1 at kbdmux0
ichwd module loaded
cryptosoft0: <software crypto> on motherboard
acpi0: <INTEL S5000PAL> 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 0x408-0x40b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
acpi_button0: <Power Button> 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 0.0 on pci3
pci4: <ACPI PCI bus> on pcib4
mpt0: <LSILogic SAS/SATA Adapter> port 0x3000-0x30ff mem 0xb8910000-0xb8913fff,0xb8900000-0xb890ffff irq 16 at device 8.0 on pci4
mpt0: [ITHREAD]
mpt0: MPI Version=1.5.12.0
pcib5: <PCI-PCI bridge> at device 0.2 on pci3
pci5: <PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci2
pci6: <ACPI PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> irq 16 at device 2.0 on pci2
pci7: <ACPI PCI bus> on pcib7
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2020-0x203f mem 0xb8820000-0xb883ffff,0xb8400000-0xb87fffff irq 18 at device 0.0 on pci7
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:04:23:d3:cd:e6
em1: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2000-0x201f mem 0xb8800000-0xb881ffff,0xb8000000-0xb83fffff irq 19 at device 0.1 on pci7
em1: Using MSI interrupt
em1: [FILTER]
em1: Ethernet address: 00:04:23:d3:cd:e7
pcib8: <ACPI PCI-PCI bridge> at device 0.3 on pci1
pci8: <ACPI PCI bus> on pcib8
pcib9: <PCI-PCI bridge> at device 3.0 on pci0
pci9: <PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci10: <ACPI PCI bus> on pcib10
pcib11: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci11: <ACPI PCI bus> on pcib11
pcib12: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci12: <ACPI PCI bus> on pcib12
pcib13: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pci13: <ACPI PCI bus> on pcib13
pci0: <base peripheral> at device 8.0 (no driver attached)
uhci0: <Intel 631XESB/632XESB/3100 USB controller USB-1> port 0x40a0-0x40bf irq 23 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 0x4080-0x409f irq 22 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 0x4060-0x407f irq 23 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 0x4040-0x405f irq 22 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
ehci0: <Intel 63XXESB USB 2.0 controller> mem 0xb8c00400-0xb8c007ff irq 23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb4: waiting for BIOS to give up control
usb4: timed out waiting for BIOS
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <Intel 63XXESB USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4
uhub4: 8 ports with 8 removable, self powered
pcib14: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci14: <ACPI PCI bus> on pcib14
vgapci0: <VGA-compatible display> port 0x1000-0x10ff mem 0xb0000000-0xb7ffffff,0xb8b00000-0xb8b0ffff irq 17 at device 12.0 on pci14
drm0: <ATI ES1000 RN50> on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
info: [drm] Initialized radeon 1.29.0 20080528
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,0x40c0-0x40cf irq 20 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
atapci1: <Intel AHCI controller> port 0x40d8-0x40df,0x40f4-0x40f7,0x40d0-0x40d7,0x40f0-0x40f3,0x4020-0x403f mem 0xb8c00000-0xb8c003ff irq 20 at device 31.2 on pci0
atapci1: [ITHREAD]
atapci1: AHCI Version 01.10 controller with 6 ports detected
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci1
ata5: [ITHREAD]
ata6: <ATA channel 4> on atapci1
ata6: [ITHREAD]
ata7: <ATA channel 5> on atapci1
ata7: [ITHREAD]
ichsmb0: <Intel 631xESB/6321ESB (ESB2) SMBus controller> port 0x4000-0x401f irq 20 at device 31.3 on pci0
ichsmb0: [GIANT-LOCKED]
ichsmb0: [ITHREAD]
smbus0: <System Management Bus> on ichsmb0
smb0: <SMBus generic I/O> on smbus0
speaker0: <PC speaker> port 0x61 on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
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]
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
ichwd0: <Intel 63XXESB watchdog timer> on isa0
ichwd0: Intel 63XXESB watchdog timer (ICH8 or equivalent)
ipmi0: <IPMI System Interface> on isa0
ipmi0: KCS mode found at io 0xca2 alignment 0x1 on isa
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc8fff,0xce800-0xcf7ff,0xcf800-0xd07ff on isa0
ppc0: cannot reserve I/O port range
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
WARNING: ZFS is considered to be an experimental feature in FreeBSD.
Timecounters tick every 1.000 msec
ZFS filesystem version 6
ZFS storage pool version 6
acd0: CDRW <TSSTcorpCDW/DVD TS-L462C/AU03> at ata0-master UDMA33
ipmi0: IPMI device rev. 1, firmware rev. 0.2, version 2.0
ipmi0: Number of channels 5
ipmi0: Attached watchdog
ses0 at mpt0 bus 0 target 9 lun 0
ses0: <ESG-SHV. SCA HSBP M11.... 1.41> Fixed Enclosure Services SCSI-3 device 
ses0: 300.000MB/s transfers
ses0: SCSI-3 SES Device
da0 at mpt0 bus 0 target 1 lun 0
da0: <ATA ST3250620NS E> Fixed Direct Access SCSI-5 device 
da0: 300.000MB/s transfers
da0: Command Queueing Enabled
da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
da1 at mpt0 bus 0 target 2 lun 0
da1: <ATA ST3250620NS E> Fixed Direct Access SCSI-5 device 
da1: 300.000MB/s transfers
da1: Command Queueing Enabled
da1: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
da2 at mpt0 bus 0 target 3 lun 0
da2: <ATA ST3250310NS SN05> Fixed Direct Access SCSI-5 device 
da2: 300.000MB/s transfers
da2: Command Queueing Enabled
da2: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
lapic2: Forcing LINT1 to edge trigger
SMP: AP CPU #1 Launched!
lapic6: Forcing LINT1 to edge trigger
SMP: AP CPU #3 Launched!
lapic4: Forcing LINT1 to edge trigger
SMP: AP CPU #2 Launched!
GEOM_LABEL: Label for provider da0a is label/gm0boot.
GEOM_LABEL: Label for provider da0b is label/dump.
GEOM_LABEL: Label for provider da0d is label/rpool0.
GEOM_LABEL: Label for provider da1a is label/gm1boot.
GEOM_LABEL: Label for provider da1b is label/swap0.
GEOM_LABEL: Label for provider da1d is label/rpool1.
GEOM_LABEL: Label for provider da2a is label/gm2boot.
GEOM_LABEL: Label for provider da2b is label/swap1.
GEOM_LABEL: Label for provider da2d is label/rpool2.
GEOM_MIRROR: Component label/gm2boot (device gmboot) broken, skipping.
GEOM_MIRROR: Device mirror/gmboot launched (2/3).
GEOM_LABEL: Label for provider mirror/gmboot is ufsid/49da60f4248e7a43.
GEOM_LABEL: Label for provider mirror/gmboot is ufs/boot.
Trying to mount root from zfs:rpool/BE/fbsd_7_2
GEOM_ELI: Device label/swap0.eli created.
GEOM_ELI: Encryption: AES-CBC 256
GEOM_ELI:     Crypto: software
GEOM_ELI: Device label/swap1.eli created.
GEOM_ELI: Encryption: AES-CBC 256
GEOM_ELI:     Crypto: software
GEOM_LABEL: Label ufsid/49da60f4248e7a43 removed.
GEOM_LABEL: Label for provider md0 is ufsid/4bbf19db2a27ea94.
GEOM_LABEL: Label ufsid/4bbf19db2a27ea94 removed.

Последний раз редактировалось Rikk 13 апр 2010, 01:32, всего редактировалось 1 раз.

Аватара пользователя
DeadMazay
Advanced member
Сообщения: 1743
Зарегистрирован: 20 сен 2007, 15:07
Откуда: Новосибирск, Мск
Контактная информация:

Re: Бунт дисковой подсистемы

Сообщение DeadMazay » 11 апр 2010, 17:16

чекайте диски... и проверьте обновление прошивок на винты... помоему должна быть SN06
с уважением Сергей.
ICQ: 365984224

Rikk
Junior member
Сообщения: 4
Зарегистрирован: 10 апр 2010, 22:56
Откуда: SPb

Re: Бунт дисковой подсистемы

Сообщение Rikk » 12 апр 2010, 00:24

Ок. Попробую глубоко прочекать его. Ужасно не везёт на эти баракуды...

Rikk
Junior member
Сообщения: 4
Зарегистрирован: 10 апр 2010, 22:56
Откуда: SPb

Re: Бунт дисковой подсистемы

Сообщение Rikk » 13 апр 2010, 01:27

DeadMazay, спасибо большое за простой совет. Как говорится, всё гениальное - просто. Перепрошил диск SN06 firmware, ошибки прекратились.

Ответить

Вернуться в «Серверы - Решение проблем»

Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и 23 гостя