@eleceng The setting that you want is called "AutoProtect"

@scottalanmiller said in Multiple Virtual Disks and Application Performance:

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.

@rjt said in Adding remote storage to Proxmox:

@jaredbusch nfs on top of ZFS.
ZFS should be the underlying block/fs for everything whether a single hard drive, block storage like iSCSi, file storage such as NFS or CIFS. I like TrueNAS for this purpose. As you can see, I love ZFS. My problem is I also love CentOS. Need to figure out easy ways to get ZFS on CentOS. We should all write a letter to Larry asking him to open up the license.

Most of us here do not subscribe to The Cult of ZFS. Yes, it has a place, but not nearly like it's made out to be.

I would like to say that I have not spoken to people who disagreed with the title. I would like to, but...

@dafyre Thanks, testing now to see if it works (as expected).

@Pete-S said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

@pmoncho said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

@JaredBusch said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

@scottalanmiller said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

@pmoncho said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

@scottalanmiller said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

@Pete-S said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

@scottalanmiller said in How to Connect Power Disable SATA Drive to Dell Inspiron 5676:

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.

Thank you for the explanation. Very helpful.

if you want to also know the progress you can pipe it to pv, like in the below example

ssh [email protected] "sudo dd if=/dev/nvme0n1" | pv | dd of=/Users/someuser/Desktop/mydisk.img

@dbeato said in Access Changed Files on VSS Copy on Write Disk Image:

@scottalanmiller said in Access Changed Files on VSS Copy on Write Disk Image:

@black3dynamite said in Access Changed Files on VSS Copy on Write Disk Image:

Mount the disk image on Windows Server instance, from the mounted disk drive, go to Properties and then Previous Versions?

That's what I thought. But it just seemed too easy, lol.

Lol, anything that appears with Microsoft as easy should work but emphasis on "should" 🙂

Emphasis with "assume" too. lol