Announcement

Collapse
No announcement yet.

Running CHKDSK on a SAN.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Running CHKDSK on a SAN.

    Hi,

    I've been running into a weird issue with a server. The server is connected to a SAN and once in a while the server will lock up and the server freezes. Everything on the server stops responding (the server still ping though).

    I've ran a checkdisk on the SAN to see if the filesystem was fine and i got this error:

    The type of the file system is NTFS.
    The volume is in use by another process. Chkdsk
    might report errors when no corruption is present
    Volume label is DRIVE.
    WARNING! F parameter not specified.
    Running CHKDSK in read-only mode.
    CHKDSK is verifying files (stage 1 of 3)...
    1784656 file records processed.
    File verification completed.
    1078 large file records processed.
    0 bad file records processed.
    3876 EA records processed.
    0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    Deleting an index entry from index $O of file 25.
    An unspecified error occurred.

    I'm wondering if i should expect this error while running checkdisk on a SAN currently in use. Also, Do you think this could be the source of the server lockup ?

    Best regards,

    trep

  • #2
    Re: Running CHKDSK on a SAN.

    it may impact your server, try running "chkdsk /r" from the comand line, hit yes and reboot.
    WARNING this can take a loooooooong time depending on the size and speed of your equipment (do not reboot if you lack the patience, take a nap...)
    The errors above still exist since you ran it in read only mode.
    "...if I turn out to be particularly clear, you've probably misunderstood what I've said” - Alan Greenspan

    Comment


    • #3
      Re: Running CHKDSK on a SAN.

      one more thing.......
      you can specify just the SAN drive, the above will do all drives.
      chkdsk g: /r
      "...if I turn out to be particularly clear, you've probably misunderstood what I've said” - Alan Greenspan

      Comment


      • #4
        Re: Running CHKDSK on a SAN.

        have you run any performance monitors on the SAN at all, or the server ?

        See if you can find out what's making the disk queue long
        Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

        Comment


        • #5
          Re: Running CHKDSK on a SAN.

          Hi,

          DRIVE is actually the SAN volume.

          For safety reason, i think i'll just move all the DATA elsewhere and then run the chkdsk. If filesystem corrution occurs i won't be in trouble. But since the data will be moved, i'd rather rebuilt the RAID as well. I'm going to also run some physical tests on the disks if the options are available on the SAN.

          I also ran performance monitor on the SAN and found some softwares causing long queue lenght. Undelete was causing this. I changed the settings a bit but still need to run another performance monitor to compare. I will probably disable that service for a period of time to see if things are going away.

          Best regards,

          trep

          Comment


          • #6
            Re: Running CHKDSK on a SAN.

            by move I assume you mean copy otherwise there is nothing for chkdsk to check.
            "...if I turn out to be particularly clear, you've probably misunderstood what I've said” - Alan Greenspan

            Comment


            • #7
              Re: Running CHKDSK on a SAN.

              Yea well, if we move/copy the data elsewhere and move the production on this, there's no need to run the chkdsk anymore hehe (for curiosity maybe)

              Comment

              Working...
              X