Comment 5 for bug 1372547
Revision history for this message
| Wasis Adi Putranto (wasis-putra) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I think nvme disk can appear on UI because the bootstrap image that fuel used based on centos kernel (and upgraded to 3.11).
nvme driver already added to linux kernel since 3.10.
the problem is, even nvme disk can appear and configured as the other disk from fuel UI, the disk left unconfigured.
using ubuntu default image (kernel 3.2), nvme not detected yet, so the installation progress will stop. nvme disk will detected after kernel upgraded to 3.11 using preseed.
while using centos default image, nvme already detected, but the installation still fail because the kickstart partition the disk as nvmeXY. it is suppose to be nvmeXpY.
in my case, installer partition my disk become nvme01 (mimicking sda1, hda1, vda1), and it shoud be nvme0p1