Install an OS Image to Fibre Canel Disk

[Dewa Negara_4]

Hi All,

Please help. I want to install an OS image using DDS3 make_recovery from other server to my N-Class server. The target server only has some Fibre canel disks, but there no internal disk. When I want to install the image to the server, I noticed on 'Hardware Summary' the size of the disks is 0 GB. It seems like the Fibre Canel disks can not be detected. How can I install the OS image to the Fibre Canel disk?

Thanks for your help in advance.
Best Regards,
Negara

[Sridhar Bhaskarla · Accepted solution]

Hi Negara,

There are couple of things you would need to check.

1. Install the latest Ignite/UX on the other box and take the image. Older ignite kernel didn't have fiber channel drivers in them.
2. Make sure you have a reasonably latest PDC firmware on your N-4000. You can check for it in HP's patches site.
3. Make sure the Fiber storage is correctly configured. You may be only seeing the place holder LUNs that are seen with size 0. The description would say "Disk-Subsystem" instead of Disk.

-Sri

[Steven E. Protter]

ioscan -fnC disk

See if the disk on the Fiber channel show up on that list.

If you wish, use sam disk disk devices to check the allocated size of the disks. Anything that shows up there should be included in the recovery image. These should not show up as 0 GB.

use make_tape_recovery if you are writing to tape, make_net_recovery if you are writing to a network Ignite Server.

Sometimes with Ignite you have to delete the client and add it back in at the Ignite server to get it to recognize and communicate with the client.

On one occaision I actually had to boot the client and force the server to push an Ignite image through the network.

At console, I had to interupt at the 10 second prompt and then
bo lan. install

That pushed the kernel, the ignite image and got the hardware configuration, including fiber attached disks to show up right.

Ignite uses the Berkley r-protocols and they need to be enabled in /etc/inetd.conf

server and client.

SEP

[Dewa Negara_4]

Hi Sri,

Thanks for your help. For the item 1: I have tried to get the latest make_recovery from other server (the same class server). The source server is also using Fibre canel disk. So I believe the driver has already been on the image. For item 2 and 3: Actually the target server was running well a few week ago. All fibre canel disks was detected well. After taking out its internal disks, then the server was halted. Now I want to install the image on the fibre canel disk. Need your further help.

Thanks and Best Regards,
Negara

[Dewa Negara_4]

Hi steven,

Thanks for your info. The image hasn't been installed yet. So I can not run any command. When I want to install the image to the target server, on the screen 'Welcome to Ignite UX!', the disk size is shown 0 (0.0GB). So I can not installe the image.

Thanks.
Negara

[Steven E. Protter]

If you are actually using make_recovery, you are a bit out of date on Ignite.

That utility is obsolete and you should take the time to do a make_tape_recovery on one of those servers with the same class.

With everything including the internal disks plugged in you should then be able to do this:

boot the box at the console

interupt at the 10 second prompt

sea


bo p#

replace # with the number on the sea display of the sequential access device(tape)

Then watch carefully, the machine will boot, load a kernel and you'll be able to interupt and configure the machine at an Ignite screen.

This will let you check what disks the machine thinks is connected to it. You can resize the filesystems and do all kinds of customization there.

swlist -l product | grep -i ignite

A version number would be useful here.

SEP

SEP

[Sridhar Bhaskarla]

Hi Negara,

No. Ignite will have it's boot kernel to boot initially the system. It should have the fc drivers in it. make_recovery is pretty outdated. Try installing latest Ignite/UX product and take the image.

What I told you had nothing to do with the OS that you backed up.

-Sri