- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- HP-UX
- >
- Ignite Backup Error Message
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
Ignite Backup Error Message
Question
I'm currently running ignite backup thru network (make_net_recovery), unfortunately i have encountered disk error related. Anyone could help me on this problem.... Appreciate your inputs/help.
* Checking Versions of Recovery Tools
* Scanning system for IO devices...
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210df". Cannot determine bootabilty of paths.
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210e0". Cannot determine bootabilty of paths.
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210e1". Cannot determine bootabilty of paths.
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210e2". Cannot determine bootabilty of paths.
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210ea". Cannot determine bootabilty of paths.
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210eb". Cannot determine bootabilty of paths.
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210ec". Cannot determine bootabilty of paths.
ERROR: Could not determine dsf for device with unique name "0x01.0x00.0x02.0x00173800037210ed". Cannot determine bootabilty of paths.
ERROR: Unable to open device special file /dev/rdisk/disk94: Invalid argument (errno = 22). Cannot determine bootability of paths.
Below is the output from
# scsimgr get_info all_lpt -D /dev/rdisk/<diskname>
# scsimgr get_info -D /dev/rdisk/<diskname>
scsimgr get_info all_lpt -D /dev/rdisk/disk56
STATUS INFORMATION FOR LUN PATH : lunpath67
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
Protocol = fibre_channel
EVPD page 0x83 description code = 1
EVPD page 0x83 description association = 0
EVPD page 0x83 description type = 2
World Wide Identifier (WWID) = 0x00173800037210df
Total number of Outstanding I/Os = 0
Maximum I/O timeout in seconds = 30
Maximum I/O size allowed = 2097152
Maximum number of active I/Os allowed = 8
Maximum queue depth = 8
Queue full delay count = 0
Asymmetric state = ACTIVE/OPTIMIZED
Device preferred path = Yes
Relative target port identifier = 1024
Target port group identifier = 0
STATUS INFORMATION FOR LUN PATH : lunpath34
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
Protocol = fibre_channel
EVPD page 0x83 description code = 1
EVPD page 0x83 description association = 0
EVPD page 0x83 description type = 2
World Wide Identifier (WWID) = 0x00173800037210df
Total number of Outstanding I/Os = 0
Maximum I/O timeout in seconds = 30
Maximum I/O size allowed = 2097152
Maximum number of active I/Os allowed = 8
Maximum queue depth = 8
Queue full delay count = 0
Asymmetric state = ACTIVE/OPTIMIZED
Device preferred path = Yes
Relative target port identifier = 1026
Target port group identifier = 0
STATUS INFORMATION FOR LUN PATH : lunpath90
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
Protocol = fibre_channel
EVPD page 0x83 description code = 1
EVPD page 0x83 description association = 0
EVPD page 0x83 description type = 2
World Wide Identifier (WWID) = 0x00173800037210df
Total number of Outstanding I/Os = 0
Maximum I/O timeout in seconds = 30
Maximum I/O size allowed = 2097152
Maximum number of active I/Os allowed = 8
Maximum queue depth = 8
Queue full delay count = 0
Asymmetric state = ACTIVE/OPTIMIZED
Device preferred path = Yes
Relative target port identifier = 2048
Target port group identifier = 0
STATUS INFORMATION FOR LUN PATH : lunpath118
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
Protocol = fibre_channel
EVPD page 0x83 description code = 1
EVPD page 0x83 description association = 0
EVPD page 0x83 description type = 2
World Wide Identifier (WWID) = 0x00173800037210df
Total number of Outstanding I/Os = 0
Maximum I/O timeout in seconds = 30
Maximum I/O size allowed = 2097152
Maximum number of active I/Os allowed = 8
Maximum queue depth = 8
Queue full delay count = 0
Asymmetric state = ACTIVE/OPTIMIZED
Device preferred path = Yes
Relative target port identifier = 2050
Target port group identifier = 0
root@cspprod[/etc] scsimgr get_info -D /dev/rdisk/disk56
STATUS INFORMATION FOR LUN : /dev/rdisk/disk56
Generic Status Information
SCSI services internal state = UNOPEN
Device type = Direct_Access
EVPD page 0x83 description code = 1
EVPD page 0x83 description association = 0
EVPD page 0x83 description type = 2
World Wide Identifier (WWID) = 0x00173800037210df
Serial number = "130037210DF"
Vendor id = "IBM "
Product id = "2810XIV "
Product revision = "10.2"
Other properties = ""
SPC protocol revision = 5
Open count (includes chr/blk/pass-thru/class) = 0
Raw open count (includes class/pass-thru) = 0
Pass-thru opens = 0
LUN path count = 4
Active LUN paths = 0
Standby LUN paths = 0
Failed LUN paths = 4
Maximum I/O size allowed = 2097152
Preferred I/O size = 2097152
Outstanding I/Os = 0
I/O load balance policy = round_robin
Path fail threshold time period = 0
Transient time period = 120
Tracing buffer size = 1024
LUN Path used when policy is path_lockdown = NA
LUN access type = T10 Symmetric Active-Active
Asymmetric logical unit access supported = Implicit
Asymmetric states supported = ao_sup
Preferred paths reported by device = Yes
Preferred LUN paths = 0
Driver esdisk Status Information :
Capacity in number of blocks = NA
Block size in bytes = NA
Number of active IOs = 0
Special properties =
Maximum number of IO retries = 45
IO transfer timeout in secs = 30
FORMAT command timeout in secs = 86400
START UNIT command timeout in secs = 60
Timeout in secs before starting failing IO = 120
IO infinite retries = false
Answer
From the output, I notice that all the 4 lunpaths to the disk56 is in FAILED state. (Ideal state should be Active or Standby)
Extract from command output:
# scsimgr get_info all_lpt -D /dev/rdisk/disk56
STATUS INFORMATION FOR LUN PATH : lunpath67
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
....
STATUS INFORMATION FOR LUN PATH : lunpath34
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
....
STATUS INFORMATION FOR LUN PATH : lunpath90
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
.....
STATUS INFORMATION FOR LUN PATH : lunpath118
Generic Status Information
SCSI services internal state = UNOPEN
Open close state = FAILED
...
World Wide Identifier (WWID) = 0x00173800037210df
------------------------------------------------------------------------
You may also check the LUN state for other disks(disk57,58,59,60,61,62,64,94) reported in the error message.
I suspect these failed LUN's are causing the issue. fixing this lun issue would all the make_net_recovery to work fine.