Jump to content

optiman

Members
  • Posts

    1,132
  • Joined

  • Last visited

Posts posted by optiman

  1.  

    I went with LSI cables for two of the ports and Supermicro cables for the other two.  I hope they are more relieable than the crappy Trip Lite ones that get errors if you just look at them.

     

    LSI 9305-24i arrived and will install soon.   After checking the website, I see there is a new firmware release.  While the hw capatibility list says works Out Of the Box, has anyone updated their firmware to this latest version, 16.00.01.00 - released May 20, 2018?   https://www.broadcom.com/products/storage/host-bus-adapters/sas-9305-24i#downloads

     

    Trying to decide if I leave the firmware as is, or update to the latest before connecting my drives.

  2. cool - thank you for sharing.  The hw compatibility list shows the 9305 24 working out of the box so I hope that is correct for my Supermicro X11SSM-F mb.

     

    Which breakout cables did you go with?  I have tried a few different brands and found the Trip Lite ones are very sensitive and even a little pressure from the case door pressing on them will cause errors.  I'm now trying LSI cables and SuperMircro brand.  I'm also trying to use right angle drive connectors so the case side door doesn't even touch them.

     

  3. Thank you!  My 9305-24i was delivered today. Did you install it in a 8x slot or a 16x slot?  I know it's a 8x card and the 16x slot won't help with anything, but I was curious if it worked ok in a 16x slot.  Very cool that we don't have do update firmware or mess with drivers.  ?

  4. Will the new LSI SAS 9400-16i sata card work with this new version of unraid?  Drivers included or I would have to manually install them?

     

    update: nevermind, that card is not on the compatibility list.

     

    Will the LSI 9305-16i be supported soon?

     

    otherwise I will have to go with the LSI 9305-24i

  5. Anyone using the LSI SAS 9400-16i card in your unraid server?  This card can drive 16 sata drives and I need more ports.

     

    update:  After reading more, this card is way overkill and plus it is NOT on the hardware compatibility list.  I also noticed that the LSI 9305-16i is not on the list.

     

    I guess  I will have to go with the LSI 9305-24i  because it is on the list and recommended.

    For LSI cables, I see LSI LSI00410 0.6m Internal Cable SFF8643 to x4 SATA.  

     

    I'm looking for a recommendation on cables.  I'm looking for the 90 degree facing down sata connections, so the cables drop downwards.  The ones that go straight in make it tight for my side door, they rub against the door.  I have tried 90 degree up cables, but those just make a big mess and the cables are in the way.

     

    The only LSI cables I can find are straight, so I need to look at other brands.  Any recommendations?

  6. Today I have more errors.  Perhaps something to do with the sata drivers or some other change in 6.5.1.  I did not have any of these errors prior and I have not touched anything else.

     

    May 3 06:13:32 Tower kernel: ata8.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen
    May 3 06:13:32 Tower kernel: ata8.00: irq_stat 0x0c400040, interface fatal error, connection status changed
    May 3 06:13:32 Tower kernel: ata8: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
    May 3 06:13:32 Tower kernel: ata8.00: failed command: READ DMA EXT
    May 3 06:13:32 Tower kernel: ata8.00: cmd 25/00:40:88:2e:73/00:05:a6:00:00/e0 tag 25 dma 688128 in
    May 3 06:13:32 Tower kernel: res 50/00:00:87:2e:73/00:00:a6:00:00/e0 Emask 0x50 (ATA bus error)
    May 3 06:13:32 Tower kernel: ata8.00: status: { DRDY }
    May 3 06:13:32 Tower kernel: ata8: hard resetting link
    May 3 06:13:38 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
    May 3 06:13:42 Tower kernel: ata8: COMRESET failed (errno=-16)
    May 3 06:13:42 Tower kernel: ata8: hard resetting link
    May 3 06:13:48 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
    May 3 06:13:49 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 3 06:13:49 Tower kernel: ata8.00: configured for UDMA/33
    May 3 06:13:49 Tower kernel: ata8: EH complete
    May 3 06:13:56 Tower kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen
    May 3 06:13:56 Tower kernel: ata8.00: irq_stat 0x0c400040, interface fatal error, connection status changed
    May 3 06:13:56 Tower kernel: ata8: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
    May 3 06:13:56 Tower kernel: ata8.00: failed command: READ DMA EXT
    May 3 06:13:56 Tower kernel: ata8.00: cmd 25/00:40:88:ce:94/00:05:a6:00:00/e0 tag 18 dma 688128 in
    May 3 06:13:56 Tower kernel: res 50/00:00:87:ce:94/00:00:a6:00:00/e0 Emask 0x10 (ATA bus error)
    May 3 06:13:56 Tower kernel: ata8.00: status: { DRDY }
    May 3 06:13:56 Tower kernel: ata8: hard resetting link
    May 3 06:14:02 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
    May 3 06:14:06 Tower kernel: ata8: COMRESET failed (errno=-16)
    May 3 06:14:06 Tower kernel: ata8: hard resetting link
    May 3 06:14:12 Tower kernel: ata8: link is slow to respond, please be patient (ready=0)
    May 3 06:14:13 Tower kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    May 3 06:14:13 Tower kernel: ata8.00: configured for UDMA/33
    May 3 06:14:13 Tower kernel: ata8: EH complete

     

    Any ideas?

  7.  

    I saw these errors in my log today, which I have never seen before.  Since upgrading to 6.5.1, these are the only errors so far.

     

    Anything to worry about?  

     

    May 2 05:28:30 Tower nginx: 2018/05/02 05:28:30 [error] 10265#10265: *761604 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost", referrer: "http://localhost/Main"
    May 2 05:28:30 Tower php-fpm[10239]: [WARNING] [pool www] child 1600 exited on signal 7 (SIGBUS) after 328.611253 seconds from start

  8. After running the Fix Common Problems tool. I have this error:

     

    **** Template URL for docker application binhex-sickrage is missing. ****   **** Template URL for docker application couchpotato is missing. ****

     

    The Docker containers are running fine, so I'm not clear on how a template goes missing and how do I correct this?

  9. After running the Fix Common Problems tool. I have this error:

     

    **** Template URL for docker application binhex-sickrage is missing. ****   **** Template URL for docker application couchpotato is missing. ****

     

    The Docker containers are running fine, so I'm not clear on how a template goes missing and how do I correct this?

     

    I went to post this question in the Docker Container thread, but it's locked and you have to beg to get access. wtf.

     

  10.  

    Time for some Go file clean up.  I installed the Update Assistant app and the report complained about some old entries in my Go file.  Taking a closer look, we have added some lines over the past few years to add a custom temp sensor (I don't need this anymore), to fix a samba issue a few versions back, and a couple of other fixes .  My guess is most if not all of those Go file entries are no longer needed.  Here is a copy of my Go file.

     

    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &
    # Update Sensors Config
    cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d/sensors.conf
    modprobe coretemp
    modprobe it87
    /usr/bin/sensors -s
    # Unmenu Start
    # /boot/unmenu/uu
    # This adjusts the PID for UNRAID server and Shares process may never be killed in a low memory condition.
    # Uses the new oom_score_adj
    # Set UNRAID webserver is never killed off.
    pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo -1000 > /proc/$PID/oom_score_adj; done
    # Set SAMBA so shares are never killed off.
    pgrep -f "/usr/sbin/smbd" | while read PID; do echo -1000 > /proc/$PID/oom_score_adj; done
    #
    # Set UNRAID Telnet is never killed off.
    pgrep -f "in.telnetd" | while read PID; do echo -1000 > /proc/$PID/oom_score_adj; done
     

    I took a look at the default Go file in the 6.5.1 and it only has one entry.

     

    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &
     

    I plan to replace my existing Go file with the default file.  Is there anything in the old Go file that is still needed or have all of those issues now been resolved?

     

    Thanks!

  11. On 3/14/2018 at 11:32 PM, blu3_v2 said:

    Limetech - I just checked my server under Settings > Scheduler > Mover Settings > Mover logging, and it was already set to Enabled. I still don't see any Mover finished notifications as I did previously. Is there anywhere else I need to adjust my Mover notifications?

     

    +1

     

    I too check the log before updating items and now the Mover is no longer telling me when it has finished.  The Mover log is Enabled.

     

    Is there a list of recommendations for 6.5, other than this thread?  After reading here, I learned that Advanced Buttons should be removed, as example.  I don't use Advanced Buttons but it would be good to know what items should be removed when upgrading to 6.5.  Another example is that Preclear plugin does not work anymore.  There is a work around, but I had to f ind that in the preclear thread.

     

    It would be cool if in the first post of this thread, they include a list of things we should do, like remove some plugins, remove preclear, remove advanced buttons, etc.

     

  12. On 3/14/2018 at 11:42 AM, NNate said:

    Is it recommended to change the NTP server to point at Google now for existing installs (noticed it's not default for new installs)? If so, why? More reliable than the ntp pool?

     

    I upgraded from 6.3.5 with no issues so far.  

     

    My NTP is pointed to pool.ntp.org.  What should i change it to?

     

  13. wow, been a while since I've read this thread, and I'm still on 6.3.5.  After reading the past few pages, I have removed the Preclear plugin and then upgrade to 6.4.1.

     

    Seems I can just use the Seagate disk tool to confirm the drives are good, and then just add them to my array.

     

    I don't see a need to even bother with the script at this point.  I think things got more simple.  :)

     

  14. Help please.  I am trying to setup a unraid share/docker and point my HDHomeRun tuner for DVR server storage.

     

    I installed the docker on my unraid 6.3.5 server, using the template from post 1.  I created a share called hdhomerundvr and shared via SMG, and made it public access.  When the docker installed, it only had one path and that was for the config or main files.  I added a hdhomerundvr path and pointed to the share I just created.

     

    Do I need any other variables?   There are currently no Ports or IP addresses showing in the config section, which is not normal compared to the other dockers that all have port and IP information.  This makes me think the install did not go as planned.

     

    I have the HDHomeRun Extend and I've purchased the DVR service.  I've used the Windows version to update the firmware to 20180110.  I tried to configure the DVR tab by selecting NAS.  The list that comes up does not show any shares or the unraid server.  It shows my Yamaha receiver and a few other items that just have long numbers for the name and ? mark, not sure what those are.

     

    I can also go directly to the IP address and I see the tuner menu.  Under Internet Configuration, it shows Not Detected, none, not tested.  The tuner has a valid IP via DHCP so it should be able to communicate with the internet just fine.  What should I do about this part?

     

    Is there more detailed instructions on how to configure this docker/unraid setup and how to setup the DVR?

     

    Thanks!

×
×
  • Create New...