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.
Question
ed_co
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
Edited by ed_coLink to comment
Share on other sites
10 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.