Hello,

I got the following error during the upgrade:



So should i remove netatalk via apt-get and install it later again?

Thankks for your help....

OK i solved this problem, seems to be a problem in the script if netatalk is running, just had to stop it and it worked after it.

Now the omv-release-upgrade is not there anymore.
How can i bring the update to an end?

omv-release-upgrade isn´t there anymore, so i executed the omv-update and the line you posted above.

So did i finish the update?

Since the upgrade i´ve performance issues with the read speed, doesn´t matter which protocol (smb, afp).

Any ideas?

OK, everything working now without problems but the performance is terrible.

normaly my nas reads with 115 mb/s and writes with 80 mb/s with protocol afp.
Now read speed is maybe a bit slower but not much..... But write speed is terrible (2 - 3 mb/s ...... after some time normal speed for a few seconds....)

I tried to check the network performance with iperf.... read and write is about 117 mb/s .... so the network is not the problem....
Also tried disk speed .... write tested via dd is about 100 mb/s .... read speed tested via hdparm is about 150 mb/s.
So everything should be fine.....

Also tried to write over smb instead of afp to see whats the problem, but the terrible write speed is the same......

Strange thing.....

Do you have a idea?


Edit: Also tried to write via ftp and the problem is also the same.....

Nothing interessting....


What about the upgrade? Could this lead to such problems?

Maybe i´ve to make a fresh install.....

Reinstalled it from the ground but still the same.

Could it help to install backport kernel?

But the strange thing is that it worked with the old version.....
Really strange.....

Backports made it a little bit better but still terrible.

One interessting thing:
If i use iperf to during the copy process, it get´s much faster as long as iperf stresses the networkcard.

Maybe a p state governor problem?

Somebody else have a idea?

Edit:
Found this in dmesg:


[ 2.889818] microcode: CPU0 sig=0x30673, pf=0x4, revision=0x321

[ 2.893289] platform microcode: firmware: agent aborted loading intel-ucode/06-37-03 (not found?)

[ 2.893421] microcode: CPU1 sig=0x30673, pf=0x4, revision=0x321

[ 2.896776] platform microcode: firmware: agent aborted loading intel-ucode/06-37-03 (not found?)

[ 2.896924] microcode: CPU2 sig=0x30673, pf=0x4, revision=0x321

[ 2.900354] platform microcode: firmware: agent aborted loading intel-ucode/06-37-03 (not found?)

[ 2.900503] microcode: CPU3 sig=0x30673, pf=0x4, revision=0x321

[ 2.903793] platform microcode: firmware: agent aborted loading intel-ucode/06-37-03 (not found?)

[ 2.904007] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

There are different governors for p states (ondemand, conservative) and for c states (menu, ladder). Its a Celeron itx quad core j1900. (pretty new)
Already tried to stress the CPU, also helps a Little Bit but not as much as the LAN stress.
Hope i find a Solution otherwise i have to go back to 0.5.