Now its funny the order i found these in but the next post i came across when searching how to recover u-boot was back on the synology forum. I think the problem for me would have been finding which chip to clip so im glad i didnt need to go down this route. So for example if you couldnt console you could go direct to the chip. **NOTE** a SOIC clip is a clip that can attach to a rom chip for reading or writing without soldering. So a new search began, how to recover u-boot, hopefully without soldering or using a SOIC clip like the tweakers post suggested. I managed to get the DS booted but typing “save” set me back a few days as it didnt save the image correctly and meant even uboot was not loading back to its prompt. Once consoled i was off to a good start although I had a major pain getting tftp to work in the stock Marvel uboot. The DS414 has the memory fixed to the motherboard unlike the DS415+ **NOTE** if you are watching these thinking the DS414 can be memory upgraded then look at the photos below. I prefer the second video as until you realise which direction to push the inside bar it can be a pain to open. As it turns out all i needed to do was tape the correct 3 UART pins together and slide them through the correct gap in the underside of the case. The console pins are hidden underneath which first lead me to a youtube video on dismantling the box to find the pins. Now Synology have not made this a simple plug and play process. So how do i confirm if uboot is corrupted? I need to console! The important part of this post that should be carefully considered is the sentence “This guide is for all who are sure that u-boot has been corrupted and that there is no other way to recover.” Now this was a scary read as soldering anything has not always worked out positively for me in the past. The first one i found wasn't the most helpful but gave me hope it was fixable. Many unhelpful suggestions on the Synology forums, even from the synology support chat saying the box was “unrecoverable” but a couple of useful posts did start me on the right track. So, where do you start with blue blinking light of death. I'm not knocking facebook marketplace in general as it has been a good way to sell stuff quickly due to the amount of people it reaches in the local area but i will take this as a warning when i next come to sell something. Ebay on the other hand have processes in place to help with disputes like this. The reason i say facebook marketplace was my first mistake was i couldn't find any support on what to do when a buyer returns something that they obviously broke themselves. The device was delivered back at my door with a blue flashing light of death and so the project began to unbrick my DS. At first it seemed like the power had been pulled during an upgrade but now after recovery i have all the logs and can see he had attempted to use disks from an old DS2XX series which seemed to corrupt the boot image. Important: Always use strong password for any account that can access your NAS.This was many hours work so i thought it was a good idea to document properly rather than leave it online as 100 or so different forum posts (in multiple different languages) that i used to solve this tricky problem.Ī special thanks to Bohdi from and Greg Langford from .uk for their assistance.Īfter selling my DS on facebook marketplace (the first mistake) the guy who bought it managed to brick it. So, be responsible of your actions, and do something only when you clearly uderstand the full consequence of your actions.Ī NAS can contains a lot of data, and form a terminal console with administrative right is very easy to mess things up, lose data, or do bad things.įirst thing: you need to enable SSH/Telnet access to your NAS.Īccess the NAS GUI, click "Control Panel", scroll to and click "Terminal & SNMP", Enalbe Telnet and SSH Services, Click Apply. On different model YMMV.ĭisclaimer: with the instructions in this guide you can mess up your NAS, you can loose your data, and do a lot of bad things. So here is a little guide about how to reboot the NAS via the SSH terminal. When my NAS get unresponsive my first solution has always been to power-cycle it, by unplugging the power cable.īut this isn't very nice for a NAS, so I found another solution: reboot the NAS from SSH terminal. The web GUI doesn't works, the network share doesn't works.īut the NAS does still respond to ping, so the network is working. I own a Synology NAS (it's a Ds213j) that every now and then get unresponsive.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |