New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About agaufres

  • Rank

Recent Profile Visitors

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

  1. Hello, I partially solved it. The solution was to immediately create a volume from the main drive. I figured out that if you create a volume into DSM directly after setup, I was able to create a second volume with another disk. Let me know if it solve your problem. I'm not 100% sure that this is the fix. Cheers
  2. I forgot something. Before booting up the HP server, I've added a second CPU and more ram memory on the HP ML. But I didn't make any change on the Virtual machine in ESXI. Could that be the issue ?
  3. Hello everyone, I'm running NUTS with my virtual Synology running on vMWare ESXI 6.7 A few months ago, I started to work with the loader on a HP ML350 G5 server. It was brilliant. I've added multiple volumes, one from the SAS 2.5 RAID bay and some other volumes from regular SATA HDD connected directly on the mainboard. It was working fine. I was able to make some backups on the basic volumes. I started the server a few weeks later and I was able to backup again. But yesterday, after a few months with the server shut down, I needed to do another backup. So I boote