SQL server issue

Hello Guys,

I am new to SQL server, We had this problem and it took long to find out the issue. When we start the SQL server, it didn't start the problem is that drive was on Read-Only mode. We wouldn't find until OS team tell us. Where is the SQL log file locates? Wouldn't it throw any error message or anything on SQL log regading read only mode drive?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
location of the errorlog file:
View the SQL Server error log by using SQL Server Management Studio or any text editor. 
By default, the error log is located at 
Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG and ERRORLOG.n files.

Open in new window

What is read only the hard drive, a database, if a database which one? Your question is very confusing and doesn't provide enough information.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mokkanAuthor Commented:
The file system is mounted using veritas volume manager and  when it mounts,  it mount the drive as read only mode. My question is that if the drive is read only, sql log should show some sort of error message right?
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

If your drive is read only it makes no sense to move to SQL server. It is obvious that your SQL server will not work and beside that it CAN"T write in a log if the drive where the log file resides is read only.

This is an OS issue that has nothing to do with SQL server. Fix it and then you can move aead.
mokkanAuthor Commented:
I totally understand this is OS issue, my question is that what kind of error might caused in sql LOG file ?
mokkanAuthor Commented:
I totally understand this is OS issue, my question is that what kind of error might caused in sql LOG file ?
I don't recall exactly the message and number but when it tries to initialize the databases on a drive that is not accessible or is read only it will throw an I/O error that will mention the database file with full path, including the drive. The same error will also be shown in the Windows Events Log.
mokkanAuthor Commented:
Thank you alll
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.