Leaderboard

Popular Content

Showing content with the highest reputation on 09/14/22 in all areas

  1. Version 6.11.0-rc5 2022-09-12 Bug fixes Ignore "ERROR:" strings mixed in "btrfs filesystem show" command output. This solves problem where libblkid could tag a parity disk as having btrfs file system because the place it looks for the "magic number" happens to matches btrfs. Subsequent "btrfs fi" commands will attempt to read btrfs metadata from this device which fails because there really is not a btrfs filesystem there. Base distro: cracklib: version 2.9.8 curl: version 7.85.0 ethtool: version 5.19 fuse3: version 3.12.0 gawk: version 5.2.0 git: version 2.37.3 glibc-zoneinfo: version 2022c grep: version 3.8 hdparm: version 9.65 krb5: version 1.19.3 libXau: version 1.0.10 libXfont2: version 2.0.6 libXft: version 2.3.6 libdrm: version 2.4.113 libfontenc: version 1.1.6 libglvnd: version 1.5.0 libssh: version 0.10.4 libtasn1: version 4.19.0 mcelog: version 189 nghttp2: version 1.49.0 pkgtools: version 15.1 rsync: version 3.2.6 samba: version 4.16.5 sqlite: version 3.39.3 Linux kernel: version 5.19.7 CONFIG_BPF_UNPRIV_DEFAULT_OFF: Disable unprivileged BPF by default CONFIG_SFC_SIENA: Solarflare SFC9000 support CONFIG_SFC_SIENA_MCDI_LOGGING: Solarflare SFC9000-family MCDI logging support CONFIG_SFC_SIENA_MCDI_MON: Solarflare SFC9000-family hwmon support CONFIG_SFC_SIENA_SRIOV: Solarflare SFC9000-family SR-IOV support patch: quirk for Team Group MP33 M.2 2280 1TB NVMe (globally duplicate IDs for nsid) turn on all IPv6 kernel options CONFIG_INET6_* CONFIG_IPV6_* Management: SMB: remove NTLMv1 support since removed from Linux kernel startup: Prevent installing downgraded versions of packaages which might exist in /boot/extra webgui: VM Manager: Add boot order to GUI and CD hot plug function webgui: Docker Manager: add ability to specify shell with container label. webgui: fix: Discord notification agent url webgui: Suppress info icon in banner message when no info is available webgui: Add Spindown message and use -n for identity if scsi drive. webgui: Fix SAS Selftest webgui: Fix plugin multi updates
    5 points
  2. Starting with 6.11.0-rc5 we have added some features to help us figure out the proper mix of SMB settings which will achieve the best performance/functionality with MacOS. This mainly involves tuning the so-called "fruit" SMB parameters. Please refer to the Samba "vfs_fruit" doc: https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html First you will notice there are Global options and Per-Share options. The global options are set in /etc/samba/smb.conf file on your server. All the options are listed near the bottom, and ones which vary from the default setting are uncommented. I don't think we will need to change these options but if you want to experiment then add your changes to /boot/config/smb-extra.conf file. Next are the set of per-share options. These are set in /etc/samba/smb-fruit.conf file on your server. Again all options are listed there and only the ones which deviate from default are uncommented. In addition, you may create the file /boot/config/smb-fruit.conf on your flash device and when Samba starts or is restarted, those options will override the options in /etc/samba/smb-fruit.conf. Thus a good staring point would be to: cp /etc/samba/smb-fruit.conf /boot/config and now you can make changes to /boot/config/smb-fruit.conf After making a change you can type this command to to restart Samba: samba restart For any of this to be applied, you first need to ensure that "Settings/SMB/Enhanced macOS interoperability" is set to Yes. This will tell Unraid OS to include the contents of the smb-fruit.conf file in each share (except for the 'flash' share, see below). Note: we actually have per-share hidden settings for enabling 'fruit', however from the documentation we read: Thus there is no UI for these settings, instead either all shares or no shares have 'fruit' extensions. As for the 'flash' share, again from the doc we read: (emphasis mine). They say 'streams_xattr' must be loaded, but later in the doc they talk about options that are incompatible with this. In addition certain file system types are inherently incompatible, notably FAT and exFAT because they don't support xattr at all... Hence we can't (or shouldn't) include the 'flash' share in 'fruit' but then if the 'flash' share is first share to be accessed on a Mac client, APPL extensions will be disabled for the duration... Yes this is confusing, maybe best bet is to not export the 'flash' share in MacOS environment. If it is exported, the 'testparm' command outputs this warning: WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients results in undefined behaviour. Time machine - if enabled for a share these parameters are automatically added (independent of smb-fruit.conf): fruit:time machine = yes fruit:time machine max size = SIZE # if "vol size limit" specified Finally Spotlight - our build of Samba includes spotlight support but only for 'elasticsearch'. But 'elasticsearch' is not installed in Unraid OS. In other places on the forum people have expressed success by setting the spotlight backend to 'tracker' - but this requires "gnone tracker" which also is not installed in Unraid OS - so I'm not sure what's going on here. Nevertheless, you can add 'spotlight = on' to the smb-fruit.conf file to play around with this. Please limit discussion in this topic to MacOS issues only.
    4 points
  3. Hi folks, shortly after Unraid 6.11 stable is released we plan to drop support for some of the older versions of Unraid. My Servers is pushing the evolution of Unraid, and we can't maintain backward compatibility with these older versions long term. We recommend that you update to the current version of Unraid: It is a good idea to read the release notes so you know what has changed: https://wiki.unraid.net/Manual/Release_Notes Backup your flash drive from Main -> Boot Device -> Flash -> Flash Backup Navigate to Tools -> Update OS. Depending on your settings you may need to press "Check for updates" Reboot when prompted If you have support questions about the new version post your diagnostics.zip file (from Tools -> Diagnostics) and a detailed description of the problem to a new support thread here https://forums.unraid.net/forum/55-general-support/ My Servers will continue to support these versions of Unraid for now: 6.10.0 - 6.10.2 (although we recommend 6.10.3 or 6.11.5) 6.10.3 (although we recommend 6.11.5) 6.11.0 - 6.11.4 (although we recommend 6.11.5) 6.11.5 Note that RC releases are not meant to be run long-term, so if you are still on an older RC version, you'll want to update as well. My Servers will specifically be dropping support for these versions of Unraid in the coming weeks, please update before that happens: 6.9.0 6.9.1 6.9.2 6.10.0-rc[x] 6.10.1-rc[x] 6.10.2-rc[x] 6.11.0-rc[x] 6.11.1-rc[x] My Servers has dropped support for these versions of Unraid: 6.9.0-rc[x] If you are unable to upgrade, please point me to your forum thread discussing the issue. Thanks!
    3 points
  4. @ich777 大佬帮忙做了r8125和r8152, r8168网卡的Unraid v6.11.5以上的plugin. R8125 和 R8156的驱动都可以在应用市场搜索到了。 各位可以不用下面的补丁了,重复的,建议多用plugin,除非有IOMMU的需求再用下面的补丁。 ------------------------------------------------------------------------------------------------------------------------------------------------------------ Unraid貌似用了r8169这个驱动来驱r8125,比较老。r8152也是很老的1.12版本,好像驱不动R8156。 以下补丁基于Unraid原版定制,加了最新的V9.012.04的r8125 2.5G PCI网卡驱动和V2.17.1的r8156 2.5G USB 网卡驱动。解压后把所有文件覆盖到U盘根目录重启即可。覆盖前记得备份原始文件。 默认自带r8169的驱动,支持板载网卡r8169和USB网卡r8156共存的情况。 如果不需要r8169,需要r8125 PCI网卡的驱动,可以靠如下blacklist屏蔽掉。命令行跑一次,会存到U盘,重启试试。 从6.12.5开始, cdc_ncm会影响r8156驱动,也需要屏蔽掉,r8156才能正常工作。 echo "blacklist r8169" > /boot/config/modprobe.d/r8169.conf echo "blacklist cdc_ncm" > /boot/config/modprobe.d/cdc_ncm.conf 如果想去掉blacklist,去U盘里面删掉上面的这些文件 /config/modprobe.d/*.conf ,重启就行了。 原生Unraid内核之外的补丁修改部分: 1. 修改了ACS Override补丁,支持某些主板的IOMMU分组补丁。 2. 增加R8125驱动,修改打开了队列支持和关闭了ASPM节能。 3. 增加R8156驱动,修改了支持最新的Unraid的Linux6.1内核。 4. 增加R8168/8111驱动,修改了支持最新的Unraid的Linux6.1内核。 只是供测试,如果感觉不稳定,用原始文件覆盖回来,重启就能恢复原状了。 免责声明: 补丁只是用于测试,请勿使用于重要的数据服务器,如果出现数据丢失等情况概不负责。谢谢。 下载链接在: 链接: https://pan.baidu.com/s/1987agT_JHTv6QT3ds1olqg?pwd=zapu Mirror (Google Drive): https://drive.google.com/drive/folders/1wA9UNejVllZfBTjDQ-pquJ-Bx4Tlqluk?usp=sharing 里面还有Unraid老版本的补丁,都是加了类似的驱动。有兴趣也可以使用。6.12之前补丁都没有R8168驱动。 已知问题1: Unraid内部似乎加了些版本检查的限制,新版本的补丁无法新建队列配置文件,会出现Stale Configuration的提示。有个妥协的办法就是先在原始文件里面将阵列启动好,生成阵列配置文件之后,再替换补丁重启。除非换硬盘,一般阵列配置也不会重新配置。 已知问题2: 某些r8125网卡在Unraid的共享目录拷贝速度跑不满280MB,只有140MB左右,可能跟主板设计或配置或桥接有关。有网友发现关掉Unraid网络配置的br0桥接,使用macvtap,可以跑满速度。推荐使用这种办法,虽然麻烦一些,但是速度确实不受影响了。 例如虚拟群晖,推荐第一个macvtap网卡使用群辉的MAC地址,第二个网卡随意MAC地址,参考本帖第三页 @benwwchen 网友的帖子。
    1 point
  5. ***Update*** : Apologies, it seems like there was an update to the Unraid forums which removed the carriage returns in my code blocks. This was causing people to get errors when typing commands verbatim. I've fixed the code blocks below and all should be Plexing perfectly now Y =========== Granted this has been covered in a few other posts but I just wanted to have it with a little bit of layout and structure. Special thanks to [mention=9167]Hoopster[/mention] whose post(s) I took this from. What is Plex Hardware Acceleration? When streaming media from Plex, a few things are happening. Plex will check against the device trying to play the media: Media is stored in a compatible file container Media is encoded in a compatible bitrate Media is encoded with compatible codecs Media is a compatible resolution Bandwith is sufficient If all of the above is met, Plex will Direct Play or send the media directly to the client without being changed. This is great in most cases as there will be very little if any overhead on your CPU. This should be okay in most cases, but you may be accessing Plex remotely or on a device that is having difficulty with the source media. You could either manually convert each file or get Plex to transcode the file on the fly into another format to be played. A simple example: Your source file is stored in 1080p. You're away from home and you have a crappy internet connection. Playing the file in 1080p is taking up too much bandwith so to get a better experience you can watch your media in glorious 240p without stuttering / buffering on your little mobile device by getting Plex to transcode the file first. This is because a 240p file will require considerably less bandwith compared to a 1080p file. The issue is that depending on which format your transcoding from and to, this can absolutely pin all your CPU cores at 100% which means you're gonna have a bad time. Fortunately Intel CPUs have a little thing called Quick Sync which is their native hardware encoding and decoding core. This can dramatically reduce the CPU overhead required for transcoding and Plex can leverage this using their Hardware Acceleration feature. How Do I Know If I'm Transcoding? You're able to see how media is being served by playing a first something on a device. Log into Plex and go to Settings > Status > Now Playing As you can see this file is being direct played, so there's no transcoding happening. If you see (throttled) it's a good sign. It just means is that your Plex Media Server is able to perform the transcode faster than is necessary. To initiate some transcoding, go to where your media is playing. Click on Settings > Quality > Show All > Choose a Quality that isn't the Default one If you head back to the Now Playing section in Plex you will see that the stream is now being Transcoded. I have Quick Sync enabled hence the "(hw)" which stands for, you guessed it, Hardware. "(hw)" will not be shown if Quick Sync isn't being used in transcoding. PreRequisites 1. A Plex Pass - If you require Plex Hardware Acceleration Test to see if your system is capable before buying a Plex Pass. 2. Intel CPU that has Quick Sync Capability - Search for your CPU using Intel ARK 3. Compatible Motherboard You will need to enable iGPU on your motherboard BIOS In some cases this may require you to have the HDMI output plugged in and connected to a monitor in order for it to be active. If you find that this is the case on your setup you can buy a dummy HDMI doo-dad that tricks your unRAID box into thinking that something is plugged in. Some machines like the HP MicroServer Gen8 have iLO / IPMI which allows the server to be monitored / managed remotely. Unfortunately this means that the server has 2 GPUs and ALL GPU output from the server passed through the ancient Matrox GPU. So as far as any OS is concerned even though the Intel CPU supports Quick Sync, the Matrox one doesn't. =/ you'd have better luck using the new unRAID Nvidia Plugin. Check Your Setup If your config meets all of the above requirements, give these commands a shot, you should know straight away if you can use Hardware Acceleration. Login to your unRAID box using the GUI and open a terminal window. Or SSH into your box if that's your thing. Type: cd /dev/dri ls If you see an output like the one above your unRAID box has its Quick Sync enabled. The two items were interested in specifically are card0 and renderD128. If you can't see it not to worry type this: modprobe i915 There should be no return or errors in the output. Now again run: cd /dev/dri ls You should see the expected items ie. card0 and renderD128 Give your Container Access Lastly we need to give our container access to the Quick Sync device. I am going to passively aggressively mention that they are indeed called containers and not dockers. Dockers are manufacturers of boots and pants company and have nothing to do with virtualization or software development, yet. Okay rant over. We need to do this because the Docker host and its underlying containers don't have access to anything on unRAID unless you give it to them. This is done via Paths, Ports, Variables, Labels or in this case Devices. We want to provide our Plex container with access to one of the devices on our unRAID box. We need to change the relevant permissions on our Quick Sync Device which we do by typing into the terminal window: chmod -R 777 /dev/dri Once that's done Head over to the Docker Tab, click on the your Plex container. Scroll to the bottom click on Add another Path, Port, Variable Select Device from the drop down Enter the following: Name: /dev/dri Value: /dev/dri Click Save followed by Apply. Log Back into Plex and navigate to Settings > Transcoder. Click on the button to SHOW ADVANCED Enable "Use hardware acceleration where available". You can now do the same test we did above by playing a stream, changing it's Quality to something that isn't its original format and Checking the Now Playing section to see if Hardware Acceleration is enabled. If you see "(hw)" congrats! You're using Quick Sync and Hardware acceleration [emoji4] Persist your config On Reboot unRAID will not run those commands again unless we put it in our go file. So when ready type into terminal: nano /boot/config/go Add the following lines to the bottom of the go file modprobe i915 chmod -R 777 /dev/dri Press Ctrl X, followed by Y to save your go file. And you should be golden!
    1 point
  6. Hello, Comme certain utilisateurs d'unRaid je suis en train de me faire une VM Gaming. Vu le peut de ressource en français sur le sujet je fais ce topic afin de partager mon expérience. Mon serveur est dans mon garage, je compte y jouer via parsec/moonlight/etc depuis principalement mon réseau local mais aussi pourquoi pas depuis Internet (je suis fibré), il faudra que je bench ces softs. Mes clients seront : * Mon Macbook pro de 13". * Un petit PC branché sur un écran 4k, un ASRock A300. * Et une nVidia Shield Pro branché sur ma TV. Pour ma part j'ai donc paramétré une VM Windows 11 : * RAM : 16Go, mon serveur en compte 64, je suis donc large. * CPU Mode : Accès Direct. * CPU : j'ai isolé 4C/8T de mon 5800X et les ai assigné à la VM. * Modèle de machine : Q35-6.2 : j'ai vu certains retours comme quoi le modèle i440fx était plus performant, mais j'ai aussi vu l'inverse, bref j'ai décidé de commencer comme ça. * BIOS : OVMF TPM, obligatoire pour le support de Windows 11 qui impose le TPM. * Hyper-V : Oui. * Contrôleur USB : 3.0, mais je n'ai aucun périphérique USB branché à passer à la VM donc je m'en fiche un peu. * Disque : J'ai configuré un disque NVME en passthrough directement sur la VM, donc pas de vdisk. C'est assez simple à faire, si ça intéresse des gents je décrirai comment faire. l'avantage c'est que les performances sont excellentes, pas loin du baremetal (= sans virtualisation). Pour l'histoire j'avais auparavant un vdisk sur un SSD et j'ai fait une migration sans réinstaller la VM (pareil je peux décrire comment on fait). Afin de diffuser une session il faut un écran branché sur la CG, comme je n'en ai pas, je vais utiliser cela : * Un dongle fake HDMI (https://www.amazon.fr/dp/B07YMTKJCR/ref=twister_B08GSQ8SSR?_encoding=UTF8&th=1) Il se branche sur un port HDMI de la CG et simule un écran, permettant ainsi d'établir une session que l'on peut ensuite diffuser. Sinon Parsec à une solution software avec un Fake Display Driver, mais je n'ai pas réussi à la faire marcher. Voilà j'attend maintenant que les prix des CGs baissent un peut pour chopper une RTX 3080. Elle sera en passthrough de la même manière que le disque NVME. Elle ne pourra pas servir à autre chose (un docker plex par exemple) à part si ça tourne sur la VM. Mais j'ai déjà une autre CG pour cela. En attendant je test un peut les softs pour me faire une idée. J'ai aussi fait quelques benchs sur la partie disque suite au passage d'un vdisk sur un SSD SATA à un passthrough d'un disque NVME. J'en ferais d'autre une fois que j'aurais une CG.
    1 point
  7. Upgrading to 6.X there's a mention in the release notes for CPU scaling configuration for Haswell and Ivy Bridge processors. http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6 More Tips CPU speed and power saving workaround The newer Linux kernels have automatic CPU frequency step down when more CPU speed is not needed, saving power and heat. But, if your CPU is an Intel Haswell or possibly an Ivy Bridge, including most Xeon's, then there is a frequency scaling issue with the intel_pstate driver, and it needs to be disabled. It's nothing serious, just means the CPU won't power down to lower frequencies when idle, so you may pay a little more in power costs. It will not hurt you in any other way. To regain the CPU frequency stepping down, there are several things you can do. You can install the Tips and Tweaks plugin and change the CPU Scaling Governor. You can edit syslinux/syslinux.cfg on the flash drive, and insert intel_pstate=disable in the append lines. Easy way to edit syslinux.cfg - browse to your unRAID Main screen, click on your Flash drive, and drop down to the Syslinux Configuration section! Make sure you click on the Apply button. You will want to change these: append initrd=/bzroot append initrd=/bzroot unraidsafemode To these: append intel_pstate=disable initrd=/bzroot append intel_pstate=disable initrd=/bzroot unraidsafemode You can monitor the current CPU frequency for each core on the Dashboard. What's not stated in the first bullet is what selection to change the CPU Scaling Governor to? Choices are: OnDemand, PowerSave, Conservative, Performance, Scheduled. Which would be the correct selection for the intent?
    1 point
  8. Something seems wrong with some symbols in the module, have to look into this tomorrow, getting pretty late here... Will report back when I know more.
    1 point
  9. Hello again, I wrote https://github.com/qdm12/gluetun/discussions/1152 since I had a report from someone outside the Unraid ecosystem as well. TLDR: it's a false positive due to it being compiled from Go and doing a bunch of networking/system things (which also makes total sense if you don't know what Gluetun is made for).
    1 point
  10. Sep 14 15:32:35 Media-Server shfs: cache disk full On your Cache drive your need to adjust the Minimum Free Space because that monitors the entire drive not shares. Shares are drive level Disk1..Disk2 so on. In order to adjust this you need to do the following. 1. Stop your array 2. Click on your Cache drive 3. Set the minimum 4. Restart array I have mine set to 20GB, but I might need to adjust that since I sometimes have files that are sometimes a little larger, but luckily I haven't had any issues since my Mover normally catches it before its to late.
    1 point
  11. @derek_zoolander Is there a chance that there was never space set for Minimum on your Cache drive. Not the share, but the actual cache drive? I'm thinking that your SSD is simply full because you never set a Minimum on the drive its self.
    1 point
  12. My container was only designed to backup data to Mega or from Mega to a share.
    1 point
  13. Yes I was Ok so now it makes sense to me. Oh my god, I had no idea ! Thank you so much!
    1 point
  14. Since appdata is cache pool only instead of cache pool prefer, it can't overflow to the array when it runs up against the pool minimum free space. Click on the pool name "Cache" in your screenshot to see the minimum free space setting.
    1 point
  15. Upgraded to 7.2.94 skipping .92 and there are no issues on the .94 version I can see, few issues on the forum. Kind regards Peter
    1 point
  16. Hello there! My first post here, please be patient! I am just getting started with Unraid and I was having the same issue with Time Machine a few days ago. The issue for me: - First backup was made successfully - After that no following backups can be made. Time Machine starts preparing and stops after 1-2 minutes. The logs show "failed to attach using DiskImages2" error... - I played around with the .sparsebundle file a bit. I could access and mount the file via terminal, show information about it and even attempting to repair the file (no error found btw), but when I tried to mount it via Finder or try to show it's size in Finder, Finder freezes and I had to restart the computer to fix it. (Same happened in terminal when I did a "ls -l" in the share, but "hdiutil" worked fine..) I tried every suggested workaround in this thread, without success, including: - different SMB configurations suggested in this thread and in smb wiki - adding the share manually via config file and verifying the actual config with `testparm -v` - using the Time Machine Docker image I was using MacOS 12.5 (or 12.6, I don't remember) and Unraid 6.10.3. After two days of testing (and multiple full backups taking hours...) I gave up and accepted that there is a bug in smb/Unraid/MacOS somewhere and I decided to wait for the fix. But today I upgraded to the Public Beta of Ventura (MacOS 13) and came back to the Time Machine issue. It is still not working, but there are new information in the log for Time Machine after the upgrade. Maybe somebody has an idea: 2022-09-14 21:00:25 Starting manual backup 2022-09-14 21:00:25 Attempting to mount 'smb://simon@NAS._smb._tcp.local/timemachine' 2022-09-14 21:00:25 Initial network volume options for 'timemachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 0, QoS: 0x0, attributes: 0x1C} 2022-09-14 21:00:26 Configured network volume options for 'timemachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C} 2022-09-14 21:00:26 Mounted 'smb://simon@NAS._smb._tcp.local/timemachine' at '/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine' (672.83 GB of 1.05 TB available) 2022-09-14 21:00:26 Skipping periodic backup verification: not needed for an APFS sparsebundle 2022-09-14 21:00:27 'MacBook Pro von Simon.sparsebundle' does not need resizing - current logical size is 996.15 GB (996,147,200,000 bytes), size limit is 996.15 GB (996,147,200,000 bytes) 2022-09-14 21:00:27 Mountpoint '/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine' is still valid 2022-09-14 21:00:27 Checking for runtime corruption on '/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine/MacBook Pro von Simon.sparsebundle' ### SO FAR THE SAME AS BEFORE, THE NEXT LINES ARE NEW ### 2022-09-14 21:00:30 Failed to get name of volume with mountpoint 'file:///Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine/', error: Error Domain=NSCocoaErrorDomain Code=257 "Die Datei „timemachine“ konnte nicht geöffnet werden, da du nicht die Zugriffsrechte hast, um sie anzuzeigen." UserInfo={NSURL=file:///Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine/, NSFilePath=/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine, NSUnderlyingError=0x60000240ba20 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}} 2022-09-14 21:00:30 Failed to get name of volume with mountpoint 'file:///Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine/', error: Error Domain=NSCocoaErrorDomain Code=257 "Die Datei „timemachine“ konnte nicht geöffnet werden, da du nicht die Zugriffsrechte hast, um sie anzuzeigen." UserInfo={NSURL=file:///Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine/, NSFilePath=/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine, NSUnderlyingError=0x60000240b750 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}} 2022-09-14 21:00:30 Failed to create volume info from disk '<TMDisk: 0x7feef7064c00> '/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine'', error: missingName 2022-09-14 21:00:30 Failed to create volume info from disk '<TMDisk: 0x7feef7064200> '/System/Volumes/Data/home'', error: missingURLForRemounting ### FROM HERE IT IS THE SAME AS BEFORE ### 2022-09-14 21:01:14 Failed to attach using DiskImages2 to url '/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine/MacBook Pro von Simon.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} 2022-09-14 21:01:14 Cancelling backup because volume '/Volumes/.timemachine/NAS._smb._tcp.local/BE2E64C3-5555-44C4-ACD3-630D8977B1BC/timemachine' was unmounted. 2022-09-14 21:01:14 Requested backup cancellation or termination 2022-09-14 21:01:14 Waiting 60 seconds and trying again. 2022-09-14 21:01:14 Backup cancelled (22: BACKUP_CANCELED) Also there are this lines in the logs multiple times, not sure if it is related: 2022-09-14 20:59:03 '/Volumes/timemachine' does not support SMB FullFSync 2022-09-14 20:59:03 Failed to create volume info from disk '<TMDisk: 0x7feef9026000> '/System/Volumes/Data/home'', error: missingURLForRemounting
    1 point
  17. Turns out the Plugin was still Instaled. When i tryed to grab the Unraid Logs from the USB stick i just took a look trough the files and i noticed that there is still this Plugin called "Swapfile for unRAID 6.9" installed. Deleted it and now my rootfs folder is now Magicaly empty. Thanks for all the Explanations whit rootfs and tmp really is.
    1 point
  18. Well. U saved me from a lot of work and lost data, Holy. A big big Thank you It came back, as it was before, works now completely fine and etc. THANK YOU!
    1 point
  19. Yes thanks all working now I will keep going on 6.11 for now, I also think it's weird as it was working 100% on 6.9 it was after the upgrade to 6.10 I have started to see some weird thing happening. But thanks all working good now had some Dockers I had to reinstall but looks like it's all working again from what I can see.
    1 point
  20. Thanks for assisting -- I discovered that the Cisco Catalyst switch I use for my network here in the house did not have spanning-tree portfast enabled on that port, and it took a bit longer than unraid was expecting to get an IP. I'm up and running. Thank you both for looking into it with me.
    1 point
  21. Meine Meinung: Keine GUI kommt auch nur ansatzweise an einen klassischen Norton Clone wie MC heran. Egal ob TotalCommander unter Windows oder MC unter Linux - Tastenbedienung schlägt Mausbedienung um Welten - zumindest in dieser Programm-Kategorie. ABER: Es liegt auch daran welche Erfahrungswerte man mitbringt. Musste vor Kurzem in einem Sekretariat kopfschüttelnd Tastenkombinationen schulen. Niemand kannte dort wort-weises vorwärts- bzw. rückwärtsspringen. Von Sätzen oder Absätzen fange ich noch nicht mal an. Einen Satz schnell markieren, ausschneiden, am Ende des nächsten Satzes einfügen, etc. Dort wurde sogar zeichen-weise mit Backtab gelöscht. Was ich sagen will: Wer mit Maus groß wurde, kennt oft die Alternativen nicht. Den File Explorer nutze ich um mal eben etwas zu löschen. Leider lande ich beim direkten Aufruf der Seite zumeist auf dem Login Dialog - und der reicht mich dann nicht weiter. Das wiederum ist Unraid-Steinzeit.
    1 point
  22. Please remove the plugin entirely, reboot, pull a fresh copy from the CA App, reboot again and see if the issue persists or if it fixes it.
    1 point
  23. Hi ghost82, meanwhile, thanks for your answer ..... I try to better explain what I did: 1 - This GPU has a UEFI custom bios because originally it was NOT UEFI. It is natively recognized on the Mac Pro without any problems. 2 - I re-extracted the vBIOS via Windows 10 VM (I know it's not the best) and the file is 132KB 3 - I installed virt manager because unlike the one I saw in the Spaceinvader One video, Macinabox didn't give me the option to choose if I wanted it or not. Maybe it's this latest version of Macinabox that no longer includes it, I don't know ..... I installed it to better see everything on the VMs. 4 - I copied the EFI partition folders of the bootloader to the EFI partition of the Mac OS installed as Spaceinvader One did in the video and I did not touch any of the various parameters because I would not even be able, that's why I asked if I needed to retouch some parameters like when building a Hackintosh. 5 - I did NOT use VFIO nor ACS patch, audio and video were already on the correct bus together. I also specify that this GPU is the only one installed on unRAID. However now everything works! I see Catalina both on the monitor attached to unRAID and via the web as a vm on another computer! Thanks again for your time, I really appreciate it !! Zippi
    1 point
  24. Before upgrading I have deleted network.cfg just to test and VOILA, that fixed the problem, it works. For some reason the physical port is actually eth2, not eth0, and eth0 and eth2 are bridged together. Not sure why this is this way, but also not sure how was it initially, so I take it. It works, and that's all I need
    1 point
  25. Open the vm in the xml mode and check at the bottom if there is something related to that usb device; if it's there manually delete the offending block of code.
    1 point
  26. 1 point
  27. It's not a problem to mix different speed disks in the array, parity check/rebuilds will be limited by the speed of the slowest disk, other than that there are no issues.
    1 point
  28. Don't remember seeing a similar issue, and certainly not a common problem, temporarily remove any extra SMB settings if you have them and/or boot in safe mode, if issue persists boot with v6.10.3 in a trial key to see if it's config related.
    1 point
  29. For the record I reported the issue of failing to update to the AUR package maintainer and they fixed it so the AUR got updated and in turn so did the binhex container.
    1 point
  30. I'm not much of a programmer. These days. But you have both naming conventions already I may be able to figure it out. If I can find some free time to dabble with it. I'll see what I can do. Good luck on your study!
    1 point
  31. Not officially supported, there is a "Virtualizing Unraid" subforum where users can help each other. But note that Unraid itself can host VMs, so, as mentioned, you can run linux or other OS under Unraid.
    1 point
  32. I run a first generation Ryzen 1500X, and I have had no issues in the nearly 2 years the server has run. First gen Ryzen had issues with Linux when it was first released, as AMD focused so much of their effort towards Windows based OS. And where AMD was at that time, I don't really blame them for doing so. But it has been 5 years since Ryzen was first released (April 2017) and most issues are in the rear view window now. EPYC processors are quickly filling data centers, which are mostly running Linux based code. The majority of the issues folks posting here on the forum are systems that are overclocking, running their RAM too fast, or have not set a simple BIOS setting correctly. All are listed in the FAQ entry What can I do to keep my Ryzen based server from crashing/locking up with Unraid? . Folks don't like the idea that the 4 3200 RAM DIMMs the marketing people sold them need be run at 2133. For the majority of Unraid use cases, you will never notice the difference. This from someone running a 4c/8t processor in his sever, with 18 running dockers. As much as a AMD fanboy I may be, if building an Unraid server for mostly media/video serving (Plex/Emby) and working from a clean sheet of paper, going the Intel route makes sense to take advantage of Quick Sync for hardware encoding/decoding.
    1 point
  33. Many thanks.. I thought that I had broken something... All is fixed now. I should have checked here first before started pulling my hair out 🙂
    1 point
  34. Historically there have been more minor issues getting and keeping AMD equipment running well with anything but Windows. There is an entire thread here dedicated to troubleshooting issues with AMD. Intel is more likely to work out of the box and stay working. If you like tinkering and problem solving, the extra performance from AMD may be worth it, but for me I prefer to spend a little more for less troubleshooting. Opinions vary, and AMD vs. Intel is almost like discussing religion and politics.
    1 point
  35. Update: Recieved the LSI card. Installed it and cable managed (extremely hard) . Running parity check with out any error or issues so far.
    1 point
  36. Download the v6.10.3 zip and extract al the bz* files to the flash drive overwriting existing ones.
    1 point
  37. I thought the flash backup didn't work because of the cache flush on the server side. About two hours ago, I tried to activate the flash backup. I found it worked. Maybe some configuration was done on the server side.
    1 point
  38. It is always recommended to dump your own bios file: the 70 kb file could be good, I would check it with an hex editor and see what it's inside. If the dumped file is crap, you should search and solve why you are not able to dump the vbios: this is recommended, because if the gpu is in use by the host you wont be able to use it even with a proper vbios. It works the same way as a bare metal hackintosh, you need lilu/whatevergreen kexts and all the workarounds (if any) needed for bare metal hackintosh. The only thing that changes compared to bare metal is that you need also to set the topology of the vm: make sure to pass both video and audio of the gpu, set them as a multifunction device (same bus, same slot, different function) and do not use bus 0. It is recommended to attach them to vfio; not sure what you are asking: you need to passthrough both devices (audio and video, so 2 checkmarks), if they are alone in the same iommu group it's ok, if they are together with some other device use acs patch to split them. On top of this make sure the vbios of the gpu is uefi, otherwise nothing will work.
    1 point
  39. Monterey has no drivers for 1070, so there's no way to get acceleration or any video output from that gpu; stick to high sierra (with installed nvidia drivers), change gpu with a compatible one, or do not use gpu passthrough.
    1 point
  40. I'll give a little insight in how the sausage is made. I've worked in semiconductor manufacturing for the past 20+ years. You do not start out manufacturing 9700 and 9700K processors. All are built as 9xxx chips, with the goal that all of them run as fast as possible. At a point near the end of manufacturing (after the individual die have been packaged) they go through a binning process. This is where they are tested for functionality at speed. In simple terms, the test determines the fasted clock speed the chip will run reliably. Processors that run at the fastest speed reliably at the "K" specification targets are binned as 9700K. Those that don't meet those targets, but function at the lower 9700 parameters go in the 9700 bin. Usually at this time they program the chip internally with the chip its designation (effectively "locking" the clock speed). There is usually still a bit of headroom given, such that a 3.5 GHz chip isn't going to fail at 3.51 GHz. Generally, even locked processors have a few 100 MHz extra, allowing the company to be confident that the chip operates at its advertised speed. As @ChatNoir wrote, a server runs 24/7/365. A binning test runs maybe an few hours. Running at the edge of a processor's speed for a prolonged time is asking for a failure to occur. With the 9700K proven to have been manufactured better and having a higher base clock, if it fits your budget the K chips (running at base clock) are probably the more reliable choice.
    1 point
  41. You need to fix this problem instead of trying to make this plugin workaround your hardware issues. I already replied to your (nearly year old) thread about your problem but never got any response.
    1 point
  42. Seems like i get "Invalid Username or password." error, i was able to get it to work by turning off my 2fa on nordvpn which id rather not do. Any way to work around this?
    1 point
  43. Just to be sure you've setup the port correctly lets start with this- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md Scroll down to Q4.
    1 point
  44. Yeah, you just need to make Unraid "forget" that parity by unassigning it and starting the array, then are free to use it as a replacement disk.
    1 point
  45. How do I get a command prompt within a docker application? docker exec -it NameOfContainer /bin/bash Or by clicking on the docker's icon from dashboard / docker tab, select "Shell"
    1 point