On 12/03/2018 Rick Stevens <ricks(a)alldigital.com> wrote:
Yes, Doc, I get it. Having never done this myself, I can only
suggest
things. I believe you'll need to run "mdadm --auto-detect -v" to see
if
it can find the RST RAID metadata. If it finds the RST data, it
should
create a container device that represents the RST array. You should
then
be able to create a device from that container (and I'd suggest a
read-
only device) using "mdadm -A" would represent the RST array.
Again, I've never done this with an Intel RST array and I'm not sure
any of my machines lying about have this "feature" enabled so I can't
do any investigation myself. mdadm says it can deal with it and a
google
search reveals some results with Mint and Scientific Linux.
-------------------------------------------------------------------
---
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com
-
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2
-
-
-
- "You think that's tough? Try herding
cats!" -
-------------------------------------------------------------------
---
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Rick,
I'm still chipping away at this. I've had to solve a couple of blockers
using Live ISO images. For example, I had to change a BIOS display
setting from [Hybrid] to [Discrete] to get a proper X screen after the
GNOME display manager starts. There was also a bug in thinkpad-acpi
that I had to report to the developers.
I just booted the system using the Fedora-MATE_Compiz-Live-x86_64-
Rawhide-20190217.n.0.iso image on a thumb drive. I was hoping that the
latest 4.20 kernel might support the Intel RST. Running "mdadm --auto-
detect -v" seemed to create a /dev/md0 block device, but "mdadm --
details /dev/md0" says it has no members.
The problem still seems to be the Intel RST chip tightly bound to the
NVMe SSDs. I can break the factory RAID1 by changing the BIOS Storage
setting from [RST] to [AHCI], but I'm not ready to pull that grenade
pin just yet. There must be a non-destructive path to accessing the
native NVMe interfaces without having to resort to SATA emulation.
--Doc