M.2 Nvme Ssd Not Showing Up
Eliane Lebouf
I bought an SSD on sale to add storage to my laptop for games and school things, and I'm unable to format it because it's not showing up on Disk Management. I have a G3 15 3500, and in BIOS the system recognizes it's there, and it's in RAID mode, but I haven't been able to figure out what the issue is? Any tips?
lspci will show you information about PCI buses in the system and devices connected to them, while lsblk will show you information about all available or the specified block devices. In other words, lspci will show you the controller on the PCI bus, whereas lsblk will show you the disk that is connected to the controller.
Basically I think you should try to get a disk image of your disk or make a raw copy to another disk, and then try to save data from that, and leave your faulty disk in peace.
You should not write to the faulty disk - you can copy it and work with the copy.
I should have been clearer that it does not appear at all in lsblk. Not that the partitions don't show. Or can bad data can make lsblk ignore a disk?
It also has no entry under /dev like the other nvme drive I have. It should show as nvme1 like the boot log mentions briefly before giving up on it.
I am running a Pod on my Kubernetes cluster with root privilege, hostNetwork: true and a few resources like shm, hughpages. And I am using a image that has a Fedora 33 base OS image and on top of it I have installed a few additional dependencies. And I wish to use nvme module for nvme discover and nvme connect commands inside my container.
With Docker alone, I needed all these extra flags on to have access to a USB device and use some modules inside the container in this project I did. Might be helpful in checking if you figured out the 1:1 equivalents for Kubernetes to make those containers.
Actually I was using a few libraries which require python 3.6 and fedora:33 have python 3.9 preinstalled. So in my image I had to install python 3.6 and replace /bin/python3 with /bin/python3.6 in order for the libraries to work.
I tried figuring out where actually was the origin for the problem and maybe it is with the installation that I am carrying out for python3.6, as after that I am not able to use dnf (it seems to be broken).
So I installed nvme-cli in my image before I deal with the python versions and it is working that way. I am able to use nvme module in the container.
I'm running a Gigabyte Aorus X570 Master (Rev 1.1) with an 3950X CPU and Windows 11. I've got a M.2 NVMe for the OS and 4 U.2 NVMe devices for data. The latter ones I configured via BIOS RAIDXpert2 as RAID-10. The array is configured well, devices show up in BIOS and the array is in ready state.
Today I found at the BIOS RAIDXpert2 that the 4 NVME devices are not connected to one of the AMD-RAID controllers but instead have a single controller ID for each. Unfortunately I did not find a way to assign the devices to the AMD-RAID controller.
I'm having the exact same issue with this. I have 8 NVMe drives that are not showing up in RAIDXpert2 but I can see them in the bios. I have the raid drivers up to date and the correct bios confiuration per the AMD raid usr guide. I can't figure out what needs to happen for them to work.
So i recently bought my dad new PC parts and today we finally had the time to start the installation of Windows 11. Everything was fine till the point where we had to decide on which Drive we wanted to install Win11 and the Setup showing that no drives were detected.
The only drive currently installed is a NVMe one (for safety and ease of install) which to work needs a fitting driver - Intel RST, but here is were the problems gets even worse, as we bought a brand new 14th gen CPU and Intel RST currently has no version for 14th gen CPUs (at least i didnt find one).
Secondly, NVMe requires that you use UEFI boot; you cannot use Legacy. Make sure you boot the Windows installer in UEFI mode and, during the Windows installation, make sure that you delete all existing partitions on the System drive (to ensure GPT partition table written to drive).
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
I have an Ubuntu 19.04 on a machine with an nvme drive. However, the drive is not found in /dev/nvme*. cat /proc/devices shows that nvme is loaded as a character device and not a block device and lsmod shows two loaded modules nvme and nvme_core. Any help on what is wrong here or how to debug would be appreciated.
i put a Samsung 980pro in my spare nvme slot on a hauwei matestation s , it shows up in device manager but not in Samsung magician. windows tell me device is working.i have tried replacing the driver with Samsung driver ,windows wont let me.
If it's not appearing in Disk Management, then it may be a limitation of some kind on the Huawei Matestation. I would then check on the manufacturer's site, or any management software that came preinstalled on the pc, to see if there isn't an option that you can configure.
If you get a new SSD and it won't show up in Windows Explorer, it's likely in the "uninitialized" state. You must initialize a disk before Logical Disk Manager can access it. Also, if an old SSD shows the "disk unknown not initialized" error, the reason is the same.
I have a 2013 Mac Pro SSD is not showing up in the utility list or in the terminal, but does show in about this Mac. Only the base boot drive shows up in the utility list and terminal. Any ideas on how to get the computer to read the SSD? Just installed a new SSD from OWC with same issue.
If you have installed a third party NVMe SSD, then you need to boot from macOS 10.13+ in order to see the SSD. Your screenshot shows you have macOS 10.13 installed, but I'm guessing when you boot into Recovery Mode you are booting into macOS 10.9 which originally shipped with the Mac Pro. In this case you will need to create a bootable macOS 10.13+ USB installer using the instructions in this Apple article:
If you received the Mac and it was booting to macOS on the internal drive, then yes, you can use your 2011 Mac to create a bootable macOS 10.13 USB installer to at least get the Mac Pro booting to the internal SSD where you can at least upgrade macOS to 11.x Big Sur.
In order to use the hack to upgrade the system firmware for Monterey, the Mac Pro's system firmware will need to be at least 195.x.x.x.x or greater and you will need to have macOS 10.13+ installed on the internal drive.
"I have a 2013 Mac Pro SSD is not showing up in the utility list or in the terminal, but does show in about this Mac. Only the base boot drive shows up in the utility list and terminal. Any ideas on how to get the computer to read the SSD? Just installed a new SSD from OWC with same issue."
The Disk Utility GUI is basically a graphical wrapper around "diskutil" and several other command line utilities. When using the command line it is best to filter for just the "internal" drives since you will get a list of over twenty virtual drives/volumes from the macOS installer ( "internal" may not be an available option with older versions of macOS -- should be ok for 10.10+).
As far a seeing the physical drive.....If the Mac doesn't have at least the system firmware provided by the macOS 10.13+ installer, then a third party NVMe SSD (aka "blade" SSDs) will not be seen at all. macOS 10.13+ added support for NVMe SSDs with a driver and also updated system firmware. Both the updated system firmware & NVMe driver are necessary to see a third party (or even Apple) NVMe SSD. The OWC Aura SSDs are NVMe based SSDs. OWC mentions the macOS 10.13+ requirement on the product page of the website.
If you replaced the original hard drive with a third party 2.5" SATA SSD (such as the OWC Mercury Electra series), then it should not matter what OS you are installing. If you are using a 2.5" SATA SSD and you don't see the 2.5" SSD, then maybe you have a loose cable or a bad SSD. You can connect a 2.5" SATA SSD externally using a USB to SATA Adapter, drive dock, or enclosure to test if the SSD is working.
Also note that to install Monterey you need an Apple SSD installed since the Monterey installer includes an update to the Mac's firmware and the installers checks to see if there is an Apple SSD installed since it writes to the SSD in order to update the Mac's firmware. If not Apple SSD the Monterey install terminates.
Perhaps if you are using a third party NVMe SSD. You can update the Mac's system firmware by installing an original Apple OEM SSD into this Mac and install macOS 12.x Monterey in order to update the system firmware. I believe @lllaass suggested another way to upgrade the system firmware if you don't have the original Apple OEM SSD.
You are using a third party NVMe SSD which requires macOS 10.13+ in order to see & use the SSD! This is why the "diskutil list internal" command gave you no results since you were most likely booted from macOS 10.9 which is the version of macOS which originally shipped with this Mac and may be the only online installer you are able to access.
You can install macOS 10.9 to 10.12 to an external drive in order to upgrade the external drive to macOS 10.13+ so you will see the internal third party NMVe SSD, or you can then create a bootable macOS 10.13+ USB installer so that you can finally boot the correct installer which will see the internal third party NVMe SSD.
No, because the macOS 12.x Monterey installer will refuse to update the system firmware while a third party SSD is installed internally even though you are installing macOS to an external drive. You need to install an original Apple OEM SSD internally, then you will be able to install macOS 12.x Monterey and update the system firmware. After the system firmware has been updated, then you can reinstall the third party NVMe SSD and install macOS 12.x Monterey to the internal or external drive.
d3342ee215