Operating System - HP-UX
1752586 Members
3855 Online
108788 Solutions
New Discussion юеВ

Re: How do you determine the current boot path/device

 
SOLVED
Go to solution
Bill Hassell
Honored Contributor

Re: How do you determine the current boot path/device

> Jayakrishnan
> I have executed sar & iostat command which shows comparably higher io on the presently used disk than the mirror.

Correct. The mirror is only written during normal operation. All reads will come from the primary.

As far as Itanium, the above procedure mentioned about tracking down the minor number from the adb...bootdev result. As seen in the bootinfo script above, you get the adb results, extract the device number (something like 0x1000004) digits, then search for a match of the minor number in the disk devicefiles.

Not straightforward, but everything about booting in Itanium is convoluted...


Bill Hassell, sysadmin
Torsten.
Acclaimed Contributor

Re: How do you determine the current boot path/device

Usually this can be found in syslog and dmesg (if still not overwritten):



Boot device's HP-UX HW path is: 0/7/1/0/4/0.0.0


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!   
Torsten.
Acclaimed Contributor

Re: How do you determine the current boot path/device

Note: the path in 11.31 is in agile format, e.g.


Boot device's HP-UX HW path is: 0.0.c.1.0.4.0.5000112345678123.4001000000000000

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!   
Travis Harp_1
Advisor

Re: How do you determine the current boot path/device

Bill -
I tried to attached script and I'm getting usage errors.
Here is the output:
bootstring using adb:
Last booted using ioscan: /dev/disk/ is not a special file
ioscan: /dev/disk/ is not a special file
0xffffffff ( or )

Boot disk and AUTO file boot command:

WARNING: The AUTO file is missing in the LIF area!
lifls -l
USAGE: lifls [-C -l -i -v -L -b BlockList] volname[:filename]

boot PATHS:
ioscan: option requires an argument -- H
usage: ioscan [-N] [-k | -u] [-e] [-d driver | -C class] [-I instance] [-H hw_path]
[-l] [-A] [-f | -F[F] [-n]] [devfile]
[-b] -M driver -H hw_path [-I instance]
[-t]
-P [-d driver | -C class] [-I instance] [-H hw_path] [devfile]
-m lun [-F] [-d driver | -C class] [-I instance] [-H lun hw_path] [devfile]
[-F]-m dsf [devfile]
-m hwpath [-F] [-H hw_path]
-s
-r -H hw_path
-B
-U
-a [-F]
-k: show kernel structures; don't scan hardware
-N: show devices present in agile view
-u: show usable devices; don't scan hardware
-e: on IPF systems, show EFI device paths when available;
on PA-RISC systems, show PA device paths when available
-d: show hardware controlled by specified driver
-C: show hardware in specified class
-I: show hardware with specified instance
-H: show hardware at specified path
-f: give full listing
-F: give listing separated by 'separators'
if specified twice (-FF), prints additional fields
-n: show device file names
-l: show only locally connected devices
-t: show date and time of previous hardware scan
or: ioscan [-b] -M driver -H hw_path [-I instance]
-b: force-configure with deferred binding
-M: force-configure specified drivers
-H: force-configure specified hardware path
-A: show the alias_path assigned to the hardware path
-I: force-configure specified hardware instance
or: ioscan -P [-d driver | -C class] [-I instance] [-H hw_path] [devfile]
-P: show property
or: ioscan -m lun [-F] [-d driver | -C class] [-I instance] [-H lun hw_path] [devfile]
-m: show mappings
or: ioscan [-F] -m dsf [devfile]
or: ioscan -m hwpath [-F] [-H hw_path]
or: ioscan -s
-s: show stale entries present in ioconfig files
or: ioscan -r -H hw_path
-r: remove deferred binding flag
or: ioscan -B
-B: list nodes with deferred binding flag set
or: ioscan -U
-U: initiate a scan on unclaimed nodes
-a: shows information about thread 0 for a processor with Hyper Threading feature
ioscan: option requires an argument -- H
usage: ioscan [-N] [-k | -u] [-e] [-d driver | -C class] [-I instance] [-H hw_path]
[-l] [-A] [-f | -F[F] [-n]] [devfile]
[-b] -M driver -H hw_path [-I instance]
[-t]
-P [-d driver | -C class] [-I instance] [-H hw_path] [devfile]
-m lun [-F] [-d driver | -C class] [-I instance] [-H lun hw_path] [devfile]
[-F]-m dsf [devfile]
-m hwpath [-F] [-H hw_path]
-s
-r -H hw_path
-B
-U
-a [-F]
-k: show kernel structures; don't scan hardware
-N: show devices present in agile view
-u: show usable devices; don't scan hardware
-e: on IPF systems, show EFI device paths when available;
on PA-RISC systems, show PA device paths when available
-d: show hardware controlled by specified driver
-C: show hardware in specified class
-I: show hardware with specified instance
-H: show hardware at specified path
-f: give full listing
-F: give listing separated by 'separators'
if specified twice (-FF), prints additional fields
-n: show device file names
-l: show only locally connected devices
-t: show date and time of previous hardware scan
or: ioscan [-b] -M driver -H hw_path [-I instance]
-b: force-configure with deferred binding
-M: force-configure specified drivers
-H: force-configure specified hardware path
-A: show the alias_path assigned to the hardware path
-I: force-configure specified hardware instance
or: ioscan -P [-d driver | -C class] [-I instance] [-H hw_path] [devfile]
-P: show property
or: ioscan -m lun [-F] [-d driver | -C class] [-I instance] [-H lun hw_path] [devfile]
-m: show mappings
or: ioscan [-F] -m dsf [devfile]
or: ioscan -m hwpath [-F] [-H hw_path]
or: ioscan -s
-s: show stale entries present in ioconfig files
or: ioscan -r -H hw_path
-r: remove deferred binding flag
or: ioscan -B
-B: list nodes with deferred binding flag set
or: ioscan -U
-U: initiate a scan on unclaimed nodes
-a: shows information about thread 0 for a processor with Hyper Threading feature
ioscan: Only one devfile allowed
usage: ioscan [-N] [-k | -u] [-e] [-d driver | -C class] [-I instance] [-H hw_path]
[-l] [-A] [-f | -F[F] [-n]] [devfile]
[-b] -M driver -H hw_path [-I instance]
[-t]
-P [-d driver | -C class] [-I instance] [-H hw_path] [devfile]
-m lun [-F] [-d driver | -C class] [-I instance] [-H lun hw_path] [devfile]
[-F]-m dsf [devfile]
-m hwpath [-F] [-H hw_path]
-s
-r -H hw_path
-B
-U
-a [-F]
-k: show kernel structures; don't scan hardware
-N: show devices present in agile view
-u: show usable devices; don't scan hardware
-e: on IPF systems, show EFI device paths when available;
on PA-RISC systems, show PA device paths when available
-d: show hardware controlled by specified driver
-C: show hardware in specified class
-I: show hardware with specified instance
-H: show hardware at specified path
-f: give full listing
-F: give listing separated by 'separators'
if specified twice (-FF), prints additional fields
-n: show device file names
-l: show only locally connected devices
-t: show date and time of previous hardware scan
or: ioscan [-b] -M driver -H hw_path [-I instance]
-b: force-configure with deferred binding
-M: force-configure specified drivers
-H: force-configure specified hardware path
-A: show the alias_path assigned to the hardware path
-I: force-configure specified hardware instance
or: ioscan -P [-d driver | -C class] [-I instance] [-H hw_path] [devfile]
-P: show property
or: ioscan -m lun [-F] [-d driver | -C class] [-I instance] [-H lun hw_path] [devfile]
-m: show mappings
or: ioscan [-F] -m dsf [devfile]
or: ioscan -m hwpath [-F] [-H hw_path]
or: ioscan -s
-s: show stale entries present in ioconfig files
or: ioscan -r -H hw_path
-r: remove deferred binding flag
or: ioscan -B
-B: list nodes with deferred binding flag set
or: ioscan -U
-U: initiate a scan on unclaimed nodes
-a: shows information about thread 0 for a processor with Hyper Threading feature
Primary bootpath = 0/2/1/0.0.0.5.0, /dev/rdsk/c0t5d0
= 0/2/1/0.0x500000e01e463872.0x0, /dev/rdisk/disk1794
= (disk) 64000/0xfa00/0xdd

Alternate bootpath = 0/2/1/0.0.0.6.0, /dev/rdsk/c0t6d0
= 0/2/1/0.0x5000c50004374551.0x0, /dev/rdisk/disk1796
= (disk) 64000/0xfa00/0xe1

HA Alt bootpath = ,
= ,
= ()


Automatic boot settings from setboot:
Autoboot is ON (enabled)


lvlnboot -v:
Bill Hassell
Honored Contributor

Re: How do you determine the current boot path/device

Looks like you need to update your bootable disks. lvlnboot -v is not reporting anything and several parts of the script depend on having valid boot values.


Bill Hassell, sysadmin
Bill Hassell
Honored Contributor

Re: How do you determine the current boot path/device

Also looks like setboot is empty, which means your system won't reboot without interaction.


Bill Hassell, sysadmin