Kernel panic after adding disk

[DD-CC]

Hi there

I'm having problem adding a extra diskarray (A3311A) with 6 new disks to my K220 server running hpux 10.20 on the F/W SCSI. After trying to load the vmunix kernel the kernel panics and the system crashes.
The last thing before the kernel panics was something about scsi id 10/8.7.0, but - I can't recall the message from memory.

I want to add 4 disks on scsi id 10/8.9.0, 10/8.10.0, 10/8.11.0 and 10/8.13.0 and 2 disks on 10/0.9.0 and 10/0.11.0.
I've checkt the scsi id settings on an other server by scanning the scsi bus and the addresses are setup correct. I've also checked the cables and they are ok.

Output from ioscan:

H/W Path Class Description
===============================================
bc
8 bc I/O Adapter
10 bc I/O Adapter
10/0 ext_bus GSC built-in Fast/Wide SCSI Interface
10/0.1 target
10/0.1.0 disk SEAGATE ST318436LC
10/0.2 target
10/0.2.0 disk SEAGATE ST39173WC
10/0.3 target
10/0.3.0 disk SEAGATE ST318436LC
10/0.4 target
10/0.4.0 disk SEAGATE ST318436LC
10/0.5 target
10/0.5.0 disk SEAGATE ST34572WC
10/0.7 target
10/0.7.0 ctl Initiator
10/0.12 target
10/0.12.0 disk SEAGATE ST318436LC
10/0.14 target
10/0.14.0 disk SEAGATE ST39173WC
10/0.15 target
10/0.15.0 disk SEAGATE ST39173WC
10/4 bc Bus Converter
10/4/0 tty MUX
10/4/16 lan HP HP-PB 100 Base TX card
10/8 ext_bus GSC add-on Fast/Wide SCSI Interface
10/8.1 target
10/8.1.0 disk SEAGATE ST318436LC
10/8.2 target
10/8.2.0 disk SEAGATE ST39173WC
10/8.3 target
10/8.3.0 disk SEAGATE ST318436LC
10/8.4 target
10/8.4.0 disk SEAGATE ST318436LC
10/8.5 target
10/8.5.0 disk SEAGATE ST34371W
10/8.7 target
10/8.7.0 ctl Initiator
10/8.12 target
10/8.12.0 disk SEAGATE ST318436LC
10/8.14 target
10/8.14.0 disk SEAGATE ST39173WC
10/8.15 target
10/8.15.0 disk SEAGATE ST39173WC
10/12 ba Core I/O Adapter
10/12/0 ext_bus Built-in Parallel Interface
10/12/5 ext_bus Built-in SCSI
10/12/5.0 target
10/12/5.0.0 tape HP C1537A
10/12/5.2 target
10/12/5.2.0 disk TOSHIBA CD-ROM XM-5401TA
10/12/5.7 target
10/12/5.7.0 ctl Initiator
10/12/6 lan Built-in LAN
10/12/7 ps2 Built-in Keyboard/Mouse
32 processor Processor
34 processor Processor
36 processor Processor
38 processor Processor
49 memory Memory

Is it at scsi address conflict ??
Any idear what I could do ??

Regards
S?ren Dreyer

[Printaporn_1]

Hi ,

Please colect /var/adm/crash and sending to HP Solution Center for analyze.
Or please try install scsi and LVM patches.

Regards,

[Tim Malnati]

You seem to have several threads open on this topic. There are a variety of responses also in http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xe7c56af52b04d5118fef0090279cd0f9,00.html

[Jaimin Parikh]

Hi,

Can you please let me know whether the disk array which you are trying to install on your server is connected externally/internally through a same cable or different one with I/O card?

Please let me know.

Regards,
Jaimin Parikh

[Jaimin Parikh]

Hi,

I mean to ask that whether all the disks of the disk array are physically connected to same I/O card or different I/O cards.I mean to ask how they are oganized and physically connected.

Please reply

-Jaimin Parikh

[Jaimin Parikh]

Hi,

If the disks are sharing the same cable and and connected to only one I/O card than I think that what you are trying will not work.

If setup is different than what I visualise please ignore the message.

Good luck.

Regards,
Jaimin Parikh.

[DD-CC]

Hi, and thanks for the reply

As Tim pointed out this question is also posted under the storage forum, but due to lack of answers (at that time) and impatience I posted it here as well.

The diskarray is an externally rack, and I'm trying to connect 4 disks to F/W scsi I/O on hw address 10/0 and 2 disks on F/W scsi I/O on hw address 10/8 - with two different sets of cables.

When I interact with the bootprocess and do a 'search' for bootable devices all new disks are displayed.

Now, the server is (of cause) an important server so I can't get my hands on it again for at least an other week. At that time I'll try the ODE tool to scan the scsi to see what's on the bus and test the disks.

The diskarray I'm using was running fine on an other server a couple of days ago, so it should be ok. If ODE dosen't show any errors, I'll try anyway to connect the diskarray without disks and boot the server, and then plug in disk by disk (and rebootding each time) to find the sinner-disk.

... or should I try something else ?