Windows 11 | 65x HP Z2 Tower G1i | UPDATE -
-
=== Festplatten-Report fuer PC117CAD ===
— Festplatte —
Modell : PSEMN01TA87NC0
Seriennummer : 0000_0000_0000_0000_6479_A7B4_1F00_1204.
Groesse (GB) : 931,51
Medientyp : Fixed hard disk media
Interface : SCSI
Partitions : 2
— Partition —
Name : Datenträgernr. 0, Partitionsnr. 0
Typ : GPT: System
Bootable : True
Groesse (GB) : 0,10
— Partition —
Name : Datenträgernr. 0, Partitionsnr. 1
Typ : GPT: Basic Data
Bootable : False
Groesse (GB) : 931,40
— Logisches Laufwerk —
Laufwerksbuchstabe :
Volumename :
Dateisystem : NTFS
Groesse (GB) : 931,40
Frei (GB) : 844,18— Festplatte —
Modell : WD Green SN350 250GB 2G0C
Seriennummer : E823_8FA6_BF53_0001_001B_448B_4FDE_90F3.
Groesse (GB) : 232,88
Medientyp : Fixed hard disk media
Interface : SCSI
Partitions : 1
— Partition —
Name : Datenträgernr. 1, Partitionsnr. 0
Typ : GPT: Basic Data
Bootable : False
Groesse (GB) : 232,87
– Logisches Laufwerk –
Laufwerksbuchstabe :
Volumename : Daten
Dateisystem : NTFS
Groesse (GB) : 232,87
Frei (GB) : 232,77=== Ende des Reports ===
-
Please check memory of computer with memtest86+ 8.0
-
@sgennadi
I don’t have any hardware issues anymore—now I just need to make sure the cloning process is happening on the right NVMe drive. One NVMe drive contains the students’ data, and the other contains the operating system. If I can’t get this to work, I’ll have to swap out the Fog for some Microsoft stuff
-
@kratkale Like I said, if you know which nvme drive has the student data, and which is expected to be the OS:
On a registered host you can explicitly call out which drive using “serial, wwn” or otherwise.
You type in the wwn or serial number:
lsblk -pdno PATH,SERIAL,WWN,SIZE --nvmerespective of your device. (I lowercase them for simplicity.)Find your “primary” drive, and put in either one of those details in the form field and give it a shot. It should work and will leave the other drive completely alone so long as the type of image you’re using is “single disk” style.
-
is this now correct?
-
@kratkale That seems correct to me, yes. If this is a drive you’re testing proof of, I’d first just replace the actual second disk with something you don’t care to lose to test.
What I don’t want is you to just trust me at my word for the sake of things and lose actual data.
Another method you can use in case this isn’t sufficient, it’s a little more involved I suppose is to simply unplug the disk you don’t want being written, but that’s a part of the problem. At a glance you of the hardware you have no idea what drive is which. That’s the basic problem you’re running into now:
nvme0n1 this time might be the right disk, but next boot nvme0n1 might be the student disk. It’s all dependent on who starts up and responds first.
-
@kratkale Here’s a big problem: updating a group overrode the “Host Primary Disk” entry on all the PCs in the group—I had already entered the information for all 65 PCs. But I had backed up the host table beforehand—can I just restore it?
It would be necessary to be able to block host entries! -
@kratkale
Okay—I have another theory about the problem: after analyzing the NVMe serial numbers, I found the following number ranges: 0525476001xxx and BMEAN00061090Axxx—where x can be a hexadecimal number and varies. The PC’s with NVMe drives from the 05… range have trouble recognizing the first NVMe drive. Those with BM… did not have this problem. The serial numbers of the data disks are all 260227800xxx and are all one digit shorter than the numbers of the system disks.When cloning with Clonzilla, I didn’t have a problem with any system (65 PCs); all hard drives were correctly recognized in the order they are installed in the PC.
Could it be that cloning with FOG always clones to the smaller serial number? … and when cloning, it also says that it’s cloning to nvme1, which is correct.
-
@kratkale I didn’t know you were updating the serial of a group of devices, you should not do that. Groups are just mass updating hosts with the information you provide for the Host base settings (snapins, primary drive, kernel, etc…).
-
@kratkale I don’t know what you are asking.
what’s nvme1n1 this boot cycle, might very well be nvme0n1 next cycle.
While you may see some level on consistency, SERIAL based devices (PCI, SATA, USB, etc…)
All load their identifiers (/dev/sda, /dev/nvme0n1, etc…) on a first come first serve basis.
What’s /dev/sda1 this boot may be /dev/sdb1 next boot and so on. There’s 0 method to guarantee they will always get the same label which is why many Linux machines use a UUID for the fstab file now instead of their path names (which was used for a long period of time).
FOG just returns the list of devices lsblk sees in the order lsblk sees it.
