xxredxpandaxx

Members
 View Profile  See their activity

  • Posts

    405

  • Joined

  • Last visited

 Content Type 

Posts posted by xxredxpandaxx

    Best way to troubleshoot supermicro backplane?

    in Hardware

    Posted

    Well, I have a bit of a weird situation. I connected both backplanes to my RES3TV360 and then to my HBA and now I'm not getting any errors. If I connect the backplanes back to my HBA I get errors.

     

    I'm confused as to why this is happening.  How finicky are these SFF-8643 cables and ports? Could it be a bad connection even after unplugging and replugging the connections several times? In my old set up with the same HBA and SAS expander I had some IO errors and it ended up being bad cables. This ran for several months without problem. Then when I moved my server I had IO errors on two of my drive bays and it has been like that for a while. Seems like the connections might be pretty finicky?

    Best way to troubleshoot supermicro backplane?

    in Hardware

    Posted

    I just bought a 36 bay SuperMicro CSE 847 chassis and I am getting I/O errors all over the place. I tried connecting with known good cables (from my old case), just the front backplane, just the back backplane, and then again to my old case. With the old system, no errors. With any combination of the new system I get I/O errors. It seems weird to me that I am getting errors on both the front and back backplanes separately as it's probably not likely that both are bad.

    What I am looking for is the best way to go about trouble shooting what could be wrong.

    HBA - LSI S3008L-L8e NI22

    Can't ssh from one unraid server to the other using keys.

    in General Support

    Posted · Edited by xxredxpandaxx

    Does the key file need to have a specific naming convention? seems like its looking for id_[encryptionName]

    I'll generate new keys with this name and see if it works.

     

    Edit: Ya looks like that was the problem. The key files need to have a specific naming convention (the default naming convention). Thanks for the help!

    • id_rsa
    • id_ecdsa
    • id_ecdsa_sk
    • id_ed25519
    • id_ed25519_sk
    • id_xmss
    • id_dsa

    Can't ssh from one unraid server to the other using keys.

    in General Support

    Posted

    I can't ssh into server 2 from server 1 using keys. Both are unraid systems. When I try to ssh from server 1 to server 2 is asks for a password. It works fine when I ssh into either server from my laptop using keys though.

    I generated my keys on server server 1 and placed the files in /root/.ssh/.  I used ssh-copy-id to copy over the public key to server 2. I manually verified that they were indeed imported correctly on server 2 as well.

    not really sure how to trouble shoot this issue and looking for some guidance.

    Nextcloud not working when on another vlan.

    in General Support

    Posted

    Honestly I'm not even sure which forum to post this to; but I seem to always get good help here.

    So I have nextcloud set up on my unraid server and behind SWAG. SWAG is running on a different non unraid server for the moment. I can access nextcloud from the same vlan that unraid is on (vlan1) and from outside my network. I just can't access from one of my other vlans. I have a UDM pro and have intervlan communication blocked. But I made a rule to allow traffic from vlan2 to vlan1(unraid vlan) over port 32400 (plex) and 33443 (unraid) I can ping both ports from vlan2 successfully and I can access plex from vlan2. Nextcloud however doesn't work. I tried both the domain and ip address:port that refers to nextcloud with no luck. I also added the vlan ip range to the trusted domains of nextcloud and still no luck.

    I'm kind of at a loss now and am looking for more things to try.

    Only getting around 50MB/s during parity rebuild?

    in General Support

    Posted

    7 minutes ago, Maticks said:

    If you have more than one Lsi card in the system you can’t have the boot bios on the cards. They fight with each other and what you are describing happens.

     You don’t need the boot bios unless you are booting Off a hard drive on the lsi controller. But you’re booting from USB so that is never required.

    You simply erase the bios from each card.

     If you have one lsi card in the system it’s fine but this behaviour happens with more than one. Sometimes the system can run for an hour before having a heap of issues read errors on drives and slow transfer speeds.

     

     

    I only have one card in the system. But thanks for the info! I'm sure that will come in handy later on. I'm currently checking each port on the LSI card with single link to the expander. I have also tried different pcie slots. Next is replacing the mini sas cables between the controller and expander?

     

    I have noticed that the crc errors show up at the 30 minute mark when doing a parity check. Does unraid check this at 30 minute intervals?

    Only getting around 50MB/s during parity rebuild?

    in General Support

    Posted

    So I took 6 other drives I had and tried them in every slot and I get CRC errors in every slot. Weird thing is, is I only get the errors on the data disks that are being read from, not the parity disk that is being written to. Also I am getting around 180MB/s during the parity check with only the 6 disks. Is it possible that my expander or controller could be bad?

    Only getting around 50MB/s during parity rebuild?

    in General Support

    Posted

    I updated and still only getting around 20MB/s.

    Anyone know how many amps or watts a motherboard and its components use on the 5v rail? My PSU can supply 20A on 5v and all my drives use about 13 amps on 5v. I wouldn’t think a motherboard and it’s components would use more than 7 amps on 5v but I really don’t know. The 12v rail has plenty of power as it is a 1000w PSU.

    I’m going to check the sata connections next but I think they are fine. Since I am getting the correct speeds when I do a speed test on one drive at a time.

    Only getting around 50MB/s during parity rebuild?

    in General Support

    Posted

    9 hours ago, JorgeB said:

    Yes.

     

     

    Expander is using an old firmware, though most likely that is not the problem, it should still be updated as mine improved performance considerably with the latest one, mostly when using a lot of devices, but if those errors persist after updating then there are other issues, I updated mine with Windows, easier since it didn't require installing anything else, instructions are included in a txt that comes with the download.

     

    You didn't have any problems updating with an LSI card instead of one of the recommended intel cards?

     

    9 hours ago, JorgeB said:

     

    Also a month ago you posted this in another thread:

     

     

    What hardware changed between then and now? Or was that an assumption? At the time I understood you already had that combo.

     

     

    I didn't have the card yet and was trying to see if anyone knew of a x16 controller so I cold get the max speed out of all of my drives.

    Only getting around 50MB/s during parity rebuild?

    in General Support

    Posted · Edited by xxredxpandaxx

    Well I found that one of my 12v connectors had come loose and I repaired that and I saw 160MB/s when I started a parity rebuild but only for a split second and then it went right back to ~28MB/s. Could this possibly be some sort of power issue?

     

    I am also still getting these codes just over and over and over in my logs. 

    Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Jul 7 23:22:57 Maple1 kernel: mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)

     

    Only getting around 50MB/s during parity rebuild?

    in General Support

    Posted

    1 minute ago, itimpi said:

    CRC errors are connection issues that will cause read/writes to be retried which will often recover the transfer but will definitely slow things down.   Occasional ones are not much of an issue but large numbers definitely are.

    I'm not thinking that the cables are the issue but maybe the expander or the controller, because how likely is it that every disk has a bad cable?

     

    I am having a hard time finding info about updating the firmware on the Intel RES3TV360. If anyone has done so or can direct me to a link to do that it would be greatly appreciated.