Acer Veriton Z4860G - cannot find disk on system NVMe PCIe Non-RAID



  • Hello wonderful people,

    I’m unable to create an image due to the hdd not being detected.

    lsblk blkid shows no output

    The hdd is Micron 2200

    From what I’ve read I might have to upgrade to trunk, is there anything else to try beforehand?

    Thank you


  • Moderator

    @Pikmin Understand it only needs to be in ahci mode for imaging, once the image is laid down just switch it back to raid-on mode before the first boot of windows. Or if you are not using any raid function, just leave it in ahci mode. There isn’t much of a performance penalty for leaving it in ahci mode.



  • @george1421

    In BIOS Advanced
    Intel ® Rapid Storage Technology

    Intel ® RST 17.2.0.3790 RAID Driver

    Non-RAID Physical Disks:
    PCIe 1.0, Micron_2200_something_something

    Physical Disk Info
    Status: Non-RAID
    Controller Type: NVMe
    Controller Interface: NVMe

    I guess I’ll just set the SATA mode to AHCI for now, good enough for me.

    Thank you for your insight and help with the matter


  • Moderator

    @Pikmin said in Acer Veriton Z4860G - cannot find disk on system NVMe PCIe Non-RAID:

    00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 10)

    Ok this system is doing the same as the dells in that when raid-on mode is configured the above adapter appears, when set to ahci mode the sata adapter appears.

    00:17.0 SATA controller [0106]: Intel Corporation Device [8086:a352] (rev 10)

    I’m speaking for the Dells, but I think the rule also applies here. Linux, uefi, and raid-on mode is an incompatible configuration (because intel has not released the specs or drivers for the Intel RST disk controller). If you change any one of the three you will be able to see the disks behind the raid controller (in reality your only option if you want to image with FOG is the disk controller mode).

    Understand this is a linux kernel issue not something specific with FOG. Any linux distro will have an issue with this configuration.



  • @george1421

    Thank you, I’ve tried and no success

     uname -a
    Linux fogclient.localdomain 5.5.3 #1 SMP Tue Feb 11 16:53:17 EST 2020 x86_64 GNU/Linux
    [Wed Feb 12 root@fogclient ~]# lspci -nn
    00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3ec2] (rev 07)
    00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92]
    00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911]
    00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:a379] (rev 10)
    00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a36d] (rev 10)
    00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a36f] (rev 10)
    00:14.3 Network controller [0280]: Intel Corporation Device [8086:a370] (rev 10)
    00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:a368] (rev 10)
    00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a360] (rev 10)
    00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 10)
    00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a33e] (rev f0)
    00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a308] (rev 10)
    00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
    00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
    00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:a324] (rev 10)
    01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0e)
    01:00.1 Serial controller [0700]: Realtek Semiconductor Co., Ltd. Device [10ec:816a] (rev 0e)
    01:00.2 Serial controller [0700]: Realtek Semiconductor Co., Ltd. Device [10ec:816b] (rev 0e)
    01:00.3 IPMI SMIC interface [0c07]: Realtek Semiconductor Co., Ltd. Device [10ec:816c] (rev 0e)
    01:00.4 USB controller [0c03]: Realtek Semiconductor Co., Ltd. Device [10ec:816d] (rev 0e)
    
    

  • Moderator

    @Pikmin Sorry I missed this embedded in the other output.

    Linux fogclient.localdomain 4.19.48
    

    So based on that kernel you probably have FOG 1.5.5 or 1.5.6.

    While I don’t think its going to help here, I just built a one off kernel of 5.5.3 that you might try on this hardware. I can’t find the exact manufacture date of this hardware, but it seems pretty new.

    https://drive.google.com/open?id=1thopskSYJd7ueDQeFg_VT4eeNcrNHvIx
    Download this as bzImage553 (watch the case) then move it to /var/www/html/fog/service/ipxe directory on the fog server.
    Go into the web ui and for the host definition for this target host, enter bzImage553 in the kernel field. Then pxe boot the computer back into debug mode and run lsblk Lets see if a really new kernel works with that really new hardware.

    Yes if ahci mode doesn’t see the hard drive with the lsblk command, switch it back to RST mode and try the 5.5.3 kernel



  • @george1421

    You want me to change back from AHCI to RST with Optane in the BIOS and then check the logs?

    I thought I pasted the output of uname -a from the debug

    EDIT:

    Set the BIOS SATA mode back to RST

    Only interesting thing I found is this, note syslog file doesn’t exist

    [Wed Feb 12 root@fogclient ~]# cat /var/log/messages | grep -i nvme
    Feb 12 10:12:05 fogclient user.warn kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices.
    

    You’re running the latest stable version: 1.5.7
    bzImage Version: 4.19.48
    bzImage32 Version: 4.19.48


  • Moderator

    @Pikmin said in Acer Veriton Z4860G - cannot find disk on system NVMe PCIe Non-RAID:

    1344:5410

    well that driver has been in the linux kernel since 4.4. So unless you are using a really old version of FOG it should be supported.

    So the next we need to run this on the target computer in debug mode grep nvme /var/log/syslog note it also might be /var/log/messages What we want to do is search the startup log for nvme to see if there are any error messages regarding the startup of the nvme driver.

    Also what is the output of uname -a on the target computer. I need the kernel version.



  • @george1421 Sorry for taking my time, had to wait for the image to upload

    [Wed Feb 12 root@fogclient ~]# uname -a
    Linux fogclient.localdomain 4.19.48 #1 SMP Sun Jul 14 13:08:14 CDT 2019 x86_64 GNU/Linux
    [Wed Feb 12 root@fogclient ~]# lspci -nn
    00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3ec2] (rev 07)
    00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e92]
    00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911]
    00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:a379] (rev 10)
    00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a36d] (rev 10)
    00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a36f] (rev 10)
    00:14.3 Network controller [0280]: Intel Corporation Device [8086:a370] (rev 10)
    00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:a368] (rev 10)
    00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a360] (rev 10)
    00:17.0 SATA controller [0106]: Intel Corporation Device [8086:a352] (rev 10)
    00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:a32c] (rev f0)
    00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a33e] (rev f0)
    00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a308] (rev 10)
    00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
    00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
    00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:a324] (rev 10)
    01:00.0 Non-Volatile memory controller [0108]: Micron Technology Inc Device [1344:5410] (rev 01)
    02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0e)
    02:00.1 Serial controller [0700]: Realtek Semiconductor Co., Ltd. Device [10ec:816a] (rev 0e)
    02:00.2 Serial controller [0700]: Realtek Semiconductor Co., Ltd. Device [10ec:816b] (rev 0e)
    02:00.3 IPMI SMIC interface [0c07]: Realtek Semiconductor Co., Ltd. Device [10ec:816c] (rev 0e)
    02:00.4 USB controller [0c03]: Realtek Semiconductor Co., Ltd. Device [10ec:816d] (rev 0e)
    
    

    Also,

    *-pci:0
                 description: PCI bridge
                 product: Intel Corporation
                 vendor: Intel Corporation
                 physical id: 1b
                 bus info: pci@0000:00:1b.0
                 version: f0
                 width: 32 bits
                 clock: 33MHz
                 capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
                 configuration: driver=pcieport
                 resources: irq:16 memory:8d200000-8d2fffff
               *-storage
                    description: Non-Volatile memory controller
                    product: Micron Technology Inc
                    vendor: Micron Technology Inc
                    physical id: 0
                    bus info: pci@0000:01:00.0
                    version: 01
                    width: 64 bits
                    clock: 33MHz
                    capabilities: storage pciexpress msix msi pm nvm_express bus_master cap_list
                    configuration: driver=nvme latency=0
                    resources: irq:16 memory:8d200000-8d203fff
    
    

  • Moderator

    @Pikmin Ok the next bit is we need to see what the lspci command gives us. Then we can cross reference the hardware codes to the linux kernel.

    Also while you are connected to the target computer issue a uname -a to get the kernel version of FOS Linux



    1. Switching to legacy doesn’t make a difference

    2. I couldn’t see an option specifically for the NVMe but only for SATA, changed it and seems to be a success

    Onboard SATA Controller: Enabled
    NVMe Port 1: Enabled
    Onboard SATA Mode: RST with Optane (other option is AHCI)

    Thanks for your help George1421

    I just have to work out whether changing the SATA mode will have any problems with my image

    Thanks for the debug mode tip, nice to see ssh server is running
    Regards,
    Pikmin


  • Moderator

    I guess a few things we can try.

    1. If you switch to bios (legacy mode) is the hard drive discovered?
    2. Does in your bios can you change the disk mode to ahci? Does that provide any usable information?
    3. You were able to issue the lsblk command and no disk was visible, what do you get when you issue lspci -nn hint if you want to make it easier to copy and paste commands into debug mode do the following.
      3.1 PXE boot into debug mode as you have done before
      3.2 Give the root user a password with passwd make it something simple like hello
      3.3 Key in ip addr show and get the IP address of the target computer.
      3.4 Use putty or other ssh application to remote into the target computer as root using the password and IP address you collected above. Then issue the lspci -nn command via putty. With putty you can copy and paste the output easier. Posts the output of lspci command here
    4. Please tell us the version of FOG you are using
    5. What version of the FOS Linux kernel are you using?

Log in to reply
 

288
Online

6.8k
Users

14.1k
Topics

133.3k
Posts