Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

CHKDSK on a SAN Volume Expand / Collapse
Author
Message
Posted Friday, February 27, 2009 9:03 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 12:08 PM
Points: 1,080, Visits: 2,880
I need a little direction.
I have a clustered SQL db (Sql 2000 / Win2k).
I have errors in the log for corruption on drive S:\.
This is my backup volume (data and tx logs are on separate vols).
I attempted to run chkdsk but it said it needed to dismount because another process had it in use.
Can I dismount this without taking SQL server down or do I need to stop the SQL server? Just trying to determine if I need to sched a downtime. Thank you.

I was thinking if I shut down SQL Server Agent...nothing would try to use Drive S:\. There are tx log backups happening every 15 mins. ??
Thanks for helping the rookie.
Post #665818
Posted Friday, February 27, 2009 1:32 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 12:08 PM
Points: 1,080, Visits: 2,880
Ok, I've pretty much determined I have to set CHKDSK to run at reboot to get exclusive access. Anyone know how long CHKDSK will take (approx) on a 700 GB volume?
Thanks again
Post #665983
Posted Wednesday, March 4, 2009 3:39 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Saturday, August 23, 2014 10:43 AM
Points: 942, Visits: 1,064
A long time; the Disk management guys at work told me it is usually a good idea to keep disks in chucks of 250GB .. easier to manage and scan and such.

Thanks.


---

Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN.
Microsoft FTE - SQL Server PFE

* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing.


How to ask for help .. Read Best Practices here.
Post #668767
Posted Wednesday, March 4, 2009 3:44 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, October 17, 2014 7:48 AM
Points: 2,040, Visits: 1,667
Also consider that if you let chkdsk do any repairs, and it touches anything in the database files, it will most-likely result in database corruption.

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Post #668768
Posted Thursday, March 5, 2009 6:25 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 12:08 PM
Points: 1,080, Visits: 2,880
YIKES!
Luckily, it is just a volume where backups are stored.
I'll likely move a copy of the backups to another volume and on tape.
I'll verify there is nothing else on this Volume other than backups.
Thanks guys!
Post #669155
Posted Thursday, December 13, 2012 6:51 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, December 21, 2012 5:56 AM
Points: 5, Visits: 12
I know that this topic is a bit old, but I have a very similar question.

Every two weeks we perform server/database maintenance; altering indexes, Windows updates and a server reboot. My issue periodically appears between maintenance weeks with a System error Event ID 55 in the event viewer: "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume XDATA."

This volume is on our SAN and I've determined that I need to perform a CHKDSK since the volume is marked as dirty.

I understand the differences between CHKDSK /F & CHKDSK /R. My question is since I'm not performing a CHKDSK /R should I be worried about database files on this volume if I perform a CHKDSK /F?
Post #1396167
Posted Thursday, December 13, 2012 8:11 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 9:03 PM
Points: 35,347, Visits: 31,884
NMHDBA (12/13/2012)
I know that this topic is a bit old, but I have a very similar question.

Every two weeks we perform server/database maintenance; altering indexes, Windows updates and a server reboot. My issue periodically appears between maintenance weeks with a System error Event ID 55 in the event viewer: "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume XDATA."

This volume is on our SAN and I've determined that I need to perform a CHKDSK since the volume is marked as dirty.

I understand the differences between CHKDSK /F & CHKDSK /R. My question is since I'm not performing a CHKDSK /R should I be worried about database files on this volume if I perform a CHKDSK /F?


Call the SAN vendor and tell them to come fix it or replace it! That kind of corruption should only happen about once every hudred years or so on a SAN.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1396456
Posted Monday, December 17, 2012 6:07 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, December 21, 2012 5:56 AM
Points: 5, Visits: 12
I've talked with the administrator of the SAN and I have asked if there was anything that needed to be done. Although he mentioned that he could update drivers and test various items, he strongly suggested that my issue is with the volume on the SAN and that this would be a job for CHKDSK. He cited that many systems are hosted by the SAN and that they are not experience issues.

I'm not as knowledgeable about the SAN as this person, so I'm not sure what to ask if he insists that I should try a CHKDSK first. What would be your suggestion?
Post #1397218
Posted Thursday, December 20, 2012 2:38 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, October 8, 2014 2:59 AM
Points: 168, Visits: 273
Best thing is build standy by server on same domain, migrate the databases and check for consistency after migration, usually you should have DR solution for critical production databases for covering these kind of issues.

Run checkdsk on original server.


Cheer Satish
Post #1398877
Posted Friday, December 21, 2012 6:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, December 21, 2012 5:56 AM
Points: 5, Visits: 12
Thank you for your reply. This production database performs a FULL back up daily and is restored daily to a separate reporting server. The integrity of the database is OK. I'm confident that this is strictly a issue with my SAN volume.
Post #1399360
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse