Bricked NS v2 after setting miniDLNA to run automatically?

[jpjpjp]

And on the same time, maybe the other outputs would be useful later :

Code: Select all

ls -al /sda5/rw_fs/etc
ls -l  /sda5/rw_fs/nas_conf_db_ok.xml
df /sda5

nas_conf_db_ok.xml is a backup of the nas database performed manually by the user from the fw web-interface. So if it is too old, it won't be used to restore the nas database

There isn't an rw_fs subirectory in my /sda5 dir, but I did find the db file you mentioned in the /sda5/etc directory.
Here is the ouput you asked for.

Code: Select all

root@fvdw-sta-kirkwood:/ # ls -al /sda5/rw_fs/etc
ls: /sda5/rw_fs/etc: No such file or directory
root@fvdw-sta-kirkwood:/ # ls -al /sda5/etc
total 48
drwxrwxrwx    4 root     root          4096 Feb 10 17:51 .
drwxrwxrwx    8 nobody   nobody        4096 Feb 10 17:51 ..
-rw-r--r--    1 nobody   nobody           0 Oct  7  2017 bootscripts.db
drwxr-xr-x    2 root     root          4096 Feb  1  2015 dropbear
-rw-r--r--    1 nobody   nobody        1597 Oct  7  2017 install-firmware.log
-rw-r--r--    1 root     root           101 Feb  1  2015 mdadm.conf
-rw-r--r--    1 nobody   nobody           0 Feb  8 13:42 minidlnaenable
-rw-rw-rw-    1 nobody   nobody         551 Feb 10 17:51 nas_conf_db.xml
-rw-rw-rw-    1 nobody   nobody         551 Feb 10 17:51 nas_conf_db.xml.bak
-rw-rw-rw-    1 nobody   nobody        6535 Oct  7  2017 nas_conf_db.xmle
-rw-rw-rw-    1 nobody   nobody         125 Feb  7  2015 nas_ext_hdd_db.xml
-rw-r--r--    1 root     root            40 Oct  3  2009 ntp.conf
drwxrwxrwx    2 root     root          4096 Oct  2  2017 ssl
root@fvdw-sta-kirkwood:/ # ls -l sda5/etc/nas_conf_db.xml
-rw-rw-rw-    1 nobody   nobody         551 Feb 10 17:51 sda5/etc/nas_conf_db.xml
root@fvdw-sta-kirkwood:/ # df /sda5
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda5               805832      1164    796316   0% /sda5


Look for a PM from me with the db file itself.

[Jocko]

Hi

So it is a no way to repair the nas database as the current file contains only information updated on the boot script (not enough to rebuild the database).
Then you can only restore the default nas database.

Luckily this version is still present on sda5 (nas_conf_db.xmle). So do

Code: Select all

cp -f /sda5/etc/nas_conf_db.xmle /sda5/etc/nas_conf_db.xml
chmod 666 /sda5/etc/nas_conf_db.xml
chown 99:99 /sda5/etc/nas_conf_db.xml
unlink /sda5/etc/nas_conf_db.xml.bak

Now force some updating on the next boot

Code: Select all

mkdir /sda2
mount /dev/sda2 /sda2
echo 'iface:usbmountmode:timezone:phptimezone:opcache:update-ldsocache:addons:exfat:owncloud:user-update:afp-share-update:update-job-servers:update-usb-disks:update-cacert:updatesmartdrivedb:updateusbids:webconsole' > /sda2/etc/init.d/postupgrade.jobs

reboot the nas, then it should get its ip from your router and the admin credentials should be now: admin-nas/admin

You have to create again all user accounts and also your shares.

For this last step, open a shell window and run

Code: Select all

ls -l /share/1000

This will give you the name of your previous shares. (Be careful, linux is a case sensitive OS, so use the same case syntax when you create the share from the fw web-interface)
Note: no need to set again the technical shares like : cronjobs, mediatomb, minidlna, mldonkey, mp3, twonkymedia, mt-daapd, mpd, nzbget, tr-downloads or tr-daemon but only the share fvdw.
These technical shares will be set again by installing their add-on package from the fw web-interface.

If you used samba4, you have to re-install it also

Other point default nas name should be restored, then it must be "fvdwsl-base"

[jpjpjp]

Thank you! Out of town for a day or two. Will try as soon as I'm back.

[jpjpjp]

Hi Jocko.

Reading through the instructions more carefully today. Before I do this, I wanted to confirm I understood this part of your instructions:

You have to create again all user accounts and also your shares.

For this last step, open a shell window and run
Code:
ls -l /share/1000
This will give you the name of your previous shares.

Will the files that I had on my previous shares still exist? For example if I previously had a share called /share/1000/Backups and I hope to restore that share along with all the files that were previously in it, what exactly do I need to do?

Hope this question makes sense. ;)

[Jocko]

Hi

Yes that is it ! All previous shares are stored in the folder /share/1000 (in fact on the partition sda8 with a nwsp2). So the action is to set again the shares in the nas database (for example a share "Backups") to be able to get access on your previous files through the wanted servers (samba, webdav, ftp,...). But yes, your files will be still there.

About my note on the share names, still with your example, you will restore access on the files present in the folder "Backups" only if you enter "Backups" and not "backups" as sharename

[jpjpjp]

It worked! Amazing...cannot thank you enough for your help!

I'll confess I'm not quite sure what you mean by this:

Other point default nas name should be restored, then it must be "fvdwsl-base"

(I never refer to the NAS by name, always by IP address).

Finally, I can now confirm the firmware I'm using:

Code: Select all

Firmware Version   fvdw-sl 17.0 (nwsp2)
Kernel:   Linux 4.6.6 #7 PREEMPT Sun May 7 11:50:52 CEST 2017


Would you recommend an upgrade?

Again, cannot thank you enough. I have "refreshed" my donation to this project.

[Jocko]

Hi

Nice ! :thumbup

I'll confess I'm not quite sure what you mean by this:

Other point default nas name should be restored, then it must be "fvdwsl-base"

(I never refer to the NAS by name, always by IP address).

Indeed, if you are used to having access to the server by its IP, it doesn't matter to restore or not the nas name. According to your old nas database its nas name was lacie-ns2-fvdw (you can set it from the LAN setup menu)

Yes I suggest to upgrade to version 18.2. We release patches for version 17.0 only if there are some issues with the upgrade feature or to connect to plugout site.

So to do it : read this topic https://plugout.net/viewtopic.php?f=7&t=3059 So you have to perform first the step 6 and after upgrading to version 18.2, you need to install another roll-up patch https://plugout.net/viewtopic.php?f=7&t=3532
Note : the patch related to version 17.0 in this last topic is the same as the one required for step 6

Again, cannot thank you enough. I have "refreshed" my donation to this project.

Thank you so much for your additional donation ! We will use it to pay for web hosting costs for year (in next March) :)