[SOLVED] Installer does not see the NVMe drive
[SOLVED] Installer does not see the NVMe drive
Hi All,
I am trying to install MX Linux 18.2 on my new laptop that has a 256GB Toshiba NVMe drive and Windows 10 installed. The problem is that the installer does not seem to 'see' the NVMe drive! I have turned off BitLocker but that did not help. When I run the partition tool within the installer, it shows only the USB drive that contains the MX Linux ISO.
Any ideas?
Thanks in advance.
NN
I am trying to install MX Linux 18.2 on my new laptop that has a 256GB Toshiba NVMe drive and Windows 10 installed. The problem is that the installer does not seem to 'see' the NVMe drive! I have turned off BitLocker but that did not help. When I run the partition tool within the installer, it shows only the USB drive that contains the MX Linux ISO.
Any ideas?
Thanks in advance.
NN
Last edited by nhutnn on Thu May 09, 2019 11:33 pm, edited 1 time in total.
Re: Installer does not see the NVMe drive
Please boot from the MX USB pendrive, run MX Tools/Quick System Info and post the results (inside of code tags: the </> icon in the forum editor toolbar.)
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: Installer does not see the NVMe drive
Thanks for the quick response JayM! Here is the output:
Only the MX Linux USB pendrive was listed, it seems.
Code: Select all
System:
Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum Apr 7 2019
base: Debian GNU/Linux 9 (stretch)
Machine:
Type: Laptop System: Dell product: Latitude 5591 v: N/A serial: <filter>
Mobo: Dell model: 0CGP1G v: A00 serial: <filter> UEFI: Dell v: 1.7.4
date: 04/26/2019
Battery:
ID-1: BAT0 charge: 81.9 Wh condition: 87.4/92.0 Wh (95%)
model: SMP DELL WFWKK65 status: Discharging
CPU:
Topology: 6-Core model: Intel Core i7-8850H bits: 64 type: MCP
arch: Kaby Lake rev: A L2 cache: 9216 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31104
Speed: 1965 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 900 2: 900
3: 900 4: 900 5: 900 6: 900
Graphics:
Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2)
v: 4.5 Mesa 18.2.6 direct render: Yes
Audio:
Device-1: Intel vendor: Dell driver: snd_hda_intel v: kernel
bus ID: 00:1f.3
Sound Server: ALSA v: k4.19.0-1-amd64
Network:
Device-1: Intel driver: iwlwifi v: kernel port: 3000 bus ID: 00:14.3
IF: wlan0 state: down mac: <filter>
Device-2: Intel vendor: Dell driver: e1000e v: 3.2.6-k port: efa0
bus ID: 00:1f.6
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 29.25 GiB used: 22.4 MiB (0.1%)
ID-1: /dev/sda type: USB vendor: SanDisk model: Cruzer Blade
size: 29.25 GiB
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 bus ID: 00:17.0
Partition:
ID-1: / size: 12.30 GiB used: 22.4 MiB (0.2%) fs: overlay source: ERR-102
Sensors:
System Temperatures: cpu: 61.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Repos:
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ stretch main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
Processes: 223 Uptime: 1m Memory: 15.46 GiB used: 547.8 MiB (3.5%)
Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12
inxi: 3.0.29
Report copied to system clipboard
Press any key to close
Re: Installer does not see the NVMe drive
I did a Google(linux Toshiba NVMe drive) and found other people with a similar problem. One fix was to go into BIOS/UEFI setup and make sure the NVMEe device is in AHCI mode, not RAID mode. I think the problem is between the BIOS/UEFI setup and the linux kernel. I don't think it is distro specific. Our kernels do have CONFIG_BLK_DEV_NVME enabled which should let them access NVMEe devices. If changing the BIOS/UEFI settings doesn't work then you may find other solutions with a Google search or a search with a different search engine of your choice.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman
Re: Installer does not see the NVMe drive
@BitJam, I think you've nailed it:
It looks like his NVMe controller is using the ahci driver but is in RAID mode.
@nhutnn: While you're in your UEFI setup, don't forget to disable secure boot if you haven't already done so, otherwise MX won't install as it's not been digitally signed by Microsoft.
Also, this may be helpful: https://www.dell.com/support/article/us ... es?lang=en
Code: Select all
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 bus ID: 00:17.0
@nhutnn: While you're in your UEFI setup, don't forget to disable secure boot if you haven't already done so, otherwise MX won't install as it's not been digitally signed by Microsoft.
Also, this may be helpful: https://www.dell.com/support/article/us ... es?lang=en
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: Installer does not see the NVMe drive
Thanks for your help JayM and BitJam, appreciate it.
I think I need to ask tech support to reinstall Windows 10 under AHCI mode first since it will not boot if I change the controller mode.
I think I need to ask tech support to reinstall Windows 10 under AHCI mode first since it will not boot if I change the controller mode.
Re: Installer does not see the NVMe drive
You should probably ask them to leave some unallocated space on the disk for you if they can, to save yourself the trouble of having to resize the Windows partition later.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: [SOLVED] Installer does not see the NVMe drive
What is the point of RAID mode on a single device? ISTM the only purpose it serves is yet another way to lock out Linux.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman
- Head_on_a_Stick
- Posts: 919
- Joined: Sun Mar 17, 2019 3:37 pm
Re: [SOLVED] Installer does not see the NVMe drive
To allow users to upgrade to a multiple drive RAID configuration without having to reinstall the operating system.
mod note: Signature removed, please read the forum rules
Re: Installer does not see the NVMe drive
I recently changed a pre-Intalled Win10 from RAID to AHCI on a Dell. It's not obvious how to do it but it works without reinstalling.
Will post the Howto here (if I have not already done so ;=) ... beeing back in about 6 hours time or so...
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB