Migrating drives to new server, HDD driver not recognized

[SomeTester]

I recently built a new server with an Asus B450-MA motherboard. It starts up, but it does not recognize the previous install I imagine due to not detecting any drives. This was an old loader setup, but I'm fine maintaining that for now if possible. My current loader details: Jun loader 1.03b ds3615 DSM 6.2.3

 

I tried replacing the extra.lzma file on the second partition with a new one, version 0.12 I believe. In either case, still no such luck. 

 

End goal: revive previous installation on the server in its current state with a compatible loader for my current DS version with the necessary drivers to recognize my HDDs. Thoughts? It's been a very long time since I've messed with this, so appreciate any extra details. 

[Peter Suh]

20 minutes ago, SomeTester said:

Hyper Threading (HT) is for Intel only, so not applicable here.

 

I don't know what core-timings are, that's not a thing. Does he mean c-state...? I'm not sure how that would help. I still have the same issue with the Jun Loaders with the NIC Intel card, very disappointed.

 

In AMD, SMT is Intel's HT.

 

Disable SMT Mode in BIOS.
In a post two years ago, it seems that there was a problem even though I replaced it with an Intel NIC.
First try disabling simultaneous multithreading.

Edited September 18, 2022 by Peter Suh

[Peter Suh]

2 hours ago, SomeTester said:

I recently built a new server with an Asus B450-MA motherboard. It starts up, but it does not recognize the previous install I imagine due to not detecting any drives. This was an old loader setup, but I'm fine maintaining that for now if possible. My current loader details: Jun loader 1.03b ds3615 DSM 6.2.3

 

I tried replacing the extra.lzma file on the second partition with a new one, version 0.12 I believe. In either case, still no such luck. 

 

End goal: revive previous installation on the server in its current state with a compatible loader for my current DS version with the necessary drivers to recognize my HDDs. Thoughts? It's been a very long time since I've messed with this, so appreciate any extra details. 

 

Which redpill loader did you use?  ARPL?  TCRP?  Did the Synology model keep the DS3615xs?  Have you ever used an HBA?

[SomeTester]

1 hour ago, Peter Suh said:

 

Which redpill loader did you use?  ARPL?  TCRP?  Did the Synology model keep the DS3615xs?  Have you ever used an HBA?

Neither. I was using Jun's as described earlier. I just now tried TCRP but was not able to get an IP via DHCP or manually, not sure why.

 

In either case, do you have suggestions for my original configuration, via Jun 1.03b or 1.04b? Thanks.

[Peter Suh]

 

It's okay to keep the DS3615xs as it is, but the DS3615xs will soon end the DSM update from Synology.
DS3622xs+ is recommended for the most stable model with good compatibility with DS3615xs.

DS3615xs is also stable enough to migrate to DS3622xs+.

 

There are a few things you might have missed in the process of building the loader via TCRP.
USB VID/PID or MAC address setting, etc.
There are several reasons why an IP address cannot be found.

 

If possible, download My M SHELL, which can easily build TCRP without making an error, and try to build the load again using the command below.

The J option after the model is jun mod , which is currently the most preferred build method.
It prevents from falling into a state where booting is impossible after DSM update.

 

curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O

tar -zxvf my.sh.gz

 

for DS3615xs

./my.sh DS3615xsJ noclean

 

for DS3622xs+

./my.sh DS3622xs+J noclean

 

If you still can't find the IP address
Please attach all the logs that appear during the build process of the loader below to this post using the last eye-shaped spoiler in the icon.

[sbv3000]

9 hours ago, SomeTester said:

Neither. I was using Jun's as described earlier. I just now tried TCRP but was not able to get an IP via DHCP or manually, not sure why.

 

In either case, do you have suggestions for my original configuration, via Jun 1.03b or 1.04b? Thanks.

ive done a number of migrations from xpe5.2!! and 104b/6.x to 7 (3615/17/22 builds) using tcrp etc. my main lessons were to thoroughly test the hardware for compatability, maybe using a spare hdd to mimic your current environment then 'migrate'. @Peter Suh mshell and @fbelavenuto arpl tools are great utilities to create builds and 'fix' various quirks with tcrp , its a matter of experimenting with the one that works for your skill levels and hardware. in all situations you should have a data backup before attempting an update!

[SomeTester]

6 hours ago, Peter Suh said:

 

It's okay to keep the DS3615xs as it is, but the DS3615xs will soon end the DSM update from Synology.
DS3622xs+ is recommended for the most stable model with good compatibility with DS3615xs.

DS3615xs is also stable enough to migrate to DS3622xs+.

 

There are a few things you might have missed in the process of building the loader via TCRP.
USB VID/PID or MAC address setting, etc.
There are several reasons why an IP address cannot be found.

 

If possible, download My M SHELL, which can easily build TCRP without making an error, and try to build the load again using the command below.

The J option after the model is jun mod , which is currently the most preferred build method.
It prevents from falling into a state where booting is impossible after DSM update.

 

curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O

tar -zxvf my.sh.gz

 

for DS3615xs

./my.sh DS3615xsJ noclean

 

for DS3622xs+

./my.sh DS3622xs+J noclean

 

If you still can't find the IP address
Please attach all the logs that appear during the build process of the loader below to this post using the last eye-shaped spoiler in the icon.

 

While I was experimenting with trying to get the Jun one to work, I "migrated" to DS3617. After it rebooted, it never came back online. After I reboot again it says that it can "recover" the Synology. However, again, after rebooting, it does not come back online as networkable. I've tried all variations of extra.lzma that I could find, but all yielded the same result. Prior to me moving on to trying TCRP, do you have any other thoughts or suggestions for me?

[sbv3000]

 
While I was experimenting with trying to get the Jun one to work, I "migrated" to DS3617. After it rebooted, it never came back online. After I reboot again it says that it can "recover" the Synology. However, again, after rebooting, it does not come back online as networkable. I've tried all variations of extra.lzma that I could find, but all yielded the same result. Prior to me moving on to trying TCRP, do you have any other thoughts or suggestions for me?

Your mobo spec is pretty simple so sata ahci and realtek nic should all be found by the tcrp/m shell/arpl tools. Unless you have an hba and more than 4 drives? Try a build with a spare HDD

Sent from my NOTE 20 using Tapatalk

[SomeTester]

18 hours ago, sbv3000 said:

Your mobo spec is pretty simple so sata ahci and realtek nic should all be found by the tcrp/m shell/arpl tools. Unless you have an hba and more than 4 drives? Try a build with a spare HDD

Sent from my NOTE 20 using Tapatalk
 

Appreciate the replies. I am trying TCRP now as a fresh install, and am presented with the following:

 

tc@box:~$ ./rploader.sh satamap

Found "01:00.1 Advanced Micro Devices, Inc. [AMD] Device 43c8 (rev 01)"
Detected 8 ports/2 drives. Bad ports: 3 4 7 8. Override # of ports or ENTER to accept <8> 

Found "09:00.0 Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)"
Detected 1 ports/0 drives. Override # of ports or ENTER to accept <1> 

Computed settings:
SataPortMap=81
DiskIdxMap=0008

WARNING: Bad ports are mapped. The DSM installation will fail!

 

This representation of data is not very intuitive. If I am understanding this correctly, I would want to override ports 3, 4, 7, and 8. I assume that my two drives are physically mapped to ports 1 and 2. For the two questions, I am not sure what sort of response it is expecting for each. Thoughts?

[sbv3000]

Appreciate the replies. I am trying TCRP now as a fresh install, and am presented with the following:
 

tc@box:~$ ./rploader.sh satamapFound "01:00.1 Advanced Micro Devices, Inc. [AMD] Device 43c8 (rev 01)"Detected 8 ports/2 drives. Bad ports: 3 4 7 8. Override # of ports or ENTER to accept  Found "09:00.0 Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)"Detected 1 ports/0 drives. Override # of ports or ENTER to accept  Computed settings:SataPortMap=81DiskIdxMap=0008WARNING: Bad ports are mapped. The DSM installation will fail!

 
This representation of data is not very intuitive. If I am understanding this correctly, I would want to override ports 3, 4, 7, and 8. I assume that my two drives are physically mapped to ports 1 and 2. For the two questions, I am not sure what sort of response it is expecting for each. Thoughts?

I would override with 2 and 0, this should work for your setup. Strange representation of the controller but it's known that some chipsets give phantom settings. You could check the chipset spec with lspci and search the vendor info if so inclined. Adding more drives at a later date would need a rebuild of the loader. Also check the bios for enabled sata and esata, this might be adding confusion to the results

Sent from my NOTE 20 using Tapatalk

[SomeTester]

4 hours ago, sbv3000 said:

I would override with 2 and 0, this should work for your setup. Strange representation of the controller but it's known that some chipsets give phantom settings. You could check the chipset spec with lspci and search the vendor info if so inclined. Adding more drives at a later date would need a rebuild of the loader. Also check the bios for enabled sata and esata, this might be adding confusion to the results

Sent from my NOTE 20 using Tapatalk
 

Similar issue as I had with the Jun Loader: the system is detected by find.synology.com, but the host itself is not pingable/can't access port 5000 or anything else. When building it, I went with apollolake and let it find drivers via the ext function. It found drivers automatically for the Ethernet chipset, but I guess it still failed. Thoughts?

 

Details: 

RedPill DS918+ v7.1.0-42661

 

It looks that you will need the following modules : 


Found SATA Controller : pciid 1022d000043c8  Required Extension : 
No matching extension
[#] Checking runtime for required tools... [OK]
[#] Adding new extension from https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json... 
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################## 100.0%
[OK]
[#] ========================================== pocopico.r8169 ==========================================
[#] Extension name: r8169
[#] Description: Adds RealTek RTL-8169 Gigabit Ethernet driver Support
[#] To get help visit: <todo>
[#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/r8169
[#] Software author: https://github.com/pocopico
[#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 dva1622_42218 dva1622_42621 ds920p_42962 ds1621p_42661 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds3622xsp_42218 ds2422p_42962 dva1622_42962 ds2422p_42218 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 ds2422p_42951 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 
[#] =======================================================================================

Found Ethernet Interface : pciid 10ecd00008168 Required Extension : r8169
Searching for matching extension for r8169
Found matching extension : 
"https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json"
Found VGA Controller : pciid 1002d00001638  Required Extension : 
No matching extension
Found SATA Controller : pciid 1022d00007901  Required Extension : 
No matching extension

 

 

[sbv3000]

Similar issue as I had with the Jun Loader: the system is detected by find.synology.com, but the host itself is not pingable/can't access port 5000 or anything else. When building it, I went with apollolake and let it find drivers via the ext function. It found drivers automatically for the Ethernet chipset, but I guess it still failed. Thoughts?
 
Details: 
RedPill DS918+ v7.1.0-42661
 

It looks that you will need the following modules : Found SATA Controller : pciid 1022d000043c8  Required Extension : No matching extension[#] Checking runtime for required tools... [OK][#] Adding new extension from https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json... [#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json######################################################################## 100.0%[OK][#] ========================================== pocopico.r8169 ==========================================[#] Extension name: r8169[#] Description: Adds RealTek RTL-8169 Gigabit Ethernet driver Support[#] To get help visit: [#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/r8169[#] Software author: https://github.com/pocopico[#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 dva1622_42218 dva1622_42621 ds920p_42962 ds1621p_42661 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds3622xsp_42218 ds2422p_42962 dva1622_42962 ds2422p_42218 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 ds2422p_42951 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 [#] =======================================================================================Found Ethernet Interface : pciid 10ecd00008168 Required Extension : r8169Searching for matching extension for r8169Found matching extension : "https://raw.githubusercontent.com/pocopico/rp-ext/master/r8169/rpext-index.json"Found VGA Controller : pciid 1002d00001638  Required Extension : No matching extensionFound SATA Controller : pciid 1022d00007901  Required Extension : No matching extension

 
 

Can you post the step by step tcrp command results and the saved user_config.json.?

Sent from my NOTE 20 using Tapatalk

[SomeTester]

50 minutes ago, sbv3000 said:

Can you post the step by step tcrp command results and the saved user_config.json.?

Sent from my NOTE 20 using Tapatalk
 

I think that it was due to the DSM version I was using. It worked right out the gate with DS1621+. I see a note there about AMD Ryzen (which is my CPU), but the note eludes to a comment about SATA drives. Not sure if that's related at all to it not appearing/booting up with any of the other DSM versions. Given that it worked with this one, would you come to the same conclusion? I just did an automated install and none of the optional steps this round.

[SomeTester]

On 9/12/2022 at 5:15 AM, Peter Suh said:

 

It's okay to keep the DS3615xs as it is, but the DS3615xs will soon end the DSM update from Synology.
DS3622xs+ is recommended for the most stable model with good compatibility with DS3615xs.

DS3615xs is also stable enough to migrate to DS3622xs+.

 

There are a few things you might have missed in the process of building the loader via TCRP.
USB VID/PID or MAC address setting, etc.
There are several reasons why an IP address cannot be found.

 

If possible, download My M SHELL, which can easily build TCRP without making an error, and try to build the load again using the command below.

The J option after the model is jun mod , which is currently the most preferred build method.
It prevents from falling into a state where booting is impossible after DSM update.

 

curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O

tar -zxvf my.sh.gz

 

for DS3615xs

./my.sh DS3615xsJ noclean

 

for DS3622xs+

./my.sh DS3622xs+J noclean

 

If you still can't find the IP address
Please attach all the logs that appear during the build process of the loader below to this post using the last eye-shaped spoiler in the icon.

 

Hey @Peter Suh, appreciate you sharing that script. Would it be possible to alter that bash file easily enough to specify a different *.pat file, such as DSM 6.2 with DS3615xs?

 

Also, I unfortunately had the same outcome post install where the server is not pingable nor loads the webpage. The TCRP bit without Internet connectivity was a mess up on my side, but with TCRP, the only one I've gotten to work has been DS1621+ with V1000. However, I wanted to stick with the older DS with DSM 6.2 if possible.

[sbv3000]

15 hours ago, SomeTester said:

I think that it was due to the DSM version I was using. It worked right out the gate with DS1621+. I see a note there about AMD Ryzen (which is my CPU), but the note eludes to a comment about SATA drives. Not sure if that's related at all to it not appearing/booting up with any of the other DSM versions. Given that it worked with this one, would you come to the same conclusion? I just did an automated install and none of the optional steps this round.

ds1621 probably 'worked' because of the device tree architecture that builds on the fly hardware spec. if you are 'working' and happy then job-done

[SomeTester]

59 minutes ago, sbv3000 said:

ds1621 probably 'worked' because of the device tree architecture that builds on the fly hardware spec. if you are 'working' and happy then job-done

Well, I do want to get this working with the older DS versions and with DSM 6.2. What suggestions do you have as to why most of the time with TCRP I simply cannot ping the host after boot? I'm just simply stuck on that front. Or, when using the Jun Loader, I can perform the migration, but it doesn't come back after rebooting and finishing the migration. 

[Peter Suh]

Prefer the old jun's loader over redpill?
I share jun's loader image for DSM 6 for you.
Instead, you have to manually edit the VID / PID to match your USB stick.
It shares both DS3615xs and DS918+ img file.

 

In my old memory, the DS3615xs driver shared by ig-88 was older than DS918+.

It would be good if @IG-88 checks once more.

 

If you try and fail with the final driver of DS3615xs
It might be worth trying a migration using the DS918+ loader.
There is no separate HBA or additional Sata interface, etc. Is the HDD mounted on the built-in Sata only?

 

 

 

Edited September 15, 2022 by Peter Suh

[Peter Suh]

1 hour ago, Peter Suh said:

Prefer the old jun's loader over redpill?
I share jun's loader image for DSM 6 for you.
Instead, you have to manually edit the VID / PID to match your USB stick.
It shares both DS3615xs and DS918+ img file.

 

In my old memory, the DS3615xs driver shared by ig-88 was older than DS918+.

It would be good if @IG-88 checks once more.

 

If you try and fail with the final driver of DS3615xs
It might be worth trying a migration using the DS918+ loader.
There is no separate HBA or additional Sata interface, etc. Is the HDD mounted on the built-in Sata only?

 

 

 

 

DS3615xs ( synoboot_103b_ds3615_6.2.3_0.11_test_patch.img )

https://drive.google.com/file/d/1_FzGGcXidj8zqNjG6fYrJVDZRm-_Q1IT/view?usp=sharing

 

DS918+ ( synoboot_104b_ds918_6.2.3_i88_0.13.3_patch.img )

https://drive.google.com/file/d/1u-JyuwgAD2LcgNzpBUMScK33rd_ySFB2/view?usp=sharing

[SomeTester]

2 hours ago, Peter Suh said:

Prefer the old jun's loader over redpill?
I share jun's loader image for DSM 6 for you.
Instead, you have to manually edit the VID / PID to match your USB stick.
It shares both DS3615xs and DS918+ img file.

 

In my old memory, the DS3615xs driver shared by ig-88 was older than DS918+.

It would be good if @IG-88 checks once more.

 

If you try and fail with the final driver of DS3615xs
It might be worth trying a migration using the DS918+ loader.
There is no separate HBA or additional Sata interface, etc. Is the HDD mounted on the built-in Sata only?

 

 

 

That's correct, no HBA and I am plugged in directly to the onboard SATA ports. Unless if I am mistaken though, I thought that I tried the latest Jun loaders. In either case, I will try once more via the Jun loader way and update the first partition with the USB items, correct serial, and MAC address. If this doesn't work, I am pretty stumped. 

[sbv3000]

47 minutes ago, SomeTester said:

That's correct, no HBA and I am plugged in directly to the onboard SATA ports. Unless if I am mistaken though, I thought that I tried the latest Jun loaders. In either case, I will try once more via the Jun loader way and update the first partition with the USB items, correct serial, and MAC address. If this doesn't work, I am pretty stumped. 

check this thread  https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ and also follow the process using ofsmount to edit the image for grub vid/pid etc

 

[SomeTester]

5 minutes ago, sbv3000 said:

check this thread  https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ and also follow the process using ofsmount to edit the image for grub vid/pid etc

 

I followed the latter half of this post before with no such luck. But at the same time, it was kind of confusing. For DS3615xs, should I load up the extra.lzma as well as the zImage and rd.gz into the second partition? I guess following "Case 2" should be my path, right?

[Peter Suh]

10 minutes ago, SomeTester said:

I followed the latter half of this post before with no such luck. But at the same time, it was kind of confusing. For DS3615xs, should I load up the extra.lzma as well as the zImage and rd.gz into the second partition? I guess following "Case 2" should be my path, right?

 

Any plans to use the above image I shared?
The files you mentioned are IMG files that have already been placed on the correct partition and have already been verified until DSM installation.

[SomeTester]

1 minute ago, Peter Suh said:

 

Any plans to use the above image I shared?
The files you mentioned are IMG files that have already been placed on the correct partition and have already been verified until DSM installation.

Yes sir! I simultaneously was doing that now. I'm just hedging my bets haha.

[SomeTester]

25 minutes ago, Peter Suh said:

 

Any plans to use the above image I shared?
The files you mentioned are IMG files that have already been placed on the correct partition and have already been verified until DSM installation.

Just tried out the first IMG. Updated the contents of grub.conf, and it is not pingable post boot. I tried both fresh install and reinstall options. I'll try the second IMG here shortly.

[SomeTester]

19 minutes ago, SomeTester said:

Just tried out the first IMG. Updated the contents of grub.conf, and it is not pingable post boot. I tried both fresh install and reinstall options. I'll try the second IMG here shortly.

Hey @Peter Suh, no luck for either. After booting up and using find.synology.com or directly navigating to the IP and port 5000, it cannot reach the destination, nor is it pingable. The find web app "identifies" that there is a host to connect to, but nothing else. Though it currently has DSM 7 on it (whe I finally got the one Ryzen noted one to work, V1000, which isn't good for me). In either case, what happened here has been consistent since the beginning of this thread.

 

For what it's worth:

 

CPU: AMD Ryzen 5 5600G 6-Core 12-Thread Unlocked Desktop Processor with Radeon Graphics

Motherboard: ASUS Prime B450M-A II AMD AM4 (Ryzen 5000, 3rd/2nd/1st Gen Ryzen Micro ATX Motherboard (128GB DDR4, 4400 O.C.), NVMe, HDMI 2.0b/DVI/D-Sub, USB 3.2 Gen 2, BIOS Flashback, and Aura Sync)

 

Driver-wise, it is the BM450 chipset as far as I can tell. This is a super simple setup, and I can't figure out why I'm having so much trouble with it. Any other thoughts?

[Peter Suh]

6 hours ago, SomeTester said:

Hey @Peter Suh, no luck for either. After booting up and using find.synology.com or directly navigating to the IP and port 5000, it cannot reach the destination, nor is it pingable. The find web app "identifies" that there is a host to connect to, but nothing else. Though it currently has DSM 7 on it (whe I finally got the one Ryzen noted one to work, V1000, which isn't good for me). In either case, what happened here has been consistent since the beginning of this thread.

 

For what it's worth:

 

CPU: AMD Ryzen 5 5600G 6-Core 12-Thread Unlocked Desktop Processor with Radeon Graphics

Motherboard: ASUS Prime B450M-A II AMD AM4 (Ryzen 5000, 3rd/2nd/1st Gen Ryzen Micro ATX Motherboard (128GB DDR4, 4400 O.C.), NVMe, HDMI 2.0b/DVI/D-Sub, USB 3.2 Gen 2, BIOS Flashback, and Aura Sync)

 

Driver-wise, it is the BM450 chipset as far as I can tell. This is a super simple setup, and I can't figure out why I'm having so much trouble with it. Any other thoughts?

 

I also have the ASUS TUF B450M-PLUS GAMING with similar specs to yours.
The invisible IP has to do with the built-in NIC.
Both MOBOs are using the same RTL8111H.
I know that Jun loader's extension driver supports this chipset.
I'll try to see if the same thing happens with my MOBO.