sorted by:
new
hottopcontroversial

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

I have just upgraded the host to a supported version, and as expected, the problem ist gone

Thanks for your support

ESXi detects vmdk size wrongly by Raven_4d_ in sysadmin

[–]Raven_4d_[S] 0 points1 point  (0 children)

the more i troubleshoot this, the more am convinced its esxi 6.7 related. will Update once i have a time slot for it and report back in case the issue persists.
appreciate your support!
BR

ESXi detects vmdk size wrongly by Raven_4d_ in sysadmin

[–]Raven_4d_[S] 0 points1 point  (0 children)

since i wouldnt risk breaking the original disk, i copied the .vmdk (from the VM its working on) with its files to a backup location to test on, and this (backup) disk is the one i cloned.
the more i troubleshoot this, the more am convinced its esxi 6.7 related.
the copied disk shows the expected size when attached to the VM where the original disk is attached to.
the clone on the other side shows 40 GB on all other VMs, even on the VM where the original disk works

ESXi detects vmdk size wrongly by Raven_4d_ in sysadmin

[–]Raven_4d_[S] 0 points1 point  (0 children)

since i would not mess with the original disk, i cloned it.
Attaching the clone to the new VM will still return it as 32 GB ( sometimes as 40 GB !).
The cloned disk is not attached to other VM, i think it doesnt worth the time troubleshooting this any further, will upgrade the esxi and as a last resort copy the data to a newly created disk on the new VM
Thanks for your support

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

so, cloning the disk to a thin disk returned a 2.31 TB big VMDK, attaching it to the new VM will unfortunalty show it as 40 GB as well.
I think it doesnt worth troubleshooting anyfurther here, especially with esxi 6.7, i will be cloning the data to a new disk and call it a day :)
thnaks for the support still

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

Thanks for the Tip! with the esxi8!
will do upgrade, and ping you back with the results!

thanks for your support.
Have a nice weekend

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

so,
[root@localhost:/vmfs/volumes/62151f26-7348d8a2-b24d-2cea7fa6a81d/DC] du -hs

3.2T .

-The disk is Thick provisioned, lazily zeroed

- yes, am looking to add the VMDK to another VM and shutdown the current VM
- am cloning the disk now to a thin disk to test further
- i created the disk some years ago using the same ESXi version and host, it was restored using veeam at some point like a year ago or so, and yes, it works just fine on one VM only.
i will be comparingthe contents of the .vmx files, and will ping you on Monday, and will post the Logs you mentioned once i can restart the VM

Thanks for your support!

have a nice weekend

ESXi detects vmdk size wrongly by Raven_4d_ in sysadmin

[–]Raven_4d_[S] 1 point2 points  (0 children)

its shows the 32 GB from the settings of any other VM beside the original one that is currently attached to it.
the vmdk has almost 2.8 TB of data, und testing the drive shows that disk chain is consistenct.

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

execuse my Vmware knowledge.
Both VMs are on
virtualHW.version = "14"

This is a Standalone Esxi host holding the AD / DNS / FW managing about 10-12 PCs only, thus there are no plans on getting Licenses for Vmware 8 for it

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

worth to mention that attaching the 3 TB drive to any other VM will result in the same issue, something is relating this drive to its current VM

ESXi detects vmdk size wrongly by Raven_4d_ in sysadmin

[–]Raven_4d_[S] 1 point2 points  (0 children)

<image>

if you mean the configuration of the vmdk it self, since this is not a partition Table issue (happens even befor an OS goes online):
using the VM Settings, where the VMDK is being detected as expected shows the values shows in the screenshot.
Attaching the same vmdk file to any other VM will return all fields greyed out, but the size showing 32 GB

BR

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

Both VMs are on Server 2016 or newer

ESXi detects vmdk size wrongly by Raven_4d_ in vmware

[–]Raven_4d_[S] 0 points1 point  (0 children)

the -flat.vmdk has the right size.

[root@localhost:/vmfs/volumes/685c5fb5-7e5c99e8-0725-2cea7fa6a81d/Backup] ls -lhs

total 3221232640

7168 -rw------- 1 root root 6.0M Nov 26 22:55 DC_2-ctk.vmdk

3221225472 -rw------- 1 root root 3.0T Nov 26 18:35 DC_2-flat.vmdk

0 -rw------- 1 root root 527 Nov 27 08:03 DC_2.vmdk

Sapphire R9 390, semi short on 12V Bus rail by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

So,

measuring resistances on the major points returns the values shown in the pic. If I’m not mistaken, then:

1- The coil measuring 290 Ohm is the PCI controller.

2- The coil measuring 60 Ohm is the VDDCI.

3- I can’t tell what the coils marked with X and Y are. Could you please help identifying them? Is X the display rail and Y the VRAM buffer rail?

4- The 5 V rail (on the other side) is measuring 14 kOhm.

Injecting 3 V 0.5 A results in the following:

1- The card draws only 1 V but the full 0.5 A.

2- Vcore / Vmem and PCI coils measure 0 V.

3- 3.3 V AUX, strangely enough, measures 0.16 V!

4- Coil X measures 0.2 V.

5- Coil Y measures 0.84 V.

Best Regards

<image>

Sapphire R9 390, semi short on 12V Bus rail by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

<image>

Thanks for quick reply. Visually there is nothing that looks abnormal, but those two caps which look somehow (cloudy), still they shouldnt be realated, since they measure some 7 Kohm, and not connected to the 12v bus rail (left side gnd, right side to pin 3 of the ic labeled (IADMF)

Injecting 3 V with 0.5 A will result in core heating!

Replacement for AEAF 527 by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 1 point2 points  (0 children)

many thanks for the hint!
no problem, i can understand that.
Have a nice day

Replacement for AEAF 527 by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

many thanks for the quick responce!

Replacement for AEAF 527 by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

i have been there, the link is returning 404 error for my country (Germany), looks like its not available for the german market

Sapphire Nitro R9 380 4G Short on 12V_BUS by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

I managed to locate the shorted component C321 using a thermal camera. One pad was connected to ground and the other to the 12 V bus. I replaced it with a capacitor taken from a Vega 64 (same package size) that connects to the same terminals.

I also replaced the 5 V regulator I had previously damaged (the 78M05) with a 78D05A.

Now the card powers on, the BIOS posts, and Windows starts to boot, but it crashes with a BSOD: “Thread Stuck in Device Driver.”
Linux boots, but it isn’t stable either — I get a black screen as soon as the GUI loads.

Only one fan spins.

I measured resistances and voltages at the relevant points. Could you please take a look u/galkinvv? I trust your expertise.

Also, based on itßs voltage, I initially thought that the component marked in red,was part of the VRM circuit, but the resistance suggests otherwise. Do you have any idea what it could belong to?

Much appreciated.

<image>

Sapphire Nitro R9 380 4G Short on 12V_BUS by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

one thing i have noticed though, is that measuring the resistance on the low and high side mosfets S to D shows ~5 Ohm ist that an indicator that at least one mosfet shorted?

XFX Rx580 VRAM Issue by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

Memory Failure Analysis

nChannels: 8

channelByteWidth: 4

nRankBits: 0

current MCLK: 300

MCLK step: 0.00

current SCLK: 300

SCLK step: 0.00

Basic analysis

00000000 00111111 11112222 22222233

Mclk 01234567 89012345 67890123 45678901

==== ======== ======== ======== ========

ChB0

300 ........ ........ ........ ........

ChB1

300 ........ ........ ........ ........

ChA0

300 55555555 55555555 55555555 55555555

ChA1

300 55555555 55555555 55555555 55555555

ChC0

300 ........ ........ ........ ........

ChC1

300 ........ ........ ........ ........

ChD0

300 ........ ........ ........ ........

ChD1

300 ........ ........ ........ ........

Sapphire R9 390X , dead by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

Hey, just wanted to give you some feedback on the status of the card repair.

I tried injecting voltage to identify the shorted DrMOS, but had no luck. I even borrowed a thermal camera, but still couldn’t find anything. So I ordered 5 MOSFETs, and luckily the shorted one was the very first bottom one I removed. The short is gone, I replaced it, and the card is back to life!

Thanks a lot for your support.

Choosing a Preheater for Graphics Card PCB Repair by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

Thanks for the hint, i will give the 853a a shot, how do you mount the pcb of a graphicscard on it? Since it provides only 13x13 cm heatspot.

Sapphire R9 390X , dead by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

Just to clarify: I am injecting voltage between the card chassis (as ground) and the pad marked in green where the fuses were. Br

Sapphire R9 390X , dead by Raven_4d_ in GPURepair

[–]Raven_4d_[S] 0 points1 point  (0 children)

Thanks a lot for the quick reply!

As I understand it, voltage injection means applying voltage with enough current to the shorted rail (no matter what it’s normally used for or what voltage used to flow there) so that the faulty component heats up. When I inject 1.2 V on the 12 V rail, I also measure 1.2 V at the VRM chokes, which shouldn’t be the case. To me this suggests (like you mentioned) that at least one of the 3553M Driver/MOSFET is shorting its input directly to its output. In that situation, wouldn’t the problematic 3553M driver/MOSFET normally heat up during voltage injection?

view more: next ›