When the shit hits the fan …

it’s going to be messy. Well, what can I say. When releasing the Nextcloud 20 add-on I failed to test it on a NAS without PHP 7.4 already installed. Thus I didn’t notice that the automatic pulling of the required PHP packages didn’t work. Sorry for that.

Now, why don’t I just fix it? Simple reason: my development environment – which happened to be on a ReadyNAS – crashed with a 100% data loss. I’m trying to recover what I can but that takes time. Time I currently don’t have for there’s loads of work at my normal day job.

So for all of you who already tried to install the Nextcloud 20 add-on, here’s the work-around for you: Just download and install the PHP 7.4 add-on which is now available free of charge. Then install Nextcloud 20 and you should be a happy camper again.

Again: sorry for the troubles and have fun with your ReadyNAS.

NTGR repos broken for 6.10.2 (hold your updates)

Hi everyone,

Firmware 6.10.2 is out and unfortunately NTGR seems to have broken their package repositories with this release. From here it looks like there was a manual push of an updated package to the repos:

Get:2 https://apt.readynas.com/packages/readynasos 6.10.2/main armel linux-libc-dev armel [774 kB]
Err:2 https://apt.readynas.com/packages/readynasos 6.10.2/main armel linux-libc-dev armel
Writing more data than expected (774020 > 773886)
E: Failed to fetch https://apt.readynas.com/packages/readynasos/dists/6.10.2/main/pool/l/linux/linux-libc-dev_4.4.184.1_armel.deb Writing more data than expected (774020 > 773886)

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

This affects many if not all new app installations but may also have a negative impact on firmware upgrades where the ReadyNAS tries to get updated packages from its known repositories. In the worst case this error prevents the ReadyNAS from updating properly which in turn may trigger an automatic cleanup procedure which then starts to remove packages and by doing so breaks some apps. I already informed NTGR about the problem but today being Sunday I don’t expect any immediate action.

For the moment please either don’t upgrade to 6.10.2 or if you already did and ran into problems please be patient until the situation is resolved by NTGR.

Dropbox drops support for BTFRS (ReadyNAS OS 6 x86)

Hi everyone,

with great sadness I have to say that Dropbox will drop support for BTRFS and some other file systems on Linux starting November 2018.
This will render the DropboxMgr add-on useless – not because of the add-on itself, but because of the decision by Dropbox to drop support for the file system used on modern ReadyNAS boxes in their Linux client, which is what the add-on uses behind the scenes. There’s nothing I can do to fix that and thus I already made the add-on unavailable from this web site.

Now, how does this affect current users of the add-on? If you’re just using the add-on for global synchronization, i.e. if you’re using just one Dropbox account to sync your data, you should be able to switch to the Dropbox sync functionality provided by the ReadyNAS in the “Cloud” tab of the ReadyNAS web UI. If, however, you were using the add-on to sync to different Dropbox accounts (which was the main reason for the add-on) then unfortunately there’s no solution that will allow you to continue to emulate that functionality in the future.

I have no idea what made Dropbox to decide that only Ext4 will be supported from November on but that’s the way it is. I’m sorry for all of you who are affected by this decision and I’d like to thank you for your support over the years but sadly the story of the DropboxMgr add-on ends here.

Sorry for the Rough Ride

Hi there. As you surely noticed the site was down for the last couple of days. This was due to a chain of events that in the end resulted in a complete outage. The system the site is hosted on is running from a dedicated server and the data resides on a simple RAID-1 array. On Monday one of the drives in that array died and so the site went down for the first time. Using the rescue system I was able to create a current backup (in addition to the ones that are created automatically) and ordered the failed drive to be replaced. This was done but while restoring the array the second drive died from the stress of rebuilding. With the backup at hand I ordered the second drive to be replaced as well, screw the data on the disks and rebuild the array from scratch. Now, this process didn’t go as smooth as I hoped because the major part of the following days was spent with convincing the hoster that the new replacement drive couldn’t be bothered to join the array. Part of the delay of course was due to the fact that I need to not only go to work but also do some actual work there so that I couldn’t be immediately available for follow-up questions from the hoster which mostly consisted of “Are you really sure that we should …” and my simple answer “Yes, I am” (felt like being at an elaborate wedding at some times).
Anyway, one the array was up with a finally again replaced second drive and the OS installed I could go about reinstalling the bits and pieces. And finally I was able to restore the data which took a long, long time for I had to use my meager 2 Mbit/s uplink to transfer roughly 70 GB of data. That’s why it took so long to bring the site up again.
I heard that some of you were encountering troubles throughout the outage, mainly due to some services seemingly being dependent on some response from the site. My apologies for that, I’ll look into those reports and will try to make sure this stuff is removed or at least changed so that it will fail gracefully should another outage occur.
On the plus side I took the chance and went through all the backup systems and refined some of those to be able to get the site up faster. Still, the major blocker here is my upload speed and there’s nothing I can do about it in the near future.
That all said, I again apologize for any inconvenience and hope you still enjoy your ReadyNAS and my add-ons.

Bye-bye Slack!

Well, switching to Slack as the primary support channel didn’t work out either. Actually, I did work perfectly for the first couple of days. And then the spammers found the invite form and from there everything went downhills. I can’t restore the invite functionality for all invites have been used up and there’s no way to get them back. So I’ll close the Slack channel again and check out other options. For the time being there’s still email but given the amount of mail I receive daily due to my job there’s a good chance I’ll overlook a message or simply forget about it at the end of the day.

A side note to all those who complained that there is no email address to send support mail to: That’s not true, you for some or other reasons just didn’t try to simply use the “reply” function of your email client. Additional hint: There’s no “noreply” type mailbox here.