Deploy problem with Optiplex 3020
-
@Pascal-Gazaille also, partition type is
PowerPC… that’s strange too.Can you try to do fog’s “Normal Wipe” task on one of the disks and then try to image it?
-
@Wayne-Workman Do you know how long it’s supposed to take for the normal wipe, I started it as soon as you asked me and it’s still not finish…
-
@Pascal-Gazaille Wayne is right, the
PowerPC PReP bootpartition type seems strange. But that’s just an ID. Fog actually checks the filesystem type on the partitions. So can you please runblkid -o udev /dev/sda1 | grep FS_TYPEandblkid -o udev /dev/sda2 | grep FS_TYPEand let us know while filesystem you actually have on those partitions…PS: Hope you don’t mind me editing your post to remove the /dev/ramX entries which are not helpful here.
-
@Pascal-Gazaille it takes a while… In the mean time, please hook up another one of those and run the commands that Sebastian requested.
-
-
@Wayne-Workman Tried the normal wipe and reimagine the computer, same result
-
@Pascal-Gazaille said:
Just dit and everything is Ok, seems to be the hdd in the new ones that have the problem
ST500DM002-1SB10A - Black screen after fog
ST500DM002-1BD142 - Works fineRe-reading this thread I stumbled upon this. Maybe it’s the disk size? 500GB on one disk is not always the same as 500GB for another. Please compare the output of
fdisk -l /dev/sdafor the two different disks. Pay attention to the byte and sector counts:Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectorsDo those match exactly?
The other things I thought about is the different ATA modes in BIOS. Make sure you have the same settings (was it called AHCI… I am not exactly sure right now) in the old and new PCs.
-
@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
