marigo

Members
  • Content Count

    35
  • Joined

  • Last visited

Community Reputation

4 Neutral

1 Follower

About marigo

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. marigo

    DSM 6.2.1-23824 Update 4

    Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 update 2 - Loader version and model: Jun 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock J1900-ITX - Additional comments: NONE
  2. marigo

    DSM 6.2.1-23824 Update 2

    - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 1 - Loader version and model: JUN'S LOADER v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock J1900ITX - Additional comments: none
  3. 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.
  4. 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.
  5. 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.
  6. 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?
  7. 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)
  8. Sure you can change this. I have applied my serial/mac from my DS211j. All Synology packages are working on xpenology.
  9. 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)
  10. I have downgraded the surveillance station package from 8.2.1 to 7.2.1 and this seems to be working for now.
  11. 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?
  12. 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
  13. marigo

    DSM 6.2 Loader

    Check out some tutorials in the installation section.
  14. 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.
  15. 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.