Sounds like a bad drive caddy. In my experience any disk thats not locked
away in a a non removable box is prone to errors.. especially if using
usb..
I don't think the mount/umount is handled very well in Linux when compared
to windows from a plug and play point of view. You have to be particularly
careful when it comes to externally powered hard drives.
Ive lost count of the times I've accidentally powered off a harddrive that
is mounted in the OS. Or accidentally pulled the power off etc..
Fsck etc is a part of the hard drive life cycle and have given up the idea
that external hard drive data is ever free from corruption or loss due to
power outage or cable issues etc.
Generally speaking fsck is enough to clear a point in time failure
hopefully you won't have lost anything but if it keeps happening chances
are u might need to get your data off and get a different drive..
Cheers G
On 5 Jan 2018 4:09 p.m., "Rob Malpass via Hampshire" <
hampshire@???> wrote:
> Hi all
>
>
>
> I can’t explain this – perhaps someone else can. I have a 2TB 3.5” ext4
> formatted internal drive (bought only in December) which was reporting
> errors yesterday. At the time, it was connected via USB Icybox JBOD and
> threw out more “short read” errors than I could count. I left it running
>
>
>
> e2fsck –y /dev/blablabla
>
>
>
> overnight and it was still reporting errors this morning. Getting fed up
> (and not wanting to write the unit off), I did
>
>
>
> mkfs /dev/blablabla
>
>
>
> and when I fired up rsync again – same type of IO errors. At this point
> I wrote the drive off and used a spare for my purposes.
>
>
>
> Curious to see if I could get any more information from the failing drive,
> I then moved it into a USB docking station on a different machine.
> Running e2fsck again and I got a clean filesystem (no new formatting or
> anything).
>
>
>
> Worried that this meant the drive was fine and potentially that particular
> bay in the (4 bay) Icybox might be the culprit, I moved the rogue drive
> back into the JBOD (same bay) and guess what – clean bill of health from
> e2fsck.
>
>
>
> So in short I have the same drive reporting errors, reformatted reporting
> errors, physically moved clean, then physically moved back clean. I’ve
> never been too hot on the rather low level way Linux handles disks – but I
> do want to know if the effing thing is good to use or not.
>
>
>
> Is a clean e2fsck result good enough? If so, were the hundreds of errors
> it was chucking out safely ignorable? Have I missed anything obvious?
>
>
>
> Cheers
>
> Rob
>
> --
> Please post to: Hampshire@???
> Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
> LUG URL: http://www.hantslug.org.uk
> --------------------------------------------------------------
>
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
