tagdump resync on tag reboot

[cire831]

• the tag rebooted with a new image. And the resync goes nuts.
  we did not write out the last sectors in memory. should have done a forced reboot first.

• So what did tagdump see?

• should have found a good reboot at the start of the next sector. But its in the weeds.

• if possible make tagdump recover from this

• where is the reboot record?

--- @4858028   6752 976646642   28     3  SYNC  prev: @4855920 (0x4a1870)
--- @4858056   6753 53899762   28     3  SYNC  prev: @4858028 (0x4a20ac)
--- @4858084   6754 137785842   28     3  SYNC  prev: @4858056 (0x4a20c8)
--- @4858112   6755 221671922   28     3  SYNC  prev: @4858084 (0x4a20e4)
*** record size too small: 0, @4858140

*** resync started @4858140 (0x4a211c)
  C-c C-c*** TF.read: unhandled exception <type 'exceptions.KeyboardInterrupt'>
*** resync: exception error: <type 'exceptions.KeyboardInterrupt'> @4859300


*** user stop

*** end of processing @4859304 (0x4a25a8),  processed: 591 records, 31466 bytes
*** reboots: 0, resyncs: 1, chksum_errs: 0, unk_rtypes: 0

rtypes: {32: 222, 3: 23, 4: 346}
mids:   {65: 5, 2: 166, 4: 2, 225: 2, 9: 5, 51: 5, 90: 1, 41: 4, 56: 26, 218: 1, 93: 5}
P222 (165): ll -a
total 0
drwxr-x--x 8 pi pi       0 Dec 31  1969 ./
drwxr-x--x 6 pi pi       0 Dec 31  1969 ../
-r--r--r-- 1 pi pi 4885776 May 14 12:18 byte
-r--r--r-- 1 pi pi 4885504 May 14 12:18 .committed
-r--r--r-- 1 pi pi 4885964 May 14 12:18 .last_rec
-r--r--r-- 1 pi pi 4882452 May 14 12:18 .last_sync
-rw-rw---- 1 pi pi       0 May 14 12:18 note
-r--r--r-- 1 pi pi     412 May 14 12:18 .recnum