Jump to content
5 posts in this topic

Recommended Posts

I have a file in my trash that wont delete. Its also in my old install of Leopard. Im trying to create a dual boot with Vista on another HDD and after installing Leopard a 2nd time on another drive the files showed up.

 

The files are different, but only the last few numbers are different, both start with a ton of 0's.

 

How do I delete this thing?

Hey idividebyzero,

 

Thanks for this - I have had the same thing happening. At least I can get rid of the files now.

 

Just in case any of the legends here on insanelymac can help, I suspect idividebyzero and I both have the same issue. I have been able to discover the following:

 

The filenames are different every boot.

 

For me, they are accompanied by a fseventsd file in the trash also. One per 0000000..... file.

 

I have discovered that the 00000000.... files are always in existence on 2 of my NTFS partitions in the .fseventsd/ directory of these 2 drives as well as being in the trash.

 

Any attempt to empty the trash normally results in all files but the 0000000000... files being deleted. The accompanying error is that the files are in use.

 

The issue seems to clearly relate to NTFS partitions and fseventsd, however I haven't been able to find any relevant boot error messages apart from ones relating to event logs being out of synch and needing a new uuid. Eg:

 

10.07.08 11:26:43 PM fseventsd[27] event logs in /.fseventsd out of sync with volume.  destroying old logs. (7737 10 87021) 
  10.07.08 11:26:43 PM fseventsd[27] log dir: /.fseventsd getting new uuid: 0465178A-EB53-4D77-819E-B184D5655444 
  10.07.08 11:26:57 PM fseventsd[27] event logs in /Volumes/HFS Storage/.fseventsd out of sync with volume.  destroying old logs. (7737 2 87035) 
  10.07.08 11:26:57 PM fseventsd[27] log dir: /Volumes/HFS Storage/.fseventsd getting new uuid: BF4893C1-E826-4FEC-A276-416CE34A666B 
  10.07.08 11:27:00 PM fseventsd[27] log dir: /Volumes/Samples/.fseventsd getting new uuid: 62038544-1CC9-4604-9BD7-53E49007ADF1 
  10.07.08 11:27:01 PM fseventsd[27] log dir: /Volumes/ProTools/.fseventsd getting new uuid: F3C7D1E2-D742-4A19-A512-A7A04F1D10CC 
  10.07.08 11:27:01 PM fseventsd[27] log dir: /Volumes/XP Box/.fseventsd getting new uuid: 186B0791-7DAA-47D0-A2BE-EA40A3988209 
  10.07.08 11:27:01 PM fseventsd[27] log dir: /Volumes/NEW2/.fseventsd getting new uuid: 782E9A41-53F2-4D14-A6C7-D6AE5C4A7A35 
  10.07.08 11:27:02 PM fseventsd[27] log dir: /Volumes/Audio/.fseventsd getting new uuid: 89BE408E-1C38-49BF-B147-B2C4100342BA 
  10.07.08 1:28:29 PM fseventsd[27] bumping event counter to: 0x1fdd (current 0x0) from log file '000000000000018f' 
  10.07.08 1:28:33 PM fseventsd[27] event logs in /Volumes/MacAudio 1/.fseventsd out of sync with volume.  destroying old logs. (8628 0 51131) 
  10.07.08 1:28:33 PM fseventsd[27] log dir: /Volumes/MacAudio 1/.fseventsd getting new uuid: B6B1FB3F-0C83-4B49-8E9C-6BB453CA87BB 
  10.07.08 1:28:33 PM fseventsd[27] event logs in /Volumes/MacAntec/.fseventsd out of sync with volume.  destroying old logs. (7737 0 51131) 
  10.07.08 1:28:33 PM fseventsd[27] log dir: /Volumes/MacAntec/.fseventsd getting new uuid: 4235BE3A-29E7-4634-A39B-EA4995A4ED17 
  10.07.08 1:28:35 PM fseventsd[27] log dir: /Volumes/Audio/.fseventsd getting new uuid: 2E41DFE8-312D-4AC6-AE10-D7869D2E4B44 
  10.07.08 1:28:36 PM fseventsd[27] log dir: /Volumes/ProTools/.fseventsd getting new uuid: 9B93070C-6ADD-4973-96E7-E72BBEC7B662 
  10.07.08 1:28:37 PM fseventsd[27] log dir: /Volumes/XP Box/.fseventsd getting new uuid: 6EB2A2BD-CE9E-4C42-ACC9-DC6FA6FFBBE5 
  10.07.08 1:28:37 PM fseventsd[27] log dir: /Volumes/NEW2/.fseventsd getting new uuid: 07536F09-A0CE-4905-97E1-21C4FBDDA52D 
  10.07.08 1:28:37 PM fseventsd[27] log dir: /Volumes/Samples/.fseventsd getting new uuid: C62079C4-0A8A-4F3C-A4AF-B75CB7DDEBEC

 

In the above errors, the partitions which are noted as being out of sync are HFS+ formatted. The other partitions are NTFS. I am running Paragon NTFS for Mac 6.5. You will also see reference to logfiles with the 00000000... format.

 

The above errors occur every boot on both HFS+ and NTFS partitions and do not stop the system from booting or running normally, however it seems odd that these errors are occurring. Can anyone shed some light on this?

 

Cheers,

gonzo :jerry:

Boot into windows and run a diskcheck.

 

Your NTFS partition has errors.

 

You can even give Disk Utility a go. These errors are common with Paragon NTFS(maybe even NTFS-3G).

  • 1 year later...
Boot into windows and run a diskcheck.

 

Your NTFS partition has errors.

 

You can even give Disk Utility a go. These errors are common with Paragon NTFS(maybe even NTFS-3G).

 

Thanks U.C. I did a "chkdsk /f" on CMD as administrator and worked! now my trash is ok!

×
×
  • Create New...