• Mit Video von youtube: https://www.youtube.com/watch?v=i7cyLLsLM8A

• Im Wesentlichen beim MegaRAID Controller einloggen die Platte identifizieren „start locating“ und dann „Offline“ setzen - Tauschen und wenn auto rebuild aktiviert ist wird gleich rebuildet
• Im Dashboard gibt es eine Option „Silence Alarm“ um den akkustischen Alarm zu deaktivieren
• Achtung RAID10 lässt sich nicht erweitern ohne das ganze Array zu löschen (https://www.broadcom.com/support/knowledgebase/1211161503168/how-to-expand-an-array-on-megaraid-controllers-adding-drives-to-)

• Predictive Failure Count beim Controller - E-Mails zB:

Controller ID:  0   PD Predictive failure:  
    -:-:3
Event ID:96
Generated On: Mon Sep 02 14:29:04 CEST 2019

• Festplatte wird „bald“ kaputt werden - Austausch empfohlen - Slot beginnt orange zu blinken
• Sicht auf den Server - In diesem Beispiel bezieht es sich auf Slot 3 im Server

• Beim Versuch des Web Logins zur verwaltung des Controllers wird immer wieder LSI Storage Authority Error Code 49 Invalid Credentials geworfen
• ACHTUNG SPRACHE DES eingesetzten OS - Gruppe der „Administratoren“ bei deutscher Windows Version hat vollen Zugriff nicht Administrators

* https://www.thomas-krenn.com/de/wiki/LSI_Storage_Authority_Error_Code_49_Invalid_Credentials

Lösung

Zur Behebung des Problems passen Sie die Konfigurationsdatei LSA.conf folgendermaßen an:[1]

    Stoppen Sie den LSAService in Windows Services
    Editieren sie die LSA config file (LSA.conf)

        C:\Program Files(x86)\LSI\LSIStroageAuthority\conf\LSA.conf

    Überprüfen Sie folgenden Befehl: full_access_groups = Administrators

        Hier muss je nach Sprache dies angepasst werden:
            Französisch = full_access_groups = Administrateurs
            Deutsch = full_access_groups = Administratoren
            Spanish = full_access_groups = Administradores
            Russisch = full_access_groups = Администраторы oder Administratory

    Sobald Sie Punkt 3 durchgeführt und gespeichert haben, müssen sie den LSAService neustarten.

Nach dem Ausführen dieser Schritte sollten Sie sich wieder ohne Probleme anmelden können.
Einzelnachweise

• Zumindest bei TD340 Remote Management
  • Achtung kein vollwertiges KVM Remote Management möglich über Konsole
  • Es muss ein Hardware dongle am Mainboard gesteckt werden !!! d.h. Server runterfahren raus aus dem Rack , zerlegen ..

• Default Username/Passwort ist NICHT unbedingt lenovo/lenovo (Server: Lenovo ThinkServer TD340 )
• Username: lenovo , Password: len0vO

boot grml live



You probably need to load the IPMI kernel modules:

modprobe ipmi_devintf
modprobe ipmi_si

You can add these to /etc/modules to have them loaded automatically (just list the module names):

ipmi_devintf
ipmi_si



ipmitool -I open user set password 2 ADMIN

The number 2 there is the user id. The ADMIN account defaults to user id 2. So I'm setting user id 2's password to ADMIN which is the default, but you could put any other password there.

• Getestet auf Windows 2019 Server 64Bit
• IPMICFG https://www.supermicro.com/SwDownload/SwSelect_Free.aspx?cat=IPMI
• ipmicfg_1.31.0_build.200205.zip
• Passwort für „ADMIN“ auf „ADMIN123!“ setzen:

C:\TMP\IPMICFG_1.31.0_build.200205\IPMICFG_1.31.0_build.200205\Windows\64bit>.\IPMICFG-Win.exe -user setpwd 2 ADMIN123!
Done.

C:\TMP\IPMICFG_1.31.0_build.200205\IPMICFG_1.31.0_build.200205\Windows\64bit>.\IPMICFG-Win.exe -user list
Maximum number of Users          : 10
Count of currently enabled Users : 1
User ID | User Name        | Privilege Level | Enable
------- | ---------        | --------------- | ------
      2 | ADMIN            | Administrator   | Yes

C:\TMP\IPMICFG_1.31.0_build.200205\IPMICFG_1.31.0_build.200205\Windows\64bit>

• Über die Web GUI unter Administration - Firmware → das *.bin File hochladen ( Signature checks usw. werden durch das ILO durchgeführt)
• Bei den Firmware Updates die .scexe Datei runterladen und entpacken
• HP Quote von der Website:

 To obtain firmware image for updating via iLO user interface, utilities, or scripting interface:
Download the SCEXE file to a client running a Linux operating system.  Execute: sh  CP0xxxxx.scexe --unpack=directory
This command will unpack the ilo4_1XX.bin into a user specified "directory". If the directory does not exist, the unpacker will attempt to create it.

• Default gateway über Web GUI lässt sich nicht ändern es bleibt der Alte
• Zugriff per SSH im richtigen Konfigurationskontext (Cisco lässt grüßen)

(controller) >enable
Password:****
Password:****

(controller) #show ip route

Codes: C - connected, O - OSPF, R - RIP, S - static
       M - mgmt, U - route usable, * - candidate default, V - RAPNG VPN

Gateway of last resort is Imported from DHCP to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from CELL to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from PPPOE to network 0.0.0.0 at cost 10
C    IP_NETWORK/MASK is directly connected, VLAN1
C    IP_NETWORK/MASK is directly connected, VLAN100
C    IP_NETWORK/MASK is directly connected, VLAN101

(controller) #show running-config | include gateway
Building Configuration...
ip default-gateway IP_DEFAULT_GATEWAY

(controller) #configure terminal 
Enter Configuration commands, one per line. End with CNTL/Z

(controller) (config) #no ip default-gateway IP_CURRENT_DEFAULT_GATEWAY
(controller) (config) #ip default-gateway IP_NEW_DEFAULT_GATEWAY
(controller) (config) #write memory 
Saving Configuration...

Configuration Saved.

(controller) (config) #exit
(controller) #show running-config | include gateway
Building Configuration...
ip default-gateway IP_NEW_DEFAULT_GATEWAY

• Projekt: https://github.com/AsamK/signal-cli
• Installation auch unter Debian stretch - https://github.com/AsamK/signal-cli/wiki/HowToUbuntu
• Installation liegt unter /opt/signal-cli/

Ubuntu/Debian: sudo apt-get install default-jre

signal-cli -u +436641234567 register
signal-cli -u +436641234567 verify CODE-FROM-SIGNAL-VIA-SMS
signal-cli -u +436641234567 (SENDER) send -m "foo" +438716213 (EMPFÄNGER)

Auth Infos werden unter ~/.local abgelegt d.h. Benutzerenvironment beachten und für nagios kopieren

• Icinga/Nagios Konfiguration

#signal Notification commands

define command {
        command_name    notify-host-by-signal
        command_line    /opt/signal-cli/bin/signal-cli -u +436641234567 send -m '$NOTIFICATIONTYPE$ Host : $HOSTNAME$ is $HOSTSTATE$ @ $LONGDATETIME$' $_CONTACTSIGNAL$
}
 
define command {
        command_name    notify-service-by-signal
        command_line     /opt/signal-cli/bin/signal-cli -u +436641234567  send  -m '$NOTIFICATIONTYPE$ Host : $HOSTNAME$ - Service : $SERVICEDESC$ is $SERVICESTATE$ @ $LONGDATETIME$' $_CONTACTSIGNAL$
}


#Contact definition

define contact{
        contact_name                    root
        alias                           Root
        service_notification_period     24x7
        host_notification_period        24x7
        service_notification_options    w,u,c,r
        host_notification_options       d,r
        service_notification_commands   notify-service-by-email notify-service-by-signal
        host_notification_commands      notify-host-by-email notify-host-by-signal
        email                           monitoring@pannoniait.at
        _signal                         +436641234567

         

        }

• Location für shared Secret für Authentifizierung

root@mrMonitoring:/var/lib/nagios# grep nagios /etc/passwd
nagios:x:116:124::/var/lib/nagios:/bin/false
root@mrMonitoring:/var/lib/nagios# ls -al /var/lib/nagios/.local/
total 12
drwx------ 3 nagios nagios 4096 Jul 15 13:08 .
drwxr-xr-x 3 nagios nagios 4096 Jul 15 13:17 ..
drwx------ 3 nagios nagios 4096 Jul 15 13:08 share
root@mrMonitoring:/var/lib/nagios# ls -al /var/lib/nagios/.local/share/
total 12
drwx------ 3 nagios nagios 4096 Jul 15 13:08 .
drwx------ 3 nagios nagios 4096 Jul 15 13:08 ..
drwx------ 3 nagios nagios 4096 Jul 15 13:08 signal-cli
root@mrMonitoring:/var/lib/nagios# ls -al /var/lib/nagios/.local/share/signal-cli/
total 12
drwx------ 3 nagios nagios 4096 Jul 15 13:08 .
drwx------ 3 nagios nagios 4096 Jul 15 13:08 ..
drwx------ 2 nagios nagios 4096 Jul 15 13:08 data

• https://nagios-plugins.org/doc/guidelines.html#AEN200

Performance data

Nagios 3 and newer will concatenate the parts following a "|" in a) the first line output by the plugin, and b) in the second to last line, into a string it passes to whatever performance data processing it has configured. (Note that it currently does not insert additional whitespace between both, so the plugin needs to provide some to prevent the last pair of a) and the first of b) getting run together.) Please refer to the Nagios documentation for information on how to configure such processing. However, it is the responsibility of the plugin writer to ensure the performance data is in a "Nagios Plugins" format.

This is the expected format:

'label'=value[UOM];[warn];[crit];[min];[max]

Notes:

    space separated list of label/value pairs
    label can contain any characters except the equals sign or single quote (')
    the single quotes for the label are optional. Required if spaces are in the label
    label length is arbitrary, but ideally the first 19 characters are unique (due to a limitation in RRD). Be aware of a limitation in the amount of data that NRPE returns to Nagios
    to specify a quote character, use two single quotes
    warn, crit, min or max may be null (for example, if the threshold is not defined or min and max do not apply). Trailing unfilled semicolons can be dropped
    min and max are not required if UOM=%
    value, min and max in class [-0-9.]. Must all be the same UOM. value may be a literal "U" instead, this would indicate that the actual value couldn't be determined
    warn and crit are in the range format (see the Section called Threshold and Ranges). Must be the same UOM
    UOM (unit of measurement) is a string of zero or more characters, NOT including numbers, semicolons, or quotes. Some examples:

        no unit specified - assume a number (int or float) of things (eg, users, processes, load averages)
        s - seconds (also us, ms)
        % - percentage
        B - bytes (also KB, MB, TB)
        c - a continous counter (such as bytes transmitted on an interface)

It is up to third party programs to convert the Nagios Plugins performance data into graphs.

• Achtung Interpreter bei eigenem plugin nicht vergessen e.g. #!/bin/bash sonst u.a. „No output returned bei daemon“ Fehlermeldung

• How To Create Nagios Plugins With Bash On Ubuntu 12.10 (https://www.digitalocean.com/.../tutorials/how-to-create-nagios-plugins-with-bash-on-ubuntu-12-10

Exit Code	Status
0	OK
1       WARNING
2	CRITICAL
3	UNKNOWN

• Offiziell: https://nagios-plugins.org/doc/guidelines.html#PLUGOUTPUT

Plugin Output for Nagios

You should always print something to STDOUT that tells if the service is working or why it is failing. Try to keep the output short - probably less that 80 characters. Remember that you ideally would like the entire output to appear in a pager message, which will get chopped off after a certain length.

As Nagios does not capture stderr output, you should only output to STDOUT and not print to STDERR.
Print only one line of text

Starting with version 3, Nagios will process plugins' multi-line output, which should be formatted as:

SERVICE STATUS: First line of output | First part of performance data
Any number of subsequent lines of output, but note that buffers
may have a limited size | Second part of performance data, which
may have continuation lines, too

Note, however, that the default configs still do not include the output's continuation lines into the notifications sent when Nagios notifies contacts about potential problems. Thus, keep your output short and to the point.

Output should be in the format:

SERVICE STATUS: Information text

However, note that this is not a requirement of the API, so you cannot depend on this being an accurate reflection of the status of the service - the status should always be determined by the return code.
Verbose Output

Use the -v flag for verbose output. You should allow multiple-v options for additional verbosity, up to a maximum of 3. The standard type of output should be:

Table 1. Verbose output levels
Verbosity level	Type of output
0	Single line, minimal output. Summary
1	Single line, additional information (eg list processes that fail)
2	Multi line, configuration debug output (eg ps command used)
3	Lots of detail for plugin problem diagnosis
Screen Output

The plugin should print the diagnostic and just the usage part of the help message. A well written plugin would then have --help as a way to get the verbose help.

Code and output should try to respect the 80x25 size of a crt (remember when fixing stuff in the server room!)
Plugin Return Codes

The return codes below are based on the POSIX spec of returning a positive value. Netsaint prior to v0.0.7 supported non-POSIX compliant return code of "-1" for unknown. Nagios supports POSIX return codes by default.

Note: Some plugins will on occasion print on STDOUT that an error occurred and error code is 138 or 255 or some such number. These are usually caused by plugins using system commands and having not enough checks to catch unexpected output. Developers should include a default catch-all for system command output that returns an UNKNOWN return code.

Table 2. Plugin Return Codes
Numeric Value	Service Status	Status Description
0	OK	The plugin was able to check the service and it appeared to be functioning properly
1	Warning	The plugin was able to check the service, but it appeared to be above some "warning" threshold or did not appear to be working properly
2	Critical	The plugin detected that either the service was not running or it was above some "critical" threshold
3	Unknown	Invalid command line arguments were supplied to the plugin or low-level failures internal to the plugin (such as unable to fork, or open a tcp socket) that prevent it from performing the specified operation. Higher-level errors (such as name resolution errors, socket timeouts, etc) are outside of the control of plugins and should generally NOT be reported as UNKNOWN states.

• Variante mit I7 und Intel onboard Grafikkarte
• Debian Buster + Backports Kernel
• M.2 NVME wurde per USB3 Adapter (https://www.amazon.de/gp/product/B07TSBR114/ref=ppx_yo_dt_b_asin_image_o05_s00?ie=UTF8&psc=1) als /dev/sdb für das System vorbereitet secure Boot ist aus UEFI Boot aktiviert und LEGACY Boot deaktiviert

Bootstrapping Debian with UEFI

https://wiki.debianforum.de/Debootstrap

I want GPT Partitions and UEFI boot

---
root@mrWhiteGhost:/home/urnilxfgbez# gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.5

Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries in memory.

Command (? for help): ?
b	back up GPT data to a file
c	change a partition's name
d	delete a partition
i	show detailed information on a partition
l	list known partition types
n	add a new partition
o	create a new empty GUID partition table (GPT)
p	print the partition table
q	quit without saving changes
r	recovery and transformation options (experts only)
s	sort partitions
t	change a partition's type code
v	verify disk
w	write table to disk and exit
x	extra functionality (experts only)
?	print this menu

Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.

-------------------------------------

root@mrWhiteGhost:/home/urnilxfgbez# gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
Model: Tech            
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): CA9A55BC-90E2-4B48-908E-AC417446BCB6
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 1953525101 sectors (931.5 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name

Command (? for help): n
Partition number (1-128, default 1): 
First sector (34-1953525134, default = 2048) or {+-}size{KMGTP}: 
Last sector (2048-1953525134, default = 1953525134) or {+-}size{KMGTP}: +600M
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): ef00
Changed type of partition to 'EFI system partition'

Command (? for help): n
Partition number (2-128, default 2): 
First sector (34-1953525134, default = 1230848) or {+-}size{KMGTP}: 
Last sector (1230848-1953525134, default = 1953525134) or {+-}size{KMGTP}: +1024M
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): 
Changed type of partition to 'Linux filesystem'

Command (? for help): n
Partition number (3-128, default 3): 
First sector (34-1953525134, default = 3328000) or {+-}size{KMGTP}: 
Last sector (3328000-1953525134, default = 1953525134) or {+-}size{KMGTP}: 
Current type is 8300 (Linux filesystem)
Hex code or GUID (L to show codes, Enter = 8300): L
Type search string, or <Enter> to show all codes: cryp
8308 Linux dm-crypt                      a02e Android encrypt                   
a905 NetBSD encrypted                    e900 Veracrypt data                    
f801 Ceph dm-crypt OSD                   f803 Ceph dm-crypt journal             
f805 Ceph dm-crypt disk in creation      f809 Ceph lockbox for dm-crypt keys    
f810 Ceph dm-crypt block                 f811 Ceph dm-crypt block DB            
f812 Ceph dm-crypt block write-ahead lo  f813 Ceph dm-crypt LUKS journal        
f814 Ceph dm-crypt LUKS block            f815 Ceph dm-crypt LUKS block DB       
f816 Ceph dm-crypt LUKS block write-ahe  f817 Ceph dm-crypt LUKS OSD            

Hex code or GUID (L to show codes, Enter = 8300): 
Changed type of partition to 'Linux filesystem'

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.

-----------------------------------------------

Partitions and Crypto:

root@mrWhiteGhost:/home/urnilxfgbez# mkfs.vfat -n EFI  /dev/sdb1
mkfs.fat 4.1 (2017-01-24)
root@mrWhiteGhost:/home/urnilxfgbez# mkfs.ext4 -L BOOT /dev/sdb2 
mke2fs 1.45.6 (20-Mar-2020)
Creating filesystem with 262144 4k blocks and 65536 inodes
Filesystem UUID: 17843802-be7c-4fac-b4b8-70e8b71eabaf
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

root@mrWhiteGhost:/home/urnilxfgbez# cryptsetup luksFormat /dev/sdb3

WARNING!
========
This will overwrite data on /dev/sdb3 irrevocably.

Are you sure? (Type 'yes' in capital letters): YES
Enter passphrase for /dev/sdb3: 
Verify passphrase: 
root@mrWhiteGhost:/home/urnilxfgbez# cryptsetup luksOpen /dev/sdb3 ROOTIGES
Enter passphrase for /dev/sdb3:

----------
root@mrWhiteGhost:/home/urnilxfgbez# mkfs.ext4 -L ROOTIGES_PLAIN /dev/mapper/ROOTIGES 
mke2fs 1.45.6 (20-Mar-2020)
Creating filesystem with 243770545 4k blocks and 60948480 inodes
Filesystem UUID: e3e418a6-eede-437f-9de5-a03ab67090b9
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000, 214990848

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

----------------------------
CHROOT Environment Preparation
root@mrWhiteGhost:/home/urnilxfgbez# mkdir /tmp/foo
root@mrWhiteGhost:/home/urnilxfgbez# mount /dev/mapper/ROOTIGES /tmp/foo
root@mrWhiteGhost:/home/urnilxfgbez# mkdir /tmp/foo/boot
root@mrWhiteGhost:/home/urnilxfgbez# mount /dev/sdb2 /tmp/foo/boot
root@mrWhiteGhost:/home/urnilxfgbez# mkdir /tmp/foo/boot/efi
root@mrWhiteGhost:/home/urnilxfgbez# mount /dev/sdb1 /tmp/foo/boot/efi/

------
Debootstrap go Debian Buster

root@mrWhiteGhost:/home/urnilxfgbez# debootstrap --arch=amd64 buster /tmp/foo/ http://ftp.de.debian.org/debian

Retreiving ...
..
..
..
 I: Configuring ifupdown...
I: Configuring bsdmainutils...
I: Configuring whiptail...
I: Configuring libnetfilter-conntrack3:amd64...
I: Configuring iptables...
I: Configuring tasksel-data...
I: Configuring tasksel...
I: Configuring libc-bin...
I: Configuring systemd...
I: Base system installed successfully.
-------------------
CHROOT GRUB Requirements

root@mrWhiteGhost:/home/urnilxfgbez# mount -o bind /proc /tmp/foo/proc/
root@mrWhiteGhost:/home/urnilxfgbez# mount -o bind /dev /tmp/foo/dev
root@mrWhiteGhost:/home/urnilxfgbez# mount -o bind /dev/pts /tmp/foo/dev/pts
root@mrWhiteGhost:/home/urnilxfgbez# mount -o bind /sys /tmp/foo/sys
-----

DEBIAN BASIC Packages

root@mrWhiteGhost:/# apt-get install  console-data console-common tzdata locales keyboard-configuration linux-image-amd64                         
Reading package lists... Done
Building dependency tree... Done
tzdata is already the newest version (2020a-0+deb10u1).
The following additional packages will be installed:
  apparmor busybox bzip2 file firmware-linux-free initramfs-tools
  initramfs-tools-core kbd klibc-utils libc-l10n libexpat1 libklibc
  libmagic-mgc libmagic1 libmpdec2 libpython3-stdlib libpython3.7-minimal
  libpython3.7-stdlib libreadline7 libsqlite3-0 linux-base
  linux-image-4.19.0-9-amd64 mime-support pigz python3 python3-minimal
  python3.7 python3.7-minimal xz-utils
Suggested packages:
  apparmor-profiles-extra apparmor-utils bzip2-doc unicode-data
  bash-completion linux-doc-4.19 debian-kernel-handbook grub-pc
  | grub-efi-amd64 | extlinux python3-doc python3-tk python3-venv
  python3.7-venv python3.7-doc binutils binfmt-support
The following NEW packages will be installed:
  apparmor busybox bzip2 console-common console-data file firmware-linux-free
  initramfs-tools initramfs-tools-core kbd keyboard-configuration klibc-utils
  libc-l10n libexpat1 libklibc libmagic-mgc libmagic1 libmpdec2
  libpython3-stdlib libpython3.7-minimal libpython3.7-stdlib libreadline7
  libsqlite3-0 linux-base linux-image-4.19.0-9-amd64 linux-image-amd64 locales
  mime-support pigz python3 python3-minimal python3.7 python3.7-minimal
  xz-utils
0 upgraded, 34 newly installed, 0 to remove and 0 not upgraded.
Need to get 62.6 MB of archives.
After this operation, 333 MB of additional disk space will be used.
Do you want to continue? [Y/n] y

-----

CRYPTO Foo
root@mrWhiteGhost:/# apt-get install  cryptsetup 


-----

VIM

root@mrWhiteGhost:/# apt-get install  vim


-------
FSTAB

root@mrWhiteGhost:/# cat /etc/fstab
# UNCONFIGURED FSTAB FOR BASE SYSTEM
/dev/mapper/ROOTIGES /               ext4    errors=remount-ro 0       1
UUID=17843802-be7c-4fac-b4b8-70e8b71eabaf	/boot	 ext4	defaults
UUID=E6B8-136A	/boot/efi	vfat	defaults


-------
Crypttab

root@mrWhiteGhost:/# cat /etc/crypttab 
# <target name>	<source device>		<key file>	<options>
ROOTIGES	UUID=d4ccc7b9-2db5-42cb-ae66-7a623744b38d	none	luks,tries=0

root@mrWhiteGhost:/# apt-get install grub-efi-amd64

----
EFI
root@mrWhiteGhost:/# grub-install -d /usr/lib/grub/x86_64-efi /dev/sdb
Installing for x86_64-efi platform.
grub-install: warning: EFI variables are not supported on this system..
Installation finished. No error reported.

• ICZI USB 3.0 Datenkabel: https://www.amazon.de/gp/product/B01IVP5B2W/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
• 5Gbit Ethernet Link über USB3 wäre nett ↔ ~1Gbit in der Praxis
• Getestet auf Kali Linux 5.5.0-kali2-amd64 und 5.3.0-kali2-amd64 Kernel
• Kabel wird automatisch über cdc_ether als usb0 erkannt

Bus 003 Device 003: ID 0ea0:7301 Ours Technology, Inc. SmartKMLink

• Performance Tests - MTU und Window Sizes alles default

root@mrWhiteGhost:/home/urnilxfgbez# iperf -c 192.168.1.1 -t 300 -i 60
------------------------------------------------------------
Client connecting to 192.168.1.1, TCP port 5001
TCP window size:  476 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.2 port 45776 connected with 192.168.1.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.0 sec  8.99 GBytes  1.29 Gbits/sec
[  3] 60.0-120.0 sec  8.97 GBytes  1.28 Gbits/sec
[  3] 120.0-180.0 sec  8.99 GBytes  1.29 Gbits/sec
[  3] 180.0-240.0 sec  8.98 GBytes  1.29 Gbits/sec
[  3] 240.0-300.0 sec  8.98 GBytes  1.29 Gbits/sec
[  3]  0.0-300.0 sec  44.9 GBytes  1.29 Gbits/sec

root@mrWhiteGhost:/home/urnilxfgbez# ip addr ls usb0
8: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 8e:0b:6e:2c:e1:d2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.2/24 brd 192.168.1.255 scope global usb0
       valid_lft forever preferred_lft forever
root@mrWhiteGhost:/home/urnilxfgbez# ethtool usb0
Settings for usb0:
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes

• vielleicht würde QNAP QNA-UC5G1T USB 3.0 auf 5GbE Adapter mehr Datendurchsatzrate schaffen https://www.amazon.de/gp/product/B07RY415TM/ref=ox_sc_saved_title_1?smid=A3JWKAKR8XB7XF&psc=1

• Linux Mint 19 Mate 64Bit
• Problem:
  • angesteckt per HDMI auf Sony Bravia TV - Auflösung bei maximal 1024×768 Ausschnitt komplett verkleinert - kein Vollbild
  • Beim Bootvorgang kein Bild (ROOT ist verschlüsselt) - Umstieg auf 4.18 generic Kernel dann ok (achtung Module installieren für Kernel sonst kein USB bei cryptsetup Passworteingabe)
• Lösung: DisplayPort auf HDMI Adapter einstecken bei Display Port zB: https://www.amazon.de/gp/product/B010SDZZ80/ref=ppx_yo_dt_b_asin_title_o01__o00_s00?ie=UTF8&psc=1
• Hintegrund: Offenbar gibt es Bug im Kernel der bis zu 4.18 reicht - Kernel Fehlermeldung zeugt davon in den Logs (*…link..intel…*) - Kabylake flanscht HDMI und Display Port zusammen - bekommt ihm offenbar nicht

• Achtung Broadcom Netzwerkkarten
• hat Zusammenhang mit 32Bit Ubuntu 18.04 4.15er Kernel Installation
• Deaktivieren von VMQ in GUI und powershell hat in diesem Fall NICHTS gebracht
  • Intel 350 Dual Interface Karte wurde installiert !!!
  • Broadcom Firmware/Treiber Upgrades von der HP Seite installiert (>202)
• Microsoft Quote:

Cause
This is a known issue with Broadcom NetXtreme 1-gigabit network adapters that use the b57nd60a.sys driver, when VMQ is enabled on the network adapter. (By default, VMQ is enabled by the Broadcom network driver.)

Broadcom designates these network adapters as 57xx based chipsets. They include 5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, and 5780. 
These network adapters are also sold under different model numbers by some server OEMs. HP sells these drivers under model numbers NC1xx, NC3xx, and NC7xx. You may be using driver version 16.2, 16.4, or 16.6, depending on which OEM version you are using or whether you are using the Broadcom driver version. 
Resolution
This issue is resolved in Broadcom driver b57nd60a.sys version 16.8 and newer. In March 2015, Broadcom published driver version 17.0 for download. In April 2015, HP published version 16.8 of the driver for their affected network adapters, here is one of their download locations. Please contact your server OEM if you need a driver that is specific to your server.

If you are unable to update your network adapter driver to resolve the issue, you can work around the issue by disabling VMQ on each affected Broadcom network adapter by using the Set-NetAdapterVmq Windows PowerShell command. For example, if you have a dual-port network adapter, and if the ports are named NIC 1 and NIC 2 in Windows, you would disable VMQ on each adapter by using the following commands:

Set-NetAdapterVmq -Name "NIC 1" -Enabled $False
Set-NetAdapterVmq -Name "NIC 2" -Enabled $False
You can confirm that VMQ is disabled on the correct network adapters by using the Get-NetAdapterVmq Windows PowerShell command.

Note By default, VMQ is disabled on the Hyper-V virtual switch for virtual machines that are using 1-gigabit network adapters. VMQ is enabled on a Hyper-V virtual switch only when the system is using 10-gigabit or faster network adapters. This means that by disabling VMQ on the Broadcom network adapter, you are not losing network performance or any other benefits because this is the default. However, you need to do this to work around the driver issue.

Get-NetAdapterVmqQueue shows the virtual machine queues (VMQs) that are allocated on network adapters. You will not see any virtual machine queues that are allocated to 1-gigabit network adapters by default.

• Symptome:
  • Netzwerkverbindung zu den virtuellen Maschinen fällt aus
  • Virtuelle Maschinen können nicht mehr heruntergefahren werden (Problem mit Netzwerk) trifft Linux, Windows..
  • Nur ein Kaltstart des Hostsystems regeneriert die Lage

• VMQ deaktivieren auf Powershell (get-Netadaptervmq) und in der GUI vom Hyper V bei den erweiterten Eigenschaften !!
• https://www.reddit.com/r/sysadmin/comments/5zxlzc/hp_ml350_gen9_hyperv_issues_with_2012r2/#
• https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04719558
• https://support.microsoft.com/en-sg/help/2986895/virtual-machines-lose-network-connectivity-when-you-use-broadcom-netxt

• Avago MegaRAID RAID SAS 9361-8i Controller (mit Battery Pack)
• SSD RAID10

------------------------------------------------------------------------------
CrystalDiskMark 7.0.0 x64 (C) 2007-2019 hiyohiyo
                                  Crystal Dew World: https://crystalmark.info/
------------------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

[Read]
Sequential 1MiB (Q=  8, T= 1):  2917.503 MB/s [   2782.3 IOPS] <  2872.92 us>
Sequential 1MiB (Q=  1, T= 1):  1146.174 MB/s [   1093.1 IOPS] <   913.20 us>
    Random 4KiB (Q= 32, T=16):   479.321 MB/s [ 117021.7 IOPS] <  4370.88 us>
    Random 4KiB (Q=  1, T= 1):    33.044 MB/s [   8067.4 IOPS] <   123.25 us>

[Write]
Sequential 1MiB (Q=  8, T= 1):  1079.696 MB/s [   1029.7 IOPS] <  7743.43 us>
Sequential 1MiB (Q=  1, T= 1):  1051.736 MB/s [   1003.0 IOPS] <   994.51 us>
    Random 4KiB (Q= 32, T=16):   162.600 MB/s [  39697.3 IOPS] < 12873.30 us>
    Random 4KiB (Q=  1, T= 1):    63.628 MB/s [  15534.2 IOPS] <    63.89 us>

Profile: Default
   Test: 1 GiB (x5) [Interval: 5 sec] <DefaultAffinity=DISABLED>
   Date: 2020/06/17 13:21:10
     OS: Windows Server 2019 Server Standard (full installation) [10.0 Build 17763] (x64)

• SAS 7.2k RAID1

------------------------------------------------------------------------------
CrystalDiskMark 7.0.0 x64 (C) 2007-2019 hiyohiyo
                                  Crystal Dew World: https://crystalmark.info/
------------------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

[Read]
Sequential 1MiB (Q=  8, T= 1):   512.458 MB/s [    488.7 IOPS] < 16287.11 us>
Sequential 1MiB (Q=  1, T= 1):   434.599 MB/s [    414.5 IOPS] <  2409.16 us>
    Random 4KiB (Q= 32, T=16):    12.390 MB/s [   3024.9 IOPS] <162041.59 us>
    Random 4KiB (Q=  1, T= 1):     1.385 MB/s [    338.1 IOPS] <  2946.58 us>

[Write]
Sequential 1MiB (Q=  8, T= 1):   293.193 MB/s [    279.6 IOPS] < 28396.52 us>
Sequential 1MiB (Q=  1, T= 1):   282.474 MB/s [    269.4 IOPS] <  3703.09 us>
    Random 4KiB (Q= 32, T=16):    11.424 MB/s [   2789.1 IOPS] <180483.72 us>
    Random 4KiB (Q=  1, T= 1):    10.530 MB/s [   2570.8 IOPS] <   386.99 us>

Profile: Default
   Test: 1 GiB (x5) [Interval: 5 sec] <DefaultAffinity=DISABLED>
   Date: 2020/06/17 13:28:21
     OS: Windows Server 2019 Server Standard (full installation) [10.0 Build 17763] (x64)

• HP ML350 Gen9 - Hardware RAID (Smart Array P440 (PCI Express)) mit 2 15K SAS Serverplatten
• Intel Xeon E5-2620V4 @ 2.1GHZ (2 Prozessoren) , 64 GB RAM

-----------------------------------------------------------------------
CrystalDiskMark 5.2.1 x64 (C) 2007-2017 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :   436.417 MB/s
  Sequential Write (Q= 32,T= 1) :   474.819 MB/s
  Random Read 4KiB (Q= 32,T= 1) :    14.301 MB/s [  3491.5 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   116.758 MB/s [ 28505.4 IOPS]
         Sequential Read (T= 1) :   506.653 MB/s
        Sequential Write (T= 1) :   406.023 MB/s
   Random Read 4KiB (Q= 1,T= 1) :     3.965 MB/s [   968.0 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :    91.430 MB/s [ 22321.8 IOPS]

  Test : 2048 MiB [C: 24.3% (67.7/278.8 GiB)] (x5)  [Interval=5 sec]
  Date : 2019/07/02 14:20:51
    OS : Windows Server 2012 R2 Server Standard (full installation) [6.3 Build 9600] (x64)
  

• HP Microserver gen8 - Software RAID1 (Windows 2012r2 Software RAID1 - AHCI Modus, Bessere Leistung , Schreibcache JA, Windows veranlasstes Leeren des Cache deaktivieren) mit 2x 256 GB Samsung SSD (consumer Version, eine 840er und eine 860er EVO )
• Intel Celeron G1610 2.3GHZ, 4GB RAM

-----------------------------------------------------------------------
CrystalDiskMark 5.2.1 x64 (C) 2007-2017 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  1045.927 MB/s
  Sequential Write (Q= 32,T= 1) :   500.788 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   218.880 MB/s [ 53437.5 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   119.822 MB/s [ 29253.4 IOPS]
         Sequential Read (T= 1) :   523.572 MB/s
        Sequential Write (T= 1) :   490.762 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    38.264 MB/s [  9341.8 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :    79.639 MB/s [ 19443.1 IOPS]

  Test : 2048 MiB [C: 3.8% (8.9/232.5 GiB)] (x5)  [Interval=5 sec]
  Date : 2015/11/03 1:46:30
    OS : Windows Server 2012 R2 Server Standard (full installation) [6.3 Build 9600] (x64)
  

• Default Route hinzufügen am Beispiel Destination 0.0.0.0 , MASK 0.0.0.0 , Next HOP 192.168.64.254

• Convert RAW Disk to VHD mit Virtualbox:

VBoxManage.exe convertdd disk.raw disk.vhd --format VHD

• Deinstallation manuell anstoßen:
• https://answers.avira.com/en/question/wie-kann-ich-nanoheal-deinstallieren-69923

 Anonymous

Sollte die Deinstallation über die Nanohealconsole nicht funktionieren, kann der Uninstaller über die Kommandozeile aufgerufen werden:

"C:\Program Files\Nanoheal\Client\cutil.exe" -5
10 months ago