FOG won't deploy properly.
-
@VlanFlex said in FOG won't deploy properly.:
/dev/sdb
Just be aware that nvme disks are labeled differently. /dev/sdX is for sata disks.
-
@george1421 I have updated to kernel version 5.16.18 and ran the command that you asked
I keep getting an error when I try to upload an picture here, so here is a link.
Apologies for it being sidewaysAlso turns out that the Samsung SSD is actually a KINGSTON 480GB SSD.
-
@VlanFlex So it looks like you have 2 sata disks installed. Do you know based on the size which one you want to deploy to?
-
@george1421 @Sebastian-Roth Also pointed out that /dev/sdb is SATA annotation. This is quite confusing to me since I can physically see the SATA SSD and M.2 here.
Any idea why it would show up as an SATA device?
As to awnser your question, I would like the operating system to be installed on the ‘‘m.2’’, which is 256 GB.
-
@VlanFlex Ok you are currently sitting (at the target computer) at the FOS Linux command prompt? If so lets go ahead and try to image this computer. Have a mobile phone handy to see if we can catch the actual error. I might expect something to be displayed on the blue partclone screen. So to start imaging in debug mode key in
fogand press enter. You will need to press enter at each breakpoint to continue on to the next step. These breakpoints hopefully will give you a chance to catch any errors.I can see (in my mind) that FOG is working as intended, but the system will not boot because you are deploying to the second drive, and your windows 8 image is actually on your 450GB drive. That 480 GB drive is listed as /dev/sda (first disk found) and then the disk you are deploying to is /deb/sdb (second disk found). The problem may be the uefi boot manager is still pointing to the 450GB drive.
-
@george1421 I have started a deployment proces in debug mode. Here are the photo’s.
1 - https://ibb.co/pRTFXct
2 - https://ibb.co/f4K593S
3 - https://ibb.co/z7qgBVd
4 - https://ibb.co/sqJBzzBAfter this proces I booted from harddisk via the FOG menu and get booted straight into reFIND. There are still two Windows boot loader options in the boot menu, but none work.
If I try to add a UEFI boot option I get file system not found.
EDIT: if necessary I can also make a video of the whole imaging process, but thats gonna take me some time.
-
@VlanFlex Ok so if you go through the windows boot manager can you still boot into the windows 8? If so lets check the content of that 250GB drive. Does it appear to be a windows 10 disk?
-
@george1421 I cannot boot into Windows 8 anymore. All I get is the reFIND screen.
To verify the contents of the two drives I’ve launched live ubuntu via USB on the target PC.
There are two drives present, both called D with the same contents.
-
@VlanFlex Ok what I’m speculating is that FOG IS working as its being instructed. It is deploying the image to what it sees as /dev/sdb. Ubuntu also see the 250GB as /dev/sdb. I think what is missing is the uefi firmware doesn’t either see the disk as bootable or the legacy windows 8 menu entry points to a location that doesn’t exist any more. I’m trying to isolate is it fog doing something wrong, or what you are asking FOG to do is causing it to fail.
If you look at that /dev/sdb with a utility like gparted does it appear to be an intact uefi disk? If your disk structure is MBR that brings in a new issue since the 250 GB disk is being reported as the second hard drive.
-
@VlanFlex said in FOG won't deploy properly.:
https://ibb.co/D1wd4cs
Any idea why it would show up as an SATA device?Can’t see enough information on the picture as it’s not clear enough. M.2 does not mean the disk is NVMe in general! So I can imagine this to be a M.2 SSD drive showing up as sdX in Linux. You can run
hdparm -i /dev/sdX(put inaandbinstead of theX) to get some more information about the disk drives.
