[schalliol]

Ok, I know this sounds easy on the surface, but these two files cannot be deleted. I tried all of the ways I know to delete, including many tries in terminal as root using the various commands of rm. I also had help from a major university top Mac admin, another Mac admin and an Apple lead Mac Genius, but to no avail. I can move these files by moving their folders, but not directly (terminal & finder) and get info on the files, but not rename them. I no longer use Direct Connect (just tried it once), so I want to get rid of them. The files also booted in the trash and haven't been active for quite some time, however connecting from a Mac OS 9 machine can't take care of it, neither can an X machine as ssh or afp.

Here's an image of the files in Finder:


A couple of pieces of output for you:

What I get in zsh & bash terminal when running ls as root:
krille??????e).dclst krille??????e).ucl

What I get in zsh & bash terminal when running ls -alo or ls -al as root:
ls:
ls:
total 0
drwxrwxrwx 4 root staff - 136 16 Dec 12:21 .
drwxrwxrwx 4 root staff - 136 16 Dec 13:39 ..

Interesting, huh? I think they might be in some other character encoding method, which maybe could help me take care of them if I could use it. Can you help me kill it?

[CharlesS]

Have you tried running DiskWarrior on the drive?

[schalliol]

Originally posted by CharlesS:
Have you tried running DiskWarrior on the drive?

Not DiskWarrior (I may have an older copy, not sure if I should try it). I did use TechTool Pro 4.0.1 though. All 4 internal drives passed all the tests, including surface scan (probably can rule out bad block causing file corruption then).

[CharlesS]

Originally posted by schalliol:
Not DiskWarrior (I may have an older copy, not sure if I should try it). I did use TechTool Pro 4.0.1 though. All 4 internal drives passed all the tests, including surface scan (probably can rule out bad block causing file corruption then).

I'd give DiskWarrior a shot. It sounds like something's wrong with your directories. Sometimes DW can fix things that Norton/TTP miss.

I think that DiskWarrior 2 and better can safely be run on OS X drives.

[schalliol]

More things I tried:
2 apps that are supposed to delete files, but alas they're just applescripts and I always get an error.

Stuffing the file and having stuffit delete the original (this worked in OS 9 sometimes), didn't work.

I used autocomplete on one of the files by typing "cat kr[tab]," which gave me (only in bash) "krille\355\234\237\355\262\267e\)." Then typing ucl to do "cat krille\355\234\237\355\262\267e\).ucl" and got "No such file or directory"

[CharlesS]

Originally posted by schalliol:
More things I tried:
2 apps that are supposed to delete files, but alas they're just applescripts and I always get an error.

Stuffing the file and having stuffit delete the original (this worked in OS 9 sometimes), didn't work.

I used autocomplete on one of the files by typing "cat kr[tab]," which gave me (only in bash) "krille\355\234\237\355\262\267e\)." Then typing ucl to do "cat krille\355\234\237\355\262\267e\).ucl" and got "No such file or directory"

If the OS X Finder, rm, and even Mac OS 9 are not able to delete the file, I highly doubt that using a different app to try to delete the file will make much of a difference.

Please try DiskWarrior and let us know if it works.

[Developer]

Trash and delete or sudo rm the enclosing folder.
If that doesn't work boot into OS 9 and delete the files.
If that doesn't work compress the files using DropStuff and let it delete the original.

[schalliol]

Originally posted by Developer:
Trash and delete or sudo rm the enclosing folder.
If that doesn't work boot into OS 9 and delete the files.
If that doesn't work compress the files using DropStuff and let it delete the original.

while I didn't directly boot into OS 9 (don't have it on this machine anymore), I did try OS 9 remotely. The other things you mentioned I talk about above, they don't work (DropStuff and Stuffit Deluxe can do the same thing). Thanks though!

Running DiskWarrior now...

[schalliol]

Originally posted by CharlesS:
If the OS X Finder, rm, and even Mac OS 9 are not able to delete the file, I highly doubt that using a different app to try to delete the file will make much of a difference.

Please try DiskWarrior and let us know if it works.

I agree there!

[Developer]

Originally posted by schalliol:
while I didn't directly boot into OS 9 (don't have it on this machine anymore), I did try OS 9 remotely.

Try Firewire target disk mode. Mount the disk in OS 9 directly not remotely.

[dagaz]

Did you try sudo rm -f /Previous\ System\ 1/Users/shalliol/Library/Application\ Support/Direct\ Connect/dcLists/* ? The best bet would be to type the first few letters of each directory then use tab to autocomplete. It looks from your image as if there are only the two files in that directory which is why I suggested the * wildcard.

Good luck.

[CharlesS]

^ He already said rm didn't work.

[schalliol]

dagaz, I did try that. I tried both autocompleting and using individual files and whole directories, none of that works

Developer, I don't really have the capability at the moment to boot into OS 9 on the machine or FireWire target into OS 9, but I'll find a way if it's the last resort. I don't see what good it would do to FireWire target into it from an OS X machine, but I'll try it if you think it's worth it.

CharlesS, I did run DiskWarrior and here's the output I got from the report on the files:
[quote]File: "krille

[Developer]

Originally posted by schalliol:
I don't see what good it would do to FireWire target into it from an OS X machine, but I'll try it if you think it's worth it.

No, I meant put it into Firewire target disk mode and mount it on the OS 9 machine. I said that because you said your machine does not boot OS 9.

[CharlesS]

[quote]Originally posted by schalliol:
CharlesS, I did run DiskWarrior and here's the output I got from the report on the files:

File: "krille

It looks like something went wrong with the BBS and your post got cut off. Could you repost this?

[schalliol]

Yeah, I don't know what happened there, let's try again, I think the garbled text even screwed up MacNN and removed all content following (that's some nasty text name)!:
dagaz, I did try that. I tried both autocompleting and using individual files and whole directories, none of that works

Developer, I don't really have the capability at the moment to boot into OS 9 on the machine or FireWire target into OS 9, but I'll find a way if it's the last resort. I don't see what good it would do to FireWire target into it from an OS X machine, but I'll try it if you think it's worth it.

CharlesS, I did run DiskWarrior and here's the output I got from the report on the files:

File: "krill[garbled].dclst" Detected that the Name changed Location: "Main Drive/delete/Previous System 1/Users/schalliol/Library/Application Support/Direct Connect/dcLists/ " File: "krill[garbled].ucl"

Detected that the Name changed Location: "Main Drive/delete/Previous System 1/Users/schalliol/Library/Application Support/Direct Connect/dcLists/ "

That didn't seem to do anything as far as I can tell and still when I go to remove as root with autocomplete:
"root# rm krille\355\234\237\355\262\267e\).ucl

"
Hitting the return key just goes down a line
then I hit return again and get no action changed and no message.

I guess booting into OS 9 or OS X FW Target is the only thing left to try (of sane solutions). Any more?

[CharlesS]

Does rm -rf'ing the parent directory produce any different results now that you have run DiskWarrior on the drive?

[schalliol]

Originally posted by CharlesS:
Does rm -rf'ing the parent directory produce any different results now that you have run DiskWarrior on the drive?

Sadly, no

root# rm -rf dcLists/
rm: dcLists/: Directory not empty

[CharlesS]

I guess the OS 9 trick is the thing to try. Weird...