Physical drive's Disk Group is not being import after restart (in windows 2003)
Today i would like to share my one experience why my Disk Group in which physically connected drive was not able to import after restart. i have also written a blog in which i was share that my ISCSI SAN drive was not able to import auto after restart. if you want to read that blog see the below link
( https://www-secure.symantec.com/connect/blogs/disk-group-not-importing-automatically-after-restart-windows2003 )
Problem
when I restart the PC the physically connected drive's Disk Group is not being able to import automatically. I had to import it after restart the PC.
Environment
i have windows 2003 server R2 with SF 5.0 installed. Two drives attached with the windows 2003 server PC. One is the boot disk drive and the second is add in the disk group named DiskGroup123.
Experience
when i restart my windows 2003 PC my disk group name DiskGroup123 is not able to import automatically.
Solution1
i just converted the drive from MBR to GPT and now able to successfully import the Disk group after restart the windows 2003 PC. See in the below snaps how to convert the drive from MBR to GPT
Step-1
Step-2
Step-3
Solution2
I just installed Microsoft iscsi initiator version 2.08 and able to view the service ( Veritas DG Delayed Import Service ) and ran the command vxdg -g DGname latestart on and finally able to import the Disk Group automatically after restart.
The Storage & Clustering Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Storage & Clustering community. Any authenticated Connect member can contribute to this blog.
Comments
Thanks for sharing the
Thanks for sharing the information. =)
Please keep in mind that the conversion only works on an empty harddisk.
Also, it usually should occur only for disks over 2TB in size. (Due to MBR limitation)
But as there is no downside to using it as GPT instead, I don't see it as an issue.
Please mark my post as solution to help others also if it resolved your issue.
Kim this is an issue !!!! 2nd
Kim this is an issue !!!! 2nd thing my hard disk drive is not over 2TB
Thanks
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
I agree that the actual issue
I agree that the actual issue of not auto-importing MDR disks for your environment is a problem.
But using GPT instead of MBR is not an issue in most cases. (As Windows 2003 sees both)
We can definitely try and find out why it won't auto import if you open a support case with us.
I expect it to be most likely environmental but we won't know for sure until we go through the logs / environment in more detail.
Please mark my post as solution to help others also if it resolved your issue.
Jay kim i respect your
Jay kim i respect your words/comments but i temporarily resolved this issue by the way which i mentioned but i again said its temporarily. But the good thing is that the problem is now resolved. Please view the below article which helped me to solve this problem.
https://www-secure.symantec.com/connect/forums/aft...
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
Alebrta
Your blog is very useful. Thank you so much for providing plenty of useful content. I have bookmark your blog site and will be without doubt coming back. Once again, I appreciate all your work and also providing a lot vital tricks for your readers.
Would you like to reply?
Login or Register to post your comment.