sdfyjert

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

1 Neutral

About sdfyjert

  • Rank
    Newbie
  1. Hi, I just upgraded my rig from an old A10 to a decent i7 with an Asus Prime with Z390 chipset. Now that I have the fire-power I wanted to play a bit with the VMs. I wanted to passthru the ALC but it's nowhere to be found in the audio devices and then also nowhere to be found in the IOMMU groups. My A10 board also had an ALC sound card (really old one) and it was always there listed. The one shipped with the Asus Prime Z390 is ALC S1220A 8-Channel (which normally should be by default included with the Linux Kernel). Any ideas / clues / hints how to make unraid aware of the audio ca
  2. I was hoping to use them to indicate purchase source and invoice number 😃
  3. version: 6.9.1 2021-03-08 Comments work fine on the other (data) drives in the array. In the Parity drive however it will not persist it.
  4. Update to v6.9.0 was flawless so I installed v6.9.1 without much thought.... lesson learned. 1st reboot... nothing working. No network no nothing. Cold sweat started running already... move the NAS to a display or a display to the NAS.... either way this is going to be a disaster... 2nd reboot... (just in case)... NAS is accessible through the network! Not too bad! Starting the array... (more cold sweat) Array stared... Parity Check started (oooookey, so no clean shutdown/reboot obviously there), Opening Docker page... big red letters, Containers
  5. I am trying to run some command and push them the in background but the GUI terminal seems to get stuck and the script doesn't really seem to finish (I do not see the echo in the window and running ps aux | grep avahi-publish show the process does not exist). Any suggestions? #!/bin/bash #description=Generate avahi aliases #foregroundOnly=true #name=Avahi aliases (sub-domains) echo "plex.inas.local" /usr/bin/avahi-publish -a -R plex.inas.local $(avahi-resolve -4 -n inas.local | cut -f 2) &
  6. Almost got it working (was easier than expected). Here's what I have so far - for however might be interested in going down that path Step-1: Change the default ports for the unraid user interface Go to http://inas.local:8008/Settings/ManagementAccess and change http and https ports. I set them to 8008 and 8443. Just remember to check your ports are not already used by some docker container, etc. Step-2: Install Nginx Proxy Manager (docker from user-apps) - or build your own container. I had my own configs ready from the past server but Nginx proxy mana
  7. First tests - just manually running avahi-publish, reveal I forgot one important component. I need to also proxy the unraid web interface. This means I will need to move it to a different port and put it also behind nginx proxy. Is it feasible to change the unraid web interface port or everything will break?
  8. Hey guys, Before moving to unraid I had an ubuntu server installation for NAS. The only thing I miss from my old setup is the aliases I had configured for avahi. I still have the script I had build for the aliases which was utilising systemd to start bind to network events. I would really love to put that back in action. In practice, this is the service I had created for systemd in ubuntu server [Unit] Description=Publish %I as alias for %H.local via mdns Wants=network-online.target After=network-online.target BindsTo=sys-subsystem-net-devices-enp5s0.device Req
  9. Update coming next morning, the files that were removed from the share but where still on the disk reappeared on the share 🤔 I removed them again from the share and this time they're gone for good. ssh, `ls /mnt/user/movies > /mnt/user/tmp/movies_share.txt` and `ls /mnt/disk1/movies > /mnt/user/tmp/movies_disk1.txt` and run a diff on the files (though I'm dead certain there's a faster way with pipes) I understand how 1+1+1+1 = 1 works (🤣) I thought maybe during parity build it locks some sectors? If not the case and considering it's fs driver
  10. Here's the situation, I deleted some files (movies) using Plex. The titles got removed from Plex and the files no longer exist in the respective share. After noticing that the disk space is not freed I checked the actual hard disk (i.e. /mnt/disk1/movies) and the files are still there. Clues The array is entirely on xfs (latest version of unraid). At the same time the parity was being built (parity first time - just added the parity drive today) There was some "intense" activity throught the array and caches (fyi: this share does not use cache, cache = NO)
  11. Changing the cache to YES for that share would actually do me more harm. I have a limited amount of cache (SSD drives) and they're primarily used with shares related to video-editing. If I would set the movies share to cache=YES then it would easily saturate the cache 'causing issues to the shares that really need it. Regarding the network based approach, moving files in a machine from disk to disk is significantly faster than doing it over samba through another machine. The same file that I can move on the machine in 1 minute doing it over Finder as mounted networ
  12. +1 for me as any alternative can yield surprising results for example
  13. ah I see. So, either copy/delete or explicitly mv directly to one of the array disks. Is there some script I can install to "replace" mv that can read the settings and determine if mv or copy/delete is required and perform it automagically?
  14. Hi guys, I got a weird behaviour here and would like to know if this is a bug or I've done something wrong. I have a share called movies. The share is configured to live only on the array (no cache). Config looks like this. I have another share which lives only on the cache called tmp I `ssh` to the nas and move a file from tmp to movies mv /mnt/user/tmp/jdownloader/movie.mp4 /mnt/user/movies/. The end result is that a folder movies is created in `/mnt/cache/movies/movie.mp4`. The expected behaviour would have been that