External drive - rsync error - failed: Structure needs cleaning (117) - GPT (GUID Partition Table) detected on '/dev/sda'

rknichols · 11-02-2017, 07:54 AM

Unsupported USB bridge chip is a problem with those external enclosures. Seagate probably has a diagnostic utility, but you'd probably need to run it on a Windows machine.

Does anything show up in the system log when the error occurs?

dakoris73 · 11-02-2017, 03:53 PM

I checked the syslog after a system update and reboot, and here's what I see in the logs:

Code:

Nov  2 06:47:35 virNAS ntfs-3g[32598]: ntfs_mst_post_read_fixup_warn: magic: 0x5ec04031  size: 1024   usa_ofs: 12550  usa_count: 57407: Invalid argument
Nov  2 06:47:35 virNAS ntfs-3g[32598]: Record 13097 has no FILE magic (0x5ec04031)
Nov  2 06:47:35 virNAS ntfs-3g[32598]: ntfs_mst_post_read_fixup_warn: magic: 0x10307021  size: 1024   usa_ofs: 8225  usa_count: 1135: Invalid argument
.......

Nov  2 15:42:56 virNAS ntfs-3g[780]: Inode is corrupt (12119): Input/output error
Nov  2 15:42:56 virNAS ntfs-3g[780]: Inode is corrupt (12119): Input/output error
Nov  2 15:42:56 virNAS ntfs-3g[780]: Actual VCN (0x0) of index buffer is different from expected VCN (0x29) in inode 0x28.

Nov  2 15:45:04 virNAS ntfs-3g[780]: Actual VCN (0x0) of index buffer is different from expected VCN (0x29) in inode 0x28.

and here is what I have in my fstab:

Code:

 
# setting up 5 TB plex media drive
UUID=D882D1B582D197F8   /mnt/plexmedia ntfs-3g auto,users,uid=108,gid=1002,umask=002,utf8       0       0

Does any of this make any sense?????

Thanks again for all the help.

rknichols · 11-02-2017, 08:02 PM

It makes sense, but adds little useful information. I was hoping to see a report of a media error on sector xxxx or the like. Since you can't run any SMART tests, perhaps you could try running "dd if=/dev/sda of=/dev/null bs=4096 conv=noerror" and see what regions of the disk it complains about. The error you're seeing (inode 28) seems to be near the beginning of the disk, so you should see something fairly quickly.

The alternative would be running whatevere Seagate provides as a diagnostic/repair utility.