Blue blinking light then 2 red lights and then nothing

[Jocko]

Well, I do not think tftp command could do it and as other conf files (backup) must be here and it is not the case so my opinion it was not here.

Maybe you will find some ones in sda1 partition as sda5 was not mounted on the regular boot sequence and then should be written directly on sda1...

So

Code: Select all

ls -al /sda1/rw_fs/etc

Please to post also

Code: Select all

ls -al /sda5

(here should have an old backup if you made one from the web interface)

Note there was again an error in the tftp command, to download a file from the nas should be

Code: Select all

cd /sda5/etc
tftp -p -l nas_conf_db.xml -r nas_conf_db.xml ip-of-your-laptop

(-p instead of -g)

[prufa]

Thank you!

Code: Select all

root@fvdw-sta-kirkwood:/ # ls -al /sda1/rw_fs/etc
total 5
drwxrwxr-x    3 root     999           1024 Dec 12  2032 .
drwxrwxr-x    8 root     999           1024 Dec 12  2032 ..
drwxr-xr-x    2 root     root          1024 Oct 23  2032 dropbear
-rw-rw-rw-    1 nobody   nobody         806 Dec 12  2032 nas_conf_db.xml
-rw-rw-rw-    1 nobody   nobody         806 Dec 12  2032 nas_conf_db.xml.bak
-rw-rw-rw-    1 nobody   nobody           0 Oct 23  2032 nas_ext_hdd_db.xml



Code: Select all

root@fvdw-sta-kirkwood:/ # ls -al /sda5
total 56
drwxrwxr-x    9 root     999           4096 Nov 19  2031 .
drwxrwxrwt   15 root     root           400 Sep  7 05:31 ..
drwxr-xr-x    2 root     root          4096 Aug 13  2019 .config
drwx------    2 root     root          4096 Jun 26  2031 .ssh
drwxrwxr-x    4 root     999           4096 Nov 19  2031 etc
-rw-r--r--    1 root     root          9106 Jun 26  2031 installer.log
drwx------    2 root     root         16384 Jan  1  2000 lost+found
drwxrwxrwx    6 root     root          4096 Jan  2  2020 tmp
drwxr-xr-x    3 root     root          4096 Jun 26  2031 usr
drwxr-xr-x    3 root     root          4096 Jun 26  2031

Code: Select all

root@fvdw-sta-kirkwood:/sda1/etc # tftp -p -l nas_conf_db.xml -r nas_conf_db.xml 192.168.1.13
tftp: can't open 'nas_conf_db.xml': No such file or directory

I still see the file in /sda1/etc

see screenshot here from imgur:

https://imgur.com/AnKDrBu


Edit: I managed to get a copy of the nas_conf_db.xml file from /sda1/rw_fs/etc
would you like me to send it to you in pm ?

[Jocko]

Sorry for this late reply but I lost my 3G connection this afternoon

I still see the file in /sda1/etc

No you see only a symlink in etc folder but the target is no longer here (and can not work from fvdw-sl console environment)

According with the file listing from /sda5, you do not have a backup in /sda5 (so bad new)

Code: Select all

root@fvdw-sta-kirkwood:/ # ls -al /sda1/rw_fs/etc
total 5
drwxrwxr-x    3 root     999           1024 Dec 12  2032 .
drwxrwxr-x    8 root     999           1024 Dec 12  2032 ..
drwxr-xr-x    2 root     root          1024 Oct 23  2032 dropbear
-rw-rw-rw-    1 nobody   nobody         806 Dec 12  2032 nas_conf_db.xml
-rw-rw-rw-    1 nobody   nobody         806 Dec 12  2032 nas_conf_db.xml.bak
-rw-rw-rw-    1 nobody   nobody           0 Oct 23  2032 nas_ext_hdd_db.xml

No need to download nas_conf_db.xml from here (too small size for being restored) but you need to delete this orphan folder

Code: Select all

rm -r /sda1/rw_fs/etc

Now we go to restore the default nas database in sda5/etc folder:
if you have rebooted the nas, you need to repeat the mount command

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5

so upload the tarball sda5-lacie-nwsp.tar.gz from the folder tftp/firmware

Code: Select all

 cd /
tftp -g -r firmware/sda5-lacie-nwsp.tar.gz 192.168.1.13

(use this time the option -g) Check if it is now present on the nas side

Code: Select all

ls -l /sda5-lacie-nwsp.tar.gz

and update sda5 content

Code: Select all

tar -xzf /sda5-lacie-nwsp.tar.gz -C /sda5

You should have now a file nas_conf_db.xml in /sda5/etc

Code: Select all

ls -al /sda5/etc
chmod -m 666 /sda5/etc/nas_conf_db.xml

If all is ok, you can try to make a regular rebooting

Code: Select all

reboot -f

and check if you can now connect to the web interface.
If yes, create again the share fvdw and reboot the nas (to restore the addons feature)

If this step is ok, then you need to create all user accounts, shares and some server configurations like ftp...

[prufa]

I cannot thank you enough, this worked flawlessly. I've recreated the Shares and everything is working, even the cronjobs are still there!
Jocko you are one of a kind, thank you so much for all your help.

I did have to change the tftp command to

Code: Select all

tftp -g -r firmware/sda5-lacie-nwsp.tar.gz 192.168.1.13 -l sda5-lacie.nwsp.tar.gz

Also had to change the last command to

Code: Select all

chmod 666 /sda5/etc/nas_conf_db.xml

Thank you again so much for all your help.

I will definitely be donating now, I will read the instructions how to donate to you :)

Have a great weekend!

[Jocko]

Nice to heard all is back :thumbup

Maybe it would be better to make a full smart check on your disk: it may have some bad blocks what would explain why you had a corrupted fs on sda5

[prufa]

Thanks alot Jocko, I will definitely be doing a SMART check today.
I was talking to my wife and se told me there was an electrical outage few days ago, so the electricity in the apartment was off and on for few minutes. It could be the cause why suddenly my Cloudbox stopped booting.

Anyways thanks a million, I will donate tonight, I had trouble with it yesterday (problem with my paypal account) I hope I can get it sorted out today :)