Question DS412+ not booting: serial console shows EFI Internal Shell missing boot devices, but EFI partition on internal storage seems intact

Currently reading
Question DS412+ not booting: serial console shows EFI Internal Shell missing boot devices, but EFI partition on internal storage seems intact

Hi!

@Notatech I am very glad to hear that!
That confirmed that it is a very small replacement to make the Diskstation work again.
Have fun with the repaired device :)

Sebastian
 
Last edited:
BOOT FLASH DRIVE DIED. SEE IT ALL THE TIME. JUST REPLACE THE USBEST OR PHISON CONOTRLLER CHIP ON FLASH DRIVE. DONE! AS WE FIX THESE IN OUR NORMAL SERVICE.
-- post merged: --

If I was Jesus. I saved you. I posted this fix on a few forums long ago. And it made it here now. As we do so many fixes on these on for 6 years now. Even this problem. Its good you made an image of the drive. Also you don't even need anything special to read the drive. Not even a RP box. It has a 10pin connector on it. But only 4 pins are used. And those 4 pins are USB. That's correct. And direct to pc connectable with putty. No different then a regular usb thumb drive. In fact the module is called eDOM USB FLASH DRIVE, or eDOM. Disk on a Module. Other companies use them alot in custom image booting a board. Mainly manufacturing systems in industry uses them. But there is sad news in all this. These controllers are only designed to last about 10 years on average. As they can only handle so many 100,000's read writes. So all NAS PLUS models from 2013 and prior are due to die from this problem.
 
BOOT FLASH DRIVE DIED. SEE IT ALL THE TIME. JUST REPLACE THE USBEST OR PHISON CONOTRLLER CHIP ON FLASH DRIVE. DONE! AS WE FIX THESE IN OUR NORMAL SERVICE.
-- post merged: --

If I was Jesus. I saved you. I posted this fix on a few forums long ago. And it made it here now. As we do so many fixes on these on for 6 years now. Even this problem. Its good you made an image of the drive. Also you don't even need anything special to read the drive. Not even a RP box. It has a 10pin connector on it. But only 4 pins are used. And those 4 pins are USB. That's correct. And direct to pc connectable with putty. No different then a regular usb thumb drive. In fact the module is called eDOM USB FLASH DRIVE, or eDOM. Disk on a Module. Other companies use them alot in custom image booting a board. Mainly manufacturing systems in industry uses them. But there is sad news in all this. These controllers are only designed to last about 10 years on average. As they can only handle so many 100,000's read writes. So all NAS PLUS models from 2013 and prior are due to die from this problem.
Thanks for all your input Elextrixman! Didn't know the fix was posted elsewhere.
So, just to be clear, replacing the USBEST UT165 chip should let the DS412+ last another 10 years (or thereabouts depending on read/writes) if nothing else goes wrong, correct?
Or do I need to replace the Samsung K9F1G08U0C-PCB0 chip also because that will fail from a certain amount of read/writes?
 
Last edited:
Thanks for all your input Elextrixman! Didn't know the fix was posted elsewhere.
So, just to be clear, replacing the USBEST UT165 chip should let the DS412+ last another 10 years (or thereabouts depending on read/writes) if nothing else goes wrong, correct?
Or do I need to replace the Samsung K9F1G08U0C-PCB0 chip also because that will fail from a certain amount of read/writes?
No that's all that's needed. The only thing left to do. Consider a power supply. These are only rated for 7 years It may run well and look good. But its time has come due. And with these you mainly don't want to wait. As it starts sending bursts and noise on the line. Get only a good PGB, or Delta. Watch out on ebay. 90% are fake ones. The supply should be heavy if its a good one, as it has better filtering than cheap Chinese ones. I did a write on those to look for on all NAS's below in link. These are all internal. But external is mentioned at the end.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

View: https://www.reddit.com/r/synology_service/comments/11g8qem/watch_what_power_supply_you_buy_online_95_are_all/
 
No that's all that's needed. The only thing left to do. Consider a power supply. These are only rated for 7 years It may run well and look good. But its time has come due. And with these you mainly don't want to wait. As it starts sending bursts and noise on the line. Get only a good PGB, or Delta. Watch out on ebay. 90% are fake ones. The supply should be heavy if its a good one, as it has better filtering than cheap Chinese ones. I did a write on those to look for on all NAS's below in link. These are all internal. But external is mentioned at the end.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

View: https://www.reddit.com/r/synology_service/comments/11g8qem/watch_what_power_supply_you_buy_online_95_are_all/

Thanks again Elextrixman! Will certainly look around for a replacement power supply. Actually wondered if that could be part of the problem causing the chip failure due to fluctuation. Thanks for all the info on it.
 
Thanks again Elextrixman! Will certainly look around for a replacement power supply. Actually wondered if that could be part of the problem causing the chip failure due to fluctuation. Thanks for all the info on it.
No problem. And could be. Anything is possible when firmware corruption occurs. Not to brag or anything. But I am the only service center for Synology in the USA. And I think if I can save a NAS from the trash heap over such a simple thing. Its worth it. I have saved $1000's for users on that forum in Reddit. Just by doing simple things. Even a coin cell can save 100's of NAS's. And if you haven't changed yours yet. Also consider it when you get that supply. Coin cell is not just a simple date and time battery. But also holds the last boot info. So if your NAS didn't boot the last time due to software or the OS boot. It holds it in firm. And locks you out. It won't power on again after that until the battery is removed. There are many saves there I did on reddit too for that one. Also did a write on it there too. In fact any older unit prior to about 2014. Should have a 10 year maintenance schedule if you plan on keeping the NAS.. Only applies to PLUS units. As non-plus units are another breed. But for those, and like yours, you should change 1) eDOM controller, 2) PSU, 3) Fans, 4) Coin Cell battery. With those 4 changes. It will last another 10 years. Obviously the controller chip on the eDOM board your changed is alot tougher for many out there. Especially shaky hands people. LOL! There are even some models like the 1812+ and 1813+ that also gets a few caps changed in that maintenance, as they burn the PCB about 7-10 years in. We call those "The Flame Boxes" here. And for good reason. Literally. But for yours. Its only those 4 needed. And the PSU is the only real expensive item in that list. Enjoy!
 
BOOT FLASH DRIVE DIED. SEE IT ALL THE TIME. JUST REPLACE THE USBEST OR PHISON CONOTRLLER CHIP ON FLASH DRIVE. DONE! AS WE FIX THESE IN OUR NORMAL SERVICE.
-- post merged: --

If I was Jesus. I saved you. I posted this fix on a few forums long ago. And it made it here now. As we do so many fixes on these on for 6 years now. Even this problem. Its good you made an image of the drive. Also you don't even need anything special to read the drive. Not even a RP box. It has a 10pin connector on it. But only 4 pins are used. And those 4 pins are USB. That's correct. And direct to pc connectable with putty. No different then a regular usb thumb drive. In fact the module is called eDOM USB FLASH DRIVE, or eDOM. Disk on a Module. Other companies use them alot in custom image booting a board. Mainly manufacturing systems in industry uses them. But there is sad news in all this. These controllers are only designed to last about 10 years on average. As they can only handle so many 100,000's read writes. So all NAS PLUS models from 2013 and prior are due to die from this problem.
Hi.

I have a DS2413+ and I believe my eDOM died after a power outage. Do you sell these modules or know someone that do?

In advance, thanks.

-WonderStivi
 
Hi.

I have a DS2413+ and I believe my eDOM died after a power outage. Do you sell these modules or know someone that do?

In advance, thanks.

-WonderStivi
This isn't a marketplace. You can use web link in the member's profile, that you were replying to, to get to their site: there's no relationship between SynoForum and the member's site.

Good luck with getting your NAS fixed.
 
This isn't a marketplace. You can use web link in the member's profile, that you were replying to, to get to their site: there's no relationship between SynoForum and the member's site.

Good luck with getting your NAS fixed.
Sorry, I did contact him when I found he had contact details on his profile.

Didn't intend to break the forum rules, and my question was in frustration.
 
Last edited:
Hi.

I have a DS2413+ and I believe my eDOM died after a power outage. Do you sell these modules or know someone that do?

In advance, thanks.

-WonderStivi
Needs a eDom. Or if you are good at soldering, just replace the controller. I fix many of these in my shop.
-- post merged: --

Hi.

I have a DS2413+ and I believe my eDOM died after a power outage. Do you sell these modules or know someone that do?

In advance, thanks.

-WonderStivi
Needs a eDom. Or if you are good at soldering, just replace the controller. I fix many of these in my shop. But need the old one to copy the firmware over.
-- post merged: --

Hey everyone

I am having issues booting my DS412+ that appeared after I had shut it down for just a while to reposition the unit. The unit does start, the fans work fine, but I am not getting any startup sound, only the blue LED blinking forever. The disks do not even spin up anymore and the reset button is not responding at all.

Since this unit has always been very reliable behind my UPS, I started looking for what was wrong. Using the serial port, I was able to see this screen as one would expect:

View attachment 2040

Afterwards I would expect the EFI to boot GRUB from the internal storage. However, I am receiving a mapping error

thus being redirected to the EFI Internal Shell:

View attachment 2041

I then replaced the CR1220 battery inside the device just to be sure, but to no avail. I then suspected the mass storage device to be broken or containing corrupt data.

Unfortunately, the EFI is said to have been modified in a way to not allow any other USB boot device (than the onboard USB DOM) to even show up in the list of boot devices, so I cannot just try booting from a flash drive.

I then took a look at the data on the USB DOM, where I would expect the EFI boot partition to reside:

View attachment 2042

The partition looks like an ordinary EFI partition and appears to contain the boot loader. It should work.

The EFI also looks like it still contains the configuration that Synology programmed into it:

Code:
Variable NV+RT+BS 'Efi:Boot0000' DataSize = 58
  00000000: 01 00 00 00 2C 00 45 00-46 00 49 00 20 00 49 00  *....,.E.F.I. .I.*
  00000010: 6E 00 74 00 65 00 72 00-6E 00 61 00 6C 00 20 00  *n.t.e.r.n.a.l. .*
  00000020: 53 00 68 00 65 00 6C 00-6C 00 00 00 04 07 14 00  *S.h.e.l.l.......*
  00000030: 01 ED D9 30 D2 38 8A 41-90 D5 C5 61 75 0B F8 0F  *...0.8.A...au...*
  00000040: 04 06 14 00 B7 D6 7A C5-15 05 A8 40 9D 21 55 16  *......z....@.!U.*
  00000050: 52 85 4E 37 7F FF 04 00-                         *R.N7....*
Variable NV+RT+BS 'Efi:Boot0001' DataSize = 40
  00000000: 01 00 00 00 1C 00 45 00-46 00 49 00 20 00 55 00  *......E.F.I. .U.*
  00000010: 53 00 42 00 20 00 44 00-65 00 76 00 69 00 63 00  *S.B. .D.e.v.i.c.*
  00000020: 65 00 00 00 02 01 0C 00-D0 41 03 0A 00 00 00 00  *e........A......*
  00000030: 01 01 06 00 07 1D 03 05-06 00 00 00 7F FF 04 00  *................*
Variable NV+RT+BS 'Efi:Boot0002' DataSize = 9C
  00000000: 01 00 00 00 84 00 53 00-59 00 4E 00 4F 00 4C 00  *......S.Y.N.O.L.*
  00000010: 4F 00 47 00 59 00 00 00-02 01 0C 00 D0 41 03 0A  *O.G.Y........A..*
  00000020: 00 00 00 00 01 01 06 00-07 1D 03 05 06 00 00 00  *................*
  00000030: 04 01 2A 00 01 00 00 00-3F 00 00 00 00 00 00 00  *..*.....?.......*
  00000040: 43 7D 00 00 00 00 00 00-33 3D 06 2B 6F 52 80 46  *C.......3=.+oR.F*
  00000050: B3 44 32 9B 22 9B C2 59-02 02 04 04 3E 00 5C 00  *.D2."..Y....>.\.*
  00000060: 45 00 46 00 49 00 5C 00-62 00 6F 00 6F 00 74 00  *E.F.I.\.b.o.o.t.*
  00000070: 5C 00 53 00 79 00 6E 00-6F 00 42 00 6F 00 6F 00  *\.S.y.n.o.B.o.o.*
  00000080: 74 00 4C 00 6F 00 61 00-64 00 65 00 72 00 2E 00  *t.L.o.a.d.e.r...*
  00000090: 65 00 66 00 69 00 00 00-7F FF 04 00              *e.f.i.......*
Variable NV+RT+BS 'Efi:BootOrder' DataSize = 2
  00000000: 00 00

In conclusion, both EFI and the mass storage device inside the unit look fine, but the EFI cannot find the storage to continue booting from it. Exiting the EFI Internal Shell does not present me with any helpful options, either.

I would greatly appreciate if anyone had a suggestion on how to track down the cause of this behaviour and maybe even how I would go about fixing it. My DS412+ is working fine and I would love to keep it around.
Read the Edom on pc/. If it takles more then 10secs to read. Controller is bad on it. When booting should have 2 options in menu. Yours only shows 1. The default. Syno 2 is the eDom. And not reading it. Replace UT148 and done
 
Hi guys, for those who have problem with USB DOM, i leaving here image of it, dumped from my working DS412+
Use dd tool to flash it back on Linux or Mac.

 
Hi guys, for those who have problem with USB DOM, i leaving here image of it, dumped from my working DS412+
Use dd tool to flash it back on Linux or Mac.

You can use this image. But it has your mac addresses and serial numbers. SO those will have to be edited out and checksum calculated at end. And for windows use HDDRAWCOPY, as that's what we use.
 
Last edited:
I dont care. Can you imagine? )
What I am saying. Is nobody can use this, as the MAC addresses won't register and turn on. Serial is ok. Just the file is useless without a MAC address change. As the bios also has MAC info that must match. Or LAN ports will not work.
-- post merged: --

I dont care. Can you imagine? )
They can use it. But must change MAC addresses to match their system for LAN's to work.
-- post merged: --

I dont care. Can you imagine? )
The file shows your MAC ends in EB:B1 and so on B2B3, B4. And the checksum F8. Those must be changed for this file to work in another system. And checksum recalculated. Serial number too and checksum for that as well. You need a special calc sheet for his we use.
 
Last edited:
Hi,
I am having strange behavior with my DOM (ds412+) . It is not exactly what your described here, maybe someone will have an idea to help me!
Everything was working well, and suddenly NAS was not working: power led blinking blue, but OS not booting. Reading with a serial cable I had no messages at all.
As I had a backup of my DOM and an USB flash drive with modified VID/PID, I flashed my backup to it and plugged it to the front USB, removing internal DOM. In this case everything is working as expected.
So I flashed again my DOM with the backup and restarted the NAS. Still nothing even with serial cable.
But next I found that after 2 minutes, NAS starts as expected: messages are sent to serial port and boot is ok.

So I am wondering whats happening with my DOM to delay the BIOS from starting. Once booted, I can see in the messages that the DOM seems ok:
[ 8.231951] usb 3-1: new high-speed USB device number 2 using ehci-pci [ 8.397700] usb 3-1: New USB device found, idVendor=f400, idProduct=f400, bcdDevice= 1.00 [ 8.405901] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 8.413044] usb 3-1: Product: Diskstation [ 8.417065] usb 3-1: Manufacturer: Synology
It is seen as a high speed device so it is not the USB1 problem you described here.
By the way if I unplug the DOM and then hotplug it, it is immediately recognized by the kernel (no 2 minutes delay as with the bios).

Some read speed show that DOM is not working at USB1 speed:
root@ds412p:~# hdparm -t /dev/sdb /dev/sdb: Timing buffered disk reads: 28 MB in 3.20 seconds = 8.76 MB/sec

But USB flash disk is twice faster:
root@ds412p:~# hdparm -t /dev/sdc /dev/sdc: Timing buffered disk reads: 56 MB in 3.02 seconds = 18.53 MB/sec

Please let me know if you have some ideas about this problem!
Thanks
 
eDOM died. Or that tiny daughter board that plugs into the motherboard. Just need to change the little controller chip on it. The controller is made by USBEST or PHISON. Once in awhile I see SMI controllers on it. See pic of controller chip to change. Or I can do it for you.
 

Attachments

  • c.jpg
    c.jpg
    122.4 KB · Views: 56
Thanks Elextrixman for your fast answer.
How can you say it has died, as I can perfectly see it from linux?
Thanks for offering your help to change the chip; will you do it for free? Otherwise do not pollute this forum.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

  • Question
I received the 1522+ today. It requires at least one disk to be formatted before any operation is...
Replies
6
Views
1,205

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top