tecno wrote: Sorry, but my 16Gb SD card is not big enough for that image.
Which brings up a problem we are going to have forever as SSD'd take over the spinning rust job.
The question to be answered, is can e2fsresize fix it going both ways? I know it can expand a crushed image that has had its end of disk inode table moved to a position just after the last data, thereby making the zip a few kilobytes bigger than the actually used data, but no one has explained to me, how, and with what utility this was accomplished with.
The bottom line is that you by x amount of memory, and its random from card to card, often varying by over a gigabyte for a so-called 64GB u-sd card, so the next card is NOT identical due to the use of substitute sectors being used for bad sectors found during test. But ext2-3-4 expect that backup inode table to be at a fixed end of disk location as recorded in the first sectors. But its not the same offset as the one before it, or the one behind it. The question then is how can we "fix" one of these zips, so it can be written back to any u-sd big enough to hold the actual data. Seems to me it ought to be possible tp shrink an image by half a gig oe such in that event.
If there was a memo, I surely missed it.
Ideas?
Thanks
gene1934
