Dotaz: HP Smart array - mptsas - pridani new RAID volume

[PC]

HP Server s SAS radicem. Aktualne 2 disky v mirroru. Instalovan Centos 5.1 x86 - bez problemu.

FSTAB:

/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0

DMESG:

ioc0: SAS1068: Capabilities={Initiator}
scsi0 : ioc0: LSISAS1068, FwRev=00033200h, Ports=1, MaxQ=511, IRQ=233
  Vendor: HP        Model: DF072A8B56        Rev: HPD3
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: HP        Model: DF072A8B56        Rev: HPD3
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: LSILOGIC  Model: Logical Volume    Rev: 3000
  Type:   Direct-Access                      ANSI SCSI revision: 02
SCSI device sda: 142577664 512-byte hdwr sectors (73000 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 08
SCSI device sda: drive cache: write through
SCSI device sda: 142577664 512-byte hdwr sectors (73000 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 08
SCSI device sda: drive cache: write through
 sda: sda1 sda2
sd 0:1:0:0: Attached scsi disk sda

-------------------------------------------------------------------------

Rozhodli jsme se pridat dalsi mirror z 2x147GB disku. Pomoci LSI BIOSu jsme pridali new array. Bez problemu

Start systemu probihal v poradku do okamziku kdy se do konzole zacalo vypisovat:

Apr 25 14:21:28 v1 kernel: mptbase: ioc0: LogInfo(0x31110a00): Originator={PL}, Code={Reset}, SubCode(0x0a00)
Apr 25 14:21:28 v1 kernel: mptbase: ioc0: LogInfo(0x31120400): Originator={PL}, Code={Abort}, SubCode(0x0400)
Apr 25 14:21:29 v1 last message repeated 37 times
Apr 25 14:21:29 v1 kernel: mptscsih: ioc0: attempting task abort! (sc=f6ec4380)
Apr 25 14:21:29 v1 kernel: sd 0:1:1:0:
Apr 25 14:21:29 v1 kernel:         command: Write(10): 2a 00 02 bf 55 8d 00 01 40 00
Apr 25 14:21:29 v1 kernel: mptscsih: ioc0: task abort: FAILED (sc=f6ec4380)
Apr 25 14:21:29 v1 kernel: mptscsih: ioc0: attempting task abort! (sc=c2b3b080)
Apr 25 14:21:29 v1 kernel: sd 0:1:1:0:
Apr 25 14:21:29 v1 kernel:         command: Write(10): 2a 00 02 b7 52 f5 00 00 08 00
Apr 25 14:21:29 v1 kernel: mptscsih: ioc0: task abort: FAILED (sc=c2b3b080)
Apr 25 14:21:29 v1 kernel: mptscsih: ioc0: attempting task abort! (sc=c2b50500)
Apr 25 14:21:29 v1 kernel: sd 0:1:1:0:
Apr 25 14:21:29 v1 kernel:         command: Write(10): 2a 00 02 b7 53 0d 00 00 10 00
Apr 25 14:21:29 v1 kernel: mptscsih: ioc0: task abort: FAILED (sc=c2b50500)
Apr 25 14:21:29 v1 kernel: mptscsih: ioc0: attempting task abort! (sc=f62d2e00)
Apr 25 14:21:29 v1 kernel: sd 0:1:1:0:
Apr 25 14:21:29 v1 kernel:         command: Write(10): 2a 00 02 bf 77 0d 00 00 08 00
Apr 25 14:21:30 v1 kernel: mptscsih: ioc0: task abort: FAILED (sc=f62d2e00)
Apr 25 14:21:30 v1 kernel: mptscsih: ioc0: attempting task abort! (sc=f6eb9200)
Apr 25 14:21:30 v1 kernel: sd 0:1:1:0:
Apr 25 14:21:30 v1 kernel:         command: Write(10): 2a 00 02 bf 77 1d 00 00 38 00
Apr 25 14:21:30 v1 kernel: mptscsih: ioc0: task abort: FAILED (sc=f6eb9200)
Apr 25 14:21:30 v1 kernel: mptscsih: ioc0: attempting task abort! (sc=c2b50680)
Apr 25 14:21:30 v1 kernel: sd 0:1:1:0:
Apr 25 14:21:30 v1 kernel:         command: Write(10): 2a 00 02 c0 f2 e5 00 00 08 00
Apr 25 14:21:31 v1 kernel: mptscsih: ioc0: task abort: FAILED (sc=c2b50680)
Apr 25 14:21:31 v1 kernel: mptscsih: ioc0: attempting task abort! (sc=f6eb9680)

Server uz nenabehl v poradku. Po rebootu opet stejna situace.

Po vyjmuti disku a ponechani konfigurovaneho druheho pole server nabehl zpet do funkcniho stavu po kontrole fs.

Co je spatne? Jak pridat druhy mirror do systemu?

Odpovědi

[Jooky (inactive)]

Kolko diskov mate na SAS radici ? Aky mate firmware ?

Posledna verzia SAS firmwaru ma jeden dost hnusny bug. Pri urcite konfiguracii sa stavaju disky nepristupne (OS hlasi problemy so zapisom, detekovanim, ...). Presne detali si nepamatam, doplnim ked budem pri fy booku. Je na to dokument kde sa to popisuje a aj sposob ako to poriesit.

[PC]

Firmware dle Smart CD 7.9 Aktualne stahuji 8.0 a zkusime jej aplikovat.

Puvodni konfigurace SAS radice: 1xMirror(RAID1) 2x74GB 15k RPM

Nova konfigurace: Mirror #1(RAID1) 2x74GB 15k RPM Mirror #2(RAID1) 2x147GB 15k RPM

[Jooky (inactive)]

Este som sa taku drobnost zabudol opytat. Aky model je ten server ?
Spominana vec sa prejavuje na:

rx2660 with 8-port SAS controller and IR configured
rx3600 with 8-port SAS controller and IR configured
rx6600 with 8-port SAS controller and IR configured

mozno aj dalsich.
V skratke je tam takyto problem:

This only happens to one or two physical disks when one or two IR volumes 
are configured and the IR LUN numbers match the bay number of physical 
disks.  For example, if one IR is configured using disks in bays 7 & 8 and is 
assigned LUN# 5 and then firmware is upgraded to 1.23.33, the physical disk in 
bay 5 becomes non-responsive and cannot be accessed.  An additional IR can 
cause a second disk to be inaccessible if the IRs logical number happens to 
correspond to the bay number of the physical disk.  So, if the second IR is 
assigned LUN# 4, then the disk in bay 4 will not be accessible.

Prejavuje sa u vas toto ?

[PC]

ML 310G5

Ma to 4 bays:

Byly obsazeny 2 pomoci 2x74GB

Ted jsme dosadili 2x147GB a nakonfigurovali druhe pole.

Zajimalo by me co je potreba udelat na strane OS/Linuxu. Pocitam s vytvorenim FS a editaci mountpointu v FSTAB.

Ale pole jako device...v logu je vsude pouze ioc0. Nemel by tam byt nekde i ioc1? Opravu tapu.

Dnes zkusime FW upgrade.