<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Windows server runs chkdsk after moving FC LUN in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91421#M5778</link>
    <description>&lt;P&gt;For a customer I am moving iSCSI and FC LUNs from old aggregates running on DS14 shelves to new SAS drives.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I connect the Windows 2008 server to the new LUN after a snapmirror replication and power on the server chkdsk comes up during initial boot up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I cancel this and log into the server fine and can access the NTFS volume without issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something more I need to do to the LUN to prevent chkdsk from coming up? Do I need to do something on the server itself so it doesn't see the new LUN having a potential issue?&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:27:44 GMT</pubDate>
    <dc:creator>cgeck0000</dc:creator>
    <dc:date>2025-06-05T05:27:44Z</dc:date>
    <item>
      <title>Windows server runs chkdsk after moving FC LUN</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91421#M5778</link>
      <description>&lt;P&gt;For a customer I am moving iSCSI and FC LUNs from old aggregates running on DS14 shelves to new SAS drives.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I connect the Windows 2008 server to the new LUN after a snapmirror replication and power on the server chkdsk comes up during initial boot up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I cancel this and log into the server fine and can access the NTFS volume without issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something more I need to do to the LUN to prevent chkdsk from coming up? Do I need to do something on the server itself so it doesn't see the new LUN having a potential issue?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:27:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91421#M5778</guid>
      <dc:creator>cgeck0000</dc:creator>
      <dc:date>2025-06-05T05:27:44Z</dc:date>
    </item>
    <item>
      <title>Re: Windows server runs chkdsk after moving FC LUN</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91433#M5779</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;You did not state so however, I suspect you are talking about the boot drive on a boot from san devices.&lt;/P&gt;&lt;P&gt;If you run&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;chkntfs /X&amp;nbsp; C:&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; On the source before migration it should prevent checkdisk from running on a dirty shutdown.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Make sure to reset it after migration.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;chkntfs /d&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if it is not causing a problem you may just want to let it run.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;John&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2014 22:43:59 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91433#M5779</guid>
      <dc:creator>olson</dc:creator>
      <dc:date>2014-10-07T22:43:59Z</dc:date>
    </item>
    <item>
      <title>Re: Windows server runs chkdsk after moving FC LUN</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91501#M5782</link>
      <description>&lt;P&gt;Hi Olson,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No, this is not a boot from SAN server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The server itself is an HP 1U DL360 with the C:\ drive on local disks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The LUN is an additional drive connected to the server, S:\ to be exact.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I snapmirror the volume to a new aggr. on new disks, shutdown the server, broke the snapmirror, moved the LUN initiator group to the new LUN, powered on the server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No every time the server boots it want to chkdsk the volume before the server boots up all the way. Just wondering if I need to do something more in this process to prevent this from happening. We have a lot of servers with FC\iSCSI LUNs we need to do this to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Oct 2014 15:05:29 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91501#M5782</guid>
      <dc:creator>cgeck0000</dc:creator>
      <dc:date>2014-10-08T15:05:29Z</dc:date>
    </item>
    <item>
      <title>Re: Windows server runs chkdsk after moving FC LUN</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91509#M5783</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; In that case use snapdrive to map the lun after the system is booted. That should prevent this issue from occuring.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Oct 2014 15:17:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91509#M5783</guid>
      <dc:creator>olson</dc:creator>
      <dc:date>2014-10-08T15:17:31Z</dc:date>
    </item>
    <item>
      <title>Re: Windows server runs chkdsk after moving FC LUN</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91521#M5784</link>
      <description>&lt;P&gt;On the server I did&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;fsutil dirty query s:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And it came back stating the volume was dirty.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did a chkntfs /x s: to stop chkdsk from scanning the volume on boot up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So should I also use SnapDrive to disconnect the LUN\LUNs on the servers before shutting them down?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've done this in the past with iSCSI LUNs and never had this problem. Do you think this may have been a one time anomoly?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else had this issue before?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Oct 2014 15:55:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Windows-server-runs-chkdsk-after-moving-FC-LUN/m-p/91521#M5784</guid>
      <dc:creator>cgeck0000</dc:creator>
      <dc:date>2014-10-08T15:55:10Z</dc:date>
    </item>
  </channel>
</rss>

