While investigating reports of corrupt files on the E: volume of a Windows Server 2019 file server, you find hundreds of NTFS Event ID 55 errors that state "The file system structure on the disk is corrupt and unusable." The RAID-10 virtual disk shows an optimal state in the hardware management utility, and SMART information for all member drives is clean. You need to confirm and repair any logical file-system corruption without taking the volume offline during business hours. Which command should you run first?
Use diskpart and issue the clean command on the virtual disk
Execute fsutil dirty set E: to schedule a file-system check at next boot
Run chkdsk E: /f /r and reboot the server
Run chkdsk E: /scan from an elevated command prompt
NTFS Event ID 55 indicates logical file-system corruption. The safest initial step is an online, read-only check that keeps the volume mounted. The command "chkdsk E: /scan" performs an online scan that detects (and on Server 2019 can repair minor) NTFS inconsistencies while the volume remains available.
Running "chkdsk E: /f /r" would attempt full repair and bad-sector recovery but requires the volume to be dismounted or the server to reboot, which does not meet the requirement to stay online.
"fsutil dirty set E:" merely marks the volume dirty so that a full chkdsk runs at the next reboot; it does not immediately verify or repair the corruption.
"diskpart clean" would erase the partition table and destroy all data, which is not a troubleshooting step for logical corruption. Therefore, "chkdsk E: /scan" is the correct first action.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.