Remember.... just because you are virtual does not imply that your storage is virtual, nor does virtual storage imply that the storage will be shared between workloads or VMs. None of that is implied or suggested in going virtual. You still maintain all proper storage management decision making when virtual as you did physical. You don't get to give any of that up.
In restrospect, I probably ought not have included the System Center Dude stuff in the discussion, since it seemed to just cause confusion about what I was curious.
You still maintain all proper storage management decision making when virtual as you did physical.
I believe this is the greatest takeaway from the discussion. Regardless if the environment is like the one I'm in where ultimately one physical storage device is hosting all of the virtual storage within the VMs.
Confirmed, snipping the orange wire (I needed help as I can't see orange) did the job, drive showed up immediately.
Congrats! I wasn't sure you'd be up for the task. A lot of people are afraid to make permanent changes to their equipment.
You can't believe how much pushback I got from @Dominica and @pchiodo about snipping a simple cable on a $2 SATA extension part! For me, it was a no brainer once knowing what it was. But they were up for spending hundreds of dollars to avoid snipping that wire. And it isn't even hard wired to the power supply or anything it's literally just a SATA extension piece! lol Like $2 tops if you don't shop around.
I would have been with @Dominica and @pchiodo on this. Electric scares me. I would think snipping the wire would cause a spark while I wasn't home and come home to a few burning cinders. :-)
That was mentioned as a concern. lol
FFS people need to just STFU if they don’t know how electricity works.
That was exactly my point and why I wouldn't have done it. As for STFU about well, that is where we differ. Those concerns could be alleviated with an explanation of why it would not be an issue.
For electrons to flow you need a circuit. If you cut the wire you don't have a circuit anymore and because of that you don't have any electricity flowing. Since there is no electricity, there can't be any sparks.
If you just cut the wire but don't remove it, then one end can come in contact with the chassis and then you have a circuit and electricity flowing.
Modern switched power supplies (as in your computer) have short-circuit protection. So nothing would happen except that 3.3V will go down to 0V. So if there is anything in your computer that need 3.3V power from the power supply, it will not get it.
If you had something else producing 3.3V (for instance a battery) and you'd short-circuit that, then it can get cause a fire. Just because it's only 3.3V doesn't mean anything.
And sparks is not a problem unless you're in an explosive environment. The problem is that a short-circuit cause increased current running in the wire. That current will turn into heat. That heat causes things to melt and catch fire. And that's how you burn down a house.
Also nice to know is that any electrical circuit inside a computer is low voltage, 12V or below. It can't kill you no matter what you do. It's the same voltage as you have in an ordinary car battery.
The only way to get into trouble with a computer is by disassembling the power supply. There you have lethal voltage.
For anyone curious, I was trying to migrate a Windows VM from QNAP to Proxmox, and this came in handy. Notes...
The VM type can be set to Q35/UEFI.
There may be multiple disk images on the QNAP box for the same VM: you need all of them in the same directory for the QCOW tooling to work correctly. Turn off the VM in Virtualization Manager, and copy them over to Proxmox via SSH; you can also download them via File Manager first.
importdisk on the latest file; it'll rebuild a RAW file where Proxmox keeps the data.
Mount the file in Proxmox as an IDE drive, and don't forget to set the boot order ahead of CD-ROM & Network.
https://github.com/virtio-win/virtio-win-pkg-scripts has the latest guest drivers for QEMU/KVM. https://superuser.com/questions/1057959/windows-10-in-kvm-change-boot-disk-to-virtio has some strategies for migrating from IDE to VirtIO; again, don't forget to check the boot order when detaching/re-attaching the disk image. Adding a tiny VirtIO drive while the system was up, shutting down, detaching the two drives & attaching the main as VirtIO; was the working solution for me.
Side note: unless you remember to look up your virtual MAC address in the QNAP VM, you'll need to reconfigure your network adapter after migration.
It really was a new term at the time. But he acts like the concept was new. It was very tried and true in the 1990s. It's an ancient article, just funny that in late 2000 he was thinking that MSPs were some hot, new thing, lol.
@Pete-S They dropped the price to 1061.24 since I posted. lol Interesting. Yes, but that is a max of 12 nvme. I may have misunderstood that option with 8 SAS/SATA. I am guessing that the max of 12 would allow for more SAS/SATA, although it doesn't mention it. My issue was also with the available drive capacities and cost per TB for spinning disks in the 2.5" spec.
Yeah, especially direct from the OEM. Have you thought about buying the storage from xByte instead?
Are their drives brand new? I did price out a server with specs as similar to Dell's as possible and it was only off by a couple grand.
IMHO, I consider their drives are 99.9% brand new as its possible an OEM install was done on the drive or something like that. Plus testing of the drive by the OEM and xByte.
Their hardware is manufacturer refurbished, not used. Big difference.
If you can get a Dell ProSupport (w/w-out) Plus 7 year warranty on the server with the drives from xByte, it doesn't really matter if they are new or not. They are under warranty for 7 years and you have no worries.