XEN issue: UUID of vol changed with v5 to v6 upgrade

[Robotbeat]

It looks to me that the UUID has the SCSI id embedded in it, according to your post:

...
UUID of volume: d64WTF-VB6E-yC3o-1x2o-2EM9-uc9b-EwHZOu
SCSI ID of LUN: VB6EyC3o1x2o2EM9

(emphasis mine)
I wonder if changing the SCSI ID in the open-e gui will change the UUID to coincide?

[silicon]

Good point, maybe. It would take more testing to see what the relationship is between them & what's actually saved in the setup/configuration set. Might wait till the next XEN SAN upgrade to go through that!

[silicon]

Like an idiot I rushed thru this process again with ESX 3.5, swapping-out a DSS v5 DoM, thinking that the UUID issue would not arise (like it did with XEN). But I ended up having to use a v6 demo (the v5 would not run in 32-bit mode correctly), and I totally forgot about the IET->SCST issue. So had to go through the "resignaturing" process for storage definitions - it works, but less than ideal.

So a warning to everyone out there with XEN or ESX hosts - what may look like a simple change/update of DSS version, can bring lots of unexpected effects! Cheers.