Synology USB DOM

[thepadol]

If I understood correctly Xpenology bootloader on USB basically mimics the original Synology USB DOM which itself is tied to the Synology hardware. Xpenology is both a bootloader as well as a "layer" so that the DSM is unaware that it is running on non Synology hardware.

 

I'm trying to resolve or rather recover a Synology box and trying to see if Xpenology can help.  The Synology bios ROM was probably corrupt but I managed to work on enough so that it seems to be ok, it will access the USB DOM.  But now it seems the USB DOM is also partially corrupt and I can't seem to find a way to recover it.  I also have all the original drives removed to avoid any further corruption.

 

Presumably I should simply clone one of the disk and see what happens since in theory if the bios is ok, the USB DOM boots, Grub works, then it should try to start the disk which then would attempt a full recovery.

 

I was trying to understand though, if an Xpenology created drive is structured the same way and is identical to a drive created in the real Synology box?  Or is the partition and images customized by Xpenology.  I would think the customizations remain in the Xpenology USB.

 

It's a big Synology box - DS3611xs so I'd hate to not be able to use the drive bays.

 

Suggestions? or am on the wrong path here.

[Peter Suh]

bromolow DS3611xs has finally entered EOS with DSM 6.2.4.
https://archive.synology.com/download/Os/DSM/6.2.4-25556-7

 

rr fully supports DSM 6.2.4,
but bromolow only supports up to DS3615xs,
but it seems they recently discontinued bromolow support.

 

My mshell supports bromolow DS3615xs but not DSM 6.2.

 

Are you trying to create a USB stick bootloader using XPE to boot DS3611xs?