Corrupted .TRASH causes crashes, REFUSES to delete files!

[WinRiddance]

This is what I got back:

drwx------ 1 winriddance winriddance 0 2010-12-17 14:03 /media/Volume/.Trash-1000

Just did that. The time is off by 30 minutes though for whatever reason ...
I believe you're right. One of these days I'll have to do the ugly bit of saving, moving, and later recovering all of that data again, in between which I'll be reformatting that drive. Thanks for all of your time. I'm not going to mark this as solved since no actual resolution has been found to the initial problem (aside from formatting the disk).

[CharlesA]

With those permissions, you should be able to delete the folder.

You could also run badblocks on the drive, to see if it finds any areas that it can't read.

[WinRiddance]

Alright, I never heard of "badblocks" before but after doing some extensive checking realize at least a few points about it.

1. Must be run from the terminal (no problem)
2. Should be used on an unmounted disk (no problem)
3. Can't find anything about NTFS file systems ... Problem ???
4. Can't find anything about ext4 file systems ... Problem ???
5. Wondering if the following would be the correct command for me ... ???

# fsck -vc /dev/sdb1

6. Or should I use something else since fsck is strictly for linux file systems, while that disk is NTFS ... ???

Something like this perhaps? badblocks -nvs /dev/hda
(however, running sudo fdisk -l doesn't give ma an "HDA" to use)
Oh, the love and joy of getting used to Linux ...

[CharlesA]

I've used badblocks on an NTFS drive no problem.

All physical drives are listed as sda, sdb, sdc with newer versions of Linux.

[WinRiddance]

Okay, well, umh, badblocks didn't work for me. I unmounted the disk first.
When I tried this: winriddance@winriddance-laptop:~$ sudo e2fsck -c -c -k -C 0 /dev/sdb1

I received this as a response:

e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

The above command was explained in another forum, step by step, like this:

The filesystem should not be mounted while this takes place, so if it is needed for your normal running system you will need to run e2fsck while booted from a "live CD" or similar. The -c option is what causes the surface scan to be added to what the checker does, then second -c makes it do a non-destructive write+read test, -k tells it to keep any existing list of badblocks instead of retesting them and -C 0 just makes e2fsck output more progress information as it does its work. See man e2fsck for more detail.

This was in answer to another Ubuntu user with an NTFS partition question.
In another forum someone mentioned that NTFS partitions require different parameters since fsck is (supposedly) strictly for Linux ext2, ext3 and ext4 partitions. I'm also wondering if it makes a difference that this is not a regular hard disk, but instead an external USB drive ???

On yet another source that I found via google one more individual mentioned that e2fsck can't be used on an NTFS partition.

Aside from that there appear to be tons of answers from dates between 2001 and 2006, all of which put me off a little since hard disk technology has gone through quite some changes in the past 5 years, in particular as far as USB volumes are concerned. I did not try the e2fsck -b 8193 option since I'm not certain how that might (or might not) impact any existing data on that USB disk?

[CharlesA]

fsck doesn't work on NTFS partitions. You'd probably have better luck running chkdisk on it from a Windows box.

The syntax I use with badblocks is this:

sudo badblocks -nv /dev/sdX

[WinRiddance]

Great, that did the trick. Thanks.
It's testing now. I'll report the results here later ... possibly much later ...

Alright, it's finished now, got done in the middle of the night and took at least 10 hours for that 250 GB drive. Here's the output from the terminal, including the original command that I used (thanks again for that).

winriddance@winriddance-laptop:~$ sudo badblocks -nv /dev/sdb1
Checking for bad blocks in non-destructive read-write mode
From block 0 to 244196000
Testing with random pattern: Pass completed, 0 bad blocks found.
winriddance@winriddance-laptop:~$

So we know the drive is absolutely fine, but the garbage bin/permissions oddity still remains.

[ellaivarios]

Hi, I have a similar problem, after trying to copy a huge file on a 10GB usb stick, the trash folder contains files with really weird jarbled up filenames. Every time I detelete these, they reappear. and reappear and reappear! The folder .Trash-1000 contains infinite copies of itself, again and again and again!

I tried:

rm -rf *

but to no avail.
I formatted the drive, but it is still acting wonky, same behavior!!

I checked it for errors and IT APPEARS PERFECT!

so weird!

seems we are in the bucket together on this one, even if you experienced this so long ago!

[CharlesA]

Replace the drive if a format didn't get rid of the problem.

[cariboo]

I agree with CharlesA, I've seen the same thing on a usb thumb drive, a format usually cures the problem.