AnsweredAssumed Answered

HORCM Failing to start

Question asked by Fazil Saiyed on Mar 4, 2014
Latest reply on Mar 4, 2014 by Fazil Saiyed


Server windows 2008'

Horcm instant =0 , installed privouly and working in C:\windows\horcm0.

Its setup as windows service and the service fails to stay running, i have rebooted the server

Here is the error

0f0-00012304- [HORCREAD]: maxldev = 16384, unitnum = 256

18:47:09-3c0f0-00012304- [HORCREAD]: maxhorc = 4, maxmrcf = 64, maxlun = 2048, maxctg = 256, maxjnlg = 256, mixport =1, slprflag = 0

18:47:09-3c0f0-00012304- [HORCREAD]: Number of used instance(s) = 8, Number of attached instance(s) = 0, Number of same instance(s) = 3

18:47:09-3c0f0-00012304- [HORCREAD]: RM time:5316740d(Tue Mar 04 18:47:09 2014), SVP time:53161f97(Tue Mar 04 12:46:47 2014), diff:-21622(sec)

18:47:09-3c0f0-00012304- [HORCREAD] execute-test read is done.:\\.\PhysicalDrive5

18:47:09-3c0f0-00012304- Seqnum(230044) of the command device(\\.\PhysicalDrive5) differs from others(25155).

18:47:09-3c0f0-00012304- ERROR:horcm_cfg_create

18:47:09-3c4d8-00012304- [HORCRELOWNLBA] floatable LBA(e003) is released.ID:0:\\.\PhysicalDrive5

18:47:14-343f0-00012392- horcmgr:Failed to connect to HORCM.

 

CMD DEVICES ARE PRESENT:

C:\HORCM\etc>inqraid $Phys -CLI
DEVICE_FILE     PORT    SERIAL  LDEV CTG  H/M/12  SSID R:Group PRODUCT_ID
Harddisk0       -            -     -   -       -     -       - LOGICAL VOLUME
Harddisk1       -            -     -   -       -     -       - LOGICAL VOLUME
Harddisk2       CL4-E    25155 16383   -       -  9150 5:01-01 OPEN-V-CM
Harddisk3       CL4-A    53803 65278   -       -  0102 A:00004 OPEN-V-CM
Harddisk4       CL3-E    25155 16383   -       -  9150 5:01-01 OPEN-V-CM
Harddisk5       CL5-A   230044 16383   -       -  0043 A:00000 OPEN-V-CM
Harddisk6       CL5-A   230044 16381   -       -  0043 A:00000 OPEN-V-CM
Harddisk7       CL5-A   230044 16382   -       -  0043 A:00000 OPEN-V-CM
Harddisk8       CL3-A    53803 65278   -       -  0102 A:00004 OPEN-V-CM

C:\HORCM\etc>raidscan -x findcmddev hdisk0,100
cmddev of Ser#   25155 = \\.\PhysicalDrive2
cmddev of Ser#   53803 = \\.\PhysicalDrive3
cmddev of Ser#   25155 = \\.\PhysicalDrive4
cmddev of Ser#  230044 = \\.\PhysicalDrive5
cmddev of Ser#  230044 = \\.\PhysicalDrive6
cmddev of Ser#  230044 = \\.\PhysicalDrive7
cmddev of Ser#   53803 = \\.\PhysicalDrive8

 

HORCM run file has following amone the rest & horcm0 is valid file

#  ****  For INSTANCE# X, change to HORCMINST=X as needed  ****

START:

set HORCM_EVERYCLI=1

set HORCMINST=0

set HORCM_CONF=C:\windows\horcm0.conf

 

Horcm0 file:

HORCM_CMD

#dev_name               dev_name                dev_name

#UnitID 0 (LDEV# 3F:FF 3F:FD 3F:FE Serial# 230044)

\\.\PhysicalDrive4 \\.\PhysicalDrive5 \\.\PhysicalDrive6

 

I wonder if the whole issue is that after window reboot the drive and ldev number as in horcmo are no longer valid how cmd devices are showing up on the server now

Outcomes