I mistakenly disconnected or shut down an external hard drive prematurely (before the directory being written was finished) and ended up with a grey bordered yellow icon (! boldly centered in icon) that will not open, be renamed or deleted.
"chmod -R 777 /mnt/sdc1/directoryname" returns "chmod: cannot access '/mnt/sdc1/directoryname/': Input/output error"
Permissions cannot be changed via right-click GUI or Properties GUI.
How do I get rid of this directory? Using FatDog 6.00 here ATM, but it is an external HD that can be connected elsewhere.
-Roy
Unable to delete broken directory - SOLVED
Unable to delete broken directory - SOLVED
Last edited by Roy on Tue 03 Mar 2015, 17:26, edited 1 time in total.
Have the drive plugged in, but not mounted.
Try running Gparted program.
Select the drive for Gparted to scan.
Right click on the drive partition and choose check.
See if maybe something is wrong with the file system on the partition.
This check will see if the file system is OK and also correct anything it finds wrong.
Try running Gparted program.
Select the drive for Gparted to scan.
Right click on the drive partition and choose check.
See if maybe something is wrong with the file system on the partition.
This check will see if the file system is OK and also correct anything it finds wrong.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
I've used Windows on numerous occasions to fix the FAT drive which host my frugal puppies. Very easy to delete something in puppy (like a save file still in use/editing gone wrong, etc.) and boom, gone but not really gone permanently. You just see you have less space left on the drive and then it's Windows to come to the rescue. Do not get rid of Windows, especially if you have FAT and ntfs partitions.mikeb wrote:ntfs or fat...use windows to run a chkdsk on it.
if posix...ext2/3/4 fsck /dev/whatever will sort it out.
mike
lol so keeping windows to fix a problem caused by running linux as root, my suggest a more baby proof linux. Or not using a proprietary filesystem like NTFS.
I am always surprised by these types of problems, intermixing Windows with Linux on same hardware is worse than running them as two separate machines. Buy a second harddrive and be done with windows = problem solved.
As I type this I am aware most of us me included just like to have windows beaten back by our own choices and the problems caused is fun to fix and complain about.
I am always surprised by these types of problems, intermixing Windows with Linux on same hardware is worse than running them as two separate machines. Buy a second harddrive and be done with windows = problem solved.
As I type this I am aware most of us me included just like to have windows beaten back by our own choices and the problems caused is fun to fix and complain about.
Well, if I have to choose between Puppy and Windows XP Pro which I have, then I will have to go with Windows, it just works better in my particular circumstances. Windows is my primary system and installed on a second ntfs partition. Frugal puppies on a small FAT partition. I like being able to access all partitions from all operating systems.Ted Dog wrote:lol so keeping windows to fix a problem caused by running linux as root, my suggest a more baby proof linux. Or not using a proprietary filesystem like NTFS.
I am always surprised by these types of problems, intermixing Windows with Linux on same hardware is worse than running them as two separate machines. Buy a second harddrive and be done with windows = problem solved.
As I type this I am aware most of us me included just like to have windows beaten back by our own choices and the problems caused is fun to fix and complain about.
Thanks to all!
I followed bigpups's suggestion and it worked on my 1.5TB ext2 drive -- or at least it removed the offending directory. I haven't checked to see if it corrupted any other files/directories, but I'm betting they are fine.
mikeb's suggestion would have probably worked, too -- but I'm no genius with the Command Line stuff and make my fair share of mistakes. Flash gave a definite solution -- but where to put 1.5TB of stuff in the meantime? (BTW Flash, thanks for cleaning up my original post for me.)
I am marking this as SOLVED. Thanks again.
-Roy
I followed bigpups's suggestion and it worked on my 1.5TB ext2 drive -- or at least it removed the offending directory. I haven't checked to see if it corrupted any other files/directories, but I'm betting they are fine.
mikeb's suggestion would have probably worked, too -- but I'm no genius with the Command Line stuff and make my fair share of mistakes. Flash gave a definite solution -- but where to put 1.5TB of stuff in the meantime? (BTW Flash, thanks for cleaning up my original post for me.)
I am marking this as SOLVED. Thanks again.
-Roy