Dfds

Moderators
  • Content Count

    601
  • Joined

  • Last visited

  • Days Won

    16

Dfds last won the day on January 24

Dfds had the most liked content!

Community Reputation

87 Excellent

About Dfds

  • Rank
    Guru

Recent Profile Visitors

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

  1. The search results you found most probably relate to a real Synology unit, you need to use the memory that is compatible with your motherboard.
  2. You should be able to just plug the existing drives into the new Synology unit, it will most likely say your are migrating from another Synology unit & offer to migrate to the new unit. FYI DSM is stored on separate partitions to your data.
  3. @jj-lolorather than asking the same question in other peoples threads you would be better off creating your own thread if you have a problem.
  4. Ok, seems there has been some confusion. Your non working system is emulating a DS918, your old N54 can only run as a DS3615. If you put the disks from the non working system into the N54 you will need to create a new boot stick using jun’s 1.03b loader, there will be a message saying your disks have come from a DS918 & that you can migrate to DS3615. At the moment DSM 6.2.3 is is the latest version you can run ok. All of your existing data should be ok however it always advisable to have backups of anything vital.
  5. @Orphée when you reply to a post there is a toolbar at the top of the window, the icon I’ve circled in red is the code tag button.
  6. @atakacsfor DSM 7 have a look at the redpill tinycore thread in the developer discussion section.
  7. I believe the HP one will work ok.
  8. Dfds

    HP Microserver N36L

    Assuming you power off before swapping the disks it shouldn’t be a problem, however as always make sure you have a backup of any important data.
  9. Dfds

    DSM 6.2 Loader

    @Niels_Jthe gen8 will happily run DSM 6.2.3 with jun’s 1.03b loader or if you want to try DSM 7 you can build a loader using redpill tinycore, see the thread in the developer discussion section.
  10. This is purely cosmetic & merely reflects the CPU used in that model, all cores will be used.
  11. Ultimately the j1900 isn’t the best choice to run vm’s. If you do go for new hardware you may want to consider running everything through esxi or proxmox.
  12. As @chickeysaid assigning assigning all your CPU cores to the vm isn’t a good idea, I’d also think about running the vm from an sad.
  13. @WDCluBplease do not use quickconnect it is not something that we condone on this forum, there are ways of accessing your server without it I.e. DDNS
  14. From memory you need to ssh into the ILO console then type vsp to see the virtual serial port
  15. As it’s a gen8 you can access the serial console via ILO so that you can monitor the boot process.