xxredxpandaxx

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?

It is, and thanks for the suggestion. I'll reach out and see if they can help.

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

Unfortunately I don’t have this setup anymore and I can’t remember the pinouts for it. What I did was trace the wires from the buttons and lights back to the harness where I wanted to connect into. Then use a multimeter to make sure I had the correct ones. Sorry I couldn’t be more help!

When I add this to my docker.cfg docker fails to start. I haven't had time to look into it yet, but does this method still work?

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

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.

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.

I had hope for a second, but I don't get any of those errors. I am getting a segfault error that I am trying to figure out though. kernel: Plex Transcoder[12979]: segfault at 150c9a93ae48 ip 00001500a9dde818 sp 00007ffde2a81420 error 4 in libigdgmm.so.plex[1500a9d50000+90000]

It's not a 4k issue. It happens with a 1080p video as well.

I have a 12600k and just updated to unraid 6.11. Using the linuxserver plex container I set up the correct passthrough parameter "--device=/dev/dri:/dev/dri" and looks like plex found the iGPU just fine. When I try to transcode It shows up as (hw) transcoding but nothing plays on the cient side. Not sure why it's not working.

Thanks! I didn't see this when I was researching. Got it working now with some crashing but I knew that was expected as of right now.

I'm not seeing the /dev/dri folder and I created the file to load the i915 driver in 6.9. I also ran the command modprobe i915 and still nothing. I just bought a new 12th gen setup and cant get legacy boot to work right now. I'm wondering if because I'm booting with UEFI that passthrough isn't working. If anyone with a 12th gen setup can chime in that would be great!

I finally figured out the problem!! one of the ports on my controller is causing the CRC errors on my drives. Everything worked fine on the second port then I moved the cable to the first one and started getting crc errors. Thanks for your help everyone!

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?

ya that’s what I figured. Sent from my iPhone using Tapatalk

Well I am still getting the errors with the new expander. Any other ideas? Possibly the two cables going to the expander from the controller? Sent from my iPhone using Tapatalk

Ya I updated the firmware to the latest one. Thanks for all of your help! I’ll see about getting a new one. Sent from my iPhone using Tapatalk

Well I connected those 6 disks to just the controller and not through the expander and I didn't get any CRC errors and got good speeds. I am starting to think my RES3TV360 is faulty. Probably going to contact the seller I bought it from and get a replacement unless someone here has any other ideas I can try.

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?

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.

Awesome, thanks! I'll update and see if that helps.

You didn't have any problems updating with an LSI card instead of one of the recommended intel cards? 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.

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)

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.