New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About 5237478232

  • Rank

Recent Profile Visitors

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

  1. I just updated my ASRock 3455-ITX from DSM 6.0 on 1.01 loader (3615xs machine) to DSM 6.2.1 on 1.04 loader (918+ machine) with a blank HDD to test if everything works properly. It looks good, but reboot / shutdown doesn't work. I read from other users that this is a "common" problem (at least some other users reported the same problem), but I didn't find information whether that is a problem of the 1.04 loader or the DSM 6.2.1. Can I use 1.03b loader in combination with DSM 6.2.1 or will I face the same problem again?
  2. I think that won't be a problem for me. It's only needed for Plex, right? I don't use that service anyway. So I can flash 1.04b loader and then upload to DSM 6.2.1 (not 6.2.2, as it doesn't seem to work on my board) if I don't plan to use hardware transcoding, am I right?
  3. I have a ASRock J3455-ITX Board with integrated Intel® Celeron® Prozessor J3455. I'm currently trying to update from my current version (DSM 6.0.2-8451 Update 9 with Jun's Loader V1.01, machine type DS3615xs) to the newest possible version. I can see from your matrix that I need a "Haswell or later" CPU for the recommended combination 1.04b loader and DSM 6.2.1 (not 6.2.2 because you mention that this DSM version fails on AsRock JXXXX). The CPU of my board (Apollo Lake / Goldmont generation) is a 14nm architecture and it was released in 2016 that makes me think that it is indeed "Haswell or later", but I'm not 100% sure, because the atom line is a parallel product line (Haswell is not part of this line). Is this the way to go for me? Flash my USB to Jun 1.04b and then on the DSM interface do a direct manual update to 6.2.1?
  4. I have a similar problem. I'm still running DSM 6.0.2-8451 Update 9 with Jun's Loader V1.01. I have a lot of important data on that machine and I don't want to risk bricking it by doing a false update. My plan right now is: 1.) Backup all data to an external drive (because all my data are in encrypted folders in the Xpenology machine and I fear that I might not be able to access them, if something goes wrong during the update) 2.) Create a working VM (VirtualBox) exactly running DSM 6.0.2-8451 Update 9 and Jun's Loader V1.01 on my USB Stick. 3.) Update my USB-Stick to Jun's new Loader for DSM 6.2. https://xpenology.com/forum/topic/12952-dsm-62-loader/ 4.) Try to start the VM with the new Loader. If that works, get the image for the newest DSM 6.2.2-24922 and update it right away from DSM 6.0.2-8451 Update 9 to DSM 6.2.2-24922. https://xpenology.com/forum/topic/14839-dsm-622-24922 5.) Check if everything is working fine on the VM. If it does, I do the same steps on my real Xpenology machine. Is that the right way to go?