I became new donator could add me new group

[wbs]

Hey,
i would like to thank you for your great work with this firmware. You made a marvelous job.
Please can you add me to the donators group, i made a donation, and i would like to install some add-ons.
Many thanks in advance ... :please

[Jocko]

Hi

You have been added in rhe donators group since two days...

But you have to set our plugout account on your bas. See :https://plugout.net/viewtopic.php?f=7&t=3224

[wbs]

Hey ,
thanks for adding me, but i got nevertheless problems to install e.g. minidlna server.
When i put in the credentials for the "plugout.net"-site and save them, i got a response message "login with given credentials is ok" but when i try to install the server the installation fails with message "Fehlgeschlagen: Installationsbefehl fehlgeschlagen, Kann nicht erstellt werden: minidlna" fyi a share minidlna is given/made in previous firmware.
Do you have some more advices for me?

[Jocko]

Hi

First step, check if nothing wrong with your account, in a shell window do :

Code: Select all

plugout check
echo $?

should return the value 0 if all is ok

Now, you can get this error message if a folder minidlna exists but the share minidlna is not set in the firmware db. You get also this error, if the firmware failed to set the right folder permissions on it.

So do

Code: Select all

grep '>minidlna' /etc/nas_conf_db.xml
ls -ld /direct-usb/minidlna

If it is the case, you can rename the folder for reusing later

Code: Select all

mv /direct-usb/minidlna/direct-usb/minidlna.old
 

And try again to install minidlna

[wbs]

Sorry again,
at the moment i can´t connect over network my nas. Only via ssh it´s possible.
In case of storing and accessing my data on nas I would like to downgrade my firmware to 18-2
but i can´t find the links for downloading anymore. After upgrading my nas isn´t useable for me.
Can you please offer me the nescessary files or links to downgrade my nas to a running system again.

Many thanks in advance ...

[Jocko]

HI

There is no change about data storing between version 18.2 and 18.3 :shocked But maybe 18.3 installation has an issue

So from firmware upgrade menu you can ask to update again the firmware to get a fresh version 18.3 or use manual installation to downgrade

[wbs]

Sorry for my late answering...
at the moment i am make a copy of my files via ssh access and it will take a couple of hours because the reduced transfer rate .
When everything is finished I will try to set up the nas again.
When i inspected the nas i found you took as base something from nslu files.
So now question: do you allthoug took their file hierarchy ? For example the config files and web interfacing?
And when I checked the root partition I found out sometimes it was filled up by 100% even when I erased installed files.
Only in case of reboot it gets reduced to something about 70%

Code: Select all

df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       244M  169M   73M  70% /
/dev/sda5       365M   88M  258M  26% /rw_fs
tmpfs           200K   80K  120K  40% /rw_fs/tmp/usr/var
/dev/sda6       465G  363G  102G  79% /share/1000

my current values

[Jocko]

Hi

Indeed your output is amazing! As I assume you are a linux man, you did not (could not) use fvdw-sl console to isntall the firmware and you did it manually.
Bad configuration, for example, sda6 is not the data partition but it must contain the kernel image :shocked

About using size on root partition, maybe some symlinks are wrong.

If you have linux acknowledge, you may follow the install script available in fvdw-sl console package to set manually your disk from a linux laptop.

This file "fvdw-sl-installer-4-0.sh" is present in the folder tftp and you need these files (location subfolder firmware in tftp) to install the firmware :
- fvdw-sl-18-1-base-v2-29jul19.files.tar.gz (common files)
- kirkwood.tar.gz (files for cloudbox)
- sda5-lacie-nwsp.tar.gz (files for sda5 partitions)
and the kernel image (subfolder kirkwood in tftp) : UIMAGE-414133-KIRKWOOD-1

Basically, the script does after creating partition table:
- write the kernel image on sda6
- format sda7 (ext3)
- uncompress fvdw-sl-18-1-base-v2-29jul19.files.tar.gz on sda7
- uncompress kirkwood.tar.gz on sda7
- format sda5 (ext3)
- uncompress sda5-lacie-nwsp.tar.gz on sda5
- format sda8 (ext4)
- create a folder public on sda8

Does nothing on sda1/2 (use for upgrading) and sda3 which is swap partition

The right partition table is

Code: Select all

root@Acrab:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 52F83CC2-D870-11EE-BA68-040E3C14B551
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            4096         1052671   512.0 MiB   8300  Linux filesystem
   2         1052672         2101247   512.0 MiB   8300  Linux filesystem
   3         2101248         3149823   512.0 MiB   8200  Linux swap
   4         3149824         3166207   8.0 MiB     8300  Linux filesystem
   5         3166208         4739071   768.0 MiB   8300  Linux filesystem
   6         4739072         4755455   8.0 MiB     8300  Linux filesystem
   7         4755456         5804031   512.0 MiB   8300  Linux filesystem
   8         5804032      5860533134   2.7 TiB     FD00  Linux RAID


as no raid is required on cloudbox, code partition for sda8 is 8300 like sda1,2,3,5 and 7