Qnap Chkdsk

[Charise Farag]

Wheni open qnap web admin page, it notifie me to check FS because is not clean. no problem to access data.

But i have cobian job witch copy data from partition D: to E: (iSCSI Drive)

the job finish (success) with File System errors (Not all folders or files).

i assume that the problem is on this space storage.

I think topology is clear.

I need to know how i can do chkdsk /F on iscsi drive, because when i run it on E: partition, it tell me to unmount drive..i never did this.

can i make this disk offline? if i do it i think it will be not displayed, so i can not run the command !

Now nas qnap has about 14 To of DATA, how can i do the check FS SAFELY ? as reminder, there are two (2) LUNs on it so nas qnap is target iSCSI for ESXi (few VMS not all) and is target iSCSI for windows server.

i need help to understand the best approach to do this operation safely.

Thinks

Thanks for signing up! Keep an eye out for a confirmation email from our team. To ensure any newsletters you subscribed to hit your inbox, make sure to add newsl...@nl.technologyadvice.com to your contacts list.

Now you have two options, work with the original LUN on QNAP or with the copied file, which is essentially a regular binary block device and can be easily converted to a Windows VHDX using free V2V Converter V2V Converter / P2V Converter - Converting VM Formats and mounted as a disk on any Windows machine via double-click.

If chkdsk does not help, try using any partition recovery utility that can recover your partition in-place. Google for in-place partition recovery tools like this one Active@ Partition Recovery restores deleted and damaged volumes and disks. Freeware Data Recovery Software Toolkit .

Full support will expire in 3 months! Limited support will continue unto February 2023. So did you already have plans to upgrade the QTS operating system and plans to replace the hardware before February 2023? And be aware that a QTS direct upgrade to latest stable version might not work. You might need to upgrade in a few steps as there happened some incompatible QTS upgrades inbetween.

Yes. This was handled by fsck on some releases. If the partition is not listed in /etc/fstab, then you will likely need to tell it the partition type. I've used this from a Linux CD to recover a partition Windows wouldn't boot from.

Unfortunately the ntfsfix tool is very limited compared to Microsoft's chkdsk. Try to get a Windows install going - preferably with the newest version of Windows as Microsoft is presumably constantly improving chkdsk (I hope..) New versions of Windows are often available for free as trials. If the problem is in a USB disk you can try installing Windows in something like VirtualBox and give the VM control of the USB device.

+"RAID Seems Unmounted and Mounting Volume Failed; How To Start e2fsck Command And Mount Volume" Document extended;

-seems-unmounted-and-mounting-volume-failed-how-to-start-e2fsck-command-and-mount-volume/?lang=en

+"Qnapcloud UPnP Router Problem; I Can Access NAS Via Cloudlink, But name.myqnapcloud.com Doestn Work?" Document renewed!

-upnp-router-problem-i-can-access-nas-via-cloudlink-but-name-myqnapcloud-com-doestn-work/?lang=en

+"PhotoStation Errors and How To Reinstall Database; Thumbnail Generation Failed A Few Photos, No Folder View And Albums Empty After Firmware, Photo Station Albums Gone, Photostation Not Showing All Files" Document Added;

-errors-and-how-to-reinstall-database/?lang=en

+"Qnap Download Station Stops Working Suddeny And Gives This Error; Download Station Is Currently Offline" Document Added;

-download-station-stops-working-suddeny-and-gives-download-station-is-currently-offline/?lang=en

El cliente estaba usando un servidor Linux conectado a un volumen iSCSI del QNAP como servidor de ficheros. De repente tuvieron un corte de luz y se les apago de golpe el QNAP. Una vez volvi la electricidad, arrancaron el QNAP y vieron que haban varios ficheros que desaparecan y cuando los intentaban crear de nuevo no les dejaba. (Accediendo por Windows.)

De hecho siempre que occura esto y tengamos el volumen ISCSI en Ext2, Ext 3, o Ext4 siempre hay que usar el e2fsck para comprobar y arreglar los ficheros. En caso de que el ISCSI est en formato NTFS, entonces desde Windows tendremos que usar el comando chkdsk /F C: siendo C el volumen daado para compobar y arreglar el volumen iSCSI

Muy til el artculo.

Solo una correcin respecto al comando chkdsk /F, y es que el /F hace alusin a un opcin del comando chkdsk de reparar errores, y no a la letra de la unidad. Por ejemplo: chkdsk /F C: buscaria errores en la unidad C, y como lleva el /F, si los encuentra los intenta corregir. Es una opcin muy potente, a mi me ha salvado en varias ocasiones.

Saludos

3a8082e126