Solved Unleashed 1.1.3 server crash at startup

[N-kay]

• Modpack is Unleashed V1.1.3
• Host is nitrado.de
• All included mods activated, except for BoP

I've been hosting a private server for me and a friend for over an month now, and today, this problem showed up in the console when trying to start the server.

2013-10-05 10:11:17 [INFO] Starting Minecraft server on 85.190.168.223:25565
2013-10-05 10:11:38 [INFO] Preparing level "world"
2013-10-05 10:11:40 [INFO] Preparing start region for level 0
2013-10-05 10:11:41 [INFO] Preparing spawn area: 56%
2013-10-05 10:11:42 [INFO] Done (4.143s)! For help, type "help" or "?"
2013-10-05 10:11:42 [INFO] Starting GS4 status listener
2013-10-05 10:11:42 [INFO] Query running on 85.190.168.223:25565
2013-10-05 10:11:42 [INFO] Damage Indicators Mod v.2.7.0.1 is out of date. v.2.9.0.9 is now available.
2013-10-05 10:11:47 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
2013-10-05 10:12:01 [SEVERE] Encountered an unexpected exception ReportedException
net.minecraft.util.ReportedException: Ticking tile entity
    at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:660)
    at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:275)
    at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:573)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:470)
    at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:573)
Caused by: java.util.ConcurrentModificationException
    at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
    at java.util.HashMap$ValueIterator.next(Unknown Source)
    at buildcraft.transport.PipeTransportItems.moveSolids(PipeTransportItems.java:269)
    at buildcraft.transport.PipeTransportItems.updateEntity(PipeTransportItems.java:233)
    at buildcraft.transport.Pipe.updateEntity(Pipe.java:174)
    at buildcraft.transport.TileGenericPipe.func_70316_g(TileGenericPipe.java:189)
    at net.minecraft.world.World.func_72939_s(World.java:2202)
    at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:546)
    at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:654)
    ... 4 more
2013-10-05 10:12:01 [SEVERE] This crash report has been saved to: /games/ni247922_1/ftproot/minecraftftb/./crash-reports/crash-2013-10-05_10.12.01-server.txt

http://pastebin.com/aDk114NE

Here's the full crash-report. I don't know much about these reports, but it seems like the crash is caused by Logistics Pipes (wich I've never used before until yesterday), to be able to remote-request stuff out of my ME system into an ender chest.( unlimited Range)
It worked, but after I left the server, I wasn't able to connect anymore, and a restart caused this error to appear.

Could I just remove the mod from the server to prevent the error? Or is there a better solution?

 

[lavarthan]

It does appear to be a logistics pipe causing this. Backup your server save and configs to a safe location. Now that you've done that use MCEdit to remove the block at 'Block location: World: (-222,75,505)' According to your log this is the ticking block and should allow you to use the world once removed. If you place down another logistics pipe it might cause this error again. Check your setup and see if there is another way to do it. Also check to see if there is an update for Logistics Pipes for 1.5.2

 

[N-kay]

Alright, thanks for the tip, I didn't know you could edit non-vanilla maps in MCEdit. Altough I've never used it before, I was able to remove the block, or rather a couple of blocks around it, too, just to be sure. The strange thing is, there were absolutely no LogisticsPipes, but some transport pipes and an item tesseract. I can't tell for sure what block caused the error, because I only saw them as purple "Future blocks" in MCEdit, because the weren't vanilla, and because I removed a couple at once.