On 5/17/20 2:13 PM, Gordon Messmer wrote:
On 5/17/20 10:22 AM, Robert Moskowitz wrote:
How can I get this bad file out of the way so I can back up properly?
IIRC, an IO error can result from either a corrupt filesystem or a
media error. The kernel "dmesg" can tell you more about the cause of
the error, typically. If there's filesystem corruption, you may be
able to correct the problem with fsck and continue using the drive.
If there's a media error, you're probably better off replacing it.
dmesg >dm.txt makes a 43K file. I grepped on sdc and got things like:
sd 6:0:0:0: [sdc] Assuming drive cache: write through
sd 6:0:0:0: [sdc] Attached SCSI disk
sd 6:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
sd 6:0:0:0: [sdc] CDB: Read(10): 28 00 3a 07 d5 cf 00 00 f0 00
end_request: I/O error, dev sdc, sector 973592015
sd 6:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
sd 6:0:0:0: [sdc] CDB:
EXT4-fs (sdc1): error loading journal
end_request: I/O error, dev sdc, sector 973592255
sd 7:0:0:0: [sdc] Attached SCSI disk
EXT4-fs (sdc1): warning: mounting fs with errors, running e2fsck is
recommended
EXT4-fs (sdc1): recovery complete
EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26386452
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 18481598
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 18482716
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 16520138
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 18481193
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 18745520
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 16520134
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 20709965
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
EXT4-fs error (device sdc1): ext4_lookup: deleted inode referenced: 26098156
so what should I include in the e2fsck command?
And should probably order a new backup drive...
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
