gray squirrel

see attached syslog

They asked if there was anything in the logs. It doesn't look like it to me, but new to linux. Is it safe to post the full syslog?

It took a little time for Asrock to come back to me and wait for another even while I was mirroring the logs to the USB. asrock point to the OS but I could use some help understanding the log. I was sitting next to the server at this time and I didn't even realize it rebooted until l tried to RDP into a VM for some testing I'm doing. IPMI has the lock up at 2020-05-19 14:09:13. Below is a snip it of the log before the boot: May 19 13:52:58 Megatron kernel: br0: port 3(vnet1) entered blocking state May 19 13:52:58 Megatron kernel: br0: port 3(vnet1) entered disabled state May 19 13:52:58 Megatron kernel: device vnet1 entered promiscuous mode May 19 13:52:58 Megatron kernel: br0: port 3(vnet1) entered blocking state May 19 13:52:58 Megatron kernel: br0: port 3(vnet1) entered forwarding state May 19 13:53:03 Megatron kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x1e@0x258 May 19 13:53:03 Megatron kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x19@0x900 May 19 14:08:58 Megatron kernel: br0: port 3(vnet1) entered disabled state May 19 14:08:58 Megatron kernel: device vnet1 left promiscuous mode May 19 14:08:58 Megatron kernel: br0: port 3(vnet1) entered disabled state May 19 14:09:00 Megatron kernel: vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none My guess is the rest is the boot log? May 19 14:11:37 Megatron kernel: microcode: microcode updated early to revision 0x718, date = 2019-05-21 May 19 14:11:37 Megatron kernel: Linux version 4.19.107-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Mar 5 13:55:57 PST 2020 May 19 14:11:37 Megatron kernel: Command line: BOOT_IMAGE=/bzimage isolcpus=0-3,16-19 initrd=/bzroot May 19 14:11:37 Megatron kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' May 19 14:11:37 Megatron kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' May 19 14:11:37 Megatron kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' May 19 14:11:37 Megatron kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 May 19 14:11:37 Megatron kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. May 19 14:11:37 Megatron kernel: BIOS-provided physical RAM map:

over the past few week I have experienced two unclean shut-downs randomly. my IMPI Log lists list them as Critical Stop ; OEM Event Data2 code = 69h ; OEM Event Data3 code = 6Dh. any pointers? I have attached the diagnostics and a snip-it from the IPMI event log. thanks in advance. Edit. I didn't trigger the shut-down. megatron-diagnostics-20200425-1400.zip

i have a 8 6 port sata cable so just switched to a new port completely and pulled and re-seated the power cable. ram going bad never seen that before (but this is the first time i'm using full on server hardware) is it worth a re-seat and run memtest, or is the module screwed? amazingly fast response Squid!!! edit, so the shouldn't worry about the disc read errors, should i swap the parity drive anyway?

so a couple of days ago my parity drive started spitting out UDMA errors. it ran up to 5155. i changed the sata cable, run a full SMART check and rebuilt the array. now fix common problems is telling that there are hardware problems and to post my log file. see attached. the UDMA error has not increased. a quick scan down syslog shows lots of md: disk0 read error, sector=11252103536 etc. is my shucked 8TB drive screwed? or do i just acknowledge the error and forget about it. on another note, can i swap my other 8TB drive to become parity? my array is 2X 8TB and 2X 6TB. megatron-diagnostics-20200201-2214.zip

this makes sense as i was looking at the logs and there was a line saying ata14 was a virtual device I have disabled the Marvell controller, lets see if that helps

non of the drives are showing any errors. and non of the drives relate to ata14.. i have taken the array off-line and unplugged and re-pluged all the drives

but what drive? I don't have at Sata 1 devices attached. this is my guess as its suggesting a 1.5 Gbps link

I am trying to diagnose some sata errors. I have a EP2C602-4L/D16 motherboard with 2 SSD's 2 HDD. non of my hard drives are generating any SMART errors, my guess is one of the ports is having issues, I have no idea why something is defaulting to SATA 1 speeds? it doesn't look like I have a port labeled 14, although this board has 14 ports. i have seen suggestions that this is a doggy cable? it is intermittent and happens 1 or 2 times an hour. Nov 22 20:47:03 Megatron kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Nov 22 20:47:03 Megatron kernel: ata14.00: irq_stat 0x40000001 Nov 22 20:47:03 Megatron kernel: ata14.00: cmd a0/00:00:00:fc:00/00:00:00:00:00/a0 tag 6 pio 16636 in Nov 22 20:47:03 Megatron kernel: opcode=0x12 12 01 00 00 fc 00res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) Nov 22 20:47:03 Megatron kernel: ata14: hard resetting link Nov 22 20:47:04 Megatron kernel: ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Nov 22 20:47:04 Megatron kernel: ata14.00: configured for UDMA/66 Nov 22 20:47:04 Megatron kernel: ata14: EH complete

Is it possible to use the reverse proxy to redirect traffic to an internal IP, either a VM or another machine? I am new to unraid, and I have a synology NAS that I am migrating away from. I have also set up a xpenology VM. I have set up a number of synology units with friends and family and I like the way it handles backup, so I want to use my xpenology VM or current synology as a remote target. I have set up Letsencrypt docker and it works grate after following the spaceinvaderone video. However this only looks to work with dockers on the Unraid machine, via proxynet. I found some example code to root the proxy pass to an internal IP for example 192.168.X.XX at https://www.reddit.com/r/unRAID/comments/apapqw/reverse_proxy_with_letsencrypt_docker_and_vm/ However I cant get it to work. I have my own domain and plan to use something like xpenology.mydomain.com and synology.mydomain.com. If it forward port 5001 to my xpenology vm I can connect directly using xpenology.mydomain.com:5001 but if I don’t specify the port I get the “Welcome to our server” nginx splash page. It would be nice to be redirected to each of these DSM web interfaces by using xpenology. and synology. as i can only forward 5001 once. My congfig file is currently. server { listen 443 ssl http2; server_name xpenology.*; server_tokens off; access_log /var/log/nginx/xpenology.SITE.access.log; error_log /var/log/nginx/xpenology.SITE.error.log error; ssl on; ssl_certificate /etc/letsencrypt/live/SITE/fullchain.pem; ssl_certificate_key /etc/letsencrypt/SITE/privkey.pem; location /{ proxy_pass https://192.168.X.XXX:50001; proxy_redirect off; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Protocol $scheme; proxy_set_header X-Url-Scheme $scheme; } }