[mythtv-users] Broken recordedseek table - what next?

[Nick Rout]

On Mon, Jun 21, 2010 at 6:55 PM, Robert Johnston <anaerin at gmail.com> wrote:
> On 21/06/2010 12:21 AM, David Whyte wrote:
>>
>> On Mon, Jun 21, 2010 at 4:06 PM, Nick Rout<nick.rout at gmail.com>  wrote:
>>
>>> What now? Is there a way to repair it?
>>>
>>
>> I often run the 'repair' options from the MythWeb>  Settings pages
>> when I get corrupt tables.
>
> If repairing simply won't work (Which it seems, from the log posted, has
> been tried and failed), you could always drop and re-make the table, then
> use mythcommflag to rebuild the seek tables. That would take a while, but
> would ensure you have few problems.
>
> Of course, you could always use the backup that the cron job produced to
> re-create the table, and mythcommflag to rebuild the missing seek table
> entries. This would reduce the time spent rebuilding, but would rely on you
> being able to pick the correct create/insert statement block(s) from the
> backup.


I have a backup that is a week old (today's failed, presumably because
of the corruption).

When I try either run the cron script, or do REBUILD TABLE
recordedseek; within mysql's command line I get this stuff repeated in
dmesg:

[  191.197909] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[  191.198560] ata1.01: BMDMA stat 0x64
[  191.199179] ata1.01: failed command: READ DMA
[  191.201612] ata1.01: cmd c8/00:08:b8:5c:50/00:00:00:00:00/f1 tag 0
dma 4096 in
[  191.201615]          res 51/40:00:ba:5c:50/00:00:00:00:00/f1 Emask
0x9 (media error)
[  191.206270] ata1.01: status: { DRDY ERR }
[  191.208730] ata1.01: error: { UNC }
[  191.216629] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f,
BIOS=0x1f000 (0xc5c60000) ACPI=0x1f01f (30:20:0x1f)
[  191.216640] ata1: nv_mode_filter: 0x3f39f&0x3f39f->0x3f39f,
BIOS=0x3f000 (0xc5c60000) ACPI=0x3f01f (30:20:0x1f)
[  191.232300] ata1.00: configured for UDMA/66
[  191.248581] ata1.01: configured for UDMA/100
[  191.248612] sd 0:0:1:0: [sda] Unhandled sense code
[  191.248617] sd 0:0:1:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  191.248626] sd 0:0:1:0: [sda] Sense Key : Medium Error [current] [descriptor]
[  191.248636] Descriptor sense data with sense descriptors (in hex):
[  191.248642]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[  191.248660]         01 50 5c ba
[  191.248668] sd 0:0:1:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[  191.248680] sd 0:0:1:0: [sda] CDB: Read(10): 28 00 01 50 5c b8 00 00 08 00
[  191.248698] end_request: I/O error, dev sda, sector 22043834
[  191.249305] ata1: EH complete


This seems to resolve in google to hard drive errors, so I booted to a
ubuntu desktop cd and ran fsck /dev/sda2 but it declares that all is
well.

sda is an older 20G IDE hard drive that i used to attempt to put the
OS and database on a separate spindle. Maybe it is dying and the
stress of the database rebuild causes a developing error to manifest
itself?