[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ssag::ask_ssag

Title:	Ask the Storage Architecture Group
Notice:	Check out our web page at http://www-starch.shr.dec.com
Moderator:	SSAG::TERZAN

Created:	Wed Oct 15 1986
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6756
Total number of notes:	25276

6430.0. "NOSUCHDEV when mount disk during boot" by HGOVC::CHIKAICHEUNG () Wed Feb 26 1997 23:12

	One of our customer got 3 alpha 8000, one use XMI CI adapter while 
the other two use PCI CI adapter and they all run VMS V6.2-1H3. Most of the 
disks are under HSJ40 controller.

	For those 8000 with PCI CI adapter, everything works fine but for 
the one with XMI CI adapter, when mounting disks under HSJ40 controller in 
the startup process, some of the disks will not be available during mount 
and the mount command will fail. Those disks that are unavailable during 
mount are not always the same, sometimes under this channel and sometimes 
under the other channels. Customer had moved the mount commands to the last 
minute of the bootup procedure but still got the error although the chance 
is much less.

	This is really a timing problem for the system to recognise all the 
disk devices but our customer would like to know what exact amount of delay 
should they add. They don't just want to have a trial and error testing as 
the machines are for production and the availability of all the disks 
before starting application is a major concern for them.

	Could anyone help to provide some data on this matter or any 
pointer that I can look for?

thanks & regards,
ck
    
    Cross posted in HSJ_PRODUCT.

T.R	Title	User	Personal Name	Date	Lines
6430.1	Check SYS$EXAMPLES:CLU_MOUNT_DISK.COM	COOKIE::FROEHLIN	Let's RAID the Internet!	`Thu Feb 27 1997 10:46`	1

6430.2		HGOVC::CHIKAICHEUNG		`Thu Feb 27 1997 18:27`	7
	re: .1 But how about if one of the disk is really dead, then the system will just loop there forever waiting to mount the disk when booting. regards, ck
6430.3	MSCP CONFIGURE Process Delay?	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Fri Feb 28 1997 08:46`	13
	MSCP requires the insertion of a wait command, to allow time for the CONFIGURE process to detect and configure MSCP devices found throughout a VMScluster. I'd suspect this delay may be what you are running into... If you need a tool that can handle disk devices appearing throughout a VMScluster, you can customize SYS$EXAMPLES:MSCPMOUNT.COM -- this procedure can be invoked as a one-shot, or can run as a detached job at x-minute intervals. (There's apparently a DISKMOUNT.C program available that mounts disks rather faster... Next step: get MSCPMOUNT to use DISKMOUNT. :-)