Exchange 2010 - 2013 Mailbox move - Syncing with no progress (Stalled?)

Question

I'm in the process of moving mailboxes from Exchange 2010 to Exchange 2013, the major of the mailboxes have moved successfully, however I did not anticipate the additional space required by Exchange 2013 and ran out of disk space during the mailbox move,
and some mailboxes did not move successfully.
I have since added additional space but can't seem to get the remaining mailboxes to sync.
I have tried :
Rebooting
Clearing out migration batches and recreating
Stopping and resuming batches.
I see nothing helpful in the Migration log files.
2013-05-20T23:59:57.904Z,14,MigrationServicelet,Information,",827890ff-522d-4c13-9f42-96fbfefb57f4,,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.2724593, job :827890ff-522d-4c13-9f42-96fbfefb57f4:ExchangeLocalMove:Staged:4::SyncStarting:2013-05-17
2:59:12 PM::"
When I download the report for one of the users I see this, but don't know what it means :
The job is currently stalled due to 'Content Indexing' lagging behind on resource 'CiAgeOfLastNotification(Mailbox Database 2065686096)'
For one of the other users the downloaded report only shows :
​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​2013-05-16
2:11:18 PM  '' created move request.
DWW
Additional Info:  I followed the info located here in regards to creating the ContentSubmitters group:
http://www.bullspit.co.uk/2013/04/08/exchange-2013-content-indexing-during-migration/
My mailbox database currently has Content index state: FailedAndSuspended
I only have one database, I am not using DAG

Answer 1

I had already created the contentsubmitters and it helped with the speed of the mailbox moves.  We have a SMB with >100 users and everything was working great, migrating from 2007 to 2013.  If I had it to do over, maybe it would have been better
to go to 2010 on a 2008 R2 box but decided to jsut go straight to 2013 on a 2012 R2 server.  But the one thing I REALLY wish I had to do over again is to allocate about 3 times more space to the drive that was to hold the mailbox database.  Everything
was working so well until a mailbox was being moved - a batch of several, I was doing maybe 5 at a time for the larger mailboxes - the disk filled up.  Also, before I realized what was going on, I ran some cmdlets thinking my receive connectors weren't
right.  I recovered the database - at first it would not mount at all... but after eseutil /r and /p (and allocating more disk space) I could mount the database and open the mailboxes.  But from then on, nothing is being received and if you send,
it goes to sent items - doesn't hang in outbox, but never goes anyhere except into a queue.  I have MS support working on it and it's been escalated to the top. If they fix it I will try to post any helpful information I can learn from it. But one
lesson - I will read the planning and preparations documentation thoroughly from now on.
Oh, and also, I keep getting this message in the ECP when navigating to the Recipients>migration applet:
Cannot open mailbox /o=<Organization>/ou=Exchange Asministrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/CN=<yourExchangeserver>/cn=Microsoft System Attendant.
If you did the same thing, (and didn't hang yourself or jump in front of a speeding locomotive), you are stronger than I.  Not that I have taken the path of the Samurai network admin or anything....
And if you were able to fix it, I am impressed and would love to know how you fixed this.
Thanks and best,
Sam