A confab with HP tech support resolved it.
     
This can happen if you have AdvFS volumes served by ASE and someone (e.g. 
myself) has gone in and modified the AdvFS volume (e.g., moved it to another 
disk) and hasn't bothered to reconfig the service in asemgr (duh, sorry).  It 
will work fine until you reboot, then it will go away and never come back.  In 
the daemon.log detail below, "rz16c" is the disk that the domain was mounted on 
previously - the disk no longer exists and thus couldn't be reserved.
     
The way to fix (or prevent) it is to go into asemgr and modify the service by 
selecting "Modify the AdvFS domain information".  As soon as you go in, it will 
detect the change and ask you to confirm it.  Do so and then start the service 
and it will come up fine.
     
Original message follows:
     
When we rebooted one of our 4.0E systems, one of the AdvFS domains 
didn't come back.  No domain panic, disks all look fine, nothing in the 
messages or syslog.dated files at all, until it tried to mount it in ASE 
as an NFS service, then it gave me the following:
     
Jan  8 18:04:49 biosta ASE: biostai Agent Notice: starting service nfs00 
Jan  8 18:04:49 biosta ASE: biostai Agent Notice: didn't reserve device 
Jan  8 18:04:49 biosta ASE: biostai Agent Error: can't open device file 
/dev/rrz16cInvalid argument
Jan  8 18:04:49 biosta ASE: biostai Agent Warning: can't reserve 
/dev/rz16c
Jan  8 18:04:49 biosta ASE: biostai Agent Error: can't unreserve device 
Jan  8 18:04:49 biosta ASE: biostai Agent Error: can't unreserve device 
/dev/rz16c
     
But I suspect these are all beside the point and because the domain was 
already history.  Even the link in /etc/fdmns is gone.  It was working 
just fine until the reboot, in fact I have a sys_check from a couple of 
hours before - here is the pertinent bit (the domain is called 
domain00):
     
showfdmn 
     
     
               Id              Date Created  LogPgs  Domain Name
3dfb79cd.000c23c9  Sat Dec 14 13:34:53 2002     512  domain00
     
  Vol   512-Blks        Free  % Used  Cmode  Rblks  Wblks  Vol Name 
   1L  355486275   196390896     45%     on    256    256  /dev/rz17a
     
Output of chvol /dev/rz17a volume: 
     
rblks = 256  wblks = 256  cmode = on, thresh = 16384
     
Output of showfsets domain00 domain: 
     
shared
        Id           : 3dfb79cd.000c23c9.1.8001
        Files        :     3401,  SLim=        0,  HLim=        0 
        Blocks (512) : 159027584,  SLim=        0,  HLim=        0 
        Quota Status : user=off group=off 
     
     
Output of BMT showfile domain00 domain: 
     
Output of showfile -x M-6 for domain00 domain: 
     
     
         Id  Vol  PgSz  Pages  XtntType  Segs  SegSz  I/O   Perf  File
fffffffa.0000    1    16    898    simple    **     **  ftx   100%  M-6
     
    extentMap: 1
        pageOff    pageCnt     vol    volBlock    blockCnt
              0          2       1          32          32 
              2        896       1       51744       14336
        extentCnt: 2
     
     
All looks fine to me.  But where did it go?  I could give it a name and 
then try a verify but I am a bit loath to start down this road until I 
can figure out what happened.  Any ideas?  I will summarize to the list.
     
     
     
Thanks
John
     
John Speakman - Manager, Clinical Research Systems
Division of Biostatistics, Memorial Sloan-Kettering Cancer Center, 1275 
York Avenue, New York, NY 10021, USA
Phone: 212 639 8443 / Fax: 212 794 5824 / E-mail: 
speakman_at_biost.mskcc.org
     
     
************************************************************ 
Please  note that this  e-mail and  any  files  transmitted 
with it are  privileged, confidential, and   protected from 
disclosure under applicable law.  If  the  reader  of  this 
message is  not the intended  recipient, or  an employee or 
agent  responsible  for  delivering  this  message  to  the 
intended   recipient,  you  are  hereby  notified  that any 
reading, dissemination,  distribution,  copying,  or  other 
use of this communication  or  any  of  its  attachments is 
strictly prohibited.
If  you  have  received this communication in error, please 
notify  the  sender immediately by replying to this message 
and  deleting this message, any attachments, and all copies 
and backups from your computer.
************************************************************
     
     
     
     
************************************************************
Please  note that this  e-mail and  any  files  transmitted
with it are  privileged, confidential, and   protected from
disclosure under applicable law.  If  the  reader  of  this 
message is  not the intended  recipient, or  an employee or
agent  responsible  for  delivering  this  message  to  the 
intended   recipient,  you  are  hereby  notified  that any
reading, dissemination,  distribution,  copying,  or  other 
use of this communication  or  any  of  its  attachments is 
strictly prohibited.
If  you  have  received this communication in error, please 
notify  the  sender immediately by replying to this message 
and  deleting this message, any attachments, and all copies 
and backups from your computer.
************************************************************
Received on Thu Jan 09 2003 - 04:22:33 NZDT