Hi,
it looks like both DGS-1100-08 do not have a proper LAG configuration, hence they do not treat the links that comprise the LAG as a single logical link (with a multiple of the bandwidth of a single link) but as individual links. This means that any ethernet frame received from one of these "LAG-wanted" links, that is a broadcast or a multicast or that is destined for an unknown MAC address is flooded to any other port (this is standard switch behaviour), unfortunately including the other "LAG-wanted" links (this must not happen, if the LAG were configured properly).
As long as only one DGS-1100-08 is connected, no loop is formed, because DGS-1210-10 seems to have a proper (local) configuration of its LAG end and would not send broadcast/multicast/unknown frames received from one LAG link back down another LAG link. Only if the second DGS-1100-08 is connected, a loop is formed between both DGS-1100-08, because the second DGS-1100-08 reveals the same misconfiguration and hence provides the "frame reflector" (this way "closing" the loop) that was so far missing in your scenario with a single DGS-1100-08.
I assume STP is switched off? You could (should!) switch it on. This would help to prevent loops, especially those that happen by accidentially connecting switch ports that shouldn't be connected. STP would also break your present loop by blocking all "LAG wanted" links except one in each "wanted LAG". While good for switch sanity this is not what you want, because this results in singly linked DGS-1100-08 switches - equivalent to having no LAGs (#3, #4) configured at all.
Hence, check your LAG configuration: Did you configure it the same way at both ends (DGS-1100-08 <-- LAG --> DGS-1210-10) of the LAG ("static")? Are all links that comprise the LAG configured the same way, e.g. for the same VLAN or set of VLANs (if VLAN trunk)? This is what the manual says to "port trunk groups" (LAGs):
"All of the ports in the group must be members of the same VLAN, and their STP status, static multicast, traffic control; traffic segmentation and 802.1p default priority configurations must be identical."
PT