BleachBit error after wipe free space

Forums: 

An error message popped up after wiping my 2TB SATA 6.0GB/s 64Mb cache HDD on Windows 7 64bit Ultimate SP1. It ran all the way to 0 then when it finished at 0% it popped up saying I/O error 112 Error:112. I clicked OK and BleachBit reported not responding and a few seconds later the same messaged popped up and it repeated itself until I just closed off BleachBit. I don't know what the bug is and nothing seemed to have went wrong with the wipe.

ROCKNROLLKID's picture

I seemed to have found something interesting. I am unknown if this is BleachBit fault or the error, but I checked a file recovery tool to see if BleachBit successfully wiped free space. I still have files recoverable dating back to 10/16/2013 all the way to time of post. there are a lot of files still recoveible. I used Kickass undelete, the one built into performance maintainer, which is found here: http://sourceforge.net/projects/pcsm/ Install the tool and install the tool in it that says undelete, then run bleachbit full clean up with latest winapp2, with wipe enabled and free space wipe along with it. After its done run the undelete tool and it still detects recoverable files, at least for me. This is not the first time I have ran BleachBit wipe free space, I believe the last time I ran it was a few months ago. Do I need to restart then run undelete and all the files will not be recoverable as I have not done that yet since I ran the wipe?

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

ROCKNROLLKID's picture

I just ran Recuva from Piriform and the same results happened so it isn't the tool, it seems to be BleachBit.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

Thank you for the report. I'll check into it.

Are you running Recuva and Kickass on the C: drive? Your hard drive is partition as one logical drive (in other words, no D: drive)? Also, I assume you are not referring to any external drive.

---
Andrew, lead developer

Did you check the file contents or just the file name?

Did you verify you are using BleachBit to wipe the right partition?

I created a 60MB NTFS test partition and filled it with images. Then I deleted them all using Windows Explorer, bypassing the trash can. They were all recoverable (as expected).

Then I used Bleachbit "wipe free disk space" on this drive and reran Recuva. Recuva showed a few files as recoverable in an "excellent" state with "no overwritten clusters detected, but Recuva was wrong: the contents were all zeros. In other words, the contents were effectively removed, and most (but not) of the metadata (filename data) was removed.

Notice in the screenshot in the header table the data is all zeros.

---
Andrew, lead developer

ROCKNROLLKID's picture

I only have one partition on my HDD and that is C: drive. I do have E: which is not connect and D: which was not connected at the time. Yes BleachBit did wipe the C: drive. I did what you did and checked some of the files and see if they had 0 values. I just checked a few and some of them that were marked as excellent recoverable that weren't, but most of them were also marked as excellent recoverable and were successfully recoverable. These were still older files marked before I ran the wipe, I haven't ran another wipe since then. Also I do run on a NTFS system and none of these files were in MFT free space. I am moving tomorrow and will be unresponsive for a couple of weeks, once I get my PC hooked up in my new home, I will run another wipe free space and re-test with both recovery tools.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).

ROCKNROLLKID's picture

After a long time away from this, I did a retest earlier today. I wiped free space making sure pass wipe is enabled and making sure its selected to C:. After it finished, the error didn't pop up, this time. Not sure what caused it, to begin with, but I re-ran Kickass and Recuva. Kickass is still showing a great number of recoverable files and Recuva is showing some recoverable that aren't actually recoverable, but BleachBit seemed to have failed to wipe some files. These files were dated before I ran wipe free space, as well. I'd say, BleachBit is doing its job, but free space wiping still needs to be improved.

____________________
Also known as Alex.

Moderator for BleachBit and a maintainer for Winapp2.

Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity

Windows 10 x64 (switching to ReactOS in the future).