256GB Micro SD Card Pi 4

[djc290761]

I have just used Win32DiskImager to make an image of my Raspberry Pi 4, stored on my Windows Backup SSD and to then copy the image on to a new 256GB card. Both images were verified using Win32DiskImager.

I then put the new card into the Pi 4 and rebooted. Everything seemed to worked OK, after making a few screen display tweeks.

I then opened raspi-config, went to Advanced Options (7) and then to Expand File System (A1).

Here the Pi displayed the error message "Your current layout is not supported by this tool". I assume this is something to do with Fat32 vesus Exfat!!

I have two questions

1. How can I get A1 to work as expected?
2. How can I find the actual size of the memory that the Pi actually sees?

Thanks

[kerry_s]

that's a big sd to use on a pi.

first thought: it should auto expand at first boot, if you made the sd correctly.
next: the /boot is always "fat32" the /root is ext4, so file system should not be a issue.

run "lsblk" and post the output.

[FTrevorGowen]

I have just used Win32DiskImager to make an image of my Raspberry Pi 4, stored on my Windows Backup SSD and to then copy the image on to a new 256GB card. Both images were verified using Win32DiskImager.

I then put the new card into the Pi 4 and rebooted. Everything seemed to worked OK, after making a few screen display tweeks.

I then opened raspi-config, went to Advanced Options (7) and then to Expand File System (A1).

Here the Pi displayed the error message "Your current layout is not supported by this tool". I assume this is something to do with Fat32 vesus Exfat!!

I have two questions

1. How can I get A1 to work as expected?
2. How can I find the actual size of the memory that the Pi actually sees?

Thanks

Are you running Raspbian? If so, what happens if, instead of using Win32DiskImager (on another computer) you try using Raspbian's SD Card Copier tool (aka piclone) to clone the original card directly to the 256Gb (uSDXC?) card using a USB-based uSDHC/XC compatible card reader/writer?
(FWIW some screenshots of the above process can be seen here: https://www.cpmspectrepi.uk/raspberry_p ... OnP4B.html
(albeit for a 16Gb setup to a 32Gb card).
W.r.t. option "A1" what size was the original card? (AIUI when using the cloning tool file system expansion is handled "automatically" and that raspi-config option is not required. If your original card was <256Gb then the Win32DiskImager written image will be that size and the "expansion" mechanism will know nothing about the extra space and will think the filesystem is already expanded!)
Trev.

[drgeoff]

I have just used Win32DiskImager to make an image of my Raspberry Pi 4, stored on my Windows Backup SSD and to then copy the image on to a new 256GB card. Both images were verified using Win32DiskImager.

I then put the new card into the Pi 4 and rebooted. Everything seemed to worked OK, after making a few screen display tweeks.

I then opened raspi-config, went to Advanced Options (7) and then to Expand File System (A1).

Here the Pi displayed the error message "Your current layout is not supported by this tool". I assume this is something to do with Fat32 vesus Exfat!!

I have two questions

1. How can I get A1 to work as expected?
2. How can I find the actual size of the memory that the Pi actually sees?

Thanks

NOOBS?

[rpdom]

W.r.t. option "A1" what size was the original card? (AIUI when using the cloning tool file system expansion is handled "automatically" and that raspi-config option is not required. If your original card was <256Gb then the Win32DiskImager written image will be that size and the "expansion" mechanism will know nothing about the extra space and will think the filesystem is already expanded!)

if that were true, the expand option wouldn't work on any size card.

The expansion routine looks at the size of the current card and expands the file system to fill that.

My guess is NOOBS, although the message reported is different to the one I'd expect, which is "Your partition layout is not currently supported by this tool. You are probably using NOOBS, in which case your root filesystem is already expanded anyway.".

[FTrevorGowen]

W.r.t. option "A1" what size was the original card? (AIUI when using the cloning tool file system expansion is handled "automatically" and that raspi-config option is not required. If your original card was <256Gb then the Win32DiskImager written image will be that size and the "expansion" mechanism will know nothing about the extra space and will think the filesystem is already expanded!)

if that were true, the expand option wouldn't work on any size card.
...

a bit tired last night - you are correct of course (assuming the first boot expansion mechanism is the same as raspi-config does if that hasn't happened which, for some reason, I was thinking might not be the case). W.r.t. to it possibly being a NOOBS-based install seems quite likely.
Trev.