[mythtv-users] No 6 O'clock News

Daryl McDonald darylangela at gmail.com
Wed Mar 20 15:18:45 UTC 2019


On Wed, Mar 20, 2019 at 7:39 AM Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Wed, 20 Mar 2019 07:16:39 -0400 (EDT), you wrote:
>
> >In my experience, a DRDY is an indication of a failing drive.
> >
> >Doug
>
> It can also be a bad cable, or even a bad SATA port.  Almost certainly
> a hardware fault though.  So it is worth just swapping the cable for a
> new one to see if that is the cause.  And it can happen where a cable
> was not quite plugged on properly and has worked loose or expanded and
> contracted with temperature cycles and is no longer making good
> contact.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


We went down the hardware path recently, I replaced my mobo and sata cables
and power cables, and the problem returned. running the e2fsck repairs the
corruption in the drive and away we go again. This is occurring on a new
drive that had the recordings cloned/copied onto it, and the corruption too
I assume. Is there a switch that I can add to "sudo e2fsck /dev/sd** -y" to
make it report to a text doc that I can share with the list to shed further
light? It may take a while for corruption to recur, but I'd like to find
out why and address the root cause.
My skills are at the enthusiastic amateur level, and I'm open to
suggestions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190320/f61f2603/attachment-0001.html>


More information about the mythtv-users mailing list