Deploy problem with Optiplex 3020

[Pascal Gazaille]

Hi all,
Everything was working well lately, but we have juste received a new batch of computer model Dell Optiplex 3020. We were able to deploy fog image on them before but not anymore.

We are on fog svn 7386, I’ve update the kernel to the latest 4.5.1.

The computer is able to do a full registration with no problem. After that I do a quick image and still everything is ok. The process does all what it’s supposed to do, by that I mean download and at the first restart I see a black screen and nothing else.

Tried other image (That work on other computers) and still have a black screen with nothing else.

[Wayne Workman]

Just to clarify, a fog update did not break this, but the new computers you just received simply cannot be imaged?

Have you checked firmware settings? Specifically bios/uefi and network operation modes, and HDD operation modes?

[Pascal Gazaille]

@Wayne-Workman I did update to the latest svn version, but dont think it’s the problem…
Maybe there’s something different in the optiplex 3020 we received lately compare to the other one’s we had.
On every DELL we have we disable secure boot and put it in legacy mode to boot on hdd.

[Wayne Workman]

@Pascal-Gazaille Can you try to image one you already had and see if it works?

[Pascal Gazaille]

@Wayne-Workman 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 fine

[george1421]

@Pascal-Gazaille I highly doubt (but still possible) that the hard drive model itself is the root cause here especially if FOG can successfully send the image to it. I might suspect some previous disk structure might be remaining that is causing the boot to fail.

Just to be clear, you took a hard drive from one of the older 3020s and put it into a new 3020 and it imaged OK?

Somewhere I saw that booting into a debug deployment you could run a command to wipe the disk that would clear any gpt structures that were remaining on the disk. I’m having a problem finding the command that Sebastian posted.

[Wayne Workman]

@george1421 fixparts /dev/sda

However, this only affects uploads.

I think something else is going on.

[george1421]

@Wayne-Workman said in Deploy problem with Optiplex 3020:

@george1421 fixparts /dev/sda

Yep that’s it.

I just find it hard to believe a simple model change would cause a deploy error… Unless the image was captured as a single disk non-resizable and the new disk model has at least 1 less sector than the old disk. The major disk part number didn’t change [ST500DM002] so the drive should be pretty much the same.

[sudburr]

Could even be a firmware issue. Check the vendor’s website.

[Wayne Workman]

@Pascal-Gazaille Is your image re-sizable?

[Pascal Gazaille]

@Wayne-Workman Yes, my image is single disk - resizable

[Pascal Gazaille]

@sudburr I’ve check on every website for firmware update, nothing…

[Pascal Gazaille]

@george1421 We’ve install win7 from scratch and it works, but when trying to image after the download the screen stays black or writes drive not found.

When we plug the hdd in another computer, we see the hdd with all the partition but it takes no letter.

[Wayne Workman]

@Pascal-Gazaille Ok then… we need to dig in. Please schedule a debug upload task on a host with this problematic HDD. Then once the computer network boots, and you get to a shell prompt, issue these commands and give us all the output.

fdisk -l | less
lsblk

[george1421]

@Pascal-Gazaille said in Deploy problem with Optiplex 3020:

@sudburr I’ve check on every website for firmware update, nothing…

Disk firmware too? I’m not suspecting this is the issue, but I have seen vendors release sata disk specific firmware from time to time.

[Pascal Gazaille]

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465.8G  0 disk 
|-sda1   8:1    0   100M  0 part 
`-sda2   8:2    0 465.7G  0 part 
sdb      8:16   1  14.4G  0 disk 
`-sdb1   8:17   1  14.4G  0 part /media

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5D0B0767-C0CA-4598-A861-390C27BA83FE

Device      Start       End   Sectors   Size Type
/dev/sda1    2048    206847    204800   100M PowerPC PReP boot
/dev/sda2  206848 976771071 976564224 465.7G PowerPC PReP boot


Disk /dev/sdb: 14.4 GiB, 15502147584 bytes, 30277632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x911e8a3c

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1  *     8064 30277631 30269568 14.4G  c W95 FAT32 (LBA)

[Wayne Workman]

@Pascal-Gazaille

Houston, we have an sdb.

Either you have external media connected, or this is a hybrid drive.

[Pascal Gazaille]

@Wayne-Workman I had a usb key to copy all the text you asked me

[Wayne Workman]

@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?

[Pascal Gazaille]

@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…