On 10/06/2020 15:54, Ralph Corderoy wrote:
Hi Peter,
So I tried to use etcher and it tells me that the image is too large
for the destination card.
Perhaps they're different sizes.
Use ‘sudo lsblk -b’ to get a list of current block devices and their
size in bytes. You can ignore the partitions.
Gather the size of both SD cards and compare.
If source > destination then that explains the error.
You can also compare source size in bytes to the size of the image file
you've created, just to see they match.
It might be that you can shrink the source's filesystem(s) and
partition(s) to leave a run of sectors at the end of the device unused.
The used sectors starting from the beginning of the block device may
then fit in the destination.
I see what you mean:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT (TDK)
sdb 8:16 1 15720251392 0 disk
├─sdb1 8:17 1 46005248 0 part
└─sdb2 8:18 1 15669919744 0 part
sr0 11:0 1 1073741312 0 rom
sr1 11:1 1 1073741312 0 rom
peterm@peterm-MBB-34204H:~$ sudo lsblk -b
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT (Toshiba)
sdb 8:16 1 15552479232 0 disk
├─sdb1 8:17 1 46005248 0 part
└─sdb2 8:18 1 15502147584 0 part
sr0 11:0 1 1073741312 0 rom
sr1 11:1 1 1073741312 0 rom
I am sure that I used the Raspbian operation to expand the filesystem when I
first used the card.
I just wondered if the bit that is missing was needed, and it must be because
the card won't boot.!
Peter
--
Next meeting: Online, Jitsi, Tuesday, 2020-07-07 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
