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:
Afterwards I would expect the EFI to boot GRUB from the internal storage. However, I am receiving a mapping error
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:
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:
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.
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:
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:map: Cannot find required map name.
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:
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.