I am having problems with silent data corruption on (some) drives
connected to an MCP55 SATA controller.
I have two servers, both running RELENG_7_0/amd64. One has the 570 Ultra
chipset, the other has 570 SLI. Both chipsets have the MCP55 SATA
controller.
The server with 570 Ultra chipset has a
Hi,
Pyun YongHyeon wrote:
The 88E8062 support wasn't tested due to lack of hardware and I just
copied the device id from myk driver. Would you show me the output
of devinfo -rv| grep oui ? Also it would be better if I can see
verbosed boot message.
Here you go:
# devinfo -rv | grep oui
Hi
I'll look into that providing I can find HW to work on, IIRC I have
one in the ATA collection but I have to verify when I get to the lab.
-Søren
On 1Jul, 2008, at 11:01 , Daniel Eriksson wrote:
I am having problems with silent data corruption on (some) drives
connected to an MCP55
On Mon, Jun 30, 2008 at 4:20 PM, Yousef Raffah [EMAIL PROTECTED] wrote:
On Mon, Jun 30, 2008 at 2:03 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Mon, Jun 30, 2008 at 01:09:25PM +0300, Yousef Raffah wrote:
Hello,
I have a box which can't sync using cvsup, therefore, ...
Let's start here.
Daniel Eriksson wrote:
Unfortunately the drives does not have a jumper for setting SATA-150
speed (they are Samsung 1 TB drives), and trying to force the drives to
SATA-150 speed with the patch provided by the manufacturer does not
seem to work (the drives still negotiate SATA-300 speed). I will
Andrey V. Elsukov wrote:
Which patch did you use?
I used BDM_SpeedSwitch1.zip
(http://www.samsung.com/global/system/business/hdd/faq/2007/10/29/184337
BDM_SpeedSwitch1.zip).
/Daniel
___
freebsd-stable@freebsd.org mailing list
On Tue, Jul 01, 2008 at 11:01:17AM +0200, Daniel Eriksson wrote:
The server with 570 Ultra chipset has a bunch of older 250GB SATA-150
drives hooked up to the MCP55 controller and it is working just fine.
The server with 570 SLI chipset has a bunch of new SATA-300 drives
hooked up to the MCP55
Hi
OK, the only modern nVidia board I have is MCP51 based, however it
uses the same codepath as the MCP55.
Anyhow, there has been fixes fro these in -current, thats not in any
of the releng's yet.
Please try the attached patch, or even better try a -current kernel.
-Søren
ff
Jeremy Chadwick wrote:
With the same cables? Not that I want to use cables as a
scapegoat, but in this case it seems applicable.
With the same cables, yes.
Can you provide atacontrol cap output for one of the drives?
# atacontrol cap ad4
Protocol Serial ATA II
device model
Hello,
I just upgraded a machine from FreeBSD 6 to 7. Very nice.
But my portupgrade -fa failed after a while.
How can I know which ports/packages are still from FreeBSD 6? Is there a
datee recorded somewhere or the FreeBSD-version of the port/package?
The date of the files in /var/db/pkg/* is
Søren Schmidt wrote:
Please try the attached patch, or even better try a -current kernel.
The patch made no difference on RELENG_7_0 unfortunately. (And I cannot try
CURRENT on this server.)
___
Daniel Eriksson (http://www.toomuchdata.com/)
___
Hi All,
I installed a recent (as of today) RELENG_7 on one of our HP Blades.
Unluckily my serial output stops right when a getty at ttyd0 should kick
in. So I'm blind for the rest of the startup.
Very unfortunate.
The boot menu, as the bootup itself is printed out on serial console until:
da0:
Ronald,
Look for files that are older than your upgrade/portupgrade -fa date in
/usr/local/bin and /usr/local/sbin.
e.g. $ find $dir -mtime +2 -type f -xdev -print
Add a little guesswork/pkg_info to determine which ports they're from.
Throw in a few more forced recursive portupgrades incase
Date: Tue, 1 Jul 2008 11:01:17 +0200
From: Daniel Eriksson [EMAIL PROTECTED]
I am having problems with silent data corruption on (some) drives
connected to an MCP55 SATA controller.
I have two servers, both running RELENG_7_0/amd64. One has the 570 Ultra
chipset, the other has 570 SLI.
,--[ On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote:
| Hi,
|
| I am trying to bring up gigabit interface in couple of Nexcom blade servers
running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers)
are recognized properly, but no media is ever detected:
|
Chris Rees wrote:
I have a 570 SLI too (Asus M2N-SLI Deluxe), I've been looking for an
excuse to put FreeBSD on here :)
I'll start installing it, anything I should do to make this
error more obvious?
No, if it is a common problem with this chipset and/or MCP55 controller
revision (which I
On Thursday 26 June 2008 11:12:33 pm Kevin Oberman wrote:
Date: Thu, 26 Jun 2008 23:53:44 +0200
From: Volker [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On 12/23/-58 20:59, Kelly Black wrote:
Hello,
I have a problem with loader. I recently upgraded from 6_rel to 7_rel.
Now
On Tue, Jul 01, 2008 at 12:32:04PM +0200, Krzysztof J??druczyk wrote:
Hi,
Pyun YongHyeon wrote:
The 88E8062 support wasn't tested due to lack of hardware and I just
copied the device id from myk driver. Would you show me the output
of devinfo -rv| grep oui ? Also it would be better if
On Tue, Jul 1, 2008 at 6:13 AM, Yousef Raffah [EMAIL PROTECTED] wrote:
I guess I couldn't figure out how to checkout RELENG_7_0_0_RELEASE
from the mirror
[EMAIL PROTECTED]:/home/ncvs
I typed this:
# cvs checkout -r RELENG_7_0_0_RELEASE src
Can someone help with it, I can't spot an issue
Daniel Eriksson wrote:
I'm not sure if the problem is amd64 specific or not, but it seems the
people that have reported problems have all run amd64 (and not i386).
This might be a coincident though.
I have two motherboards with MCP55. They work well and I didn't
see any data corruption.
1.
This rhymes with sio deciding that your TTY is something other than
ttyd0. We had this same problem on Rackable -- even though the proper
tty was setup 0x3f8 irq 4 it was being assigned to sio1. You can see
this by 'grep sio /var/log/messages'
The only fix for this is to edit
21 matches
Mail list logo
