Leaderboard

Popular Content

Showing content with the highest reputation on 03/31/21 in all areas

  1. Interesting. Unraid OS 6.9.1 is on kernel 5.10.21 and the referenced patch is not applied. Upcoming 6.9.2 release is on kernel 5.10.27 which does have the patch. Working on finalizing the release now.
    4 points
  2. Big News from NVIDIA Just a few hours ago, NVIDIA added an article to its support knowledge base regarding GPU passthrough support for Windows VMs. While we've supported this functionality for some time, it was done without official support from the vendor themselves. This move by NVIDIA to announce official support for this feature is a huge step in the right direction for all of our VM pass through users. This should also help instill confidence in users that wish to pass through these GPUs to virtual machines without the worry that a future driver update would break this functionality. Let us know what you think about this announcement here!
    3 points
  3. @Boyturtle an update just rolled out. Give that shot. Resolved it for me so far.
    2 points
  4. currently working on it with a glass of rum&coke
    2 points
  5. Hi All, It has a 2.5G network onboard, updated the unraid version on the USB and it looks to have found the network again. All looks good besides my VM which requires a BIOS setting somewhere. Thank you for the help, things are rocking again this side. Regards, Brandan
    2 points
  6. Yes, I know, the server already built it about 1 and a half hours ago. EDIT: Please give my scripts a little bit, I update the versions every two hours and the build only for the Nvidia Driver takes about 30 minutes so the longest time you have to wait after a new driver is released is 2 and a half hours. EDIT2: But the good news is that the automated build is working.
    2 points
  7. This container will no longer be maintained or supported as of 23.07.2021. Fork it, modify it, do whatever with it if you need it. Docker container for Ethereum mining with CUDA (nsfminer) with Nvidia OC capabilities. This Docker container was inspired by the docker-nsfminer which was inspired by docker-ethminer. It uses the nsfminer with OC capabilities with the Nvidia driver. This docker will allow for over- and underclocking of Nvidia GPU's for Ethereum mining in a docker. One docker template per GPU. GitHub project: https://github.com/olehj/docker-nsfminerOC Questions about mining specific questions, workers and wallets will not be answered anymore. There's enough guides and information out there in the sky. Google it, please. Support here is limited to the docker container, where most is answered in this post below: Requirements Unraid 6.9+ NVIDIA drivers for your GPU installed* Docker is set to run in privileged mode, it is required for overclocking and for setting the drivers in persistence mode. GPU with at least 5GB memory or more (current requirement is above 4,2GB). *) Verified working Nvidia driver: v460.73.01 (Production Branch) - v465.X does not allow for overclocks with Unraid/docker combo for unknown reasons. Installation Install this docker container using CA (Community Applications), search for NsfminerOC and install! Configuration Variable Default Value Description ------------------------------------------------------------------------------------------- NSFMINER_GPU 0 Set GPU ID to use (open terminal and check "nvidia-smi") NSFMINER_GPUPOWERLIMIT 150 Set power limit for GPU in Watt (set this as low as you can with highest possible hashrates) NSFMINER_POWERMIZER 2 Set PowerMizer performance level (0=adaptive, 1=max performance, 2=auto) NSFMINER_GPUGFXCLOCKOFFSET 0 Set GPU graphics clock offset (under- or overclock your GPU in MHz offset) NSFMINER_GPUMEMCLOCKOFFSET 0 Set GPU memory clock offset (overclock your memory in MHz, NB! often these values are the double of what they are shown as in Windows so just crank it up!) NSFMINER_HWMON 2 Set Feedback level from nsfminer (feedback from the miner, 0=off, 1=temp+fan, 2=temp+fan+power) NSFMINER_TRANSPORT stratum1+ssl Set transport for worker NSFMINER_ETHADDRESS 0x516eaf4546BBeA271d05A3E883Bd2a11730Ef97b Set your worker ethereum address (or mine an hour or so for me if you wanna support my docker work ;) NSFMINER_WORKERNAME unraid-worker Set a worker name NSFMINER_ADDRESS1 eu1.ethermine.org Set address 1 for worker, both must be set NSFMINER_ADDRESS2 us1.ethermine.org Set address 2 for worker, both must be set NSFMINER_PORT1 5555 Set port for address 1 NSFMINER_PORT2 5555 Set port for address 2 NSFMINER_GPUFANCONTROLL 0 Set GPU fan controll, 0 will run auto and other fan settings are ignored. GPU MUST have exactly 2 fan controllers available, else this container will fail if this is used. NSFMINER_GPUFAN1 0 Set the FAN ID 1 of GPU (check fan ID with "nvidia-settings -q fans" in terminal) NSFMINER_GPUFANSPEED1 100 Set the speed in percent of FAN ID 1 NSFMINER_GPUFAN2 1 Set the FAN ID 2 of GPU (check fan ID with "nvidia-settings -q fans" in terminal) NSFMINER_GPUFANSPEED2 100 Set the speed in percent of FAN ID 2 Running View the logs for worker output Overclocking example Some cards will report that they are read-only when trying to overclock them, such as Quadro cards. This is normal behavior as they are factory locked. For on-demand overclocking, open the "Logs" to check the hashrates when the docker container is running. Then open "Console" to enter in tuning data manually to figure out the optimized mining values for your card. When all values are found, store them in the variables in the docker container edit in Unraid. The GPU ID is set to "0", adjust yours accordingly. The examples below is set for a GTX 1070. Set the PowerMizer mode to 0=adaptive, 1=max performance, 2=auto nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1 Adjust the GPU Graphics clock offset on all performance levels, crank it up until it starts giving errors and then back up. If you are on a 3000-series card, you might want to underclock this one instead and save the power consumption (check example settings for other cards below). nvidia-settings -a [gpu:0]/GPUGraphicsClockOffsetAllPerformanceLevels=200 Adjust the GPU Memory clock offset, crank this one up until it gives errors, crashes or decreases in hashrates, then back it up to a stable value. nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffsetAllPerformanceLevels=800 Finally, adjust the power limit. Decrease this as much as possible until you hit a target where the hashrates fall. Optimally calculate how much power vs. hashrates you can squeeze out. Sometimes some fine tuning with less or more clocks and power draw can give you better profit. Slightly less hashrates with less power draw might be better profit! nvidia-smi -i 0 -pl 135 Other GPU value examples GPU PowerMizer GPU GFX GPU MEM Power limit Hashrates (~) Effective Score -------------------------------------------------------------------------------------------------- RTX 3080 1 (-300)-(-200) 2300-2500 230-235 97.0-98.5 MH/s 0,421-0,419 * RTX 3070 1 (-600)-(-550) 2300-2400 130-135 60.0-60.2 MH/s 0,462-0,446 * GTX 1070 Stock 1 200 800 135 28 MH/s 0,207 GTX 1070 OC 1 100 400 135 28 MH/s 0,207 Quadro P2000 1 0 0 65 15.6 MH/s 0,24 Some cards might have higher factory clocks in VBIOS like these GTX 1070 GPU's. One of these cards is an OC optimized VBIOS/card, the other one just a standard VBIOS/card with less cooling. The target to reach the hashrates might vary, don't use this table for your own input, this is just an example and might be slightly used for a reference of where it should be. The values might need slight tuning after a while as it might wear out the real top performance of the memory chips, or the ambient temperature simply rises etc. *) The effective score of the RTX 3000 cards shows that it might even be better to run at slightly lower hashrates and power limit, than trying to boost it all up, even with just 5 watts. Fan curves You can also play around with the fan curves, setting it low to reduce the noise can also impact the hashrates. But maybe you want to duplicate your docker container for a "optimized run mode" and a "night mode". Adjusting fan curves might require 2 fan controllers on the graphics card, if the docker container fails and the GPU has only one controller, use "auto" setting (default). Adjust fan controller, 0=auto, 1=manual nvidia-settings -a [gpu:0]/GPUFanControlState=1 Adjust speed for fan 1 (same procedure for fan 2, just replace the number with another fan ID), value in %: nvidia-settings -a [fan:0]/GPUTargetFanSpeed=80 Setting up multiple cards/containers root@Odin:~# nvidia-smi Tue Apr 6 15:06:36 2021 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 460.67 Driver Version: 460.67 CUDA Version: 11.2 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| ID -> | 0 GeForce GTX 1070 On | 00000000:04:00.0 Off | N/A | | 51% 76C P2 135W / 135W | 4631MiB / 8119MiB | 100% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ ID -> | 1 Quadro P2000 On | 00000000:83:00.0 Off | N/A | | 92% 81C P0 65W / 75W | 4862MiB / 5059MiB | 100% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ ... The output of "nvidia-smi" in the terminal will show you each GPU ID, this ID you enter under NSFMINER_GPU variable. If you have multiple GPU's: Install first the NsfminerOC container via CA. Configure the first NsfminerOC Click "Add container" and select one of your NsfminerOC templates Configure your second container Repeat steps 1-4 for third, fourth etc...
    1 point
  8. Hi, I'm having problem with the 6.9 version of Unraid. The server freezes at random times, and can only be fixed by doing a hard reset on the server itself. It does not respond to ping when it has freezed. It happened a few days after I upgraded, then it ran for around 2 weeks before freezing again. Yesterday it froze again, restarted it and now it freezed again around 15 minutes ago. I did not have these problem with 6.8 and has not changed anything in the setup. I tried to check the log files but it seems like it was reset when server was rebooted again. Is there any way seeing what happened from the diagnostic file? Anyone has any idea of what's causing this? Thanks! unraid-diagnostics-20210329-1011.zip
    1 point
  9. OK..... problem solved i believe. So i got a message from my ISP last week that they were doing maintenance to the entire township and i was included in that. What i didnt know is that my IP address changed 😆. Steam seems to be able to see it both ways now. I will have a friend try to connect and see what happens
    1 point
  10. Need to run to get the image name that the container is using and find out where the image is coming from and what it is.
    1 point
  11. The mce's are somewhat common when the system initializes the cores and affects certain hardware combinations for some reason, and can be safely ignored.
    1 point
  12. Thanks again, Jorge! Have had a few other things to deal with, and being away for a little while, but working on it slowly here and there. Looks like I've at least got the server array back up and running along with my docker services, etc. The NVMe shows up in the unassigned devices as I removed it from the cache pool for the moment while doing some clean up and reworking. So I think I'm back in a good spot to continue with everything. Thanks again! Considering this solved for now!
    1 point
  13. Yes. That is planned for a future update.
    1 point
  14. There is an interesting kernel bug fix, which looks like our case https://lkml.org/lkml/2021/3/29/499 I don't know if this already available in a linux version for Unraid, perhaps @limetech can tell?
    1 point
  15. v0.3 ist fertig. Jetzt kann man IP-Bereiche freischalten, die Dateien enden auf .ip und der Firewall-Code steht nun ganz oben in der .htaccess.
    1 point
  16. @bonienl There are lots of mover failure messages in this syslog: syslog.txt.zip
    1 point
  17. Yes. IIRC It's been quite a while since I've looked at this. The not displaying only really affects HOST / Custom networks.
    1 point
  18. This setting restricts management access to interface eth0 only, still this interface needs connectivity as before to do upgrades and plugin/docker installations.
    1 point
  19. Aber wenn du mit dem parameter "-allow_psid_change" hat es funktioniert oder? Überleg dir auch ob du das BIOS der Karte entfernst wenn du den Netzwerkboot nicht brauchst usw, sieht dann so aus: Sollte bei dir mit diesem Befehl funktionieren: mstflint -d 01:00.0 --allow_rom_change drom
    1 point
  20. Meine Karte war / ist IBM gebrandet Die original FW von Mellanox ließ sich nicht aufspielen. Hab das Ganze jetzt mit einem Crossflash gelöst, so dass ich die aktuellste Mellanox-FW aufspielen konnte und nicht auf die ältere IBM-FW greifen musste: root@Filer:/tmp/mellanox# mstflint -d 01:00.0 query full > flint_query.txt root@Filer:/tmp/mellanox# mstflint -d 01:00.0 hw query > flint_hwinfo.txt root@Filer:/tmp/mellanox# mstflint -d 01:00.0 ri orig_firmware.bin root@Filer:/tmp/mellanox# mstflint -d 01:00.0 dc orig_firmware.ini root@Filer:/tmp/mellanox# mstflint -d 01:00.0 rrom orig_rom.bin root@Filer:/tmp/mellanox# mstvpd -m 01:00.0 > orig_vpd.txt root@Filer:/tmp/mellanox# mstflint -d 01:00.0 -i fw_2.bin -allow_psid_change burn Current FW version on flash: 2.35.5100 New FW version: 2.42.5000 You are about to replace current PSID on flash - "IBM1080110023" with a different PSID - "MT_1080120023". Note: It is highly recommended not to change the PSID. Do you want to continue ? (y/n) [n] : y Burning FS2 FW image without signatures - OK Restoring signature - OK Resultat:
    1 point
  21. Thank you for your help, that worked perfectly.Server booted with the GUI first try.
    1 point
  22. Also brauchst du einen Slot für eine GPU? Weil dein Board hat ja 2x x8 und 3x x1 (der x4 ist bereits aus, wenn du eine zweite M.2 installierst): Vom Prinzip sollte das aber gehen. Du wirfst die Delock-Karte weg und steckst die zwei ASM1166 Karten einfach in die x1 Slots und verbindest aber jeweils nur 4 HDDs. Ein x1 Slot hat 1 GB/s Bandbreite, also ausreichend für 4x 250 MB/s. Plus die 6 SATA Ports auf dem Board macht das 14 HDDs. Reicht das? Ansonsten noch eine dritte Karte in den dritten x1 Slot oder eben in einen x8 Slot. Der Chipsatz ist übrigens über x4 mit der CPU verbunden. Daher ist das mit den drei M.2 eh so eine Sache (die ja alle mit dem Chipsatz verbunden sind). Wenn du jetzt 14 HDDs im Parity Check hättest und die würden mit 250 MB/s laufen, dann würden die schon 3,5 GB/s nutzen und x4 hat in Summe nur 4 GB/s. Da bleibt natürlich wenig Bandbreite für die ganzen M.2 übrig. Aber in der Regel macht man ja keinen Parity-Check während man die M.2 voll auslasten möchte. Also das nur als Info. Dein Board unterstützt laut Anleitung übrigens auf PCIe x16_2 so einen Adapter: https://www.supermicro.com/en/products/accessories/addon/AOC-SLG3-2M2.php Man könnte es also auch so machen: GPU in x8 Slot 2x M.2 über Adapter in x8 Slot ASM1166 in x4 Slot mit 6 HDDs ASM1166 in x1 Slot mit 4 HDDs 6 HDDs über Onboard-SATA Dann wäre man bei 16 HDDs und zwei x1 Slots und ein M.2 Slot wären sogar noch übrig und es gäbe keinerlei Flaschenhals, da die beiden M.2 direkt über die CPU laufen.
    1 point
  23. okay have fix that, think there is something corrupt inside the docker.img? Is that loop3? as you stated. I will try re-create it.. hope my plex files are gucci I get a tone of errors of this nature when starting plex Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 654, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 655, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 656, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 657, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 658, gen 0 After docker.img rebuild, plex is gucci again... thanks so much for you help @JorgeB
    1 point
  24. This won't help, if there are uncorrectable errors the corrupt file(s) will be listed in the syslog, you'll need to delete them or restore from backups.
    1 point
  25. So, after limiting the Docker RAM allocation to 4GB, I tried to log into my Docker this morning and it threw up a web socket error, then a weird 404 (404 was written in red inside the interface, not an actual 404 from the browser). Looking at the usage, it was up hard against 4GB RAM. So I had to restart it. As per recommendations in this topic, I've now disabled DPI as it was only a mildly useful feature for me, anyhow. I really don't see how constantly growing RAM usage is acceptable. And given the constant complaints on the forum about v6.x, I've grown to regret forking out the money for the USG to replace my EdgerouterX. Every single feature that it brought into the Unifi interface has been a worse experience than on the EdgerouterX, and it offers absolutely no benefit (I have a 500Mbps connection, so it's not fast enough to handle threat protection (which I only found out AFTER I bought it) and the in-built speed test can't handle an internet connection of that speed, either). So yeah, not feelin' the love for Ubiquiti right now. Which sucks, coz the WiFi hardware has been great - fast and reliable (except for the problem with Chromecasts introduced in a fw update and promptly fixed). But the Controller... just terrible. I hope that, by the time v7 rolls around, Unifi Controller will be a fully fleshed out, reliable, usable product.
    1 point
  26. This is usually the result of a device dropping offline, see below for more info: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582 That's what likely caused the issues with loop3, which is the docker image and should now be recreated.
    1 point
  27. Wenn du keinen ECC RAM benötigst, gibt es ja viel Auswahl. Zb das ASRock B365 Pro4 kombiniert mit einem Pentium Gold G5400? Kommt auch drauf an wie viel Leistung du benötigst. Oder ein neueres Board wo direkt auch 2.5G LAN dabei ist und 8 SATA Ports wie das Gigabyte W480M Vision, kombiniert mit einem G6400. Das Board ist allerdings deutlich teurer.
    1 point
  28. I had the same issue. Try replacing repository with olehj/docker-nsfmineroc:latest
    1 point
  29. I'll keep you updated. It has been stable since the downgrade yesterday at least.
    1 point
  30. Have you tried it without the Mover Tuning plugin installed?
    1 point
  31. Back about ten years ago, I decided I had a storage space problem. So I looked around to see what was available. I don't remember what was around at the time but I came across the unRAID product. So you load something on an USB and then boot to it and it then sees all the attached drives. Create shares, add data and you're good. It has data recovery as well in case of drive failure. Sounded pretty much agnostic as far as motherboard hardware was concerned. Interesting concept. And an online community with all kinds of info. Like any IT guy with 20+ years of hardware experience I had accumulated assorted old/unused small drives and out of date motherboards. Let me slap together something as a proof of concept thing real quick and see what happens. This was just as SATA was coming out. But my old boards only had IDE Master/Slave stuff. It was just stuff I had laying around. Got four assorted drives of unknown heritage from the junk box and stuffed them into an old case. Made the bootable USB and fired the whole mess up. Got the web console up and poked around. Yea, all the drives were listed. OK, biggest drive will be parity and the assorted leftovers will be drive space. I liked that idea because you could use what you had on hand, they didn't need to be the same size. Probably had a total of less than one TB of drive space scattered across the entire box. UnRAID got done prepping all the space and I set up some shares and copied test files to them. That was pretty straight forward. So I let it run a few days as I went on to other stuff in life. I brought the console up a few days later and saw that I had a drive failure. The drives did come from the junk box so that was sorta expected. Ok, let's see how this data protection things works. The shares were still there and so was the data. The parity drive was doing it's job. Nice. That's working as advertised. Almost got me sold at this point. Back to the online community and the assorted FAQ's. How do you recover the drive/data? Shut down, pull bad drive and insert another drive of same or larger size. Click a few buttons and the system kicks in and the data recovery begins and then new drive is repopulated with data. Only downtime was swapping out hardware. From the user point of view I couldn't tell anything was going on in the background as the data was being recovered. Ok, I'm sold. Take my money now. Bought a couple keys and a pair of USB drives in September of 2011. Don't remember for sure but I think they had a sale or something going at the time. I'm on my second specially built production server now. Got the second USB on the test box. it's just just an old desktop stuffed with the smaller drives I have pulled from the production box as I upsize it. 23 TB scattered across 8 drives with Plex running on the SSD. Yes, I'm happy with the product.
    1 point
  32. The error 43 is the exact driver shenanigans they pull with video cards, but with virtual functions its unfortunately even more difficult to get around. A couple things you can try: * instead of running the full installer, open the executable (.exe installer) with 7zip or the like, and manually install the drivers for your OS (using the .inf files) * test against a different version of windows 10 to verify whether its locked to a specific build type (education, pro, pro for workstation, or an enterprise LTS build) * read through the release notes for earlier driver versions in order to find one that has the best chances for success; 2017 or earlier is likely your best bet in my experience - note, this may require a firmware downgrade of your card, which I've very limited personal experience with
    1 point
  33. Not necessarily. There are still many good uses for unassigned devices: Plug in an external USB drive and backup share data to it automatically via a UD script Use a USB device as a location for the syslog A UD for VMs is still preferred by some A UD as a download, personal cloud data, transcode or media conversion location may still be preferable in some cases over a cache pool Unassigned Devices supports formats such as NTFS which allow these devices to read in Windows outside the array.
    1 point
  34. Post it here, if you feel like editing it you can delete it later. Trust me, you are not the dumbest person on this forum.
    1 point
  35. I was having issues getting ProFTP running again after upgrading Unraid to version 6.9.1 using ProFTP 1.3.7a. ProFTP just would not start and I could not get anything in the log. I tried enabling debug logging, but still nothing. I removed the plugin and did a clean install multiple times and still nothing. Then I stumbled upon running this command in terminal sudo -u root /usr/local/SlrG-Common/usr/local/sbin/proftpd -c /etc/proftpd.conf which resulted in this error: 2021-03-30 20:12:19,459 TOWER proftpd[24730]: fatal: unknown configuration directive 'IdentLookups' on line 24 of '/etc/proftpd.conf' So looking at the config file I removed this section at lines 22-24: # Speedup Login UseReverseDNS off IdentLookups off Tehn ProFTP started without any issues.
    1 point
  36. If you want it as a separate module, you need to specify export CONFIG_TLS_DEVICE=m When you specify it as "y", it is compiled into the kernel (becomes part of it).
    1 point
  37. I am making my final update to this thread because I finally solved this problem. The solution was to return my Asmedia SATA Controller card back to Amazon and get the one shown in the link below: https://www.youtube.com/watch?v=UlVk1Bwkh-Q&t=3s Boxed in YELLOW below are my optical drives shown in the System Devices page in the UnRaid OS. I was not getting the results shown below with the Asmedia card. But this new MZHOU PCIe SATA Card recognizes my cd/dvd optical drives. And I am sure once I setup my Linux Mint VM these optical drives will appear on my Linux Mint desktop. So my advice is you don't waste your time buying an Asmedia card and instead get the MZHOU PCIe SATA Card I got if you need support for optical drives.
    1 point
  38. My best for a Linux machine was 4years. We moved and I thought it was safer for me to shut it all down than to carry the UPS and pray the drive didn't get bumped in the back of my car for the 15minute drive. lol
    1 point
  39. Maximum size limits on shares. That way i can partition X TB on a single large disk and set the samba settings so only certain users can access Y TB of it. This is nice so i can use something like a single 12TB disk and give 3TB to everyone in the household to use exclusively so no one goes over their quota. Also big +1 to user groups with folder/share permissions
    1 point
  40. Actually the devs can do something about it I made a correction to not flag mover messages.
    1 point
  41. The first one failed to mount but the second one did and I was able to recover about 50GB of appdata and the docker.img. Thanks for all of your help!
    1 point
  42. Are you getting errors, or is it converting files? Just because you have hardware acceleration enabled, does not mean the CPU will not be used. The CPU is still used for decoding, audio encoding and remixing. If the task is only those, then it will use 100% CPU. Sent from my Mi MIX 2 using Tapatalk
    1 point
  43. 1 point
  44. Most people think "bitrot" refers to flaws in the physical storage media developing over time, such that data written to a storage block at time 0 is not the same data that is read at time 1, and this fact goes undetected. Indeed storage media does degrade over time, however, storage media devices also incorporate powerful error detection and correction circuitry. This makes it mathematically impossible for errors due to degrading media to NOT be detected and then not reported as "unrecoverable media error", unless there is a firmware error or other physical defect in the device. In virtually all h/w platforms, all physical data paths are protected by some kind of error detection scheme. For example, if a DMA operation is initiated to read data from RAM and write to a storage controller over PCI bus, all the various data paths are protected with extra check bits, either in parallel with parallel data paths, or using checksums. This means (again barring firmware errors), random bit errors in data leaving memory and arriving at the storage end up getting detected before ever being written to the media. There is ONE subsystem in modern PC computer systems that is typically not protected however: system RAM. If you have a file in RAM and along comes a random alpha particle (for example) and flips a bit, nothing detects this - in btrfs or zfs (for example) the s/w happily calculates an (incorrect) checksum and the h/w happily writes it all the way to the media. Until one day you read the file and see corruption and say, "Damn you crappy storage device, you have bitrot!", when all along it was written that way. If you really care about flawless storage, and indeed better system in general, you must use ECC RAM for starters. Also use quality components everywhere else, especially PSU. That will be your best defense against "bitrot".
    1 point
  45. Just one quibble, the parity drive does not have a format, so don't bother trying. It's going to be *completely* overwritten.
    1 point
  46. Yes, doing a new config keeps all data intact, unless a data disk is assigned to a parity slot by mistake.
    1 point
  47. You could use unraid as your cell phone! But really, it's more of a "cause I can" thing. My end goal is to get Android TV working in a VM with GPU passthrough so I don't need to buy a physical Android TV. As much as I like Kodi, the lack of official apps for it like Netflix and HBO GO/Now, really kill the WAF. Having an Android TV with native apps for those services, plus Emby as my personal media hub and live tv would finally provide me an all-in-one front end for media conception in front of the TV. So I used Android Lollipop as a jumping off point since that seemed the easiest to prove it could work, and I'll go from there trying to get Android TV to work.
    1 point