Bosch DIVAR 3000 VRM issue

[pacco 0]

Hi,

 

We have a Bosch DIVAR 3000 running version 6.17 and since a month in the VRM dashboard we notice that the storage target is offline (total targets 1, total luns 4, offline targets 1) and we get some weird log entries:

 

Storage 192.168.20.200\0\0 Cannot set VRM lock to LUN (error 0xf037). Devices may be unable to record.

Storage 192.168.20.200\0 Target is offline.

Storage 192.168.20.200\0 Target is available again.

 

So now and then cameras stop recording and we have to reboot the system or restart VRM.

 

Really strange is that the backup DIVAR running an older version and using VSG to record the same cameras also stops now and then.

Log shows:

 

2018-02-07 01:09:27.094;targetId=192.168.20.201\0;Storage;Info;Target is available again.

2018-02-07 01:09:27.094;deviceId=192.168.20.201\0;Storage;Info;0DCC0428 canceling discovery.

2018-02-07 01:09:27.111;diskId=192.168.20.201\0\3;Storage;Info;Storage has 1862 blocks and type 0.

2018-02-07 01:09:27.112;diskId=192.168.20.201\0\0;Storage;Info;Storage has 1762 blocks and type 0.

2018-02-07 01:09:27.112;diskId=192.168.20.201\0\1;Storage;Info;Storage has 1862 blocks and type 0.

2018-02-07 01:09:27.455;diskId=192.168.20.201\0\2;Storage;Info;Storage has 1862 blocks and type 0.

2018-02-07 01:09:35.631;targetId=192.168.20.201\0;Storage;Error;Target is offline (0x3f).

2018-02-07 01:09:35.631;diskId=192.168.20.201\0\0;Storage;Warning;Can't set VRM lock to lun (error 0xf03f). Devices may be unable to record.

2018-02-07 01:09:35.631;diskId=192.168.20.201\0\1;Storage;Warning;Can't set VRM lock to lun (error 0xf03f). Devices may be unable to record.

2018-02-07 09:18:48.522;cameraId=192.168.20.201\1\13;Sender;Warning;VDP allocation failed on Lun: 192.168.20.201\0\1\902

2018-02-07 09:18:48.596;cameraId=192.168.20.201\1\2;Sender;Warning;VDP allocation failed on Lun: 192.168.20.201\0\2\699

2018-02-07 09:19:11.368;targetId=192.168.20.201\0;Storage;Error;Target is offline (0x3f).

2018-02-07 09:19:12.606;targetId=192.168.20.201\0;Storage;Info;Target is available again.

2018-02-07 09:19:12.606;deviceId=192.168.20.201\0;Storage;Info;0C02E8B8 canceling discovery.

2018-02-07 09:19:12.606;deviceId=192.168.20.201\0;Storage;Info;0C02EBD8 canceling discovery.

2018-02-07 09:19:12.606;deviceId=192.168.20.201\0;Storage;Info;0C02EEF8 canceling discovery.

2018-02-07 09:19:12.606;deviceId=192.168.20.201\0;Storage;Info;0C02F218 canceling discovery.

2018-02-07 09:19:13.590;diskId=192.168.20.201\0\0;Storage;Info;Storage has 1762 blocks and type 0.

2018-02-07 09:19:17.274;diskId=192.168.20.201\0\1;Storage;Info;Storage has 1862 blocks and type 0.

2018-02-07 09:19:21.623;targetId=192.168.20.201\0;Storage;Warning;The target has very little storage available (2%). Devices might be unable to record on this target!

2018-02-07 09:19:21.623;deviceId=192.168.20.201\0;Storage;Warning;The system has very little storage available (2%). Devices might be unable to record!

2018-02-07 09:19:23.274;targetId=192.168.20.201\0;Storage;Error;Target is offline (0x3f).

2018-02-07 09:19:23.274;diskId=192.168.20.201\0\3;Storage;Warning;Can't read/set lun type, error 0xf062.

2018-02-07 09:19:23.276;diskId=192.168.20.201\0\2;Storage;Warning;Can't read/set lun type, error 0xf062.

2018-02-07 09:19:23.276;diskId=192.168.20.201\0\1;Storage;Warning;Can't set VRM lock to lun (error 0xf03f). Devices may be unable to record.

2018-02-07 09:19:23.276;diskId=192.168.20.201\0\2;Storage;Warning;Can't set VRM lock to lun (error 0xf03f). Devices may be unable to record.

2018-02-07 09:19:23.277;diskId=192.168.20.201\0\3;Storage;Warning;Can't set VRM lock to lun (error 0xf03f). Devices may be unable to record.

2018-02-07 09:19:25.397;targetId=192.168.20.201\0;Storage;Info;Target is available again.

 

Does anyone know what is going on and how to fix this? We did have a power loss about a moth ago and problems started soon after this power loss.

 

Thanks!

 

Pacco

[mgriff1969 0]

We are having the same issue with a couple IP 6000s. We have 12 of these machines but only a few of them are doing this.

Looks like you could have pulled the logs from our machines, everything is the same word for word. I will continue to monitor this forum and post if I find a fix.

[pacco 0]

We were advised to upgrade to the latest BVMS version, which we will do in 2 weeks.

If anything changes I will post it here.

[pacco 0]

We are having the same issue with a couple IP 6000s. We have 12 of these machines but only a few of them are doing this.

Looks like you could have pulled the logs from our machines, everything is the same word for word. I will continue to monitor this forum and post if I find a fix.

 

We upgraded both DIVARs to the latest BVMS version and errors no longer occur. Looks like both machines should be on the same software level.