Recent content by jaysol

it may be the final piece of puzzle is to use DISKPART to verify partiton is active. diskpart select disk 0 select parition 1 active exit I just did this, and it WORKED --- but, curiously, the partition was already *ACTIVE. So who knows. It's a win. I'll take it.

Nope.... I'm wrong. I was unable to reproduce this "success". Not sure what the combination was to get it to work, but it happened after I ran fix_hdc. first I ran fix hdc as ide presented by the vm - - tried and BSOD then I ran fix hdc as sata presented by the vm - tried and it worked...

my VM id is 101.... so I did this: qm set 101 --delete ide0 qm set 101 --delete scsi0 qm set 101 --sata0 zfast-mfgdisk:vm-101-disk-0 qm set 101 --boot order=sata0 then boot into hirens, run fix hdc, it used iastor6.sys drivers, and worked. :)

WOW! Finally got it!.... So I switched my proxmox drive back to SATA MODE. Then I ran hirens (15.x) fix HDC again --- it recognized my new virtual controller. So it copied over iastor6.sys .... And finally booted!

Can add: tried hirens fix_hdc = BSOD 7B stop error (hirens found IDE controller and copied pciide.sys)

Hello, I think I've tried everything at this point. Unable to successfully P2V a Windows Server 2003. The phsyical server is: - Dell R210 - Dell AHCPI with C: drive running in AHCI auto - C: drive is partitioned as "basic" (not dynamic) - C: drive has no underlying software/hardware raid...

Great! I We are using the backup tool (vzdump files) but have only tried to recover to the the same/existing VM. Good to know it has what is needed within. I'll try to restore one of these to a different PVE server to see what it looks like. Thanks!

Assumming these hypothetical circumstances: - Standalone PVE server (no HA/cluster) - rpool crashed, server won't boot, PVE can't launch. - Must build new standalone PVE from scratch - Have recent full backups of each VM hosted on the failed PVE I assuming one will be missing (and requiring)...

So for anyone that finds this later on.... CHELSIO T420-CR (and I assume entire T4, T5, T6 series associated w/this driver set) seems to work OOB with PVE 6.x Once I assigned the NIC to a new vmbr# in proxmox, and rebooted the system, I was able to get link.

Ok looking in DMESG I found this: [ 3.789865] cxgb4 0000:15:00.4: Direct firmware load for cxgb4/t4-config.txt failed with error -2 [ 4.541838] cxgb4 0000:15:00.4: Successfully configured using Firmware Configuration File "Firmware Default", version 0x0, computed checksum 0x0 [...

I'm using a direct fiber optic cable between PVE and switch port, but not getting link: TX -> RX RX -> TX I've tried swapping the cable TX/RX around just in case, but no change. Reminds me of the "allow_unsupported_sfp" issue with Intel 10GBE and "unsupported" SFP+ modules but I am not...

**WARNING** to future low budget 10GBE NIC purchasers.... Chelsio T420-CR does not work OOB here with PVE 6.x. If you're finding these old threads, be sure to research well before you buy. This was incorrect. The Chelsio T420-CR (and likely T5xx and T6xx from same driver series) did work...

Any ideas here? We bought a few of these cards because they were low cost and could be used OOB with FreeBSD, but apparently with Proxmox they may not OOB ready These Chelsio's CXGBE seems like it should be supported: https://manpages.debian.org/buster/freebsd-manpages/cxgbe.4freebsd.en.html...

I am seeing the message in startup: This would lead you to believe it is updating the firmware on the card right? Unfortunately no other messages for cxgb4 and I do not see them as interfaces in the system.

Hi Bill, Based on you reply I dug around a little more. I don't think shareiscsi is built into the ZFS used by proxmox unfortunately. Properties that allow you to set 'sharenfs' and 'sharesmb' exist though. I've checked in both PVE 5.4-3 and 6.x. I'll try to work through the german doc...