Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 06/14/2017 in all areas

  1. Сделал видео-инструкцию по установке DSM 6.1.1 Update 4 на HP MicroServer Gen8 с нуля для новичков: Инструкция Всё подробно, по шагам. Админы закрепите в шапке.
    1 point
  2. Looks like that is the case even if you don't plan to use quick connect. NeoID has done some research on this. I'm just not sure what a valid SN is, and if the tool checks the MAC too. The error message only complains about the SN, but who knows what it really checks? I'm wondering if this is a signal that Synology has started to add more checks to their code so that they can limit what non-authorized system (like Xpenology) can do. I didn't have this problem in 5.2.
    1 point
  3. Ya no recuerdo en qué hilo estaba... Pero viene a decir. En inglés. Que edites el fichero de configuración de la máquina y donde pone que no soporta shr le pongas un yes.. Enviado desde mi Aquaris X5 Plus mediante Tapatalk
    1 point
  4. Hi. Before any upgrade please take a full backup of your important data. There is no "Do it so and it will work!" guide. I can describe how I updated my bare-metal systems from 6.0.X to 6.1.1 (including a Gen8 MS) - Backup your data - Disable any SSD cache - Shut down your server - Unplug your boot stick or micro-sd from the server and open it's grub.cfg - Write down the important modifications and entries like serial no., macs, sataportmap, etc. - You can either write the new synoboot.img to your old boot device or use a new one - Download the 1.02a2 image for DS3615XS from here: https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!Fwki3A4B - Use a tool like OSFMount to mount the synoboot.img (15MB partition) and uncheck the "read-only" option, open it's the grub.cfg - Check the VID & PID of your new device or (if you intend to use your old boot medium) use the old values - Fill in the entries mentioned above (vid, pid, serial, etc.) - Save the image and unmount it - Write the image to your desired boot medium with Win32Diskimager, plug it into to your server and let it boot - Log in to DSM and go to the control panel -> Updates & Recovery - Download the official PAT file from Synology: https://global.download.synology.com/download/DSM/release/6.1.1/15101/DSM_DS3615xs_15101.pat - Select "Manual update" and upload the previously downloaded PAT - Confirm the update and let the server reboot (this can take a little bit more time as usual) - If anything went smooth you should be able to re-login into DSM - Apply actual Update 4 and after another reboot everything should be finished
    1 point
  5. Jun's loader contains 4 files. I did the following steps: 1) modified ds3615.vmx ( virtualHW.version = "11" ) 2) uploaded all 4 files to a new directory on the ESXi server 3) added ds3615.vmx to the list of Virtual Machines. 4) in the VM settings: deleted the network adapter and added a new one 5) in the VM settings: created and added 8GB virtual drive 6) started the vm an connected to it in the browser 7) installed DSM 6.1.1 on DS3615xs 8) upgraded within DSM to 6.1.1-15101 Update 4 9) configured DS3615xs to my likes and shut it down 10) in the VM settings: created and added 4TB virtual drive 11) started VM 12) on DSM: added new Raid Group (basic, btrfs) 13) on DSM: added a new volume 14) installed Hyper Backup and Hyper Backup Vault from the Package Center 15) tested my backup concept after a few hours all data were restored ...
    1 point
  6. Есть такая проблема при переезде на новый движок. Поисковики быстро новый форум обсосут. Проблем скоро не будет. Проблему со ссылками на ветки внутри сообщений буду решать программно. Пытаюсь разобраться и построить таблицу соответствия.
    1 point
×
×
  • Create New...