Reading jasper 16MB nand: 1st read = 1 bad block , 2nd read = 2 bad blocks ??

[keropi]

I am currently reading the nand of my 16MB jasper...
I got a 250 error in block 0x90 with nand pro , and degraded1.1b reports:

Note: Bad Block @ 0x90
Note: Block 0x9000 found at 0x3FF

ok I thought, normal...

the 2nd read finished and I got a different crc32 this time ... so I opened the new image in degraded and the report this time is:

Note: Bad Block @ 0x90
Note: Bad Block @ 0x3DD
Note: Block 0x9000 found at 0x3FF

So what is the course of action now? 3DD is not remapped, and nandpro did not complain at all about 3DD (gave error only on 0x90)...
- Should I just remap 0x90 in 3FF in XBR.BIN , and ignore 3DD ?
- Or also remap 3DD to 3FE ?

I am currently doing a 3rd read...

[Arakon]

dump a few more times, chances are one of the two is a bad dump.

[keropi]

did a 3rd dump, now 0x90 still remapped to 3FF , and degraded (not nandpro) reports bad blocks at 0x331 , 0x332 ...

I wonder why I get those bad dumps, I did flash a falcon mobo just fine, and took 3 similar dumps in a row, using the same computer... I checked my cabling, seems solind, lenght is ~28cm... I will reduce lenght by ~10cm and see how that goes...

edit: damnit, shorter cables, another image... this one has a bad block 0x0 , eventhough nandpro only complained about 0x90...  

edit2: I did 8 redumps, and found that 4 where identical (only 0x90 relocatted) so I went on and flashed XBR... Block 90 could not be written (so nandpro was correct, I already remapped it to 3FFF) and now I have a jasper XBR 360