• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. NIoSaT
    3. Posts
    N
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 3
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by NIoSaT

    • RE: Swap UUID does not match after deploy

      @Sebastian-Roth
      I just did the debug deploy.

      On the target system all partitions are called /dev/sdaX.

      The manual mkswap with the old uuid and the /dev/nvmeXXXX device name gave an error (device not found).

      I then tried mkswap with the old uuid and with the /dev/sdaX device name and it worked!
      Debian now boots correctly and finds the swap!

      I will now try your fix and edit the d1.original.swapuuids to match the /dev/sdaX name to test if the deploy will work automatically again.

      It is still strange to me that the two systems use different names for the devices, since both use nvme drives.

      But I guess this problem will solve itself once I use 100% identical hardware.

      — UPDATE —
      I updated the d1.original.swapuuids, it works!

      posted in FOG Problems
      N
      NIoSaT
    • RE: Swap UUID does not match after deploy

      Thanks for the quick answer!

      Yes I am capturing from and deploying to an NVMe drive.

      The content of the d1.original.swapuuids is as follows

      /dev/nvme0n1p6 ed7ca9e8-1c85-4321-9e59-9e5b1414a8fc
      

      One thing I also noticed is that the original system that I capture from uses paths like /dev/nvmeXXXX when I look at the comments in /etc/fstab.
      But the system I deploy to shows paths like /dev/sdaX when using lsblk.
      I think I saw the same differences in the naming scheme during the imaging/writing process of Partclone.
      Both systems have NVMe drives but are not 100% identical hardware (two different Version of the Dell OptiPlex platform). I will get 100% identical systems soon (this is were the real deployment will happen).

      I will do the debug deploy and see if the manual mkswap will work.

      posted in FOG Problems
      N
      NIoSaT
    • Swap UUID does not match after deploy

      Hello,
      I am currently trying to capture and deploy a Dual-Boot System (Debian 9 + Win10), but I am having trouble with some UUIDs.

      I am using FOG Version 1.5.7
      Dell Optiplex 3060
      GPT partitioning

      Capture and deploy generally work, and I can even boot the Debian System. But the swap partition does not work correctly.
      I narrowed it down to a missing UUID.
      All other Partitions get a correct UUID, Lable and PARTUUID that match the /etc/fstab. The Swap Partition only gets a PARTUUID (even the same as the original system, so that works) but nothing else. So Debian can’t find the partition while booting.

      I already tried “Single Disk - resizable” and “Multiple Partition Image - Single Disk (not resizable)” as Image Type, both with the same problem.

      When I check the d1.original.swapuuids in the image on the Fog server, there is the correct UUID but it does not get written during the deploy.

      I did some research and as far as I understand this should work in 1.5.7?

      posted in FOG Problems uuid dual boot swap
      N
      NIoSaT
    • 1 / 1