optiman

Members
  • Posts

    1097
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

optiman's Achievements

Collaborator

Collaborator (7/14)

7

Reputation

  1. can anyone please confirm if the drive spin down issue is resolved in RC2? That's the only reason I haven't tried it yet and why I'm stuck on 6.9.1. When I went to 6.9.2, all my drives would remain spun up 😭
  2. Have you read all the posts in this thread? There are several issues still being worked on, that's why it's a RC. Unless you want to test and provide feedback, you may want to stay on the current stable release until 10 stable is released. On the other hand, several people don't have any issues at all. It may depend on hardware and how you are using Unraid. Could be risky for a Production server because the team is still sorting out some bugs / known issues. Of course this is just my opinion
  3. read my post on page 4, see that I uploaded the older version which has worked for many. Give that a try and read instructions carefully. you can check the current state, see first post instructions. If EPC is not listed, your drive doesn't support it. You can also check for new drive firmware and try again. I hope it helps you
  4. You don't need to address it to anyone, just post your questions. That said, be sure to Search and Read before posting questions that have already been posted and answered. You might want to start in the General Support thread... https://forums.unraid.net/forum/55-general-support/ that old post you replied to was just about how to Tag a specific member so they get a Notification and will see your post. If you need LT support, then @limetech is the correct tag.
  5. I had the same questions but I'm unable to provide more technical information about why this happened. As you said, there was updates on the Linux side (good thing) with 6.9.x and this issue was born. I see this as Linux continues to evolve and LSI and Seagate have to keep up to remain compatible. That said, this is just my opinion and there are way smarter people here than me who can talk to this. What I can tell you is that with EPC disabled, I've had zero issues. I'm running 6.9.1 because 6.9.2 all my drives remain spun up @ReLe It looks like Seagate has changed the file and folder format again with their tools. For example, the command I used did not have the word RedHat in it. Back up your data and at your own risk, try again using the version of SeaCheast that I have attached for you. The files are from June 2019 and they work perfectly. Due to file size limits, I only attached the Info and PowerControl utilities. PM me if you want any of the other tools that were part of the zip file. I personally didn't need any of the others. Unzip and give it a try again. I used this version on my system, and you can follow the instructions on page 1 of this thread, exactly Be sure to run the Info command first to see what the current state is. Confirm you have the correct mapping. Seacheast.zip
  6. I tried 6.9.2 and my drives would not spin down. Therefore I rolled back to 6.9.1 and I 'm testing to makes sure the drives spin down like they should. If you are not worried about the drive spin down issue, then 6.9.2 may work for you.
  7. 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
  8. @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?
  9. 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.
  10. 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
  11. 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?
  12. 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.
  13. 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?
  14. 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