Delete device plus reboot server changes LUN ids
Posted: Wed Apr 09, 2014 2:12 pm
Hello,
In 8.0 RC I have noticed a horrible bug.
I created a target and added 5 devices. These had LUN id from 0-4.
After some time I no longer needed the first device (lun 0) and removed it.
All devices kept their existing LUN id - expected.
However after some days I rebooted the server to install some Windows Updates and suddenly the LUN id was changed for the remaining devices.
This meant:
Lun 1 was now lun 0.
Lun 2 was now lun 1.
Lun 3 was now lun 2.
Lun 4 was now lun 3.
This caused HUGE problems for the VMware ESXi servers connecting to the Starwind server.
Trying to remove the devices or detaching them afterward also causes the management console to crash.
Please tell me this is a bug and you will fix it?
If you have a patch I can apply soon I would deeply appreciate it.
In 8.0 RC I have noticed a horrible bug.
I created a target and added 5 devices. These had LUN id from 0-4.
After some time I no longer needed the first device (lun 0) and removed it.
All devices kept their existing LUN id - expected.
However after some days I rebooted the server to install some Windows Updates and suddenly the LUN id was changed for the remaining devices.
This meant:
Lun 1 was now lun 0.
Lun 2 was now lun 1.
Lun 3 was now lun 2.
Lun 4 was now lun 3.
This caused HUGE problems for the VMware ESXi servers connecting to the Starwind server.
Trying to remove the devices or detaching them afterward also causes the management console to crash.
Please tell me this is a bug and you will fix it?
If you have a patch I can apply soon I would deeply appreciate it.