SOLVED M.2 not recognised during deploying stage


  • @sebastian-roth Yes. There is no issue when using USB Windows 10 Installation media.

  • Moderator

    @will said in M.2 not recognised during deploying stage:

    The Lexar M.2 is having the same “can not find disk on system” issue with Asus Prime B550M-A motherboard.

    Have you tried installing plain Windows on the Lexar M.2 in combination with those mainboards yet? Just want to rule out general hardware incompatibility…


  • @fog_newb Sorry for the confusion. I mean the Gigabyte B550M Gaming motherboard and Lexar NM700 256GB M.2 SSD for the “2 modules”.

    The Lexar M.2 is having the same “can not find disk on system” issue with Asus Prime B550M-A motherboard.


  • @george1421 The output for the two commands:

    [Fri Mar 12 root@fogclient ~]# lsblk
    [Fri Mar 12 root@fogclient ~]# lspci -k -nn
    00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
    	Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
    lspci: Unable to load libkmod resources: error -12
    00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
    	Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481]
    00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
    00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
    	Kernel driver in use: pcieport
    00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
    	Kernel driver in use: pcieport
    00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
    00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
    00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
    	Kernel driver in use: pcieport
    00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
    00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
    00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
    00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
    	Kernel driver in use: pcieport
    00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
    00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
    	Kernel driver in use: pcieport
    00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
    	Subsystem: Gigabyte Technology Co., Ltd FCH SMBus Controller [1458:5001]
    00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
    	Subsystem: Gigabyte Technology Co., Ltd FCH LPC Bridge [1458:5001]
    00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440]
    00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441]
    00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442]
    00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443]
    00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444]
    00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445]
    00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446]
    00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447]
    01:00.0 Non-Volatile memory controller [0108]: Marvell Technology Group Ltd. Device [1b4b:1092]
    	Subsystem: Device [1d97:1092]
    	Kernel driver in use: nvme
    02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ee]
    	Subsystem: ASMedia Technology Inc. Device [1b21:1142]
    	Kernel driver in use: xhci_hcd
    02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device [1022:43eb]
    	Subsystem: ASMedia Technology Inc. Device [1b21:1062]
    	Kernel driver in use: ahci
    02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43e9]
    	Kernel driver in use: pcieport
    03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
    	Kernel driver in use: pcieport
    03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
    	Kernel driver in use: pcieport
    03:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
    	Kernel driver in use: pcieport
    03:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
    	Kernel driver in use: pcieport
    03:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
    	Kernel driver in use: pcieport
    08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 16)
    	Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
    	Kernel driver in use: r8169
    09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 560] [1002:67ff] (rev ff)
    	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (Radeon RX 560) [1002:0b04]
    09:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0]
    	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0]
    0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
    	Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
    0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
    	Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
    0b:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486]
    	Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486]
    0b:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
    	Subsystem: Gigabyte Technology Co., Ltd Matisse USB 3.0 Host Controller [1458:5007]
    	Kernel driver in use: xhci_hcd
    0b:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487]
    	Subsystem: Gigabyte Technology Co., Ltd Starship/Matisse HD Audio Controller [1458:a184]
    

    messages.txt


  • @will said in M.2 not recognised during deploying stage:

    But when put these 2 modules together

    What do you mean by put them together? Like in onboard RAID?

    Is it possible like with NVMe drives, the M.2s are initializing at different times during the boot process and the drives switch places? Like changes from say /dev/nvme0n1 to /dev/nvme1n1?

  • Moderator

    @will OK this will take a little work on your side.

    1. Setup a new debug capture/deploy (doesn’t matter). Schedule a new deploy task but before you hit the schedule task button tick the debug checkbox.
    2. Now pxe boot the target computer after a few screens of text you will be dropped to the FOS Linux command prompt.
    3. Key in ip a s and collect the ip address of the target computer
    4. Key in passwd and give root a one time password. Make it simple like hello
    5. Use putty or ssh to connect to the target compute using the above information. hint this method will allow you to copy and paste commands into the FOS Linux system.
    6. Now key in the following. I need to know the output of each.
      lsblk
      lspci -k -nn
    7. Using Winscp or scp I need the contents of the syslog file from /var/log directory.

    That should give us an idea what we are dealing with.


  • @george1421 Hi, George

    I can confirm this M.2 is running at AHCI mode, not behind any RAID controller.

    This M.2 model is working with other motherboards (i.e GigaByte B550 Aorus Elite & Gaming X, ASUS & MSI B550, B550M, X570…).
    GigaByte B550M Gaming motherboard is also working with other M.2 models (i.e WD SN550 1TB, Crucial P1 1TB…).

    But when put these 2 modules together, FOG will report “cannot find disk on system”.

  • Moderator

    @will Its possible that the disk is hiding behind a raid controller. I don’t know the Gigabyte motherboard, but look in the firmware under disk controller mode. If the setting is anything other than ahci mode, try it in ahci mode. There is a known issue between linux, uefi, and the intel raid controller in raid-on mode. You are running a pretty new kernel so it should support that mobo. FOG does have a later kernel 5.10.12 but then you will loose the realtek patch in the kernel you have. I would check to see if there is a disk controller mode first.

292
Online

9.1k
Users

15.7k
Topics

145.8k
Posts