I never bother mirroring disks in a home server. I just make sure I back up to my z240 nas with a 12tb mirror on a daily basis.... 20w overhead for 12tb is fine by meI have 2x 2TB NVME drives in there right now, but think it's probably better to run them in a ZFS mirror (or at least play around with it like that), and move proxmox off to the sata drive.
Oh that a+e microSD card adapter is slick. I don't think I could run proxmox off it (unless I get crafty with moving logs to a ramfs). Would be neat if there was a small ssd drive that could fit and key into that slot. I've seen adapters for m.2 but it might get chunky.i have been using this little adapter with satadoms. I also just tested the a/e keyed sd card adapter. it works also as long as your os can usb boot since it is just using the usb side of the m.2 wifi connector View attachment 27370
I'm used to the vmware world of things - where I could just turn each drive into a datastore for VMs, and assign/vmotion accordingly. Looks like I could just apply an LVM to the secondary drive and use it fully like that as well.I never bother mirroring disks in a home server. I just make sure I back up to my z240 nas with a 12tb mirror on a daily basis.... 20w overhead for 12tb is fine by me
Agreed, at work I ensure full redundancy, local and geo resilience. My home lab is a toy and somewhere to learn new tech. Rebuilding a box takes 20 minutes with ansible and I can restore any vm's back up and running in a further 10 minutes. No lossI'm used to the vmware world of things - where I could just turn each drive into a datastore for VMs, and assign/vmotion accordingly. Looks like I could just apply an LVM to the secondary drive and use it fully like that as well.
Yeah, I'm of a similar mindset - there's a lot more wanting to experiment with configurations themselves before assigning any real workloads to it. That said, I do like separating the OS off from VM storage though.
Appreciate the reply, I'll get one ordered then!no you will still need a riser. Those expansion ports plugin differently
Yeah, now that I'm running twice-daily backups of all my VMs and hosts to my PBS server, I'm pretty sure my zfs mirrors are overkill.I never bother mirroring disks in a home server. I just make sure I back up to my z240 nas with a 12tb mirror on a daily basis.... 20w overhead for 12tb is fine by me
It is Optional DisplayPort 1.2 out connector (second) in Tiny M920qMy second query is, here's a pic of the machine I've purchased and I think that's a HDMI/diplay port
View attachment 27426
One possible option - assuming there's an A+E keyed slot, is to get a wired gigabit (or 2.5gbps even) to a+e key adapter. Assuming you just want to only have two total interfaces.I've just purchased an M920q with the aim of making an opnsense box (virtualised on top of proxmox) and had a couple of questions, whilst from all the reading here I can see that an Intel I350 quad NIC card works, I don't really need that many ports and am trying to minimise power consumption so I was wondering if anyone has had success running an I210 single NIC card in it, I have read references to a BIOS whitelist and wasn't sure if that applied to addon cards to the PCIe slot.
My second query is, here's a pic of the machine I've purchased and I think that's a HDMI/diplay port socket in the PCIe slot, so can I assume that the necessary riser will be present? I understand I'll still need some sort of baffle for whatever NIC card I use.
View attachment 27426
Thank you, that's really useful information. Appreciate the detailed reply and pointers in how to fit it properly when I come to replace things.BTW in yours case mentioned the item (on picture) is NOT properly attached to Tiny.
The lower toothed edge of the bezel should be inside the chassis.
It means that One had problems with smart installation (with escape from attachment).
IMVHO again problems with connections of DP header
with too elastic (in this place) the System Board.
In some cases, DP socket not work (or problems with proper DP signals).
To correct this (same kind of magic) :
by the first good attachment, small plate to SB but with unscrewed bezel.
Then screwed bezel to plate, after this to chassis.
Would that mean the slot isn't then available for a NVME drive? Or would this be going where the Wireless card should go? I did think about this. Just not sure how to go about attaching it to the chassisOne possible option - assuming there's an A+E keyed slot, is to get a wired gigabit (or 2.5gbps even) to a+e key adapter. Assuming you just want to only have two total interfaces.
Something like this: https://www.amazon.com/IO-CREST-Gigabit-Ethernet-Module/dp/B08S2P1N6W/
If it's there, it should be a very tiny a+e key slot on the top instead of the underside where a wifi card would normally go. It's different from your run of the mill M.2 nvme drive.Would that mean the slot isn't then available for a NVME drive? Or would this be going where the Wireless card should go? I did think about this. Just not sure how to go about attaching it to the chassis
Answered my own question about whitelisting, no idea how I missed that last night when I posted.You can install most x1/x2/x4/x8/x16 PCIe cards as long as they are half height and shorter than 150mm, but bear in mind there is no direct airflow around the card and little space, so avoid anything too hot.
That's pretty nifty, these tiny machines are so versatile it's amazing. I like the idea of this solution from a "it's very cool" perspective and space/airflow but I'm struggling to see how I'd attach it to the chassis, I do have a 3d printer so I might scour thingiverse and see what's available, because whilst I can print, my CAD skills are non-existant.If it's there, it should be a very tiny a+e key slot on the top instead of the underside where a wifi card would normally go. It's different from your run of the mill M.2 nvme drive.
Oh the ethernet port to the rear of the chassis? Probably some cutting up of the bracket you have in place - I'd popout the VGA port blank you have on the right, and then check dimensions to see how far off you'd be.That's pretty nifty, these tiny machines are so versatile it's amazing. I like the idea of this solution from a "it's very cool" perspective and space/airflow but I'm struggling to see how I'd attach it to the chassis, I do have a 3d printer so I might scour thingiverse and see what's available, because whilst I can print, my CAD skills are non-existant.
I saw that you slapped an LSI 9200-8e in there. I'm thinking of upgrading already from the single SAS port HBA I have now. My only hesitation on the 9200 was heat generation. Have you noticed any issues now that you've been running it for >6 months?As a conclusion to this story, the 01AJ940 adaptor worked perfectly. The LSI HBA was detected straight away. No idea why the 01AJ902 wouldn't work, but this information might be useful for people in the future.
Oh, if I'd seen that I might have opted for a M910q instead. Definitely an option I could consider. Any experience with either passing it through to an opnsense VM on proxmox or using it as a paravirtualised card in proxmox?[tiny pc] m.2 pcie addon 2.5gbe nic
Check that post