Nunong21 Posted January 21, 2020 Share Posted January 21, 2020 Hello everyone, First of all, I'm new to unraid so still learning I've been using a PC with Ubuntu Server for a year for storage, docker images, media server, etc., but now I wanted to try unraid. I installed unraid two days ago and I'm still installing all the docker containers that I need, migrating my files.... This is my setup: M/B: ASUSTeK COMPUTER INC. H81M-K Version Rev X.0x - s/n: 141134737523395 BIOS: American Megatrends Inc. Version 3602. Dated: 03/26/2018 CPU: Intel® Core™ i7-4790 CPU @ 3.60GHz HVM: Disabled IOMMU: Disabled Cache: 256 KiB, 1024 KiB, 8192 KiB Memory: 12 GiB DDR3 (max. installable capacity 16 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 4.19.94-Unraid x86_64 OpenSSL: 1.1.1d So far, I've had my unraid server crashing 2 times. Basically, the server becomes unusable, docker images wont open, can't even access the unraid panel. The first time was when I was moving 400gb of my old files to a shared folder. The server just stop responding, and then I had to manually shutdown the computer. In here I could see some errors about the CPU I think, maybe it was a bit overloaded. The second time, I went to sleep and left some files copying to my Nextcloud docker. Unfortutally I forgot I has the Nextcloud folder in my cache disk and it got full with only 5gb left or something. When I woke up, all my services were gone and couldn't again access the server, nor unraid admin panel. Again, I had to shut it down. Is there any good practices to avoid this, is this an error? Can someone please guide me or give me some details? Would really appreciate it, thank you! retronwarz-diagnostics-20200121-0829.zip Quote Link to comment
JorgeB Posted January 21, 2020 Share Posted January 21, 2020 See here to enable syslog server/mirror to see if it catches something: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601 Quote Link to comment
testdasi Posted January 21, 2020 Share Posted January 21, 2020 You need to turn on syslog server and either save it to cache or mirror to flash. Then when the freeze / crash happens, it can provide some clues as to what happened as it contains log pre and post crash. Diagnostics that's taken after a crash (and reboot) tends to be of little use since they don't contain details pre-crash i.e. what caused it. Your 2nd problem is sort of known. Whenever cache drive is completely filled up, strange things happen. You need to look at all your shares and make sure you genuinely needs it to use cache. A few tips: If a docker points to a share that is Cache = Only, you should map it to /mnt/cache/[share] instead of /mnt/user/[share]. That will bypass shfs which tends to improve stability and performance, especially under heavy IO. You shouldn't be using Cache = Prefer unless you intentionally want it to overflow and have your mover scheduler set up properly to cater for that. The mover can stop working when cache drive is completely filled up, rendering Cache = Prefer useless. Cache = Yes is rarely ever required with modern HDD's and network-limited transfers. For very large transfers, always have Cache = No and turn on reconstruct write (aka Turbo Write). Quote Link to comment
Nunong21 Posted January 21, 2020 Author Share Posted January 21, 2020 Thank you, Activated the syslog and disabled all the cache prefer from every shared folder that didn't really need it. I'll keep an eye out for any crash that may occur, thank you! Quote Link to comment
Nunong21 Posted January 21, 2020 Author Share Posted January 21, 2020 (edited) Unfortunatelly I don't think the syslog is logging anything. The server just crashed now while I was sending some 30gb to nextcloud. It seems I have my CPU running @ 100% I then SSH to the server, ran `top` and this is what I get: In my unraid backend I can move by some menus, but I can't do anything. The Diagnostics doesn't create any file, the docker menu doesn't get fetch any results... This time I have 150GB free on my cache Note: I have docker-compose and my containers are created from the docker-compose that I add as attach Edit: Fount the following log in the Tools: Jan 21 11:29:33 Retronwarz kernel: BUG: unable to handle kernel paging request at 0000400000000014 Jan 21 11:29:33 Retronwarz kernel: PGD 0 P4D 0 Jan 21 11:29:33 Retronwarz kernel: Oops: 0000 [#1] SMP PTI Jan 21 11:29:33 Retronwarz kernel: CPU: 1 PID: 20249 Comm: unraidd1 Not tainted 4.19.94-Unraid #1 Jan 21 11:29:33 Retronwarz kernel: Hardware name: ASUS All Series/H81M-K, BIOS 3602 03/26/2018 Jan 21 11:29:33 Retronwarz kernel: RIP: 0010:bio_endio+0x5/0xc2 Jan 21 11:29:33 Retronwarz kernel: Code: 21 48 8b 5d 50 48 89 ef e8 01 e8 ff ff 48 89 ef e8 b2 e7 ff ff 48 89 ef e8 1a f5 ff ff 48 89 dd eb da 5b 5d c3 55 48 89 fd 53 <80> 7d 14 00 79 19 8b 45 40 85 c0 7f 02 0f 0b f0 ff 4d 40 0f 85 a1 Jan 21 11:29:33 Retronwarz kernel: RSP: 0018:ffffc90001cffd98 EFLAGS: 00010206 Jan 21 11:29:33 Retronwarz kernel: RAX: 0000000000000000 RBX: ffff8882ba250900 RCX: 0000000000001000 Jan 21 11:29:33 Retronwarz kernel: RDX: 0000000000003000 RSI: 0000000000000000 RDI: 0000400000000000 Jan 21 11:29:33 Retronwarz kernel: RBP: 0000400000000000 R08: ffff88830e7795d0 R09: 0000000000000000 Jan 21 11:29:33 Retronwarz kernel: R10: 0000000000001000 R11: ffff88830fc4f000 R12: 0000000000000000 Jan 21 11:29:33 Retronwarz kernel: R13: ffff8882ba2508f0 R14: ffff8882ba250900 R15: 0000000000000001 Jan 21 11:29:33 Retronwarz kernel: FS: 0000000000000000(0000) GS:ffff888313c40000(0000) knlGS:0000000000000000 Jan 21 11:29:33 Retronwarz kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 21 11:29:33 Retronwarz kernel: CR2: 0000400000000014 CR3: 0000000001e0a004 CR4: 00000000001606e0 Jan 21 11:29:33 Retronwarz kernel: Call Trace: Jan 21 11:29:33 Retronwarz kernel: unraidd+0x10f8/0x136e [md_mod] Jan 21 11:29:33 Retronwarz kernel: ? __switch_to_asm+0x35/0x70 Jan 21 11:29:33 Retronwarz kernel: ? __schedule+0x4f7/0x548 Jan 21 11:29:33 Retronwarz kernel: ? md_thread+0xee/0x115 [md_mod] Jan 21 11:29:33 Retronwarz kernel: ? rmw5_write_data+0x172/0x172 [md_mod] Jan 21 11:29:33 Retronwarz kernel: md_thread+0xee/0x115 [md_mod] Jan 21 11:29:33 Retronwarz kernel: ? wait_woken+0x6a/0x6a Jan 21 11:29:33 Retronwarz kernel: ? md_open+0x2c/0x2c [md_mod] Jan 21 11:29:33 Retronwarz kernel: kthread+0x10c/0x114 Jan 21 11:29:33 Retronwarz kernel: ? kthread_park+0x89/0x89 Jan 21 11:29:33 Retronwarz kernel: ret_from_fork+0x35/0x40 Jan 21 11:29:33 Retronwarz kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod nct6775 hwmon_vid bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd i2c_i801 glue_helper i2c_core r8169 intel_cstate intel_uncore video intel_rapl_perf backlight wmi_bmof realtek ahci pcc_cpufreq libahci thermal button fan wmi Jan 21 11:29:33 Retronwarz kernel: CR2: 0000400000000014 Jan 21 11:29:33 Retronwarz kernel: ---[ end trace 5c28ff519feb737d ]--- Jan 21 11:29:33 Retronwarz kernel: RIP: 0010:bio_endio+0x5/0xc2 Jan 21 11:29:33 Retronwarz kernel: Code: 21 48 8b 5d 50 48 89 ef e8 01 e8 ff ff 48 89 ef e8 b2 e7 ff ff 48 89 ef e8 1a f5 ff ff 48 89 dd eb da 5b 5d c3 55 48 89 fd 53 <80> 7d 14 00 79 19 8b 45 40 85 c0 7f 02 0f 0b f0 ff 4d 40 0f 85 a1 Jan 21 11:29:33 Retronwarz kernel: RSP: 0018:ffffc90001cffd98 EFLAGS: 00010206 Jan 21 11:29:33 Retronwarz kernel: RAX: 0000000000000000 RBX: ffff8882ba250900 RCX: 0000000000001000 Jan 21 11:29:33 Retronwarz kernel: RDX: 0000000000003000 RSI: 0000000000000000 RDI: 0000400000000000 Jan 21 11:29:33 Retronwarz kernel: RBP: 0000400000000000 R08: ffff88830e7795d0 R09: 0000000000000000 Jan 21 11:29:33 Retronwarz kernel: R10: 0000000000001000 R11: ffff88830fc4f000 R12: 0000000000000000 Jan 21 11:29:33 Retronwarz kernel: R13: ffff8882ba2508f0 R14: ffff8882ba250900 R15: 0000000000000001 Jan 21 11:29:33 Retronwarz kernel: FS: 0000000000000000(0000) GS:ffff888313c40000(0000) knlGS:0000000000000000 Jan 21 11:29:33 Retronwarz kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 21 11:29:33 Retronwarz kernel: CR2: 0000400000000014 CR3: 0000000001e0a004 CR4: 00000000001606e0 Jan 21 11:29:33 Retronwarz kernel: ------------[ cut here ]------------ Jan 21 11:29:33 Retronwarz kernel: WARNING: CPU: 1 PID: 20249 at kernel/exit.c:778 do_exit+0x64/0x922 Jan 21 11:29:33 Retronwarz kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod nct6775 hwmon_vid bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd i2c_i801 glue_helper i2c_core r8169 intel_cstate intel_uncore video intel_rapl_perf backlight wmi_bmof realtek ahci pcc_cpufreq libahci thermal button fan wmi Jan 21 11:29:33 Retronwarz kernel: CPU: 1 PID: 20249 Comm: unraidd1 Tainted: G D 4.19.94-Unraid #1 Jan 21 11:29:33 Retronwarz kernel: Hardware name: ASUS All Series/H81M-K, BIOS 3602 03/26/2018 Jan 21 11:29:33 Retronwarz kernel: RIP: 0010:do_exit+0x64/0x922 Jan 21 11:29:33 Retronwarz kernel: Code: 39 d0 75 1a 48 8b 48 10 48 8d 50 10 48 39 d1 75 0d 48 8b 50 20 48 83 c0 20 48 39 c2 74 0e 48 c7 c7 b1 f9 d2 81 e8 3c b1 03 00 <0f> 0b 65 8b 05 b4 2b fc 7e 25 00 ff 1f 00 48 c7 c7 01 01 d4 81 89 Jan 21 11:29:33 Retronwarz kernel: RSP: 0018:ffffc90001cffee8 EFLAGS: 00010046 Jan 21 11:29:33 Retronwarz kernel: RAX: 0000000000000024 RBX: ffff88830eefde80 RCX: 0000000000000007 Jan 21 11:29:33 Retronwarz kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff888313c564f0 Jan 21 11:29:33 Retronwarz kernel: RBP: 0000000000000009 R08: 000000000000000f R09: ffff8880000be100 Jan 21 11:29:33 Retronwarz kernel: R10: 0000000000000000 R11: 0000000000000044 R12: 0000400000000014 Jan 21 11:29:33 Retronwarz kernel: R13: ffff88830eefde80 R14: 0000000000000009 R15: 0000000000000000 Jan 21 11:29:33 Retronwarz kernel: FS: 0000000000000000(0000) GS:ffff888313c40000(0000) knlGS:0000000000000000 Jan 21 11:29:33 Retronwarz kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 21 11:29:33 Retronwarz kernel: CR2: 0000400000000014 CR3: 0000000001e0a004 CR4: 00000000001606e0 Jan 21 11:29:33 Retronwarz kernel: Call Trace: Jan 21 11:29:33 Retronwarz kernel: ? md_open+0x2c/0x2c [md_mod] Jan 21 11:29:33 Retronwarz kernel: ? kthread+0x10c/0x114 Jan 21 11:29:33 Retronwarz kernel: rewind_stack_do_exit+0x17/0x20 Jan 21 11:29:33 Retronwarz kernel: ---[ end trace 5c28ff519feb737e ]--- docker-compose.yml Edited January 21, 2020 by Nunong21 Quote Link to comment
trurl Posted January 21, 2020 Share Posted January 21, 2020 Just now getting to look at your diagnostics, and I know you have made some changes to your shares use cache setting, but I doubt you have them set up correctly now. This is unlikely to be the reason for the crashes but I thought I would comment anyway. appdata, domains, and system shares should be cache-prefer until you get them all moved to cache, then you should set them to cache-only. But mover can't move open files, so Docker and VM services would have to be disabled before attempting to move them. And in your diagnostics each of those shares had files on the array. You had another share, probably Downloads, that was prefer and that was probably how you filled cache. People are often confused about the cache settings. Prefer means prefer to keep files on cache and if any are on the array move them to cache. That share should be cache-yes. All the other shares should be cache-yes also, at least until you get all their files moved to the array, then you can set them to cache-no if you want. That is just a basic guideline. Once you better understand how you intend to use cache you can set them as you see fit. See here for more details about the nuances of the use cache setting: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=537383 You can see how much of each disk each user share is using by going to Shares - User Shares and click on Compute... for the share, or just use the Compute All button at the bottom. If it hasn't produced any results after several minutes refresh the screen. Why are you using docker-compose instead of the Unraid webUI to manage your dockers? I know there are some things that can't be easily done without docker-compose, but if you manage your dockers at the command line there are some features of the Unraid webUI for managing dockers that won't apply. Quote Link to comment
Nunong21 Posted January 21, 2020 Author Share Posted January 21, 2020 7 minutes ago, trurl said: Just now getting to look at your diagnostics, and I know you have made some changes to your shares use cache setting, but I doubt you have them set up correctly now. This is unlikely to be the reason for the crashes but I thought I would comment anyway. appdata, domains, and system shares should be cache-prefer until you get them all moved to cache, then you should set them to cache-only. But mover can't move open files, so Docker and VM services would have to be disabled before attempting to move them. And in your diagnostics each of those shares had files on the array. You had another share, probably Downloads, that was prefer and that was probably how you filled cache. People are often confused about the cache settings. Prefer means prefer to keep files on cache and if any are on the array move them to cache. That share should be cache-yes. All the other shares should be cache-yes also, at least until you get all their files moved to the array, then you can set them to cache-no if you want. That is just a basic guideline. Once you better understand how you intend to use cache you can set them as you see fit. See here for more details about the nuances of the use cache setting: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=537383 You can see how much of each disk each user share is using by going to Shares - User Shares and click on Compute... for the share, or just use the Compute All button at the bottom. If it hasn't produced any results after several minutes refresh the screen. Why are you using docker-compose instead of the Unraid webUI to manage your dockers? I know there are some things that can't be easily done without docker-compose, but if you manage your dockers at the command line there are some features of the Unraid webUI for managing dockers that won't apply. Yes, I already changed those settings, I'll just no set up te folders you said to use cache only (appdata, domains, and system). The rest is already with the cache correct. Indeed, first time mistake, and I learned from it Still, the server got that other error that I said above. Probably something to do with memory, I'll have to do a memory check once I get home. Thanks for the reply! Quote Link to comment
trurl Posted January 21, 2020 Share Posted January 21, 2020 12 minutes ago, Nunong21 said: Yes, I already changed those settings, I'll just no set up te folders you said to use cache only (appdata, domains, and system). The rest is already with the cache correct. Indeed, first time mistake, and I learned from it Still, the server got that other error that I said above. Probably something to do with memory, I'll have to do a memory check once I get home. Thanks for the reply! I knew you had changed the settings. What I am still unsure about is whether the shares that should be on cache still have files on the array. Just changing a share to cache-only will not do anything about files for that share that are already on the array, and even changing it to cache-prefer may not get them moved to cache if they are open. 26 minutes ago, trurl said: You can see how much of each disk each user share is using by going to Shares - User Shares and click on Compute... for the share, or just use the Compute All button at the bottom. If it hasn't produced any results after several minutes refresh the screen. Quote Link to comment
Nunong21 Posted January 21, 2020 Author Share Posted January 21, 2020 (edited) 8 hours ago, trurl said: I knew you had changed the settings. What I am still unsure about is whether the shares that should be on cache still have files on the array. Just changing a share to cache-only will not do anything about files for that share that are already on the array, and even changing it to cache-prefer may not get them moved to cache if they are open. Hello, I got home and tried the following: Ran memtest and one of the RAMs gave me some errors on the first pass. Then I switched the RAM for another and ran memtest again. This time I had 3 passes without any errors. Turned on the unraid server, everything booted up ok. I then opened my nextcloud web view and started moving 30gb of images. After a few minutes the server just stoped and I couldn't access the admin panel, my docker images were stoped, and I got the following errors in the screen connected to my server. The last logs I got from the server were: Jan 21 22:05:52 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:05:52 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:05:52 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:05:52 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:06:04 Retronwarz sshd[1733]: Server listening on 0.0.0.0 port 22. Jan 21 22:06:04 Retronwarz sshd[1733]: Server listening on :: port 22. Jan 21 22:06:39 Retronwarz sshd[16121]: Invalid user dp from 213.148.198.36 port 34436 Jan 21 22:06:39 Retronwarz sshd[16121]: error: Could not get shadow information for NOUSER Jan 21 22:06:39 Retronwarz sshd[16121]: Failed password for invalid user dp from 213.148.198.36 port 34436 ssh2 Jan 21 22:06:39 Retronwarz sshd[16121]: Received disconnect from 213.148.198.36 port 34436:11: Bye Bye [preauth] Jan 21 22:06:39 Retronwarz sshd[16121]: Disconnected from invalid user dp 213.148.198.36 port 34436 [preauth] Jan 21 22:06:49 Retronwarz sshd[1733]: Received signal 15; terminating. Jan 21 22:06:50 Retronwarz sshd[19972]: Failed password for root from 218.92.0.204 port 20085 ssh2 Jan 21 22:06:50 Retronwarz sshd[20152]: Server listening on 0.0.0.0 port 22. Jan 21 22:06:50 Retronwarz sshd[20152]: Server listening on :: port 22. Jan 21 22:06:50 Retronwarz sshd[19972]: Failed password for root from 218.92.0.204 port 20085 ssh2 Jan 21 22:06:50 Retronwarz sshd[19972]: Failed password for root from 218.92.0.204 port 20085 ssh2 Jan 21 22:06:51 Retronwarz sshd[19972]: Received disconnect from 218.92.0.204 port 20085:11: [preauth] Jan 21 22:06:51 Retronwarz sshd[19972]: Disconnected from authenticating user root 218.92.0.204 port 20085 [preauth] Jan 21 22:07:13 Retronwarz sshd[20829]: Invalid user wagner from 129.204.84.35 port 41816 Jan 21 22:07:13 Retronwarz sshd[20829]: error: Could not get shadow information for NOUSER Jan 21 22:07:13 Retronwarz sshd[20829]: Failed password for invalid user wagner from 129.204.84.35 port 41816 ssh2 Jan 21 22:07:13 Retronwarz sshd[20829]: Received disconnect from 129.204.84.35 port 41816:11: Bye Bye [preauth] Jan 21 22:07:13 Retronwarz sshd[20829]: Disconnected from invalid user wagner 129.204.84.35 port 41816 [preauth] Jan 21 22:07:55 Retronwarz root: modprobe: ERROR: could not insert 'kvm_intel': Operation not supported Jan 21 22:08:21 Retronwarz sshd[25226]: Failed password for root from 222.186.30.167 port 57420 ssh2 Jan 21 22:08:22 Retronwarz sshd[25226]: Failed password for root from 222.186.30.167 port 57420 ssh2 Jan 21 22:08:22 Retronwarz sshd[25226]: Failed password for root from 222.186.30.167 port 57420 ssh2 Jan 21 22:08:22 Retronwarz sshd[25226]: Received disconnect from 222.186.30.167 port 57420:11: [preauth] Jan 21 22:08:22 Retronwarz sshd[25226]: Disconnected from authenticating user root 222.186.30.167 port 57420 [preauth] Jan 21 22:08:31 Retronwarz sshd[25498]: Failed password for root from 218.92.0.204 port 59297 ssh2 Jan 21 22:08:31 Retronwarz sshd[25498]: Failed password for root from 218.92.0.204 port 59297 ssh2 Jan 21 22:08:31 Retronwarz sshd[25498]: Failed password for root from 218.92.0.204 port 59297 ssh2 Jan 21 22:08:32 Retronwarz sshd[25498]: Received disconnect from 218.92.0.204 port 59297:11: [preauth] Jan 21 22:08:32 Retronwarz sshd[25498]: Disconnected from authenticating user root 218.92.0.204 port 59297 [preauth] Jan 21 22:08:38 Retronwarz sshd[25592]: Invalid user examen from 134.209.24.143 port 35134 Jan 21 22:08:38 Retronwarz sshd[25592]: error: Could not get shadow information for NOUSER Jan 21 22:08:38 Retronwarz sshd[25592]: Failed password for invalid user examen from 134.209.24.143 port 35134 ssh2 Jan 21 22:08:38 Retronwarz sshd[25592]: Received disconnect from 134.209.24.143 port 35134:11: Bye Bye [preauth] Jan 21 22:08:38 Retronwarz sshd[25592]: Disconnected from invalid user examen 134.209.24.143 port 35134 [preauth] Jan 21 22:08:39 Retronwarz sshd[25590]: Accepted none for ftp from 128.199.235.128 port 36488 ssh2 Jan 21 22:08:58 Retronwarz sshd[25984]: Invalid user cg from 136.228.161.66 port 36632 Jan 21 22:08:58 Retronwarz sshd[25984]: error: Could not get shadow information for NOUSER Jan 21 22:08:58 Retronwarz sshd[25984]: Failed password for invalid user cg from 136.228.161.66 port 36632 ssh2 Jan 21 22:08:58 Retronwarz sshd[25984]: Received disconnect from 136.228.161.66 port 36632:11: Bye Bye [preauth] Jan 21 22:08:58 Retronwarz sshd[25984]: Disconnected from invalid user cg 136.228.161.66 port 36632 [preauth] Jan 21 22:09:02 Retronwarz sshd[26097]: Invalid user neil from 213.148.198.36 port 59894 Jan 21 22:09:02 Retronwarz sshd[26097]: error: Could not get shadow information for NOUSER Jan 21 22:09:02 Retronwarz sshd[26097]: Failed password for invalid user neil from 213.148.198.36 port 59894 ssh2 Jan 21 22:09:02 Retronwarz sshd[26097]: Received disconnect from 213.148.198.36 port 59894:11: Bye Bye [preauth] Jan 21 22:09:02 Retronwarz sshd[26097]: Disconnected from invalid user neil 213.148.198.36 port 59894 [preauth] Jan 21 22:10:12 Retronwarz sshd[27950]: Failed password for root from 218.92.0.204 port 36786 ssh2 Jan 21 22:10:13 Retronwarz sshd[27950]: Failed password for root from 218.92.0.204 port 36786 ssh2 Jan 21 22:10:13 Retronwarz sshd[27950]: Failed password for root from 218.92.0.204 port 36786 ssh2 Jan 21 22:10:13 Retronwarz sshd[27950]: Received disconnect from 218.92.0.204 port 36786:11: [preauth] Jan 21 22:10:13 Retronwarz sshd[27950]: Disconnected from authenticating user root 218.92.0.204 port 36786 [preauth] Jan 21 22:10:30 Retronwarz sshd[28661]: Invalid user demo from 129.204.84.35 port 42976 Jan 21 22:10:30 Retronwarz sshd[28661]: error: Could not get shadow information for NOUSER Jan 21 22:10:30 Retronwarz sshd[28661]: Failed password for invalid user demo from 129.204.84.35 port 42976 ssh2 Jan 21 22:10:30 Retronwarz sshd[28661]: Received disconnect from 129.204.84.35 port 42976:11: Bye Bye [preauth] Jan 21 22:10:30 Retronwarz sshd[28661]: Disconnected from invalid user demo 129.204.84.35 port 42976 [preauth] Jan 21 22:10:55 Retronwarz sshd[29349]: Invalid user luciano from 46.101.204.20 port 36180 Jan 21 22:10:55 Retronwarz sshd[29349]: error: Could not get shadow information for NOUSER Jan 21 22:10:55 Retronwarz sshd[29349]: Failed password for invalid user luciano from 46.101.204.20 port 36180 ssh2 Jan 21 22:10:55 Retronwarz sshd[29349]: Received disconnect from 46.101.204.20 port 36180:11: Bye Bye [preauth] Jan 21 22:10:55 Retronwarz sshd[29349]: Disconnected from invalid user luciano 46.101.204.20 port 36180 [preauth] Jan 21 22:11:15 Retronwarz sshd[30049]: Failed password for root from 222.186.30.76 port 46654 ssh2 Jan 21 22:11:15 Retronwarz sshd[30049]: Failed password for root from 222.186.30.76 port 46654 ssh2 Jan 21 22:11:16 Retronwarz sshd[30049]: Failed password for root from 222.186.30.76 port 46654 ssh2 Jan 21 22:11:16 Retronwarz sshd[30049]: Received disconnect from 222.186.30.76 port 46654:11: [preauth] Jan 21 22:11:16 Retronwarz sshd[30049]: Disconnected from authenticating user root 222.186.30.76 port 46654 [preauth] Jan 21 22:11:22 Retronwarz sshd[30248]: Connection closed by 42.200.78.78 port 33156 [preauth] Jan 21 22:11:32 Retronwarz sshd[30541]: Invalid user test from 134.209.24.143 port 36242 Jan 21 22:11:32 Retronwarz sshd[30541]: error: Could not get shadow information for NOUSER Jan 21 22:11:32 Retronwarz sshd[30541]: Failed password for invalid user test from 134.209.24.143 port 36242 ssh2 Jan 21 22:11:32 Retronwarz sshd[30541]: Received disconnect from 134.209.24.143 port 36242:11: Bye Bye [preauth] Jan 21 22:11:32 Retronwarz sshd[30541]: Disconnected from invalid user test 134.209.24.143 port 36242 [preauth] Jan 21 22:11:33 Retronwarz sshd[30562]: Invalid user rob from 213.148.198.36 port 57128 Jan 21 22:11:33 Retronwarz sshd[30562]: error: Could not get shadow information for NOUSER Jan 21 22:11:33 Retronwarz sshd[30562]: Failed password for invalid user rob from 213.148.198.36 port 57128 ssh2 Jan 21 22:11:33 Retronwarz sshd[30562]: Received disconnect from 213.148.198.36 port 57128:11: Bye Bye [preauth] Jan 21 22:11:33 Retronwarz sshd[30562]: Disconnected from invalid user rob 213.148.198.36 port 57128 [preauth] Jan 21 22:11:55 Retronwarz sshd[30996]: Failed password for root from 218.92.0.204 port 19037 ssh2 Jan 21 22:11:55 Retronwarz sshd[30996]: Failed password for root from 218.92.0.204 port 19037 ssh2 Jan 21 22:11:55 Retronwarz sshd[30996]: Failed password for root from 218.92.0.204 port 19037 ssh2 Jan 21 22:11:56 Retronwarz sshd[30996]: Received disconnect from 218.92.0.204 port 19037:11: [preauth] Jan 21 22:11:56 Retronwarz sshd[30996]: Disconnected from authenticating user root 218.92.0.204 port 19037 [preauth] Jan 21 22:12:31 Retronwarz sshd[31998]: Invalid user email from 136.228.161.66 port 34820 Jan 21 22:12:31 Retronwarz sshd[31998]: error: Could not get shadow information for NOUSER Jan 21 22:12:31 Retronwarz sshd[31998]: Failed password for invalid user email from 136.228.161.66 port 34820 ssh2 Jan 21 22:12:31 Retronwarz sshd[31998]: Received disconnect from 136.228.161.66 port 34820:11: Bye Bye [preauth] Jan 21 22:12:31 Retronwarz sshd[31998]: Disconnected from invalid user email 136.228.161.66 port 34820 [preauth] Jan 21 22:13:34 Retronwarz sshd[1010]: Failed password for root from 218.92.0.204 port 40161 ssh2 Jan 21 22:13:34 Retronwarz sshd[1010]: Failed password for root from 218.92.0.204 port 40161 ssh2 Jan 21 22:13:34 Retronwarz sshd[1010]: Failed password for root from 218.92.0.204 port 40161 ssh2 Jan 21 22:13:35 Retronwarz sshd[1010]: Received disconnect from 218.92.0.204 port 40161:11: [preauth] Jan 21 22:13:35 Retronwarz sshd[1010]: Disconnected from authenticating user root 218.92.0.204 port 40161 [preauth] Jan 21 22:13:51 Retronwarz sshd[1399]: Invalid user karen from 129.204.84.35 port 44138 Jan 21 22:13:51 Retronwarz sshd[1399]: error: Could not get shadow information for NOUSER Jan 21 22:13:51 Retronwarz sshd[1399]: Failed password for invalid user karen from 129.204.84.35 port 44138 ssh2 Jan 21 22:13:51 Retronwarz sshd[1399]: Received disconnect from 129.204.84.35 port 44138:11: Bye Bye [preauth] Jan 21 22:13:51 Retronwarz sshd[1399]: Disconnected from invalid user karen 129.204.84.35 port 44138 [preauth] Jan 21 22:14:00 Retronwarz sshd[1671]: Invalid user lw from 213.148.198.36 port 54362 Jan 21 22:14:00 Retronwarz sshd[1671]: error: Could not get shadow information for NOUSER Jan 21 22:14:00 Retronwarz sshd[1671]: Failed password for invalid user lw from 213.148.198.36 port 54362 ssh2 Jan 21 22:14:00 Retronwarz sshd[1671]: Received disconnect from 213.148.198.36 port 54362:11: Bye Bye [preauth] Jan 21 22:14:00 Retronwarz sshd[1671]: Disconnected from invalid user lw 213.148.198.36 port 54362 [preauth] Jan 21 22:14:21 Retronwarz sshd[2184]: Failed password for root from 134.209.24.143 port 37344 ssh2 Jan 21 22:14:21 Retronwarz sshd[2184]: Received disconnect from 134.209.24.143 port 37344:11: Bye Bye [preauth] Jan 21 22:14:21 Retronwarz sshd[2184]: Disconnected from authenticating user root 134.209.24.143 port 37344 [preauth] Jan 21 22:14:41 Retronwarz sshd[2560]: Invalid user alg from 46.101.204.20 port 37956 Jan 21 22:14:41 Retronwarz sshd[2560]: error: Could not get shadow information for NOUSER Jan 21 22:14:41 Retronwarz sshd[2560]: Failed password for invalid user alg from 46.101.204.20 port 37956 ssh2 Jan 21 22:14:41 Retronwarz sshd[2560]: Received disconnect from 46.101.204.20 port 37956:11: Bye Bye [preauth] Jan 21 22:14:41 Retronwarz sshd[2560]: Disconnected from invalid user alg 46.101.204.20 port 37956 [preauth] Jan 21 22:14:56 Retronwarz sshd[3008]: Failed password for root from 51.15.87.74 port 44688 ssh2 Jan 21 22:14:56 Retronwarz sshd[3008]: Received disconnect from 51.15.87.74 port 44688:11: Bye Bye [preauth] Jan 21 22:14:56 Retronwarz sshd[3008]: Disconnected from authenticating user root 51.15.87.74 port 44688 [preauth] Jan 21 22:15:09 Retronwarz sshd[3360]: Invalid user socket from 190.0.127.78 port 49593 Jan 21 22:15:09 Retronwarz sshd[3360]: error: Could not get shadow information for NOUSER Jan 21 22:15:09 Retronwarz sshd[3360]: Failed password for invalid user socket from 190.0.127.78 port 49593 ssh2 Jan 21 22:15:10 Retronwarz sshd[3360]: Received disconnect from 190.0.127.78 port 49593:11: Bye Bye [preauth] Jan 21 22:15:10 Retronwarz sshd[3360]: Disconnected from invalid user socket 190.0.127.78 port 49593 [preauth] Jan 21 22:15:11 Retronwarz sshd[3445]: Failed password for root from 218.92.0.204 port 56007 ssh2 Jan 21 22:15:12 Retronwarz sshd[3445]: Failed password for root from 218.92.0.204 port 56007 ssh2 Jan 21 22:15:12 Retronwarz sshd[3445]: Failed password for root from 218.92.0.204 port 56007 ssh2 Jan 21 22:15:12 Retronwarz sshd[3445]: Received disconnect from 218.92.0.204 port 56007:11: [preauth] Jan 21 22:15:12 Retronwarz sshd[3445]: Disconnected from authenticating user root 218.92.0.204 port 56007 [preauth] Then once I booted the server back up, this is the logs I have in my System Logs Jan 21 22:30:13 Retronwarz kernel: ACPI: Early table checksum verification disabled Jan 21 22:30:13 Retronwarz kernel: floppy0: no floppy controllers found Jan 21 22:30:13 Retronwarz kernel: random: 7 urandom warning(s) missed due to ratelimiting Jan 21 22:30:13 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:30:13 Retronwarz kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514) Jan 21 22:30:13 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:30:13 Retronwarz kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180810/psparse-514) Jan 21 22:30:13 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:30:13 Retronwarz kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-514) Jan 21 22:30:13 Retronwarz kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Jan 21 22:30:13 Retronwarz kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180810/psparse-514) Jan 21 22:30:26 Retronwarz rpc.statd[1686]: Failed to read /var/lib/nfs/state: Success Jan 21 22:32:17 Retronwarz root: modprobe: ERROR: could not insert 'kvm_intel': Operation not supported Got any idea why this may happen? syslog Edited January 21, 2020 by Nunong21 Add syslog Quote Link to comment
JonathanM Posted January 22, 2020 Share Posted January 22, 2020 Is your server directly exposed to the internet? If so, don't. You must put unraid behind a firewall, and only pass through specific ports, preferably only one port pointed to the Let'sEncrypt container running reverse proxy for any other services that need to get through. Never allow direct internet access to unraid's management or console ports. Quote Link to comment
trurl Posted January 22, 2020 Share Posted January 22, 2020 1 hour ago, jonathanm said: Is your server directly exposed to the internet? Obviously Jan 21 10:55:29 Retronwarz sshd[3200]: Failed password for root from 111.229.57.47 port 50646 ssh2 CHINA ... Jan 21 10:55:41 Retronwarz sshd[3370]: Invalid user tester from 198.245.50.81 port 56916 CANADA ... Jan 21 10:55:49 Retronwarz sshd[3531]: Invalid user yaya from 47.17.177.110 port 57790 US ... Jan 21 10:56:07 Retronwarz sshd[3805]: Failed password for root from 157.245.62.79 port 58732 ssh2 SINGAPORE ... Jan 21 10:56:16 Retronwarz sshd[3971]: Failed password for root from 139.255.35.181 port 59750 ssh2 INDONESIA ... Jan 21 10:56:17 Retronwarz sshd[3977]: Invalid user damiano from 92.222.72.234 port 45280 FRANCE ... Jan 21 10:56:30 Retronwarz sshd[4181]: Invalid user wz from 138.68.168.137 port 46360 UK ... Jan 21 10:56:37 Retronwarz sshd[4316]: Invalid user deployer from 37.139.0.226 port 35390 NETHERLANDS ... Hundreds more Quote Link to comment
Nunong21 Posted January 22, 2020 Author Share Posted January 22, 2020 2 hours ago, trurl said: Obviously Jan 21 10:55:29 Retronwarz sshd[3200]: Failed password for root from 111.229.57.47 port 50646 ssh2 CHINA ... Jan 21 10:55:41 Retronwarz sshd[3370]: Invalid user tester from 198.245.50.81 port 56916 CANADA ... Jan 21 10:55:49 Retronwarz sshd[3531]: Invalid user yaya from 47.17.177.110 port 57790 US ... Jan 21 10:56:07 Retronwarz sshd[3805]: Failed password for root from 157.245.62.79 port 58732 ssh2 SINGAPORE ... Jan 21 10:56:16 Retronwarz sshd[3971]: Failed password for root from 139.255.35.181 port 59750 ssh2 INDONESIA ... Jan 21 10:56:17 Retronwarz sshd[3977]: Invalid user damiano from 92.222.72.234 port 45280 FRANCE ... Jan 21 10:56:30 Retronwarz sshd[4181]: Invalid user wz from 138.68.168.137 port 46360 UK ... Jan 21 10:56:37 Retronwarz sshd[4316]: Invalid user deployer from 37.139.0.226 port 35390 NETHERLANDS ... Hundreds more Yes, I already blocked that port. Now i'm almost finishing my unraid server (so far didn't get any more error of that kind, but sometimes I get stuck in the bzimage while booting). Now my problem has to do with Traefik + Nextcloud. I'm looking into that... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.