Eduardo
-
Posts
145 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Eduardo
-
-
Only SN? Does Xpenology work without matching MAC? I thought a paired MAC-SN was needed to run it.
-
5 hours ago, Oelli said:
I have succesfully updated my n54l from 6.0.2 to 6.1.3 update 1 with ejt01´s guide. I can confirm that this works fine.
The only issue I´m having right now is that unfortunately WOL has stoppped working since I updated. I got the same MAC as before and inbefore it worked flawlessly. If someone has a suggestion as how I could get it to work again, it would be much appreciated
Does your Xpenology MAC match with your real MAC?
-
3 hours ago, neotronic said:
I found the grub file was created on the USB boot media after installation of the latest update. The trick is to power off after the update restart and look for the file on the USB media (plug it into your PC), edit the file and update with the version of the update you just applied. Reinsert the boot media in your server and boot up. You should be ok then.I'm lost. What's the matter with this file? Why are you editing it?
-
Khile's bootloader included a bunch of modules for AMD N54L. USB 1.1 working, etc.
Can you check if this bootloader has these modules?
-
3 minutes ago, pehun said:
Sorry,
I thought it was a different script than yours
-
2 hours ago, pehun said:
Hello,
Where could I get the "workaround script "?
Bruno
Hi Bruno, are you joking?
On 16/7/2017 at 9:59 PM, Eduardo said:Hi Bruno,
Sure it is.
For now, I'm using a trick to update without loosing anything. 6.1.3-15152 at the moment. Working flawlessly.
Just created a script to copy modules from /lib/modules/update to /lib/modules and reboot. It only acts when needed.
I attached the script.
I'm a linux newbie. Somebody would improve it, but it is working here.
Instructions:
Put it anywhere.
Set X permission to be executable (0744).
Go to scheduled tasks and program it on reboot. Root user.
Go to DSM and update from web UI normally.
I set a long time to reboot (720s) for safety reasons. In case of loop, I think is enough to disable the task. So, be patient.
As it only should work when needed, you can leave this task enabled.
I'm not an expert. Please, don't blame me if something fails.
-
You can leave the task enabled. It will check if needs to copy and reboot. Only if needed. This way you won't forget when updating.
-
1
-
-
On 17/7/2017 at 3:51 PM, pehun said:
Sorry for my english faults
Thanks for the procedure.
But at witch moment you plug a usb key with the new loader?
At the reboot?
Bruno
No need to change loader. You keep Khile's one as before. You simply update from DSM UI keeping all your data and configuration untouched.
-
6 hours ago, pehun said:
Thanks a lot Eduardo,
So you just copy the datas, and the update propose the update function?
Bruno
Sorry. I just can't understand what you mean.
I attached a file (script). You just should copy it somewhere (share) in the NAS and give this file X permission.
After that, go to DSM UI Panel Control and program a scheduled task that will be execution of this script. On boot, root user parameters.
Now you are ready to update. Go to DSM UI Control Panel and Update normally.
One test you could do before updating is running the script without updating, just to assure it will work.
As I told you, after updating and reboot, script action will add a new long reboot. Don't worry.
-
1
-
-
On 13/7/2017 at 5:14 PM, pehun said:
Hello All,
Thanks a lot for the loader.
Does a version which permit update mode is in progress?
Bruno
Hi Bruno,
Sure it is.
For now, I'm using a trick to update without loosing anything. 6.1.3-15152 at the moment. Working flawlessly.
Just created a script to copy modules from /lib/modules/update to /lib/modules and reboot. It only acts when needed.
I attached the script.
I'm a linux newbie. Somebody would improve it, but it is working here.
Instructions:
Put it anywhere.
Set X permission to be executable (0744).
Go to scheduled tasks and program it on reboot. Root user.
Go to DSM and update from web UI normally.
I set a long time to reboot (720s) for safety reasons. In case of loop, I think is enough to disable the task. So, be patient.
As it only should work when needed, you can leave this task enabled.
I'm not an expert. Please, don't blame me if something fails.
-
36 minutes ago, ordimans said:
You are right.
But i think it's same method, just need to find driver compiled for this kernel.
But i don't know why, but loader 1.01 with 6.02 my UPS doesn't work on USB of N40L.
Now with the new loader custom for AMD (1.02b) it's working...Did you compile 1.02b? If referring Khile's bootlader is 1.02a, isn't it?
-
He dado por supuesto que la CPU es Intel G1610T, no un Xeon.
-
Están basadas en diferentes plataformas. Ya te puse cuál es la más apropiada para la tuya. Con el buscador te saldrán, en inglés, los detalles de cada una.
-
No conozco el firmware de Netgear. Puede que te permita todo lo referido. ¿Tiene servidor de OpenVPN?.
Yo uso el de Shibby http://tomato.groov.pl/ Desde hace años. En Linksys y en Asus. Encantado con él. Si te gusta, no olvides donar. Que el trabajo del muchacho realmente lo merece...
-
Para el 6.1.1 tienes que cambiar el usb que utilizas de boot. Mira en el hilo del 6.1.1. Tienes los vínculos al principio. http://xpenology.com/forum/topic/7046-juns-alpha-loader-for-dsm-61/ . Por lo que he leído, para el G8 celeron, mejor utiliza Jun's v1.02a + DS3615xs. Muy aconsejable instalación limpia. Más, en tu caso, que estás en prueba.
Para wake on lan, MAC ethernet física, real, de tarjeta de red y MAC del DSM (configurada en el Grub) deben coincidir. Yo modifiqué la física para que combinara con un número de serie, pero no es necesario. Después, debes lanzar el paquete mediante algún procedimiento. Yo lo hago mediante el router, al cual le tengo instalado el Firmware Tomato y tiene esa función, pero puedes buscar otros procedimientos que no sean QC y no abusar de Synology.
Respecto al ruido del G8, yo tengo un G7 y poco te puedo decir. Leí por ahí que era un problema que se solucionó tras una actualización de Bios de HP y que ahora sólo hace ruido al arrancar. Luego, se tranquiliza. Otro tanto te digo del ILO. Ya quisiera yo tenerlo en el G7. Me temo que el G8 viene con una licencia light del ILO y sin complicarte mucho no vas a poder acceder desde fuera. Nuevamente, con un router avanzado, se consiguen muchas cosas. Si tiene servidor de OpenVPN, ya estás en red local desde fuera, por ejemplo. OpenWRT o Tomato son estupendos para esos juegos.
-
Bueno, al final ya lo pedí y ya tengo mi G8. Ayer mismo, tras algunos problemillas de configuración inicial, ya conseguí instalar DSM 6.0 y pude realizar las primeras pruebas desde la red interna. Configuré los dos discos duros como RAID 1 y ahora me toca seguir enredando.
Gracias por todo y un saludo. (Seguro que daré más guerra)
¿y por qué no el 6.1.1?
-
El G8 no es de lo más moderno, pero sale bastante más barato que construir con mini itx. Cualquier caja + fuente decente ya cuesta bastante.
No he estudiado el consumo, pero tampoco creo que sea mucho más respecto a la opción de autoconstrucción, salvo que uses una MIni itx con NUC moderno. Y el ILO es un valor añadido.
-
Por lo que me dices, entonces, para ver el contenido en la TV debo hacerlo a través de la red, olvidándome de la salida HDMI, ¿no?
En mi opinión, para eso, por seguridad y por eficacia, un TV-Box de 35€-60€ por televisor. Reproduce 4k sin problemas. IPTV y lo que quieras. Y al NAS lo dejas en funciones de NAS. Yo tengo un NAS, dos televisores y dos TV-Box. Uno de los TV-Box lo he dejado en Android y el otro está, ahora, con LibreELEC. Ver, no veo casi nada. Pero cacharrear, todo lo que quiero.
-
(if i "gap" in the internal sata ports is allowed - never tried that)
Yes, gap has been working here from some years ago. I mapped to eSATA flawlessly.
-
So out of the box DSM recognized the 8 LSI ports and then 4 out of the 8 Mobo ports. I tried hotswapping between the MOBO ports but only 2 out of the 4 listed are working. So the two marvell ports are working but the 6 intel ports are now. Im fine with buying another LSI card and running 18 ports. I have no idea how to use GRUB to map the ports correctly.
This is my mobos sata controllers.
Intel® X79 chipset :
2 x SATA 6Gb/s port(s), brown
4 x SATA 3Gb/s port(s), black
Support Raid 0, 1, 5, 10
These 2 are part of the 4 since
Marvell® PCIe 9128 controller :
2 x SATA 6Gb/s port(s), gray
Did you try SataPortMap=242 or SataPortMap=62?
-
asumtion on that is the system (dsm) finds the 4+2 (or 4+1+1) onboard first and the lsi is last
what you did (with the placeholders for a "1") would correctly "writen" look like this
(lis = 8 Ports = 8 x 1, mobo 4 x 1)
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0011 0000 = esataportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0011 1111 1000 0000 = usbportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 011 1111 1100 1111 = internalportcfg
or with additinal "0" from the right side, so its good to read
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0011 0000 = esataportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0011 1111 1000 0000 = usbportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0011 1111 1100 1111 = internalportcfg
(red marks a error, 3 bit instead of 4, but in this case it does'nt matter it's only the "0" for filling)
you see the problem (to "read" from left to right = lower bits first)?
internal and usb overlaping - not good
It makes sense. I'll try it. Not sure why I had seven "1" on usbportcfg.
And what about Grub? SataPortMap=68 ?
-
I'm almost in the same boat. That's a nightmare!
Actually:
HP N54L + LSI SAS9211-8I + 5.2 DSM
N54L has 6 sata ports (4 sata, 1 eSata, 1 optical Sata) and 6 USB ports
LSI SAS9211-8I has 8 sata ports.
I changed ODD with a hot swap bay case.
I want Back eSATA and ODD set as eSATA. That's my goal.
As the 8 ports of the LSI SAS9211-8I appear as one on esataportcfg (7th) and can't separate 2 from the rest, my solution was:
Four internal disks are controlled by the LSI SAS9211-8I
Back eSATA and hot swap bay case (ODD) are set eSATA and controlled by N54L MOBO
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00(ODD)(back_eSATA) 0000 = esataportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0011 1111 1000 0000 = usbportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0(LSI 8 ports)00 (MOBO_sata)(MOBO_sata)(MOBO_sata)(MOBO_sata) = internalportcfg
So, config that works flawlessly:
esataportcfg="0x0030"
usbportcfg="0x3f80"
internalportcfg="0x004f"
maxdisks="12"
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0011 0000 = esataportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0011 1111 1000 0000 = usbportcfg
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0100 1111 = internalportcfg
I think is time to move to 6.1.1, but after reading and reading some times, I still can't understand and I'm not sure what to set on grub and synoinfo.conf.
-
Yes. Resolved in 2.3. Read the roadmap people.
Hi quicknick
Can't find about Drivers for USB 1.1 (for UPS). Any info?
-
USB 1.1 Support for my UPS
+1
Is DSM checking SN for video conversion?
in Packages & DSM Features
Posted
I knew about propietary apps/features and SN/MAC generators rules. I don't use them. But I thought paired SN/MAC was needed for running XPEnology itself. Thanks for the info.