SQL Server keeps losing drive letter

hongedit
hongedit used Ask the Experts™
on
Hi

This is a virtual server, that until today had no problems I am aware of.

I have the OS installed on C and a seperate virtual drive for the actual DB (B:\)

Everytime I reboot the DB Drive is missing its drive letter. Even after I reassign it, I cannot start the SQL service - error in eventlog:

Log Name:      Application
Source:        MSSQLSERVER
Date:          16/05/2011 14:45:38
Event ID:      17053
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Saints-SQL.Saints.local
Description:
FCB::ZeroFile(), GetOverLappedResult(): Operating system error 19(failed to retrieve text for this error. Reason: 15105) encountered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSSQLSERVER" />
    <EventID Qualifiers="49152">17053</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-05-16T13:45:38.000000000Z" />
    <EventRecordID>6947</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Saints-SQL.Saints.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FCB::ZeroFile(), GetOverLappedResult()</Data>
    <Data>19(failed to retrieve text for this error. Reason: 15105)</Data>
    <Binary>9D420000100000000B0000005300410049004E00540053002D00530051004C00000000000000</Binary>
  </EventData>
</Event>
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Is that the letter B:

A: and B: are sometimes reserve for floppy disk drives.

Have you removed the floppy disk drive from the virtual machine.

Have you tried a different drive letter?

Author

Commented:
Yes, that is the letter B.

I dont understand, it worked fine for a week. Just noticed it today that it wasnt working.

I will try removing the floppy disk.

I could change the letter, but I am unsure how to tell SQL where to look for the database if i do so
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
So if you got into Disk Management, the Drive is not assigned A letter?
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Well, removing floppy didnt work.

The first time I checked this out, Disk Management listed the Drive as offline.

So I right click, select Online, and give it the driver letter back.

Now, everytime I reboot, the drive stays online but the drive letter is missing.

Even after I give it a drive letter back, SQL will not start.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
I would recommend using drive letters that are reserve A: and B:.

I've never known anyone ever use Drive A: or Drive B:, usually drives letters are used after the first fixed disk C:.

e g. D:

Yes, it's because the drive probably needs to be available to SQL at boot-up, at service start, as the disk is missing, SQL cannot start.

an article here about moving SQL disks

http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/5c0e5ba5-1e1a-4c38-ac92-3e5c50ac6c7b/

Author

Commented:
There is one big problem - I cannot start Managment Studio to move the DB's to a new drive letter!
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
have you re-assigned the drive letter as B:

and SQL doesn't start?

Author

Commented:
Correct
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
If you cannot get SQL started, you are probably going to have to copy and move the data separately.

and follow this...

http://www.psoft.net/HSdocumentation/sysadmin/mssqlchangehome.html

but the issue you have is the B:, and it may be better to build a new server. and install SQL on C: or D: etc

Author

Commented:
I dont think its the B causing the issue.

I reassigned it as J, rebooted, still lost the drive letter!
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
You've not got the Virtual Machine Disk set to Non-Persistent for the VM?

Author

Commented:
Nope
Commented:
Fixed.

I created a new VDisk, copied the contents over, assigned it letter B, service started...

Something wrong with the original VDisk...
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
I would sanity check your environment.

Something is not right.

Author

Commented:
I agree, its driving me mad.

I dont even know where to start though.

Author

Commented:
Thanks

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial