venno

Yes they are different sizes as they contain a differing quantity of programming lines, the syntaxs and structures in both seem the same though. I would gues that the extra2 file has less lines/content as it may serve a differnet process in the loader (possibly upgrades maybe). I used the following post as a guide to unpack the lzma archives, modify internal files and then repack: https://xpenology.com/forum/topic/14358-tutorial-modifying-104b-loader-to-default-to-24-drives/ I concur, did the same, better safe than sorry. My mistake I should have elaborated more, the lzma and also the other files I used where tested on a test install(s) to amalgamate all the mods I would need for my bare metal install. Once I was happy I performed a fresh bare metal install using all the mods/hacks I required for my HW platform, so my finally production install occured as I required with collected files and hacks. The reason for posting the lzma is my near complete lack of specific knowledge of how the code I entered may affect other things (unintended consequences) and I was after comment from an experienced set of eyes. This worked, you have pointed out the part of the patch file I missed. In hindsight I should have started with a slighlty older version of DSM so I could test the efficacy of my mods after performing an upgrade/update. The mods work for the latest version but may not remain functional in an upgrade scenario. I may repeat all my steps but in a VM environment to try and gain a confidence level regards upgrading.

Hi IG-88 Thanks for replying, can you expand on this comment I am unsure of what you mean/refer to: I had missed the lower part of the patch file and I guess would need to add: +_replace 'maxlanport="2"' 'maxlanport="4"' /tmpRoot/etc.defaults/synoinfo.conf I found the extra.lmza and extra2.lmza similar so made my mods to both files, for brevity I only posted the extra.lmza for comment, or does the extra2 require different modification? I ignored the wol options as I did not think it important in my use case or do they need to be specified for programming reasons to enable the mtu values to be changed? I came about the lan ports mod when I had issues with my new 918+ baremetal install only seeing 2 nics, I observed that when I modified the file '/etc.defaults/synoinfo.conf' and changed this value to 4 I got my additional 2 ports to appear in DSM. I decided to try and make this change permanent in the loader and began to investigate. I don't know the ins/outs of how the loader fil;es work but based on observation of the contained code I made the following assumptions: 1. The override file probably passes in values to the DSM that override the set ones in either the kernel or loader files (or both maybe) 2. Both lmza archives would require the same mods to the same files 3. I should endevour, where possible, to place code mods in the loader on a line where existing mods near the actual lines in the file being modified are located Cheers for the help

Could someone double check the mods I made to synoinfo_override.conf and jun.patch to enable 4 lan ports in the 918+ extra.lmza attached, its my first time modding this type of file and I just want to make sure (I did use for new install and it did work, seemingly). cheers extra.lzma

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: New Install - Loader version and model: Juns v1.04b - DS918+ - Using custom extra.lzma: Yes - both extra/extra2 918+_v0.13 as per IG88 - Installation type: BAREMETAL - a2sdi-h-tf SuperMicro dual 10gbe, HP NC360T, UNAS build 8 x 4tb hdd and 4 x 1tb ssd plus optane cache ssd - Additional Comment: modified both lzma to provide for default of 4 nic ports, injected rd.gz and zImage from PAT as per IG88

Just found the section by IG88 on the 918 extra files mod to boot drive, works like a charm, posted too quick for help.

Just found the section on 918 extra files mod by IG88, works like a charm, I posted too quick.

New install and am running juns 1.04b loader and DSM 6.2.3 25426 PAT file. DS918+ I have a Supermicro A2SDi-H-TF mobo that has 2 onboard 10gbe copper nics, Icannot get these to show up in DSM (I have used a USB ethernet dongle and the IPMI to install and configure DSM so far). The onboard nics are intel x557 I think which should be supported by ixgbe inbuilt driver. Can anyone suggest what to do to get nics showing up ?

New install and am running juns 1.04b loader and DSM 6.2.3 25426 PAT file. I have an Optane p800 m2 installed on the PCIE x2 m2 slot in a Supermicro A2SDi-H-TF mobo (its on the 918 supported list), it shows in bios but not in DSM, or even ssh'ing and running 'nvme list'. I tried the libsynonvme.so.1 in /usr/lib64 and reboot but still no change. Can anyone help with suggestions to try ?

Cheers for letting me know, I had disabled vt-d in bios previously. I think your board has 4 x 1gbe nic ports and these should be recognized by the 1.04 loader natively or older loader with extra.izma as you have found out and installed. My board only has 2 x 10gbe copper nic ports and I think these require a higher driver revision than what is in the latest loader, as well as the extra.izma. I don't think kernel panic is occuring or the i915 is problematic, I think the install is occurring fine just no nic driver working. I may try and get a usb to ehternet adaptor and try.

Ok I have searched thru the threads and find that my motherboard should be fully supported according to IG-88 where he responded to a request to provide the nic driver. The actual nic chip is x557 (I got it wrong in my last post) and is part of the ixgbe.ko driver in IG-88's extra.izma which I have already tried. So the only thing I can think of is a kernel panic is occuring, possibly related to the i915 driver maybe as my cpu has no integrated gpu, plus I am also booting in legacy mode so that the thumb drive will boot. Can the i915 be disabled?

Hi All I recently built a new Xpenology NAS using the following HW: Supermicro A2SDi-H-TF mini itx motherboard that has an intel atom SOC C3758 cpu Intel SOC C3000 integrated 2 10gbe copper ports X553 SOC controller for 12 sata ports, 4 x sata3 and 2 x mini-sas 8gb ecc ram Intel optane 800p m2 nvme Unas 810 case modified to house icy dock 4 bay ssd unit Seasonic 250W 1U psu 2 x 500gb ssd 2 x 1000gb ssd 8 x 4tb 3.5" I have been using Xpenology as my NAS OS for 5 yrs and am acustomed to installing it bare metal on HP microservers and also ESXi VM. I decided to try ds918+ as I want to use caching. I am using a samsung usb 3 fit drive for boot. The install gets to Jun's happy hacking message but the nic does not get IP and the NAS cannot be found on the network either by web finder or synology tool. Variations I have tried: ds3615 loader 103b ds3617 loader 103b ds918+ loader 3a plus extra.izma found on the forum ds918+ loader 104b ds3615 loader 102b I have disabled c states in bios and have also tried a usb 2 toshiba thumb drive. In each and every case the result is the same, happy hacking message and then nothing further, no network. I have managed to succesfully install latest freenas (this was my alternate OS) and verified that all my NAS HW workss correctly, so I don't have a fault with my HW or usb drive as it all works in freenas. I never had any issues on microserver and am at a loss as to why I cannot get a network as the intel igbe driver supports my nic and is available in expenology standard extra.izma according to this forum. Can anyone help?

Hi cristimv Sorry to hear about your NAS, thats the exact scenario I am trying to avoid. For me it would be disastrous if this occurred while I was away for work given how reliant I am on the functions provided by the 1515 currently and yes I am well aware of the atom bug and my unit is affected. Its interesting what you say about the cameras, when I was running exponology as a VM on my G8 I had 4 cameras and never had any trouble, I have a 4 pack camera licence. My plans have changed somewhat since the original post, I have purchased a HP ML310e V2 server with a xeon 1241 cpu, I will reuses what HW I can from my G8 (ram, raid card, cables, SSD's) and my NAS (just the disks). I have also ordered a dual port NIC card and an Icydock 4 bay SSD unit (fits into a 5.25 bay), these will also go into the new server which will run ESXi. The SSD's will provide VM storage and the HDD's will be passed thru to the Xpenology VM using the B120i controller in SATA AHCI mode. The only thing I am uncertain of is whether my ram will work in the new server, I have only found one post on German forum where someone claimed they had successfully re-used the same ram.

Hi All Need some advice on best way to proceed with a g8 microserver. I have 16gb of ram, an e3-1260l, and 4x3 TB wd red drives. I also have 2 pice cards spare, so I could use one of them. I have a dual Nic card and a raid card that can be reprogrammed to IT mode. My question is what is the best path forward for me to run Xpenology. Should I go bare metal or Esxi. In more detail, how should I best use the HW at my disposal in each scenario? Currently I run a ds1515+ which I am looking at retiring, it runs 6.1 dsm. I use the dsm virtual machine licence to run mail, cloud, caldav, carddav and surveillance station. The main dsm in install runs docker for plex, Sab, sickrage, photos, music streaming. I had been using the g8 for VM land but have finished with playing around and would like to repurpose the HW in a meaningful way. Appreciate any guidance suggestions.

Success! I was not able to create a raid group using a 3tb drive, but I dropped the size down to 600gb and have a volume 1 now. Apps seems to install and run ok, now for some further testing. Do i need to keep the 16gb disk 2 or can I delete it now I have a volume in operation?

Yep, realized that I just deleted the Syno OS which was on the 16GB drive its booted into the install DSM screen. I think I will just blow it away and re-import the OVF and add a third drive. Would there be anyway of transitioning the boot disk to an Xpenology bootloader for bare metal install?