Leaderboard

Popular Content

Showing content with the highest reputation since 11/06/21 in all areas

  1. I have a created a file manager plugin, which I will release when the next Unraid 6.10 version comes out, This plugin extends the already present Browse function of Unraid with file management operations, such as copy, move, rename, delete and download. Operations can be performed on either folders and/or files and objects can be selected using a selection box at the left (in case multiple objects need to be copied or moved for example) or by clicking on a selection popup to an operation on a single object. All operations need to be confirmed before proceeding, this should avoid accidental mistakes. The file manager gives direct access to all resources on the array and pools and should be handled with care. Below two screenshots to give a first impression. Once released more info will be given in the plugins section.
    13 points
  2. Hallo an alle! Wollte hier schon längst mal meinen Server vorstellen da ich das für schon längst fällig hielt und ich sonst irgendwie nie so richtig Zeit gefunden hab. Der Server besteht aus folgenden Komponenten: Case: NZXT H2 Classic (Frontblende wurde entfernt für besseren AirFlow) zusätzlicher HDD Cage: ICY Dock MB074SP-B (wird demnächst gegen ein MB074SP-1B mit Hot-Swap getauscht) CPU: Intel Core i5-10600 CPU Kühler: Noctua NH-U14S Motherboard: ASUS Z490-E GAMING RAM: 4x Corsair Vengeance LPX 16GB DDR4 @2666MT/s C16 Netzteil: Corsair RM850x Addon Karten: Mellanox ConnectX3 CX311A-XCAT 10Gbit/s SFP+ NIC 2x DigitalDevices Cine C/T v6 Dual Tuner TV Karten Dell Perc H310 LSI 9240-8i im HBA Modus Coral Dual Edge TPU (leider nur einer verfügbar da nur über PCIe x1 angebunden) Nvidia T400 2GB Speicher: 2x Samsung 970 Evo Plus 1TB ZFS Mirror (appdata, Docker, libvirt,...) 2x Crucial MX500 1TB als Cache Pool (Nextcloud Datenverzeichnis, unRAID Cache,...) 1x M2 NVMe Transcend 128GB (per VirtIO durchgereicht zu einer Debian VM zum bauen der Docker Container) 6x WD Reds/White Labels für das Array mit einer Parity (Debian aptitude Mirror, verschiedenste Mirror von Betriebssystemen, Private Cotnainer Registry, Medien...) 1x Industrial Samsung SSD 128GB (per VirtIO durchgereicht zu einer VM zum bauen der Plugin Pakete für unRAID) 1x WD Red Unassigned Devices (Nextcloud externe Speicher, Backups, nicht kritische Daten...) Boot Stick(s): 1x Transcend JetFlash 600 Extreme-Speed 32GB USB 2.0 (unRAID) 1x SanDisk 16GB Cruzer Blade USB 2.0 (durchgereicht zu einer unRAID VM) Der Server beherbergt außerdem auch noch ein Git Repo, Jenkins und wie schon oben erwähnt eine Debian VM & eine unRAID VM. Auf dem Server werden lokal alle meine Docker Container gebaut, werden danach zu DockerHub und nochmal auf den Server in eine Private Registry (sicher ist sicher ) hochgeladen. Wie schon oben erwähnt befindet sich auf dem Server noch eine unRAID VM die gestartet wird wenn eine neue Version von unRAID gefunden wird, diese wird dann automatisch auf die neue Version aktualisiert. Danach startet der Build Prozess für die verschiedensten Plugins die nach dem erfolgreichem build auf Github in das dementsprechende Repositor hochgeladen werden. Eine zusätzliche Routine wurde ebenso eingebaut die die unRAID VM startet wenn eine neue Version von ZFS, CoreFreq und Nvidia Treiber gefunden wird die diese Packages für die aktualle Release version von unRAID kompiliert und hochlädt. Momentan wird bei einem Build Vorgang, wenn eine neue unRAID Version gefunden wird, folgendes kompiliert: ZFS Package @steini84 USB Serial Package @SimonF USB IP Package @SimonF NCT 6687 Package Nvidia Treiber Package DigitalDevices Package LibreELEC Package TBS-OS Package Coral TPU Package Firewire Package CoreFreq AMD Package CoreFreq Intel Package AMD Vendor Reset Package HPSAHBA Package Sound Package (noch kein Release geplant) So ein Build Vorgang dauert ca. zwischen 35 und 45 Minuten, je nachdem wie viele Nvidia Treiber Version gebaut werden müssen, da mittlerweile mindestens zwei bzw. in Zukunft drei gebaut werden müssen: Production Branch New Feature Branch Beta Branch (nur falls vorhanden) 470.82.00 (letzte Treiberversion die Serie 600 und 700 unterstützt) Der Build Vorgang ist vollständig automatisiert und wird spätestens nach 15 Minuten nachdem eine neue unRAID Version Released wurde gestartet. Ein Hinweis zum Verbrauch, durschnittlich liegt die Systemlast beim Bild Vorgang bei ca. 180Watt für die 35 bis 45 Minuten, hab noch ein Bild von der Auslastung ganz unten hinzugefügt... 🙈 Nur zur Erklärung, diese Packages müssen für jede unRAID Version kompiliert/erstellt werden da die Module die dafür benötigt werden in Abhängigkeit zum Kernel der jeweiligen unRAID Version stehen, die Plugins erkennen eine Änderung der Kernel Version beim Booten und laden die Packages für die jeweilige Kernel Version herunter und werden dann beim Start auch gleich installiert. Das ist mitunter ein Grund warum ich gegen Virtualisierte Firewalls auf unRAID bzw. AdBlocker die auch unRAID mit einschließen bin, da ein herunterladen der Packages beim Start von unRAID dann nicht möglich ist weil eben keine Internetverbindung besteht bzw. der DNS Server (im Falle von AdBlockern) noch nicht verfügbar ist. Momentan überlege ich den Server mit einem i9-10850k auszustatten um den Build Vorgang nochmal zu verkürzen aber da diese CPU momentan schwer zu bekommen ist und auch nicht gerade billig ist muss das noch warten. Ich hoffe euch hat die Servervorstellung und der kurze Einblick hinter die Kulissen wie so einiges bei mir auf dem Server funktioniert gefallen. Hier noch ein paar Bilder: Auslastung beim Build Vorgang, immer zwischen 90 und 100% :
    11 points
  3. Hey Unraid Community! For the first time ever, we're running a Cyber Monday Sale: 20% off Unraid Pro and Pro Upgrades! If you're planning a new build soon or want to purchase a key for a friend or family member, do it this Monday, 11/29/21- 24 hours only from 12:01-11:59 PST! No server installation required for purchase. For full details, head over to unraid.net/cybermonday
    9 points
  4. In den anhängenden Bildern seht Ihr einen Unraid Server der aus drei Gehäusen besteht. Der eigentliche Server (oben) besteht aus: ------------------------------------------ 1x Supermicro SC846E16 Gehäuse 1x Supermicro BPN-SAS2-EL1 Backplane 1x Supermicro X12SCA-F Mainboard 1x Intel Xeon W-1290P CPU 1x Noctua NH-U9S Kühler 4x Samsung 32 GB M391A4G43AB1-CVF RAM --> 128 GB 1x LSI 9300-8i HBA mit zwei Kabeln an interne Backplane angeschlossen 2x LSI 9300-8e HBA mit jeweils zwei externen Kabeln an eine JBOD/DAS Erweiterung angeschlossen 2x Samsung 970 EVO Plus 1 TB PCIe NVMe M.2 SSD 24x Festplatten mit Dual Parity - überwiegend Toshiba Jede der beiden JBOD/DAS Erweiterungen besteht aus: --------------------------------------------------- 1x Supermicro SC846E16 Gehäuse 1x Supermicro BPN-SAS2-EL1 Backplane 1x Supermicro CSE-PTJBOD-CB2 Powerboard 1x SFF-8088/SFF-8087 Slot Sheet 2x SFF-8644/SFF-8088 Kabel (zu einem der beiden LSI-9300-8e HBA im Server) 24x Festplatten mit Dual Parity - überwiegend Toshiba Jede JBOD/DAS Erweiterung wird im Server als eigenständige Unraid VM geführt. Jeder Unraid VM ist einer der beiden LSI 9300-8e HBAs durchgereicht sowie ein eigener Unraid USB Lizenz Stick. Jeder Unraid VM sind 16 GB RAM zugewiesen. Jede Unraid VM besitzt Zugriff auf alle CPUs - es gibt also keine CPU Isolation. Alle Festplatten der JBOD/DAS Erweiterungen sind via SMB im eigentlichen Server gemountet. Der Server hat somit alle Festplatten aller drei Gehäuse im Zugriff. Es gibt keine User-Shares. Alles läuft über Disk-Shares. Da ich nach wie vor BTRFS für meine Zwecke als - ahem - gefährlich betrachte, betreibe ich mit den beiden 1 TB PCIe NVMe M.2 SSDs keinen RAID Cache/Pool. Die Docker- und VM-Subsysteme laufen auf einem Single XFS Pool den ich selbst regelmäßig auf die zweite SSD repliziere. Das System ist "rock solid". Es hat schon mehrere Inkarnationen hinter sich. Unraid, und hier speziell das Unraid Array, genießt mein volles Vertrauen. Mir fehlt nur noch die Unterstützung für mehrere Unraid Arrays. Dann könnte ich die beiden LSI 9300-8e entfernen und statt dessen die in den Backplanes eingebauten Expander nutzen. Theoretisch geht das jetzt schon - ich hatte das auch schon getestet - die Performance Werte über VirtIO waren aber unerträglich und kläglich. Vorderansicht: Rückansicht (ich habe es nicht so mit Kabeln): Das innenleben eines der beiden JBOD/DAS. Links kommen die beiden Kabel vom zuständigen HBA, in der Mitte das Powerboard: Hier der Link zum alten Server - den gibt es nicht mehr: https://forums.unraid.net/topic/78165-how-many-tbs-is-your-unraid-server/?do=findComment&comment=797795
    5 points
  5. 16 at home counting a couple of test servers plus a small server at work, do I win?
    5 points
  6. Since you mention "for others to see", I take it as giving me right to comment (after all it IS in a public forum). So let me comment on this after reading your original post too. 1) Disclaimer: I am not taking the side of Limetech. I don't care. I had my own rough times in the past (with Tom too IIRC)... many years ago. Don't even remember why any more. Back then I "voted" with my decision. I stopped using unRAID for years. Yet I returned because it became what I dreamt it should be before I stopped using it. So being first and foremost a consumer, not a fanboy nor a hater, I just returned. My original Pro license waited for me patiently. 2) Since you are talking about "tone"... Your tone in your first post and this post is quite a Karen. You are only ONE customer. Who made you our representative and the right to speak for us? Who told you we want this removed (even if we don't use it, I don't either). It doesn't bother me. It just stays there, who cares. 3) I don't see any threat whatsoever by LT. Maybe you mean "treat", but still, I don't see an issue. 4) LT is a business, as you said. They make things, we buy them, they support them indefinitely ON the price we originally bought them (no service fees). So why would they be grateful, or would we be grateful? $$$ = product. And I bet you have the product already. It is a transaction - as simple as that. Yet, they stand by their clients all right and do it for years (and this is not proven by removing something nobody else asked to remove than entitled-you). 5) Also, since they are a business, it is in the end their choice if they want to actively promote a new feature (their "cloud" system) if it is not too intrusive. So that login up in the corner and the OPTIONAL plugin, is not what I would call "intrusive". 6) Nobody is forcing you to update unRAID to next version. Stay on the current one. Remove unRAID for all we care. 7) If this login button and menu is (or was) a real problem, I am sure someone will step in with a tiny plugin (like the one that widens the interface for super-wide screens), that removes it. Or you can try making such a plugin. 8 ) Back to tone. I am sure if your original post was something like "this thing on the top right about logging in... could you please make hide-able, maybe by a toggle in the settings in some future version, for us OCD people?". This possibly would get a better reply. Cheers.
    5 points
  7. Yes, these are things I have in mind for future releases, but wanted to start with the basics and get feedback. Development simply takes time
    4 points
  8. Good day! Machinaris v0.6.6 is now available. Changes include: - Maize - cross-farming support for this blockchain fork. - Forktools - utilities including a multiproc patch to limit memory usage. - Farming - right-side of Plots table offers Chia "plots check", slowly generated on background thread. - Bug Fix - hourly log rotation for `farmr`, auto-deletion log if above 20 MB in size. Sorry all!
    4 points
  9. You know the drill - "Go PRO or go home"
    4 points
  10. Pre-6.10 release: if someone wants to try out Unraid with a Trial key they have to give us an email address. When someone makes a key purchase they have to give us an email address. Hence we already have email/key database, i.e., "accounts". The primary purpose of the UPC is to now make these accounts accessible by users. We leveraged the IPS (forum) member capabilities to do this. That is why we enabled 2-factor authentication for the forum. When you "sign-up" via a sever we create an association between the account screen name/email address and the particular key GUID. If you already have a forum account then "sign-in" will do the same association. This lets us simplify a great deal of support having to do with keys. You also get a nice "dashboard" (the My Servers menu option) that shows all your servers. In order to show this dashboard, the sign-up/sign-in process will upload your server name and description. This is so we can present a link to your webGUI on your LAN. But of course this is a local IP address and only works if you click from a browser running in a PC on the same LAN. We don't send up any other info and the code that doing the sending up is open source in the webGUI - you can examine and see this. If you don't want to use your forum account to associate with your keys, then just create a different forum account. Yes, having "accounts" will open the door for us to provide "cloud based" services. For example you can install our My Servers plugin and get real-time status of your server presented on the dashboard as well as automatic flash configuration backup. If you don't want this, don't install the plugin. If you don't want your server to appear "signed in" then sign out. For those who think the will never sign-in and are disturbed by having a "sign in" link in your header - well we will consider cosmetic changes. No doubt some may have more questions and want more details. So let's do this: go ahead and fire away but please ask only one question or ask for only one clarification per post and I'll try to answer them all until we're all exhausted.
    4 points
  11. In episode 12, @jonp covers the recent announcement by Facebook regarding "The Metaverse." Is this really a good idea and is Facebook the right organization to launch it? Could this be the beginning of an Orwellian future? In addition, Jon also provides a public service announcement regarding Linux driver support of hardware and how some users with specific gear may need to hold back on updating Unraid to the latest release.
    4 points
  12. Good day! Machinaris v0.6.3 is now available. Changes include: Staicoin - cross-farming support for this blockchain fork. Chia - Update to version 1.2.11. See their changelog for details. NOTE: If you encounter v0.6.3 upgrade error, you are likely using a customized appdata location. Please visit Docker tab of Unraid UI. Select each Machinaris container (one by one), edit their Config, Show More Settings (at bottom), find mnemonic_path and Edit it to the location where you are storing the original mnemonic.txt. Apologies again for any inconvenience to existing users.
    4 points
  13. Retired computer tech support for 32 years. Started as a dBase/Visual Basic database programmer for the first 5 years but the rest of my time as system administrator for file & print servers. First with Novell Netware & Citrix Winframe later with Windows server & SUSE samba servers. At home I have a small network of Windows 10 Home PC (used for photo editing of my raw photos shot with Nikon & Olympus DSLRs via Adobe Lightroom & Photoshop), digital illustrations via Photoshop, Corel Painter, ArtRage & Rebelle, 3D modeling via 3DCoat, Blender, Silo3d 2.5, Moi3D, DAZ Studio and 3D rendering in e-onsoftware's Vue, 2nd Windows 10 Home PC using as a NAS via Windows storage space and a linux PC running Zorin-Os which is a Ubuntu 20.04 derivative. All computers were built by me. I take many photos at local classic car shows during the summer as well as landscape photos throughout Nova Scotia, New Brunswick and Maine. I also have lots of 3D models I've created or purchased as well as digital illustrations. All assets reside on my photo editing PC and backed up to a mess of 9 external drives plus several portable drives. I stated shucking some of the older 3 & 4TB WD external drives and placing them into a new Corsair 200R case with a Seasonic 650 powersupply. I had an older Gigabyte GA-H97-D3H socket 1150 mobo with I-7-4770S cpu and 32 gbs of memory on my shelf (used to be my photo editing PC). My first thought was about building another Windows 10 storage spaces box or an Ubuntu server using mdadm raid 5 or 6 OR ZFS raidz1 / raidz2. But raid 5/6 seemed too old school. And ZFS raid seemed to waste too much disk space. Then I ran ran into SpaceInvaders youtube channel when I started searching for NAS solutions and alternatives to Windows storage space and Linux mdadm or ZFS pools. After much youtube watching, I downloaded the trial yesterday and was hooked. I'll be purchasing soon. Maybe tomorrow. My hobbies are digital photography, 3D modeling/rendering, digital illustrating, watching NHL hockey (played the sport unit I was 52), antique and classic cars (restored an antique car in 1983 and still own it) and of course computer technology. Cheers and many thanks for creating this wonderful product Unraid.
    3 points
  14. Probably this Dec 2 05:39:35 Tower root: Creating new image file: /mnt/user/system/docker/docker.img size: 18000G Dec 2 05:39:35 Tower root: touch: cannot touch '/mnt/user/system/docker/docker.img': No space left on device You're attempting to create an 18T docker image. Settings - Docker and set it to something reasonable (like 20G)
    3 points
  15. I'm sure that will solve your issues.
    3 points
  16. Below I include my Unraid (Version: 6.10.0-rc1) "Samba extra configuration". This configuration is working well for me accessing Unraid shares from macOS Monterey 12.0.1 I expect these configuration parameters will work okay for Unraid 6.9.2. The "veto" commands speed-up performance to macOS by disabling Finder features (labels/tags, folder/directory views, custom icons etc.) so you might like to include or exclude these lines per your requirements. Note, there are problems with samba version 4.15.0 in Unraid 6.10.0-rc2 causing unexpected dropped SMB connections… (behavior like this should be anticipated in pre-release) but fixes expected in future releases. This configuration is based on a Samba configuration recommended for macOS users from 45Drives here: KB450114 – MacOS Samba Optimization. #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [global] vfs objects = catia fruit streams_xattr fruit:nfs_aces = no fruit:zero_file_id = yes fruit:metadata = stream fruit:encoding = native spotlight backend = tracker [data01] path = /mnt/user/data01 veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes My Unraid share is "data01". Give attention to modifying the configuration for your particular shares (and other requirements). I hope providing this might help others to troubleshoot and optimize SMB for macOS.
    3 points
  17. There was a discussion about this a few years ago, but it was never changed, and IMHO it's more than time for that, it's a constant support issue, UEFI should be enable by default both in the download/ZIP and when using the USB tool, it won't affect legacy boot, concern at the time were buggy UEFI BIOS but this should no longer be an issue.
    3 points
  18. Good day! Machinaris v0.6.5 is now available. Changes include: Cryptodoge - cross-farming support for this blockchain fork. Docker images now roughly 1/3 the size of previous releases. Shared base image further decreases download size for forks. API endpoint /metrics/prometheus exposes plotting statistics. Thanks to @Nold360 for the contribution! Windows deployments now support automatically mounting remote plot shares (such as on a NAS) using CIFS in-container. On Wallets page, display total wallet balance including cold wallet address amounts.
    3 points
  19. If they start enforcing the min 5 requirement (they don't now), then I think that might be the solution - users pairing up in groups of 5.
    3 points
  20. Ich stelle vermehrt fest, dass der Unraid Cache mit einem klassischen Schreib-/Lese-Cache verwechselt wird. Ursprünglich war der Unraid Cache lediglich ein Schreib-Cache (siehe Link unten). Zwischenzeitlich wurde er zu einer schnellen Ablage für Docker Container und VM Images aufgebohrt. Was er aber nach wie vor nicht ist, ist ein klassischer Lese-Cache. https://wiki.unraid.net/Manual/Overview#Cache
    3 points
  21. Hello everyone. Tailscale for unraid has become rather more popular than I ever imagined, when I started this it was in the great tradition of scratching my own itch, wanting to access my sever over tailscale. Since then there have been over 250,000 downloads, there are tutorials on youtube, and increasing numbers of requests for new features and support. So I think it might be time to open this up a little bit more and so I have a few asks. Firstly, if you want a new feature, or think you have found a bug please don't post them here - or at least not only here, please create an issue on github if at all possile. https://github.com/deasmi/unraid-tailscale Secondly I'm just one person and while this is a realatively simple thing, it's really just packaging tailscale, using it can get more complicated as new features are always being added. So if you'd like to get involved as a developer or tester for future things please let me know by sending me a DM along with how you'd like to help. Thank you Dean
    3 points
  22. Buy a bigger house. Problem solved
    3 points
  23. ZFS Master 2021.11.09a is live with a few changes, check it out: 2021.11.09a - Add - List of current Datasets at Dataset Creation - Add - Option for export a Pool - Fix - Compatibility with RC version of unRAID
    3 points
  24. there are ongoing issues with PIA DNS, you can try setting NAME_SERVERS to the following (removes PIA DNS):- 84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
    3 points
  25. I have a 12600K and DDR5 mem arriving next week and will do some testing.
    3 points
  26. 3 points
  27. After updating your Authelia to v4.33.1, You'll probably see an error "Can't continue due to the errors loading the configuration" To solve the issue, edit the configuration yaml file, and add a new encryption_key key under storage. storage: local: path: /config/db.sqlite3 #this is your databse. You could use a mysql database if you wanted, but we're going to use this one. encryption_key: you_must_generate_a_random_string_of_more_than_twenty_chars_and_configure_this Hope this helps
    2 points
  28. Sure thing. @Torsten_UN- please send us a ticket to https://unraid.net/contact with a screenshot of the issue and I will assist.
    2 points
  29. bienvenido yo llevo un año mas o menos con unraid. me apunto Ibracorp (no lo conocía), de Spaceinvaders si me e visto casi todos los videos. un saludo
    2 points
  30. Hi, the patch is automatically applied on every start of the container so nothing needed on your end. Please see /tmp/forktools_setup.log inside the container.
    2 points
  31. For new Maize farmers, there's a promo to receive 30 XMZ. Jump on their discord for details if it's of interest.
    2 points
  32. 1.18.1 has been released and tagged as 1.18.1, 1.18 and latest.
    2 points
  33. 1.17 works fine with Java 17.
    2 points
  34. Yes, this is because the scanner & folder watcher doesn't know for sure whether you deleted it or it got moved or maybe some random file system issue and it wasn't detected. In that case if it removed the audiobook you would lose any metadata you adjusted or entered in manually. This could change in the future, but for now I think it best to play it safe.
    2 points
  35. Did you update to the latest container today? If it still isn’t working after updating probably best to attach your entire supervisord.log to your next post. Be sure to redact user/password info.
    2 points
  36. https://github.com/hectorm/docker-qemu-win2000 Tried it and it works out of the box (connect via RDP to your server's IP address) Who'd have thunk this would have been possible. my-qmu-win2000.xml
    2 points
  37. and you did set this up like described ? may also take a look here
    2 points
  38. hat funktioniert, nachdem ich gerafft habe das ich alle 4 festplatten im container erstellen muste. Vielen Danke allen
    2 points
  39. Good day! Machinaris v0.6.4 is now available. Changes include: - Farmr - include `farmr` client for optional monitoring at farmr.net - Stor - cross-farming support for this blockchain fork. - Cactus - cross-farming support for this blockchain fork. Thanks to all who helped test and provided feedback! Known-Issue Discovered: Please use ":test" images for Machinaris harvesters of Cactus and Stor to avoid issue on harvester connection to fullnode.
    2 points
  40. Now that the QEMU included with Unraid 6.10.0-rc2 now supports emulation of ARM CPU's I am wondering if anyone has got such a VM running? I am wondering if it is now possible to emulate a Raspberry Pi (any model) and if so running which OS? If so please share the XML you are using for the VM.
    2 points
  41. Du musst den Container bearbeiten und weitere "path" hinzufügen. Da dann /mnt/disk1 zb
    2 points
  42. Nov 6 15:23:28 OuterHaven emhttpd: error: get_limetech_time, 256: Connection timed out (110): -2 (7) Was wondering why the next log entry wasn't "Soon". Should this be a feature request @limetech@jonp?
    2 points
  43. I have a similar issue with Catalina, samba is on and off. Reverted back to rc1 and everything seems to be OK. In my case the connection to the Tower samba shares will drop on a random basis. Not sure how to reproduce this issue.
    2 points
  44. With all due respect, have you addressed the UPC / login option located in the upper right of the webGUI header? Give us an option to take it off, remove it? I don't care to log in, I don't care for the cloud intrusion in my personal life, I don't care to see it, full stop period, regardless of your business case. And I am very unhappy how some of these intrusive feature are being pushed down our throats. I just want it off my GUI header and I don't want anything to do with unraid cloud service as working offline (OFF THE GRID) is my primary priority. Can we have that option?
    2 points
  45. Drive encryption is one of Unraid's many good features. When you encrypt part or all of your array and cache, at some point you might end up wanting to change your unlock key. Just how often, would depend on your threat model (and on your level of paranoia). At this time (6.8), Unraid does not have a UI for changing the unlock key. Here is a small tool that will let you change your unlock key. Each of the current and new unlock keys can either be a text password / passphrase, or a binary key file if you're into those (I am). Your array must be started to use this tool. Essentially, the script validates the provided current key against your drives, and on all drives that can be unlocked with the current key, replaces it with the new one (in fact, it adds the new key to all of them, and upon success, removes the old key from all of them). Important: The tool does not save the provided new (replacement) key on permanent storage. Make very sure you have it backed up, either in memory (...) or on some permanent storage (not on the encrypted array 😜 ). If you misplace the new key, your data is hosed. Currently this script needs to be run from the command line. I may turn it into a plugin if there's enough interest (and time) - although I'm pretty sure Limetech has this feature on their radar for some upcoming version. Usage: unraid-newenckey [current-key-file] [new-key-file] Both positional arguments are optional and may be omitted. If provided, each of them is either the name of a file (containing a passphrase or a binary key), or a single dash (-). For each of the arguments, if it is either omitted or specified as a dash, the respective key will be prompted for interactively. Note: if you provide a key file with a passphrase you later intend to use interactively when starting the array (the typical use case on Unraid), make sure the file does not contain an ending newline. One good way to do that is to use "echo -n", e.g.: echo -n "My Good PassPhrase" > /tmp/mykeyfile This code has been tested, but no warranty is expressed or implied. Use at your own risk. With the above out of the way, please report any issues. EDIT 2021-08-16: Posted an updated version for Unraid 6.10. The 6.10 OS includes an updated "lsblk" command which is not backwards compatible. unraid-newenckey
    2 points
  46. im going to make this short and sweet, the week long test went extremely well, no dropouts whatsoever, it simply worked and allowed me full access to my LAN whilst hundreds of miles away, love it!.
    2 points
  47. I have to admit my lazinees towards success. I install a Windows 10 with a SSD. Then I realize that I have the chance to export a GPU ROM (vbios). So I did. Archwiki mentioned KVM guest will see a shadow copy of a vbios which would be invalid. That is the white screen and the error in the previous log about ROM. I tried with the original ROM from GPU-Z which does not work. Even though I don't know why removing NVIDIA header from vbios helps but it works. Following this guide and editing a ROM without NVIDIA header. Now the steps are crystal clear. 1. setup necessary steps as Unraid guide. 2. pass all device in the IOMMU group of NVIDIA card to vfio. 3. disable efifb. My boot paramaters for Unraid looks like this: kernel /bzimage append video=efifb:off vfio-pci.ids=10de:21c4,10de:1aeb,10de:1aec,10de:1aed initrd=/bzroot 4. Use SATA for isoes and modified vbios to use NVIDIA card. Genesis is a little bit tedious but the reward is great!
    2 points