The directory is corrupted and unreadable
Posted: 01 Apr 2012 00:09
Hi,
I don't know if it's just my HDD getting bad, but this is the issue: I've started using the wipe functionality of XYPlorer about one week ago, and have deleted a couple of files with it (wiping beyond recovery).
Today I started noticing that at least three folders (two of the android sdk, one of the vlc player, which I've never touched), have become unreadable by the system.
It surely may be that the HDD is damaged, even tough SMART data shows no signs of problems on the HDD. I'm going to run chkdist on the drive over night, as well as spinrite, in order to check the surface for errors.
But, I've hadn't any issues for years, and now that I start using that feature, things start to go wrong. Of course there are no signs that this is XYPlorer related, only the timing of the problems may indicate a relationship. The drive will get replaced ASAP anyway, just in case, but I just want to stick a note here in the forum just in case some others may have the same issue.
Could, due to bad programming, the wipe functionality create these problems or are those truely safe operations which don't operate at those problematic low levels?
Kinds regards,
Daniel
I don't know if it's just my HDD getting bad, but this is the issue: I've started using the wipe functionality of XYPlorer about one week ago, and have deleted a couple of files with it (wiping beyond recovery).
Today I started noticing that at least three folders (two of the android sdk, one of the vlc player, which I've never touched), have become unreadable by the system.
It surely may be that the HDD is damaged, even tough SMART data shows no signs of problems on the HDD. I'm going to run chkdist on the drive over night, as well as spinrite, in order to check the surface for errors.
But, I've hadn't any issues for years, and now that I start using that feature, things start to go wrong. Of course there are no signs that this is XYPlorer related, only the timing of the problems may indicate a relationship. The drive will get replaced ASAP anyway, just in case, but I just want to stick a note here in the forum just in case some others may have the same issue.
Could, due to bad programming, the wipe functionality create these problems or are those truely safe operations which don't operate at those problematic low levels?
Kinds regards,
Daniel