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

    fog issues with nvme drives

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    1
    1
    128
    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.
    • O
      okafor-abc
      last edited by

      Hello,

      We have many systems with a similar configuration (1TB nvme system drive and 2TB nvme data drive). When capturing and deploying images, we are having the issue where sometimes the image is deployed onto the 1TB (as intended) other times the image is deployed onto the 2TB data drive. I’ve tried Single Disk - Resizable images and Multiple Partition Image - All Disks (Not Resizable) images. I’ve also tried specifying /dev/nvme0n1 in the Host Primary Disk but this does not resolve the issue. I read that the reason why this happens is because linux enumerates nvme drives differently from sda/sdb drives (my understanding was that linux would randomly select which drive will be nvme0n1 on boot); I confirmed this by booting into the fog menu checking the drive, rebooting and verifying that the first time /dev/nvme0n1 was the 1TB drive and the second time /dev/nvme0n1 was the 2TB drive. Is there any way we could reliably target the drive such that upon capture, /dev/nvme0n1 is the 1TB and upon deployment /dev/nvme0n1 is also recognized as the 1TB drive? Thank you very much in advance.

      1 Reply Last reply Reply Quote 0
      • 1 / 1
      • First post
        Last post

      174

      Online

      12.0k

      Users

      17.3k

      Topics

      155.2k

      Posts
      Copyright © 2012-2024 FOG Project