baruch / diskscan

Scan disk for bad or near failure sectors, performs disk diagnostics
GNU General Public License v3.0
108 stars 29 forks source link

Create a text user interface #14

Open baruch opened 10 years ago

baruch commented 10 years ago

To make it easier to follow what happens in real-time it would be nice to have a text user interface with the likes of curses to show a continuously screen of updating information where the scan is and the current status.

Baltix commented 10 years ago

Also it would be nice to show current disk temperature (and maybe some other SMART data, like bad/pending sectors count) in user inteface during scan.

baruch commented 10 years ago

I agree. I'm backlogged on this work but showing some more information during the scan will make it more useful.

MasterCATZ commented 7 years ago

it would be nice if the progress bar could stay in the same position how often does it get updated? any way to keep the verbose just showing that last x amount? as we have the logs to see the offsets and ms , or should I just turn verbose off and tail the log?

V: Verbosity set I: Validating path /dev/disk/by-id/ata-WDC_WD30EZRX-00DC0B0_WD-WMC1T2465007 I: Disk start temperature is 37 I: Opened disk /dev/disk/by-id/ata-WDC_WD30EZRX-00DC0B0_WD-WMC1T2465007 sector size 512 num bytes 3000592981504 I: Scanning disk /dev/disk/by-id/ata-WDC_WD30EZRX-00DC0B0_WD-WMC1T2465007 in 512 byte steps I: Scan started at: Tue Apr 25 17:28:47 2017

V: Scanning stride starting at 0 done 0% Disk scan | | ETA: 0h00m00s V: not all read: requested=512 read=0 sense=18

E: Error when reading at offset 0 size 512 read -1, errno=0: Success

E: Details: error=need_retry data=none 06/29/00

V: Scanning at offset 1024 took 1797 msec

V: Scanning at offset 4608 took 1808 msec

V: Scanning at offset 5120 took 1156 msec

V: Scanning at offset 5632 took 1799 msec