I use a Synology NAS with NFS for manual backups from Proxmox. Works pretty well.

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.

@krisleslie said in Linux Copy a Disk Over SSH with DD:

@scottalanmiller can this be used while on XCP-NG host?

Can be used on every non-Windows system.

@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

@ccwtech said in Import a QCOW2 Into Proxmox:

A couple of things I ran into. You need to make sure that you switch to BIOS to UEFI or it won't recognize that there is anything to boot to.

And you have to choose something other than VIRTIO for the controller. Because it's likely that there aren't VIRTIO drivers installed you have to use something else.

You can't install drivers to a device you don't have so...

You can add a 2nd hard drive to the mix as VIRTIO to get Windows to ask for drivers, then you can shut down, trash the 2nd HD and make your main disk use the VIRTIO controller. Obviously use the VIRTIO drivers for the other unknown devices that pop up and you are good to go.

None of that has anything to do with the actual import of a QCOW2 into ProxMox.

This is all crappy windows design. I've imported many things and with the exception of an ancient RHEL 4 system, had zero issues importing something that was already a QCOW2.

@scottalanmiller I haven't used them, but from what I hear it's only network storage. I could easily build something that would be faster for less money.

@Jimmy9008 said in CSV... what happens at a lower level?:

That makes sense, would a drop from 1GB/s to 100MB/s be expected? Seems huge...

Depending on the system, yeah, especially with certain kinds of operations.

@pmoncho said in How do you get your departments to quantify what they actually need for their jobs:

Your more than welcome to dive into https://issurvivor.com/ and search his archives

His only mention of MSP is from Nov, 2000 when he discovered the term. And he talks about ASPs as well. I had started my first of both, over a hear before he heard the terms :)

https://issurvivor.com/2000/11/20/trend-overload-first-appeared-in-infoworld/

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.

Thanks for the reply, the issue is that sanoid.conf does not send the snapshot to the usb but syncoid does, or does having that template automatic prune the snapshots?

@wrx7m said in IOPS for SSD?:

@travisdh1 said in IOPS for SSD?:

@wrx7m said in IOPS for SSD?:

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

@Obsolesce said in UREs Strike InnoDB on MySQL:

@scottalanmiller said in UREs Strike InnoDB on MySQL:

@Pete-S said in UREs Strike InnoDB on MySQL:

Step one is to remove the drives and clone them with dd or recovery tool to a new drive.
You could probably recover 99.9% of the data - if you want.

As you can guess from all of their previous issues, they don't want to pay for any recovery, they just want it magically fixed for free. They don't own any storage onto which to clone it, either.

Then what is the point of any of it? It appears to have zero value to the business.

I said that to them.

@StorageNinja said in Veeam with NetApp?:

Netapp E-Series is the same as the old Dell MD36xxx or the LSI enginio code base (IBM also sold a similar low-end modular array). These things were wicked fast/cost-effective at streaming workloads (got used for Lustre clusters a lot as the DAS on the nodes). Dell's abandoned reselling them for Seagate (Dothill) but they still around

Not wicked fast compared to building your own. And the staggering lack of internal support if anything goes wrong is a big deal... storage is one of those things you want to have work, especially at these price ranges. Having been a NetApp customer, I know that their support is helpless when it comes to trying to do high performance, their crap just falls over and so do their engineers.

@matteo-nunziati said in Deciding Between Hardware and Software RAID in My FreeNAS Deployment:

@saniplastic said in Deciding Between Hardware and Software RAID in My FreeNAS Deployment:

@DustinB3403 said in Deciding Between Hardware and Software RAID in My FreeNAS Deployment:

metadata

metadata?

please explain more.

The config files where the vm is defined. Do not backup the vm disk only. I suppose he referes to this.

I backup with veeam.
whole vm files.