Right everyone. When you perform the upgrade, be aware that there is some script performed during the upgrade to 2.10.12-129 which is not working correctly, but so far things things are working properly.
r--r-- 1 root root 63 Mar 8 19:41 2
-rw-r--r-- 1 root root 0 Mar 8 19:41 alias.inc
-rw-r--r-- 1 root root 0 Mar 8 19:41 apache_userlist
-rw-r--r-- 1 root root 0 Mar 8 19:41 htgroup
-rw-r--r-- 1 root root 0 Mar 8 19:41 require.inc
drwxr-xr-x 5 root root 4096 Mar 16 02:20 root
drwxr-xr-x 2 root root 4096 Mar 8 19:41 sbin
drwxr-xr-x 2 root root 4096 Mar 8 19:37 selinux
drwxr-xr-x 21 root share 65536 Feb 21 22:16 shares
drwxr-xr-x 2 root root 4096 Mar 8 19:37 srv
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxrwxrwt 10 root root 1100 Mar 17 01:32 tmp
drwxr-xr-x 14 root root 4096 Mar 8 19:42 usr
drwxr-xr-x 12 root root 4096 Mar 8 19:42 var
Contents of the file 2 =
//etc/nasglobalconfig.ini: line 1: [global]: command not found
This may explain why some MyBook Lives are getting bricked or the update throught he Web II is not working, getting stuck at 10%. I have made Western Digital aware about this issue weeks ago but it’s either been overlooked or ignored.
For my MBL the upgrade was performed by invoking the script to upgrade from file from the Linux command line.
The files that should not be in the root directory are . . .
-rw-r--r-- 1 root root 63 Mar 8 19:41 2
-rw-r--r-- 1 root root 0 Mar 8 19:41 alias.inc
-rw-r--r-- 1 root root 0 Mar 8 19:41 apache_userlist
-rw-r--r-- 1 root root 0 Mar 8 19:41 htgroup
-rw-r--r-- 1 root root 0 Mar 8 19:41 require.inc
