Wreid23

- Outcome of the update: SUCCESSFUL - DSM version prior update: TCRP v0.9.2.9(Updates done in 9.2.6 from Terminal to update to 0.9.2.9 , very convenient) DS918+ and DSM918+ DSM 7.1.1-42962 withfriend - Loader version and model: TCRP v0.9.2.9 DS918+ and DSM918+ DSM 7.1.1-42962 Update 2 (Manual Update from DSM GUI) - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS ROG STRIX Z390 I GAMING, Intel - Core i3-8100 3.6 GHz Quad-Core Processor - Additional comments: TCRP Friend seems to have done all the work. Took about 3-5 Minutes Total. Everything is in Working Order and Data OK.

take disks out his system. take empty hdd load dsm 5 on there and put some junk data then create loader and test if it works (reads hardware fine, gets ip etc etc and you of course setup loader properly with right info) it should be fine to my understanding. No reason to not test though, its easy and fast to test.

Just chiming in to say THANK YOU for the Hard work for all parties involved successful upgrade today on my system

Both of Your sata port maps sound wrong try sataport map 44 (I have 4 disks so I know that works) . I don't know what it should be for 12 disks but you should pm IG88 or flyride and or look for sataportmap threads to see what values should be in a VM or baremetal. Tons of same question asked on this forum just gotta search. Some info(one example):

Option 1: proxmox: use a virtual serial on your VM and test on your hardware with a junk disk and your usb drive taht you plan to use with baremetal Option 2: You would either need to use the one on your motherboard (if it has one) or get a pcie serial card and a serial to USB

PM'd You easy way

I plan to do the same but since you on proxmox make a backup of Your VM throw new hardware in and Try thats the best part of VM lol. We are the testers and please let me know if it works . nothing to lose

I would hang tight until we have confirmations that it works or take drives out and test with a junk disk and existing 7.0.1 loader to see if latest updates 1 and 2 work. That's usually the only way to know have to test, test, test lol. This experiment helped me learn proxmox very quickly and that eventually led to getting baremetal working after playing with sataportmaps / diskmaps in the vm and gaining confidence while trying to repeat working builds on junk disk. Short Story try it in the VM. The Auto command at the end of your build script should discover your ethernet card and download the driver to my understanding.

is there any mirror of the above .pat files for beta??

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 1 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: YES - Installation type: BAREMETAL - ASUS ROG STRIX Z390 I GAMING, Intel - Core i3-8100 3.6 GHz Quad-Core Processor - Additional comments: Reboot required

is your nic on the compatible list?, you booted UEFI and it worked just sounds like you don't have a compatible NIC. What is your NAS specs? You Should prob start here and get your device id by booting into a linux usb and check if ytou have compatible nic and then move on to using extra.lzma once you understand whats going on:

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23922 Update 5 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: YES - Installation type: BAREMETAL - ASUS ROG STRIX Z390 I GAMING, Intel - Core i3-8100 3.6 GHz Quad-Core Processor - Additional comments: Ran Recommended Commands: rm -rf /usr/lib/modules/update/* rm -rf /usr/lib/firmware/i915/* from ssh terminal to remove drivers and restarted before using newly copied Test LZMA 0.11. Updated Directly with DSM_DS918+_25426.pat file, took about 7-10 minutes from restart back to Main Page. All Settings Seem to be intact including Docker. AMAZON USB 3.0 GIGABIT ETHERNET NIC Working (0B95 1790), . I-219-V Internal NIC (WORKING GREAT with Test LZMA v0.11 previously did not work). I am a happy camper. I also recommend having a ubuntu iso flashed to a flash drive on hand for quick troubleshooting and getting a better view of your devices ID's & grub editing/mounting. Cheers and Thank You again to all members who assisted!

Boot Your nas with linux bootable (ubuntu or whatever) and get the vid and pid and match it in the excel sheet with the dsm you want to use.

only 1 of the nics will work cause of driver compatibility

Hey All, Just returned this board. Great Board but it has the I 219V nic please get a linux bootable and confirm the VID and PID of your nic. If it is not on this list it will not work. Newer device ID's of this nic stop it from being recognized (cause it does not match the driver id for it) if you use the search bar in the forums it has been covered in detail. If you do not know how to get the VID and PID of your nic you are going to take a flash drive google how to make a linux bootable whether it be mint or ubuntu. Take all your drives out boot into the linux bootable, open terminal run sudo -i to get elevated priveleges. Then run lspci -k confirm the VID and PID of your nic and find it on the excel sheet for the dsm version you are using using the link below , if you confirm it matches on the spreadsheet, remake your loader/settings and test with 1 junk hdd installed (avoid using your active setup unless its a new setup). Test with junk setup until you see nic if you cannot see nic or connect to find.synology.com your nic is more than likely unsupported. Next steps is getting a supported nic from the confirmed list and you should be good.