Aigor

Ti consiglio di aspettare la prossima release di xpenoboot, al momento il dsm6 funziona quasi, nel senso che da diversi problemi, uno assodato e' l'impossibilità di di usare il btrfs come filesystem per i volumi, poi alcuni riscontrano problemi con il package manager e il quickconnect, in sintesi, se devi usarlo a casa e dimenticartelo, usa l'ultimo bootloader, se invece hai bisogno di caratteristiche che sono presenti solo su DSM6 , be' aspetta.

I don't think we will have a short term upgrade, Synology still unpublishing gpls source , without them the team can't write new bootloader

I think it's better you run last know working version, have you need only v6 feature ?

Hi, few hints On Esxi, add serial interface on both machines and point them into a file somewhere in filesystem Both machine Must have 2 nics, one connected on lan where you can manage them, another one connected on same ethernet segment whitout ip address, those are for heartbeat Both must have MTU of 9000 Do not create any volume, both have to have same version of DSM and updates in this way you can enable HA

Only if you have a kernel compiled with specific option to export running config into /proc or, if you have compiled specific module

Try to choose second option and manual select .pat file, you onlu have to reconfigure network, users and so on, yours files are safe

Hi friends, as far you know, is there a driver already compiled to support this card Intel X520-DA2 Dual Port GbE Ethernet CNA 10 GB ? Many thanks I forgot to mention DSM 5.2-5565 Update 2 Many Thanks

Another success Acer Veriton x 270 Boot = only in installation mode Installation DSM6 = ok Update via webgui = ok Build volume = Yes only extfs4 Package fully working even with foreign package source.

viewtopic.php?f=7&t=4767 Il mac-address valido ti serve SOLO per quickconnect, basta non usare quel servizio e puoi metterci il mac originale della tua scheda di rete, in questo modo ti funziona il wol seguendo qul thread in cui ho scritto come fare.

You need to download synology gpl source of your branch you have installed at now only 5644 branch is available https://sourceforge.net/projects/dsgpl/ ... z/download expand and inside you will find 2 folder, one for 2.4 kernel and other for 3.x kernek. look inside last one and you will find a working .config file.

Ciao, il cambio Mac in e' indispensabile, serve solo se vuoi usare il servizio quickconnect di Synology, ma se hai un router dove puoi mettere le mani, non ti serve e quindi non ti serve nemmeno il cambio mac e seriale.

Hi, it's' not a question directly connected with xpenology, but my curiosity. Someone has tried to use some 10Gb card into gen8 microserver with xpenology? which model of card? Many thanks

Hi, as far i read CMS it's only for central management of several synology from one single point, it's not about cluster, or, as i suspect, it's only for management.

As far i know valid serial and MAC are needed only if you want use quickconnect feature. IMHO i prefere to use DDNS so i can have more granural way to setup my external forwarding.

Premessa, non voglio essere polemico. A mio modestissimo avviso e' meglio avere un servizio tipo noip piuttosto che appoggiarsi a quickconnect, questo perche' passi dai server synology, con noip hai un controllo piu' granulare di cosa fare o non fare. per esempio, se uno volesse installare un mail server sulla synology, quickconnect ti permette di aggiungere il record MX nella zona che lui gestisce?

Dipende, so che alcuni hanno installato Xpenology su altre nas, se non e' x86 no, non puoi, attualmente Xpenology e' fatto solo per x86 per architetture diverse ci vorrebbe un bootloader fatto apposta, cio' che e' xpenology per x86

Hi, no you can't DSM we are using it's only X86 code and it's' very hard to port on ARM, bootloader like xpenology works only in x86 mode, for arm mode there isn't any bootloader who works in different hardware. Using last model of RASP i think it's not a good idea because you don't have any sata port and you need to modify code to install operating system on usb key. If you would use rasp like Media center, use Kodi

Come risposto nel thread inglese DSM6 al momento non e' supportato, devi attendere i dev

E' standard per le synology, quindi si, e' sicuro esattamente come lvm o raid che ricordo essere fatti tutti via software

esattamente, devi usare dischi sacrificabili o vuoti dato che se li inizializzi ne perdi il contenuto.

Non puoi, Synology usa il suo shr o lvm

Jbod per usare dischi singoli, oppure crei un volume esattamente come faresti con linux, Synology usa LVM per questo.

But i'm still unable to understand why even original driver compiled from synology source with synology suggested compiler, still doesn't work maybe i miss some options or i don't know

You rigth, but i'm talking about to 4gb fc card, i know that i don't need switches if i'm using one san and one pc I bought two 4gb fc card for 20 €

Target FC mode are supported by SCST subsystem. I would like to add SCST subsystem support on synology, i'v read howto and i decide to try, SCST doesn't use already present qla2xxx module, new module will be compiled during SCST subsystem build, all the steps are ok, but the specific qla2xxx_scst doesn't read the card, the qla2xxx already present in synology works but it's useless with scst. I suppose one my fault so i wanted to try to compile qla2xxx driver already present in kernel tree, same result, it doesn't work, so it's not my fault but i suppose i miss something, or the running kernel on synology it's' compiled with certains options that i don't know or it's' not enough to have GPL kernel source from synology to compile module for qla2xxx. I suppose that source kernel from Xpenology it's' different then Synology kernel, but to much different to avoid to use this particular module, other modules compiled with synology source works well, I can not understand where is the trick, or where i'm wrong. At this time i can only ask to Xpenology dev to compile SCST with their kernel that we can not have, or i have to abandon my project, but i think it would be a mistake, because adding FC support we can use synology like real SAN due to less price of FC cards , using ISCSI we are bonded to ethernet speed or we have to buy 10Gb card that are expensive, with fc we could be in the middle way from "slow" iscsi via ethernet, to fast 10GB ethernet but they are expensive.