I have an external disk with 2T of memory of which ~500G are being used. It is formatted as:
[root@localhost hn2-vinicius]# fdisk -l
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0006055c
Device Boot Start End Blocks Id System
/dev/sdc1 63 3907024064 1953512001 c W95 FAT32 (LBA)
My problem is that I have a folder within the disk, from an earlier backup, in which all files became corrupt. I want to delete the folder (and the files) but the computer wont let me. I log in as root and when I try to remove it I get
[root@localhost hn2-vinicius]# rm -fr hn2_vinicius_final
rm: cannot remove `hn2_vinicius_final/Ä\017╥+ú¬\023c.¿▒ï': Read-only file system
rm: cannot remove `hn2_vinicius_final/8d:¿4î╜\035.└a·': Read-only file system
rm: cannot remove `hn2_vinicius_final/f~┤avh*Γ.╚┴c': Read-only file system
rm: cannot remove `hn2_vinicius_final/É6\v)3ƒ░É.ÿ1\031': Read-only file system
rm: cannot remove `hn2_vinicius_final/e«\006½æσ▌k.lë(': Read-only file system
rm: cannot remove `hn2_vinicius_final/qmô─╢r\vσ.╓d÷': Read-only file system
rm: cannot remove `hn2_vinicius_final/─|╖ÿδ\0212╜.|«Å': Read-only file system
rm: cannot remove `hn2_vinicius_final/\036ª╪═öz.▒ç\002': Read-only file system
rm: cannot remove `hn2_vinicius_final/∙\r3┐1╩oÉ.Θÿx': Read-only file system
rm: cannot remove `hn2_vinicius_final/f┐«ë\004\rhq..≤δ': Read-only file system
rm: cannot remove `hn2_vinicius_final/α\017\'τ╬üæo.Bº5': Read-only file system
rm: cannot remove `hn2_vinicius_final/⌠+≈\026α╗èφ.)e▌': Read-only file system
rm: cannot remove `hn2_vinicius_final/╨+╧╗eΓö\016.\fíl': Read-only file system
rm: cannot remove `hn2_vinicius_final/Θæ═π÷\réî.╤ë┤': Read-only file system
rm: cannot remove `hn2_vinicius_final/│e\017w¥σpñ.≥└0': Read-only file system
Shown above is just a small number of lines of the output because I get thousands of them. I try to run FSCK to try to correct the problems and what I get is
[root@localhost hn2-vinicius]# fsck -a /dev/sdc1
fsck from util-linux 2.20.1
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
Unfinished long file name ":1EU:1kW:Es6:F4l:6yf:93o:0FS:5Jj:Fv8:2vC
Sg
XA: As-".
(Start may have been overwritten by �-�;[NDE.6\022�)
Not auto-correcting this.
Reserved field in VFAT long filename slot is not 0 (but 0x06).
Auto-setting to 0.
Start cluster field in VFAT long filename slot is not 0 (but 0xdd12).
Auto-setting to 0.
Unfinished long file name "
qq:9LO:9WA:5uQ:A4r:0Am:3q8:0VD:ALs:10h:AQr
Dh: FDO".
(Start may have been overwritten by �\021�\205���\222.L�V)
Not auto-correcting this.
/vinicius-total2/vinicius/Desktop/PhD/tese/tese-IMPRESSA/artigosmeus-bkp/hn2-vinicius/hn2_vinicius_final/\025�E�\024 ��.�\227u
Bad short file name (\025�E�\024 ��.�\227u).
Auto-renaming it.
Renamed to FSCK0000.191
/vinicius-total2/vinicius/Desktop/PhD/tese/tese-IMPRESSA/artigosmeus-bkp/hn2-vinicius/hn2_vinicius_final/\232��1:oaJ.\210[�
Bad short file name (\232��1:oaJ.\210[�).
Auto-renaming it.
Renamed to FSCK0000.192
/vinicius-total2/vinicius/Desktop/PhD/tese/tese-IMPRESSA/artigosmeus-bkp/hn2-vinicius/hn2_vinicius_final//�\032\000\026A\233w.�@\222
Bad short file name (/�\032\000\026A\233w.�@\222).
Auto-renaming it.
Renamed to FSCK0000.193
/vinicius-total2/vinicius/Desktop/PhD/tese/tese-IMPRESSA/artigosmeus-bkp/hn2-vinicius/hn2_vinicius_final/�$\022\033b"#�.�\210d
Bad short file name (�$\022\033b"#�.�\210d).
Auto-renaming it.
Renamed to FSCK0000.194
Again, shown is just a part of the huge and endless output. In fact, the "fsck -a /dev/sdc1" run for hours and never ends (today I left the computer for 5 hours at least running this command and it was not enough).
I cant backup the disk and format it because it is already my backup disk and I have no place to put the 500G it contains. Is there any work around to delete this folder?
Linear Mode
