jarugut
-
Posts
182 -
Joined
-
Last visited
-
Days Won
6
Everything posted by jarugut
-
Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP Proliant MicroServer gen8) - Additional comments: Requires reboot, Phpvirtualbox working again with the following package VirtualBox_x64_5.0.40-115130-1_6.1.5.spk and Power Button package reinstalled and working.
-
Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP microserver gen 7 N54L, Esx 6.5) - Additional comments: Requires reboot, Phpvirtualbox working again with the following package.
-
I've updated the spk file to works on 6.1.5 version. Modified Kernel_build version and specific name folder of package.tgz file. It's working on my DSM 6.1.5-15254 VirtualBox_x64_5.0.40-115130-1_6.1.5.spk
-
The problem is that this package version is only for kernel 3.10. It not have the compiled libraries for other kernels.
-
That is the problem that some people we have with VirtualBox_x64_5.1.30-118389-1 version.
-
I used the 7zip software to open the spk file and I used the notepad++ to modify directly the file inside the 7zip. In the options of the 7zip on the Editor tab you can select what software do you want to use to modify the files.
-
- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 3 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HP MicroServer N54L) - Additional comments: Requires reboot
-
- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 - Update 2 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (HPE Microserver Gen8) - Additional comments: Requires reboot
-
- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 update 2 - Loader version: Jun's v1.02b - ds 3615xs - Installation type: HP N54L - Additional comments: Requires reboot - Virtualbox 5.0.40 : package : OK
-
I've tried to upgrade my previous 5.0.40 version without success. I've gotten the same problem "Could not connect to host (http://127.0.0.1:18083/)"
-
Use the following package for DSM 6.1.4 VirtualBox_x64_5.0.40-115130-1_6.1.4.spk
-
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.
-
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
-
Virtual Machine Manager can not start VM's
jarugut replied to Wurstpilot's topic in Synology Packages
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 -
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.
-
HP N54L DSM 6.1.3-15152 Update 8 successful. UPS works fine. Virtual VMware DSM 6.1.3-15152 Update 8 successful
-
The UPS works fine with version 6.1.1 series..... I've updated to 6.1.3-15152 Update 6 without problems.
-
N54L DS3615xs updated to 6.1.3 -15152 Update 6 OK. UPS ok.
-
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.
-
DS3615xs Jun's Mod v1.02b Update 6 on Proxmox version OK Update 6 on ESXi 6.5 version OK
-
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.
-
Yes, for the moment with a real sn.
-
Is DSM checking SN for video conversion?
jarugut replied to princerock's topic in Packages & DSM Features
I can confirm that if you have a real sn the codec transcodification works fine! -
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
-
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?
