Jump to content
XPEnology Community

James62370

Rookie
  • Posts

    8
  • Joined

  • Last visited

Everything posted by James62370

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 update-2 - Loader version and model: ARPL-i18n v23.8.1 / DVA1622 & DS920+ - Using custom extra.lzma: NO - Installation type: ProxMox VE 8.0.4 NUC7i5BNH 32GB DDR4 - Additional comments: Manual update via DSM GUI (Downloaded respective .pat then upload to NAS) As some others stated, the update was quick, reboot was not required.
  2. I had a similar issue in the past. The fix for me was setting the machine type in my VM to q35. Good luck.
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 update-1 - Loader version and model: ARPL-i18n v23.7.4 / DVA1622 & DS920+ - Using custom extra.lzma: NO - Installation type: ProxMox VE 8.0.3 NUC7i5BNH 32GB DDR4 - Additional comments: Manual update via DSM GUI (Download corresponding .pat then upload to NAS)
  4. I know this thread is a few years old. However, I'm currently having continuity errors also especially during recording. When you say your changed the board from J3455 to J4105, could you elaborate on how this was done? My setup is on a GB-BXi7-4770R. Appreciate your help.
  5. I was able to setup DS918+, but unsuccessful with DS920+. I get No drives detected in DS920+ - Is there currently an issue with DSM920+? Or has anyone been successful with DS920+
  6. It actually did work... I wasn't able to find the server with the synology assistant or the find.synology.com url. However, my home assistant server noticed new dsm servers and I was able to find the ip address that way. I wonder why the url or assistant is unable to locate. Anyway, it seems to work. Thank you! Edit: Figured it out, Windows Defender Firewall was blocking the Synology Assistant app from locating servers.
  7. Thank you for this guide. First time ProxMox user. I'm having the same issue as MrHappy. After trying several times (with different options) I always ended with the vm starting and pending at 'Booting the kernel'. I tried with tinycore-redpill 0.4.6 and also 0.8.0.0 - always stuck at the same place. I've also tried dcop1's suggestion, but I'm new to proxmox and don't really understand all the steps that he listed. Any help would be appreciated. Thank you
×
×
  • Create New...