On 2020-09-01 00:07, golinux@??? wrote:
> Thanks to everyone who has responded to this thread (some off-list). I
> just wanted to drop a short note updating you that the dock arrived
> earlier today but I haven't yet had a chance to open the box. I am not
> an impulsive person. I tend to measure 6 times and cut once! So it's
> going to take me a while to sort through all the suggestions and
> decide how to proceed. I'll post when I have figured that out and the
> stars align. Stay tuned . . .
>
> golinux

Well . . . I decided to run an fsck on the misbehaving harddrive. It
started off by identifying the errors and rewriting them and then went
through Free block counts, Inode bitmap differences and Free inodes and
directory count. Some snippets of the output are posted below. I did not
stick around to watch all of it so may have missed something. It took a
long time to sort itself!

======================================

root@devuan:/home/xxxxxx# fsck /dev/sdc1 -y
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
cstwo contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and size
Error reading block 40042498 (Attempt to read block from filesystem
resulted in short read) while getting next inode from scan. Ignore
error<y>? yes
Force rewrite<y>? yes
Error reading block 41943042 (Attempt to read block from filesystem
resulted in short read) while getting next inode from scan. Ignore
error<y>? yes
Force rewrite<y>? yes
yada, yada

======================================

Free blocks count wrong for group #6302 (22328, counted=25579).
Fix? yes

Free blocks count wrong for group #6678 (21, counted=22).
Fix? yes

Free blocks count wrong (72019929, counted=75713399).
Fix? yes
yada, yada

======================================

Inode bitmap differences: -(20021249--20021280) -(20971521--20971552)
-(21250049--21250065) -(23756801--23756811) -(25772033--25772051)
-(25772053--25772057) -(25772059--25772064) -(25772067--25772069)
-(25772073--25772074)
yada, yada

======================================

[ending with]

Free inodes count wrong for group #6278 (13844, counted=14355).
Fix? yes

Directories count wrong for group #6278 (19, counted=0).
Fix? yes

cstwo: ***** FILE SYSTEM WAS MODIFIED *****
cstwo: 191841/122109952 files (1.9% non-contiguous), 168476601/244190000
blocks

======================================

When it finished, I mounted the drive without issue and could read the
remaining directories and files. However the /media/xxxxxx/cstwo/600
directory mentioned in the original mounting error below was nowhere to
be found:

"Error when getting information for file '/media/xxxxxx/cstwo/600':
Input/output error."

Then I ran the SMART Short offline test and it completed without error

I have no idea how reliable the repaired drive is after this radical
surgery. Can it be written to or files deleted? Should I even try?

Thanks to all and especially g4sra for detailed suggestions and advice.

Now onto the next project needed to moving on from jessie at long last.

Take care all,

golinux