• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bluepr0

  • Rank
  1. Hello guys, thank you for your reply. Sorry that I didn't explain it well, what I meant about tutorial is for adding the extra files to the loaders/PAT files. I'm already running a Xpenology using 918+ so I'm familiar with the installation process. I will try to follow @mosaati steps to get the extra files in! Thanks
  2. Hello guys, I've been trying to find what the hell is going on and I can't get it working. I have a Dell optiplex 9020 that was perfectly working as a 918+ on 6.2.2 24922-4. Early today I've installed 6.2.2-24922-6. Apparently it went fine, everything was working correctly after the restart except I can't access the Synology DSM website. However other services like Samba or my VMs were working, so this lead me to think there was some kind of problem on the Synology server. I procceded to restart the server and after that it never came back. Not even the IPs are responding to ping. I've from this tried almost EVERYTHING I COULD THINK OF. I've re-write my USB stick with the bootloader 1.04b and then forcing to install 6.2.2 24922. The installation will work, meaning I can find my Synology on or by pinging the IPs, but after the restart it won't work again and not even the iPS will give ping. I've also tried with bootloader 1.03b and 3617xs, installation goes fine, I upload the PAT file 6.2.2 24922 as always and on restart... ONCE AGAIN THE SAME THING!. This is driving me incredible crazy, I don't really understand by it was working perfectly before, and now I'm trying to install the same version and it's not working. Anyone got any ideas on what's going on? Thanks a lot!
  3. Hello, where I can find a step by step tutorial on how to use these driver extensions? I'm reading the initial post but I'm totally lost on how to use them. Thanks a lot!
  4. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-4 - Loader version and model: Jun's Loader v1.04b DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Dell Optiplex 9020 - Additional comments: Reboot required
  5. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Dell Optiplex 9020 / Intel i350-t4 - Additional comments: REBOOT REQUIRED
  6. I was able to recover my HDDs by downgrading using this guide I installed back 6.2.1-23824 which seems to work just fine. However DSM was showing an update, 6.2.1-24XXX-4 (sorry can't remember exact numbers) which I accepted to install because it was still 6.2.1 and IT BRICKED IT AGAIN!. What's going on here?
  7. Hello @IG-88 Thanks so much for your work. I had a 6.1 DSM working but wanted to try with DSM 6.2.2. My Xpenology is a 918+ and my hardware is a Dell Optiplex 9020 that comes with an Intel i217LM, which sadly seems to not work with the 1.04b loader. I've bricked my NAS now I've tried to follow your insutrctions and copy the extra.lzma and extra2.lzma to the USB, but when I connect it to Windows I just can't read the USB stick, it will just ask for format. What I was able to do is to modify the synoboot image and copy those files there, then writing again the image to the USB stick. When booting the PC I get the migrate screen, click next, select the latest PAT file for my NAS ( it installs, restarts and I'm unable to connect again (no ping on IP either). I'm not entirely sure what else to do. I know that if I format my HDDs I can install it again, but I will lose all my data. I'm also not sure how to downgrade, because even if I burn the original 1.04b loader on the USB and at boot select the Reinstall option, when the DSM installation ask for the PAT file it won't accept anything below 6.2.2 now (see image below) Any help will be greatly appreciated, really looking forward to access my data again :D. Thanks!
  8. Thanks so much man, that's what I was doing actually! I read that you had to put the drives in the same position (so Disk 1 in your bare-metal has to be Disk 1 on your VM) but the VM already got 2 (sata0 and sata1) for booting up the system, so not sure if it will work... anyway I'm scrubbing my RAID because I erased the 2 SSDs I had for cache on Synology to install Proxmox and now my RAID is crashed LOL
  9. Nevermind, I took a look at some articles and it seems you need to use the --storage option
  10. Just tried this but I'm getting an error when restoring it (and then when I power on the VM there's no boot device and it restarts in a loop) restore vma archive: vma extract -v -r /var/tmp/vzdumptmp40639.fifo /var/lib/vz/dump/vzdump-qemu-xpenology-3617xs-6.1_15284.clean.vma /var/tmp/vzdumptmp40639 CFG: size: 471 name: qemu-server.conf DEV: dev_id=1 size: 54525952 devname: drive-sata0 DEV: dev_id=2 size: 6442450944 devname: drive-sata1 CTIME: Sat Jan 5 08:52:16 2019 command 'set -o pipefail && vma extract -v -r /var/tmp/vzdumptmp40639.fifo /var/lib/vz/dump/vzdump-qemu-xpenology-3617xs-6.1_15284.clean.vma /var/tmp/vzdumptmp40639' failed: storage 'LVM-SSD' does not exists root@pve:/var/lib/vz/dump#
  11. Just a quick question from a noob trying to learn Proxmox to virtualize DSM there (currently on bare-metal). I would like to passthrough all my disks so I can restore all my data and configuration... would this be possible by adding the physical disks to the VM? I'm currently on 6.1.7 with 3617xs on bare-metal as I said
  12. bluepr0

    DSM 6.2 Loader

    Hello! I'm currently running Jun's loader 1.02b with 3617xs+ and DSM 6.1. Everything is great and super stable, however my Intel Xeon E5 2698 v4 is only recognised as a 16 core CPU (instead as a 20 core/40 threads). I was wondering if it will be worth trying bootloader 1.04 and DSM 6.2.1 to try to fix this problem. Aside from that I'm not sure there's a huge difference between 6.1 to 6.2.1 (tried to search on internet but nothing fancy so far)
  13. Hello guys, I have Xpenology 6.1 installed on my server and the only problem I'm finding is that I'm not getting all my precious cores usable. My cpu is an Intel Xeon E5-2698 v4 (20 cores, 40 threads) This is what I get doing a dmidecode -t processor # dmidecode 2.12 SMBIOS 3.0 present. # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Handle 0x0069, DMI type 4, 42 bytes Processor Information Socket Designation: CPU1 Type: Central Processor Family: Xeon Manufacturer: Intel ID: F0 06 04 00 FF FB EB BF Signature: Type 0, Family 6, Model 79, Stepping 0 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Genuine Intel(R) CPU 0000 @ 2.00GHz Voltage: 1.8 V External Clock: 100 MHz Max Speed: 4000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: <OUT OF SPEC> L1 Cache Handle: 0x0066 L2 Cache Handle: 0x0067 L3 Cache Handle: 0x0068 Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 20 Core Enabled: 20 Thread Count: 40 Characteristics: 64-bit capable Multi-Core Hardware Thread Execute Protection Enhanced Virtualization Power/Performance Control However doing a cat /proc/cpuinfo I get only 16 cores and nothing about 32 threads. processor : 15 vendor_id : GenuineIntel cpu family : 6 model : 79 model name : Genuine Intel(R) CPU 0000 @ 2.00GHz stepping : 0 microcode : 0x14 cpu MHz : 2001.000 cache size : 51200 KB physical id : 0 siblings : 16 core id : 24 cpu cores : 16 apicid : 48 initial apicid : 48 fpu : yes fpu_exception : yes cpuid level : 20 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap bogomips : 4000.02 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: If I do a htop to see core usage you can also see that there's only 16 cores available. Is there a way to fix this and use all the available cores?
  14. Hello guys, I was thinking about building a new NAS for my home and I was wondering if any of you is using successfully any 1151 mother board (latest socket from Intel). I was thinking for example in the ASRock Z170M-Itx. How is the new Intel Z170M chipset working? Thanks for any info!