plugout.net

Hi to all,

after peers reported not being able to reach me through Transmission, I decided to reinstall the server (after eliminating the router as a potential source, obviously). However, the reinstallation through the Web interface fails with error -99. That is on fvdw firmware 18.2.

Exact message is:
Fail: can not retrieve the package, -99

Since I'm already a donator, this can't be the issue.

How can I trace down the source of the problem?

Hi Cubytus,

Did you see this announcement ? https://plugout.net/viewtopic.php?f=3&t=3532. You have to install the latest roll-up patch for version 18-2

Hello Jocko,

thanks for the tip. No, I didn't read it as I thought updates would be signalled by fvdw firmware itself.

Instructions weren't too clear at first, but here's an updated version:
How to install the patch :
- Save the attached zip archive in the file share 'fvdw'[1]
- From the left menu: firmware update > load patch
- Select the file by clicking on the small button [...]
- Type in the "control code" field: "shell" (without quotes)

Glad to see somebody else was able to complete the Spanish translation, sorry I couldn't find the time to do that. However a few grammatical and typos errors remain, how does one "extract" the current strings? Both the ones from your native language (I assume French, from the profile city) and the ones from the target language. Having a pinned thread about localizing would greatly help.

I didn't read however, does this patch finally solves the NFS server becoming inaccessible when a sustained transfer is ongoing? This has been a major issue as I regularly shuttle content back and forth with a bigger NAS, and it almost always requires either manual intervention, or only do small transfers at a time.

Minor issue remaining:
In the Spanish version, the SMART page buttons are all aligned on the same level. Since the words are longer in that language, there's an unsightly horizontal scrolling required.
Make the text fields wider so it doesn't require as much scrolling.

Not exactly related to the current hardware fvdw runs on, but have you thought about porting the firmware to the Western Digital My Cloud series? The company replaced their MyBook Live series that could be administered locally by the My Cloud series featuring a stronger CPU, but whose firmware is needlessly complicated, restricted and controlled by the manufacturer (based on Android, requires constant internet connectivity and a dedicated app to load files). They envisioned it as a "cloud-replacement" rather than a true NAS, and a lot of people are unhappy with the change. There was a proof-of-concept to install Debian on it, then OpenMediaVault on top, but the process remains very buggy and delicate.

Hi Cubytus,

On next patch release we will improve its howto.

Cubytus wrote:Glad to see somebody else was able to complete the Spanish translation, sorry I couldn't find the time to do that. However a few grammatical and typos errors remain, how does one "extract" the current strings? Both the ones from your native language (I assume French, from the profile city) and the ones from the target language. Having a pinned thread about localizing would greatly help.

All dictionaries are available in the folder /usr/htdocs/includes (files dictionary_xx.php). I suggest you to make a backup of those before editing because the web-interface will be broken on any php syntax error.

Cubytus wrote:I didn't read however, does this patch finally solves the NFS server becoming inaccessible when a sustained transfer is ongoing? This has been a major issue as I regularly shuttle content back and forth with a bigger NAS, and it almost always requires either manual intervention, or only do small transfers at a time.

Sorry I do not remember what was the issue. Can you detail it

Cubytus wrote:Minor issue remaining:
In the Spanish version, the SMART page buttons are all aligned on the same level. Since the words are longer in that language, there's an unsightly horizontal scrolling required.
Make the text fields wider so it doesn't require as much scrolling.

Maybe because you use a small screen ?

Jocko wrote:All dictionaries are available in the folder /usr/htdocs/includes (files dictionary_xx.php). I suggest you to make a backup of those before editing because the web-interface will be broken on any php syntax error.

Thanks, found it!

Cubytus wrote:I didn't read however, does this patch finally solves the NFS server becoming inaccessible when a sustained transfer is ongoing? This has been a major issue as I regularly shuttle content back and forth with a bigger NAS, and it almost always requires either manual intervention, or only do small transfers at a time.

Sorry I do not remember what was the issue. Can you detail it

Well, only these symptoms appear.

Have a NFS connection between fvdw and a Synology NAS configured.
Try to move 4-6GiB of data from fvdw to the Synology -> will work most of the time
Try to move 40-60GiB at a time, same direction: most of the time, fvdw becomes unresponsive, Synology detects a broken / corrupted transfer. Hierarchy from fvdw won't be shown on Synology. Transfer has to be restarted to make sure it isn't corrupted.
Doesn't happen when the same Synology NAS is moving content with another NAS, so pretty sure it comes from fvdw.

Maybe because you use a small screen ?

Well 13" isn't very large, but not exceptionally small either… The English version does fit.

Hi Cubytus,

Cubytus wrote:Well, only these symptoms appear.

Have a NFS connection between fvdw and a Synology NAS configured.
Try to move 4-6GiB of data from fvdw to the Synology -> will work most of the time
Try to move 40-60GiB at a time, same direction: most of the time, fvdw becomes unresponsive, Synology detects a broken / corrupted transfer. Hierarchy from fvdw won't be shown on Synology. Transfer has to be restarted to make sure it isn't corrupted.
Doesn't happen when the same Synology NAS is moving content with another NAS, so pretty sure it comes from fvdw.

I assume you set a remote share of your Synology on the nas. On such a case, there are many pages with the same issue on the NET and it seems it may be fixed by setting the r/w buffer size with the mount command instead of letting the kernel to manage them.

So mount command sets the value 8192 on rsize and wsize options.

To test if it fixes your issue, do

Code: Select all

plugout download 6497
tar -xf /tmp/fvdw-sl-remoteshr-nfs-buffersize-08jun2022.tgz -C /

and then mount or remount your nfs shares

Are these commands to run in the "upload patch" section?

No you have to open a SSH session

It seems file 6497 isn't the correct ID. I got "/tmp/log_diskmon_lacie.zip", but not "/tmp/fvdw-sl-remoteshr-nfs-buffersize-08jun2022.tgz" I also tried using the full file name, but it seems there's no link between the numeric ID and the filename…

Indeed it is not the right Id....
So you need to use 6947 as Id file