[mythtv-users] Consequences of drive failure

[Nick Rout]

On Mon, Dec 3, 2012 at 1:12 AM, Mike Perkins
<mikep at randomtraveller.org.uk>wrote:

> On 02/12/12 09:22, Phill Edwards wrote:
>
>> On 02/12/2012 6:25 AM, "Mike Perkins" <mikep at randomtraveller.org.uk>
>> wrote:
>>
>>>
>>> Okay. So I've discovered that one of the two 500Gb drives in my recording
>>>
>> storage group is failing, enough that I'm getting jumps during playback
>> and
>> indecipherable error messages in dmesg.
>>
>>>
>>> I've ascertained that there is enough auto-expirable files in the system
>>>
>> that I can run on one drive until the newly-ordered ones arrive next week,
>> so I've pulled the SATA cable. It's not comfortable, but doable, and the
>> alternative is writing fresh recordings to a dying disk.
>>
>>>
>>> My question is, how does the system react when you take half the
>>>
>> recordings away? They are all still present in the database, but is there
>> any indication that they are or are not available for watching?
>>
>>>
>>>
>> I think there is a script you can run somewhere which you can run and it
>> will prompt you to sync database with whatever recording files exist. I
>> can't remember what it's called but someone else will surely know.
>>
>>  Well, fine, but my intention is to try and recover what I can off the
> dying disk when the new ones arrive. (I won't do this from within mythtv,
> but on another box.) I'll simply copy from the two old disks to the two new
> ones and then install the new ones at the original mount points. With any
> luck mythtv might not even notice :)
>
>
>
My experience was that I lost a couple of recordings - most likely those
that had damaged sectors of course. Once you have everything back in place
find_orphans.py will find database entries with no file and files with no
database entry.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20121203/149183b9/attachment-0001.html>