Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About sjoerd

  • Rank
  1. 👍 well - sorted I guess 🙂
  2. Yes I did click - check for updates. They are spinning for about 10 min now. Oh wait - I reloaded the page with dockers and now I see they can be updated. It seems 3 out of 4 dockers could be updated. I wonder why I had to check manually using the "check for updates" button and why they kept spinning for so long (until i refreshed the page).
  3. I'm a bit puzzled I installed your version from the CA And when I start the webui the webui tells me is available. The download now link let me download plexmediaserver- from download.plex.tv but I got a feeling that not a docker. And what do u mean with "updates are done automatically via script". Can I check I those scripts actually fire (logs and suchs)
  4. Hi, Sorry for my late reply; So I just need to wait a bit then I guess 🙂
  5. Hello binhex, Thank you for this plexpass docker. I noticed the other day the plex has an update "A Plex Media Server update is available for the server SJOERD Tower! Download now. Do I need to update it from within the docker or do we need to wait till you made a new docker ? Regards
  6. Oke - I will try to umout then otherwise I can reboot the array tonight. Not going to reboot during the day unless I absolutely have to. My family won't like that.. Edit 1: Uhm - oke When I umount /dev/sdt1 (USB3_1G) it got remounted as /dev/sdr1 Also - I cannot remove (rmdir) the connected directory (Device or resource busy) which is ofc impossible since the drive is on my desk. Maybe I accidently (but consciously) mapped the drive in docker or something.. Will investigate Edit 2: I was able to reboot the array. After the array was up I got an extra item on the main tab. Under the unassigned devices section I got a line to remove the missing disc (it got identified by the usb-drive's serial-number). After I clicked "remove" the drive disappeared from the mountlist (df) and I was able to rmdir /mnt/disks/USB3_1G So - fixed 👍 Still not sure why those two usb-drive stayed mounted 🤔
  7. Oh cool - i didn't know there was a tool like that. There's a lot of info in there. I checked the df.txt (which I should have done using df -hP on the console ofc) and found "the problem". A couple of days I made backups of my usershares to those two (indeed ntfs-formatted) external usb-drives with hexbin-krusader. After I unmounted those disks properly with the unassigned devices plugin but I guess something went wrong. I seems I also have two shares namely \\tower\Elements and \\tower\USB3_1G visible in my windows file-explorer but those share are not at the shares-tab. Can I simply umount those drives ? Filesystem Size Used Avail Use% Mounted on /dev/sdt1 932G 405G 528G 44% /mnt/disks/USB3_1GB /dev/sds1 1.9T 405G 1.5T 22% /mnt/disks/Elements This is weird tho: root@Tower:/mnt/disks# ls -l total 8 drwxrwxrwx 1 root root 4096 Mar 6 18:19 Elements/ drwxrwxrwx 3 nobody users 21 Feb 15 17:15 SLOT20_320GB/ drwxrwxrwx 1 root root 4096 Mar 6 18:18 USB3_1GB/ Can they be removed with rmdir ? SLOT20_320GB contains my vm's so that's a valid directory/mapping
  8. Since a couple of days (I think) I got these weird errors about disks that are not even in my array.. What's going on here? The system keeps telling me that something is wrong with sds1 and sdt1 and about ntfs. I don't have ntfs disks (apart from the 2 windows vm's that is) I don't get it.. - I don't like errors in my log esp. when I don't know where they are comming from. Regards,
  9. Hello, Last night I added a 250GB ssd cache drive. When I got home the whole system got haywire because appearently all my shares were set to "prefer" cache and unraid dumped (accoording the plan) everything to the cache-drive till it was full. Because of the large amount of small files that got moved to the cache-drive and spamming that the cache was full the /var/log mountpoint was also full because the syslog file reached over 100 leaving me with a 99% full mountpoint. After I fixed the "static" shares to "no" and normal user shares to "yes" or "prefer" (again - a SpaceInvaderOne saved my life) I could empty the cache and delete the syslog (syslogging stopped completely there so I had to "touch" the syslog) Now - couple of hours later the cache-drive shows normal behaviour but.. the /var/log is already at 46%.. That's mainly because of telling me which files got moved.. I am interested what the mover does esp when something goes wrong but the mountpoint it only 128M or something like that.. Since I'm new to unraid and not familiar with tinkering - altho I did a fair share today - so, is it possible to log only mover errors to the syslog and let normal logging be logged to different logfile on the system like the cache folder or an unassigned drive or whatever. Regards
  10. I knew I read it somewhere about the + but I forgot to unmount - makes perfectly sense of course.. Thanks for the other questions being answers @jpotrz, @dlandon
  11. Hi, Starting to move my vm's to an unassigned disk.. Now I know it's possible but i got some questions Is it possible to rename how the disks are mounted? E.g. /mnt/disks/Hitachi_HDS721032CLA362_JPB470HB18RZ3D is a ridiculously long and meaningless name. My test desktop will be at /mnt/disks/Hitachi_HDS721032CLA362_JPB470HB18RZ3D/domains/UbuntuDesk01/vdisk1.img for instance... I rather have it something like /mnt/disks/SLOT4_320GB/domains/UbuntuDesk01/vdisk1.img About sharing. If all I do on those disks is hosting vm's then I do not need to share it right - that is only for nfs/cifs/smb? And if I share can I share it the same way as unraids user shares (set R/W access to a unraid user?) If I need to stop/powerdown/reboot the array. Will the vm's be shutdown gracefully like if they were on an array disk - like they do now?
  12. Excellent! I was indeed afraid a new config would wipe everything. I will take a look at unBALANCE before I start.
  13. 32GB Corsair Vengeance 4x 8GB cl 9-9-9-24 DDR3/1600MHz. Maximum for my motherboard/cpu (GA-H97M-D3H / i7-4785T). Upgraded from an 8Gb/ i5 (2x 4GB / i5-4670K).
  14. I'm not sure if it's related but I encountered similar issues with coping large amounts of files to shares from my old NAS. I have 4 shares with each only R/W permission for my family members. For the time being I also added my own account as R/W to the user-share for the convenience. After copying I set my account to access denied on the shares of family member but then some folders inside were not accessible by the rightful owner.. Turn out I had to manually chown -R <user>:users ./the-user-share to fix the problem since <user> was set to my own instead of (in this case) my son's account.
  15. Sorry to kick this topic as it is already marked solved but I'm still a bit puzzled - because I'm new to unraid everything is "scary" when making changes like this. If I read and understand everything correctly then this is what i should do to remove one (or more) disks at once (I copied this list partially from @Luca 1. make screenshot from your array (disk locator plugin is very useful here) 2. stop the array. 3. exclude the disk(s?) at the global share settings. 4. restart the array 5. move all the data from the disk(s?) you want to remove to other disks pref. using krusader (great vid by SpaceInvaderOne on youtube!) 6. stop array 7. physically remove the disk(s?) from the existing array 8. start array (but not possible since there is/are missing disk(s) so go to 9. 9. run tools / new config (keeping existing parity disk(s)) 10. assign the remaining disks (I assume the remaining disks needs to be assigned at the exact same place where they were - hence the screenshot) 11. start array / run parity-sync So euhm.. If I understand the procedure correctly it does not matter if you yank out more then one disk at once as long as the date from those disk has been moved to other disks. Parity needs to be rebuild anyways so.. and yes the array in not protected by parity at this point. From my understanding this is only possible because unraid is not a raid but a jbod with normal filesystem on it.. Also.. Can this procedure also be used to rearrange the physical disks (move them into an other physical slots of the array) or does unraid not care where the disks are as long as the order in the unraid-config stays the same? Could someone confirm this.. edit 16feb2019: 12. Do not forget to re-set the global share to include all disks and exclude none if you want unraid to use any new disks in those "slots". I added this morning 3x 3TB from my old rig and was wondering why I had a disk-share named "disk2" and why disk 2 was not spinning up. Disk two was the one I removed couple of days ago.