bulisor007 Posted January 2, 2021 Share #1 Posted January 2, 2021 I'm having a failed DS1815+ unit (CPU died most likely) and I was wondering if it can be transformed into an expansion unit like DX517. The PSU is still working and I don't believe that the electronic part in an expansion unit is that complex so I may repurpose the failed unit to an expansion unit. Any thoughts? Quote Link to comment Share on other sites More sharing options...
flyride Posted January 2, 2021 Share #2 Posted January 2, 2021 IMHO you would have to scrap the 1815 board and somehow interface the backplane to an existing multi-port eSATA controller? So you would also need a donor expansion unit. When I have taken apart lower-end Syno units, the backplane cable to the main board was not something I recognized. Probably more trouble than it's worth, especially with the existence of cases like U-NAS 810a etc. Quote Link to comment Share on other sites More sharing options...
jamkiki72 Posted January 2, 2021 Share #3 Posted January 2, 2021 Tried this? 1 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted January 2, 2021 Share #4 Posted January 2, 2021 8 hours ago, bulisor007 said: was wondering if it can be transformed into an expansion unit like DX517 afaik these units use sata multiplexer and a special (synology) firmware, dsm will not work with a multiplexer, only when its a specific chip and has the right firmware even with xpenology we cant use multiplexer as there was no one with the know how and the need to do it synology introduced this ~2012 (?) the best link about details i know is this https://community.synology.com/enu/forum/17/post/54396 Quote Link to comment Share on other sites More sharing options...
bulisor007 Posted January 4, 2021 Author Share #5 Posted January 4, 2021 I've tried the resistor workaround, without any luck. Currently I'm looking for an USB adapter to be able to read the DOM module and see if that's corrupted or not - this will help me understand if the issue is with the boot disk or with the CPU itself. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted January 4, 2021 Share #6 Posted January 4, 2021 12 hours ago, bulisor007 said: Currently I'm looking for an USB adapter to be able to read the DOM module thr pinout look like a normal usb2 onboard thats on most systemboards, you could try it in a normal system if there is enough room to plugin it in (as its not mechanical coded keep a eye on the small triangle, thats the one) just check it against the manual of your systemboard to compare it Quote Link to comment Share on other sites More sharing options...
bulisor007 Posted January 5, 2021 Author Share #7 Posted January 5, 2021 That's true but the pitch of the pins is smaller than the standard USB layout so you can't plug it on a standard socket without an adapter. Quote Link to comment Share on other sites More sharing options...
pocopico Posted January 5, 2021 Share #8 Posted January 5, 2021 If i understand correctly, you could just cut a spare micro USB wire on the micro usb end and keep the USB end. Check wires with a multimeter and find the pinout and connect the right wires to the board. It should not be that hard. Quote Link to comment Share on other sites More sharing options...
bulisor007 Posted January 6, 2021 Author Share #9 Posted January 6, 2021 I've managed to read the DSM boot disk with the use of 4 breadboard jumper wires. The strange thing is that even though the disk seems to be with no errors and the first partition is marked as bootable, I was not able to boot my computer with that disk. I don't know if this is normal or not, I was still expecting to see some boot messages on the screen then to stop the process with an error message that the hardware is not Synology. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted January 6, 2021 Share #10 Posted January 6, 2021 9 hours ago, bulisor007 said: I was not able to boot my computer with that disk. I don't know if this is normal or not, I was still expecting to see some boot messages on the screen then to stop the process with an error message that the hardware is not Synology. the messages you see with xpenology are from juns loader, you might see nothing with a normal original loader, you might see something with a serial console and even if it boots it might be a short process and might stop shortly after starting the kernel and there might never anything to find in network as the nic driver is missing or the protection kicks in because some pci id's are missing (that would be present on the original hardware) imho you cant say that for sure with just that little test i don't know how deep you looked into the atom cpu (intel) desaster, it was a degrading process and even the resistor was only slowing it down, all damage already done could not be reversed and if a cpu started to have problems there was slight chance it might come up again with the fix but in that degraded state its likely to fail later mine never woke up again and the whole system board was useless as the cpu could not be changed (new system has a socket again) Quote Link to comment Share on other sites More sharing options...
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.