• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About jarugut

  • Rank
  1. Sorry mandolin but my kernel version is the following: Linux NAS 3.10.102 #15217 SMP Fri Nov 10 20:08:59 CST 2017 x86_64 GNU/Linux synology_bromolow_3615xs Maybe it's possible to change the REQUIRED_KERNEL_VERSION="3.10.102" to your kernel, but it's your responsability, I don't know what can happens.
  2. Hello, I've modified the virtualbox 5.0.40 package following the instructions from Ygor. I have running the phpvirtual box on my DSM 6.1.4. I attach the spk if can help to others. VirtualBox_x64_5.0.40-115130-1_6.1.4.spk
  3. Virtual Machine Manager can not start VM's

    For remove the package you need to access via ssh to the NAS the command I used to break the cluster so it can be removed is in this folder; /volume1/@appstore/Virtualization/bin (In this case is the volume where it's installed the VMM) execute: ./etcdctl member list copy the ID execute: ./etcdctl member remove ID
  4. DSM 6.1.3-15152 Update 8

    HP N54L with LSI 9260-CV upgraded from 6.0.2 U11 to 6.1.3-15152 U8 without any issue. All OK included the generic USB ups that not works with the 6.0.2 version.
  5. DSM 6.1.3-15152 Update 8

    HP N54L DSM 6.1.3-15152 Update 8 successful. UPS works fine. Virtual VMware DSM 6.1.3-15152 Update 8 successful
  6. HP N54L - DSM 6.1 onwards

    The UPS works fine with version 6.1.1 series..... I've updated to 6.1.3-15152 Update 6 without problems.
  7. DSM 6.x.x Loader

    N54L DS3615xs updated to 6.1.3 -15152 Update 6 OK. UPS ok.
  8. Xpenology + Esxi add drives

    Are you created some snapshot? the Xpenology*-000002.vmdk means that exist some snapshot, this means that the ESX needs space to save the all data changes from the snapshot. If the 4 virtual hard disk are a passthough the datastastore where is saved the virtual Nas maybe not have enough space to save the data. In my opinion the first action is remove the snapshot or consolidate.
  9. DSM 6.1.3-15152 Update 6

    DS3615xs Jun's Mod v1.02b Update 6 on Proxmox version OK Update 6 on ESXi 6.5 version OK
  10. DSM 6.x.x Loader

    You need to configure your BIOS with the both external usb connected to the pc. In the boot priority of the USB you need to be sure that the USB boot is the first device. As you describe it seems like some external usb have more priority than your USB boot and that is the possible reason because not boot your NAS.
  11. DSM 6.x.x Loader

    Yes, for the moment with a real sn.
  12. I can confirm that if you have a real sn the codec transcodification works fine!
  13. DSM 6.x.x Loader

    The boot loader for the 6.02 is 1.01 and works perfectly selecting the AMD option. For the 6.1 or 6.1.1 the correct boot loader is 1.02a
  14. DSM 6.x.x Loader

    Only Jun can answer that. He is the developper of the loader. Why don't you disable intel boot in BIOS? There is no need for intel boot to be enabled in principal. Sorry Polanskiman, I'm not understand you correctly! The Microserver have an AMD processor, and I've tried the bzimage with no success. The Microserver bios I think that not have anything about intel. Maybe are you talking about some configuration in the grub.cfg file?
  15. DSM 6.x.x Loader

    First of all thank you Jun and Polanskiman!!! You are doing a great job! My configuration is a HP Microserver G7 N54L (AMD), 8GB with DSM 6.1.1-15101-4 (Boot 1.02) I would like to contribute to the other colleagues with my experience. 1. Lost configuration. I had a bad experience with a shutdown, when the NAS turned on with 6.1.1 15101 the system inform me that I lost all configuration. After make a lot of test, I remembered that I have an old disk from my NAS with 6.0.2 version. I’ve cloned the partition /dev/sdx1 (X is the disk with the old system version) over the /dev/sda1, I’ve used the dd command (example: dd if=/dev/sdx1 of=/dev/sda1 bs=1M). After that I booted with the 1.02 and the wizard detect a previous version configurations. From that moment I have a backup of the /dev/sda1 partition in case of disaster. 2. Now my little issue: My NAS is working fine with no problems but I’m running over AMD processor with the default option of Intel boot. I’ve tried to use the bzimage in the USB boot stick with not success. The USB stick boot but the NAS not boot. I’ve used the OSFmount to mount add the bzimage. Jun, Polanskiman do you have some news about the AMD option? For the moment the only problem in my case is that I lost 4,6 GB of RAM memory because is reserved, I only able to use 3,4 GB. This lost memory is because I’m using the Intel boot. Thank you in advance