dh22r

i was able to boot my Q1900DC-ITX with the above mods by switching the USB boot from legacy to UEFI. on bootup, the internal NIC light flashes yellow for about a min, then it goes dark and the the green light comes on (ie. after DSM loads the RTL driver).

just curious ... are you booting the loader using USB legacy or UEFI?

i forgot to report back earlier ... changing my USB boot from legacy to UEFI resolved the above NIC issue.

not sure what's with my Q1900DC-ITX. with the custom extra.lzma, i'm able to install/reinstall ok. but on reboot, 3 of 4 times, the built-in NIC isn't recognized (i.e. no green/activity light). but via reinstall, the NIC is always recognized. it's as though some of the settings in the DSM partitions -- i've 5 3TB in my rig -- aren't in sync. it's hit-n-miss whether LAN connection occurs. any ideas? much appreciated. dh22r

just adding my two cents ... maybe it's not relevant for the issues on this thread. i'd to always boot in legacy mode for my NIC to work; boot via UEFI never seems to get an DHCP assigned IP address for my DS918+ build.

have you check with your router's network/admin page (assuming you're using DHCP) to see whether your server is assigned an IP address? also, i boot my servers using the "legacy USB" option instead of "UEFI USB". dh22r

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - DS3617xs - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock J1900DC-ITX - Additional comments: None - Outcome of the installation/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 - Asrock J3455-ITX - Additional comments: None

can anyone tell me the downsides of having a separate mini PC (i.e. intel nuc) to front as the plex server instead of using the DSM? my current setup is an asrock J1900DC-ITX in a fractal design node with 5 HDs (4 using onboard SATA, 1 using a iocreate SATA pci card). my DSM is ds3617xs on 6.2. the DSM is currently my plex server. if i buy a NUC J3455 (or J5005), install windows 10 home, install the latest plex server and add movies/TV media from the DSM, i can expect hw transcoding (enabled for plex pass holders) to work, right? thanks for any help. dh22r

did you try booting in legacy/BIOS instead of UEFI?

my builds are: - asrock J3455-itx - ds3617xs - 1 x WD-red 3TB - asrock j1900d-itx (DC version, no PSU required) with 4-port iocrest sata card - ds3617xs - 5 x WD-red 3TB - zotac zbox (celeron j2597u) - ds3615sx - 1 x firecuda 2TB i couldn't get WOL working, but since all the build have low-powered CPUs, i leave them on all the time. dh22r

i had similar issue with my server build's (asrock J3455-ITX, DS918+) network card not "registering" and getting an IP address assignment from my router. for me, the issue was i was booting via UEFI. once i switched to bios/legacy boot, the server was visible via my router (ie. IP address assigned) and working as expected. dh22r

in my grub.cfg, i'd set the MAC address the same as the NIC's MAC address. should i be doing something different? thanks. dh22r

i've the same iocrest 4-port sata card in my DS3617xs build (asrock j1900-itx). at this point, i'm using just one of the ports in my SHR setup, but everything works. dh22r

nope ... on the migration/update page to DS918+, i chose to keep my existing data & configs when asked.

I think I'd the same issues initially. Screen showing loader as booted, but not able to connect via the web GUI or visible via synology assistant. Turned out, for me, I had to boot with legacy bios (ie. not UEFI). dh22r