Deploy problem with Optiplex 3020

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

[Sebastian Roth]

@Pascal-Gazaille Wayne is right, the PowerPC PReP boot partition type seems strange. But that’s just an ID. Fog actually checks the filesystem type on the partitions. So can you please run blkid -o udev /dev/sda1 | grep FS_TYPE and blkid -o udev /dev/sda2 | grep FS_TYPE and 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.

[Wayne Workman]

@Pascal-Gazaille it takes a while… In the mean time, please hook up another one of those and run the commands that Sebastian requested.

[Pascal Gazaille]

@Sebastian-Roth

ID_FS_TYPE=ntfs

That’s the result for both you asked

[Pascal Gazaille]

@Wayne-Workman Tried the normal wipe and reimagine the computer, same result

[Sebastian Roth]

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

Re-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/sda for the two different disks. Pay attention to the byte and sector counts:

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors

Do 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.

[Pascal Gazaille]

@Sebastian-Roth both of the disk have the same information except for the disk identifier.
In the bios we keep the disk settings to AHCI

Here is the new disk :

Here is the old one :

[Sebastian Roth]

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.

[Wayne Workman]

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

[Pascal Gazaille]

@Sebastian-Roth Can I change the image type without reuploading the image?
All my images are single disk -resizable.

[Wayne Workman]

@Pascal-Gazaille No. After changing the image type you have to re-upload. Sorry.

[Pascal Gazaille]

@Wayne-Workman

[Wayne Workman]

@Pascal-Gazaille @Sebastian-Roth

It’s got a firmware version, CC43! I Wonder if it can be updated?!?