RN 102 update firmware from 6.9.5 to 6.10.0 and now won't boot UGH!!

More information, more poking around.

on startup there were a series of processes running, and these seem to have stuck in trying to update (automatically?  online??) the subversion library used by apache2.

So this is probably related to the underlying update of apache2 that I've read about in other posts.

Here's what ps -eaf in SSH was showing:

root      3745  3744  0 11:50 ?        00:00:00 /bin/sh -c dpkg --configure -a
root      3746  3745  0 11:50 ?        00:00:00 dpkg --configure -a
root      3747  3746  0 11:50 ?        00:00:00 /bin/sh /var/lib/dpkg/info/libapache2-mod-svn.postinst configure
root      3761  3747  0 11:50 ?        00:00:00 /bin/sh /usr/sbin/invoke-rc.d apache2 restart
root      3792  3761  0 11:50 ?        00:00:00 systemctl restart apache2.service

By simply killing all those processes, I could then see that apache started after, and furthermore my attempts at

apg-get update 

and similar would not stop with a lock error. 

I've not yet been brave enought to reboot (expecting the fault to come back), thats coming up.

So far everything seems to be working EXCEPT subversion.

A long long time ago, I installed subversion using the direction here:

https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/subversion-configuration/m-p/860158#M1163

Since that time subsequent updates of the OS have clearly updated SVN as I see that in /usr/lib/apache2/modules, the file mod_dav_svn.so is dated May 21, 2018.

What seems to have gone wrong this time is that mod_dav_svn.so, and its cousin mod_authz_svn.so seem to have failed in the update from apache 2.2 to apache2.4, OR in the auto-update-on-bootup process.

As to waht to do about it... this is still to be worked out.

It means that for now, I have the NAS back running for backup purposes, but my primary need was SVN... and that does not work.