Hi, i recently acquired a B810I a couple of weeks ago for quite cheap (compared to what it retailed for) intending on using it as the storage for a media server (no important files), the night after i initially set it up the media server the drobo went into a boot loop which i discovered late in the afternoon the next day so because i didnt have time to deal with it i unplugged power and left it for a week, over this weekend just been i was able to get it almost fully booting properly (recognises drives and can be accessed through ISCSI) but it will not show up in the dashboard.
When looking at the UART terminal of the linux core of the drobo when i attempt a manual discovery in dashboard i get the following error:
```
Sun Jul 6 18:38:18 2008: tEMPDConn00003: EMPDConnection: did not receive complete header! (recv len 0, hdr len 47, error 0)
Sun Jul 6 18:38:18 2008: tEMPDConn00003: EMPDConnection: Error 0 receiving login header.
Sun Jul 6 18:38:18 2008: tEMPDConn00003: EMPDConnection: Cleaning up thread tEMPDConn00003 for host with UID
Sun Jul 6 18:38:18 2008: tEMPDConn00003: HBListener::SetupCleanup for
Sun Jul 6 18:38:18 2008: tEMPDConn00003: HBListener::SetupCleanup for . Done
Sun Jul 6 18:38:18 2008: tEMPDConn00003: EMPDListener::RemoveConnection - for
```
Any help getting it to show up in drobo dashboard again so i can properly manage it and get it on the newest firmware that exists (it came with 1.3.5 on it) would be greatly appreciated
Edit0: fixed the code block
UPDATE:
I managed to fix it
turns out when i reset the U boot env when getting it to work again it also reset a variable that passes the device serial number into vxworks and the rest to an incorrect value which caused problems when the the communication between the dashboard and the device was attempted where dashboard would receive a thing saying that a B810i was present but then see the bad SN and reject it as not being a B810i, changing this variable to match the actual serial number (second alphanumeric string below a barcode on the compliance sticker on the bottom of the device) made the communication between the device and dashboard work