<div dir="ltr">I have a 3TB external USB3 drive that mysteriously disconnected from the machine it usually lives on the other day, so I started doing some checking to see if I can figure out what's up with it.<div><br>
</div><div>It's got a single GPT partition on it, formatted as ext4.</div><div><br></div><div>Hooked it up to my workstation, it mounts, data looks good, everything seems fine. It has reached it's mount count though, so I thought I'd run fsck on it. fsck says it has a bad superblock.</div>
<div><br></div><div>Tried running against a ton of different potential superblock backup locations, no dice. The only difference is that when I run against a backup superblock it reports:</div><div><br></div><div><div>1.41.10-2198: ***** FILE SYSTEM WAS MODIFIED *****</div>
</div><div><br></div><div>In addition to the warning about the bad superblock. (1.41.10-2198 is the drive label)</div><div><br></div><div>I did notice in gparted that the "msftdata" flag was incorrectly set on it, so I cleared that flag thinking it might have been confusing fsck, but no love there.</div>
<div><br></div><div>Anyone run into something like this before? My prayers to google aren't returning anything I haven't tried.</div><div><br></div><div>For the record, I'm not necessarily opposed to nuking the partitions and starting over, the drive only contains backups, but re-loading it would be time consuming so I'd love to avoid that if I can.</div>
<div><br></div><div>QH</div></div>