Ever run into that nasty and annoying problem with a file server that screams, "I NEED DISK SPACE AND I WANT IT NOW!"
As a Systems Engineer or Admin you know that it is only a matter of time when this happens and not really something you can anticipate. Sure you can track, add quotas and everything else but there is that one project that just pops up and now your file server is crying in its virtual environment somewhere.
So typically this is easy in VMWare where you locate your drive and expand it. If you were proactive you might have two drives, but what happens if you have more? Which disk do you expand? Which is exactly my issue.
As you can see the old Admin did not leave me anything helpful to go by. So I then looked at the Properties of my drive, looking for some information I could use.
And that is where I found my help. Finally something I could use!
The first thing we need to understand is that Bus Number 0 is NOT the equivalent to the Bus Number actually in VMWare. The VMWare Bus Number translates in the Windows "Location" value, so it is a bit misleading. So I did a bit of research and cross-compared to my VMWare environment.
| VMWare Bus Number | Windows Location | |
| older | version 6 | |
| 0 | 160 | 160 |
| 1 | 192 | 224 |
| 2 | 224 | 256 |
| 3 | 256 | 161 |
The Unit Number in VMWare relates to the Target ID in Windows.
For my issue the VMWare disk was on controller 1 or 1:0:0, which I then easily expanded.
No comments:
Post a Comment