• Content count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About marigo

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. marigo

    DSM6.2 installation on Asrock J1900ITX

    Great news! Didn't know about this power button package; thank you. My J1900 is running just fine for about five days. Now I see the difference between a virtual and a barebone installation. It is running much smoother now. With surveillance station package and 5 IP camera's it's using between 4 - 8 % of CPU power. I am monitoring it with Grafana, telegraf and Influxdb.
  2. marigo

    DSM6.2 installation on Asrock J1900ITX

    The v1.04 was made to override the problems with the PCI devices. I thought I had red that somewhere here. Yes, I am running xpe on a J1900ITX and it's working. (so far so good) I was used to install xpe in a KVM on Proxmox, but this is much faster than I thought it would be. I guess you have something to do.
  3. marigo

    DSM6.2 installation on Asrock J1900ITX

    Thanks for your reply. I have figured it out. My installed SSD had several (linux) partitions. When a new DSM has to be installed DSM don't likes a harddrive with partitions. So I downloaded a live linux distribution, made a bootable USB en deleted all the "old" partitions so I had a clean disk. The boot process with V1.04b loader works now fine and latest DSM is installed.
  4. Hi all, I have a spare J1900 PC to try a baremetal installation of Xpenology. I have followed the tutorial and I can find the diskstation in my LAN. I use the DS918+ loader 1.04b. When I want to install DSM I get a warning that "disk 1" will be formated. When I click "ok" the installation will begin but end soon with the message: "unable to format the disk, error 35". I have one Sata SSD on the first SATA3 port and is recognized in the BIOS. I updated the grub.cfg with the VID/PID of the USB device and changed the MAC and SN of the installation. Am I missing something here?
  5. I have never used quickconnect to get to my xpenology. I use a VPN to connect to home when on the road. Personally I prefer to block all internet activity of my xpenology. Only when I need to upgrade some packages, Internet connectivity is allowed. (or install manually)
  6. Sure you can change this. I have applied my serial/mac from my DS211j. All Synology packages are working on xpenology.
  7. You can also try the following: Disconnect the xpenology from the internet Apply the key You get a warning that there is something wrong. Just click "ok" Connect the xpenology again The key should have been applied. Note: This does not work on latest surveillance station package (8.2.1-5765)
  8. I have downgraded the surveillance station package from 8.2.1 to 7.2.1 and this seems to be working for now.
  9. Hi all, I make use of the Surveillance station package on xpenology. After some random time the CPU usage will double the utilization. It goes from 20% to 40%. The only thing I can do about it, is to restart the xpenology and it goes back to normal. xpenology is running on KVM in Proxmox 5.2.8. Anyone else with this issue and knows a solution?
  10. marigo

    DSM 6.2.1-23824 - WARNING

    - Outcome of the update: SUCCESSFUL - DSM version prior update: Fresh install on Proxmox 5.2.8 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VM - KVM - Additional comments: Used Intel E1000 NIC
  11. marigo

    DSM 6.2 Loader

    Check out some tutorials in the installation section.
  12. Hey, great that you have found the issue. I use the "default" SeaBIOS so that's why I don't had any problem. :) In the meantime you can use 1.03b with a sata drive as the boot disk.
  13. I have no experience with booting from USB inside Proxmox. I think that it should not matter what bootdevice you use. You can try the 50MB Sata loader and see if that will help. With my setup I can access the terminal when booting so somewhere something is different.
  14. root@proxmox2:/etc/pve/qemu-server# cat 103.conf boot: c bootdisk: sata0 cores: 4 memory: 512 name: DSM-test net0: e1000=32:32:66:61:37:30,bridge=vmbr0,tag=101 numa: 0 ostype: l26 sata0: local:103/vm-103-disk-2.raw,size=50M sata1: local:103/vm-103-disk-1.qcow2,size=8G serial0: socket smbios1: uuid=dec697d4-36e6-43de-a2e0-896db9f2dfe1 sockets: 1
  15. Yes, I can confirm. Just tried it seconds ago. No problem. The "qm terminal 101" also gave me the same results. I know I had to switch from "IDE" harddisks to "SATA" with 1.03b loader. So for the migration I had to shutdown the DSM6.1 VM, detach the IDE HD en edit this to SATA. Then add it again and set new bootdisk. Hope this helps you.