From owner-freebsd-bugs@freebsd.org  Fri May 19 15:53:11 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BDCAD74E1A
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 19 May 2017 15:53:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2B3421EA6
 for <freebsd-bugs@FreeBSD.org>; Fri, 19 May 2017 15:53:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4JFrARx085194
 for <freebsd-bugs@FreeBSD.org>; Fri, 19 May 2017 15:53:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 219372] ataraid does not recognized by new kernel
Date: Fri, 19 May 2017 15:53:11 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: oklaspec@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-219372-8-CrUK1tXLii@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219372-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-219372-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 May 2017 15:53:11 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219372

--- Comment #6 from oklaspec@gmail.com ---
Thank you! You're right. This is exactly what it is.
Disabling the specific "promise" metadata allows to work up
nvidia raid and success boot done.

I'd like to avoid bug anyway if it take place.

I test both disks last 8 sectors bytes all is zero.
I not found first 63 sectors some like "Promise Inc" signature.

Can some one explain what to check else.
Is there reference to "promise" format specs?
I can do some modifications of sources and build
user level app. But i need some explanations.

--=20
You are receiving this mail because:
You are the assignee for the bug.=