Deploy problem with Optiplex 3020
-
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?
-
@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. -
@Pascal-Gazaille Can you try to image one you already had and see if it works?
-
@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 -
@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.
-
@george1421
fixparts /dev/sdaHowever, this only affects uploads.
I think something else is going on.
-
@Wayne-Workman said in Deploy problem with Optiplex 3020:
@george1421
fixparts /dev/sdaYep 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.
-
Could even be a firmware issue. Check the vendor’s website.
-
@Pascal-Gazaille Is your image re-sizable?
-
@Wayne-Workman Yes, my image is single disk - resizable
-
@sudburr I’ve check on every website for firmware update, nothing…
-
@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.
-
@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 -
@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.
-
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 /mediaDisk /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) -
Houston, we have an
sdb.Either you have external media connected, or this is a hybrid drive.
-
@Wayne-Workman I had a usb key to copy all the text you asked me
-
@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.