dh22r

hello all. i've running a dell T30 server (xeon e3-1225v5) on DSM 7.1 via ARPL (ds3622xs+). i jumped on a memorial day sale on the dell refurbished website. bought a dell precision 5820 tower with xeon w-4125 (8 cores) has anyone running a ARPL build using "xeon w" CPUs? thanks for any help.

i'd similar issues with my ethernet connections with the v1.1 versions. try selecting all modules (in the advance menu section) before building the loader. maybe overkill to include all the modules, but the step did resolve the NIC issues for me.

not sure whether i'm doing something off ... i'm using 1.1-beta2 and everything on my DS920+ build is fine. on boot, it pickups up the DHCP assigned IP 192.168.1.127. but when i boot up with 1.1-beta2a, the assigned IP is 192.168.1.61 (a different IP). in past builds, the server never shows up on synology assistant. when i boot with beta2 stick, the assigned IP appears again. is the there something new, added in beta2a that messes with the IP assignment? just wondering.

has anyone got a USB 3.0 (or USB C) 2.5gbe (or 5gbe) ethernet NIC adapter working in DSM 7? my ITX motherboard has a single PCIe 3.0 x 16 slot that used for my HBA card. i'm on the latest ARPL build 1.1-beta2. i'd tried several but none of them show up under the "Network Interface" section as "LAN xx": https://www.amazon.com/Plugable-Ethernet-Adapter-Compatible-Thunderbolt/dp/B084L4JL9K https://www.amazon.com/RSHTECH-Ethernet-Aluminum-Thunderbolt-RSH-WK-C25/dp/B09TB9TJ54 any help appreciated.

same here, on bare metal -- dell optiplex 7050 micro.

yes ... it was a while back ... using one of the arpl-0.4-alphaN versions. i think once/if the systems boots, via "Synology Assistant" (desktop app), the server shows up as "SynologyNAS" with status "Migrateable" (i believe).

on my dell T30, i'd migrated from 3615xs (DSM6) to 3622xs (DSM7) using arpl-0.4-alpha8 (i believe). now it's on arpl-1.0-beta13.

one more question ... if i were to get a J4125 motherboard (https://www.amazon.com/ASRock-J4125M-Quad-Core-Processor-Motherboard/dp/B08VGZYBTD), what would the "amisetupwriter 0x48A 0x?" param be? thanks again.

thanks for confirming.

sorry if this is dumb question, does this scenario and the "amisetupwriter" update apply to just the AMI bios with an onboard CPU? the fix works on my asrock j3455-itx (realtek RTL8111GR NIC). i also have an asrock z390 phantom gaming-itx/ac (with 8700K) running on arpl-1.0-beta10a. the onboard NIC is intel i219v. this build sometimes take 2-4 minutes to recognize the NIC on board or sometime not at all. usually works again after a few reboot. i couldn't find the tool, that i can run, to display the "One Of: OS Selection, VarStoreInfo ..." option on the z390 board to see whether i can do the AMI tweak. any help appreciated.

got it -- much appreciated. another question ... my setup: asrock z390 phantom ITX board. i've 8 drives -- 4 onboard SATA, 4 on a 9207-8i card. via arpl-1.0-beta10a, with all modules selected, my LAN (i219, i believe) and my LSI card is recognized. everything works. via arpl-1.0-beta11a, all modules selected, my LAN works but the LSI card isn't recognized. reboot again using the beta10a flash drive, everything working as before. not sure whether i should've done anything different for the beta11a to work. i'm fine with beta10a. thanks again. dh

apologies if this item was already covered earlier in the thread ... is there a list/descrs of all the modules available under "advanced menu"? i did a recent loader build, using aprl-1.0-beta11a, and couldn't get my LSI 9207-8i (4-drives) recognized. i ended up adding all the modules to the loader for the card to be recognized. any help appreciated. dh

just used the alpha9 image to upgrade my T30 PowerEdge to model DS3622xs+. no issues.

check this out ... https://xpenology.club/install-dsm-7-on-baremetal-or-vm/

- Outcome of the update: Successful - DSM version prior update: None - Loader version and model: Tinycore-Redpill 0.4.6 - DS918+ - 7.0.1-42218 update 3 - Using custom extra.lzma: No - Installation type: BAREMETAL - VivoPC (Celeron 2957u, 4GB), Zotac ZBox (Celeron 2957u, 4GB) - Additional comments: None

- Outcome of the update: Successful - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: Tinycore-Redpill 0.4.6 - DS3615xs - 7.0.1-42218 update 3 - Using custom extra.lzma: No - Installation type: BAREMETAL - Dell PowerEdge T30 (Xeon e3-1225 v5, 8GB), 6 x 3TB HDD - Additional comments: File Station, Download Station failed to start due issue with "Synology Application Service". Had to reinstall DSM 7 (preserving all files).

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-4 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Dell PowerEdge T30 - Additional comment: Reboot required

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