The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My work

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,811 other followers

Archive for the ‘Power User’ Category

What directories to backup on ESXi apart from the VMs? – Server Fault

Posted by jpluimers on 2017/08/18

What directories to backup on ESXi apart from the VMs? – Server Fault [WayBack]:

You may want to look at purpose-built VMware backup tools. You will be very disappointed if you treat an ESXi host like a Linux/Unix server.

Use the VMware backup commands [WayBack] from a separate station, and you’ll be left with a nice configuration tarball. I would find another approach for the actual VM backups.

Edit: Host-based example

vim-cmd hostsvc/firmware/sync_config
vim-cmd hostsvc/firmware/backup_config

This stores the config in /scratch/downloads:

# vim-cmd hostsvc/firmware/backup_config
Bundle can be downloaded at :

Also see: [WayBack]


Posted in ESXi5, ESXi5.1, ESXi5.5, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »

A start job is running for dev-disk-by\… – Google Photos – Jeroen Wiert Pluimers – Google+

Posted by jpluimers on 2017/08/17

Reproduction of A start job is running for dev-disk-by... – Google Photos / Oops. Let’s see if I can reproduce it, as I think this is related: https://…

Reproducible steps below.


Tried tips from last link: fails as well

These are the modifications of the steps further on based on the last link above.

  1. After first boot, verify the WiFi drivers are there:

# rpm -qa | grep bcm43xx

  1. After editing /etc/dracut.conf.d/raspberrypi_modules.conf, perform sudo mkinitrd without any -f
  2. After reboot, same error

Error result

At boot time:

A start job is running for dev-disk-by\…

After waiting:

Reproducible steps

  1. download (or a more recent one) from :
  2. Install them on a MicroSD card
  3. Put in Raspberry Pi 3 and boot
  4. Get the IP address of the machine, then SSH into it (ssh root@ip-address, password linux)
  5. Follow the steps from [WayBackopenSUSE on Raspberry Pi 3: From Zero to Functional System in a Few Easy Steps – SUSE Blog | SUSE Communities to get WiFi working:
    1. Edit /etc/dracut.conf.d/raspberrypi_modules.conf and remove the sdhci-iproc from the first and # on the last line:From :
      add_drivers+=" sdhci-iproc bcm2835-sdhost bcm2835_dma mmc_block dwc2 "
      # Workaround for Wifi
      #omit_drivers+=" sdhci-iproc"

      To :

      add_drivers+=" bcm2835-sdhost bcm2835_dma mmc_block dwc2 "
      # Workaround for Wifi
      omit_drivers+=" sdhci-iproc"
    2. Run these commands:
      mkinitrd -f
    3. Check in Yast if wlan0 exists in System -> Network Settings, then assign an SSIS plus credentials to it
      1. Verify the list contains BCM43430 WLAN card
      2. Select it
      3. Click the Edit button
      4. Put the check mark next to Dynamic Address then select DHCP and the kind of DHCP (in my caseboth version 4 and 6)
      5. Click the Next button
      6. Keep Operating Mode as Managed
      7. Click the Scan Network button
      8. Select Network Name (ESSID) from the list
      9. Select Authentication Mode from the list
      10. Put the check mark for Key Input Type as Passphrase
      11. Enter the Encryption Key
      12. Click the Next button
      13. Click the OK button
      14. Quit Yast
      15. Wait a few moments, then very with ip a that wlan0 got an IP address
  6. Update the system:
    zypper refresh
    zypper dist-upgrade
  7. Reboot
  8. Wait for the error to occur on the HDMI screen (USB keyboard does not work there, so I cannot copy logs)

Gist log until 7. is below.

IRC chat transcript opensuse-factory

10:40am<wiertIs there anyone of the dev team here with a RPi3 that can see if my steps at reproduce?
10:40amwiertTL;DR: Tumbleweed on Rpi3; enable WiFi according to site and forum instructions; zypper dist-upgrade; boot failure.
10:41amwiertwithout enabling WiFi everything is fine.
10:41amwiertspare RPi3s get in next week, so I’ll configure this one for my brother without WiFi for now.
10:43amfvogtHm, that guide can’t actually work that way (unless something changed significantly)
10:43amwiertit worked in the sense that it got WiFi working. it failed in the sense that you cannot upgrade any more (:
10:43amfvogtThe omit_drivers line removed the driver for the sd card controller, so it’s no surprise that it doesn’t boot anymore. It needs a different device tree
10:44amfvogtI guess you upgraded the kernel + DT? You must not do that
10:44amwiertfunny as after the mkinitrd, a reboot went fine.
10:44amwiertit’s only that after a zypper dup it fails.
10:44ammnowak__DimStar, I wan’t $$ only on Windows, I should not have to re-define $prompt_sign. I guess I need to move the second $prompt_sign to the if-clause below
10:45amfvogtwiert: Ah, so it ships with a WiFi enabled DT + Kernel with the TW image
10:45amfvogtIf you zypper dup then, it’ll switch to the DT + Kernel from plain TW, breaking everything
10:46amwiertWhat’s DT?
10:46amfvogtClose, device-tree
10:46amwiert(that gist has all the steps I performed)
10:46amfvogtIt contains the assignment of memory and other HW resources to each other and drivers
10:47amfvogtwiert: “dtb-broadcom  obs:// -> openSUSE”
10:47amfvogtThat’s most likely the issue
10:48amfvogtYou can recover from that by downloading the right .dtb file and putting it on the sd card manually
10:48amfvogtAlternatively, the u-boot embedded one should still work, so you can delete the DT on the SD and it should boot again (with some missing peripherals though)
10:51amwiertI’ve already put a fresh disk image on it and I’m in the midst of configuring it for my brother (he’s mentally retarded and I’m putting it behind his TV so he can view his agenda electronically to see if that gives him more stability in organising his life; I need to be at his place in 2 hours)
11:27amwiert@fvogt: I will add this part of the IRC chat to that blog post and try to get your suggestions done when the spare RPI3s get in.


Read the rest of this entry »

Posted in *nix, Development, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, SuSE Linux, Tumbleweed | Leave a Comment »

SSD TRIM check tool | CyberShadow’s blog

Posted by jpluimers on 2017/08/17

SSD TRIM check tool | CyberShadow’s blog [WayBack] has source code on github:

trimcheck – SSD TRIM check tool for Windows

Source: CyberShadow/trimcheck: SSD TRIM check tool for Windows

It’s written in D using rdmd as compiler.


via via.


Posted in D, Development, Hardware, Power User, Software Development, SSD, Trim, Windows | 1 Comment »

Closed: HDD Guardian – Home

Posted by jpluimers on 2017/08/16

Too bad: it was fun while it lasted.

Mid april 2017 [WayBackHDD Guardian – Home closed down, so the latest commit removed all the [WayBackHDD Guardian – Source Code.

HDD Guardian provides a Windows front-end for smartctl, a utility which monitors your hard drive(s) and SSD(s) for health status, taking advantage of S.M.AR.T.

The WayBack machine and have archived some links though:

Anyone interested in getting it before codeplex itself shuts down:

git svn clone


Posted in .NET, Development, Power User, Software Development, VB.NET, Windows | Leave a Comment »

Mikrotik UDP port 5678 usage is for MikroTik Neighbor Discovery Protocol (MNDP)

Posted by jpluimers on 2017/08/14

Just in case you see UDP port 5678 in the firewall log of your MikroTik device: it’s usage of the MikroTik Neighbor Discovery Protocol (MNDP) [WayBack] protocol.

You can either block Neighbour Discovery [WayBack] in the firewall or turn it off on the MikroTik Services [WayBack] or inspect any of these protocols:

Proto/Port Description
20/tcp FTP data connection
21/tcp FTP control connection
22/tcp Secure Shell (SSH) remote Login protocol
23/tcp Telnet protocol
67/udp Bootstrap protocol or DHCP Server
68/udp Bootstrap protocol or DHCP Client
80/tcp World Wide Web HTTP
123/udp Network Time Protocol ( NTP)
161/udp Simple Network Management Protocol (SNMP)
179/tcp Border Gateway Protocol ( BGP)
443/tcp Secure Socket Layer (SSL) encrypted HTTP
500/udp Internet Key Exchange (IKE) protocol
RIP routing protocol
646/tcp LDP transport session
646/udp LDP hello protocol
1080/tcp SOCKS proxy protocol
1698/udp 1699/udp RSVP TE Tunnels
1701/udp Layer 2 Tunnel Protocol ( L2TP)
1723/tcp Point-To-Point Tunneling Protocol ( PPTP)
Universal Plug and Play ( uPnP)
1966/udp MME originator message traffic
1966/tcp MME gateway protocol
2000/tcp Bandwidth test server
5246,5247/udp CAPsMan
5678/udp Mikrotik Neighbor Discovery Protocol
6343/tcp Default OpenFlow port
8080/tcp HTTP Web Proxy
8291/tcp Winbox
8728/tcp API
8729/tcp API-SSL
20561/udp MAC winbox
/2 Multicast | IGMP
/4 IPIP encapsulation
/41 IPv6 (encapsulation)
/46 RSVP TE tunnels
/47 General Routing Encapsulation (GRE) – used for PPTP and EoIP tunnels
/50 Encapsulating Security Payload for IPv4 (ESP)
/51 Authentication Header for IPv4 (AH)
/89 OSPF routing protocol
/103 Multicast | PIM
/112 VRRP


Posted in Internet, MikroTik, Power User, Routers | Leave a Comment »

%d bloggers like this: