ehowton: (BSD)

I've been running backups awhile now - nothing unusual - UrBackup on the UNRAID server to backup my desktop and its (seven?) volumes, and TimeMachine (also on the UNRAID server) to backup my Minis and (more importantly) the MacBook Pro - which is only connected to TimeMachine when I am on my personal VPN which allows me to connect to the UNRAID shares at home (and subsequent Windows shares through UNRAID) when I am away, which these days is more often than not. Given the storage capacity of the MacBook, I do most of my audio/video (but not AI) work on the UNRAID shares over VPN, which translates into TimeMachine not being able to assist much in that regard as it doesn't cover remote-mounted volumes (though it does cover the USB-attached volume).

I was working on the graphic below, which contains less than 20 layers, and was saving the PSD file frequently. During one of my last saves I received a "disk error" message, so saved it again - that one went through - then closed the file. As it turns out, the save wasn't successful and I was unable to open it later. I tried a variety of tools which were supposed to work, but didn't, before I remembered I had backups. I logged into the UrBackup GUI (located on the UNRAID server), selected the approximate time of the last known good backup (I've since changed it to two days worth of hourly incremental), and successfully restored my layered PSD. First chance I've had to test my restores, and I was thrilled it was so smooth and easy!



◾ Tags:
ehowton: (Sun Logo)
Trying to undo a corporate corner I painted myself into fifteen years back...

I wrote a webpage:
cat index.html | wc --> 3,827 characters

Used wkhtmltopdf to convert it to PDF, then used Word to turn it back into a webpage:
cat index.html | wc --> 6,646,652 characters



◾ Tags:
ehowton: (SGI Octane)


◾ Tags:
ehowton: (Computer)
Travel ready; new disk added to pool and full remote access to my systems:


◾ Tags:
ehowton: (Computer)

It wasn't really fun, or easy, or even really necessary if we're being honest. Mostly because UNRAID isn't much of a hypervisor, and I'm really not into that whole "Docker" thing - which looks freaking awesome if it like, worked and stuff. But I'm a sysadmin - I have needs. Things like access, and tools, and the ability to manipulate things outside their intended purpose. Dockers don't really have that. So I used VMs, but again, UNRAID is not much of a hypervisor which made things difficult. Geekfriend migrated her minecraft server from my R610 to her UNRAID, mostly because COX can eat a bag of dicks. That meant at some point, I'd likely poweroff the minecraft server. And really, the only things running on the ESX host are my bastion (openBSD) and my DNS server (rocky linux), neither of which require many resources. Figured running them on UNRAID would be non-impactful. What I didn't plan on doing was spending most of the day and all night getting something relatively easy to work. Enter the Story of my Life.

Anyway, upgraded openBSD from 6.6 to 7.5 while I was at it, and traded in rocky linux for openSUSE 15.6. What gave me the most difficulty was qemu, which UNRAID runs as it's built-in hypervisor, so I was unfamiliar with....well, just about everything.

Anyway, its done. I have a 14TB drive arriving tomorrow, which is going to be a huge pain in the ass because your parity drive has to be the largest one (the reason I only bought 12TB drives for so long) and migrating that much data is a pain in the ass. Just in case (and because Geekfriend did it also) I'm upgrading from 16GB of RAM to 64GB because running Dockers and VMs requires more than just idling storage - the idea being, I've managed to consolidate my entire homelab into a single box I could lift and ship at a moment's notice.

We'll see.



◾ Tags:
ehowton: (BSD)
When macOS can nslookup, but returns the following error when attempting ssh/ping:

ssh: Could not resolve hostname unraid: nodename nor servname provided, or not known

Simply run:

% sudo killall -HUP mDNSResponder
◾ Tags:
ehowton: (Sun Logo)

# cat /etc/hosts | grep backendNAS
192.168.0.3

# for x in {4..62} ; do echo "192.168.0.$x backendNAS" >> /etc/roundrobin_nas
# chmod 644 /etc/roundrobin_nas

# cat /etc/dnsmasq.conf | grep addn-hosts
addn-hosts=/etc/roundrobin_nas

# systemctl restart dnsmasq

# nslookup backendNAS

Name: backendNAS
IP: 192.168.1.3

Name: backendNAS
IP: 192.168.1.4

Name: backendNAS
IP: 192.168.1.5

...

Name: backendNAS
IP: 192.168.1.60

Name: backendNAS
IP: 192.168.1.61

Name: backendNAS
IP: 192.168.1.62

◾ Tags:
ehowton: (BSD)

Had an idea that would require learning how to utilize AI for text-to-speech projects, but I had to learn some things first. There's an Nvidia-specific application which sounded fun (Tachatron 2), but the RTX4090 is Ada Lovelace architecture and the app only supports Volta, Turing, and Ampere and the next one which looked interesting was ESPnet, which appears to work best on linux. So I fired up the old desktop (the one with the RTX3070) but I had to replace a brand new monitor that went out after only two months of use (ugh), then patch and upgrade the operating system since its been so long since I've powered it on.

Really only three tasks left: Figure out how to install all the inane prerequisites using incomprehensible GitHub links which don't tell you *where* to put stuff so everything can work together, try to start and run the damn thing, and (if all that works), figure out how to actually use the application. Which reminds me, since this is text-to-speech, I probably ought to hook up some sort of audio output device to the linux box.



◾ Tags:
ehowton: (BSD)
IF:

Failed to attach disk 'C:\Users\howto\AppData\Local\Packages\46932SUSE.openSUSELeap15.5_022rs5jcyhyac\LocalState\ext4.vhdx' to WSL2: The system cannot find the file specified.

THEN:

> wsl --unregister openSUSE-Leap-15.5

> wsl --install -d openSUSE-Leap-15.5


OR IF:

Error: 0x80070422 The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

THEN:

Turn Windows features on or off
Check Windows Subsystem for Linux
run --> services.msc
WSL Service --> Automatic --> Start
Reboot (if wsl won't start after the above)
◾ Tags:
ehowton: (BSD)
rmt:/var/lib/rmt/public # for x in `find . -name "*aarch64*" | sed -r 's/.{2}//'` ; do rm -Rf $x ; done
rmt:/var/lib/rmt/public # for x in `find . -name "*s390x*" | sed -r 's/.{2}//'` ; do rm -Rf $x ; done
rmt:/var/lib/rmt/public # for x in `find . -name "*ppc64le*" | sed -r 's/.{2}//'` ; do rm -Rf $x ; done

Then rmt-cli mirror just the ones you need for quick/dirty:

rmt: # for x in `rmt-cli repos list --all | grep 15 | grep SP5 | grep -v Not | grep -v Don | awk '{print $2}'` ; do rmt-cli mirror repository $x ; done
◾ Tags:
ehowton: (BSD)
# systemctl stop systemd-resolved.service
# systemctl disable systemd-resolved.service

Removed "/etc/systemd/system/dbus-org.freedesktop.resolve1.service".
Removed "/etc/systemd/system/sysinit.target.wants/systemd-resolved.service".

# ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Mar 21 2023 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

# rm /etc/resolv.conf
# vi /etc/resolv.conf
◾ Tags:
ehowton: (BSD)
zypper ref | grep "gpg-pubkey-" | xargs rpm -e
◾ Tags:
ehowton: (BSD)


◾ Tags:
ehowton: (pic#11704131)
ehowton@wdt:~> crontab -l
*/5 * * * * /home/ehowton/scripts/directory_listing_unixspook
*/5 * * * * /home/ehowton/scripts/directory_listing_wdt
*/5 * * * * /home/ehowton/scripts/rotate_lj_pic_banner.sh

ehowton@wdt:~/scripts> cat directory_listing_wdt
#!/bin/bash

rm /srv/www/vhosts/wilddamntexan/kids/index.html
echo "" > /srv/www/vhosts/wilddamntexan/kids/index.html
for x in `ls -last /srv/www/vhosts/wilddamntexan/kids/ | awk '{print $10;}'`;
do echo "$x
" >> /srv/www/vhosts/wilddamntexan/kids/index.html;
done

ehowton@wdt:~/scripts> cat directory_listing_unixspook
#!/bin/bash

rm /srv/www/vhosts/unixspook/drop/index.html
echo "" > /srv/www/vhosts/unixspook/drop/index.html
for x in `ls -last /srv/www/vhosts/unixspook/drop/ | awk '{print $10;}'`;
do echo "$x
" >> /srv/www/vhosts/unixspook/drop/index.html;
done

ehowton@wdt:~/scripts> cat rotate_lj_pic_banner.sh
#!/bin/bash
# Script which rotates my LiveJournal header image

cp /srv/www/vhosts/wilddamntexan/kids/kansas1.jpg /srv/www/vhosts/wilddamntexan/kids/spacer.jpg &
sleep 60
cp /srv/www/vhosts/wilddamntexan/kids/kansas2.jpg /srv/www/vhosts/wilddamntexan/kids/spacer.jpg &
sleep 60
cp /srv/www/vhosts/wilddamntexan/kids/kansas3.jpg /srv/www/vhosts/wilddamntexan/kids/spacer.jpg &
sleep 60
cp /srv/www/vhosts/wilddamntexan/kids/kansas4.jpg /srv/www/vhosts/wilddamntexan/kids/spacer.jpg &
sleep 60
cp /srv/www/vhosts/wilddamntexan/kids/kansas5.jpg /srv/www/vhosts/wilddamntexan/kids/spacer.jpg &

exit
◾ Tags:
ehowton: (BSD)
If your screen won't unblank after overnight, log in remotely and try this command:

dbus-send --session --dest=org.gnome.ScreenSaver --type=method_call --print-reply --reply-timeout=20000 /org/gnome/ScreenSaver org.gnome.ScreenSaver.SetActive boolean:false

If that doesn't work, this will, but will kill your current session (and everything running) and start a new one:

for x in `ps -aef | grep gnome | awk '{print $2}'` ; do kill -HUP $x ; done
◾ Tags:
ehowton: (BSD)

In more recent releases of distributions, one might notice a tendency for NetworkManager to overwrite the resolv.conf file with arbitrary numbers effectively rending name resolution inoperable. To fix, add the following verbiage to /etc/NetworkManager/NetworkManager.conf

dns=none
rc-manager=unmanaged

Then restart NetworkManager:
systemctl reload NetworkManager

◾ Tags:
ehowton: (Windows)
Windows Explorer right-click NAS folder to "Map Network Drive" and assign as X.

C:> wsl

ehowton@WSL:~$ sudo mkdir /mnt/x
ehowton@WSL:~$ sudo mount -t drvfs X: /mnt/x

ehowton@WSL:~$ cd /mnt/x
ehowton@WSL:/mnt/x$
◾ Tags:
ehowton: (Computer)
for x in `cat hostnames`; do echo $(nslookup $x | grep -e Address | sed -n 2p | sed -r 's/.{9}//') $x ; done >> hostfile



for x in `cat hostnames`; do echo $(nslookup $x | grep -e Address | sed -n 2p | sed -r 's/.{9}//') $x $(echo $x | sed "s/\..*//") $(echo $x | sed "s/\..*//").homelab.local ; done >> hostfile
◾ Tags:
ehowton: (A Beautiful Mind)
cd /oracle/MRP/origlogA
rsync -aAXxv . /tmporigA/
◾ Tags:
ehowton: (BSD)
https://documentation.suse.com/suma/4.2/en/suse-manager/client-configuration/client-upgrades-major.html

* for worky-work add proxy=[proxy] for Kernel Options (may not need)

You need at least SLES 12 SP5 before you can proceed to SLES 15 SP3/4
Upgrading from SLES 12 SP5 is only supported via an offline upgrade.

# zypper packages --orphaned
# zypper packages remove [module module module] (for Unknown URL in Add-Ons)

Systems --> Autoinstallation --> [upload autoyast.xml] --> Next -->

Add to Distribution KERNEL OPTIONS:
autoupgrade=1
useonlinerepo
insecure=1


Add to Profile VARIABLES Text Box:
IPADDR=192.168.1.69
GATEWAY=192.168.1.1
◾ Tags:
ehowton: (BSD)
Only because I keep looking for it here, and haven't (apparently) posted it yet, here's how to get neofetch to display at boot on various operating systems:

CentOS/openSUSE/SLES: echo "neofetch" >> /etc/profile.d/motd.sh

Ubuntu/Slackware: sudo bash -c $'echo "neofetch" >> /etc/profile.d/neofetch_motd.sh && chmod +x /etc/profile.d/neofetch_motd.sh'

bsd: echo "neofetch" >> /[homedir]/.profile

macOS: echo "neofetch" >> /[homedir]/.zprofile

PhotonOS: sudo bash -c $'echo "neofetch" >> /etc/motdgen.d/01-neofetch.sh && chmod +r /etc/motdgen.d/01-neofetch.sh'





pkg_add neofetch-x.x.x (https://cdn.openbsd.org/pub/OpenBSD)
apt install neofetch
zypper install neofetch

wget https://github.com/dylanaraps/neofetch/archive/master.zip
unzip master.zip
cd neofetch-master
sudo make install
◾ Tags:
ehowton: (Default)
On the cloned machine, change the hostname and IP addresses. Make sure /etc/hosts contains the changes you made and the correct host entries.

For distributions that support systemd: If your machines have the same machine ID, delete the file on each duplicated client and re-create it:

# rm /etc/machine-id
rm /var/lib/dbus/machine-id
dbus-uuidgen --ensure
systemd-machine-id-setup

For distributions that do not support systemd: Generate a machine ID from dbus:



You don't really need to do these unless errors:

rm /var/lib/dbus/machine-id
dbus-uuidgen --ensure

If your clients still have the same Salt client ID, delete the minion_id file on each client (FQDN will be used when it is regenerated on client restart):

rm /etc/salt/minion_id
Delete accepted keys from the onboarding page and the system profile from SUSE Manager, and restart the client with:

service salt-minion restart
Re-register the clients. Each client will now have a different /etc/machine-id and should be correctly displayed on the System Overview page.
◾ Tags:
ehowton: (Default)
Before you install|upgrade|reinstall anything, you need to uncomment
ONE mirror in /etc/slackpkg/mirrors and run:

# slackpkg update


# slackpkg upgrade-all


Unsure if the following two commands are required - if so, and if you find yourself unable to boot the updated system, simply boot from CDROM, mount the disk (and the associated --bind mounts) and run the following before rebooting once again:

# mkinitrd


# lilo





◾ Tags:
ehowton: (Default)
Had no idea xeyes was considered a unix "power tool"
[root@princess ~]# dnf --enablerepo=powertools install xorg-x11-apps
◾ Tags:
ehowton: (Default)
I walk into the office and Dorian has her head down; hoodie up, pounding away on her mechanical keyboard authoring her first shell script, listening to Industrial on YT. Talk about embracing your authentic self 😍
◾ Tags:
ehowton: (Default)
Find the Hog

If your users keep using up all the space in your home directory, here is a way to apprehend the top offenders.

cd /home
du -ks *|sort -nr|pg

(Note: The "k" option may not be necessary in non-posix systems.)

This string will show you all the directory sizes in order, largest first. Now if you are going to do a little cleanup yourself, in one of those directories run:

ls -ls|sort -nr|pg

This will list files by size largest first. That way when you do your compress, move, or remove, you may actually reclaim a significant amount of space.
◾ Tags:
ehowton: (Default)
When you need to recursively grep for a keyword in an older system which otherwise has no such functionality:

find . -type f -exec grep keyword {} /dev/null \;
◾ Tags:
ehowton: (Default)
Was working in my openSUSE 15.3 desktop and rebooted. So far, so good. When the box came back up and presented with with the login GUI, attempting to login errored with, "Sorry, you have to log out a previous session first. Multiple sessions are not supported." I mean, I assumed multiple sessions weren't supported but as the box had *just* come back up, I was 100% certain there were no other sessions on the box.

To fix: Shift+Alt+F1, login as root, and issue:

loginctl terminate-user ehowton


Shift+Alt+F7 back to to the login screen and login was successful.

Weird.
◾ Tags:
ehowton: (Default)

Let's talk ClusterSSH on macOS. Because ugh.
ehowton@minime % brew install csshx
Running `brew update --preinstall`...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
...
ehowton@minime % csshx
Unimplemented: POSIX::tmpnam(): use File::Temp instead at /System/Library/Perl/5.30/darwin-thread-multi-2level/POSIX.pm line 185.
Unimplemented: POSIX::tmpnam() at /usr/local/bin/csshx line 1130.
BEGIN failed--compilation aborted at /usr/local/bin/csshx line 1130.

According to StackOverflow, something with how the Perl they used to compile csshX was deprecated in the Perl included with Big Sur and Catalina. Easy fix:

# vi /usr/local/Cellar/csshx/0.74/bin/csshX

Replace:

use POSIX qw(tmpnam);

With

use File::Temp qw(tmpnam);

Works immediately.
◾ Tags:
ehowton: (Default)
When:
dnsmasq[454824]: dnsmasq: cannot open log /var/log/dnsmasq.log: Permission denied

Do:
ausearch -c 'dnsmasq' --raw | audit2allow -M my-dnsmasq
semodule -X 300 -i my-dnsmasq.pp
systemctl start dnsmasq


● dnsmasq.service - DNS caching server.
   Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2022-01-19 10:06:14 CST; 5min ago
  Process: 454824 ExecStart=/usr/sbin/dnsmasq -k (code=exited, status=3)
 Main PID: 454824 (code=exited, status=3)

Jan 19 10:06:14 bkpsrv systemd[1]: Started DNS caching server..
Jan 19 10:06:14 bkpsrv dnsmasq[454824]: dnsmasq: cannot open log /var/log/dnsmasq.log: Permission denied
Jan 19 10:06:14 bkpsrv dnsmasq[454824]: cannot open log /var/log/dnsmasq.log: Permission denied
Jan 19 10:06:14 bkpsrv dnsmasq[454824]: FAILED to start up
Jan 19 10:06:14 bkpsrv systemd[1]: dnsmasq.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Jan 19 10:06:14 bkpsrv systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
[root@bkpsrv log]# systemctl start dnsmasq
[root@bkpsrv log]# systemctl status dnsmasq
 dnsmasq.service - DNS caching server.
   Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2022-01-19 10:12:14 CST; 1s ago
 Main PID: 454964 (dnsmasq)
   Memory: 916.0K
   CGroup: /system.slice/dnsmasq.service
           └─454964 /usr/sbin/dnsmasq -k

Jan 19 10:12:14 bkpsrv systemd[1]: Started DNS caching server..
◾ Tags:
ehowton: (Default)

So I thought it would be fun and easy to simultaneously de-register VMs from one datastore path and register them on the identical datastore but through a private GB interface while also exporting an ancient WinXP VM require for iDRAC from some random volume on one computer to my VM volume on another computer utilizing two different hypervisors (both of which can hypothteically read *.ova) and deleting unused zvols from FreeNAS while copying TBs of data from external drives to UNRAID while also attending to phone calls and answering emails today. You know what? It wasn't.
◾ Tags:
ehowton: (Default)

When I first set up my FreeNAS server, I had no idea what I was doing. At all. This was my proverbial toe in the water of storage. I read over all the documentation beforehand, sure, but that didn't mean I knew what I was doing.

The phenomenon surrounding FreeNAS is its use of Solaris' ZFS filesystem, a hearty, replicated aggregate of both filesystem and volume manager, underneath a FreeBSD front-end. By default ZFS requires a lot of resources, which is why I put it on my beefiest box, which just so happened to be the only box I had which contained a RAID controller which could be bypassed to allow FreeNAS to carve the raw disks directly. Or so I thought. Spoiler alert, it doesn't.

So unbeknownst to me for nearly a year, my FreeNAS instance carved its volume management from the server's RAID array. Surely this would have gone unnoticed indefinitely, excepting a single drive failure. ZFS handles drive failures with aplomb - disable the drive in the NAS GUI, hot swap and rebuild. However, because FreeNAS couldn't see the individual drive (remember, it only sees the entire array), I couldn't disable it. No problem for a hot-swap RAID array though, right? Or was it?


I posted the conundrum to the local FreeNAS forums and the reply I received was, "Well, it might work, it might not." Awkwardly enough, that was my own conclusion as well prior to posting the question. Regardless, I backed up the entire array to my UNRAID server, and for good measure powered-down the FreeNAS server before replacing the failed disk. Everything booted and the hardware RAID starting rebuilding, unbeknownst to FreeNAS, and someday (not today) I'll look at migrating away from my initial architectural failure.



◾ Tags:
ehowton: (Default)
# rpm -Uhv migrate-sles-to-sles4sap-12.1-3.1.noarch.rpm
# rpm -Uhv migrate-sles-to-sles4sap-12.2-8.1.noarch.rpm
# rpm -Uhv migrate-sles-to-sles4sap-12.3-1.8.noarch.rpm
# rpm -Uhv migrate-sles-to-sles4sap-12.4.2-4.3.1.noarch.rpm

# Migrate_SLES_to_SLES-for-SAP-12.sh

(y)
◾ Tags:
ehowton: (Default)
Matt's vm firmware upgrade:

grab file systems to that will be upgraded.
# df -h | grep vx | awk '{print $6}' | grep -v vx > list

grab vxdg that will upgrade
# vxdg list |grep -v NAME |awk '{print $1}' > list2

check volume group version
# for i in $(cat list2); do vxdg -q list $i |grep version; done

upgrade volume groups
# for i in $(cat list2); do vxdg upgrade $i; done

Verify VG upgrade successful
# for i in $(cat list2); do vxdg -q list $i |grep version; done

Now upgrade file system versions, check version level for each.
# df -h |grep vx| awk '{print $1}' |grep -v tmpfs > vxfs.out
# for i in $(cat vxfs.out); do /opt/VRTS/bin/fstyp -v $i |grep version; done

Step upgrade each file system, if current version is 9 start with 10 and upgrade through 15.
# for i in $(cat list); do /opt/VRTS/bin/vxupgrade -n 10 $i; done
# for i in $(cat list); do /opt/VRTS/bin/vxupgrade -n 11 $i; done
# for i in $(cat list); do /opt/VRTS/bin/vxupgrade -n 12 $i; done
# for i in $(cat list); do /opt/VRTS/bin/vxupgrade -n 13 $i; done
# for i in $(cat list); do /opt/VRTS/bin/vxupgrade -n 14 $i; done
# for i in $(cat list); do /opt/VRTS/bin/vxupgrade -n 15 $i; done

Finally verify all vxfs are version 15 now
# for i in $(cat vxfs.out); do /opt/VRTS/bin/fstyp -v $i |grep version; done

IF YOU GET A SIMILAR ERROR:
UX:vxfs vxupgrade: ERROR: V-3-27659: /sapmnt/SID is not a mountpoint
and the raw device cannot be deduced.
use [-r] to specify a raw device

Find the *actual* path via /etc/fstab & /etc/auto.direct and upgrade that path separately:

# /opt/VRTS/bin/vxupgrade -n 10 /export/sapmnt/SID
# /opt/VRTS/bin/vxupgrade -n 11 /export/sapmnt/SID
. . .
. . .
. . .
# /opt/VRTS/bin/vxupgrade -n 15 /export/sapmnt/SID
◾ Tags:
ehowton: (Default)
IF THIS:

UX:vxfs mount.vxfs: ERROR: V-3-22168: Cannot open portal device: No such file or directory
UX:vxfs mount.vxfs: ERROR: V-3-25255: mount.vxfs: You don't have a license to run this program

THEN THIS:

# modprobe vxportal
# lsmod | grep vxportal
vxportal 16384 0
vxfs 3923968 1 vxportal
veki 20480 9 vxfs,vxio,dmpaa,dmpap,vxdmp,dmpjbod,vxportal,vxspec
# mount -a
◾ Tags:
ehowton: (Default)

To "lock" packages, use zypper "add lock"
zypper al 'kernel*'

Now you can run zypper -n update -t patch && zypper update -t patch
or
zypper up/zypper migration
All the while locking the kernel-level. You can verify lock with "list lock"
zypper ll 'kernel*'

# | Name | Type | Repository
--+---------+---------+-----------
1 | kernel* | package | (any)


Similarly "remove lock"
zypper rl 'kernel*'


When updating/migrating will likely get a list of applicable kernel combinations:
Solution 4: Following actions will be done:
  remove lock to allow installation of kernel-default-4.12.14-95.65.1.x86_64[SMT-http_smt:SLE-12-SP4-SAP-Updates]
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-736-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-1596-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-1891-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-2422-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-434-1.noarch
 Solution 5: Following actions will be done:
  remove lock to allow installation of kernel-default-4.12.14-95.68.1.x86_64[SMT-http_smt:SLE-12-SP4-SAP-Updates]
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-1596-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-1891-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-2422-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-736-1.noarch
 Solution 6: Following actions will be done:
  remove lock to allow installation of kernel-default-4.12.14-95.71.1.x86_64[SMT-http_smt:SLE-12-SP4-SAP-Updates]
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-1891-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-2422-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-1596-1.noarch
 Solution 7: Following actions will be done:
  remove lock to allow installation of kernel-default-4.12.14-95.74.1.x86_64[SMT-http_smt:SLE-12-SP4-SAP-Updates]
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-2422-1.noarch
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-1891-1.noarch
 Solution 8: Following actions will be done:
  remove lock to allow installation of kernel-default-4.12.14-95.77.1.x86_64[SMT-http_smt:SLE-12-SP4-SAP-Updates]
  do not install patch:SUSE-SLE-SAP-12-SP4-2021-2422-1.noarch
 Solution 9: Following actions will be done:
  remove lock to allow removal of kernel-default-4.12.14-95.45.1.x86_64
  deinstallation of kernel-default-4.12.14-95.45.1.x86_64
 Solution 10: remove lock to allow installation of kernel-default-4.12.14-95.80.1.x86_64[SMT-http_smt:SLE-12-SP4-SAP-Updates]

Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/6/7/8/9/10/s/r/c] (c): c
◾ Tags:
ehowton: (Default)
For SMT smt-3.0.37-52.23.6.x86_64 and greater only

# vi /etc/cron.d/novell.com-smt-randomized

Older versions remain in YAST --> Network Services --> SMT Server Configuration --> Scheduled SMT Jobs
◾ Tags:
ehowton: (Default)

I moved a formatted NVMe from one USB adapter to another USB adaptor and rebooted the host. ESXi GUI saw it as USB accessible storage, but would not mount it as a DATASTORE. Let's fix that!

# esxcli storage vmfs snapshot list

612fd952-87ba1925-3294-e45f012e79af
Volume Name: CYBERPUNK_NVMe
VMFS UUID: 612fd952-87ba1925-3294-e45f012e79af <-- note
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1

esxcli storage vmfs snapshot mount -u 612fd952-87ba1925-3294-e45f012e79af

# df -h
Filesystem Size Used Available Use% Mounted on
NFS 529.4G 438.9G 90.5G 83% /vmfs/volumes/SANDATASTORE
VMFS-6 931.2G 89.4G 841.9G 10% /vmfs/volumes/CYBERPUNK_NVMe
VFFS 13.8G 2.6G 11.1G 19% /vmfs/volumes/OSDATA-613a47c6-0701eb8e-8416-e45f012e79af
vfat 1023.8M 116.7M 907.2M 11% /vmfs/volumes/BOOTBANK1
vfat 1023.8M 32.0K 1023.8M 0% /vmfs/volumes/BOOTBANK2

Now GUI has auto-mounted as usable DATASTORE!
◾ Tags:
ehowton: (Default)


◾ Tags:
ehowton: (Default)
Originally posted by fgrehk @ Virten.net

Connect to the ESXi host with SSH
###########################################################################################################################
Stop the USB arbitrator service. This service is used to passthrough USB device from an ESX/ESXi host to a virtual machine.
(When disabling it, you can no longer passthrough USB devices to VMs)
-------------------------------------------
# /etc/init.d/usbarbitrator stop
-------------------------------------------
###########################################################################################################################
(optional) Use this command to permanently disable the USB arbitrator service after reboot.
-------------------------------------------
# chkconfig usbarbitrator off
-------------------------------------------
###########################################################################################################################
Plug in the USB device to your ESXi host. While connecting the USB device you can either watch /var/log/vmkernel.log
to identify the device name or identify it within /dev/disks. Devices are either named mpx.vmhbaXX or with an naa.X number.
-------------------------------------------
# ls /dev/disks/
-------------------------------------------
###########################################################################################################################
Write a GPT label to the device (Assuming that the Device ID is naa.5000000000000001)
--------------------------------------------------------
# partedUtil mklabel /dev/disks/naa.5000000000000001 gpt
--------------------------------------------------------
###########################################################################################################################
To create a partition you need to know the start sector, end sector, which depends on the device size and the GUID.
The start sector is always 2048
The GUID for VMFS is AA31E02A400F11DB9590000C2911D1B8
The end sector can be calculated with the following formula (Use the numbers from getptbl):
-----------------------------------------------------
# partedUtil getptbl /dev/disks/naa.5000000000000001
-----------------------------------------------------
gpt
15566 255 63 250069680
15566 * 255 * 63 - 1 = 250067789 (Your end sector)
###########################################################################################################################
You can also calculate the end sector with the following command:
------------------------------------------------------------------------------------------------------------------------
# eval expr $(partedUtil getptbl /dev/disks/naa.5000000000000001 | tail -1 | awk '{print $1 " \\* " $2 " \\* " $3}') - 1
------------------------------------------------------------------------------------------------------------------------
250067789 => Your end sector
###########################################################################################################################
Create the VMFS partition (Replace with your end sector)
--------------------------------------------------------------------------------------------------------------
# partedUtil setptbl /dev/disks/naa.5000000000000001 gpt "1 2048 250067789 AA31E02A400F11DB9590000C2911D1B8 0"
--------------------------------------------------------------------------------------------------------------
###########################################################################################################################
Format the partition with VMFS5 or VMFS6
VMFS v5
-------------------------------------------------------------------------
# vmkfstools -C vmfs5 -S USB-Datastore /dev/disks/naa.5000000000000001:1
-------------------------------------------------------------------------
VMFS v6
-------------------------------------------------------------------------
# vmkfstools -C vmfs6 -S USB-Datastore /dev/disks/naa.5000000000000001:1

NOW DO THIS:

esxcli system settings advanced set -o /Disk/AllowUsbClaimedAsSSD -I 1
esxcli storage nmp satp rule add -s VMW_SATP_LOCAL --device=mpx.vmhba32:C0:T0:L0 --option=enable_ssd
esxcli storage core claiming unclaim --type device --device=mpx.vmhba32:C0:T0:L0
esxcli storage core claimrule load
esxcli storage core claimrule run

REMEMBER TO:

In the vSphere Client, navigate to the ESXi host.
Click the Configure tab.
Under System, click Advanced System Settings.
In the Advanced System Settings table, select the Misc.APDTimeout parameter and click the Edit icon.
I've been using 600 as the value.
◾ Tags:
ehowton: (Default)


◾ Tags:
ehowton: (Default)


◾ Tags:
ehowton: (Default)
To reconfigure a thin-provisioned disk to eagerly-zeroed thick:

vmkfstools -c 100m virtualdisk.vmdk -d eagerzeroedthick

To reconfigure a thick-provisioned disk to thin:

vmkfstools -i virtualdisk.vmdk -d thin virtualdisk_thin.vmdk
mv virtualdisk-flat.vmdk virtualdisk-flat.vmdk.OLD
mv virtualdisk_thin-flat.vmdk virtualdisk-flat.vmdk

UNREGISTER in GUI
REGISTER in GUI
VERIFY DISK TYPE

rm virtualdisk-flat.vmdk.OLD
rm virtualdisk_thin.vmdk
◾ Tags:
ehowton: (Default)
When, in VMware Fusion, the left-mouse click doesn't work, do this:

Shutdown all VMs.
Quit Fusion.

# vi /path/to/virtual_machine/vm.vmx

Add:

mouse.vusb.startConnected = "FALSE"

Fix you right up.
◾ Tags:
ehowton: (Default)

Long story short, I have no idea what I'm doing. And I was frustrated I couldn't see the (TrueNAS, formerly FreeNAS) iSCSI volumes from the ESXi host. Especially since I plan on backing up the the NAS and reconfiguring it as an honest-to-god fiber-connect SAN once I build-out my UNRAID NAS server. I reached out to a vSphere guy who explained what I was doing wrong, subsequently hobbling my way through an admittedly redneck solution. But it works:

iSCSI requires communication on its own VMKernel NIC.
Created vmk1 and assigned it the IP 10.0.0.5

Unsure if VMKernel NICs required discrete interfaces.
Attached a patch cable from a port in the ESXi QFE to a port in the TrueNAS QFE, and assigned TrueNAS interface 10.0.0.4

We need a vSwitch to handle traffic from the physical adapter to the VMKernel port.
Created vSwitch1 and attached both VMKernel and vmnic3

Let storage know what's going on.
Change IP to 10.0.0.4 for Static and Dynamic targets under STORAGE --> Adapters --> Software iSCSI

Once everything was saved and rescanned, everything just sprung to life!

The TrueNAS now shows up under Storage Devices, and VMguests have the functionality to map raw LUNS :)
◾ Tags:
ehowton: (Default)
So this was a lot easier than trying to figure out how to get an XDMCP login propmt on the new flavors of linux login screen:

On the SGI box Toolchest --> System --> Utilities --> Enable Remote Display

Then on the linux host, in a console window (choose one):

yum install xnest
zypper install xnest
apt install xnest

Finally run this command:


Xnest -query host_to_connect -geometry 1280x1024 :1
◾ Tags:
ehowton: (Default)
zypper pa --orphaned > /tmp/orphaned-packages.txt

for x in `cat /tmp/orphaned-packages.txt | awk '{print $5}' | xargs` ; do zypper remove -y $x; done

reboot
◾ Tags:
ehowton: (Default)
To set a hostname on a server without an Enterprise iDRAC:

ssh user@IP

admin1> racadm config -g ifcRacManagedNodeOs -o ifcRacMnOsHostname hostname
◾ Tags:
ehowton: (Default)
Create server certificate
1.Select the newly created CA in the YaST2 CA management module.
2.Press "Enter CA".
3.Enter the CA password.
4.Select the Certificates tab.
5.Click on "Add" and choose Server Certificate.
6.Provide the requested data:
7.For Common Name put in the fully qualified domain name of the server (FQDN) of the server, for example "smt-server.example.net". This is mandatory! NOTE: If you are recreating the CA because of a server name or domain change for the SMT server do not forget to also change the url setting in the /etc/smt.conf file.
8.Add an valid email address of the server administrator and press "Add".
9.Press "Next".
10.Here it is possible to either use the CA password for the server certificate or a different one. Also key length and validity may be changed.
11.Add DNS hostname and IP address to Subject Alternative Name. Adding the IP is optional, but the DNS hostname (as the FQDN) must be added, else the certificate will not accepted on all implementations. Adding the IP address has the advantage that clients also could use IP to connect to SMT server, but as IP might change, DNS hostname should be preferred . Add additional DNS hostnames and IP addresses of the SMT server if needed.

◦Select 'Advanced Options'.
◦Select 'Subject Alt Name' (not to be confused with Issuer Alt Name!!).
◦Select 'Add'.
◦Choose 'DNS' and put int the hostname (FQDN) of the server

◦Choose 'IP' and put in the IP address of the server.
12.Select 'Next' to get to an overview over the certificate.

CREATE

TAB to highlight newly created certificate

Export the certificate as common server certificate, so that the http server apache uses it
1.On the certificates tab locate the "Export" button.
2.Select "Export as common server certificate".
3.Enter the password that was chosen for the server certificate.
4.A message "Certificate has been written as common server certificate" will be displayed.

Export the CA certificate to the smt.crt file
1.In the YaST2 CA management module change to the "Description" tab and select "Advanced / Export to File".
2.Select "Only the Certificate in PEM Format" and enter "/srv/www/htdocs/smt.crt" as the filename.
3.Select "Ok" to export the file.
4.Leave YaST.

Restart SMT
1.Restart the smt server by entering "rcsmt restart" into the root shell. This will also restart the http server apache on SMT 11/10, so that apache uses the new certificate.

NOTE: on SMT 12 SP1/2/3 servers run

systemctl restart smt.service

and

systemctl restart apache2
◾ Tags:
ehowton: (TRON)
for x in `cat hostnames`;
do echo $(nslookup $x | grep -e Address | sed -n 2p | sed -r 's/.{9}//') $x >> hostfile;
done
◾ Tags:

June 2025

S M T W T F S
1 2 3 4 5 6 7
891011121314
15161718192021
22232425262728
2930     

Most Popular Tags

Expand Cut Tags

No cut tags