<div>I recently re-built my mythbox (software-wise) due to a malfunctioning hard drive. Unfortunately, I did something stupid. I thought that I would keep the 250GB drive in the machine and use it simply as a disk to record TV to since the data is "not critical". Well, we were watching a recording a few hours ago and it kept hanging for a few seconds then booting me back to myth. After this happened about 5 times, we gave up on watching it and watched something else. I did a little snooping around and it appears that the recording we were trying to watch was on the "failing disk" and I got a bunch of messages in my syslog from it like this:</div>
<div> </div>
<div>Nov 9 18:48:15 mythbox kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0<br>Nov 9 18:48:15 mythbox kernel: ata2.00: BMDMA stat 0x24<br>Nov 9 18:48:15 mythbox kernel: ata2.00: cmd 25/00:00:cf:77:f4/00:02:02:00:00/e0 tag 0 dma 262144 in<br>
Nov 9 18:48:15 mythbox kernel: res 51/40:00:37:78:f4/40:00:02:00:00/e0 Emask 0x9 (media error)<br>Nov 9 18:48:15 mythbox kernel: ata2.00: status: { DRDY ERR }<br>Nov 9 18:48:15 mythbox kernel: ata2.00: error: { UNC }<br>
Nov 9 18:48:15 mythbox kernel: ata2.00: configured for UDMA/133<br>Nov 9 18:48:15 mythbox kernel: ata2: EH complete<br></div>
<div>and</div>
<div> </div>
<div>Nov 9 18:48:21 mythbox kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0<br>Nov 9 18:48:21 mythbox kernel: ata2.00: BMDMA stat 0x24<br>Nov 9 18:48:21 mythbox kernel: ata2.00: cmd 25/00:00:cf:77:f4/00:02:02:00:00/e0 tag 0 dma 262144 in<br>
Nov 9 18:48:21 mythbox kernel: res 51/40:00:37:78:f4/40:00:02:00:00/e0 Emask 0x9 (media error)<br>Nov 9 18:48:21 mythbox kernel: ata2.00: status: { DRDY ERR }<br>Nov 9 18:48:21 mythbox kernel: ata2.00: error: { UNC }<br>
Nov 9 18:48:21 mythbox kernel: ata2.00: configured for UDMA/133<br>Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08<br>Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]<br>
Nov 9 18:48:21 mythbox kernel: Descriptor sense data with sense descriptors (in hex):<br>Nov 9 18:48:21 mythbox kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00<br>Nov 9 18:48:21 mythbox kernel: 02 f4 78 37<br>
Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4<br>Nov 9 18:48:21 mythbox kernel: end_request: I/O error, dev sdb, sector 49575991<br>Nov 9 18:48:21 mythbox kernel: ata2: EH complete<br>Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] 490234752 512-byte hardware sectors (251000 MB)<br>
Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Write Protect is off<br>Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00<br>Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA<br>
Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] 490234752 512-byte hardware sectors (251000 MB)<br>Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Write Protect is off<br>Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00<br>
Nov 9 18:48:21 mythbox kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA<br></div>
<div>I looked and sure enough /dev/sdb is hosting the recording that was giving me problems. So I want to remove that recording directory (from the broken disk) from myth but I want to do it so that the database doesn't get corrupted. How do I go about it? Can I just delete it from mythtv-setup? Will that update the database's list of recordings so that everything is happy??</div>
<div> </div>
<div>Thanks,</div>
<div>-Greg</div>