rangusT

After a couple of Unraid updates I stopped experiencing this behavior. I attributed it to the updates but never found a conclusive answer.

I recently bought some new gear to add 10gbe to my unraid server and pc client. I have an Intel x520 sfp+ card on both sides and are connected to each other via an spf switch. I have an nvme drive in the server which I benchmarked using the DiskSpeed docker and got 2 gigabyte per second read and 2.7 write. I also have an nvme on my Windows PC so that should not be a bottleneck. I shared the drive using the unassigned devices plugin and found the max speed I can hit is about 250MBps uploading to the server and 400MBps downloading from the server. I was expecting speeds closer to the link max at 1GBps. I installed iperf3 on the server and get around 5 Gbps or 7 Gbps with the -R flag on 1 thread. If I up the threads to 3 or more iperf3 will saturate the connection. I'm not really sure where to start. There are a ton of threads on the forum with various advice surrounding 10gbe but nothing conclusive in improving the transfer speeds. morioh-diagnostics-20240107-2002.zip

I started experiencing a very bizarre issue recently. I woke up one morning to find that my entire network was down. Initially I assumed an ISP outage but found that I was still able to connect to my VPN (the VPN server runs from my router, not Unraid) from my phone via 5g. After much experimenting I discovered that once I unplugged the ethernet from my Unraid box my network instantly came back online. It has since happened two more times and pulling the ethernet brought my network back online both times. I want to say this started happening after upgrading to 6.12.0 but I am not completely confident in that timeline. I have since upgraded to the latest 6.12.3 and still experienced the issue. I can provide diagnostics but I'm not sure how useful they'll be. Once this issue occurs I am unable to access Unraid until I hard boot the server. I connected an hdmi to attempt to see the console but I can't get video until I hard boot the server. I normally run the server headless. I am unable to get network access to the server as well until a hard boot is performed. I'm hoping to find some advice on how to troubleshoot this issue. morioh-diagnostics-20230720-2008.zip

I started the rebuild as you suggested. Now, a different disk is throwing a significant number of errors. I attached diagnostics.

Unfortunately I didn't think to grab diagnostics before shutting down the system. In the main tab there were counts in the errors column on the affected drives. I want to say between 4-5000 on the parity2 and a few hundred on disk5. I'm assuming these errors triggered the disable. If I do a rebuild on top, which way would be safest? Parity first, or data drive first? Would it make sense to use one of the empty drives to rebuild into rather than on top of the existing drives?

I noticed today that two of my drives are marked as disabled. One of them is a parity drive, the other is a data drive in the array. I am running dual parity. I am looking for advice on properly assessing whether my drives are faulty and needing to be replaced. I ran short SMART tests on both drives and that came back normal. Also of note, I have two extra drives that are currently in the array but empty, so I could repurpose these to replace the two disabled drives if they are bad. If I need to do that, what order would be best to tackle this? Party or data drive first? I have not had a drive failure before in unraid, so I don't want to take any uneducated steps that could permanently lose data.

Are people storing their plots on storage that's part of the array or on unassigned devices?

I'm running an older motherboard. I am on the latest bios update, from 2018.

I've been battling with an issue where the network on my unraid box intermittently comes up at boot. I can't seem to find any commands that will bring up the eth0 via terminal. Only rebooting and crossing my fingers seems to work. I believed the issue to be my onboard nics had failed. I installed an Intel pcie nic and that worked well for a couple of months. I rebooted the server today and the box was isolated. I logged in via the bmc which always keeps its connection. My syslog is littered with firmware errors related to one of the cards. I'm not sure if that's the onboard or pci card. A while back I attempted to update the firmware on the onboard nic but was unable to due to the version of the efi shell being too old to work with Intel's utilities. I have also rebuilt my unraid install from scratch. This started happening on a previous stable build. I moved over to beta builds to see if that helped but it's still exhibiting this issue. Hoping someone can help point me in the right direction.

I take it you're suggesting that I collect some syslogs. I believe that I already had syslog collection turned on luckily. I'm less sure how to get them off the system. I want to say I had them collecting onto my cache ssd. The issue still stands that I cannot get even a newly built flash drive to boot with networking to be able to access the share on the cache.

Topic no longer needed

I'm looking for some help troubleshooting an issue that recently came up on my server. The symptom is that my ethernet connection drops out. I have two onboard ethernet ports and both drop at the same time. My motherboard has a third port for the bmc and that always stays up so I am able to connect and see that the local cli is still functional. The ethernet always returns after rebooting the server. I pulled the logs and every time the ethernet drops I get errors like this. I attempted to research the Received ECC Err, initiating reset errors but came up short on information. I was running Unraid 6.8.3 when this started happening and I upgraded to 6.9.0-beta22 as a troubleshooting step. Since the upgrade, my system was online for nearly a week with no drops when all of a sudden it happened again today.

I am looking for a way to suppress a specific type of notification. I realize that I can turn off notifications by category but I'm looking for something more granular. Specifically, I want to suppress a single type of notification that my UPS generates. The notification is an alert type. I don't want to silence the entire category and risk missing something that is actually important.

I am booting from usb2 from the onboard ports. My motherboard does not have usb3. Here are the diagnostics attached. morioh-diagnostics-20200408-1525.zip

I just upgraded from 6.8.2 to 6.8.3. The server failed to boot after the upgrade. I rebuilt the flash drive from the creator to 6.8.2 and copied over the config folder, which was backed up immediately before the upgrade. I am booting into Unraid but it doesn't detect my drive order. I don't have a screenshot of my order, but my parity drive is the largest drive and I have two other drives in the array. So it's pretty easy to try both configurations. It seems to want to rebuild the parity and warns All existing data on this device will be OVERWRITTEN when array is Started on the parity drive. Should I be able to re-add my drives without rebuilding parity?

My internet connection is metered to 1tb. Over the past couple of months I've been blowing through the cap. I have a hunch that it is deluge and duplicati and I have altered settings on those to limit their usage. This got me thinking about how to monitor my docker bandwidth usage. I'm looking for some advice on how to monitor data usage of my docker containers at an individual level.

Getting the same issue here as Fiservedpi.

I can't know for sure since I don't have logs from the router. It's the most likely explanation and I'm comfortable with it. That link I posted above shows that Netgear Armor will scan IOT devices on the network for vulnerabilities and this appears to be that exact behavior and the fact that it came from the router's IP makes sense to me.

That's an interesting point. I had enabled the trial of Netgear's new Netgear Armor suite that runs from the router itself. https://community.netgear.com/t5/NETGEAR-Armor/Check-your-Smart-Home-Devices-For-Vulnerabilities-with-NETGEAR/td-p/1770404 This link backs up your idea.

I just installed the Common Problems plugin and was alerted to a "possible hack attempt". I checked my logs and saw many entries similar to what follows. For clarity, the only port I have forwarded is one port to my qbittorrent docker and the server is not in the dmz. It appears that all of the connection attempts are from my own router. I am concerned if this is the case that my router was compromised. I did not have remote administration setup on the router's gui except for access through Netgear's app with their account through their cloud service. I use a long, randomly generated password for that account. I factory reset my router once I noticed this situation but in my haste did not check to see if any logs were available that could indicate a breach. The entirety of the logs happened within about one minute. Also of note is that I was installing a new hard drive that day so my server was rebooted and I do not have logs from before this. Can anyone help me understand these log entries? Jul 17 18:12:10 Morioh sshd[9019]: Failed none for invalid user from 192.168.1.1 port 60484 ssh2 Jul 17 18:12:10 Morioh sshd[9024]: Invalid user 666666 from 192.168.1.1 port 60485 Jul 17 18:12:10 Morioh sshd[9024]: error: Could not get shadow information for NOUSER Jul 17 18:12:10 Morioh sshd[9024]: Failed none for invalid user 666666 from 192.168.1.1 port 60485 ssh2 Jul 17 18:12:10 Morioh sshd[9019]: Failed password for invalid user from 192.168.1.1 port 60484 ssh2 Jul 17 18:12:10 Morioh sshd[9024]: Failed password for invalid user 666666 from 192.168.1.1 port 60485 ssh2 Jul 17 18:12:10 Morioh sshd[9033]: Failed password for root from 192.168.1.1 port 60487 ssh2 Jul 17 18:12:10 Morioh sshd[9037]: Failed password for root from 192.168.1.1 port 60488 ssh2 Jul 17 18:12:10 Morioh sshd[9017]: Connection closed by invalid user 192.168.1.1 port 60483 [preauth] Jul 17 18:12:10 Morioh sshd[9019]: Connection closed by invalid user 192.168.1.1 port 60484 [preauth] Jul 17 18:12:10 Morioh sshd[9024]: Connection closed by invalid user 666666 192.168.1.1 port 60485 [preauth] Jul 17 18:12:10 Morioh sshd[9033]: Connection closed by authenticating user root 192.168.1.1 port 60487 [preauth] Jul 17 18:12:10 Morioh sshd[9037]: Connection closed by authenticating user root 192.168.1.1 port 60488 [preauth] Jul 17 18:12:10 Morioh sshd[9141]: Invalid user ubnt from 192.168.1.1 port 60490 Jul 17 18:12:10 Morioh sshd[9141]: error: Could not get shadow information for NOUSER Jul 17 18:12:10 Morioh sshd[9141]: Failed none for invalid user ubnt from 192.168.1.1 port 60490 ssh2 Jul 17 18:12:10 Morioh sshd[9162]: Invalid user from 192.168.1.1 port 60492 Jul 17 18:12:10 Morioh sshd[9141]: Failed password for invalid user ubnt from 192.168.1.1 port 60490 ssh2 Jul 17 18:12:10 Morioh sshd[9162]: error: Could not get shadow information for NOUSER Jul 17 18:12:10 Morioh sshd[9162]: Failed none for invalid user from 192.168.1.1 port 60492 ssh2 Jul 17 18:12:10 Morioh sshd[9162]: Failed password for invalid user from 192.168.1.1 port 60492 ssh2 Jul 17 18:12:10 Morioh sshd[9168]: Invalid user 888888 from 192.168.1.1 port 60494 Jul 17 18:12:10 Morioh sshd[9168]: error: Could not get shadow information for NOUSER Jul 17 18:12:10 Morioh sshd[9159]: Invalid user from 192.168.1.1 port 60491 Jul 17 18:12:10 Morioh sshd[9159]: error: Could not get shadow information for NOUSER Jul 17 18:12:10 Morioh sshd[9168]: Failed none for invalid user 888888 from 192.168.1.1 port 60494 ssh2 Jul 17 18:12:10 Morioh sshd[9159]: Failed none for invalid user from 192.168.1.1 port 60491 ssh2 Jul 17 18:12:10 Morioh sshd[9168]: Failed password for invalid user 888888 from 192.168.1.1 port 60494 ssh2 Jul 17 18:12:10 Morioh sshd[9159]: Failed password for invalid user from 192.168.1.1 port 60491 ssh2 Jul 17 18:12:10 Morioh sshd[9167]: Invalid user from 192.168.1.1 port 60493 Jul 17 18:12:10 Morioh sshd[9167]: error: Could not get shadow information for NOUSER Jul 17 18:12:10 Morioh sshd[9167]: Failed none for invalid user from 192.168.1.1 port 60493 ssh2 Jul 17 18:12:10 Morioh sshd[9167]: Failed password for invalid user from 192.168.1.1 port 60493 ssh2 Jul 17 18:12:10 Morioh sshd[9141]: Connection closed by invalid user ubnt 192.168.1.1 port 60490 [preauth] Jul 17 18:12:10 Morioh sshd[9159]: Connection closed by invalid user 192.168.1.1 port 60491 [preauth] Jul 17 18:12:10 Morioh sshd[9167]: Connection closed by invalid user 192.168.1.1 port 60493 [preauth] Jul 17 18:12:10 Morioh sshd[9162]: Connection closed by invalid user 192.168.1.1 port 60492 [preauth] Jul 17 18:12:10 Morioh sshd[9168]: Connection closed by invalid user 888888 192.168.1.1 port 60494 [preauth] Jul 17 18:12:10 Morioh in.telnetd[9308]: connect from 192.168.1.1 (192.168.1.1) Jul 17 18:12:11 Morioh sshd[9303]: Invalid user admin from 192.168.1.1 port 60497 Jul 17 18:12:11 Morioh sshd[9303]: error: Could not get shadow information for NOUSER Jul 17 18:12:11 Morioh sshd[9303]: Failed none for invalid user admin from 192.168.1.1 port 60497 ssh2 Jul 17 18:12:11 Morioh sshd[9303]: Failed password for invalid user admin from 192.168.1.1 port 60497 ssh2 Jul 17 18:12:11 Morioh sshd[9298]: Failed password for root from 192.168.1.1 port 60495 ssh2 Jul 17 18:12:11 Morioh sshd[9302]: Failed password for root from 192.168.1.1 port 60496 ssh2 Jul 17 18:12:11 Morioh in.telnetd[9390]: connect from 192.168.1.1 (192.168.1.1) Jul 17 18:12:11 Morioh sshd[9298]: Connection closed by authenticating user root 192.168.1.1 port 60495 [preauth] Jul 17 18:12:11 Morioh sshd[9302]: Connection closed by authenticating user root 192.168.1.1 port 60496 [preauth] Jul 17 18:12:11 Morioh sshd[9303]: Connection closed by invalid user admin 192.168.1.1 port 60497 [preauth] Jul 17 18:12:11 Morioh sshd[9418]: Invalid user from 192.168.1.1 port 60501 Jul 17 18:12:11 Morioh sshd[9418]: error: Could not get shadow information for NOUSER Jul 17 18:12:11 Morioh sshd[9418]: Failed none for invalid user from 192.168.1.1 port 60501 ssh2 Jul 17 18:12:11 Morioh in.telnetd[9438]: connect from 192.168.1.1 (192.168.1.1) Jul 17 18:12:11 Morioh sshd[9416]: Invalid user from 192.168.1.1 port 60500 Jul 17 18:12:11 Morioh sshd[9416]: error: Could not get shadow information for NOUSER Jul 17 18:12:11 Morioh sshd[9421]: Invalid user from 192.168.1.1 port 60502 Jul 17 18:12:11 Morioh sshd[9421]: error: Could not get shadow information for NOUSER Jul 17 18:12:11 Morioh sshd[9418]: Failed password for invalid user from 192.168.1.1 port 60501 ssh2 Jul 17 18:12:11 Morioh sshd[9416]: Failed none for invalid user from 192.168.1.1 port 60500 ssh2 Jul 17 18:12:11 Morioh sshd[9421]: Failed none for invalid user from 192.168.1.1 port 60502 ssh2 Jul 17 18:12:11 Morioh sshd[9416]: Failed password for invalid user from 192.168.1.1 port 60500 ssh2 Jul 17 18:12:11 Morioh sshd[9421]: Failed password for invalid user from 192.168.1.1 port 60502 ssh2 Jul 17 18:12:11 Morioh sshd[9416]: Connection closed by invalid user 192.168.1.1 port 60500 [preauth] Jul 17 18:12:11 Morioh sshd[9418]: Connection closed by invalid user 192.168.1.1 port 60501 [preauth] Jul 17 18:12:11 Morioh sshd[9421]: Connection closed by invalid user 192.168.1.1 port 60502 [preauth]