• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify

Scheduled Pinned Locked Moved
Hardware Compatibility
5
38
7.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    george1421 Moderator @AlexPDX
    last edited by Mar 15, 2023, 9:55 AM

    @AlexPDX Lets debug this a bit more then. If you have the target computer registered in FOG, then lets setup a debug capture or deploy doesn’t matter. So schedule a deploy task but before you hit the schedule task button tick the debug checkbox.

    Now pxe boot the target computer. After a few screens of text that you have to clear with the enter key you will be dropped to the fos linux command prompt.

    This next section is optional but will help with debugging so that you can copy and paste info a bit easier., Key in ip a s and get the IP address of the target computer. Next key in passwd and give root a password. Make it something simple like hello, no worries it will be reset when FOS Linux reboots. Now ssh or use putty to connect to the target computer using the IP address, user id of root and password you just set. This remote console will let you copy and paste.

    Now key in/paste the following info:
    lspci -nn | grep -i sata
    lspci -nn | grep -i raid
    grep -i firm /var/syslog

    Post the results here. The lspci commands will let us see what disk controller is being reported and the last will look to see if there is any missing firmware statements posted by the kernel.

    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

    A 2 Replies Last reply Mar 16, 2023, 8:32 AM Reply Quote 0
    • A
      AlexPDX @george1421
      last edited by Mar 16, 2023, 8:32 AM

      @george1421 Ok , ill do this…sorry for the late reply …i’m actually Help-desk Support in the company i work so yea…a lot of “Hello, IT, have you tried turning it OFF and ON again” 😀 …i just love FOG and makes things better 4me 🙂

      ill be back after the debugging

      1 Reply Last reply Reply Quote 0
      • A
        AlexPDX @Sebastian Roth
        last edited by Mar 16, 2023, 8:43 AM

        @Sebastian-Roth Exactly , in the web UI , hosts with SATA SDD’s , are acknowledged …hosts with NVMe SSD > not 😐
        The same Motherboard , if i attache SATA SSD and do a HW Inventory, it works fine …but if i attached the NVME M.2 SSD > the Hard Disk is BLANK just like in the attached images

        1 Reply Last reply Reply Quote 0
        • A
          AlexPDX @george1421
          last edited by Mar 16, 2023, 9:31 AM

          @george1421 ok so i got this :

          [Thu Mar 16 root@fogclient ~]# lspci -nn | grep -i sata
          00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] (rev 11)
          [Thu Mar 16 root@fogclient ~]# lspci -nn | grep -i raid
          [Thu Mar 16 root@fogclient ~]#
          [Thu Mar 16 root@fogclient ~]# grep -i firm /var/syslog
          grep: /var/syslog: No such file or directory

          but i did found this “messages” in /var/log of it helps : messeges.txt

          fggg.jpg

          G 1 Reply Last reply Mar 16, 2023, 9:54 AM Reply Quote 0
          • G
            george1421 Moderator @AlexPDX
            last edited by Mar 16, 2023, 9:54 AM

            @AlexPDX From the log it looks like the nvme is detected. At the fos linux command prompt key in lsblk and post the results. That should show us the block devices (i.e. hard drives attached)

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            A 1 Reply Last reply Mar 16, 2023, 10:15 AM Reply Quote 0
            • A
              AlexPDX @george1421
              last edited by Mar 16, 2023, 10:15 AM

              @george1421 said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

              From the log it looks like the nvme is detected. At the fos linux command prompt key in lsblk and post the results. That should show us the block devices (i.e. hard drives attached)

              [Thu Mar 16 root@fogclient /]# lsblk
              NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
              nbd0 43:0 0 0B 0 disk
              nbd1 43:32 0 0B 0 disk
              nbd2 43:64 0 0B 0 disk
              nbd3 43:96 0 0B 0 disk
              nbd4 43:128 0 0B 0 disk
              nbd5 43:160 0 0B 0 disk
              nbd6 43:192 0 0B 0 disk
              nbd7 43:224 0 0B 0 disk
              nvme0n1 259:0 0 232.9G 0 disk
              |-nvme0n1p1 259:1 0 100M 0 part
              |-nvme0n1p2 259:2 0 16M 0 part
              |-nvme0n1p3 259:3 0 996M 0 part
              `-nvme0n1p4 259:4 0 231.8G 0 part
              nbd8 43:256 0 0B 0 disk
              nbd9 43:288 0 0B 0 disk
              nbd10 43:320 0 0B 0 disk
              nbd11 43:352 0 0B 0 disk
              nbd12 43:384 0 0B 0 disk
              nbd13 43:416 0 0B 0 disk
              nbd14 43:448 0 0B 0 disk
              nbd15 43:480 0 0B 0 disk

              G 1 Reply Last reply Mar 16, 2023, 10:43 AM Reply Quote 0
              • G
                george1421 Moderator @AlexPDX
                last edited by Mar 16, 2023, 10:43 AM

                @AlexPDX Is this output from fos linux?

                the nbdX devices have me confused.

                On the NVMe side we can surely see the nvme disk is there and it has 4 partitions .

                Rereading your initial post, is it that FOS isn’t returning the hard disk model name, or it can’t image the computer?

                ref: /dev/ndbX devices: https://medium.com/@aysadx/linux-nbd-introduction-to-linux-network-block-devices-143365f1901b

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                T 1 Reply Last reply Mar 16, 2023, 10:53 AM Reply Quote 0
                • T
                  Tom Elliott @george1421
                  last edited by Tom Elliott Mar 16, 2023, 4:54 AM Mar 16, 2023, 10:53 AM

                  @george1421 From the looks of things and @AlexPDX please keep me honest:

                  This isn’t a problem from imaging. Simply the HDD information for the inventory isn’t present.

                  So while sure it’s weird that we can’t detect the drive type for the inventory, it’s not really hurting anything at the present as the Inventory is just an informational thing.

                  dmidecode (which I believe is what pulls all the inventory data) might just not know how to detect the specific information from that NVME either because the manufacture didn’t fill out the items that dmidecode is looking for, or is using a different language that can’t be utf decoded.

                  Just my thoughts.

                  Ultimately, there’s not really a “problem” persay. Just that the inventory can’t pull the information from this NVME device?

                  (I believe for HDD we use hdparm and all that jazz)

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  T A 2 Replies Last reply Mar 16, 2023, 11:00 AM Reply Quote 0
                  • T
                    Tom Elliott @Tom Elliott
                    last edited by Mar 16, 2023, 11:00 AM

                    @Tom-Elliott This is the location of the “get hard disk” elements:

                    https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L1405

                    This is the code that stores the hd returned from above link:
                    https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L106

                    To try to get information from it.

                    Since nvme0n1 is the drive, you could manually attempt running:
                    hdparm -i /dev/nvme0n1 to see what returns in the debug prompt?

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    A 1 Reply Last reply Mar 16, 2023, 11:39 AM Reply Quote 1
                    • S
                      Sebastian Roth Moderator
                      last edited by Mar 16, 2023, 11:12 AM

                      @Tom-Elliott said:

                      dmidecode (which I believe is what pulls all the inventory data) might just not know how to detect the specific information from that NVME either because the manufacture didn’t fill out the items that dmidecode is looking for, or is using a different language that can’t be utf decoded.

                      Pretty sure Tom is right here. Just had a quick look at the scripts and turns out we use hdparm (code ref) which might not be able to grab the information from NVMe disks per se.

                      @george1421 said:

                      the nbdX devices have me confused.

                      You are right. I am wondering if we added this kernel feature when updating to a newer LTS line at some point. I don’t think we need it. Though it’s always good to make sure. So here is the github commit that introduced those features years ago when we moved from 4.5.x to kernel 4.7.x: https://github.com/FOGProject/fos/commit/b56b8d9f6356f6e702e6ff580b2c4500f27ac41f#diff-15f9b0e5270fc1caac75f8b936c3df11534ceeb08de376b7a72b38c75ff2ad1aL1122

                      @Tom-Elliott Do you remember if this was added for a reason? Not saying this is an issue at all. Just wondering if we might think about removing it to further slim down the kernel binaries?

                      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                      T 1 Reply Last reply Mar 16, 2023, 11:14 AM Reply Quote 0
                      • T
                        Tom Elliott @Sebastian Roth
                        last edited by Mar 16, 2023, 11:14 AM

                        @Sebastian-Roth Those are network block devices. I don’t remember exactly why it was added, but it seemed a necessity.

                        I’ll try to re-review the why.

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        1 Reply Last reply Reply Quote 0
                        • A
                          AlexPDX @Tom Elliott
                          last edited by Mar 16, 2023, 11:36 AM

                          @Tom-Elliott said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

                          Ultimately, there’s not really a “problem” persay. Just that the inventory can’t pull the information from this NVME device?

                          That’s exactly what my problem is…i have over 300 host managed by FOG …i use a lot of snap-ins, imaging, and specially Hardware Inventory so i know exactly what that host has in order to deploy the MBR or UEFI image, without having to physically travel to that host…only in case of hardware change (RAM, SSD or the whole PC).
                          And there is also an “internal managing” issue …each PC has an bar code and we do the “handover report” , so, each PC has his own bar code, but some of them are slightly different one from each other, by RAM or SSD or NVME…and i need to know that 😐

                          1 Reply Last reply Reply Quote 0
                          • A
                            AlexPDX @Tom Elliott
                            last edited by Mar 16, 2023, 11:39 AM

                            @Tom-Elliott said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

                            hdparm -i /dev/nvme0n1

                            HDIO_GET_IDENTITY failed: Inappropriate ioctl for device

                            T 1 Reply Last reply Mar 16, 2023, 12:02 PM Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by Sebastian Roth Mar 16, 2023, 5:58 AM Mar 16, 2023, 11:55 AM

                              @AlexPDX said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

                              HDIO_GET_IDENTITY failed: Inappropriate ioctl for device

                              Yes, surely we need to use a different command to get that information, e.g. nvme id-ctrl /dev/nvme0n1 | grep mn or smartctl --info /dev/nvme0n1 | grep Model (https://sleeplessbeastie.eu/2022/03/21/how-to-display-information-about-nvme-storage-device/)

                              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                              A 1 Reply Last reply Mar 16, 2023, 12:04 PM Reply Quote 0
                              • T
                                Tom Elliott @AlexPDX
                                last edited by Tom Elliott Mar 16, 2023, 6:21 AM Mar 16, 2023, 12:02 PM

                                @AlexPDX said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

                                HDIO_GET_IDENTITY failed: Inappropriate ioctl for device

                                https://opensource.com/article/21/9/nvme-cli

                                May need to see if we have nvme-cli on the FOS systems.

                                Specifically you would use nvme list /dev/nvme0n1 and should provide details.

                                Trying to figure out what we’d need.

                                Maybe something like:

                                hdinfo=$(hdparm -i $hd 2>/dev/null || nvme id-ctrl $hd | awk  '/mn[ ]+:/ {split($0, model, ": "); modelno = model[2]} /sn[ ]+:/ {split($0, serial, ": "); serialno = serial[2]} /fr[ ]+:/ {split($0, firmware, ": "); fwrev = firmware[2]} END {gsub("^[[:space:]]+|[[:space:]]+$", "", modelno);gsub("^[[:space:]]+|[[:space:]]+$", "", fwrev);gsub("^[[:space:]]+|[[:space:]]+$","",serialno);print "model="modelno",fwrev="fwrev",serialno="serialno}')
                                

                                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                T 1 Reply Last reply Mar 16, 2023, 12:03 PM Reply Quote 0
                                • T
                                  Tom Elliott @Tom Elliott
                                  last edited by Mar 16, 2023, 12:03 PM

                                  @Tom-Elliott said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

                                  nvme list $hd | tail -1 | awk -F" {2,}" ‘{print “model=”$4",fwrev=“$8”,serialno="$NF}’

                                  @AlexPDX Can you try running the command:

                                  nvme list /dev/nvme0n1 | tail -1 | awk -F" {2,}" '{print "model="$4",fwrev="$8",serialno="$NF}'
                                  

                                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                  A 1 Reply Last reply Mar 16, 2023, 12:06 PM Reply Quote 0
                                  • A
                                    AlexPDX @Sebastian Roth
                                    last edited by Mar 16, 2023, 12:04 PM

                                    @Sebastian-Roth said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

                                    nvme id-ctrl /dev/nvme0n1 | grep mn

                                    This one worked 🙂
                                    [Thu Mar 16 root@fogclient /]# nvme id-ctrl /dev/nvme0n1 | grep mn
                                    mn : KINGSTON SNV2S250G
                                    mntmt : 273
                                    mnan : 0

                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      AlexPDX @Tom Elliott
                                      last edited by Mar 16, 2023, 12:06 PM

                                      @Tom-Elliott said in Host Hardware Inventory - Hard Disk Model - M.2 Nvme not identify:

                                      nvme list /dev/nvme0n1 | tail -1 | awk -F" {2,}" ‘{print “model=”$4",fwrev=“$8”,serialno="$NF}’

                                      this returned :
                                      model=1,fwrev=512,serialno=ELFK0S.4

                                      And :

                                      smartctl --info /dev/nvme0n1 | grep Model
                                      returned:
                                      Model Number: KINGSTON SNV2S250G

                                      T 1 Reply Last reply Mar 16, 2023, 12:20 PM Reply Quote 0
                                      • S
                                        Sebastian Roth Moderator
                                        last edited by Mar 16, 2023, 12:12 PM

                                        @AlexPDX @george1421 @Tom-Elliott Great we got this figured out. Please let us discuss the details on github: https://github.com/FOGProject/fos/issues/72

                                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          Tom Elliott @AlexPDX
                                          last edited by Mar 16, 2023, 12:20 PM

                                          @AlexPDX can you try:

                                          nvme id-ctrl /dev/nvme0n1 | awk  '/mn[ ]+:/ {split($0, model, ": "); modelno = model[2]} /sn[ ]+:/ {split($0, serial, ": "); serialno = serial[2]} /fr[ ]+:/ {split($0, firmware, ": "); fwrev = firmware[2]} END {gsub("^[[:space:]]+|[[:space:]]+$", "", modelno);gsub("^[[:space:]]+|[[:space:]]+$", "", fwrev);gsub("^[[:space:]]+|[[:space:]]+$","",serialno);print "modelno="modelno",fwrev="fwrev",serialno="serialno}'
                                          

                                          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                          A 1 Reply Last reply Mar 16, 2023, 12:24 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 1 / 2
                                          1 / 2
                                          • First post
                                            16/38
                                            Last post

                                          198

                                          Online

                                          12.2k

                                          Users

                                          17.4k

                                          Topics

                                          155.5k

                                          Posts
                                          Copyright © 2012-2024 FOG Project