This post is more than 5 years old
10 Posts
0
17599
December 8th, 2011 11:00
iSCSI LUNs Windows 2008 - ps6010e
hi guys
I have virtual Machine that will be used as a Windows 2008 Cluster
Since my SAN is iSCSI I am assigning LUNs for my Virtual Machine the thing is the initial setup in disk management is as below
| Initial Setup |
| Disk 1 - Datos - E |
| Bus Number 0, Target Id 0, LUN 0 |
| Disk 2 - Logs - F |
| Bus Number 0, Target Id 1, LUN 0 |
| Disk 3 - BK - G |
| Bus Number 0, Target Id 2, LUN 0 |
| Disk 4 - TempDB - H |
| Bus Number 0, Target Id 3, LUN 0 |
| Disk 5 - Quorum - Q |
| Bus Number 0, Target Id 4, LUN 0 |
But after I reboot my disk management gets messed up like this
| After Restart |
| Disk 1 - TempDB - H |
| Bus Number 0, Target Id 4, LUN 0 |
| Disk 2 - BK - G |
| Bus Number 0, Target Id 3, LUN 0 |
| Disk 3 - Quorum - Q |
| Bus Number 0, Target Id 0, LUN 0 |
| Disk 4 - Datos - E |
| Bus Number 0, Target Id 1, LUN 0 |
| Disk 5 - Logs - F |
| Bus Number 0, Target Id 2, LUN 0 |
After reboot
any ideas guys how to fix this?
thanks a lot
No Events found!
karlochacon
10 Posts
0
December 8th, 2011 15:00
you know I run the Cluster validation stuff and it says everything is OK so I'm good thanks a lot guys
natsukun4319
2 Posts
0
December 19th, 2011 06:00
Once you enabled the "Automatically restore this connection..." during volume login, and it mapped to your required drive letter, then you can bind it via iSCSI initiator. Then windows try to keep volume online and map same drive letter after system reboot. But it doesn't care drive id. And it is generally not problem for application.