Can't uninstall Amule

[perdido]

@perdido - tried 3 times, and I'll put the Terminal text - combined for all the attempts. First tried for the folder "Temp" ― so I opened Terminal in the folder containing "Temp" - which is "Program Files D", Then opened Terminal in the "Temp" folder - for one of the files - with 2 attempts: first by its name; then by its whole path. Non worked.

Code: Select all

# chattr -i Temp
chattr: Inappropriate ioctl for device while reading flags on Temp
# chattr -i 001.part
chattr: Function not implemented while reading flags on 001.part
# chattr -i /mnt/sda5/Program Files D/Temp/001.part
chattr: No such file or directory while trying to stat /mnt/sda5/Program
chattr: No such file or directory while trying to stat Files
chattr: No such file or directory while trying to stat D/Temp/001.part
# 
 

Hi MrAccident,
# chattr -i Temp
chattr: Inappropriate ioctl for device while reading flags on Temp
# chattr -i 001.part
chattr: Function not implemented while reading flags on 001.part

Don't know the answer for those two errors
---
The other errors (chattr: No such file or directory) were just wrong path to the file.

I don't think chattr will work on symlinks or windows file systems.
Plus some system files will return that error.
Good try anyway.

Best I can suggest is boot from a different puppy and try it again, I had success doing that on stubborn system files.
Better suggestions needed if a try with a different puppy fails.

.

[MrAccident]

OK, if that won't work - I'll make a new thread.
Thank you all.

[williams2]

What error messages do you get if you try to delete
one of the files from a console?
Show the file you want to delete in a rox window,
then press ` (backtick) to open a console window.
Or right click the rox window, and select
Window, Terminal Here.

Code: Select all

ls -lh 001.part
rm 001.part

Sometimes a file can be created with a name that
contains characters that cause trouble in that file system.

If it is a MS Windows ntfs file system you could try
checking and repairing the file system.

If it is an ext2/3/4 file system you can try a file system check (fsck).
The file system should first be unmounted.

If it is the file system Puppy is using for the operating system files,
you need to start Puppy using pfix=fsck

[MrAccident]

@williams2:
It's NTFS.

Code: Select all

# ls -lh 001.part
-rwxrwxrwx 2 root root 58M May 16  2018 001.part
# rm 001.part
rm: cannot remove ‘001.part’: Input/output error
# 

Another thing I noticed ― when the window just opens - there are more files - which disappear right away; and also appear\disappear - every time I click on refresh. These are consecutive files after the visible, by their name; so the last visible are 2 files starting with "006.part"...; and the ones invisible (even with clicking the eye symbol) ― are 5 files for "007.part"... and "008.part"...

...characters that cause trouble in that file system...

The first visible file name is "00皼.part.met.bak".
It's also impossible to create a file in that folder.
It's not Puppy's file-system.

[williams2]

input/output errors are often hardware problems,
like a bad sector, or a defective usb port.

Assuming it is an NTFS file system:

I would boot ms Windows and run the filesytem repair program.
Running chkdsk in a dos box might be better.
If there are files with illegal file names,
the repair program should move the files to .found000

Then I would try deleting the problem files from Windows.

You might try renaming the file first.

You could try copying the file somewhere.
Sometimes it helps to read all of the bytes in the file
if the drive has a bad sector.

Running Windows chkdsk with the check bad sectors option might help.

"00皼.part.met.bak" does look like it might be an illegal name.

One of the usb ports on my laptop disconnects the flash drive
sometimes, giving an input/output error.
I avoid using that usb port.

The file permissions look ok.

dmesg in a console might show a helpful error message,
if it's a hardware problem.

You could try renaming a file like this,
if you can't type in the filename:

Code: Select all

mv 00*.part.met.bak 001.part.met.bak

(assuming there is only 1 file named 00*.part.met.bak)

You could try testing your drive using smartctl (Smartmontools).

Does the rest of the drive work properly,
or are there other files that don't work right?

[MrAccident]

@williams2 - using your code;

Code: Select all

# mv 00*.part.met.bak 001.part.met.bak
mv: target ‘001.part.met.bak’ is not a directory

BTW - I did rename and move the folder; so it's probably the files that are the problem.
The rest of the drive works fine. I'll just leave it as is (just 450mb of 1TB); I want to buy a new computer anyway; and it may be soon.
Anyway - I tried to rename it normally - and here's the result:

Code: Select all

Moving /mnt/sda5/to delete/00皼.part.met.bak as /mnt/sda5/to delete/f.part.met.bak
mv: cannot move ‘/mnt/sda5/to delete/00皼.part.met.bak’ to ‘/mnt/sda5/to delete/f.part.met.bak’: Input/output error
Failed to move /mnt/sda5/to delete/00皼.part.met.bak as /mnt/sda5/to delete/f.part.met.bak

Done
There was one error.

[williams2]

If that directory has an illegal name,
then you probably can not access any file in the directory.

If it's an ntfs file system, you should use MS Windows
to repair the drive, if you can.

There is a program ntfsfix but I think it only resets the clean flag,
I don't think it actually repairs the file system.
I'm not really sure.

Sometimes a program can create a file or dir with an illegal name.

Or it could be hardware.
If it's hardware, your drive might be near it's end of life.
You might think about backing up any files you want to keep.

There are programs you can run to test your drive.

[MrAccident]

@ williams2 -

There are programs you can run to test your drive.

Haven't thought of that; will try.
Thanks.