From owner-freebsd-bugs@freebsd.org  Thu May 18 14:28:14 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 B8FAFD723A9
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 18 May 2017 14:28:14 +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 A8E2D1E92
 for <freebsd-bugs@FreeBSD.org>; Thu, 18 May 2017 14:28:14 +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 v4IESESL024331
 for <freebsd-bugs@FreeBSD.org>; Thu, 18 May 2017 14:28:14 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: Thu, 18 May 2017 14:28:14 +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-pL0RfrZ6N9@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: Thu, 18 May 2017 14:28:14 -0000

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

--- Comment #4 from oklaspec@gmail.com ---
Thanks for useful info!

I found in `man graid` the section `Supported Metadata Formats`

The `NVIDIA` and the `Promise` formats is mentioned.

In dmesg from worked 8.3 declared:

    ar0: 305245MB <nVidia MediaShield RAID1> status: READY

In dmesg from "new" declared:

    GEOM_RAID: Promise: Array Promise created.

The interesting questions is this a normal or bug:

1. Why "new" see `Promise` instead of `NVIDIA`?

2. Why "new" does not see `NVIDIA`? (if `Promise` mean some else)=20

3. Why "new" does not recognize partition table and show
   only "ada0" and "ada1"? In `/dev` does not exists
   "/dev/ada1s1a", "/dev/ada1s1h" and so on?
   ("/dev/ad4s1a" "/dev/ad4s1h" is visible in 8.3)

Which command I need to use to load array from given disks?
The `graid label` will destroy data and kernel boot process
does not properly recognize existed bios nvidia raid markup.

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