Already a member?
Sign in
Welcome! This is a website that everyone can build together. It's easy!
03/20/2008 Opps Leads to PSOD and New WS08 DC
I have a confession to make. I was trying to rush through a setup of VCB server on our SAN late last week and ended up reformatting the wrong LUN. Now this was all in our lab so no matter what gets destroyed - it's not the end of the world. But of all the LUNs, this was probably the one that I really didn't want to get reformatted. It had the Domain Controller for the older of our two Windows Server 2003 Domains in the lab. This DC was also the only DNS for that portion of the lab - so DNS was out which was the really annoying part.
It took me about a half a day of investigation to figure out exactly what had happened because that older domain isn't used as much and a weekend passed before anybody complained. At first I thought that the VMFS partition had gotten corrupted, which turned out to be kinda true. The problem was it was me that corrupted it by formatting it with an NTFS filesystem.
After mourning for a few minutes, I decided that this would be a good opportunity to install my first Windows Server 2008 domain. First I straightened out the LUNs and formatted the correct LUN as NTFS and unassigned the initial LUN away from the windows system. I then used the Add Storage option in Virtual Center for the ESX server that I was using to get the LUN reformatted as VMFS. For some strange reason I was then getting an error when I tried to create my new WS08 DC VM on that LUN. So I tried to create it from another ESX server in the same server farm. I had to do a rescan of the storage adapters, but then the storage showed up and everything seemed to work OK.
I used the WS08 RTM ISO to install the new VM, but got an error on reboot of the VM that the installation was corrupt. I did some investigating and found that several ESX systems thought that they still had VMs running from the original LUN before it was formatted NTFS and then reformatted VMFS. This ended up causing a PSOD (Purple Screen of Death - very cool if you haven't see one yet) on one ESX server when I tried to access one of these VMs. It apparently also caused some corruption in the new VM that I was building.
So I went back and did storage adapter rescans on all ESX servers in the farm and made sure that all VMs that were from the LUN that I deleted were removed from inventory. After this my install of the new DC went great.
I have only had two PSODs while working with ESX, this one was caused by me doing something that you really really shouldn't do with your storage. I learned (or maybe learned again) that you should always take your time when you are going to do something like format and make sure you have the right disk!
Todd
It took me about a half a day of investigation to figure out exactly what had happened because that older domain isn't used as much and a weekend passed before anybody complained. At first I thought that the VMFS partition had gotten corrupted, which turned out to be kinda true. The problem was it was me that corrupted it by formatting it with an NTFS filesystem.
After mourning for a few minutes, I decided that this would be a good opportunity to install my first Windows Server 2008 domain. First I straightened out the LUNs and formatted the correct LUN as NTFS and unassigned the initial LUN away from the windows system. I then used the Add Storage option in Virtual Center for the ESX server that I was using to get the LUN reformatted as VMFS. For some strange reason I was then getting an error when I tried to create my new WS08 DC VM on that LUN. So I tried to create it from another ESX server in the same server farm. I had to do a rescan of the storage adapters, but then the storage showed up and everything seemed to work OK.
I used the WS08 RTM ISO to install the new VM, but got an error on reboot of the VM that the installation was corrupt. I did some investigating and found that several ESX systems thought that they still had VMs running from the original LUN before it was formatted NTFS and then reformatted VMFS. This ended up causing a PSOD (Purple Screen of Death - very cool if you haven't see one yet) on one ESX server when I tried to access one of these VMs. It apparently also caused some corruption in the new VM that I was building.
So I went back and did storage adapter rescans on all ESX servers in the farm and made sure that all VMs that were from the LUN that I deleted were removed from inventory. After this my install of the new DC went great.
I have only had two PSODs while working with ESX, this one was caused by me doing something that you really really shouldn't do with your storage. I learned (or maybe learned again) that you should always take your time when you are going to do something like format and make sure you have the right disk!
Todd
Latest page update: made by todd_muirhead
, Aug 5 2008, 1:30 AM EDT
(about this update
About This Update
Moved from: Virtualization Frontier
- todd_muirhead
No content added or deleted.
- complete history)
Moved from: Virtualization Frontier
- todd_muirhead
No content added or deleted.
- complete history)
Keyword tags:
esx
psod
purple screen of death
vcb
virtual center
virtualizaiton
vmware
w2k8
windows server 2008
ws08
More Info: links to this page
| Started By | Thread Subject | Replies | Last Post | |
|---|---|---|---|---|
| scott_hanson | Personal thanks to you ! | 2 | Sep 11 2008, 3:30 PM EDT by scott_hanson | |
 |
Thread started: Mar 21 2008, 11:21 AM EDT
Watch
... and I thought I would be the first to destroy a LUN on our SAN. Yeah ! , free pass for me ... Todd is human ! with all the miracles I've seen you work in the lab and your love of Star Wars, I was beginning to think your were a dark Sith lord !
|
|||