Re: Ignite Backup Error Message (1629 Views)
Reply
Frequent Advisor
samarah
Posts: 45
Registered: ‎01-12-2009
Message 1 of 14 (1,667 Views)
Accepted Solution

Ignite Backup Error Message

Good Day!

 

hello, 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.

Honored Contributor
Bill Hassell
Posts: 14,205
Registered: ‎05-29-2000
Message 2 of 14 (1,661 Views)

Re: Ignite Backup Error Message

You have work to do to repair your boot areas. Start with lvlnboot -v and vgdisplay -v. You can't take an Igite backup with disk setup errors, especially with the boot area and vg00.

Frequent Advisor
samarah
Posts: 45
Registered: ‎01-12-2009
Message 3 of 14 (1,659 Views)

Re: Ignite Backup Error Message

Hi Bill, do you have a procedure to fix the error? below is the lvlnboot -v output. Thanks

 

root@hostname[/dev/dsk] lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk1_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk1_p2
Root: lvol3 on: /dev/disk/disk1_p2
Swap: lvol2 on: /dev/disk/disk1_p2
Dump: lvol2 on: /dev/disk/disk1_p2, 0

 

HP Pro
pradeep m
Posts: 154
Registered: ‎12-08-2010
Message 4 of 14 (1,647 Views)

Re: Ignite Backup Error Message

As Bill suggested check the vgdisplay -v output for any pv errors. Also run
# ioscan -fnC disk
# insf -e
Regards,
Pradeep

I am an HP Employee
Frequent Advisor
samarah
Posts: 45
Registered: ‎01-12-2009
Message 5 of 14 (1,642 Views)

Re: Ignite Backup Error Message

Thanks..

here's the output of vgdisplay -v command..

 

root@cspprod[/home/sysops/bin] vgdisplay -v | more
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4356
VGDA 2
PE Size (Mbytes) 32
Total PE 4346
Alloc PE 2848
Free PE 1498
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 2178g
VG Max Extents 69696

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 64
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 3072
Current LE 96
Allocated PE 96
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 320
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 320
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 320
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 320
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 320
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 26624
Current LE 832
Allocated PE 832
Used PV 1


--- Physical volumes ---
PV Name /dev/disk/disk1_p2
PV Status available
Total PE 4346
Free PE 1498
Autoswitch On
Proactive Polling On


VG Name /dev/vgswap
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 2
Open LV 2
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4374
VGDA 2
PE Size (Mbytes) 32
Total PE 4374
Alloc PE 4348
Free PE 26
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 2187g
VG Max Extents 69984

--- Logical volumes ---
LV Name /dev/vgswap/lvswap
LV Status available/syncd
LV Size (Mbytes) 133120
Current LE 4160
Allocated PE 4160
Used PV 1

LV Name /dev/vgswap/lvswap2
LV Status available/syncd
LV Size (Mbytes) 6016
Current LE 188
Allocated PE 188
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c1t0d0
PV Status available
Total PE 4374
Free PE 26
Autoswitch On
Proactive Polling On

Frequent Advisor
samarah
Posts: 45
Registered: ‎01-12-2009
Message 6 of 14 (1,641 Views)

Re: Ignite Backup Error Message

hello,

 

tried to run the ioscan -fnC disk anf insf -e, and re-run the ignite backup... i've still enccountered the error below.

 

ERROR: Unable to open device special file /dev/rdisk/disk56: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk57: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk58: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk59: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk60: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk61: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk62: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk64: Invalid argument (errno = 22). Cannot determine bootability of paths.
ERROR: Unable to open device special file /dev/rdisk/disk94: Invalid argument (errno = 22). Cannot determine bootability of paths.

Acclaimed Contributor
Torsten.
Posts: 23,303
Registered: ‎10-02-2001
Message 7 of 14 (1,632 Views)

Re: Ignite Backup Error Message

Check if there are non-present volume groups still defined in /etc/lvmtab / /etc/lvmtab_p.

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!   
HP Pro
pradeep m
Posts: 154
Registered: ‎12-08-2010
Message 8 of 14 (1,630 Views)

Re: Ignite Backup Error Message

Check if the disks reported in the error message is in CLAIMED state in ioscan output. 

Send the output of the below command for all the disks reported in the error

# scsimgr get_info all_lpt -D /dev/rdisk/<diskname>

# scsimgr get_info -D /dev/rdisk/<diskname>

Regards,
Pradeep

I am an HP Employee
Frequent Advisor
samarah
Posts: 45
Registered: ‎01-12-2009
Message 9 of 14 (1,629 Views)

Re: Ignite Backup Error Message

hi, thanks for the reply, really appreciate it! 

 

as checked, there's lvmtab_p file found in /etc/ but no any entries.

 

root@hostname[/etc] pwd
/etc
root@cspprod[/etc] ls -lrt lvmtab*
-rw------- 1 root sys 28 Jan 26 2011 lvmtab_p
-rw------- 1 root sys 4176 Sep 2 2011 lvmtab

 

root@hostname[/etc] strings /etc/lvmtab_p
root@hostname[/etc] cat lvmtab_p
Ðroot@hostname[/etc] cat lvmtab_p

 

root@hostname[/etc] strings lvmtab
/dev/vg00
/dev/disk/disk1_p2
/dev/vgswap
/dev/dsk/c1t0d0

 

Thanks,

Frequent Advisor
samarah
Posts: 45
Registered: ‎01-12-2009
Message 10 of 14 (1,627 Views)

Re: Ignite Backup Error Message

hi pradeep... below is the output. Thanks

 

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

HP Pro
pradeep m
Posts: 154
Registered: ‎12-08-2010
Message 11 of 14 (1,622 Views)

Re: Ignite Backup Error Message

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.  

Regards,
Pradeep

I am an HP Employee
Frequent Advisor
samarah
Posts: 45
Registered: ‎01-12-2009
Message 12 of 14 (1,615 Views)

Re: Ignite Backup Error Message

Thanks for the help guys... :-) 

 

God Bless.....

Trusted Contributor
jerrym
Posts: 134
Registered: ‎02-12-2008
Message 13 of 14 (1,443 Views)

Re: Ignite Backup Error Message

So what is the fix for this? I have the same problem but I don't care about the old Aglie disk entries after we migrated to new storage. If I try to remove them with rmsf I get the following errors when running make_net_recovery.

 

Before:

 

      * Scanning system for IO devices...
ERROR:   Unable to open device special file /dev/rdisk/disk260: No such device
         or address (errno = 6).  Cannot determine bootability of paths.

 

After:

 

 * Scanning system for IO devices...

ERROR:   Could not determine dsf for device with unique name
         "0x01.0x00.0x03.0x60060480000190105067533030314533".  Cannot determine
         bootabilty of paths.

Acclaimed Contributor
Dennis Handly
Posts: 25,091
Registered: ‎03-06-2006
Message 14 of 14 (1,435 Views)

Re: Ignite Backup Error Message

>So what is the fix for this?

 

I think your problem is different.  These topics imply you must still have the Legacy DFS names:

http://h30499.www3.hp.com/t5/Ignite-UX/Ignite-and-agile-persistent-device-file-support/m-p/5717303

http://h30499.www3.hp.com/t5/Ignite-UX/Latest-ignite-requires-Legacy-devices-on-11iv3/m-p/4781899

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.