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

[Warren Sturm]

On Sat, 2007-12-08 at 20:50 -0500, Sam Varshavchik wrote:
> Craig Huff writes:
> 
> > On Dec 8, 2007 3:50 PM, Sam Varshavchik <mrsam at courier-mta.com> wrote:
> >> Craig Huff writes:
> >> > when I tried fdisk before and after using dd:
> >> > [root at penguin ~]# fdisk /dev/sda
> >> >
> >> > Unable to read /dev/sda
> >> > [root at penguin ~]# dd if=/dev/zero of=/dev/sda bs=512 count=1
> >> > dd: writing `/dev/sda': Input/output error
> >>
> >> Now, does anything further get logged to /var/log/messages, at this point?
> >>
> > 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?
> 
> > As far as John's suggestion to put the jumper back in and try it on
> > the SATA1 ports, it will have
> > to wait a few hours (~5) while shows that are scheduled to record
> > finish. ;-)  After that, I can take
> > the system down to work on the drive and reboot.
> 
> 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.