To all you Linux gurus. Here's a tough one.

 

I have some corrupted files on one of my unRAID volumes and am not able to get rid of them. When performing an ls -al (logged into the box via telnet), I get the following result

 

d??? ? ?  ?    ?            ? doMainMenu.nib/

 

Needless to say that whatever I try to do, I get a "no such file or directory" message from the system. I performed an fsck on the system and also tried to determine the inode number of the files / directories in question. No luck.

 

Any help would be appreciated.

 

Regards,

Carsten

To all you Linux gurus. Here's a tough one.

 

I have some corrupted files on one of my unRAID volumes and am not able to get rid of them. When performing an ls -al (logged into the box via telnet), I get the following result

 

d??? ? ?   ?     ?            ? doMainMenu.nib/

 

Needless to say that whatever I try to do, I get a "no such file or directory" message from the system. I performed an fsck on the system and also tried to determine the inode number of the files / directories in question. No luck.

 

Any help would be appreciated.

 

Regards,

Carsten

 

What happens when you type: ls *doMainMenu.nib*?

 

If it only displays that single file, then try rm *doMainMenu.nib*.

 

I still get the same old

 

/bin/ls: cannot access doMainMenu.nib: No such file or directory

 

Anything else I could try?

 

Thanks,

Carsten

 

Back in DOS days, we could sometimes use the wildcard substitution method mentioned above, and other times could use a windowed file manager to delete it, because the file manager would be deleting from its stored string, even if that could not display correctly.  Try using mc to delete it.

I had tried mc, but no luck ... guess I'll have to live with these stray files for a while.

 

Thanks,

Carsten

I had tried mc, but no luck ... guess I'll have to live with these stray files for a while.

 

Thanks,

Carsten

 

Have you run a file system check on your drives?

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

Yes, I did, but it didn't find any problems with the system.