Automated install from dashboard went fine (apparently)
Device seemed to work OK for one day, then I got a message about SMART Disk problem, saying to contact customer assistance:
Echec du disque SMART
Echec de l’autotest du disque. Contactez l’assistance client.
lundi 28 juillet 2014 08:20:02 Code 0003
To confirm, I tried running System Diagnostics from the dashboard, but got no response either to Fast Test (Test rapide) or to Full Test (Test Complet), so I tried rebooting.
After rebooting, front led remained fixed white and web UI stalled on “Lecture des informations de configuration” after successful login.
samba server was still working (shares accessible from Windows 7)
ssh access was still working (from Ubuntu box)
I connected via ssh, and checked which runlevel was current:
# runlevel
1 2
so the system was in runlevel 2, coming from runlevel 1
so I went on checking the startup scripts for runlevel 2 in /etc/rc2.d
# ls -l /etc/rc2.d
total 4
-rw-r–r-- 1 root root 677 Sep 10 2013 README
lrwxrwxrwx 1 root root 14 Jun 30 17:38 S01motd -> …/init.d/motd
lrwxrwxrwx 1 root root 20 Jun 30 17:42 S01wdAppEntry -> …/init.d/wdAppEntry
lrwxrwxrwx 1 root root 17 Jun 30 17:47 S04apache2 -> …/init.d/apache2
lrwxrwxrwx 1 root root 17 Jun 30 17:42 S16ntpdate -> …/init.d/ntpdate
lrwxrwxrwx 1 root root 17 Jun 30 17:46 S16openvpn -> …/init.d/openvpn
lrwxrwxrwx 1 root root 13 Jun 30 17:41 S16ssh -> …/init.d/ssh
lrwxrwxrwx 1 root root 28 Jun 30 17:42 S17monitorTemperature -> …/init.d/monitorTemperature
lrwxrwxrwx 1 root root 19 Jun 30 17:42 S18monitorio -> …/init.d/monitorio
lrwxrwxrwx 1 root root 20 Jun 30 17:46 S20nfs-common -> …/init.d/nfs-common
lrwxrwxrwx 1 root root 27 Jun 30 17:46 S20nfs-kernel-server -> …/init.d/nfs-kernel-server
lrwxrwxrwx 1 root root 15 Jun 30 17:44 S20samba -> …/init.d/samba
lrwxrwxrwx 1 root root 17 Jun 30 17:42 S20sysstat -> …/init.d/sysstat
lrwxrwxrwx 1 root root 16 Jun 30 17:45 S20vsftpd -> …/init.d/vsftpd
lrwxrwxrwx 1 root root 17 Jun 30 17:47 S20winbind -> …/init.d/winbind
lrwxrwxrwx 1 root root 18 Jun 30 17:44 S50netatalk -> …/init.d/netatalk
lrwxrwxrwx 1 root root 23 Jun 30 17:44 S60mDNSResponder -> …/init.d/mDNSResponder
lrwxrwxrwx 1 root root 18 Jun 30 17:44 S61upnp_nas -> …/init.d/upnp_nas
lrwxrwxrwx 1 root root 14 Jun 30 17:44 S75sudo -> …/init.d/sudo
lrwxrwxrwx 1 root root 16 Jun 30 17:47 S84itunes -> …/init.d/itunes
lrwxrwxrwx 1 root root 16 Jun 30 17:46 S85twonky -> …/init.d/twonky
lrwxrwxrwx 1 root root 21 Jun 30 17:46 S85wdmcserverd -> …/init.d/wdmcserverd
lrwxrwxrwx 1 root root 17 Jun 30 17:46 S86commgrd -> …/init.d/commgrd
lrwxrwxrwx 1 root root 26 Jun 30 17:46 S86wdphotodbmergerd -> …/init.d/wdphotodbmergerd
lrwxrwxrwx 1 root root 14 Jun 30 17:42 S89cron -> …/init.d/cron
lrwxrwxrwx 1 root root 14 Jun 30 17:44 S90lltd -> …/init.d/lltd
lrwxrwxrwx 1 root root 14 Jun 30 17:45 S91nspt -> …/init.d/nspt
lrwxrwxrwx 1 root root 21 Jun 30 17:45 S92wdnotifierd -> …/init.d/wdnotifierd
lrwxrwxrwx 1 root root 21 Jun 30 17:45 S95wdAutoMount -> …/init.d/wdAutoMount
lrwxrwxrwx 1 root root 23 Jun 30 17:42 S98user-start -> /CacheVolume/user-start
lrwxrwxrwx 1 root root 23 Jun 30 17:42 S99wdAppFinalize -> …/init.d/wdAppFinalize
#
Noticing file S98user-start was displayed in red, I had a closer look:
# more /etc/rc2.d/S98user-start
/etc/rc2.d/S98user-start: No such file or directory
There was no file /CacheVolume/user-start, i’m wondering whether this may have prevented the startup of some remaining functions after reboot?
In an attempt to prevent the next reboot to fail on this file again, I renamed the file to /etc/rc2.d/xxS98user-start
I was able regaining normal functionality after manually re-applying the upgrade via ssh
# cd /DataVolume/shares/Public/
# wget http://download.wdc.com/nas/sq-040000-607-20140630.deb.zip
# unzip sq-040000-607-20140630.deb.zip
# /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-040000-607-20140630.deb
which succeded but made the dead link reappear in /etc/rc2.d: S98user-start -> /CacheVolume/user-start
-> Anybody with similar experience ?
-> Any idea what this broken link should have been ?