clowncracker

For anyone who stumbles upon this, this was a Windows issue, it has nothing to do with a device being named incorrectly. This is what I had to do to in Windows to fix the issue: Windows Update → Advanced options → Delivery Optimization → Allow downloads from other PCs = Off

What’s odd is that my server name hasn’t changed in over seven years. I do have a VM called “Home Assistant,” but it’s had that name for about four years. The hostname on my network is homeassistant, though. When you say there’s a device on the network, do you mean something tied to my server? It wouldn’t be a random Wi-Fi device, right? If that’s the case, the issue would have to be related to Docker or the VM, correct?

I've noticed that this has been getting spammed in my logs lately. I'm not entirely sure what this means. Can anyone help me determine the root cause and how to stop it from happening? I've attached my diagnostics file.

Is this docker PPA based? One of my trackers has the following rules: Deluge latest allowed recommended - version 1.3.1 through 2.1.x. Due to release stream issues, Versions 2.x Sourced from their PPA (or docker based on PPA) will not work here.

The issue was the mover tuning plugin, I uninstalled it and restarted my server and it looks like things are going now.

I've moved my current cache pool (dockers, vms, system, etc) already to the array by changing the mover action on each share. When I changed the primary storage and mover actions to move to the new pool basically nothing moved. Now when I hit Mover, nothing happens. VM & Docker are both disabled.

All of a sudden my server was unaccessable on my local network. It showed as offline on my network switch. I was forced to hard reboot my server which led to an unclean shutdown. The only thing in my logs that I saw was: Oct 27 07:27:33 clowncracker ntpd[1791]: no peer for too long, server running free now I've attached my diagnostics file to help. clowncracker-diagnostics-20241027-2150.zip

I'm hoping this is good enough.

I do not, maybe I should just buy the fan to be safe. I'd rather spend $15 now then to have the card fail prematurely in the future.

I ended up rebuilding over disks 8 & 10 without issue and my server is back online and operational. I appreciate all of the help. I guess my final question is do you think the airflow for the LSI card is good or should I add another NF-A4x20 over the heatstink?

I installed the old disk 8 and unassigned them from the array. Here is the new config:

I'm just concerned because the old disk 8 had 96 relocated sector counts. I've never used a new config before and I'm not going to lie the warning on this page scares me a bit, Neither of the parity drives are on the SAS controller, so it makes me feel like doing a new config isn't the best option. What are the benefits of building a new config vs using a USB backup from before all of these issues started vs just trying to rebuild disk 8/10? Ideally I want to go with the option that will protect the data, but also something that will verify the new SAS card will actually solve my problems.

Disk 8 is emulated because it's new, but disk 10 had read/write errors from starting the array and trying to rebuild disk 8. Would a new config still be the best option? I still have the old disk 8 if that helps. The disk errors would have been in syslog-previous.txt, I restarted the server after the UDMA CRC errors came up (both boots with the new SAS card) just to see if I would get any more errors.

The new card came today, but the last time I started the system it caused a device to be disabled. At this point I'm afraid to start the array since I already have two drives that are now disabled. Is there an issue with me using a backup of my USB file to clear out the errors before I start the array? I'm afraid there is going to be data loss, even though I haven't actually tried to write anything to the array. I've attached diagnostics just in case. Is there anything that would indicate that the new SAS card wouldn't solve the problem? I did have a lot of UDMA CRC error counts when I turned the system on (not started the array), but I don't know if that's just leftover from the last SAS card.

I guess I'll bite the bullet and buy one from the art of the server. All of the drives having issues are stemming from the SAS card (old and new). After replacing the SAS cables and PSU, at this point it can only be the card or the motherboard is failing (I've tried both PCIe lanes). The motherboard dying seems unlikely, it's less than a year old at this point.

I didn't with that original card, but with the new card I added some because I read that can cause failures.

I could buy another one to test it, but looks genuine to me. It looks identical to the old one, same logo and the PCBs look the same. Unless I was using a counterfeit one for years without issue. https://www.ebay.com/itm/165949664051?_skw=9207-8i+it+mode&itmmeta=01J7RFKPNBDMB2EA8T23GDJE0X&hash=item26a35eeb33:g:GNQAAOSwkxFkwCjz

This is the controller I'm using. I replaced it with an exact copy and swapped out the cables and I'm still having issues. Of note I was using the old controller for years without issue. https://www.amazon.com/LSI-Logic-9207-8i-Controller-LSI00301/dp/B0085FT2JC

I just tried replacing the power supply entirely and I'm still running into issues. Still seeing this in my log a lot and more read errors: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)

This is a followup to this thread: I'm having issues with my server still. After rebuilding disk 5, I opted to replace disk 8 because it had 96 relocated sector errors. I ran a parity check after rebuilding disk 5 without issue. As soon as I replaced disk 8, I started running into issues. I would get read errors and UDMA CRC error count on multiple drives simultaneously. I thought maybe the issue was the SAS card or cables, since the log was being spammed with the following: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) I replaced the SAS card and cables and I'm still running into issues. I just have no idea what to do at this point. Here are my diagnostics and I've included my syslog right after replacing drive 8 before I tried replacing the cables/SAS card. The diagnostics provided are after I replaced my cables/SAS card.

Here are the new diagnostics. I also ran a SMART extended self-test on disk 5 before I started the array (I restarted the server).

I have a disk error for disk 5 and I'm exactly sure what to do. I've attached a diagnostics file. When I try to run a SMART extended self-test, nothing happens. It get the following error: Smartctl open device: /dev/sdm failed: No such device

I ended up changing the repo to lscr.io/linuxserver/jellyfin:10.8.13-1-ls10 and restored jellyfin from a backup I made last week. Solved the issue.

The latest 10.9.0 update broke one of my plugins. What repo should I use to go back to 10.8.13-1-ls10? The repo in the docker is currently: lscr.io/linuxserver/jellyfin

It ended up being a power problem, I replaced the sata power cables and the problem is now resolved.