I’m using a RaspberryPi 3 with RaspberryMatic distribution to control my HomeMatic thermostats. This distribution has a „heartbeat“ functionality, which leds the green LED of the Pi light up in constant time intervals.
These LEDs are quite strong and disturb the sleep of my family. Therefore its time to disable these leds.
Connect via SSH to the RaspberryMatic installation. Edit or create the file /usr/local/etc/rc.local and add this content:
Now try to execute the uup_download_macos.sh script again. It will now download the requested update files and will create automatically a nice ISO file, which can be used to install Windows.
As we’re using the official Windows Server Update files, this method should be legal. There is a more detailed report available ag win10.guru which explains, that most of the tool was developed by analyzing the network traffic of a Windows installation running updates. It’s also a good way to get the versions including the latest updates including the Insider builds. Of course there’s still the official download page from Microsoft.
Select other as DDNS service provider. Use dyndns.kasserver.com/ as update server with dyndns2 as protocol. Configure username and password as provided by all-inkl. Use eth0 as network interface (we’ll change this later on) and add your DynDNS Domainname.
$ sudo nano /etc/ddclient.conf
Change the file accordingly to your needs:
# Configuration file for ddclient generated by debconf
web-skip='Current IP Address: '
This config will use checkip.dyndns.org to get your currently used external IP address. If you’ll use eth0, it will probably report the internal IP address of your eth0 interface instead.
If it encounters any errors, it will send an failure email to the provided email.
I’m a longtime fan and user of automount. Automount mounts automatically my Apple Music media folder, once the Music app tries to access it.
I’ve recently updated to a Macbook with apple Silicon running Big Sur. It looks like the default behaviour changed, because I’m often adding songs to Apple music, just to see that they are copied to my SSD instead of the automounted NAS media folder.
This is incredible annoying and is probably caused by a race condition between Apple Music and automount not mounting the volume fast enough. So from time to time I’ll need to check my configured media folder in Apple music. I’ll end up changing the folder back to the automount folder and need to wait for Apple music to finish a complete scan of the library:
You can now add that link to MusicOnNAS.app to your dock, but it can only be placed in the area next to the recycle bin.
You can test this now by unmounting the volume manually on the terminal. If you click now on the link in your dock, it won’t start Apple Music. However, if you’ll click it a second time, it will start since automount has successfully remounted your volume containing the link.
Nevertheless, Apple Music forgot its media path and I’ll have to change it again to the folder. So this is just a bad workaround. Even when you’ll change the media’s path after this test, it will be reset on the next iTunes startup.
So ultimately I’ll end up with a the instructions of „Make a split library portable„, which basically says you shouldn’t separate the Apple Music library and its media. Always put the library next to the location of your media.
Also you’ll need to make sure that you’ll manually open the right .musiclibrary file. You can define the library to open when you hold the alt key before you’ll start the Apple Music app:
If you’ll just double click, it will most likely not open the right library. Somehow macOS still knows where you’ve moved your local library file (e.g. to the NAS in the automounted folder) and will open it from the new location.
With moving the library next to the media I’m somehow happy about the outcome. Looks like Apple did not consider moving the Apple Music library to any external volume and expects it to be always present in a reachable location.
A friend asked me to check her MacBook Pro 13″ from 2012. It is running unbearable slow. So I’ve made a bootable copy with Carbon Copy Cloner and TimeMachine and tried to start with a fresh installation.
I’ve created an external Bootdisk with macOS 10.15 and tried to repartition and wipe the SSD. This process took already very long and I started to wonder what might have caused this delay.
This MacBook was running fine for almost two years when I’ve replaced the internal HDD with a SanDisk SSD Plus SDSSDA-480G. All the more I was wondering why it started to be so slow without warning.
I’ve checked the cable and did not see any damages to the cable. So I’ve tried an old HDD on the same cable and repartitioning and installing was reasonable fast again.
I was still not convinced that the cable should be the problem, but decided to order a new cable including the IR receiver as well as the standby LED. There’s some sort of confusion about the right model number, but looks like 821-1480-A is the right one. I’ve ordered the cable from iFixit.com as I intended to avoid quality problems. However, you’ll get the same cable with the HDD bracket for less money from Amazon.
After I’ve replaced the cable, I’ve tried the SanDisk SSD again. The installation was still very slow so I’ve cancelled the installation. Luckily I’ve had another SSD which I could test and this one installed quite fast.
So I’ve decided to replace the exchanged cable with the original cable and rebooted the Mac. I was surprised by a login screen where the default user was unknown. I’ve only created one user on that machine and it should’ve been automatically preselected. Ok, I can type that username by myself and typed the password, but I’m unable to login at all. Either password or username are wrong?!
I’ve rebooted to the recovery partition of the currently installed SSD and tried to repartition the SSD. Deletion was now slow again and failed with this error I’ve never seen before (got the error message only in German, sorry 😞):
Das Entfernen der Volumedaten zum Verhindern zukünftiger unbeabsichtigter Überprüfungen ist fehlgeschlagen (-69825).
Searching for this error lead me to a German forum, where a user has also the same MacBook and problems with his SSD. Looks like changing the SATA cable helped in this case.
After I’ve replaced the faulty SATA cable with the new one, I was able to repartition the SSD which wasn’t deletable before.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.