Decebalus

I have the same server, same Xenon CPU and the latest ARPL version and works with no modifications using 3622xs+ model. Both NICs are recognized OOB. Just followed the steps in order to select the options and build the loader. Not sure why you are having the issues.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 2 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen 8 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 2 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P8H61-M-LE-R2 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 2 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P5N7A-VM - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 2 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - GA-B75M-HD3 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 2 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - GA-Z68X-UD3H-B3 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 2 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL – Lenovo Thinkcentre M910S - Additional comments: Upgraded like an original Synology NAS through manual update

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 1 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen 8 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 1 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P8H61-M-LE-R2 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 1 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P5N7A-VM - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 1 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - GA-B75M-HD3 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 1 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - GA-Z68X-UD3H-B3 - Additional comments: Upgraded like an original Synology NAS through manual update - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42692 Update 1 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL – Lenovo Thinkcentre M910S - Additional comments: Upgraded like an original Synology NAS through manual update

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen 8 - Additional comments: Upgraded like an original Synology NAS - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P8H61-M-LE-R2 - Additional comments: Upgraded like an original Synology NAS - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P5N7A-VM - Additional comments: Upgraded like an original Synology NAS - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - GA-B75M-HD3 - Additional comments: Upgraded like an original Synology NAS - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL - GA-Z68X-UD3H-B3 - Additional comments: Upgraded like an original Synology NAS - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: TCRP Friend 0.0.3 - Using custom extra.lzma: NO - Installation type: BAREMETAL – Lenovo Thinkcentre M910S - Additional comments: Upgraded like an original Synology NAS

Tried with TCRP w/o Friend and same result. Most likely DSM 7.0 does not like something about the old hardware. A note that yesterday I have upgraded 4 servers from 6.2.3 to 7.1.1 without a hitch using TCRP Friend, except this one.

Interesting. As a note, the upgrade I attempted this morning for another machine using DS3615xs platform, from DSM 6.2.3 to 7.1.1 went without a hitch. Smooth as butter. Weird that the machine with the old Pentium CPU is the only one having the NIC issue.

Delete

Right. So not really the same situation since in my case TCRP is getting an IP address and it’s able to check for new versions online when it boots up. It looks like my NICs are going down after TCRP has done its job and when DSM starts to load.

In your case, was TCRP Friend getting an IP address?

Hi, First of all, I want to say HATS OFF to Pocopico - and everyone else who contributed to its development - for this awesome TCRP Friend bootloader! I am in awe to where we got from Jun's boot loader years ago. Congrats! Now, to my silly issue and I deeply apologize if this has been encountered and discussed before. Despite my research over the past few days, I was not able to find anything similar. I have an older PC (CPU Pentium dual-core E5300) running DSM 6.2.3 and I am trying to install on it TCRP Friend 0.0.0.3 (a note that I've installed TCRP Friend successfully on a couple of other servers w/o any issues and running latest DSM 7.1.1-42692 update 2). The (stupid) issue I am hitting is like this: 1. TCRP Friend boots up without issues 2. Obtains an IP, checks online for latest version, etc. 3. Displays the last line "Loading exec, nothing will be displayed here anymore..." 4. After 5-10 seconds the NIC goes dark, it turns off And it's not only the Atheros NIC from the MB, I tried also a DGE-530T NIC (which I know it works on another machine) with the same result. Tiny Core and ./rploader.sh at build recognize both cards and it adds the extensions. And, again, both are getting an IP address when TCRP Friend boots up but they turn off shortly after. Could it be that the CPU is too old and DSM 7 does not support it? Or is it something else that I'm missing (incompatible NICs somehow with the note that the DGE-530T one works with DSM 7 on another machine)? Could it be the extension scripts? Has anyone else encountered this issue? Thanks a lot for all the help.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 - Loader version and model: TCRP FRIEND version 0.0.3 DS3622xs+ - Using custom extra.lzma: NO - Installation type: VMWare - Additional comments: Manual install via DSM GUI

Agreed with merve04. You can go a step further and install ESXI bare metal on Mac if you don’t need macOS. I am running Esxi 6.7 on a Mac mini late 2012 and on it Xpenology VM with a few docker containers as well as another VM with pfSense. Works great despite that’s only a Mac mini.

Yup! You got it. Trust me, been there, done that Another option is to unplug and plug back the USB stick but it’s faster and more elegant to umount through terminal. Plus it’s safer since unplugging the USB could result in data corruption on the stick. When the partition is mounted by your terminal instance the DSM update can’t write to it, hence the error and the need to unmount it.

That makes no sense. Mine got updated in less than 4 min and was available on the network immediately after that. It does have a xenon CPU but even with a GT CPU it should be under 10 min.

You got it. Plus you have to unmount synoboot2 after you have copied the file with umount. After that you start the manual update from Control Panel. Do not reboot before updating.

It's right in the Jun's loader 1.03b bootloader. Get it from there (from the 2nd partition of 30MB).

Yes, it works. As others have stated, for HP Microserver Gen8, if you have DSM 6.2.2 you need to use the custom extra.lzma. In order to update to DSM 6.2.3 you need to replace the custom extra.lzma with the original one from Jun's v 1.03b. I went through this process with 4 Xpenology servers without any issues. Just make sure you replace the extra.lzma on the USB stick through ssh / terminal before updating to DSM 6.2.3 through Control Panel. You will have to update manually i.e. select the 6.2.3 pat file. For new installation you just need to use Jun's 1.03b original boot loader (w/o any changes) and 6.2.3 pat file. Hope that helps.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver Gen 8 - Additional comments: Using built in NIC - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P5Q - Additional comments: Using built in NIC - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P8H61-M-LE-R2 - Additional comments: Using built in NIC - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25423 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASUS P5N7A-VM - Additional comments: PCI-E NIC; onboard NIC does not work

It sounds like you have the right steps. To answer your question, yes, you should see the HP microserver with the factory broadcom NIC on the network if you have used the proper extra.lzma v0.5 modified by IG88. That file, plus the rd.gz and zImage files from the 24922 DSM 6.2.2 for 3615xs should be copied to the 2nd partition of 30MB on Jun's 1.03b bootloader for 3615xs. I recommend to redo the steps carefully since it's possible you missed a step in the execution. Always use an extra empty HDD. If you have used the HDD previously, I recommend to erase it, just to be safe there are no DSM leftovers on it.

Correct and thanks!

Duh! I did not unmount the USB stick before loading the .pat file. That's why I was getting the error. So after replacing the extra.lzma file, just unplug and plug back in the USB stick, then proceed with update. Hope this helps others.

I am sure I am doing something wrong. I have mounted the USB stick and replaced the extra.lzma file, however, when I am trying to load the 6.2.3 pat file from control panel, I am getting an unknown error. Now, 2 things I think it is worth mentioning: 1. 6.2.3 does not show up under Update/Restore in control panel - hence trying to install it manually. Is it expected for 6.2.3 not to show up as an available update? 2. I have not replaced zImage and rd.gz files on the stick with the ones from June's loader. Those files are from 6.2.2. Do those need to be replaced as well? Thanks in advance.

Quick update: I have been running 6.2.3 non-stop since yesterday and, so far, it has been rock solid. In fact, with 6.2.2 and the custom extra.lzma used previously, one of the HDDs connected to one of the two extra Marvell SATA ports was dropping from the pool randomly. Not happening any longer with 6.2.3 and June's 1.03b unmodified loader.

You rock! Thanks a million, sir!

That's perfect. Is there a link or a thread that contains those details? What commands to use in terminal? Any help is definitely appreciated.