This is a suggested improvement. After about 48 hours of disk scan an error was reported about a third of the way through the read verification and further reads stopped. I wanted to interrogate this further by confirming the error on the identified file and block as well as continue scanning the remaining files for read errors. As far as I know, I had no way to find or know the seed used to finish the read verification. My only option is to restart the scan and wait another 32-48 hours...
I suggest that upon failure and exit print out the seed used or include it in the name of the files created as in random-[seed]-00000000.
This is obviously not a mistake I will may twice (hopefully), but since the scans take so long for the large disks in use now, I think this would help new users.
This is a suggested improvement. After about 48 hours of disk scan an error was reported about a third of the way through the read verification and further reads stopped. I wanted to interrogate this further by confirming the error on the identified file and block as well as continue scanning the remaining files for read errors. As far as I know, I had no way to find or know the seed used to finish the read verification. My only option is to restart the scan and wait another 32-48 hours...
I suggest that upon failure and exit print out the seed used or include it in the name of the files created as in random-[seed]-00000000.
This is obviously not a mistake I will may twice (hopefully), but since the scans take so long for the large disks in use now, I think this would help new users.