[mythtv-users] Gotchas replacing FC6 disk with new one?

[Craig Huff]

On Dec 8, 2007 8:00 PM, Warren Sturm <wrsturm at shaw.ca> wrote:
>
> On Sat, 2007-12-08 at 20:50 -0500, Sam Varshavchik wrote:
> > Craig Huff writes:
<snip>
> > > I tried tail -f /var/log/messages in another window while I ran "fdisk /dev/sda"
> > > again and got a *lot* of messages.  Here are samples:
> > >
> > > Dec  8 16:14:53 localhost kernel: ata3.00: exception Emask 0x0 SAct
> > > 0x0 SErr 0x0 action 0x0
> > > Dec  8 16:14:53 localhost kernel: ata3.00: cmd
> > > c4/00:20:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 16384 in
> > > Dec  8 16:14:53 localhost kernel:          res
> > > 51/04:20:00:00:00/04:00:3a:00:00/e0 Emask 0x1 (device error)
> >
> > Ugh, yeah. That definitely looks like a problem.
> >
> > > Unfortunately, I don't understand what it may be telling about the
> > > situation.  Did I get a bad disk out of the starting gate?
> >
> > This does not look like a bad disk to me, but this is not really my cup of
> > tea. We need to wait and hope our resident SATA guru notices this thread,
> > and jumps in for the rescue. How about you rename this thread to "SATA
> > errors -- help", report the capsule summary of your situation, and the
> > entire error log, from start to finish?
> >
<snip>
> >
> > This looks like something either not jumpered correctly, or the cable is
> > bad, or it's plugged in wrong. That would be my guess.
>
> Another thing to check is that the controller has raid mode disabled in
> the BIOS.
>
Bingo!  Turns out that the data cable (as I have read in other threads) is
notorious for not being a secure electrical connection.  When I pulled
the drive
to test one last time before trying to make the suggested changes, it worked
just fine laying in the bottom of the chassis.  Now I just have to get it to
behave when it's in the drive cage where it belongs.  Many thanks for the
helpful suggestions.

Craig.