Dark Zydor

Members
  • Content Count

    35
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Dark Zydor

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: JUN'S LOADER v1.03a - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Additional comments: Did not work with onboard NIC. Following comments on this topic, I bought a intel NIC added it, stopped DSM, disabled the onboard NIC. Update was applied successfully then.
  2. - Outcome of the installation/update: UNSUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: JUN'S LOADER v1.03a - DS918+ - Using custom extra.lzma: NO - Installation type: Baremetal - Additional comments: None
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 UPDATE 1 - Loader version and model: JUN'S LOADER v1.03a2 - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASROCK J3455-ITX - Additional comments: Reboot is very slow, as usual: at least 5 minutes.
  4. Huge thanks to AndreyATGB ! This was indeed the solution of my reboot issue when using hardware tanscoding. Do not plug anything on your graphic ouputs otherwize DSM will crash when using hardware transcoding. If any wire is plugged and system is on, you need to unplug it and then restart before using hardware transcoding.
  5. That is interesting ! I will try to disconnect my display within few hours and confirm that for my own configuration.
  6. Yes, I have a valid serial number. Without a valid one, transcoding do not work neither with nor without hardware acceleration. Thank you for this information.
  7. I would be interested by the result of a videostation hardware transcoding test. I personally get this behaviour with videostation and DSM 6.2 : - without transcoding option, transcoding works fine - with transcoding option, transcoding starts and works maybee 15 seconds. Then, DSM freezes and reboots.
  8. I guess this could be linked to controller driver or BIOS settings, so motherboard specific ? (That was a fresh install too) I used default BIOS settings and I read here & there that there are some tweaks (AHCI, legacy settings...). Some of them could even solve the hardware transcoding problem ? Here again, i will run some tests as soon as I have enough time.
  9. - I tried both i5-2500k and i5-4570 and never got an IP address. So I was not able to go further. Indeed, i5-2500k seemed too old so I did not insist on it. - Indeed, my bet was that using same CPU as 918+, It should work as well as possible. I will run more tests in the following days.
  10. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 UPDATE 1 - Loader version and model: JUN'S LOADER v1.03a2 - DS918p - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455-ITX - Additional comments: Untick hardware transcoding in videostation to avoid freeze of the machine.
  11. I wanted to try DSM 6.2 and the new loader and my i5-2500k/i5-4570 were not supported (although i5-4570 is on the list - maybee a network driver issue). So I bought a ASRock J3455-ITX which seems to be the more promising. Here are my advices to those who would like try it too. 1/ Do not plug your USB stick on USB3 port. I got an error 13 during installation until I changed to USB2 port. 2/ Be patient. When I launch the system, It lasts sometimes 2 minutes or more to get an IP address. You can think it is not working whereas it is only super slow. 3/ Everything works fine including DSM 6.2 Update 1, except hardware transcoding. If you untick the box (see capture below) in videostation, everyting is fine. If you tick it, system gets frozen as soon as you launch a transcoding. Maybee those advices are valid only for this motherboard/CPU.
  12. Vous avez oublié de décocher la case "Lecture seule" au moment du montage de la partition avec OSFmount. Je vous invite à relire le tutoriel suivant où tout est indiqué (point 4) : https://xpenology.com/forum/topic/7980-tuto-installermigrer-dsm-52-à-61x-loader-jun/
  13. Sounds like time bomb issue. It happened to me 2 or 3 times when I was using 1.02b 3617 loader. So I went back to 1.02b 3615 and no problem so far.
  14. Thanks man @jun. Your work is amazing. So as sharing it with this community.
  15. Update OK on my production environment. No problem so far.