asheenlevrai

Doing this right now

I made a mistake. Actually I DO get an error message mentioning the system shut down improperly after a hard reset (required because the machine became unresponsive). I guess this tells me that DSM is was still running (system didn't freeze) but somehow lost internet connection, right?

Thanks. What should I do in order to be able to use this quad-port NIC in a different system? The 2nd unit I purchased, I mean... Best, -a-

Completed 21 passes. 0 errors. @flyride how should I go about testing the resat of the hardware? Tx -a-

I am currently running MemTest86+ v5.01 from SystemRescue. I have no experience with that so I am not sure how to interpret the results. So far, 2 passes, 0 errors. I don't know what that means (how many passes with no errors is considered significant?) but at least it's not a bad sign. CPU temp during the test: 52-55°c EDIT: at least 8 passes are required apparently

Thank you very much for your help I understand that. Makes sense. Thanks You're right. Memory should be checked I guess How? (See below). I don't overclock. How would you suggest I monitor/log system and CPU cooling. I have alerts set up in the BIOS for when the CPU goes above 80°c but I never heard that beep. Or at least I wasn't next to the machine to hear it. Do you mean most PCs? Or most DSM systems? I haven't. I will. How would you recommend I do that? Using something like SystemRescue or UltimateBootCD, for instance? Yes I use real PCI x4 slots (or a x16 slot running at x4). No slots that would run at lower speed when another AIC is present in a different slot sharing the same PCI lanes. I didn't use extra.lzma in any of my machines. I started with machineC and chose 918+ because I had a haswell CPU available. Then I went on with machineA & B and had to use 3617xs since the CPU wouldn't support 918+. For machineD, I actually tried both (as I mentioned in the OP). This one is for testing only right now. Anyway, it seems like for some obscure reason this quad-port NIC I need to use doesn't seem to work on any hardware other than machineC, which is very surprising and inconvenient to me. It doesn't seem to make a whole lot of sense, right? Once again, thank you very much for your highly valuable help. I appreciate it. Best, -a-

Yes @flyride I didn't pay attention. My bad... 🙏

Hi In order to explain my problem more easily, let me list here the xpen machines I use for reference: machineA (shutdown issue reported here) DS3617xs 1.03b MB : ga-z68ap-d3 rev2.0 (onboard NIC is dead and disabled in BIOS) CPU : i5 3470 RAM : 2x 2GB DDR3 1066MHz NIC : GbE AIC based on Broadcom BCM95722A2202G sATA : 5ports sATA3 AIC based on jmb585 (2 disks on MB sATA3 ports, 5 disks on AIC) machineB (instability issue reported here) DS3617xs 1.03b MB : Asus p8z77-m (onboard NIC disabled in BIOS) CPU : i7 3770k RAM : 4x 4GB DDR3 1066MHz NIC : PCIe2.0 x4 quad-port GbE NIC based on Realtek RTL8111G sATA : 5ports sATA3 AIC based on jmb585 (2 disks on MB sATA3 ports, 4 disks on AIC) machineC (works OK) DS918+ 1.04b MB : ga-z87-hd3 CPU : i7 4770s RAM : 2x 2GB DDR3 1333MHz NIC : onboard GbE sATA : 5ports sATA3 AIC based on jmb585 (6 disks on MB sATA3 ports, 2 disks on AIC) machineD (for testing, OK) DS918+ 1.04b MB : optiplex 9020 sff (onboard NIC disabled in BIOS. i217-LM Doesn't work in windows 10 : Error 10. Driver Issue) CPU : i7 4770 RAM : 1x 4GB DDR3 1600MHz NIC : random GbE AIC (works) or PCIe2.0 x4 quad-port GbE NIC based on Realtek RTL8111G (doesn't) sATA : onboard (1 disk) After installing and configuring machineB I noticed I had stability issues. The machine would randomly become unresponsive and Synology Assistant would no longer detect it. Following a hard reboot to revive it, there was no message mentioning it was shutdown improperly, which has me thinking the system froze rather than just lost Ethernet connection. First, I thought maybe it was due to the bond connection (LACP) so I disabled that and started testing with only 1 port (without LACP). The problems remain when using only 1 port at a time. If I put a random GbE AIC or use the onboard GbE, it seems to work alright. Then, I needed to test the quad-port GbE AIC. I thus tried it - actually tried them, since I have 2 units - in windows10 and they seem to work alright. Then I tried using this card (using only 1 port) in machineA, machineC or when installing machineD. This card won't work in any of these!?! For machineA and machineC, I know DSM starts up but doesn't get any Ethernet connectivity since a hard reboot leads to a report of improper shutdown after I put back the original GbE NIC. For machineD, I couldn't install using this card (I tried both ds3617xs 1.03b and ds918+ 1.04b). I tried installing with a random GbE NIC and then replace it with the quad-port NIC, but again, it doesn't work (no Ethernet connectivity). Declaring mac1 to mac4 in grub.cfg seems to have no effect functionally for the tests I am currently running. I don't understand how on earth I am able to use this quad-port card on machineB. What is different with this HW compared to the 3 other rigs? Thank you very much in advance for your help. Best, -a-

I figured this was the origin of the problem for the emigration install. I shouldn't use this file for DSM6.2.3-25426-3 but rather the install file for DSM6.2.3-25426 (no update3) https://archive.synology.com/download/Os/DSM/6.2.3-25426 -> DSM_DS3615xs_25426.pat 🤪 Then -> no error 13 -> migration OK

Are you talking about Jun? @jun? Does that mean XPEnology is more or less a dead end now? I'm asking because I just found out about it and I am currently switching most of my older DSes to Xpen rigs. I might reconsider if there is no way forward for Xpen. I hope the source code for the loader is released if this is the case. This is a great project. Best, -a-

After reading this, I wondered if the USB medium could be the source of the error 13. Thus I tried burning the loader image on an USB dongle that I know previously worked in another Xpen rig. -> I still got the error 13, though. Now, for my 3617xs rigs I used the serial generator from here. It worked OK. I'm wondering if the version for 3615xs might return invalid serials or something and maybe this leads to error 13? Tx -a-

Hi Did you solve your problem? Would you consider burning a new USB loader and see if your rig appears in Synology Assistant then? Maybe as "migratable" or something... Good luck -a-

Interesting... Does that mean that XPEnology is intentionally staying 1 version behind the current DSM version? For "political" reasons or something? (I'd be totally comfortable with this, just curious...) Thanks -a-

Could my problem be caused by something else than a driver issue with the NIC? Like a BIOS setting or something? Thoughts? Thank you very much in advance for your help. Best, -a-

Thanks I was careful not to forget 0x

vid is 058F Should I have rather put 058f into grub.cfg? Could the capital F be misinterpreted?

I did all that. I still get Error 13 even after re-making the USB dongle

Hi I found out the USB key needs to be MBR. If it's GPT, then burning the image with Win32 Disk Imager fails Best, -a-

Thanks @flyride I paid attention using the right vid & pid when making the USB loader for 3615xs but I must have made a mistake somewhere I guess. I'll try fixing that by pressing C at boot and re-entering vid and pid. If it still fails, I'll re-make the dongle.

Hi @flyride I'm currently trying to migrate from 3717xs to 3615xs in order to see if this solves my NIC problems on this rig (as suggested by @nemesis122 on the 3rd post of this thread). I made a new USB loader using 1.03b for 3615xs (I assumed it would be better than using 1.02b and DSM 6.1.x, right?) I rebooted using this USB dongle and Synology Assistant detects the rig as migratable. Then I start the migration process by providing the .pat file I could find here: https://archive.synology.com/download/Os/DSM/6.2.3-25426-3 -> synology_bromolow_3615xs.pat I get an error 13 (file corrupted). I guess that's a noob mistake but I cannot figure out what I'm doing wrong... Please help Best, -a-

I borrowed the following NIC from a friend: https://sunsetmicro.com/intel-pci-express-ethernet-network-adapter-desktop-single-port-e25869-002-e25871-002-e46981-003-cpu-e25869-expi9301ctblk/ (Intel CT E25869 or whatever) Again, the problem remains (shutdown and reboot won't work). What do you think @IG-88? I guess this is no longer a problem with the driver of the NIC, right? Best, -a-

Hey @randylin I'm sorry I don't have any answer but rather a question. Do you actually need any GPU? Could you boot off the 3800xt without the GT710?

Hi It seems like I cannot edit the title of a thread afterwards. Is there any way to mark a thread as solved? Tx -a-

Have a look at this chart: Then define what hardware you will need according to your needs. If you need to purchase anything, also consider aftermarket prices, sometimes they don't make any sense... I guess the 1st line (loader 1.04b - DS918+) is the safest bet. so Haswell CPU and above. Now pay attention since I am not sure whether very recent CPUs are supported at all. I believe I read somewhere that Coffee lake CPU can also be tricky in some ways. Maybe search for that if you plan on using one. Then adapt this old tutorial to your setup (it's pretty easy actually). Classic noob mistake: make sure to provide the appropriate .pat file when installing DSM onto your setup. XPEnology doesn't support the most recent version of DSM. Good luck

AFAIU, Synology Photos runs on DSM 7. Currently XPEnology supports up to DSM 6.2.3 AFAIU, in order to run Synology photos, we will need to wait for a new loader to come up, allowing the upgrade to DSM 7. For now, I believe you should be able to run Synology Moments on DSM 6.2.3 Best, -a-