Operating System - Tru64 Unix
1748117 Members
3700 Online
108758 Solutions
New Discussion юеВ

Can't connect a disk enclosure.

 
SOLVED
Go to solution
Yves Sevigny
Occasional Advisor

Can't connect a disk enclosure.

Hello ,
I am trying to connect DS-BA356 disk shelf in my Alphaserver DS20 (Tru64 5.1B). The SCSI card is KZPBA-CA (single ended).

When I boot in Console mode, the system sees the BA356 and the disks.
When I boot the OS, a SCSI event 700 appears and loops with messages like:
Unable to allocate contig memory for console firmware usage.
Contig Malloc: Cannot find memory in saved list.

I do a control-C, and the the OS boots.

In the kern.log, i have the following messages:

May 25 09:30:08 sapdev vmunix: hwc_check_devnode: block devt (0x05100a80) already in use by hwid 108:re-use requested by cdisk for h
wid 109
May 25 09:30:08 sapdev vmunix: hwc_check_devnode: char devt (0x05100a80) already in use by hwid 108:re-use request by cdisk for hwid
109
May 25 09:30:08 sapdev vmunix: unable to register devnode status= 95


May 25 09:30:09 sapdev vmunix: vm_swap_init: swap is set to eager allocation mode
May 25 09:30:09 sapdev vmunix: isp0 at pci4 slot 0
May 25 09:30:09 sapdev vmunix: contig_malloc: cannot find memory in saved list
May 25 09:30:09 sapdev vmunix: cam_logger: SCSI event packet
May 25 09:30:09 sapdev vmunix: cam_logger: bus 4
May 25 09:30:09 sapdev vmunix: isp_get_console_image
May 25 09:30:09 sapdev vmunix: Unable to allocate contig memory for console firmware image
May 25 09:30:09 sapdev vmunix: cam_logger: SCSI event packet
May 25 09:30:09 sapdev vmunix: cam_logger: bus 4
May 25 09:30:09 sapdev vmunix: isp_init
May 25 09:30:09 sapdev vmunix: Unable to read back firmware from chip
May 25 09:30:09 sapdev vmunix: cam_logger: SCSI event packet
May 25 09:30:09 sapdev vmunix: cam_logger: bus 4
May 25 09:30:10 sapdev vmunix: isp_init

Q: anyone had this problem?
Q: Do I have to rebuild the kernel?

Desperatly yours,
Yves
7 REPLIES 7
Ivan Ferreira
Honored Contributor
Solution

Re: Can't connect a disk enclosure.

If the SCSI adapter was also installed, you should recompile the kernel. I would start by recompiling the kernel anyway.

Ensure that the firmware is current, boot from your Firmware CD and run:

verify

Check that everything passed the test.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
VINCENT, Jean-Marc
Valued Contributor

Re: Can't connect a disk enclosure.

Hi Yves,

Driver isp is needed for KZPBA.

So, you should add the following line in you /sys/conf/$HOSTNAME config file, rebuild your kernel, save old kernel, move new kernel to / and reboot:

# Static Driver Definitions
...
config_driver isp

VINCENT Jean-Marc
HP France
Groupe Support Unix
Tru64(tm) UNIX Technical Consultant - Tru64(tm) UNIX Ambassador HP France
+33 1 5762-8861
jean-marc.vincent@hp.com
Vladimir Fabecic
Honored Contributor

Re: Can't connect a disk enclosure.

Jean-Marc is right.
Did you try to boot the machine with genvmunix kernel?
In vino veritas, in VMS cluster
Yves Sevigny
Occasional Advisor

Re: Can't connect a disk enclosure.

Thanks for your replies.

I have not tried rebuilding the kernel yet and will include the isp_init entry.

I will try to schedule a shutdown for today
or Tuesday.

Thanks again and will keep you informed.

Yves
Yves Sevigny
Occasional Advisor

Re: Can't connect a disk enclosure.

Hello all,

as recommended, I booted with /genvmunix, rebuilt the kernel, and Bingo! No more errors, the devices were created and was able to configure my disks.

Thank you all for your help,

Yves
Hein van den Heuvel
Honored Contributor

Re: Can't connect a disk enclosure.

Thanks for your feedback!
It's good to hear this problem is resolved.

You may want to 'close'/'lock' this topic and assign 'points' to those that helped

http://forums1.itrc.hp.com/service/forums/helptips.do?#28

Regards
Hein.
[ 0 points for this please ]
Yves Sevigny
Occasional Advisor

Re: Can't connect a disk enclosure.

Proposed solution resolved the problem.