Huberer
-
Posts
62 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Huberer
-
-
Some to my system (see sig.). Everything works ok after reboot
-
Hi Sancome,
since many new cpus (N3700 Braswell for ex.) cannot be used at the maximum performances with acpi_freq,
can you compile intel_pstate module in the next release?
I would like to try if it will raise correctly.
thanks
br
Neverstopdreaming
+1
That would be great. Thanks in advance
-
Ja, es gibt eine Idee. Das was du machen willst, bist du hier vermutlich falsch. Schau dazu im synology-forum.de nach. Dort haben User ein Script entwickelt, dass auf einer Syno läuft und beim Anstecken ein bestimmten HDD (erkennbar über die UUID) sofort ein Backup macht. Nach Entfernen dieser wartet das Script im Hintergrund auf das neuerliche Anstecken dieser Platte. Wird eine andere Platte angesteckt, dann erkennt das Script, dass es keine Backupplatte ist und macht nichts. Natürlich dürfte dieses Script auch auf einen XPEno-Nas laufen. Also schau dich dort mal um. Hab jetzt im Moment keinen link dazu nur gibts das wirklich, weil ich einmal über diesen Beitrag drüber gestolpert bin.
Ok, hab mich hinreißen lassen und schnell gegoogelt. Hab einen Beitrag hier gefunden:
https://bernd.distler.ws/archives/1449-Synology-automatisches-Backup-auf-USB-Festplatte.html
oder hier:
weiß nicht warum beim zweiten link die URL-Einfügung nicht funktioniert. Kopiere halt den link
-
When the script is running with the command "grep "MHz" /proc/cpuinfo" it show 480MHz when the cpu is idling and 1600MHz under load and the steps in between (for all four cores and MHz varies for the single cores when cpu is working).
But without script the before mentioned command only shows 1600MHz for all four cores. Even when the cpu is idling. Under GSM GUI it shows when the cpu is idling or working (shows speedstep). I guess that the command doesn't show the real frequency (without script) but DSM is doing it correctly. That means that is better watching DSM GUI instead of watching the grep "MHz" /proc/cpuinfo - command.
In another forum a user wrote that this script also had no effect on his N40L. But I don't know which DSM and XPEnology he used.
-
I guess this script is useless with the latest DSM-firmware. The powermanagement within DSM works better instead of the script. Just my two cents. With older XPEnology and DSM maybe it's a good workaround for powermanagement but not with the latest ones. Just look at the power consumption of my "NAS" I posted one befor yours.
-
So I made a test with this script and the result surprised me:
Power consumption with script:
CPU idle and HDD's run: 22,8-23 watt
CPU idle and HDD's spin down: around 15,1 watt
Power consumption without script:
CPU idle and HDD's run: 22,0 - 22,1 watt
CPU idle and HDD's idle: 12,3 - 12,4 watt
Test with a Profitec KD 302 to measure the power consumption. My hardware is in my signatur. So I guess that this how-do is out of time and only valid for older XPEnology and DSM-firmware. If your really want to use it just test the power consumption if its good for your hardware or not. In my case I don't use it.
-
Thanks, it works great with my Asrock N3150-ITX (Intel Celeron N3150)
-
Zur Info. Nach dem du DSM installiert hast bitte einen Neustart machen, da ansonsten das Updatedate auf v5 mit einer Fehlermeldung abbricht. Dies nur so als Randnotiz
-
Did you add it three times in syslinux.cfg?
It should look like this:
UI menu.c32
PROMPT 0
TIMEOUT 50
DEFAULT xpenology
MENU TITLE XPEnoboot 5.2-5644.4-df9e09c
LABEL xpenology
MENU LABEL XPEnology DSM 5.2-5644
KERNEL /zImage
APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=XXXXXXXXXX mac1=XXXXXXXXXXXX rmmod=ata_piix vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305
LABEL debug
MENU LABEL XPEnology DSM 5.2-5644 Debug
KERNEL /zImage
APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=XXXXXXXXXX mac1=XXXXXXXXXXXX rmmod=ata_piix vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 debug=1
LABEL install
MENU LABEL XPEnology DSM 5.2-5644 Install/Upgrade
KERNEL /zImage
APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=XXXXXXXXXX mac1=XXXXXXXXXXXX rmmod=ata_piix vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.2-5644
The string should added direct after mac-address and if you don't have it direct after serial number
Just try it again
-
Did you add the command
rmmod=ata_piix/code]
to the syslinux.cfg on your boot loader? Like described here [u][b]https://idmedia.no/projects/xpenology/installing-or-upgrading-to-xpenology-5-2-or-later/[/b][/u].
If no just try it.
-
Did you reboot after the first installation? I had the same problem that I couldn't update to 5644.3 after install of 5.2-5644 (first release). I always got an error. So I rebooted my "NAS" and voila I could install the update. I had no issues with network.
My suggestion do it again right from the beginning
DSM 5.2-5967 out now - safe to install?
in Readers News & Rumours
Posted · Edited by Guest
Yes, all my settings within Hardware & Power are gone. It's possible to create a new energy timetable but can't enter any settings within hibernatemode of the harddrives. Everytime I want to enter a setting it changes automatically to the USV option and says that I have to enter something. What the hell has hibernatemode of the hdd's to do with USV....
I think there's an update of the bootloader necessary..