No announcement yet.

bit linux doesn't detect raw nvme drive

  • Filter
  • Time
  • Show
Clear All
new posts

  • bit linux doesn't detect raw nvme drive

    I've a system w/ several nvme drives installed, and no partition on the drives, and bit is configured to test all raw disks in cmdline_config.txt:

    ##TestAllRAWDisks - Test all detected RAW disks, uncomment to use

    But latest bit linux v3.1 (1002) didn't detect these nvme drives at all, any idea how to workaround this issue?
    Host OS is EL7.1, and nvme drives can be detected by "fdisk -l"

    Thanks in advance!


  • #2
    BurnInTest Linux checks /etc/fstab to determine what kind of media types your system have and where it could be mounted.

    Could you please email us the full debug log or the contents from /etc/fstab (contact details on this page).


    • #3
      I intended to test raw disks, so there's no partitions on the disks, and here's /etc/fstab content:

      [root@nsgsh-dhcp-93-172 ~]# cat /etc/fstab

      # /etc/fstab
      # Created by anaconda on Wed Apr 1 16:39:02 2015
      # Accessible filesystems, by reference, are maintained under '/dev/disk'
      # See man pages fstab(5), findfs(, mount( and/or blkid( for more info
      /dev/mapper/ol_nsgsh--dhcp--93--172-root / xfs defaults 0 0
      UUID=225f1e85-8844-4d4d-a39d-1b3f6e4e9949 /boot xfs defaults 0 0
      /dev/mapper/ol_nsgsh--dhcp--93--172-swap swap swap defaults 0 0

      BTW, lsscsi can't detect these NVME drives as well, since these drives are relatively new staff
      but fdisk can list it:
      [root@nsgsh-dhcp-93-172 bitcmd]# fdisk -l /dev/nvme1n1

      Disk /dev/nvme1n1: 1600.3 GB, 1600321314816 bytes, 3125627568 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk label type: dos
      Disk identifier: 0x000618c0

      Device Boot Start End Blocks Id System


      • #4
        Currently BurnInTest Linux won't detect these sort of drives, we'll need to make some changes when parsing the available devices to correctly identify them as testable disks.

        If you could please start BurnInTest in debug mode (using the command line parameter -d) and then send us the debug log that would great.


        • #5
          Has this been address? I am having the same issue.


          • #6
            NVMe support was added in V3 of BurnInTest, are you using the latest build of BurnInTest (4.0 build 1004)?

            If you are still having problems in V4 please send us a debug log after launching BurnInTest and trying to start the disk test.