Maybe you (fvdw) should know an EBD is not 'symmetric', like other 2 disk Lacie devices. On a 2Big or D2 network both disks are equal, regarding partition table and so on. The EBD is not. It has one 'classical' disk, and a 2nd, unpartitioned one. The sda2 of the bootdisk is expanded with the 2nd disk in a linear raid volume.
As you could see in the thread, the bootloader only loads it's kernel from device 1, and not from device 0. So the bootscript is designed to enforce this behaviour. Further, in the EBD update kernel, you can see first sdb is found, and then sda. So I guess indeed the devicenames are swapped.
A last note, it's not clear to me which box this actually is. The EBD in the wiki has an EdminiV2 board with a 2nd sata port. This one is different. And the bootloader says it's a 'D2 Next'. So maybe it is
a D2, but AFAIK that box is symmetric, so the bootloader should be able to boot from both disks.
The fact the this arm-arch kernel won't work is simple it doesn't support this board.
Which kernel do you mean?
@heavyarms: Clearly the webserver is running. Else it couldn't tell you the system is still booting. On other Lacie's a factory reset on this point can help.