jarugut
-
Posts
182 -
Joined
-
Last visited
-
Days Won
6
Posts posted by jarugut
-
-
Hi Satdream,
if you are sure that the ssd are ok, one option that you have to get access to all your data and make a copy of data is following the tutorial using a livecd of ubuntu to mount the volume.
-
I hope the information in the following file can help you. There are information about it. In the last screenshot you will see what command I applied in the past to recover one crashed volume in one storage.
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update:DSM 6.2.2-24922-3
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP N54L gen7 + Intel NIC
- Additional comment: Reboot required, restart + shutdown OK / Extra Intel NIC, ACPI Bios configured to Version 1.0.
- Outcome of the update: SUCCESSFUL
- DSM version prior update:DSM 6.2.2-24922-3
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP Microserver g8 + Intel NIC
- Additional comment: Reboot required
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 6.2.2-24922-3
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: 2 BAREMETAL - Dell Optiplex 790
- Additional comment: Reboot required
-
1
-
-
the Realtek it's compatible with DSM 6.1.x but not for 6.2.x version for 3615xs
-
I think that the AMD arquitecture in background is the responsible of your problem. I've tested the VMM in two different HP Microserver generations AMD and Intel, the result it's that in AMD the VMM not works and on Intel CPU works perfectly.
One option is to use the phpvirtualbox to virtualize instead of VMM with AMD cpu.
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update:DSM 6.2.2-24922 Update 2
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP N54L gen7 + Intel NIC
- Additional comment: Reboot required
- Outcome of the update: SUCCESSFUL
- DSM version prior update:DSM 6.2.2-24922 Update 2
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP Microserver g8 + Intel NIC
- Additional comment: Reboot required
-
if you have a realtek nic the only bootloader that is going to works is 1.02b for DSM 6.1 version.
You can try with bootloader 1.03b for DSM 3617xs, but I think this will not works.
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update:DSM 6.2.2-24922
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP N54L gen7 + Intel NIC
- Additional comment: Reboot required
- Outcome of the update: SUCCESSFUL
- DSM version prior update:DSM 6.2.2-24922
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP Microserver g8 + Intel NIC
- Additional comment: Reboot required
-
Try this file!
-
2
-
-
On 6/30/2019 at 10:16 AM, d3mone said:
Which architecture did you install?
I'm using the Bromolow, the 3615xs architecture.
-
Si te revisas el foro verás que el loader 1.04 para un N34L no es valido, ese loader es para procesadores intel superiores a generación 4 creo recordar.
El loader 1.03 te debería de funcionar siempre y cuando instales una tarjeta de red Intel , desactives la tarjeta integrada del servidor y descatives el C1.
El loader 1.02b te funcionará perfectamente sin tener que instalar una tarjeta de red intel, la versión maxima de dsm será 6.1.7
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 6.2.1-23824 update 6
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP Microserver Gen 8
- Additional comments: restart + shutdown OK / Extra Intel NIC
-
11 minutes ago, Hackerjac said:
with 8GB DDR3 laying around and wanted to play with it, so hooked a couple of small SSD to is, booted it with DS3617xs 6.1 Jun's Mod V1.02b (MBR_Genesys), have disabled the RTL8111c lan controller
installed the 3617.pat, every thing seems to be ok, just one small problem, when turning off the sever from the web interface, the server keeps running but it cuts the connection to the lan
Have a feeling its caursed be the ME subsystem on the board, but if i turn off ME subsystem in bios it doesn't load the syno loader
Anyone have an idea about what might be wrong
Check in the the bios if you can change the ACPI configuration. In the case of the N54L microserver changing to ACPI version 1 fix your problem, maybe if you have the option you could fix it.
-
Instalar la NAS directamente utilizando la wifi no es viable tal y como comenta bluesnow ya que se debe elegir que wifi conectar, etc...
Eso si, puedes instalar la NAS utilizando una tarjeta ethernet y una vez instalada utilizar un pendrive wifi compatible con synology y configurarlo para que se conecte a la red, a partir de ese momento la nas puede funcionar sin problemas solo con la wifi.
Un problema que yo me encontré en el pasado, creo que fue con la version dsm 6.0.8 , era que de vez en cuando al cabo de unos dias perdia la conexion con la nas y tenia que conectar y desconectar el usb de wifi para que volviera a responder en la red.
-
22 hours ago, Alex89 said:
Ok, I managed to insert the valid serial number from my old Synology NAS but I still get "{"success":false,"msg":"SN format is wrong."}".
Any idea?
Is it the SN from a modern Synology NAS?
-
15 hours ago, moretty said:
Estoy en la última versión de 6.2.2 con 3615xs loader 1.03b y no hay manera de apagar ni desde la web ni desde el boton.
Alguien me puede ayudar?
graciasThe problem is not the package or version, the problem is in your bios ACPI configuration. Check the following thread.
El problema no esta en el paquete o la version, el problema está en la configuración del ACPI de la bios. El equipo N54L funciona perfectamente.
-
1
-
-
On 6/4/2019 at 8:25 PM, seba said:
There was a package that was downloading few files from internet, but they are not created by me.
If you refer about not being able to select anything outside volume1 in file browser then yes. You need to edit file config.php in webstations folder there look for line
var $browserRestrictFolders = array('/volume1');you can modify it to suite your needs.
Also Virtualbox 6.0.8 is out you can find it on github where I'm posting new versions.
The new version 6.0.8 on DSM 6.2.2-24922 (3615xs) over HP Microserver N54L works perfectly, included the USB assignation to the virtual computers.
Thank you Seba!
Good job!
-
Intenta borrar los discos antes de hacer la instalación. Si no te devuelto error (13) es que el USB es correcto y el PID/VID son correctos.
-
Buenos días,
bootloader 1.03:
Al realizar la instalacion debes de utilizar el fichero *.pat de la siguiente version como máximo DSM 6.2-23739 utilizando la instalación manual, con la configuración nativa del servidor HP Microserver Gen8.
Si por el contrario utilizas la instalación automática o quieres poder disponer de la ultima versión de DSM debes de instalar una tarjeta de red intel en el servidor y desactivar desde la bios la tarjeta integrada.
por ejemplo esta:
- Intel PRO/1000 GT 1000 Mbit/s Interno - Accesorio de Red (Interno, Alámbrico, PCI, 1000 Mbit/s) https://www.amazon.es/dp/B00030DEOQ/ref=cm_sw_r_cp_api_i_jGN0Cb9583EFZ
- 10Gtek® Tarjeta de Red Gigabit PCIE E1G42ET - Intel 82576 Chip, Dual RJ45 Puertos, 1Gbit PCI Express Ethernet LAN Card, 10/100/1000Mbps Nic para Windows Server, Win8, 10, XP, Linux https://www.amazon.es/gp/product/B071R3YS2H/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1
Bootloader 1.02:
Sin ninguna modificación e instalando manualmente la versión 6.1.7 hasta la update 6.
-
14 minutes ago, Hemin said:
Hi,
I accidentally reset my HP microserver Bios and now Juns loader 1.03b boots and get stuck on "find.synology.com" message, seems that don't get an IP address. Could someone screenshot all relevant screen on NL bios?
Thanks
and disable the C1 option in bios.
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 6.2.1-23824 update 6
- Loader version and model: JUN'S LOADER v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - HP G7 N54L
- Additional comments: restart + shutdown OK / Extra Intel NIC, ACPI Bios configured to Version 1.0.
-
On 5/18/2019 at 7:26 PM, pacemaker72 said:
Thanks Seba. Its working on 6.2.2 24922 on 3615xs...(i also tested on 3617xs, it installed but link throwing 403 error as if DSM is blocking it)
tested both DSMs in ESXI inside vmware workstation on windows 7 PC(..crazy)...upgraded from 6.2.1 23824
Hope it helps someone.
..patiently waiting for seba's Virtualbox 6 (for nested virtualization so i can install ESXI on virtual box itself:) )
I confirm that this version works perfectly in the new DSM version 6.2.2-24922
-
On 5/21/2019 at 3:07 PM, gauchim said:
Hola siulman. Gracias! XD
Sí, tengo el DSM 6.1 virtualizado sobre un ESXi 6.5, corriendo en un Microserver Gen8. A ver si alguien que esté en la misma situación puede echarme un cable...
¿Sabéis si puedo "convertir" mi DS3617xs en un DS3615xs o en un DS918? No sé si es una tontería, pero si realmente tuviese un DS361Xxs y me comprara un DS918 ¿podría cambiar los discos de chasis y continuar trabajando con la configuración original? Es decir, sin reinstalar de cero...
Si los discos que utilizas en tu dsm sobre ESXi6.5 son virtualdisk, no puedes traspasar los discos, ya que el sistema de ficheros de los discos son de Vsphere.
Si los discos de la DSM se los has traspasado nativamente a la maquina virtual, entonces si que puede colocarlos directamente en la nueva DSM, ésta los reconocerá y realizará una migracion.
-
On 3/24/2019 at 9:20 PM, seriousm4x said:
and also dmesg:
root@nas:~# dmesg | grep -i atlantic [ 117.128184] atlantic: module verification failed: signature and/or required key missing - tainting kernel [ 117.147160] IP: [<ffffffffa0358f4c>] aq_pci_func_init+0xac/0x170 [atlantic] [ 117.162922] Modules linked in: atlantic(OE+) r8168(O) igb(O) i2c_algo_bit e1000e(O) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd xhci_pci xhci_hcd usbcore usb_common [last unloaded: apollolake_synobios] [ 117.242010] RIP: 0010:[<ffffffffa0358f4c>] [<ffffffffa0358f4c>] aq_pci_func_init+0xac/0x170 [atlantic] [ 117.351490] [<ffffffffa035903c>] aq_pci_probe+0x2c/0x2c0 [atlantic] [ 117.422475] [<ffffffffa036901e>] aq_pci_ops_init+0x1e/0x20 [atlantic] [ 117.495859] RIP [<ffffffffa0358f4c>] aq_pci_func_init+0xac/0x170 [atlantic] [ 119.073050] Modules linked in: atlantic(OE+) r8168(O) igb(O) i2c_algo_bit e1000e(O) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd xhci_pci xhci_hcd usbcore usb_common [last unloaded: apollolake_synobios] [ 119.271144] [<ffffffffa0358f4c>] ? aq_pci_func_init+0xac/0x170 [atlantic] [ 119.278827] [<ffffffffa0358f41>] ? aq_pci_func_init+0xa1/0x170 [atlantic] [ 119.286509] [<ffffffffa035903c>] aq_pci_probe+0x2c/0x2c0 [atlantic] [ 119.357447] [<ffffffffa036901e>] aq_pci_ops_init+0x1e/0x20 [atlantic]
Theoretically the nic is officially supported by Synology
like it's an oficial DS918 you can open a ticket with Synology directly to check why the NAS is not recognizen the NIC.
DSM 6.2-23739 en HP Gen8 con cpu G1610T
in SPANISH
Posted
Buenas noches,
Si en principio es correcto, con una tarjeta de red compatible puedes disfrutar de la ultima version de DSM 6.2.2.
Lo único que tendrás que pelearte con la bios segun que version tengas instalada con la opcion de ACPI para que el servidor se apague por completo. En mi caso tuve que forzar ACPI v.1 para que el servidor se apagara por completo.