Polanskiman

It seems your switch is able to aggregate links >>> http://www.downloads.netgear.com/files/ ... 8feb10.pdf Look at the Layer 2 Services, there you will see IEEE 802.3ad Link Aggregation (LACP) as one of the service.

Espero aprendistes la leccion. No restaurar configuracion entre versiones diferentes. [emoji12] O sea, a la hora de instalar NO le damos a actualizar? Eso me imagino que mantendría el Raid pero no la configuración ni usuarios de la 5.2? No no. Uno puede actualizar sin ningún problem. Estábamos hablando de restauración de la configuración después de haber actualizado DSM con el archive de configuración de DSM 5.2.

A little bit of searching and reading would have brought up you an answer.

Your sata controller is a C226 Datasheet : http://www.intel.com/content/dam/www/pu ... asheet.pdf Only one controller for 6 sata HDD Use : sataportmap=6 I try that but i still get the error that HDD 5,6 are damaged and sata ports are disabled .... when i boot up with the old 5.2 everything is fine This is clearly mentioned in the OP. Try a force install.

Some bios have an option for serial enable/disable I am not acquainted with your specific machine but if you see it then I would recommend you to turn that option on. Have you tried other usb ports? Try again with another pen drive if possible. Don't forget to change vid/pid as each pen drive brand / model has its own pid/vid

Oui plusieurs personnes. Il semblerait que tout marche.

As far as I know the N54L is a BIOS machine not UEFI. Nonetheless, the loader is a hydrid loader made for UEFI and Bios MOBOs. Are you using the latest loader v.1.01? Try to burn the loader on the USB again and/or change USB key. I have seen some reports where people had dysfunctional USB keys and nothing was showing up. Make sure your bios is configured to AHCI. A BIOS reset sometimes helps. To re-assure you though other people have been able to install DSM 6.0 on a HP N54L so I don't see why you wouldn't be able to do the same. Tried three different flash drives, and did a BIOS reset. No way. Black screen. My n54l is running 5.2 with no problems. Modified vid/pid? What burning software are you using? Is your monitor plugged directly to the serial port and not some other port? It might be coming from a config issue in your bios. Make sure your serial is activate in bios. Also make sure usb key is set to be bootable from bios.

Quelle est l'erreue exacte SVP? Le fichier .pat n'est pas le coupable en principe.

Espero aprendistes la leccion. No restaurar configuracion entre versiones diferentes. [emoji12]

You could try reading the OP. That would have answered your question.

Press up/down key before the menu is shown, the same way as you enter BIOS setup screen Yes it's not a problem for me at all. I was simply conveying the message as I have seen a countless number of people missing the menu as it was too fast

Make sure you are able to boot from a usb key. You need to check in the bios that this feature is enabled. Yes sataportmap=4 should be fine if you have 4 drives. A bios reset somtimes help.

When you mount your USB key with OSFMount make sure you un-tick the "Read-only Drive" box, else any changes will not be saved to the grub file once you dismount the key. The Loader's image made by Setsunakawa and Arcao were made using an MBR partition table. That's the reason why you were able to edit it directly with your file explorer without the need of a third party software. In Win 10 you can access the pen drive without any 3rd party software. I tried with 2 different usb keys but it can't boot from them (the grub doest even show up). Tried to copy with Win32DiskImager and with rufus too.. after the dd finished I cant access my pendrive, not in my Win10 or with my mac. (I see the pendrive under disk utility without any partition) You wont be able to see it on Mac OS either. You need to issue the following commands: diskutil list this should bring the list of disks available. In my case it's: /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *640.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS El Cap_TESTING_ENVIR... 214.1 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS El Capitan 424.5 GB disk0s4 5: Apple_Boot Recovery HD 650.0 MB disk0s5 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *640.1 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Mac 1 639.8 GB disk1s2 /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_HFS Backup_OSX 1000.0 GB disk2s2 3: Apple_HFS Backup_DATA 999.9 GB disk2s3 /dev/disk3 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *4.0 GB disk3 1: EFI NO NAME 31.5 MB disk3s1 2: Linux Filesystem 15.7 MB disk3s2 3: Bios Boot Partition 4.2 MB disk3s3 find the EFI disk of the USB key. Mine is disk3s1 as you can see above. Then issue: mkdir /Volumes/efi followed by sudo mount -t msdos /dev/disk3s1 /Volumes/efi Note I have used disk3s1 in my last command. Your disk ID might not be the same so pay attention to what you are doing.

Cela est faux, il faut le VID/PID. Cela ne m'étonnerais pas que si vous n'avez pas changer le vid/pid que votre clef soit visible en tant que partitions partagées dans DSM. Les loaders fait par Jun ne sont lisibles par default que sur Windows 10 ou une distri unix. Les loader fait par Arcao peuvent être lu sur Windows XP, Vista, 7, 8, 10. Je conseil d'utiliser la dernière loader de Jun v.1.01. si vous n'avez pas Windows 10 alors vous pouvez utiliser ca pour éditer le fichier grub.cfg >>> http://www.osforensics.com/tools/mount-disk-images.html Pour le VID/PID c'est indiqué par Jun quelque message après la sorti de sa version 1.0 il indique que la gestion du PID/VID été automatique ou alors je n'ai rien compris. Ensuite pour voir les partirions autant pour mois, mais j'ai un script user qui monte automatiquement les partitions connectés ce qui fait que pour moi je voyais très bien la partition. Alors oui c'est que sur win 10 Voici ce que dit Jun: Effectivement il a implémenté une methode pour ne pas avoir à mettre le vid/pid mais il dit clairement qu'il est encore conseillé de les mettre. Moi je suis partisant du "mieux vaut prevenir que guérir" et tant que Jun ne dira pas que se passer du vid/pid est sans conséquence alors je continuerais à preconiser de mettre le vid/pid. Je dis cela car j'ai constaté que plusieurs personnes avaient des problemes et le coupable était le vid/pid. Vous êtes sous Win 7 et avec votre script vous arrivez à monter la clef et lire son contenu? Je ne suis pas sûr d'avoir bien compris. Si c'est le cas partagez votre script si possible. Ca pourra en aider plus d'un. Si vous êtes sous Windows 10 il n'y a pas besoin de script. En tout cas moi j'en ai pas besoin.

You should NEVER get the pat file from any place other than Synology's servers.

You need a compatible network switch. I am using TP-Link TL-SG2216 and you can see how I did it at http://jarvis.pimpmyrig.com/how-to-enab ... 16-switch/ If using IEEE 802.3ad Dynamic Link Aggregation or Balance XOR you are right, you need a compatible switch. I use a Cisco 200-08 However if are you using Adaptive Load Balancing or Active/Standy then a standard routeur will be enough. Obviously in this scenario there is no speed aggregation but as the options suggests either a load balancing aggregation or a basic active/standby aggregation.

I thought one second is enough Next update maybe change the timeout= parameter to default to 3 or 4 seconds. Should be plenty enough

Yes someone did. He is in the main thread. He then came asking how to un-brick his bricked paper weight >>> viewtopic.php?f=2&t=20216&p=77371&hilit=beta#p77371 That should answer your question in full.

On Win you have a s**t load of software out there. Have you tried this for example http://www.poweriso.com/download.php ? If you are on MAC OS you can do it from the disk utility. When selecting he image format you need to choose DVD/CD master and encryption None. Once it's done change the extension from .cdr to .iso Voila.

Yes me. My NICs are bonded.

No and it wont be officially. It was not supported in 5.2 so I see no reason for it to be supported in 6.0. However, I might get my hands dirty one of these days and have a try in compiling the necessary module. No promises though.

Vous vous êtes bloqué en dehors de DSM? Tous les ports sont fermés?

Es normal. Synology mejoro la seguridad en DSM 6.0 y no es possible accesar DSM via SSH con la cuenta root. Si es absolutamente necesario utilizar la cuenta root para hacer modificación entonces entra con tu cuenta admin y eleva los permisos con esto: sudo -i entra tu clave admin de nuevo y......magia.... ahora eres root. Tendras que hacer esto a cada vez que quieras acceder DSM por SSH.

Te sucede lo mismo? Gracias. Entonces eso quiere decir que el problem debe venir específicamente de su instalación.

There is no need to confirm. Most internal WLAN won't work in DSM and there is nothing new about it since Synology does not include internal wireless cards in their machines. Even under 5.2 Trantor refused to compile WLAN drivers. An internal WLAN NIC is not expected to work in DSM and I do not consider its lack on functionality as an abnormality. Those who wish to compile internal WLAN drivers can do so if they really need internal WLAN to work. Hum : Even under 5.2 Trantor refused to compile WLAN drivers. You might as well read by yourself >>> viewtopic.php?f=2&t=1361#p6528. I've copied/pasted it below for you convenience: If he ultimately decided to compile WLAN drivers then good for those who benefited from it. The basic logic concept still stands though and you might well try to understand it. Internal WLAN NICs are not part of Synology's hardware features.