ed_co

That's very interesting. So change the model is doable, but has to be DSM converted, you mean like from 6.2.3 to 7.X.X? This is because every DSM is always a different OS depending on the hardware and is not a common OS for all, right? If so, it is a pity there is no project trying to unify all the DSM OS's and create just one to be compatible with all the hardware at the same time, and is just matter of installing, and no loader needed anymore... could be somewhat doable?

Since the BIOS update never failed anymore. Haven't tested the asm1166, cause didn't need it. All looks is working as before with the previous mobo/cpu. I consider it a success, except I am still in 6.2.3 with its pros and cons... Will try to find a safe way to update to 7.2.1 with ARK, still nothing out there...

Unfortunatelly is not a guide and is using ARPL, not Arc Ideally I woud like to have the intel qsv, and sa6400 should have it, right? Why you chosing this model? @IG-88 Couple of more questions: - Very important! I guess you used all the loaders out there, what is the best for you: TCRP (looks like you don't use this one currently, why?), ARPL, Arc? - And last question, what is the procedure to update a new version of DSM with Arc in major DSM versions? Is more complicated in TCRP/ARPL? Thanks for the reply!!

@FOXBI Can you help here? Thanks

Changed to a new CPU, and wrong stuff (even the count/thread is wrong): Can anyone help with this? Thank you very much

BTW, I just changed from the i3 12100 to an i5 12400 6 cores/12 threads I guess, I don't need too much more for my needs

@IG-88I was thinking installing ark doing something like this: Although not sure how possible it is... If I could do this changing and then when I port it to dsm 7.2.1 maybe changing to a different model (like from dsm-918+ to sa6400) could be easier?

My mini pci-board is not that flimsy (https://www.sybausa.com/index.php?route=product/product&product_id=945), although I use it along the M.2 e-key -removing the onboard m.2 wifi card- adapter (similar or same to this: https://www.ebay.com/itm/123814040736)... but as I said in my previous post, after a bios update looks like works perfectly fine like before (fingers crossed!!). I am about to receive an asm1166 6x sata in m.2 M key board that I bought when the previous board was failing... (via Amazon). If you have a link of a better suggestion just let me know. The problem is that my motherboard is a mini ITX and has few expansion ports (Asrock H610M-ITX/ac). But please, send me your link suggestions, if you have. Thanks

I don't want to count the chickens before they hatch, but I end up updating the BIOS from 8.04 to 10.01 and looks like the problem disappeared...

@IG-88 or anyone else. Small stupid question about ARC: does it support more than 4 disks with DS918+ model? I hope not, I have 16 disks in Jun's DS918+

I have now partially working my migration hardware (some problems with the second controller, which disconnect the disks connected to it after a while with the log message "Drive Plugged out"). Thread here: Now let's say that I want to update from Jun's loader 1.04b 918+ BAREMETAL to ARC. I investigated how to do it in the "official way" (meaning, real Synology hardware), and I found this page: https://kb.synology.com/en-ph/DSM/tutorial/How_can_I_update_to_the_latest_DSM_version_from_an_older_version So after having a look how to update the DS918+ to the latest DSM 7.2.1, they advice: Starting from my version: 6.2.3-25426 First update to: 6.2.4-25556 Then update to: 7.0.1-42218 Then update to: 7.2.1-69057 (with Update 1) And finally update to: 7.2.1-69057 Update 5 So I was thinking if could be possible to do it that way: Creating an ARC loader based on 918+ (to match exactly the current installation), and keep installing in sequence all this updates (probably changing the loader in every step of the way), so it will be smooth and with no problems instead of trying to do a migration, like even @AuxXxilium discourages to do it in his wiki, advising: "Upgrade DSM 6 to DSM 7 can cause some Issue, please use clean Disks for DSM 7 (Partition Layout and Size changed)." @AuxXxilium, @Polanskiman, @IG-88, @flyride or anyone else, do you think could be possible to do it? Thank you very much

Have it partially working with the drivers 0.13.9 for 6.2.3 918+, just need to see what is happening to my second controller as I am getting disks disconnected after a while when are connected to this second controller mini pcie via m.2 e key adapter. Not sure why is happening, but I am very happy to see it working in a way...

It would be so great if this guide could be updated to current status. I think is quite outdated with all the current possibilities in platforms and loaders...

Haven't mentioned the i211, which is not present in my current motherboard (h610m-itx/ac) Now there are lots of loaders, and it looks like lately ARC is the one that is getting traction (more than ARPL or TCRP). Although not sure if is better or worse. But even ARC has variations like ARC-A, which I am not sure what of them to get. My only worry with the new loaders is having to create another loader every time you have to update to a new version, or you will not be able to load DSM anymore. Which I never saw how this is done and how complex it is. I loved with Jun's loader, you could update any update from the DSM control panel with no problem.

So with your 0.13.9 driver extension for 918+ for Jun's loader 6.2, will work the m.2 sata x6 asm166 controller or the m.2 x5 jmb585 controller?? Need to buy one asap. If both are compatible, any preferences for any of them? Thanks

I changed from my motherboard from H370M-ITX/ac to H610M-ITX/ac and using the same controller SATA card SYBA SI-MPE40125 4 SATA ports -with Marvell 88SE9215 controller-, installed via M.2 e-key to mini pic-e adapter. While I was not having any problem with the first board using it almost 24/7 for several years, with the new motherboard something weird is happening, after a while the disk connected to the second controller just disappears... and I don't know why... it does not make any sense to me... In Storage Manager/logs it says: "Drive plugged out" Why could be the cause? Is the card that is disabled after a while for any given reason? Any energy efficiency related staff could be that it disables the controller SATA card? Anyone had any problem similar with a secondary controller SATA card? Thanks

First of all, thanks for the reply!! Is there any guide for Arc Loader? It does not look that there is a guide here in the forums... Talking about the Arc Loader, what is the procedure to follow when you want to update to a new version? AFAIK, with DSM 7+ (which didn't happen with Jun's loader) you have to recreate the USB again to be able to load DSM, right? Please, what is your step by step procedure to follow. Thanks

It looks like there is not link to ark with my processor and instead uses undefined? Weird... Any help? Thanks

After reading a lot, I think that I am totally wrong assuming that the extra.lzma would work with my system. I was expecting it would, because the same NICs were shared in both rigs (and was the only reason to use the extra.lzma), but I guess much more drivers should be compatible with my rig in order to make it work. I was thinking about my new processor i3 12100 has a UHD 730 graphics, maybe this could make it fail entirely at boot, along with other things. Or do you think guys, that the graphics processor does not have anything do do with having problems at booting but just when transcoding and nothing more... Can anyone let me know what could be the next step to proceed and make my new system to work? It should be great to have documented a reference of an updated current build from an old system, as it would help others too. Thanks guys

Are there any Driver extension jun 1.04b for DSM6.2.3 for 918+? My new hardware is: h610m-itx/ac motheboard (NIC is i219V) with a i3 12100 processor (UHD 730) Link to my question thread:

Links are dead!! Can anyone please share all the 08_syno/std/recovery for ds918+? Thank you very much in advance!! EDIT: nevermind, I was trying to find it for DSM 6.2.3!!

Hello guys, I need your help. I was using a xpenology build since fall of 2018 and was working AMAZING!! The configuration was: - Asrock H370M-ITX/ac (6 SATA, 2 x NIC: i211V and i219V) - i3 8700 - 32Gb DDR4 RAM - SATA card SYBA SI-MPE40125 4 SATA ports -with Marvell 88SE9215 controller-, installed via M.2 e-key to mini pic-e adapter. So with the 6 ports of the motherboard have a total of 10 SATA ports. - 5x8Tb disks - Using Jun's loader 1.04b 918+ BAREMETAL (with extra.lzma for the second NIC) with DSM 6.2.3 I was completely in love with the build, I thought it was almost perfect for my needs (well, never had enough space ). I was always updating until I couldn't do it more in DSM 6.2.3. It was working so well, that even that I was tempted numerous of times to update to DSM 7 (but I was not confident enough), I kept locked to DSM 6.2.3 because I was not sure if there was anything I could do better with DSM 7, at least for my needs, and I wanted to wait until I buy new disks in summer, to do an update to DSM 7.2. It was working rock solid almost 24/7 for almost 5.5 years!! Sadly, a couple of weeks ago, the motherboard died (with no explanation), and there was no way to find a motherboard to replace it, at least in this form factor. So I had to find a replacement board (with obviously a new processor) to match the needs (and seriously there are really few possibilities, the world shortage is huge, at least in mini-ITX boards), thinking I would be able to make it work straight away with my build with few changes in the config, so I found the following: - Asrock H610M-ITX/AC (4 SATA, 1 x NIC: i219V) - i3 12100 - Same 32GB DDR4 RAM Using the mentioned SYBA card in the M.2 port, still have 8 SATA ports, and is fine for my needs even losing 2 ports, as have just 5 disks. I can see the disks in the EFI BIOS, so are being recognised, which is great as was one of my fears. So, I changed the grub.cfg of the USB with the Jun's loader of the previous configuration, and modified: - The mac address of my NIC, I got the mac address of the new board via USB with Ubuntu LTS (NOTE ABOUT MAC ADDRESSES IN THE PREVIOUS BUILD: "strangely" I was using in the previous build a "well known" mac addresses with a serial number that you can find in the forum, and it was working beautifully even with transcoding, and I don't think I was using the real mac addresses of the board!! Don't remember seriously... unless I changed the NIC mac addresses permanently to these ones, which I am not sure if it is even possible). - The SataPortMap configuration to 44 (means first 4 ports of 1st controller and first 4 ports of 2nd controller), instead the previous 64 As the previous build was using the extra.lzma for the i219V, I chose this motherboard because it had the same NIC, and I thought it would work straight away. So I booted the computer with the USB, and I am not not able to run the previous DSM installation nor able to find any Synology device with the web or the Synology assistant. Not sure if I have to use the reinstall option of the Jun's loader because of the new configuration (or is just if you want to install again DSM), and just used it with the default option of the loader (the first BAREMETAL one). I have the feeling that maybe the NIC is not being recognised and I don't understand why. Being headless I don't see any message when connected to my monitor via DisplayPort about if the loader is having any problem. Not sure what to do nor debug. Don't remember if I changed any BIOS settings in the past that maybe could matter. Just changed the hot plug of the SATA and few things more... Obviously, as I want to recover all the disks and see that everything is correct, I would like to avoid installing the DSM 7 for now (as I don't want to risk the existent disks and I have no other backups), and would love to first having DSM 6.2.3 working, and not have any problem afterwards to updated. But now I just want to see everything is correct and the DSM 6.2.3. Can anyone help me with that? I am very desperate and I don't know what more to do. Find attached the grub.cfg just in case there is any error. Thank you very much. grub.cfg

Should be great to have a mechanism to be able to update your USB stick without have to do the burning image process again and again, but just updating, once connected to internet. That sounds great!!

Do you realise this is exactly what I put in the third post, right?

Where, in this README, appears how to update to a new version of DSM?? Specially when the new version requires a change in the kernel (like from 7.1.1 to 7.2). I am assuming you have already install the 7.1.1 and you just want to UPDATE to 7.2. Explain, where in that README? Because the previous question is the ONLY thing I am asking (updating), I know how the process of installation works, and I am not asking about how to install it from scratch. I know how to do it. Well, it is being for me since 2016, that I am using xpenology, with total success and ZERO problems. Before, as Jun's loader, was a MONOLITHIC loader, there was not a problem to update until 6.2.4 (I am still in DSM 6.2.3). I never had a problem updating.