bisk
Members
-
Joined
Solutions
-
bisk's post in Slow Parity Calculation was marked as the answerSo I think I’ve got everything sorted out. I initially had the graphics card in PCIEX16_1 and the LSI HBA in PCIEX16_2. As soon as I added anything into any of the PCIEX1_x slots, then PCIEX16_2 will change from x4 to x1. Since I’m only using the video card for transcoding, I swapped the slots that it and the HBA are installed in and now my parity calculation is running nicely at about 170-180MB/s with the NVME risers in PCIEX1_1 and PCIEX1_3 (PCIEX1_2 is blocked since the video card is a double height card).
-
bisk's post in Server rebooting after starting the array was marked as the answerThanks for the assistance. I was never able to get the system to stay up long enough to start the array in maintenance mode. I replaced the motherboard, but was still having the same issue. Thankfully I still had an old AM4 CPU kicking around, so I put that into the system and everything looks stable now. Time to RMA my 18 month old 5700G CPU. Part of my troubleshooting yesterday I replaced my USB, but that one seems to have issue dropping when starting the array (diagnostics attached). I've tried multiple USB ports too. I bought a new key, but now I'm getting an error that I've replaced my USB key twice over the past year and I can't update the key for the new USB key. I opened a support case to hopefully allow me to update the key to either the new USB key or the original good USB that is now blacklisted.
homeserver-diagnostics-20240330-1248.zip
-
bisk's post in RetroNAS - Issues accessing shares from VM created with SpaceinvaderOne Docker was marked as the answerI was able to resolve the issue by going into the RetroNAS Config, going to settings and setting the password. I reused the same password, but it looks like the samba service needs to have the password set after it's installed.