MCP55 SATA data corruption in FreeBSD 7
utisoft at googlemail.com
Wed Jul 2 23:35:01 UTC 2008
On 02/07/2008, Chris Rees <utisoft at googlemail.com> wrote:
> > Date: Wed, 2 Jul 2008 10:55:07 +0200
> > "Daniel Eriksson" <daniel_k_eriksson at telia.com> wrote:
> > Jeremy Chadwick wrote:
> >> Can the OP get some non-Samsung disks for testing?
> > I've got a 750 GB Western Digital that I've been planning to use to
> > verify if it's a SATA-150 / SATA-300 problem (it can be jumpered to
> > SATA-150), but the drive is packed with valuable data that I'd have to
> > move elsewhere first.
> > I'll get to it eventually, but maybe not this week.
> > ___
> > Daniel Eriksson (http://www.toomuchdata.com/)
> Looks like I'm the guinea pig for now, I'll post in about half an hour
> with the results :)
> This is a clean install; it works perfectly with the restriction
> jumper on, now it comes off.
Real sorry fellas, can't reproduce on my M2N-SLI; chipset 570 SLI.
I've been building ports for hours on here, everything's working
perfectly I'm afraid.
# pciconf -lv
- snip -
atapci1 at pci0:0:5:0: class=0x010185 card=0x82391043 chip=0x037f10de
vendor = 'Nvidia Corp'
device = 'MCP55 SATA Controller'
class = mass storage
subclass = ATA
- snip -
# FreeBSD hydra.bayofrum.net 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #1:
Wed Jul 2 16:50:49 UTC 2008
chris at hydra.bayofrum.net:/usr/obj/usr/src/sys/HYDRA amd64
Looks like mine's hardware revision (rev=) 0xa3; yours however is 0xa2.
I had PS/2 port trouble on Linux, and needed a BIOS update, perhaps it
came with that? Is the revision a firmware or hardware property?
Good luck tracking that down, anyway, hope my tests helped :)
R< $&h ! > $- ! $+ $@ $2 < @ $1 .UUCP. > (sendmail.cf)
More information about the freebsd-stable