[00:32:03] hddscan2 progress: 14.28% :) [00:33:10] wishlist for hddscan3: 1. progress in percent 2. ETA based on the speed in the last 5 minutes [00:33:17] i might be able to implement both [00:41:41] *** Quits: n1s (~n1s@rockbox/developer/n1s) (Quit: Ex-Chat) [02:03:51] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [02:03:51] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [05:28:29] *** Quits: alberthrocks (~alberthro@unaffiliated/alberthrocks) (Read error: Connection reset by peer) [05:45:34] *** Joins: alberthrocks (~alberthro@unaffiliated/alberthrocks) [06:21:56] *** Quits: [7] (~quassel@rockbox/developer/TheSeven) (Disconnected by services) [06:22:04] *** Joins: TheSeven (~quassel@rockbox/developer/TheSeven) [08:03:48] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [08:03:48] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [10:54:07] *** Joins: n1s (~n1s@nl118-168-30.student.uu.se) [10:54:07] *** Quits: n1s (~n1s@nl118-168-30.student.uu.se) (Changing host) [10:54:07] *** Joins: n1s (~n1s@rockbox/developer/n1s) [10:55:37] *** Joins: Kebianizao (~kvirc@95.2.219.87.dynamic.jazztel.es) [12:23:21] *** Quits: Kebianizao (~kvirc@95.2.219.87.dynamic.jazztel.es) (Quit: Estaba usando KVIrc KVIrc Equilibrium 4.2.0, revision: 420, sources date: 20120701, built on: 2013-05-18 09:37:12 UTC 420 http://www.kvirc.net/) [14:03:51] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [14:03:51] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [14:05:02] TheSeven: where does hddscan2 store BBT? does it write it at the end of scanning, or it keeps the current progress somewhere, so the scan can be resumed, if it is interrupted for some reason? [15:28:44] user890104: the BBT is generated at the end of scanning [15:29:06] however in order to save/resume you can take a snapshot of the sector state buffer [15:29:19] the address of that should have been printed to the USB console [15:29:55] but I'd recommend to re-run it anyway after it completes, because during the first one the drive will internally remap stuff in your case (because it hadn't used up all its spares yet) [15:30:24] it might well be that the drive itself manages to fix all problems during the first run, making a BBT unncessary [15:30:51] you should re-check the diagmode counters after hddscan completes [15:31:23] which drive model is it btw? 80gb? [15:50:03] from the stats so far it seems likely that the drive will be able to completely recover the damage itself [20:03:53] *** Joins: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) [20:03:53] *** Quits: clustur (~logger@c-68-53-250-91.hsd1.tn.comcast.net) (Remote host closed the connection) [21:08:02] TheSeven: classic 2g, 120 GB [21:20:31] TheSeven: is it expected to complete much faster, once the bad blocks are remapped? [21:20:47] it didn't hit many bad blocks in the first place [21:21:16] if it finds zero damage, it will read and write the full disk surface 5 times each [21:21:25] so a total traffic of 1200GB [21:21:33] the drive does 20-40MB/s [21:22:02] so under ideal conditions it should complete after ~12h, which it obviously doesn't do in practice [21:56:30] TheSeven: is there a way to find out what is the real uptime of the app? (not cpu time) [21:56:56] no [21:58:25] uhm... *any* uptime? emcore's for example? [21:59:21] i'd like to make a rough estimation of the ETA [22:03:28] irc logs are your best bet [23:13:54] *** Quits: n1s (~n1s@rockbox/developer/n1s) (Quit: Ex-Chat) [23:56:03] *** [Saint] is now known as [Sinner] [23:57:39] *** [Sinner] is now known as [Saint]