bluepr0

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bluepr0

  • Rank
    Newbie
  1. 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
  2. Nevermind, I took a look at some articles and it seems you need to use the --storage option
  3. 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#
  4. 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
  5. 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)
  6. 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?
  7. 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!
  8. I've got some news! I tried booting from USB with Xpenoboot and it worked great. I installed the .path file without problems and used my SSD as a disk to create a volume inside Xpenology. It seemed that all was recognised well, with the exception of the fan which I guess I can control with the BIOS!. I haven't tried connecting my RAID1 disks as I was afraid to screw them
  9. Hello! Thanks for this tutorial! I was wondering if I could install Xpenology on QNAP NAS too. I recently got a 451+. I've got a few questions that if you feel you have a bit of time would be great to know. 1. I've been searching through this forums and also on QNAP's one to see how do I reinstall QNAP OS in case I don't want to keep Xpenology. Correct me if I'm wrong, but it seems the NAS comes with a memory built in where is the system and installation wizard that after will be installed into your disks, so I will always have that memory to restore QNAP system if I want to and not overwrite it! Another doubt I had, which it seems answered on this thread is regarding data on the drives. I've got 2x4TB WD RED in RAID1 where is the system installed, but I've also got 2 single volumes (1x 2TB disk and 1x3TB disk). Could I use these somehow to backup the data there and then regenerate the RAID1 on Xpenology and copy it back (mostly backups, movies, shows, etc). Thanks!
  10. BTW, anyone knows if the software RAID that creates QNAP NAS and Xpenology are compatible? or I will have to recreate the RAID 1 I currently have on my QNAP NAS? I'm planning on testing it today, if it works install the Xpenology system on an SSD disk I'm currently using as cache for the QNAP and then connect the the RAID1 disks I have and see if they are recognised without having to create it again. What do you think? sounds like a good plan?
  11. Hello guys... First of all, I know... it doesn't make sense to buy an expensive QNAP box to put another OS inside of it. It's my fault for not knowing about Xpenology. I've installed it on a Virtual Machine inside my QNAP NAS and it's so much snappy and better, I absolutely love it. Also it looks nicer than the QTS (OS from QNAP). I was wondering one thing... I'm not sure if all my hardware is compatible but I will find out by booting with Diskstation... however what I'm really worries is that I currently have a RAID 1 where all my data, backups, etc are. Is there a way to know if it will work the RAID or I will have to rebuild it?. Thanks!