optiman

Members
  • Posts

    1116
  • Joined

  • Last visited

Everything posted by optiman

  1. Thanks! I have upgraded to 6.9.1. Providing the drives spin down and no new issues, I'll camp out here until 6.10 is stable
  2. @klepel Thank you! I cannot believe that I saw nothing out of place, yet the issue was looking right at me, wow. I didn't notice that the cache drives were no longer assigned. That explains my issues. After assigning the drives, everything is back to normal on 6.8.3. Take away for me is to remember to review those release notes Now that I emergency is over, what do you think about staying on 6.8.3 vs trying 6.9.1? I have downloaded 6.9.1 zip, but should I just wait for 6.10 stable? @Hoopster Oh thanks for the reminder about manually upgrading. It's been so long since we had to do it that way, I forgot. I thought we only copied a couple of files back then. I see there are several bz* files now. If I decide to try 6.9.1, I assume I can just copy the highlighted bz* files to my flash, and there is no need to update any other files on the flash, meaning no need to update files from the syslinux directory, as example. Is that correct?
  3. Thank you! That does bring back some memories of how we upgraded in the old days. That said, I will wait to take any further action until I get advice on a path forward. I don't want to make things worse.
  4. Was on 6.8.3 with no issues. Upgraded to 6.9.2, everything was working great except my drives would not spin down, so they remained up all the time. Because that will take life off the drives, I decided to use the GUI to rollback to 6.8.3. I now have the follow issues: -Missing shares, some are there and some are missing. Those missing are not accessible, "Share not published". However, the conf files for shares on my flash drive look ok, nothing missing. -Docker says it cannot start, most likely corrupt. I did see an error for one of them saying my Automation path was invalid. That's one of the shares missing. I posted in a couple of threads and was told to start a new thread, so here we are. I want advice before taking any further action. I'm now worried that going back to 6.8.3 is the problem. I have downloaded 6.9.1, but I'm not certain the process to manually upgrade. Update : Marked as Solved. The solution is to read the release notes, especially when upgrading or downgrading major releases, 6.8x to 6.9x 6.9.2 before downgrading tower-diagnostics-20211125-0835.zip after downgrading to 6.8.3 tower-diagnostics-20211202-0939.zip
  5. ok, how can I do that? The GUI offers 6.9.2 only. Will upgrading to 6.9.1 also fix the mnt/user permissions and the fact that some of my shares are missing and not accessible? BTW, I don't see any Cache issues. What do you mean re-assign cache?
  6. no, I was on 6.8.3 before upgrading to 6.9.2 So I just used the Upgrade OS tool to rollback. However, no sooner than I posted here, I noticed that some of my shares are missing and my docker won't start. I found in another thread to check folder permissions for /mnt/user and it indeed has the wrong permissions. I'm trying to fix that right now. Is there a issue going back to 6.8.3? Should I, and how do I get to 6.9.1? The GUI only offers the latest version.
  7. I have this issue. Everything was working great until I rolled back to 6.8.3. I couldn't stay on 6.9.2 because all of my drives would not spin down. After the downgrade, I had no dockers, error saying could not start, and I am missing shares. I found this thread and found that my /mnt/user permissions don't look right. I looked at the flash drive and the conf files for all of my shares are still there. Based on this thread, it looks like I need to change the permissions to look like this, I don't play much at the command prompt so can somebody kindly share the commands to fix these permissions?
  8. there are too many issues IMHO to upgrade to 6.10.rc2, and with the drives not spinning down 6.9.2, I had to roll back to 6.8.3
  9. well there are way too many issues with 6.10.rc2, so I had to roll back to 6.8.3. I can't have all of my drives spinning the life out of them.
  10. wow, still quite a number of issues with rc2, maybe good idea to wait for rc3? I'm on 6.9.2 and the only issue I am having is the drives do not spin down. Can anyone confirm this is fixed in rc2+?
  11. ah good to know, thanks! I hate going back, so I may try 6.10rc2
  12. After upgrading to 6.9.2, I've noticed that my drives do not spin down like they should. Sometimes they will spin down, or some of the drives will spin down, but as of about a one week ago - most of the time they do not spin down. I'm running the same 5 dockers as I've been for a long time. I've made no other changes to my system. I do not run any VM's and there is nothing using my server that requires the drives to remain spun up. I've been on 6.9.2 for about a month and I only noticed the drive won't spin down issue about a week ago. I do not know if this issue is related to the upgrade, so I'm posting here in General Support. I confirmed that Disk Settings is still set to spin down after 45 minutes. I don't see anything in my syslog related to this issue. diag file attached Thanks! tower-diagnostics-20211125-0835.zip
  13. It's my understanding that the issue isn't with Unraid at all, so the answer would be never. If you have a LSI controller and Seagate drives, it's best to just follow the instructions and disable EPC to be safe. Again, my understanding is that the issue is with combo of LSI controller and some Seagate drives. We need updated LSI drivers that could help address this, or updated fw from Seagate that addresses it. Let's hope new Seagate fw at least has that EPC disabled by default
  14. I disabled the EPC and did the upgrade and haven't had any issues. I guess the EPC was the issue, because as I mentioned in my other post, I wasn't able to disable the lowpowerspinup. As long as you disabled EPC, you should be good to go. Based on input from others, it sounds like future unraid version will not effect us. The issue is with LSI and Seagate. We need updated LSI drivers that address this, or updated fw from Seagate that addresses these issues. For me, I'm moving back to WD drives. I used those for years without any issues.
  15. That did it! Thank you! Thank you! Thank you! I haven't changed the dns servers in a long time, so I have no idea why they stopped working, but plugins page loads and docker check for updates works fine now ping after the change,
  16. yes sir, I will try those dns servers and report back
  17. So did post these questions / issue in the wrong place? Weird not getting any support
  18. @Squid new issue that may be related. When I go to the Plugins page, the status for each plugin says Unknown. I click on the Plugins header at the top and it will come back after only 10 - 20 seconds and say unknown for status. I have to do this 5 or 6 times and then it will take about 2 or 3 minutes to come back and then say Up to Date. I've never had this issue before. Now looking at my Docker page, it now says up-to-date. However, if I click on the Check for Updates at the bottom, each one just spins, same as before and I get the error in the syslog. The docker page never recovers, will spin forever until I go to another page, Main for example. When I go back to the Docker page, it will say up-to-date. So the check seems to work (maybe), but given the syslog errors and the fact that the docker page never refreshes, something is still wrong. I've tried changing to another ISP DNS, but that didn't help. Any ideas? tower-diagnostics-20210929-0542.zip
  19. @Squid As suggested, I started a new topic https://forums.unraid.net/topic/114042-docker-check-for-updates-not-working/?tab=comments#comment-1037745 diag posted there
  20. Here you go. tower-diagnostics-20210923-1551.zip
  21. When I try to Check For Updates on the Docker page, each docker just spins forever. I see this error in the syslog Sep 23 15:43:25 Tower nginx: 2021/09/23 15:43:25 [error] 8444#8444: *269827 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.11.79.248, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.11.79.162", referrer: "http://10.11.79.162/Docker" Any ideas?