How To Understant Which HDD Is Broken And Cause Problem In Command Lines?

I – Problem With RAID Rebuilding Process; Md_checker and  init_lvm.sh Command Doesnt Work, RAID Resync Takes Very Slow Problem

II – How To Understant Which HDD Is Broken And Cause Problem In Command Lines? (for Qnap Technical Guys Only!)

.

I – Problem With RAID Rebuilding Process; Md_checker and  init_lvm.sh Command Doesnt Work, RAID Resync Takes Very Slow Problem

If, After AFR command, init_lvm.sh command stuck;

..and md_checker command stucks;

and RAID rebuildign seems like takes forever, there maybe a broken HDD which cause this problem..

.

II – How To Understant Which HDD Is Broken And Cause Problem In Command Lines? (for Qnap Technical Guys Only!)

1 – Login NAS with putty, and type this command;

[~] # dmesg

.

2  -You’ll realise that broken HDD gives errors.. Check our “ata to drive number table.xlsx“ document about which model ata code means which HDD to identify broken HDD;

.

3 – Also you can understant with typing this command;

[~] # iostat -x 1

Daniel from Qnap Team Report;

“if one disk is always on 100%, and other disks are on 0%, then that disk should be hanging on the I/O request but the more reliable way to check for disk error is by dmesg output and finding the ata error message. you can also see “wait” field is very high, this means the request has no response for a long time”

.

How To Understant Which HDD Is Broken And Cause Problem In Command Lines?Qnap'ı Yavaşlatan Yada Durduran Arızalı Diski Konut Satırlarından Nasıl Anlayabilirsiniz?, 10.0 out of 10 based on 3 ratings