Date: Thu, 18 May 2017 14:28:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219372] ataraid does not recognized by new kernel 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219372-8-pL0RfrZ6N9>