Posts made by Sebastian Roth

@Rizingknight72 Make sure you have fast boot disabled in Windows and so a clean shutdown before you start capturing.

@herman said in Very slow cloning speed on specific model:

Link down of Drive Google…!!!

Well, this link is more than two years old and was probably meant as a temporary one…

What exactly so you hope to get from an old init.xz? I suggest you open a fresh new topic here in the forums and describe the exact issue you have, mention the FOG version and OS version used.

@DBCountMan I suggest to verify the checksum (sha256 file on github). If the checksum is wrong, then re-download init.xz. But if it’s right then try another init.xz version, e.g. https://github.com/FOGProject/fos/releases/download/1.5.10/init.xz

@DBCountMan Which init.xz exactly did you download? There are several ones online.

Do you have the old one still available to put in place and see if you can get things back to working with this?

@Lementchow Sorry for the very long delay. I had very little time in the last months and I knew this one needed a bit of time for a good research.

Trying to find out more about this SSD I searched for “3C07140238” as well as “nvme s990 512” and found this is being sold on ebay as “Lite-On S990 512GB M.2 2230 SSD NVMe PCIe”.

There are some interesting details on this in a tech forum: https://forums.anandtech.com/threads/making-use-of-an-old-hp-laptop.2604210/

There is also rumor on the S990 SSDs making trouble in SteamDecks:
https://www.reddit.com/r/SteamDeck/comments/yyh8zd/nvme_drive_doesnt_found_on_steam_os/
https://www.reddit.com/r/SteamDeck/comments/y4goh4/psa_some_ssd_may_not_supported_by_steamos/

Now talking about Linux drivers I checked the PCI ID 1e95:9100 (picture below) and found that we should have the driver included in our kernel:
https://linux-hardware.org/index.php?id=pci:1e95-9100-126f-2263
https://github.com/FOGProject/fos/blob/master/configs/kernelx64.config#L1123

You might want to use some of these commands to see if the Linux nvme commands can give you some information on this drive: https://wiki.archlinux.org/title/Solid_state_drive/NVMe

PS: If you are very keen you might want to send an email to the kernel driver author and ask him about how to dig why this SSD is not working: https://github.com/torvalds/linux/blob/master/drivers/nvme/host/pci.c#L3527

@DBCountMan When you re-run the installer the iPXE buildscript is called and should use /opt/fog/snapins/ssl/CA/.fogCA.pem to embed into the compiled binary (code ref). That file is being copied to /var/www/fog/management/other/ca.cert.pem by the installer but only on the very first install run or if you force it to - don’t do that without knowing exactly what you do and having backup copies of all the files!! (code ref).

I suggest you compare the fingerprints of those two files - should be identical:

openssl x509 -in /opt/fog/snapins/ssl/CA/.fogCA.pem -noout -fingerprint
openssl x509 -in /var/www/fog/management/other/ca.cert.pem -noout -fingerprint

@Allen @Nestor2022 Which version of FOG do you use?

FOG does not officially support MINT. We have tested this in the past a couple of times but I can imagine it having a problem right now.

@mardonis200 Whoops, was too quick to mark it solved. Would you please re-phrase the topic to reflect this as well.

I remember there was a topic in the forums on a similar issue. Just can’t find it right now. Try the forum search or your search engine of choice (e.g. using site:forums.fogproject.org as well).

@OutlastTrace said in FOG with TrueNAS on Proxmox Setup:

I’ve tried NFS and had errors when I go to take an image, I don’t remember them exactly but it was on the lines of having trouble mounting NFS. Would using virtual iSCSI work?

As FOS (our custom build FOG Linux OS doing all the heavy lifting for you) is using NFS mounting as well this would be like re-exporting a mounted NFS share. NFS does not support this by definition. You can give iSCSI a try, no promise it will work and give you good performance though.

@asawtell @george1421 Great to see you have been working on this while I was absent. So far to me it looks like a specific issue on this hardware with the Linux kernel.

Would be great if you can boot some kind of live Linux OS, or maybe just an installer ISO will do as well.

The other option is adding additional print output statements to the kernel source code and compile a custom kernel to boot and see exactly where it hangs. I can guide you on this if you are keen to give it a go, let me know.

Also you might see if there is an UEFI firmware update available (not sure if you talked about this already).

@Lementchow Thanks for the picture. Will take a look next week.

@Lementchow What NVMe drive is installed in this machine? Please post brand and model for us to check.

@Tim-Reynolds Thanks for the update and great you got this fixed.

@Evelyn09 said:

Can I use Linux device file name, disk size, and disk serial number?

Yes to all three if you use FOG 1.5.10.

@irwan First off, why do you double post within three hours? Was this by accident or intended? There is no need to do this. This is a community based forum for the open source tool FOGProject and people try to help each other in their free time. This is not any kind of professional support.

I will close down this topic now and we’ll be discussing things in the other topic: https://forums.fogproject.org/topic/16923/partition-tables-gpt-problems

@irwan We need more information to be able to help you. Please provide the contents of the text files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions. As well we need to know the disk size of the source disk and the destination disk.

@Tim-Reynolds On first sight this looks a lot like a PHP 8 issue. Are you absolutely sure you installed FOG 1.5.10? Not 1.5.9?

@Numa09 Nice find, well done!

@smtadmin67 You say you have a WDS server. Do you still use FOG? Having two PXE booting servers will surely cause trouble.

@Numa09 Unfortunately there aren’t any logs for the NFS mount part of FOG. But it’s surely a network filtering issue I guess as other network traffic is going through no problem. The whole PXE bootup uses several different protocols and they all seem to work fine up to that point where NFS comes into play. So you might want to search the web for NFS and your switch model.

Other than that you could search this forum for an extensive post by @george1421 about using NFSv4 on a single port which is more network friendly. Be aware this is bleeding edge testing and not officially supported.