Deploy problem with Optiplex 3020
-
@Sebastian-Roth both of the disk have the same information except for the disk identifier.
In the bios we keep the disk settings to AHCIHere is the new disk :
Here is the old one :
-
Have you tried non-resizable image type as you seem to have target and destination disk with the same size!?! Resizable and non-resizable images take about the same amount of disk space on the server so I don’t see any need to use resizable in your case - possibly I am wrong as I don’t know your whole setup.
-
@Pascal-Gazaille Can you take the bad drive out and just take pictures of all the labels on it? The pictures need to be close-up enough and focused enough for us to read everything on the label (without any big glares from flash or lighting, also).
It’ll allow us to do additional thinking/searching and see if we can find something.
-
@Sebastian-Roth Can I change the image type without reuploading the image?
All my images are single disk -resizable. -
@Pascal-Gazaille No. After changing the image type you have to re-upload. Sorry.
-
-
@Pascal-Gazaille @Sebastian-Roth
It’s got a firmware version,
CC43! I Wonder if it can be updated?!? -
@Wayne-Workman I’ve searched everywhere but did not find any firmware update or downgrade…
-
@Pascal-Gazaille Lets wait and see what Sebastian says. He’s a pro with HDDs.
-
@Wayne-Workman Tried imaging the hdd with a multiple partition image - all disk (not resizable) we use for our laptops and it’s working…
-
@Pascal-Gazaille huh… well, then this is a fog issue for sure! Notifying @Tom-Elliott and @Sebastian-Roth
Also to be sure, please re-upload the image you want as non-resizable and try it!
-
@Pascal-Gazaille said in Deploy problem with Optiplex 3020:
@Wayne-Workman Tried imaging the hdd with a multiple partition image - all disk (not resizable) we use for our laptops and it’s working…
For clarification, did the non-re sizable image deploy to the troublesome HDD?
-
@Wayne-Workman We already had an image with multiple partition image - all disk (not resizable) in our fog and yes this image has worked on the new HDD
-
@Pascal-Gazaille Thanks a lot for all the information and testing you did so far. I need to sit down and read through the whole thread again when I have a bit more time over the weekend.
Seeing the title of the post I am wondering if this has turned out a completely different issue, right? It’s the disk, right? Do you see the exact same issue if you put this “problem HDD” into a different computer? As well are you able to successfully deploy to a “good HDD” in the Optiplex 3020? You see I am trying to circle the issue…
-
Bumping this
-
@Pascal-Gazaille Ok here is what I ran into re-reading it all and trying things out a bit:
- In one of your ealier posts it says
Disklabel type: gptandPowerPC PReP bootwhile we seeDisklabel type: dosandHPFS/NTFS/exFAT. While I don’t say this is a problem I am still wondering when and how this got changed along the way. The two partition schemes are quite different from each other and will cause different behavior in FOG as well. - I guess we need the image information as well to get an idea if and where things go wrong. Please post the output of
ls -al /images/<image-name>,cat /images/<image-name>/d1.fixed_size_partitions,cat /images/<image-name>/d1.minimum.partitionsandcat /images/<image-name>/d1.partitionshere in the forum!
- In one of your ealier posts it says
-
@Sebastian-Roth Hi, I’ trying your commands and none of them works…I’m I missing something? I started the computer in “deploy - debug” like all other debug.
-
@Pascal-Gazaille Sorry, should have said that those commands I meant you to run on the FOG server! Note that you need to replace the
<image-name>part with your actual image name! -
cat /images/<image-name>/d1.fixed_size_partitions= 1
cat /images/<image-name>/d1.minimum.partitions= not working
cat /images/<image-name>/d1.partitions= not working -
@Pascal-Gazaille Well then please run
cat /images/TNI64/d1.original.fstypesandcat /images/TNI64/d1.original.partitions
