Operating System - HP-UX
1834635 Members
3462 Online
110069 Solutions
New Discussion

asio0_init: unexpected SAS subsystem ID (1283)

 
SOLVED
Go to solution
Brian Killeen_4
Occasional Advisor

asio0_init: unexpected SAS subsystem ID (1283)

Hi all,

Recently installed HPUX 11.00 (June 2001 General Releases) on a RP2470 and all was well - We have two HDD and our developers wanted a second clean installation to test on so I installed a second install of the OS on the other drive and use a console to change the boot path. The first time we tried this I first removed the drives to label them. Put them back in and changed the boot path using the PA PRI command. Now I get a software failure on boot with the error message

asio0_init: unexpected SAS subsystem ID (1283)

This on review seems to be to do with the GSP. Have attempted to reset the GSP with no luck. Thought it may have been the drives so tried booting off the original drive to no avail.

Found an article relating to this error but that mentions a patch for an ignite server. This was installed from CD.

Has anyone seen this before as I would prefer not to have to reinstall the OS twice again.

Cheers

Brian
2 REPLIES 2
eran maor
Honored Contributor
Solution

Re: asio0_init: unexpected SAS subsystem ID (1283)

Hi Brian

It looks like if rp24xx revision B GSP firmware C.02.09 is installed, it becomes
to return a new SAS subsystem ID 0x1283. If MUX, PTY (asio0, console driver)
patch PHNE_26326/11.11 or PHNE_27393/11.00 is not installed, the old asio0
cannot recognize the new SAS subsystem id and shows following message in
bootup.

install patch PHNE_26326/11.11 or PHNE_27393/11.00 to solve the problem
love computers
Brian Killeen_4
Occasional Advisor

Re: asio0_init: unexpected SAS subsystem ID (1283)

Eran,

Thanks for your reply - Having run a reset on the GSP the 0/0/1/1.15 drive is now booting. I swapped the drives to allow me install patch PHNE_29519 (recommended MUX & pty patch) on both drives. Still only the drive on the Primary path will boot. If I break the boot by hitting space bar and choose to boot off the alternative drive (0/0/2/1.15) I now get the error

LVM : Failure in attaching PV (0/0/1/1.15.0) to the root volume group.
Cross device link. The disk is not a LVM disk.
LVM : Activation of root volume group failed
Either no physical volumes are attached or no valid VGDAs were found on the phys
ical volumes.
Quorum not present, or some physical volume(s) are missing


It should not be looking for this drive as it is not part of the installation. Remember I have two different installations of HP on two seperate drives. Perhaps it is not possible to have this config although I thought it would be fine...

Hmmmm

Brian