Jump to content

tucansam

Members
  • Content Count

    798
  • Joined

  • Last visited

Community Reputation

11 Good

About tucansam

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. How do you guys have your music organized? I have a music share, and in it, I have directories for artist name, and under that, directories for albums, with songs inside those. ie g:\abc\album1, g:\abc\album2, etc Problem is, headphones is downloading multiple copies of the same albums, because it seems that it can't see into those subdirectories. If I instead do g:\abc_album1, g:\abc_album2, etc., then headphones appears to understand that the album already exists and does not download it. Is anyone else having this issue?
  2. Disregard. Found this: https://forums.unraid.net/topic/80103-keyfile-permissions/
  3. ETA On the other server (also encrypted) I just noticed that /root/keyfile isn't present until after I have booted and successfully entered the key. So it this a temporary file?
  4. Encrypted array. /root/keyfile just got deleted. How to recover? Thanks.
  5. Based on the pictures I found online, I would bet two weeks' pay that those are made by iStarUSA, or whoever the OEM is for iStarUSA. Except for the design on the drive doors, they look identical. I have been using the iStarUSAs for years, and they are great. I wouldn't hesitate going with the Silverstones.
  6. I used ssh (root) to move some files, and file permissions ended up messed up, so when I tried to run an rsync backup script, I had issues. 'docker safe new permissions' takes hours to run on my array, and I only needed the permissions of one share changed. 'chmod 777 *' didn't work. Failed with an 'invalid option' error. But 'chmod 777 1*' and then 'chmod 777 2*' and then 'chmod 777 A*' and then 'chmod 777 B*' etc etc etc worked fine. chown, same exact behavior. 'chown -R nobody:users *' failed with an 'invalid option' error. 'chown -R nobody:users A*' B* C* D* etc etc etc worked fine. What did I do wrong?
  7. High-Water, 750gb min free, automatically split as required, include all disks, export nfs private r/w to the other unraid server, export smb private with only me having r/w access. ETA I just manually cp'd the rest of /appdata with zero issues, I presume my use of recursive verbose on the initial command with the 99,999,999 deep plex directories is what blew the system up.
  8. Had to do the set-inform thing from the command line on two of my APs, but aside from that, the changeover to the new container seems to have gone reasonably smoothly.
  9. I'm at 6.6.6 and have been for a while. Today I had an issue where the GUI became unresponsive, and then the shell did. There have been no updates to plugins or docker containers in the last three or four days, and everything has been running OK until tonight. Last thing I did was: # cp -Rv /mnt/disks/ssd/* /mnt/user/backups/ssd-3-4-19 largely in order to backup my 'appdata' directory. This command ran fine for hours (appdata is huge thanks to Plex's inefficiency) and, when I came back to check on it, the shell was fozen (^C had no effect) and the GUI was too. I was able to ssh in a second time and 'htop' would not work (blank screen after execution). Another ssh session, 'top' wouldn't work, blank screen. Another ssh session, 'uptime' showed a sysload of 49 across the board. 'ps -ef | more' hung (waited 10 minutes and it didn't display anything). Now 'reboot' has also hung, I got the system going down message but the system is still powered on and I can still ssh in (GUI is inop, array is down). At this point I'm going to simply cross my fingers and pull the plug, and cancel the subsequent parity check. 'diagnostics' also had no effect, I waited almost 20 minutes and it never completed.
  10. I have never even thought of this. I will have to look into this more. I have often feared what would happen if one of my primary application disks failed, never even thought of putting it in the array so it is protected.
  11. Here's a dumb question, for which I think I already know the answer, but I'm going to ask anyway. Once all other disks in the array have been converted to encrypted volumes, is there any necessary action to take on the parity drive(s)? IE, can they remain their default partition format of GPT, or do they need to be encrypted also?
  12. Something doesn't look right, but I can't put my finger on it 😆
  13. Thank you, I sure will. I've got 60 hours left on a data move from one disk to the others, so I can convert the final disk in the array to an encrypted volume. So in a couple of days I'll have one more stop/start cycle to do, and will report back. Not busy at all. Its running plex, unifi, headphones, sonarr, and sab. Right now the load average is hovering around 8-9 because of the huge rsync job, but its usually between 1-2 if sab or sonarr is busy, and less than 1 when its idle doing nothing. i7-2600 with 16gb ram.
  14. Yes, just stopping the Recycle Bin, not actually shutting down the server. I'll update, thanks!
  15. Manually stopping the Recycle Bin hangs the GUI. Running 'diagnostics' from the shell prompt hangs. login as: root root@192.168.0.5's password: Last login: Wed Feb 27 05:40:10 2019 from 192.168.0.53 Linux 4.18.20-unRAID. root@ffs2:~# cd / root@ffs2:/# ls bin/ dev/ home/ lib/ mnt/ root/ sbin/ tmp/ var/ boot/ etc/ init@ lib64/ proc/ run/ sys/ usr/ root@ffs2:/# diagnostics Starting diagnostics collection... (Nothing ever happens beyond this) Here is what I can get: root@ffs2:~# tail /var/log/syslog Feb 27 02:49:17 ffs2 nginx: 2019/02/27 02:49:17 [error] 19871#19871: *834072 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.53, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.5", referrer: "http://192.168.0.5/Main" Feb 27 05:39:39 ffs2 kernel: mdcmd (181): spindown 12 Feb 27 05:40:10 ffs2 sshd[19803]: Accepted password for root from 192.168.0.53 port 50084 ssh2 Feb 27 05:46:02 ffs2 sshd[24417]: Accepted password for root from 192.168.0.53 port 50161 ssh2 Feb 27 05:46:49 ffs2 ool www[21531]: /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin 'empty' Feb 27 05:46:51 ffs2 Recycle Bin: User: Recycle Bin has been emptied Feb 27 05:46:54 ffs2 ool www[24117]: /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin 'update' Feb 27 05:46:54 ffs2 Recycle Bin: Stopping Recycle Bin Feb 27 05:48:42 ffs2 sshd[26830]: Accepted password for root from 192.168.0.53 port 50197 ssh2 Feb 27 05:48:54 ffs2 nginx: 2019/02/27 05:48:54 [error] 19871#19871: *881430 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.53, server: , request: "POST /update.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.0.5", referrer: "http://192.168.0.5/Settings/RecycleBin" root@ffs2:~#