Transition Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


PerkyUnicorn last won the day on February 29 2020

PerkyUnicorn had the most liked content!

Community Reputation

3 Neutral

About PerkyUnicorn

  • Rank

Recent Profile Visitors

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

  1. Several apps such as VMM and hyper backup ended updates on 6.1.7 However 6.1.7 seem to be more stable with a few NICs than 6.2.2
  2. I think whether can discover on syno assistant or not depends on the NIC more than the CPU or the loader version There were people succeeded on AMD builds before on both 3617 and 918 loaders Try using 918+ 6.2.1 pat with 1.04b loader first, that's supposed to work easily AFAIK there was a guy succeeded with 1.04b 918+ loader on a Ryzen machine, RTL8111 NIC I guess your board has the same NIC too as most consumer boards use RTL8111 Worth trying If not, try to use IG-88's driver mod
  3. I don't see any difference between 1019+ and 918+ apart from having one more drive bay and more ram on the stock machine... To be honest, I'm very familiar with what Chinese would do... (No offense) When they say it's based on Jun's mod, this loader is more or less a renamed Jun's 918+ 1.04b with driver mod probably from IG-88... btw the "2 in 1" image might worth attention as it saves you a USB drive for the loader, the downside is, no matter what drive you flash the image on, you'll only have 9GB of usable space on that drive P.S. I can read Chinese so I understand them w
  4. Thanks for the info I don't use any of the RAID solutions though, just paranoia If in any case I need parity I'll just replicate the whole shared folder in two different basic volumes... I know that's a dumb way to do it but it just feels more like eggs in different baskets to me
  5. I think the price difference between the R Pi 4 and some old celeron boards doesn't worth the trouble of making an ARM loader for dsm unless you want the extreme small size... They're right about using other Linux distros, the NAS stuff can be done with OMV easily, and the syno-exclusive apps you want, ARM won't have enough juice for those
  6. If there's no faults in the loader drive and the data drives, I think a hardware swap won't affect your stuff A migration shouldn't be a pain in the ass, just remember to mark your drive positions
  7. What CPU are you using? Currently only Intel CPUs with VT-x enabled can work with the VMM in xpenology
  8. It has a limit per card as well if I rmb correctly, max 4/6 per card
  9. 1) Not sure about 9th gen, coz I've never thought of using anything higher than my pentium G5400 at this moment, I'd rather save electricity lol A NAS is supposed to be idle most of the time... Too much CPU power is useless in my use case however, the CPU itself should work, just the internal graphics card might not give you flawless hardware transcoding without driver mods 2) Not sure, not even sure if the card is compatible with non-syno boards maybe you should look up the official synology list:
  10. Basically any Intel system newer than Haswell plus an Intel NIC would give u a safe result, although I would really really wanna try Ryzen, I need to use VMM in the NAS and AMD systems wouldn't work with Synology's VMM, what a pity I personally use Pentium G5400 on an OEM B365 itx board with dual Intel i211 NIC, 6 onboard SATA, 1x m.2 nvme slot However, as I read before the nvme support on xpenology may be tricky, and one nvme slot could only give me read cache instead of read/write cache in my DS918+ system, plus I wouldn't want to SSH mount the nvme drive as it doesn't give me a sa
  11. Your Motherboard has a Realtek 8111E NIC which should work with 1.04b 918+ loader, however 1.04b loader seems to only work with Haswell or above. It still worth trying coz I had J1900 running the 918+ 1.04b loader which J1900 was also pre-haswell Good luck fine tuning here and there P.S. If, by any chance you have a spare Intel NIC on your hand, it should gain you better success rate with the 3615/3617 loaders as they natively support the intel e1000e cards up to DSM 6.2.2
  12. I think the problem you're having might be due to the driver of your internal Realtek 8111GR NIC, coz in synology's driver package the realtek NIC driver is their self-signed R8168 which only works with: RTL8111B / RTL8168B / RTL8111 / RTL8168 / RTL8111C / RTL8111CP / RTL8111D(L) / RTL8168C / RTL8111DP / RTL8111E / RTL8168E / RTL8111F / RTL8411 / RTL8111G / RTL8111GUS / RTL8411B(N) / RTL8118AS Your NIC needs a proper R8169 to function properly. The above are only my wild guess coz I had problems with realtek NICs before and DSM 6.2.x is really picky about NICs. If fi
  13. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 update 6 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO (Couldn't boot with IG-88's extra.lzma, maybe a wrong swap or something. Just reverted to original Jun's loader and worked fine) - Installation type: BAREMETAL - Some Chinese B365 mITX IPFS board + Intel G5400 / NIC: 2x Intel I211AT (igb) (seen people ripped apart a real DS918+ and it was 2x i211AT too) - Additional comments: Only pressed the DSM manual upgrade button in the UI and just ditched
  14. - Outcome of the update: SUCCESSFUL - DSM version prior update: FRESH INSTALL - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Some Chinese board named "Interstellar Snail" (J1900 SoC) / NIC: 2x Intel 82583-V (e1000e) - Additional comments: Hardware transcode only works up till H.264, H.265 not working. VMM works fine. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 UPDATE 6 (Read below) - Loader version and model: JUN'S LOADER v1.04b - DS918+