Eraser can't erase traces even with 7 pass and 1 pass

[Altair1572]

ok, joel, can you tell me why i cant wipe free space using more than single pass pseudorandom?. I can only use single pass. when overwriting free space with any other passes from 2-35, my drives are getting full at some 90%-95% and Eraser fails to complete the process successfully.

Ca we use only single pass for wiping free space?. Why using other passes fills drive early and fails the process?.

[Joel]

The drive filling up is expected and is normal. Letting Eraser complete the erasure will allow Eraser to discard those files properly. If Eraser is erroring out, please copy and paste the task log here.

As of now, current sentiments are that on a modern hard drive, one pass is sufficient.

[Altair1572]

No, i said this. When the Eraser process reaches some 90%, the drive fills completely with only some 800KB left and Eraser stops there telling it couldnt access/write to a folder with random name like E:\ytHm1uelvw5bhes7yh75o in the log. Then eraser leaves the random named folder on disk to let us delete it manually. This tells Eraser failed to complete the wipe.

So no other option than single pass!!.

[Joel]

Altair, I think you are doing no one a service by complaining and ignoring advice. I have said logs from the failed erase attempt are needed before any form of diagnosis can be made.

[Altair1572]

Sorry for the misunderstandings, joel. I said i got this log entry when the process failed because of full disk.

"When the process fails,

Eraser stops, telling it in the log that it couldnt access/write to a folder with random name like E:\ytHm1uelvw5bhes7yh75o. Then eraser leaves the random named folder on disk to let us delete it manually

"

This is the usual Eraser error when it fillouts drive before writing random data fully to drive when we use more than single pass.

Is it correct?..

[Joel]

Yes, correct, but I need the exact message. Even if it is not in English.

[Altair1572]

Found some bugs today when erasing...

When i erase a file when Eraser process is not running in background, Eraser erases that file after some seconds, but when i open Eraser window the task list contains the same file marked as Not queued. When i choose Run now, it shows error that the file is not on disk.
Why eraser lists this erased file as Not queued?. It should empty the task list as soon as the task completes.

I found that this is happening when i start Eraser first time after booting up system. I chose to erase some temp files without eraser running in background and above thing happens. But when i erase temp later for the second time it is not happening and the task list is shown empty. It only happens for the first eraser start after system bootup.

[Joel]

This would need some investigating. Let me try to reproduce the issue.

[Joel]

Sorry for taking so long. This is a race condition, I'll be fixing it shortly (testing the fix now).

[Joel]

For the record, this was fixed in r2339 (which made it into Eraser 6.0.9)

[william070707]

Hi,

Thanks for the update that it has been fixed