failed to open cdp device

[mkaishar]

problems with storage server had problems with 1 raid controller and storage volume, shutdown starwind, then moved to different volume, tried to add targets back and now I get this error.

failed to open cdp device error code -1073741823
Device test failed
oh and i was on 5.6 and upgraded to 5.7...not sure if that makes a difference?

[Anatoly (staff)]

No, it doesn`t.

I think the most fast way will be to re-create targets, but still, could you described the process of moving of StarWind to another drive - was it all(starwind service and storage-emulating files) on the same drive and it moved to another drive but with the same drive letter assigned?

[mkaishar]

2 raid controllers - 2 volumes, 1 raid controller battery melted (heat issues), lost all accessible volumes to that controller, removed battery, restarted and it found the volumes again, but then it crashed again...so to preserve volumes, I directory and the ibv and supporting files from bad volume to other volume which was stable on the other controller.

I tried to re-add the targets after moving and I got the errors below.

for 1 volume I created a brand new target and brand new .img (no more .ibv) and restored the data from the previous night backup, so that virtual server (running esxi 4.1u1) is back up and running.

i now have 2 other targets that i tried to re-create from ibv files, but same errors as below. I might have to restore those from backup too, unfortunately this is my first setup of using CDP volumes, I usually use basic .img volumes, I decided to use .ibv volumes and CDP and I think the files were corrupted when raid controller crashed a few times.

what does failed to open cdp device error code -1073741823 mean?

[Anatoly (staff)]

Could you provide us withnext files, that you can find in StarWind installation folder:
confiogupdater.log, starwind.cfg and starwin.cfg.bak and StarWind log on the time of the issue (you can find it in /Logs)

[mkaishar]

It was much easier to restore from backup than try to spend time and troubleshoot.
Anyhow this was a test server running the free version, our production is still on 5.6 with .img files

[anton (staff)]

Upcoming versions of StarWind would have CDP implemented on top of de-duplication engine with recovery points written every period of time (pretty much like WAFL except we do it for any file system on top of us). So there should be no issue with incomplete data written to CDP container. Sorry for inconvenience this time