Operating System - HP-UX
1751894 Members
4769 Online
108783 Solutions
New Discussion

Re: Several device files missing after ignite recovery

 
Lali
Occasional Contributor

Several device files missing after ignite recovery

Our banking customer asked to do a crash recovery test on an rx3600.

 

Using Ignite-UX for backup / recovery I was not able to log in via ssh.

 

Logging in via the console I relalized /dev/ptmx were missing.

 

It was not restored with recovery and insf did not create it.

 

No errors in "install log" .

 

 

Version C.7.15.254 seems to be okay, but with C.7.16.283  C.7.17.391

 

recovering HPUX 11.31 2011/09 or greater produces all the below device files mising:

 

/dev/beep

/dev/diag/diag2

/dev/echo

/dev/ptmx

/dev/rscsi

/dev/strlog

 

Have anyone experienced this ?

 

HP said this has not been reported / documented yet .

 

 

P.S. This thread has been moved from Integrity Servers to HP-UX > Ignite. - Hp Forum Moderator

 

7 REPLIES 7
Lali
Occasional Contributor

Re: Several device files missing after ignite recovery

Update from HP support at last.

 

Error reproduced by the lab.

 

All pseudo device files are missing after ignite recovery.

 

Seems to be a bug in later IGNITE versions , but it is more likely an 'insf' problem.

 

It happens on servers having the iSCSI-00 bundle installed (!)

 

(ISCSI:

 

Although , not the choice for your HA critical clusters, but our first choice for

 

test and development systems , because its low costs. )

 

Workaround:

 

1. Run insf -C pseudo  after the recovery

 

or

 

2. Remove the iSCSI-00 bundle if you do not need it. (No ISCSI based storage)

 

Customer request waiting for the sw developers a new insf patch:

 

QXCR1001344501: insf -e doesn't create pseudo devices when iSCSI initiator installed

 

No ETA yet.

 

So this is a new issue again for a server with ISCSI stoage configured.

 

The existing ones:

 

1.

When you recover your system with ISCSI storage , you will get

 

'Wrong device files'  errors starting up the ISCSi daemon  during boot.

 

You need to remove both /dev/iscsi and /dev/isw and reboot in order /sbin/init.d/iscsi

 

can recreate the right dsfs.

 

2.

IGNITE recovery is not able to import the volume groups based on ISCSI, because, the initiator

is not started in that phase.

 

 

QXCR1001329058  ER: Support recovery of system using iSCSI for non-root volumes.

 

Customer request is still waiting for the sw developers.

bbsrlubos
Frequent Visitor

Re: Several device files missing after ignite recovery

We had the same problem, when trying to clone rx3600/rx7640 to rx2800i4 using Ignite version C.7.18.63 .

 

Saw a hint on http://stdout-dev-null.blogspot.de/ how to solve "ssh doesn't work after ignite recovery" manually.

 

After reading this thread i searched for a patch for insf.

Installed PHCO_44172 - mksf(1M) cumulative patch on both source machines.

Newly created ignite images were perfectly recovered to new hardware without missing pseudo devices !! 

 

 

Torsten.
Acclaimed Contributor

Re: Several device files missing after ignite recovery

>> clone rx3600/rx7640 to rx2800i4 

 

Make sure you are using to minimum OS release to support the "i4" system and you have all needed drivers installed!

 

 

There is maybe too much difference between these generations.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
bbsrlubos
Frequent Visitor

Re: Several device files missing after ignite recovery

thanks for this hint !

 

We had to update Ignite Server, because install kernel of IGNITE C.7.10.472 did not support family 33 (Poulson) of ia64 !!

 

Source machines have unsopported version (for rx2800i4) of OS :

    HPUX11i-OE-MC B.11.31.0709

 

But needed HWE was already installed :

    HWEnable11i B.11.31.1209.383a

Torsten.
Acclaimed Contributor

Re: Several device files missing after ignite recovery

>> HPUX11i-OE-MC B.11.31.0709

 

This is much too old for sure.

 

Consider to do update-ux to the latest version on the source machine first or do a cold install on the new system.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
bbsrlubos
Frequent Visitor

Re: Several device files missing after ignite recovery

clone is up & running fine

the recommended HWEnable11i does the trick, all HW has state CLAIMED :

 

Class       I  H/W Path        Driver       S/W State   H/W Type     Description
=================================================================================
ext_bus     0  0/0/0/1/0/0/0   ciss           CLAIMED     INTERFACE    PCIe SAS SmartArray P410i RAID Controller
disk        0  0/0/0/1/0/0/0.0.0   sdisk          CLAIMED     DEVICE       HP      LOGICAL VOLUME
disk        1  0/0/0/1/0/0/0.0.1   sdisk          CLAIMED     DEVICE       HP      LOGICAL VOLUME
disk        2  0/0/0/1/0/0/0.0.2   sdisk          CLAIMED     DEVICE       HP      LOGICAL VOLUME
fc          0  0/0/0/3/0/0/0   fcd            CLAIMED     INTERFACE    HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter (FC Port 1)
fc          1  0/0/0/3/0/0/1   fcd            CLAIMED     INTERFACE    HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter (FC Port 2)
fc          2  0/0/0/9/0/0/0   fcd            CLAIMED     INTERFACE    HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter (FC Port 1)
fc          3  0/0/0/9/0/0/1   fcd            CLAIMED     INTERFACE    HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter (FC Port 2)
usb         0  0/0/0/26/0      uhci           CLAIMED     INTERFACE    Intel UHCI Controller
usb         1  0/0/0/26/7      ehci           CLAIMED     INTERFACE    Intel EHCI 64-bit Controller
lan         0  0/0/0/28/0/0/0  iether         CLAIMED     INTERFACE    HP AT101-60001 PCIe 1000Base-T
lan         1  0/0/0/28/0/0/1  iether         CLAIMED     INTERFACE    HP AT101-60001 PCIe 1000Base-T
lan         2  0/0/0/28/2/0/0  iether         CLAIMED     INTERFACE    HP AT101-60001 PCIe 1000Base-T
lan         3  0/0/0/28/2/0/1  iether         CLAIMED     INTERFACE    HP AT101-60001 PCIe 1000Base-T
usb         2  0/0/0/28/5/0/4  uhci           CLAIMED     INTERFACE    HP UHCI Virtual Controller
usbcomp     0  0/0/0/28/5/0/4.1    usbcomposite   CLAIMED     DEVICE       USB Composite Device
usbhid      0  0/0/0/28/5/0/4.1.0  hid            CLAIMED     DEVICE       USB HID Kbd(0)
usbhid      1  0/0/0/28/5/0/4.1.1  hid            CLAIMED     DEVICE       USB HID Pointer(1)
tty         0  0/0/0/28/5/0/5  asio0          CLAIMED     INTERFACE    PCIe Serial (103c3301)
usb         3  0/0/0/29/0      uhci           CLAIMED     INTERFACE    Intel UHCI Controller
usb         4  0/0/0/29/1      uhci           CLAIMED     INTERFACE    Intel UHCI Controller
usb         5  0/0/0/29/2      uhci           CLAIMED     INTERFACE    Intel UHCI Controller
usb         6  0/0/0/29/7      ehci           CLAIMED     INTERFACE    Intel EHCI 64-bit Controller
graphics    0  0/0/0/30/0/3/0  gvid_core      CLAIMED     INTERFACE    PCI Display (1002515e)
ext_bus     1  0/0/0/31/2      satadvd        CLAIMED     INTERFACE    HP PCIe SATA AHCI Adapter
tty         1  0/250/0         asio0          CLAIMED     INTERFACE    Built-in RS232C
ipmi        0  0/250/1         ipmi           CLAIMED     INTERFACE    IPMI Controller
acpi_node   0  0/250/2         acpi_node      CLAIMED     INTERFACE    Acpi Hardware
iscsi       1  255/0           iscsi          CLAIMED     VIRTBUS      iSCSI Virtual Node
usbmsvbus   1  255/1           mass_storage   CLAIMED     VIRTBUS      USB Mass Storage
ext_bus    72  255/1/0         usb_ms_scsi    CLAIMED     INTERFACE    USB Mass Storage SCSI

Torsten.
Acclaimed Contributor

Re: Several device files missing after ignite recovery

OK, but keep in mind using an too old OS release is an unsupported configuration.

 

see

 

http://h20565.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=5330448&docId=emr_na-c03597950&docLocale=en_US

 

Minimum is sept. 2012


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!