L2TP Ipsec Windows to Mikrotik eror 789

 Add this to registry

REG ADD HKLM\SYSTEM\CurrentControlSet\Services\PolicyAgent /v AssumeUDPEncapsulationContextOnSendRule /t REG_DWORD /d 0x2 /f

Delete connection and create it again

Proxmox Backup Server find backup for specific chunk

 proxmox-backup-debug inspect chunk b531d3ffc9bd7c65748a61198c060678326a431db7eded874c327b7986e595e0 --reference-filter /path/in/a/datastore/directory

reference-filter  <- path to the Datastore

References:

Technical Overview — Proxmox Backup 3.1.4-1 documentation

Resize ZFS

 If iscsi -> rescan disk after the volume has been increase, for instance sdb

echo 1 >/sys/block/sdb/device/rescan

zpool online -e POOL /dev/sdb  <- Or other device, for instace scsi-... the volume displayed in the zpool list command

zpool list 

Verify status

zpool status POOL

Restart Hyper Backup - Synology DSM CLI

 Connect vía SSH and sudo

 synopkg stop HyperBackup

 synopkg stop HyperBackup

Filter to view details of the System File Checker process

After SFC /Scannow

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" 

 References:

Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

Disable IPv6 Windows - PowerShell

 View

Get-NetAdapterBinding | Where-Object ComponentID -EQ 'ms_tcpip6'

Disable one

Disable-NetAdapterBinding -Name 'Ethernet' -ComponentID 'ms_tcpip6'

Disable all

Disable-NetAdapterBinding -Name "*" -ComponentID ms_tcpip6

Searching shutdown logs

Linux

grep -iva ': starting\|kernel: .*: Power Button\|watching system buttons\|Stopped Cleaning Up\|Started Crash recovery kernel' /var/log/messages /var/log/syslog /var/log/apcupsd* | grep -iw 'recover[a-z]*\|power[a-z]*\|shut[a-z ]*down\|rsyslogd\|ups'

Windows

Event ID	Description
41	The system has rebooted without cleanly shutting down first.
1074	The system has been shutdown properly by a user or process.
1076	Follows after Event ID 6008 and means that the first user with shutdown privileges logged on to the server after an unexpected restart or shutdown and specified the cause.
6005	The Event Log service was started. Indicates the system startup.
6006	The Event Log service was stopped. Indicates the proper system shutdown.
6008	The previous system shutdown was unexpected.
6009	The operating system version detected at the system startup.
6013	The system uptime in seconds.

PS C:\> Get-EventLog System -Newest 10000 | `
        Where EventId -in 41,1074,1076,6005,6006,6008,6009,6013 | `
        Format-Table TimeGenerated,EventId,UserName,Message -AutoSize -wrapdasd

References

https://geekflare.com/check-linux-reboot-reason/

Windows: Shutdown/Reboot Event IDs - Get Logs - ShellHacks