10 x Beep

[Warichet]

The check box "Passive-Mode" needs to be checked ?

[Warichet]

Hello Hartmut,

I would check:
- path on the ftp-Server (upper and lower case path names may have to match)
- any Limitation of space on the NAS (are there a lot of HS backup files, sometimes they don't get deleted as expected)
- the log file of the ftp server on the NAS (if any)

Thank you for the tips. I've already done my homework, but will do it again more carefully, maybe I missed it.

My NAS is in powerdown mode and the HDs don't spin up fast enough before a ftp timeout on the HS side occurs. This happens sometimes and I miss one of four remanent backups a day, but that's not critical for me.

OK, I hear the NAS's disks spin up, but as you say, this would't cause all attempts to fail.

Thanks

[HartmutB]

Debug Information regarding FTP isn't a lot of help. It doesn't give you more then an info of either "ERROR" or "OK" but nothing about possible reasons (is always "FTP").

I would check:
- path on the ftp-Server (upper and lower case path names may have to match)
- any Limitation of space on the NAS (are there a lot of HS backup files, sometimes they don't get deleted as expected)
- the log file of the ftp server on the NAS (if any)

I have similar errors from time to time, but I know their reason: My NAS is in powerdown mode and the HDs don't spin up fast enough before a ftp timeout on the HS side occurs. This happens sometimes and I miss one of four remanent backups a day, but that's not critical for me.

Regards,
Hartmut

[Warichet]

From a DOS box, I can upload a file to the Remanent directory via FTP, so I guess it's not an access rights problem

ftp> put D:\Temp\cmdline.txt
ftp: 105 bytes sent in 0,00Seconds 105000,00Kbytes/sec.

[Warichet]

Have a look at the remanent data section of your debug page!

Here it is.
It confirms what we already know:
there is an error with the FTP service
it is trying on 02.01.2014, and failed.

Maybe it is bumping against a limitation or a bad configured parameter ?
Should I implement the Ringspeicher option ?

[MatthiasS]

Have a look at the remanent data section of your debug page!

[Warichet]

Hello,

This is caused by a problem in saving remanent data (to FTP).

Thank you for the hint.
I checked the files on the NAS, last one is 2013 08 03, ouch, that's not yesterday and it confirms there is a problem with the remanent, since long.
I checked the free space on NAS, 1.4TB
I used the NAS file manager and deleted a couple of old files, no problem.

On the HS: no change I can remember (maybe the Pimp)

With Windows:ftp:// NAS ip /Ftp/HS/Remanent is reachable

See debug page!

Looks pretty empty, no error message but I guess it's not normal.

I'm stuck. From the above, I conclude the NAS is OK. I can only think about the Pimp procedure, but what could I check ?

Thanks for any hint.

[MatthiasS]

This is caused by a problem in saving remanent data (to FTP). See debug page!

[Warichet]

Hello,

As I remember, beeps via PC speaker during reboot are a BIOS functionality indicating an error.

Yes, agree.
But in this case, the beeps are send minutes after reboot.
Also, I noticed that the reboot is very slow. When looking at the client, the asterisks are displayed very slowly.

Any hint about how to troubleshoot ?

[En3rGy]

As I remember, beeps via PC speaker during reboot are a BIOS functionality indicating an error. Usually a broken memory bar. I would recommend to contact GIRA about this issue...

[Warichet]

Hi,

My HS has a problem. From time to time, I hear a string of 10 beeps, I think it is shortly after reboot. So it's not the 10 beeps every 15 min.
According to the posts talking about the subject it is

Problem with saving and/or reading the retentive memory.

How can I solve this problem ?

NB: it could be that it is a result of "Pimp my server" but which was undetected.