DIY NAS Thread

[it.expert]

Προφανώς με διαφορετικους λογαριασμούς ε?

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk

Δεν έχει να κάνει με λογαριασμούς, μην μπερδεύεσαι.

Τα Virtual είναι ξεχωριστά μηχανήματα με δικά τους Resources που απλά τρέχουν πάνω σε έναν host (esxi, hyperv κτλ)

Μπορεί να έχεις πχ στημένα 4 διαφορετικά μηχανήματα με 4 διαφορετικά λειτουργικά τα οποία να δουλεύουν όλα ταυτόχρονα με διαφορετικούς ρόλους.

Virtualization - Wikipedia, the free encyclopedia

[it.expert]

Παρακάτω 2 κείμενα (από τον ίδιο άνθρωπο) που εξηγούν περί FreeNas και virtualization τα οποία είναι πολύ καλογραμμένα οπότε και δεν θα μεταφράσω (με συγχωρείτε)

Αν τα είχα διαβάσει από την αρχή μπορεί να είχα γλιτώσει τις άπειρες ώρες που έφαγα προσπαθώντας να υλοποιήσω αυτό που είχα σκεφτεί.

Please do not run FreeNAS in production as a Virtual Machine! | FreeNAS Community

FreeNAS is awesome. FreeNAS can and will run as a VM. That does not make it a good idea.

FreeNAS is designed to run on bare metal, without any clever storage systems (UNIX/VMFS filesystem layers, RAID card caches, etc!) getting in the way. Think about this: ZFS is designed to implement the functionality of a RAID controller. However, its cache is your system's RAM, and its processor is your system's CPU, both of which are probably a lot larger and faster than your hardware RAID controller's cache!

Without direct access to the hard drives, FreeNAS lacks the ability to read SMART data and identify other storage failures.

A lot of the power of FreeNAS comes from ZFS. Passing your hard disks to ZFS as RDM to gain the benefits of ZFS *and* virtualization seems like it would make sense, except that the actual experiences of FreeNAS users is that this works great, right up until something bad happens, at which point usually more wrong things happen, and it becomes a nightmare scenario to work out what has happened with RDM, and in many instances, users have lost their pool. VMware does not support using RDM in this manner, and relying on hacking up your VM config file to force it to happen is dangerous and risky.

FreeNAS with hardware PCI passthrough of the storage controller (Intel VT-d) is a smart idea, as it actually addresses the three points above. However, PCI passthrough on most consumer and prosumer grade motherboards is unlikely to work reliably. VT-d for your storage controller is dangerous and risky to your pool. A few server manufacturers seem to have a handle on making this work correctly, but do NOT assume that your non-server-grade board will reliably support this (even if it appears to).

Virtualization tempts people to under-resource a FreeNAS instance. FreeNAS can, and will, use as much RAM as you throw at it, for example. Making a 4GB FreeNAS VM may leave you 12GB for other VM's, but is placing your FreeNAS at a dangerously low amount of RAM.

The vast majority of wannabe-virtualizers seem to want to run FreeNAS in order to provide additional reliable VM storage. Great idea, except that virtualization software typically wants its datastores to all be available prior to powering on VM's, which creates a bootstrap paradox. Put simply, this doesn't work, at least not without lots of manual intervention, timeouts during rebooting, and other headaches.

I'm pretty sure I'm forgetting a few. But the conclusion is this: it's perfectly fine to experiment with FreeNAS in a VM. However, if you run it in production, put your valuable data on it, and then something bad happens, and you absolutely positively must get your data back, there probably won't be a lot of help available from the forum. We've seen it happen again, and again, and again. Sigh.

"Absolutely must virtualize FreeNAS!" ... a guide to not completely losing your data. | FreeNAS Community

You need to read "Please do not run FreeNAS in production as a Virtual Machine!" ... and then not read the remainder of this. You will be saner and safer for having stopped.

<the rest of this is intended as a starting point to be filled in further>

But there are some of you who insist on blindly charging forward. I'm among you, and there are others. So here's how you can successfully virtualize FreeNAS, less-dangerously, with a primary emphasis on being able to recover your data when something inevitably fscks up. And remember, something will inevitably fsck up, and then you have to figure out how to recover. Best to have thought about it ahead of time.

Pick a virtualization platform that is suitable to the task. You want a bare metal, or "Type 1," hypervisor. Things like VirtualBox, VMware Fusion, VMware Workstation, etc. are not acceptable.

VMware ESXi is suitable to the task.

Hyper-V is not suitable for the task, as it is incompatible with FreeBSD at this time.

I am not aware of specific issues that would prevent Xen from being suitable. There is some debate as to the suitability of KVM. You are in uncharted waters if you use these products.

Pick a server platform with specific support for hardware virtualization with PCI-Passthrough. Most of Intel's Xeon family supports VT-d, and generally users have had good success with most Intel and Supermicro server grade boards. Other boards may claim to support PCI-Passthrough, but quite frankly it is an esoteric feature and the likelihood that a consumer or prosumer board manufacturer will have spent significant time on the feature is questionable. Pick a manufacturer whose support people don't think "server" means the guy who brings your food at the restaurant.

You will actually want to carefully research compatibility prior to making a decision and prior to making a purchase. Once you've purchased a marginal board, you can spend a lot of time and effort trying to figure out the gremlins. This is not fun or productive. Pay particular attention to the reports of success or failure that other ESXi users have had with VT-d on your board of choice. Google is your friend.

Do NOT use VMware Raw Device Mapping. This is the crazy train to numerous problems and issues. You will reasonably expect that this ought to be a straightforward, sensible solution, but it isn't. The forums have seen too many users crying over their shattered and irretrievable bits. And yes, I know it "works great for you," which seems to be the way it goes for everyone until a mapping goes wrong somehow and the house of cards falls. Along the way, you've probably lost the ability to monitor SMART and other drive health indicators as well, so you may not see the iceberg dead ahead.

DO use PCI-Passthrough for a decent SATA controller or HBA. We've used PCI-Passthrough with the onboard AHCI controllers on mainboards and LSI controllers usually pass through fine. Get a nice M1015 in IT mode if need be. Note that you may need to twiddle with setting hw.pci.enable_msi/msix to make interrupt storms stop.

Try to pick a board with em-based network interfaces. While not strictly necessary, the capability to have the same interfaces for both virtual and bare metal installs makes recovery easier. Much easier.

Now, here's the thing. What you want to do is to use PCI-Passthrough for your storage, and create a virtual hardware platform that is very similar to your actual physical host... just smaller. So put FreeNAS on the bare metal, create your pool, and make sure that all works ... first! Then load ESXi. ESXi will want its own datastore, and cannot be on the PCI-Passthrough'd controller, so maybe add an M1015 in IR mode and a pair of disks for the local ESXi image and datastore (you have to store the FreeNAS VM somewhere after all!). Create a FreeNAS VM and import the same configuration.

Now at this point, if ESXi were to blow up, you can still bring the FreeNAS back online with a USB key of FreeNAS, and a copy of your configuration. This is really the point I'm trying to make: this should be THE most important quality you look for in a virtualized FreeNAS, the ability to just stick in a USB key and get on with it all if there's a virtualization issue. Your data is still there, in a form that could easily be moved to another machine if need be, without any major complicating factors.

But, some warnings:

Test, test, and then test some more. Do not assume that "it saw my disks on a PCI-Passthru'd controller" is sufficient proof that your PCI-Passthrough is sufficient and stable. We often test even stuff we expect to work fine for weeks or months prior to releasing it for production.

As tempting as it is to under-resource FreeNAS, do try to aggressively allocate resources to FreeNAS, both memory and CPU.

Make sure your virtualization environment has reserved resources, specifically including all memory, for FreeNAS. There is absolutely no value to allowing your virtualization environment to swap the FreeNAS VM.

Do not try to have the virtualization host mount the FreeNAS-in-a-VM for "extra VM storage". This won't work, or at least it won't work well, because when the virtualization host is booting, it most likely wants to mount all its datastores before it begins launching VM's. You could have it serve up VM's to other virtualization hosts, though, as long as you understand the dependencies. (This disappoints me too.)

Test all the same things, like drive replacement and resilvering, that you would for a bare metal FreeNAS implementation.

Have a formalized system for storing the current configuration automatically, preferably to the pool. Several forum members have offered scripts of varying complexity for this sort of thing. This makes restoration of service substantially easier.

Since you lack a USB drive key, strongly consider having a second VM and 4GB disk configured and ready to go for upgrades and the like. It is completely awesome to be able to shut down one VM and bring up another a few moments later and restore service at the speed of an SSD datastore.

[TifoziF1]

Δεν θα μπορούσες να εγκαταστήσεις το freenas στο h/w σου και πάνω του να εγκαταστήσεις το VirtualBox να στήσεις τα VMs που θές ?

VirtualBox On FreeBSD - Tutorials / Howtos - Sysconfig's Wiki

[it.expert]

Εαν το στησεις με ΖΕΝ Server, πάλι θα έχεις θέμα με το RDM ?

Για να μην μείνεις παραπονεμένος

Cross your fingers!!!

Έγινε επεξεργασία Ιανουάριος 17, 2014 από it.expert

[it.expert]

Δεν θα μπορούσες να εγκαταστήσεις το freenas στο h/w σου και πάνω του να εγκαταστήσεις το VirtualBox να στήσεις τα VMs που θές ?

VirtualBox On FreeBSD - Tutorials / Howtos - Sysconfig's Wiki

Σε αγαπώ, έτσι απλά...

[YDinopoulos]

Τελικά τί εγινε με το ΖΕΝ ?

[it.expert]

Ακόμα παλεύω. Μου άρεσε το Xen και παιδεύομαι. Έπαιξε αμέσως το passthrough με τους 2 δίσκους, ο 3ος δεν θέλει...

[it.expert]

Τελικά τί εγινε με το ΖΕΝ ?

Αλλά τώρα που το σκέφτομαι, δεν αξίζει. Και με τον XenServer, οι επιδόσεις του write/read είναι κάτω του αναμενόμενου. Μόλις δοκίμασα με τους 2 που βλέπει έχοντας φτιάξει ένα Stripe. Δες νούμερο:

Δεν είναι τραγικές αλλά κάτσε να μπουτάρω από Pure FreeNas εγκατάσταση να καταλάβεις διαφορά

Πίσω σε 10...

[it.expert]

[MENTION=376]YDinopoulos[/MENTION] δες ομορφιά... Εγγραφή 2 μεγάλων αρχείων και ένα Sequential για το νούμερο.

Τερματίζει το Gigabit για πλάκα!!!

[slalom]

Κατι δε μου αρεσει εδώ

Εμενα φτανει τα 100ΜΒ/sec και ακομα δεν εχει τερματισει το Gigabit

Δες τα δικα μου

[thaaanos]

Δεν σε πρόλαβα.

αν πας για ZFS με FreeNas ξεχνά το virtualization. (προσοχή και με την μνήμη τουλαχιστον 6 για το Freenas)

Μπορείς όμως να στήσεις jails κάτω από το freenas και να τελειώνει το παραμύθι,

το μόνο που δεν είμαι σίγουρος είναι αν σηκώνει Χ για απευθείας σύνδεση με TV, αλλiως streaming αν έχεις μοντέρνα TV.

Συμβουλή αν υπάρχουν τα φράγκα: πάρε έναν ακόμα δίσκο και στήσε raidZ2 πάνω στους 4, μιας και είναι 3tb, τον μαμά βάλε τον εκεί που έχει θέση για cd, για τα jails.

[it.expert]

Κατι δε μου αρεσει εδώ

Εμενα φτανει τα 100ΜΒ/sec και ακομα δεν εχει τερματισει το Gigabit

Δες τα δικα μου

Για κάνε ένα 2πλό run Seq του 1GB

[slalom]

Εγω να το κανω αυτό?

Ειμαι ΟΚ όπως ειδες στις εικονες, δεν εχω πρόβλημα

Το 85ΜΒ/sec με χρηση δικτυου 99% δε μου αρεσε, εκτος αν μετεφερες και κατι άλλο που δε φαινοταν.

[minast]

Εγω να το κανω αυτό?

Ειμαι ΟΚ όπως ειδες στις εικονες, δεν εχω πρόβλημα

Το 85ΜΒ/sec με χρηση δικτυου 99% δε μου αρεσε, εκτος αν μετεφερες και κατι άλλο που δε φαινοταν.

To να προσπαθείς να βγάλεις συμπέρασμα από το νούμερο που βγάζει το παράθυρο της αντιγραφής δεν είναι καθόλου ακριβές. Αντίθετα, το γράφημα της χρήσης του δικτύου είναι αρκετά πιο αξιόπιστο...

[slalom]

Δηλαδη τωρα τι θες να μας πεις, ότι εχει σφαλμα?

Αναλογικο είναι?

Μιλαμε για 20ΜΒ διαφορα, ~20% αποκλιση

[it.expert]

Εγω να το κανω αυτό?

Ειμαι ΟΚ όπως ειδες στις εικονες, δεν εχω πρόβλημα

Το 85ΜΒ/sec με χρηση δικτυου 99% δε μου αρεσε, εκτος αν μετεφερες και κατι άλλο που δε φαινοταν.

Όπως βλέπεις δεν είναι 85 αλλά 101-107. Η ένδειξη των windows είναι λίγο ό,τι να ναι.

Γι αυτό σου είπα να κάνεις το παραπάνω αν θες.

Από την άλλη οι κάρτες μας λογικά δεν είναι ίδιες. Μπορει η δική σου να πιάνει μεγαλύτερη πραγματική (αν και χλωμό διότι κι εσύ 100% έπρεπε να πιάνεις εκτός και αν σε φρενάρει ο δίσκος που δεν το ξέρω)

Btw ούτε σε εμένα φαίνεται να έχει πρόβλημα

Sent from my Note II

Έγινε επεξεργασία Ιανουάριος 18, 2014 από it.expert

[slalom]

Δεν είναι θεμα της καρτας 1000ρες είναι και οι δύο.

Ο δισκος μου δεν τερματιζει.

[tragikos]

Αναφερεις θεμα ασφαλειας. Το Raid xx ΔΕΝ ειναι ασφαλεια. Ειναι θεμα data availability σε ενα hardware προβλημα 1-2 δισκων. Αν θες ασφαλεια, κοπια και αλλου. Αλλιως Backup ΔΕΝ εχεις

Δεν είμαι σίγουρος ότι καταλαβαίνω τι εννοείς.

Μήπως ότι το να έχεις μια κόπια σε έναν εξωτερικό που έχεις εκτός ρεύματος είναι πιο ασφαλές από το να έχεις RAID-1 σε ένα NAS ανοιχτό 24/7;

[vaios]

Επειδή και εγω χρειαζόμουν ένα Nas με αρκετό χόρο και να είναι επεκτάσιμο και μου κάθονταν ένας Microserver N36L.

Configuration

Microserver N36L 6 gb Ram.

2x2tb + 2x3tb + 500gb Hdd.

HP NC112T ( NIc teaming )

οι ανάγκες ήταν το μοίρασμα ταινιών και αρχείων μέσα στο οικιακό δίκτυο ( Smb , Iscsi ) και Dlna .

H λύση που βρήκα που μου δίνει πολυ μεγάλη επεκτασιμότητα ήταν Server 2012 με ρόλο Storage Server.

Στημένο με Thin Provisioning σε Raid 5 .

Παράληλα τρέχει και Plex Server για Dlna κλπ.

Σας παραθέτω και Screenshot από το στίσιμο καθώς και από copy από τον Server.

[it.expert]

Κομπλέ είναι, πολύ καλό!