How to run TrueNAS on Proxmox?
Вставка
- Опубліковано 25 чер 2024
- DIY NAS Server - Installing TrueNAS on my Proxmox Server. How to install and set up TrueNAS as a virtual machine with a passthrough of hard drives or storage controllers. Complete Walkthrough. #Proxmox #TrueNAS #HomeLab
Home Server PC build with Proxmox: • Home Server PC build w...
Follow me:
TWITTER: / christianlempa
INSTAGRAM: / christianlempa
DISCORD: / discord
GITHUB: github.com/christianlempa
PATREON: / christianlempa
MY EQUIPMENT: kit.co/christianlempa
Timestamps:
00:00 - Introduction
01:44 - What is TrueNAS Core?
02:25 - What you should consider!
05:25 - Create a VM in Proxmox
08:25 - Passthrough Storage Controllers
09:08 - Passthrough HDDs without a PCI Controller
12:53 - Install TrueNAS Core
14:02 - TrueNAS Basics
16:17 - Run VMs in TrueNAS
________________
All links with "*" are affiliate links.
You are just a freaking beast man. I don't care how long it takes you to make videos or whatever.. You changed my life man and I am thankful. Best wishes from Pakistan :)
Haha, thank you so much! :)
I can't tell you how many times I've watched this video for the CLI way to add the hard drives. Thank yo so much.
Im glad it was helpful 😊
@@christianlempa i watched over 200 times
You're just an amazing mentor! Thanks for all the knowledge, much appreciated
super helpful, especially how to setup drives connected to the motherboard controller. Works fine for a simple media pool. THANKS!
For better Processor access and usage, set the CPU type to host and then it will be hardware rather than software access and processing. I have been running this for a few months and it is solid!
Thanks! I'll look into it
Hi @NightHawkATL, have you perhaps had any further experience with this setup (TrueNAS VM on Proxmox bare metal)? I'm thinking of spinning one up myself. Have you faced any issues?
@@unsolaci initially I had processor type Default (kvm64). It does not allow to use virtualization on TrueNas Scale. Once I switched to type host - I can use virtualiztion (for dockers)
Hi, thanks for the tutorial. However, my disks details don't show up with "ata-xxxxxx-xxxxx". It shows as "wwn-xxxxxxxxx", please, what should I do? Regards
@@IamKanuKingsley Check your connector type. What kind of drives do you have?
I loved that you showed how to do it without pcie passthrough, every tutorial did pcie which wouldnt work for my setup! Thank you so much!!
Thanks! Glad it helped ;)
I just wanna say THANK YOU! This video is the only one that explains how to add a hard disk not the card itself. It can be not elegant but for me that don´t have a card and it´s hard to get one in affordable price (i live in Brazil) works perfect! Thank you! Thank you! Thank you! Thank you!
love the honesty and dedication man, keep going :)
Perfect. Got my TrueNAS VM up in 10 minutes. Computers are so cool these days. Also, for any of your videos, much respect for your brevity. All the details we need while respecting our time.
Awesome! Thanks :)
Thank you. I've been struggling to make this work for a couple of days. It works now.
Glad it helped
great content like always! keep up the good work
Thank you! Of course, I'll do :)
Followed this. Worked like a charm.
Awesome! This video was very helpful. Much appreciated.
Glad it was helpful!
champion, excellent guide as always
Thanks 🙏
fantastic, you solved my TRUE nas migration from old server to new Proxmox true nas vm
Awesome! Glad I could help you
@@christianlempa just migrated using your commands and video .. thanks..
@@christianlempa I need your help , i could see 90% ram usage in Proxmox grap for TRUENAS Virtual machine. How to fix this. ( i have allocated 8GB) always 7.5GB using.. free .5
Thank you! This was a great video!
Super cool video!
love your work!! thank you so much
Excellent video. Thanks for elaborating on how to set up the physical drives independently with the Truenas VM. Personally, I would instead use RaidZ and have TrueNas control the RAID System rather than having to use a controller to manage the hard drives. I'm sure you would sacrifice a little performance. However, everyone's use case can be different.
Finally a tutorial I actually understood. Dankeschön!
Sehr gerne! :)
Thanks for the detailed video and I'm looking forward to videos about Sophos XG :-)
Awesome, thanks 😄
great walk thru...thank you
Thank you!
This video is really really the top of the iceberg. A few crucial thing is missing from this like:
- excluding the disks from pve, or else you will wonder why it periodically interrupts disk operations or wakes up sleeping disks
- disabling the "use tablet for pointer" as that in itself causes 10+% CPU load on the host side for some reason
- disabling "hardware" acceleration of virtIO as this is known to cause problems
- doing smart configuration (like APM, idle times) on the host side as the guest won't have access to smart data and alerts
- optionally moving the system dataset to the boot disk
do you have any links to tutorials on the above suggestions?
Thank you. I'll stick with bare metal then. Sounds like this dude just wants us to stick his finger up our po poos.
So true he don't even set the guest OS right.. XD
What he should also really have done is change the cpu type to host so that the VM can use all the instructions the cpu has...
Excluding disks from pve, nobody mentioned that. I scratch my head for weeks why disk sleep isn’t working 😡
How do I exclude disks from pve?
I like this vid. Good insight.
Thank you really much for showing how to connect or passthrough those hard disks! I've googled this before and people wrote, that this is impossible!!! SO WRONG.
Your method works like a charme!
Thank you thank you really much, you are really a kind guy!!! :)
Greets TheItalian :)
Thank you! Glad to hear that :D
It actually is impossible to really pass through the drives itself (if you don't count NVMe drives) as what he's doing is using the drive as a backing store for a virtual drive with the size of the physical drive. You don't get any of the benefits that would make sense for zfs / TrueNas like smart or temperature sensors.
@@LampJustin is this fact? SMART won't work with this passing threw method? that would be a shame, I didn't had time yet to check if SMART Values are showing up or not ...
@@theitalian94 that's definitely the case. You either need to setup monitoring on the Proxmox host itself or get a SATA/SCSI controller and pass it to the VM.
The truenas VM is unfortunately not able to see the smart values, but you can still check it on proxmox.
Bro, THANKS!!!
Thank you for this. :D
You're welcome!
Thank you!
Very helpful. I so plan to virtualize some of my file storage. I'd like to have separate VM / machines for different storage purposes. So, glad that you overviewed how you did it.
Thank you! :)
Amazing, thanks mate !
Glad you liked it!
Well explained.
Thank you! :)
I'm currently using zfs pool on proxmox itself and a LXC container as a network storage but I think your way is much better
Thanks, You helped my a lot
You’re welcome ☺️
@@christianlempa On more question Christian, How could I do that in proxmox container?
I'm looking forward to Rockstor 4. Btrfs raid-1c3 is just so nice and to have native support and custom Docker support is quite nice.
I'm looking forward to TrueNAS Scale, this will be a great Proxmox replacement
@@christianlempa I thought this myself, however the clustering of servers requires TrueCommand, which comes at a fee. Ultimately, i decided to stick with proxmox as migrating from the old hardware i used was simpler than trying to port VM's while running two seperate clusters. Ceph for block storage + 3 node cluster is a sweet spot for my needs atm.
I run truenas scale on a z620 with an asmedia pci chip. It's passthrough, and it works great with two drives mirrored... 10TB. Been running proxmox for about 4 years now
Note that the disk serial number results for some nvme devices in ridiculous long serial numbers, so I prefer to use the UUID of disk or partition for the creation of the datapool. I always split my HDDs in 2 partitions, the first ~40% faster partition is for the VMs and the remainder for the other stuff. As a consequence the SSD I use for caching has four partition, 2x cache (L2ARC) and 2x log (ZIL).
Very cool.
Thanks!
This is excellent thank you for the in depth review. I was wondering on your options for a NAS on Proxmox how would that apply if I implemented a Proxmox cluster with HA? Knowing we can't mirror the serial # of hard drives do you know of options I could look into?
3400 views of this great video,,, and only "156 likes" shame on these people,,, hit the likes people!!!!,,, this is someone doing hard work for us to view and learn....!
Thank you so much, what a great feedback 😉
One little thing (and I've been seeing this in a lot of similar tutorials), but "SCSI" is pronounced "Scuzzy". Probably not something that comes up a lot if you didn't work in enterprise storage in the 90s, so I'm not surprised that nobody else has mentioned it
Great video! I have my TrueNAS system virtualized for well over two years now and it runs flawlessly. Using Vmware ESXi. :)
Thank you 😊 sounds like a great setup as well! ESXi is also nice
That's exactly how I do it. I have two TrueNAS VMs along with PFSense, Windows Server 2016 (to play with), and a variety of Windows and Linux desktops. Remoting into Linux can be problematic though...
🤔 so there is physical storage dedicated to the hypervisor in addition to the physical storage dedicated to TrueNAS?
Thanks! I really got a lot from this video. I also benchmarked using the same volume set with direct hardware versus via a hypervisor. My file read/write test on a 1 GB file direct hardware was around 19 to 20 seconds whereas via a hypervisor it was around 22 seconds. So I can see some overhead but no too much.
I'm still debating if I want to go direct hardware or via Proxmox. It's just not so clear what the advantages are except if I had a complex confirmation and I didn't want to redo it. It seems you can easily import volumes that were disjoined from the operating system in TrueNAS via the import command.
Not necessarily need ecc, it helps but not necessary.
ZFS actually checksums the data as it goes into the drive, so it actually prevents data corruption that would have been an actual issue with traditional raid.
The thing with ecc RAM is mostly for example the case of a database where you have large amount of data being transacted in flight and then ZFS is writing that back to the hard drive, but it actually checksums the data as it is writing it. For file storage it isn't that much of an issue.
Thanks for sharing your insights. It's hard to find good technical resources on this topics, some people say it's important, some people say it's not.
As I said in my video it's hard to determine how likely something goes wrong, even if it might be just a very rare edgecase scenario, I decided to recommend ECC in my video, because it is useful for filesystem integrity, and it's not hurting anyone to use it.
@@christianlempa Its hurting guys who dont use enterprise server :D
But yes, great to know. So i should run my Databases on my HP380p instead using one of the nodes wich are built with desktop hardware.
At 00:30 you tell there are no "bigger" downsides when running TrueNAS on Proxmox.
There are a few guys who provide their proxmox/rancher nodes with disc-space by linking them with 10G connections to a single TrueNAS Server.
Why do they mostly use a baremetal TrueNAS server? Is it because of performance reason or is there a problem to link the disc-space to another node?
@@christianlempa Also i recommend to take a look at the new "TrueNAS SCALE". I would love to see a video from you!
"TrueNAS SCALE is a new Open Source edition that brings scale-out storage and hyper-convergence to enthusiasts, businesses, and data centers alike.
TrueNAS SCALE is in the Alpha development phase and can run on any TrueNAS system with higher than 10GbE support."
@@DigitEgal TruenasCORE it's Unix when TrunasSCALE it's a Linux beta at the moment, who has tried can tell us the differences! Big thanks bye
oh i used freenas on my HP microserver gen7for a while but decided to give Xigmanas a try... had it for 2 years but now went back to TrueNAS scale.. SO much better than this complicated and buggy hell of a NAS OS called xigmanas. never again.
Thanks Christian for this video. Is it possible with passthrough HDDs to use an smb share as mount point to a docker container like ecoDMS? The docker ist on the same proxmox as truenas
Did you try to install a VM into the TrueNAS managed storage? Or do you just provide the space managed in truenas to the VMs as additional storage, e.g. as a remote /home?
Excellent video and instruction I appreciate your dedication to the community. I did have a question in regards to this process and Proxmox Clustering. What considerations need to be made there? Can this same process be done at the DataCenter level?
I think that Christian covered that with 3:40 about use of ECC memory. Because as you increase the scale, you increase the amount of errors. You wouldn’t be able to run a datacenter with desktops very effectively. Lots of errors and bugs.
Is it possible to create a folder on the zfs for photos other videos other for books with different record size (depending on file size) to optimize the space?
I've done this for some time , now I require the securing your home server with a firewall video asap please :D
It's coming but it will take a few weeks 😉
I usually virtualize pfense or opnsense, then additionally I put a container running Pihole to block ads and malware
Very detailed and helpful. Just wondering, is the raw HDD pass-thru to TrueNAS the recommended option or the only option? I mean, I am contemplating whether it would make more sense to create a RAID5 pool via m/b RAID controller and pass-thru the disk to TrueNAS instead. Would that be an option? I am using a Synology DS920+ as my main NAS Server. I am considering running a TrueNAS VM on Proxmox as a 2nd level level of data backup.
I'd love to see a solution that takes an old outdated dedicated NAS, connects it to a Pi running the NAS appliance and then gives you a (new) webgui+SSH+updates for the physically old Nas. :)
Nice one again. 👍
I have been running Free/TrueNAS on bare metal for years and love it. Tried it firs on consumer grade HW but it runs much better on a really old Proliant G5. I think its the ecc memory that boost the performance. Ecc memory and battery helps when things go sideways - as it usually do at som point.
I also have virtualization TrueNAS servers from time to time. My settings are different but generally the same as yours. I have been thinking of moving my production TrueNAS to Proxmox just to have all machines running Proxmox make some work easier. I run 3 Proxmox servers and a ProxmoxBS and then the TrueNAS.
I have 4 HP servers in my rack and one self build.
I strongly recommend real server HW due to performance and cost. SAS is superior but SATA is cheap - your choice.
I will not recommend the Scale at this time due to the weak performans as to date (see Tom Lawrence videos)
Exactly what I was looking for!
Glad it helped! :)
In proxmox 8 you can get the model and serial number for the drives in the Disks section of your node
hello thx for this video very useful.However if one disk fail how can you make to change It because I suppose you have to declare un new physical volume in proxmox is that easy
Was the reason to pass through the HD vs just allocating a pool of space from proxmox for the storage?
What is betterwith for Trunas on Proxmox? Pass through disk, pass through sata controller or just do do that and use virtual disks?
Hi Christian and everyone, with the passthrough of the disks to Truenas, do you have the SMART tests working? I can't see any tests results and even if I try a manual run, I got an error message "Short offline self test failed [unsupported scsi opcode]", does not matter the type of test selected.
Does the hard drive you pass through have to only be used by Truenas? As an example, I have a large hard drive that has files for home assistant and Jellyfin on it. Do I need to move those to another hard drive before passing it through to Truenas?
I know this comment is very late but not all motherboards have SATA as something you cannot passthrough, some boards show their sata controller as PCIe devices/chipset and allow you to passthrough them to said VMs (works for me, however it doesn't mean that It'll work for everyone)
At 13.24 where you mention about the bios mode, since you you propose to viewers to passthrough an hba controller, it would be better to select uefi and q35 options for the VM, as it is way better when you are passing through a pci device.
Thanks, I'll look into that!
This does solve one part of the problem that Proxmox is not so great for providing space if you do not want to separate the file server (or NAS) and the VE engine. But one problem remains: the TrueNAS VM cannot be snapshottet, since it has pass-thrus.
Also, this is a viable solution only if you deploy new hardware - you are in trouble when you try to migrate a huge array that is on an existing RAID, probably also encrypted.
I have yet found no way of doing this - if Proxmox mounts the device, it must also provide the shares (which is not very good at). Every other solution carries over the control to an embedded VM, which can then not be snapshottet like other VMs. Containers are not a solution for this, either.
Hello Christian, thanks again for your great content. Quick question, could you tell me what kind of terminal you re using? I kind of like the look of the interface...
Thank you again
Thanks! Back then windows terminal, now I’m using warp on macOS
@@christianlempa thanks for your time 🙂
I am trying to do a very similar setup but when I installed Proxmox I set up a ZFS RAIDz1 pool over three SATA disks. I can add that pool as a disk source from the Proxmox add hard drive menu. Should I have not set up ZFS on those disks via Proxmox and used the method in this video of adding the individual disks to the Truenas VM and then creating my zpool from within Truenas? What are the consequences of these two different methods?
what is the outcome in relative terms when comparing no passthrough vs passthrough?
1. Thanks!
2. First time NAS and ProxMox user.
3. I added 2 HDDs to a new install using your method. TrueNAS says they have same serial number. I drilled down in the "Disks" list and they both have empty serial numbers (which makes them equal I suppose). I will now look back at the QEMU command that added them and see if something there about serial numbers.
Same here. Did you manage to find a solution to this?
EDIT: I managed to find a solution. Go to your proxmox shell and do: nano /etc/pve/qemu-server/[ID-OF-YOUR-VM].conf
Find your SCSI device.
(Mine was "scsi2: /dev/disk/by-id/ata-ST5000LM000-2AN170_WCJ6B8PP,size=4883770584K")
Add your serial number at the end.
(Mine now is "scsi2: /dev/disk/by-id/ata-ST5000LM000-2AN170_WCJ6B8PP,backup=0,size=4883770584K,serial=WCJ6B8PP")
Hope that helps :)
@@flakmoppen I ended up buying an LSI HBA and passing them in that way. It is an old mobo and only had 4 SATA 3 ports so was worth it anyway because I was using 2 of those for ZFS boot of ProxMox. But thanks!
Great video. I tried the passthrough and it works flawlessly.
Just a question: why do we not add the hard disks to the VM via the PVE GUI? I think you would need to set the disks as storage devices in PVE (like you have with the truenas named storage)? I sadly skipped that part so can't try for myself if it is possible.
You can add the PCI device for the disk controller in Proxmox, I've tested it in my new setup and it works well.
It's been 2 years now and I wonder if you'd keep this as a setup? Any downside found in terms of performances or reliability during that time? Or perhaps you are rocking now a different setup for the storage part of your Homelab?
what would be a decent budget hba card? im new to this im probably never going to use more then 12 drives ever if anything's as well im just trying to virtualize my truenas and my firewall
I run omv on hyperv passing through an SSD. Works great, I also run all my dockers on it too!
Sounds like a cool setup 😁
hi do you have any idea if the passthru would work with hp 530sfp+ card cause i cant get it to work
How do I configure a disk array or disk bay?
I want to buy bare metal and then populate it with some disks. Can you please share some idea on how to set that up?
How do you install the qemu-guest,-agent on the TrueNAS Core VM?
I built my current Proxmox server around AMD 3400G CPU, before understanding the risk associated with non ECC memory. However, I agree with Michael that for home users it's not so much an issue. Plus one should not rely on ZFS or any RAID system equivalent for backup. For that reason I also use Backblaze, which has very reasonable rates for offsite backup storage. Then in the unlikely event that my data gets corrupted, I can rebuild it.
I am using Alpine Linux/SMB LXC container as a file server right now, but I really liked TrueNAS (was using my Proxmox box as standalone TrueNAS server) and will most likely switch to a TrueNAS VM in the near future. But LXC containers are a whole lot of fun, and very efficient.
Sounds great! Yeah I don't think that ECC is always needed, however I would still recommend it generally. But I can see that it's not a must have for every setup, especially in a home server.
Interesting... would anyone know if is possible to refer the hard-drivers by ID to a VM and still accessing them via Proxmox? As if the ZFS is used by two systems at the same time.
hey good video mate!. I ran my first trueness- proxmox install. I'm having issues with my Kubernetes cluster. not launching. any ideas in how to troubleshot that? cheers!!
Thank you! Depends on the k8s setup, maybe check out our discord ;)
Hi, how is it possible to automate backups of the truenas vm without the data-disks?
Got it - there is an option in the drive-settings of the vm :-)
let's say that i've setup a truenas/freenas or unraid within a vm. and i want this nas to use my to 2 harddrives in raid 1. would that be possible?
Hello, I am also going to build my first nas at home, I have 4x 8TB Hdd, that I have used i my old Readynas.
But now I want to run Proxmos on a ssd disk, and have vm like truenas...
My question is, should I install the truenas on the ssd or sould I install it on my raid with my 4 hhd ?
I just did approximately the same set-up, but I noticed that you don't have IOMMU enabled on your server?
If you enable IOMMU in your motherboard BIOS, you're able to pass through the onboard SATA controllers as PCIe devices to your VMs (in this case TrueNAS).
This gives the VM hardware-level access to the controller and all attached disks, and thus means more native performance + being able to do S.M.A.R.T. tests on the disks.
Oh that's nice to know, let me check that! Thanks mate 😍
@@christianlempa Just checked your motherboard manual, I would enable these settings:
Advanced/CPU Configuration/SVM Mode
Advanced/Onboard Devices Configuration/SR-IOV Support
And then look in Advanced/AMD CBS subsections for:
IOMMU
PCIe ARI
PCIe ACS
This is the single best advice here. Thanks for the information and I have just done that on my supermicro mobo.
Hello! great video! I have an question. Isnt the best way to use the /dev/sda1 /dev/sda2 and etc identification to passthru the hard drives from mainboard? in case of failure of hard drive you can offline it from truenas, power off the whole system and replase it to new one. you plug new hard drive and mount it in truenas and thats it. otherwise you must write the new id of new disk in proxmox at first.
You should use the IDs instead of sda, sdb, .. because these could change under some circumstances, so better go with the ID to avoid any issues.
@@christianlempa thank you!
currently im running a ITX Server with 16x LSI in a similar config, DMZ, 10G, LAN, Truenas Core VM on Server 2019 and passing the LSI to the VM. Im thinking about switching to proxmox due to ur videos or... stick with installing Truenas Scale as main OS on the server. It has 2x2TB SSD Raid 1 which is used for all kind of VMs for now, but i wonder if this fits fine for Truenas Scale and how the virtualization is on that. 2TB would be massive waste for Truenas only. Most VMs i currently use are fine in Scale with Apps, Plex, Nextcloud, but sometimes app dont fit and therefore virtualiszation would be ideal. thus i never worked with proxmox and i think truenas scale as main OS should be quite capable on Vms too + cloudflare tunnels for all of the apps to be accessible
I've been tempted by TrueNAS, but I already have an existing folder structure on my external drives that I don't want to lose.
I ended up just mounting the external drive on my pve host and pointing SAMBA at it.
Hello @christianlempa! Im running truenas on proxmox, but i need to changee the motherboard, could you make a tutotial on how to migrate everithing to the new sistem without loosing data?
curious about virtio block vs. the virtio scsi you're using in the video. Also - some people suggest write-back cache (*not* the one that is labeled "unsafe" of course). Anyone do testing with these?
Virtio blk should be marginally faster as it doesn't implement the full SCSI controller like Virtio SCSI. Blk just presents a block device to the system. Also I'd recommend to completely disable caching in this case, as Zfs does it on it's own and it will cause problems when there's a crash or sth
I tried doing this for the os drive of previous installs but they wouldn't load (both truenas and a windows 10 disk/vm) any ideas?
Hi, If I create another VM in Proxmox I should be able to access this TrueNAS right? As a shared storage among both VMs and Physical devices connected to the Host.
Sure that is possible
Sweet! Are you able to use thst pool which you created in TrueNas back in the Proxmox utilizing RAID? I sume you could, but How about when TrueNas is not running? Are there any disadvatgaes with this sort of approach you can think of? Why not to rather have TrueNas as a main OS and use virtualization There?
No, if you do passthrough the device becomes unavailable to the host
@@christianlempa and how you connect this drives to your VMs? as NFS?
Hi there! First of all, thank you for the great content and the great community! Y'all are my people :)
I wanted to ask, why go through the trouble of giving the VM direct control over the disks instead of allocating some disk space, like with the boot partition?
Thanks mate! :) ZFS works better with direct access on the drivers.
@@christianlempa That makes sense! Good to know it's just an optimization thing and not necessarily required for operation
@@christianlempa yeah but you do the opposite of you say. By binding the disks to the VM like you did, you just use the drive like a raw image. Nothing from the drive can be seen by the os.
Also you should've set the cpu type differently, kvm64 doesn't have access to most instructions
@@LampJustin Noob here. Does that mean actually that ZFS will not work as intended by binding it that way?
@@coolricksanchez yes and no. ZFS will pretty much work as expected, but there are some problems with it, first data integrity can't be certain as there are multiple levels of cache involved and zfs can't know what sector size the drive has, so performance will suffer if the sectors aren't aligned. Another problem is that some TrueNAS features just don't work for the reason that SMART isn't available, like disk error warnings and such.
Is it possible to add network card or network cad interface (in case when one card carry more than one interface) the same way as You added HDD? with out bridge, not by vmbr0 but directly eno0 let's say
Sure, you can add more network cards (as much as you need and fit in :D)
I cant get my HBA controller to passthrough to me TN VM. The drives are all listed under the node level and show up using lsblk. IOMMU is enabled in the BIOS. It is an LSI 3900 16i on a ROMED8-2T. Also couldnt pass the native on board sas controllers to pass through either.
Any reason to still go for TrueNAS CORE instead of SCALE?
I am currently running truenas bare metal but I do want to move it to a virtual machine through proxmox. Can I simply backup the data and the config file and use that? So once installation on proxmox is complete, can I just upload the config file and the set-up will look exactly like my previous installation minus the data?
Good question, I haven't done this unfortunately. But I believe you could, because you just need to pass the drives to the VM like they were in bare metal, everything else should remain the same, I guess.
Careful! There is a difference between plain ECC and registered/buffered ECC memory!
Just ECC can also run on some consumer price range machines. AMD Ryzens have unofficial support for it. It's in the chip but AMD didn't deactivate it and doesn't advertise it. It should work but it may not. No guarantee for that. And some selected Intel CPUs also can have ECC. Both will only work with unbuffered/unregistered ECC.
Registered/buffered ECC is a thing for high end professional server hardware only. Those machines that support over TB of RAM. It's not a thing for home players.
If you have problems on truenas that it cannot identify unique disks, use sata insteads of scsi: qm set 103 -sata1 /dev/disk/by-id/...
I have done a similar setup just a few days ago, with an old Fujitsu D3417 MoBo. I have installed Proxmox on a nvme ssd drive and therefore the buildin sata controller (00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)) was unused an i could easyly passthough it to the Truenas vm.
That's interesting. It seems that this also has something to do with the chip on the motherboard. Thanks for sharing!
Ok so I have truenas on baremetal then decided to do via proxmox last month.
After a while I skipped adding apps in truenas and left it only for shares smb and app made into proxmox mostly lxc so far so good, however my only issue
Truenas doesnt see the cpu temperature from cpu. Can any one share how did they fix that
I'm curious why you are logged in as 'root'; is it required or only for demonstration purposes??
Trouble with Drive stats Visibility and SMART in TrueNAS VM on Proxmox
I had set up a TrueNAS VM on Proxmox, utilizing a RAID Z configuration with four 2TB HDDs. Here's the catch: three drives are directly connected to the motherboard, and I've added a PCIe SATA expansion card for the fourth drive.
However, I've encountered a snag-I've noticed that not all drive information is visible in TrueNAS, and the SMART options aren't working either. Given that I'm now using this server for work purposes, I'm feeling a bit uneasy about the situation.
My SMB shares are functioning correctly, and backups are happening as expected. However, I'm concerned about potential drive failures and whether I'll be able to manage replacing a failed drive without risking data loss.
Is there a way to address this issue without redoing the entire setup? Any guidance or suggestions on ensuring drive visibility, SMART functionality, and data protection would be greatly appreciated.
Thanks in advance!
Great video, Im a bit late to the game but I have watched quite a few now. The more i watch the more confused i get. Ive had 2 low end servers over the years and recently wanted to update it. First server was WHS second was just an old PC running windows. Anway, i want a place to hold my files and Plex and perhaps try a few virtualizions. I want to use my old hardware to do this (4th gen i7)
Now i watch this and learn about needing ECC RAM and i dont know what to do. Honestly it all just seems too difficult
Don’t worry about ECC in a Homelab, will make your life easier :)
Instead of by-id is there a way to do the drive linking by physical port? I have a 24bay hot-swap chassis I want half the bays to be assigned to one program (truenas, unraid, etc) and the rest to another, but I am uneducated in linux things including commands and this "ssh"
I'd still suggest using by-id, linking to the drive rather than the bay. That way you can label the drives as TrueNAS and it won't matter which bay they go into. You could also tag the drive caddies so you can still have labels from the outside
If you really want to link to the bay rather than the drive, take a look at "/dev/disk/by-path" (instead of by-id). Keep in mind though, if you do that and then put another in-use drive into that bay, TrueNAS may not be able to tell that you're using a new drive and may just think it's had a drive replacement and start rebuilding the data it previously had. The only reason I can see for this being a good thing is if you expect your drives to die and need replacing often.