Pmarszal

Actually, I just realized that backup is at 6.11 so the update might not be the issue. After restore from backup, unraid works, but as soon as shut down, drive stops working.

My pc only has 3.0 usb ports. It worked fine for year and a half with no issues, just right after update to latest unraid version.

Hey guys! So after upgrade to latest version my boot drive stopped working! I had a usb 3.0 and figured that was the problem. I ran out, got a usb 2.0 and ran a flash backup. It booted up correctly which just registration key missing (as expected), however I shut it down, and the usb 2.0 is now also not being recognized after first boot. Any ideas?

Where is the mover logging setting. I cannot seem to find this.

Hello, I wanted to loop back around to this issue, I am still having issues with mover not moving files. I have set all my shares to "most-free" and the mover is still not moving files to array. I am getting the follow log item when I manually click move: "Jul 18 07:44:37 unraid emhttpd: shcmd (236075): /usr/local/sbin/mover &> /dev/null &" Any insights or suggestions on how to resolve or diagnose this problem would be greatly appreciated. Thanks! unraid-diagnostics-20230718-0747.zip

I encountered a problem with the cache_transfer drive being completely filled up, and I observed a significant amount of read and write activity on drive 7. Upon examining the array, I discovered that drive 7 indicates it is full at 14TB, yet it still shows 5.8TB of free space. Considering this is a 14TB drive, I'm wondering what steps I should take to resolve this issue. unraid-diagnostics-20230711-0743.zip

Weird! Disk 7 showing up that is 14TB and its full but the free space showing up as 5.8TB?

Hey Jorge, I have all shares using all disks. I dont have preferences and all are set to "high-water" allocation method. Shouldn't the invoker move to next non-full drive?

Help needed! I've encountered a problem with my cache drive (cache_transfer - 2tb) where it is unexpectedly filled up completely. Normally, it operates smoothly and manages files efficiently and mover runs as expected. However, recently, Disk 7 has reached its maximum capacity (I think when mover stopped running correctly), and while running invoker, it seems to be reading and writing a massive amount of data on Disk 7. Is there anyone who has experience with this issue and can provide guidance on how to resolve it? Any assistance would be greatly appreciated! unraid-diagnostics-20230711-0743.zip

After binding the vfio at boot, the GPU Statistics plugin no longer functions. Is there a solution to make this plugin work while the vfio is bound? I require the binding for GPU passthrough to one of my VMs. I appreciate any assistance.

SOLVED: It was my browser crashing...

More diagnostic details: 1. Crash appears to only happen when docker is enabled. 2. Fix Common Problems is reporting: "Share appdata set to use pool cache_appdata, but files / folders exist on the cache pool Either adjust which pool this share should be using or manually move the files with Dynamix File Manager More Information" I am at this point starting over fresh with docker so all I am looking to do a fresh start of docker. I've deleted vDisk file and all appdata but everytime i enable docker - it starts, fix common problems reports above and then eventually my array crashes (as explained above post) I am also getting the following error in system log: May 16 16:34:32 unraid root: error: /webGui/include/InitCharts.php: wrong csrf_token

I got VMs to return by replacing libvirt. Thanks! Another issue is that my server array freezes and have to restart. The server becomes unresponsive with the unraid "wait" logo. I can click through the tabs but everything becomes unresponsive, including running a diagnostic. Attached is a log after restart and starting array. I appriciate all the help @JorgeB and @itimpi as I wouldnt even have gotten this far without the community. unraid-diagnostics-20230516-1312.zip

I have a copy of the libvert. How do I add old libvert I unfortunately don’t have old appdata

I did take a flash backup from unraid.net prior to all this... if that helps.. but unsure what that would do.

I believe I have worsened the situation, guys. Upon starting, I noticed that all VMs and Docker applications are nowhere to be found. When I explore the directory "/mnt/user/domains," I can locate the VMs. Similarly, when I browse through "/mnt/user/system/docker," I can see the docker.img file. However, when I access the appdata directory, only krusader is visible. I am convinced that I have completely messed up everything! Sigh... I deeply regret my actions. unraid-diagnostics-20230516-1042.zip

This is a link h430 user manual?

Sorry! Might be a stupid question but, how do I do that once assigned. obviously the “cache” drive I just click format but the other one is assigned and doesn’t ask to be reformatted.

The following two were in a pool together: Cache - Samsung_SSD_870_QVO_2TB_S6R4NJOR610134Y-2 Cache_appdata - SAMSUNG_MZVL2512HCJQ-00B00_S675NUOTA07380 ”Cache” drive needs to be formatted and the “cache_appdata” drive had the data left behind prior to new config. I am looking to keep them as separate pools, one as cache (2tb) and the other is going to be used to hold appdata on the cache_appdata

Sorry for late reply, attached is the diagnostic file. unraid-diagnostics-20230515-1639.zip

Hello everyone, I'm facing an issue with my Unraid server and I could use some help. Recently, I made a mistake by adding a cache drive to my pool that was only a fraction of the size of my other cache drives. Now I'm trying to remove this "smaller" cache drive from the pool, and here are the steps I took: First, I moved all the data from the cache drives by setting every share to YES and running the mover. After the mover completed, I disabled the use of cache drives. I also created a new configuration to ensure that the array drives were preserved. Next, I removed the "smaller" cache drive from the pool and created a new pool. However, the old cache pool required me to format it, which was not an issue since I had already moved everything to the array. The problem is that the "smaller" cache drive I removed still has some files on it, such as appdata and system files. Currently, the parity drive is in the process of rebuilding, and it will take a couple of days to complete. But I'm starting to wonder if I should have formatted the "smaller" drive before starting up the array, considering that there were still some remaining data on it. Did I make a mistake in the removal process, and how can I resolve this situation without creating further complications? I would greatly appreciate any assistance you can provide. Thank you!

Thanks guys! Took lots of learning but flashed to IT mode and everything is working like a charm!

Im getting the following error when running OpenVPN-Client: Error: ipv4: FIB table does not exist. Im also getting the following warnings: 2022-01-19 19:40:43 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1582', remote='link-mtu 1569' 2022-01-19 19:40:43 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1532', remote='tun-mtu 1500' 2022-01-19 19:40:43 WARNING: 'comp-lzo' is present in local config but missing in remote config, local='comp-lzo' 2022-01-19 19:40:43 WARNING: 'auth' is used inconsistently, local='auth [null-digest]', remote='auth SHA256' 2022-01-19 19:40:43 WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128' 2022-01-19 19:40:44 WARNING: You have specified redirect-gateway and redirect-private at the same time (or the same option multiple times). This is not well supported and may lead to unexpected results 2022-01-19 19:40:44 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this How can I resolve these?

Need help here on best strategy: I’m going to be moving unraid to a r720 and DAS. R720 - will hold the cache drive SC200 - will hold my array drives I have strategy on transferring array drives so I don’t have issues there as it’s plug and play with my hba card. My only concern is the following: R720 required configuring Raid0 and reformat when connecting new drives. Since I will be connecting my cache (ssd) into the r720, I will need to configure as raid0 and format the cache drive. If I move all items off the cache drives before the move, will I have any issues with configuration of array (after configuring raid0 and formatting)? Will the new server recognize serial and just continue to use this as cache drive? Is a better option for create new config (before the move) without the cache drive? My concern with removing the cache drive is that I’ll most likely have to create new parity rebuild, which I wouldn’t want to do!

Hello, Newb here needing answers! I recently changed my router and same day noticed the following: What is going on? Attempt at a hack? What are the proper steps to secure my network? I turned off SSH and TELNET. HELP! Dec 19 22:14:52 unraid sshd[28336]: Connection from 192.168.1.1 port 53921 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid vsftpd[28335]: connect from 192.168.1.1 (192.168.1.1) Dec 19 22:14:52 unraid in.telnetd[28334]: connect from 192.168.1.1 (192.168.1.1) Dec 19 22:14:52 unraid sshd[28336]: error: kex_exchange_identification: Connection closed by remote host Dec 19 22:14:52 unraid sshd[28336]: Connection closed by 192.168.1.1 port 53921 Dec 19 22:14:52 unraid sshd[28361]: Connection from 192.168.1.1 port 53989 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28367]: Connection from 192.168.1.1 port 53999 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28371]: Connection from 192.168.1.1 port 54001 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28357]: Connection from 192.168.1.1 port 53983 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28363]: Connection from 192.168.1.1 port 53975 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28366]: Connection from 192.168.1.1 port 53991 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28368]: Connection from 192.168.1.1 port 53985 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28362]: Connection from 192.168.1.1 port 53993 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28370]: Connection from 192.168.1.1 port 53995 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28360]: Connection from 192.168.1.1 port 53973 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28359]: Connection from 192.168.1.1 port 53977 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28352]: Connection from 192.168.1.1 port 53971 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28358]: Connection from 192.168.1.1 port 53981 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28365]: Connection from 192.168.1.1 port 53987 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28364]: Connection from 192.168.1.1 port 53979 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:52 unraid sshd[28369]: Connection from 192.168.1.1 port 53997 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:56 unraid sshd[28361]: Invalid user admin from 192.168.1.1 port 53989 Dec 19 22:14:56 unraid sshd[28361]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:56 unraid sshd[28361]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:56 unraid sshd[28371]: Invalid user admin from 192.168.1.1 port 54001 Dec 19 22:14:56 unraid sshd[28371]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:56 unraid sshd[28371]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28363]: Invalid user from 192.168.1.1 port 53975 Dec 19 22:14:57 unraid sshd[28363]: Failed none for invalid user from 192.168.1.1 port 53975 ssh2 Dec 19 22:14:57 unraid sshd[28368]: Invalid user admin from 192.168.1.1 port 53985 Dec 19 22:14:57 unraid sshd[28358]: Invalid user admin from 192.168.1.1 port 53981 Dec 19 22:14:57 unraid sshd[28363]: Bad packet length 3764872703. [preauth] Dec 19 22:14:57 unraid sshd[28363]: ssh_dispatch_run_fatal: Connection from invalid user 192.168.1.1 port 53975: message authentication code incorrect [preauth] Dec 19 22:14:57 unraid sshd[28360]: Invalid user pi from 192.168.1.1 port 53973 Dec 19 22:14:57 unraid sshd[28369]: Invalid user admin from 192.168.1.1 port 53997 Dec 19 22:14:57 unraid sshd[28367]: Invalid user admin from 192.168.1.1 port 53999 Dec 19 22:14:57 unraid sshd[28357]: Invalid user admin from 192.168.1.1 port 53983 Dec 19 22:14:57 unraid sshd[28370]: Invalid user admin from 192.168.1.1 port 53995 Dec 19 22:14:57 unraid sshd[28366]: Invalid user admin from 192.168.1.1 port 53991 Dec 19 22:14:57 unraid sshd[28365]: Invalid user admin from 192.168.1.1 port 53987 Dec 19 22:14:57 unraid sshd[28359]: Invalid user admin from 192.168.1.1 port 53977 Dec 19 22:14:57 unraid sshd[28352]: Invalid user pi from 192.168.1.1 port 53971 Dec 19 22:14:57 unraid sshd[28368]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28368]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28733]: Connection from 192.168.1.1 port 54007 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:57 unraid sshd[28358]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28364]: Invalid user admin from 192.168.1.1 port 53979 Dec 19 22:14:57 unraid sshd[28360]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28360]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28369]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28367]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28357]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28370]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28370]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28366]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28365]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28365]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28359]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28359]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28352]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28352]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28364]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28364]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28362]: Invalid user admin from 192.168.1.1 port 53993 Dec 19 22:14:57 unraid sshd[28362]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28362]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28733]: Invalid user admin from 192.168.1.1 port 54007 Dec 19 22:14:57 unraid sshd[28733]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:57 unraid sshd[28733]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:57 unraid sshd[28361]: Failed password for invalid user admin from 192.168.1.1 port 53989 ssh2 Dec 19 22:14:58 unraid sshd[28371]: Failed password for invalid user admin from 192.168.1.1 port 54001 ssh2 Dec 19 22:14:58 unraid sshd[28361]: Bad packet length 604003085. [preauth] Dec 19 22:14:58 unraid sshd[28361]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53989: message authentication code incorrect [preauth] Dec 19 22:14:58 unraid sshd[28772]: Connection from 192.168.1.1 port 54041 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:58 unraid sshd[28772]: Invalid user admin from 192.168.1.1 port 54041 Dec 19 22:14:58 unraid sshd[28772]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:58 unraid sshd[28772]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:58 unraid sshd[28371]: Bad packet length 3850756272. [preauth] Dec 19 22:14:58 unraid sshd[28371]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 54001: message authentication code incorrect [preauth] Dec 19 22:14:58 unraid sshd[28776]: Connection from 192.168.1.1 port 54043 on 192.168.1.12 port 22 rdomain "" Dec 19 22:14:58 unraid sshd[28776]: Invalid user admin from 192.168.1.1 port 54043 Dec 19 22:14:58 unraid sshd[28776]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:14:58 unraid sshd[28776]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:14:59 unraid sshd[28368]: Failed password for invalid user admin from 192.168.1.1 port 53985 ssh2 Dec 19 22:14:59 unraid sshd[28360]: Failed password for invalid user pi from 192.168.1.1 port 53973 ssh2 Dec 19 22:14:59 unraid sshd[28358]: Failed password for invalid user admin from 192.168.1.1 port 53981 ssh2 Dec 19 22:14:59 unraid sshd[28369]: Failed password for invalid user admin from 192.168.1.1 port 53997 ssh2 Dec 19 22:14:59 unraid sshd[28367]: Failed password for invalid user admin from 192.168.1.1 port 53999 ssh2 Dec 19 22:14:59 unraid sshd[28357]: Failed password for invalid user admin from 192.168.1.1 port 53983 ssh2 Dec 19 22:14:59 unraid sshd[28370]: Failed password for invalid user admin from 192.168.1.1 port 53995 ssh2 Dec 19 22:14:59 unraid sshd[28359]: Failed password for invalid user admin from 192.168.1.1 port 53977 ssh2 Dec 19 22:14:59 unraid sshd[28366]: Failed password for invalid user admin from 192.168.1.1 port 53991 ssh2 Dec 19 22:14:59 unraid sshd[28365]: Failed password for invalid user admin from 192.168.1.1 port 53987 ssh2 Dec 19 22:14:59 unraid sshd[28364]: Failed password for invalid user admin from 192.168.1.1 port 53979 ssh2 Dec 19 22:14:59 unraid sshd[28352]: Failed password for invalid user pi from 192.168.1.1 port 53971 ssh2 Dec 19 22:14:59 unraid sshd[28362]: Failed password for invalid user admin from 192.168.1.1 port 53993 ssh2 Dec 19 22:14:59 unraid sshd[28733]: Failed password for invalid user admin from 192.168.1.1 port 54007 ssh2 Dec 19 22:15:00 unraid sshd[28772]: Failed password for invalid user admin from 192.168.1.1 port 54041 ssh2 Dec 19 22:15:00 unraid sshd[28772]: Bad packet length 4075915883. [preauth] Dec 19 22:15:00 unraid sshd[28772]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 54041: message authentication code incorrect [preauth] Dec 19 22:15:00 unraid sshd[3287]: error: beginning MaxStartups throttling Dec 19 22:15:00 unraid sshd[3287]: drop connection #15 from [192.168.1.1]:54047 on [192.168.1.12]:22 past MaxStartups Dec 19 22:15:00 unraid sshd[28776]: Failed password for invalid user admin from 192.168.1.1 port 54043 ssh2 Dec 19 22:15:00 unraid sshd[28776]: Bad packet length 921309574. [preauth] Dec 19 22:15:00 unraid sshd[28776]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 54043: message authentication code incorrect [preauth] Dec 19 22:15:00 unraid sshd[28815]: Connection from 192.168.1.1 port 54049 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:00 unraid sshd[28352]: Bad packet length 1359432112. [preauth] Dec 19 22:15:00 unraid sshd[28360]: Bad packet length 1589818681. [preauth] Dec 19 22:15:00 unraid sshd[28360]: ssh_dispatch_run_fatal: Connection from invalid user pi 192.168.1.1 port 53973: message authentication code incorrect [preauth] Dec 19 22:15:00 unraid sshd[28352]: ssh_dispatch_run_fatal: Connection from invalid user pi 192.168.1.1 port 53971: message authentication code incorrect [preauth] Dec 19 22:15:00 unraid sshd[3287]: drop connection #13 from [192.168.1.1]:54053 on [192.168.1.12]:22 past MaxStartups Dec 19 22:15:00 unraid sshd[28817]: Connection from 192.168.1.1 port 54055 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28815]: Invalid user admin from 192.168.1.1 port 54049 Dec 19 22:15:01 unraid sshd[28815]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:15:01 unraid sshd[28815]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:15:01 unraid sshd[28359]: Bad packet length 1920080390. [preauth] Dec 19 22:15:01 unraid sshd[28368]: Bad packet length 4184988466. [preauth] Dec 19 22:15:01 unraid sshd[28368]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53985: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28359]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53977: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28357]: Bad packet length 1795377332. [preauth] Dec 19 22:15:01 unraid sshd[28357]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53983: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28367]: Bad packet length 1107808729. [preauth] Dec 19 22:15:01 unraid sshd[28367]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53999: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28365]: Bad packet length 789643454. [preauth] Dec 19 22:15:01 unraid sshd[28365]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53987: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28366]: Bad packet length 2221404649. [preauth] Dec 19 22:15:01 unraid sshd[28366]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53991: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28358]: Bad packet length 1974245784. [preauth] Dec 19 22:15:01 unraid sshd[28358]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53981: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28370]: Bad packet length 1081036157. [preauth] Dec 19 22:15:01 unraid sshd[28370]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53995: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28369]: Bad packet length 1012252943. [preauth] Dec 19 22:15:01 unraid sshd[28369]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53997: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[3287]: exited MaxStartups throttling after 00:00:01, 2 connections dropped Dec 19 22:15:01 unraid sshd[28364]: Bad packet length 602478263. [preauth] Dec 19 22:15:01 unraid sshd[28364]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53979: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28863]: Connection from 192.168.1.1 port 54065 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28867]: Connection from 192.168.1.1 port 54079 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28868]: Connection from 192.168.1.1 port 54069 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28869]: Connection from 192.168.1.1 port 54071 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28865]: Connection from 192.168.1.1 port 54061 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28866]: Connection from 192.168.1.1 port 54067 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28864]: Connection from 192.168.1.1 port 54063 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28872]: Connection from 192.168.1.1 port 54075 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28870]: Connection from 192.168.1.1 port 54077 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28871]: Connection from 192.168.1.1 port 54073 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:01 unraid sshd[28362]: Bad packet length 2295812421. [preauth] Dec 19 22:15:01 unraid sshd[28362]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 53993: message authentication code incorrect [preauth] Dec 19 22:15:01 unraid sshd[28817]: Invalid user admin from 192.168.1.1 port 54055 Dec 19 22:15:01 unraid sshd[28817]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:15:01 unraid sshd[28817]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:15:01 unraid sshd[28885]: Connection from 192.168.1.1 port 54083 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:02 unraid sshd[28733]: Bad packet length 608058997. [preauth] Dec 19 22:15:02 unraid sshd[28733]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 54007: message authentication code incorrect [preauth] Dec 19 22:15:02 unraid sshd[28912]: Connection from 192.168.1.1 port 54089 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:03 unraid sshd[28815]: Failed password for invalid user admin from 192.168.1.1 port 54049 ssh2 Dec 19 22:15:03 unraid sshd[28817]: Failed password for invalid user admin from 192.168.1.1 port 54055 ssh2 Dec 19 22:15:04 unraid sshd[28864]: Invalid user vagrant from 192.168.1.1 port 54063 Dec 19 22:15:04 unraid sshd[28864]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:15:04 unraid sshd[28864]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:15:04 unraid sshd[28865]: Invalid user admin from 192.168.1.1 port 54061 Dec 19 22:15:04 unraid sshd[28865]: pam_unix(sshd:auth): check pass; user unknown Dec 19 22:15:04 unraid sshd[28865]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 Dec 19 22:15:04 unraid sshd[28868]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28867]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28872]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28866]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28863]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28871]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28885]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:04 unraid sshd[28912]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root Dec 19 22:15:05 unraid sshd[28815]: Bad packet length 1975614561. [preauth] Dec 19 22:15:05 unraid sshd[28815]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 54049: message authentication code incorrect [preauth] Dec 19 22:15:05 unraid sshd[29182]: Connection from 192.168.1.1 port 54123 on 192.168.1.12 port 22 rdomain "" Dec 19 22:15:05 unraid sshd[28817]: Bad packet length 2733480275. [preauth] Dec 19 22:15:05 unraid sshd[28817]: ssh_dispatch_run_fatal: Connection from invalid user admin 192.168.1.1 port 54055: message authentication code incorrect [preauth] Dec 19 22:15:05 unraid sshd[3287]: error: beginning MaxStartups throttling Dec 19 22:15:05 unraid sshd[3287]: drop connection #13 from [192.168.1.1]:54125 on [192.168.1.12]:22 past MaxStartups Dec 19 22:15:05 unraid sshd[29182]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.1 user=root .... Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR guest, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR user, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR 666666, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR guest, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR user, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR user, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR user, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR 888888, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR user, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR mother, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR administrator, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR Administrator, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR tech, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR administrator, Authentication failure Dec 19 22:15:37 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR ubnt, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR support, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR info, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR oracle, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR default, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR ftp, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR ftp, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR supervisor, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR Carlisle, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR public, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR admin1, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR security, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR Darlington, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR ghost, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR info, Authentication failure Dec 19 22:15:44 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR ftpuser, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR adm, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR julian, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR Kirton, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR mysql, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR git, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR joggler, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR sybase, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR nagios, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR mike, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR 1234, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR cop, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR Aldershot, Authentication failure Dec 19 22:15:51 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR backup, Authentication failure Dec 19 22:15:52 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR nobody, Authentication failure Dec 19 22:15:52 unraid login: FAILED LOGIN 1 FROM 192.168.1.1 FOR Bedford, Authentication failure