#WIN32 DISK IMAGER VS BALENAETCHER HOW TO#
#WIN32 DISK IMAGER VS BALENAETCHER UPDATE#

If yes then could you again apply the update from 1.2.2.0 to 1.2.2.0 again with the 32GByte SD card. Is my understanding correct so far how you proceed? After the next boot it still shows 8Gbyte but should show 30Gbyte+ as my colleague told us. Then you initated the update to 1.2.2.0 with this large SD card. During this first boot sequence the new 32Gbyte SD card should still indicate 8Gbyte in size. You had the original 8GByte SD card in the version V1.2.0.0 This one you cloned to a 32Gbyte SD card and put it back into your netPI. I just trusted in what a colleague of mine told me. To be honest the tip I gave in this post was not verfied by myself. In order to change the size of the SYSTEM volume additionally you need help of a Linux system supporting the LVM(2) file system.

But this is not enough because the logical volume SYSTEM - responsible for netPI's usable flash memory - within Partition 3 was not changed in its size during this procedure. For this you probably used for the Linux partition tool named 'gparted' and is a thing of a minute. What can be quite easily handled is to extend the size of the Partition 3 from 6GB to 32GB and is what you might have successfully done already. Partition 3 : Filesystem LVM2, noname, containing two logical volumes named SYSTEM and BACKUP, both ext4 formatted. Partition 2 : Filesystem FAT32, name BOOT Partition 1 : Filesystem FAT32, name RESC In general the SD card image of netPI consists of 3 partitions: This procedure does not work on netPI booted with the original SD card since this image is secure and does not allow you to make any partition modifications. The following procedure described needs a separate Linux machine (like ubuntu) along with an external SD card reader. To cut a long story short.Would anyone who is trying to do the same/has done the same and is more into filesystems and logical volumes than me be willing to share his way of doing it with me (and everyone else) in form of a quick manual? Or would one of the Support-Team be that kind? Now I am able to reproduce 16GB netPi Images, but as you might guess, I can't handle e.g. But I managed to change the hardware-ID wirtten to the Image by coping one Partition of the original netPi(2)'s Image to the 16-GB Image of netPI(1). After that of course the netPI(2) did not boot, since the Hardware-ID of the netPi did not match the hardware-ID written to the image by Hilscher. I flashed the Image of netPi(1), which I was able to sucessfully extend to 16GBs, to the netPI(2). After hours of trying, I surrendered and found a kind of a 'hack' which helped me out. Trying this at the second netPi, I wasn't able to do it again.

#WIN32 DISK IMAGER VS BALENAETCHER HOW TO#

I thought 'hey, now I know what to do' and wrote a quick manual of how to do the extension.

After that I was able to use the complete 16-GBs of the new card on this netPi. After googeling, try and error, I actually managed to extend the Logical Volume which is used by the netPi for storing our data, with the underlying volume group and physical volume. So my 16 GB-card still worked like a 8 GB-one. The only problem is that I forgot to extend the filesystem/logical Volume on the new card to be able to use the additional space. When I inserted the new card into the netPi, everything worked well. I was also able to flash this image to the new card using balenaEtcher. Therefore I have backuped the original Image with win32-Disk-Imager, which worked well. Since I like the original Hilscher-Image with its security features quite a lot, I would not want to miss it on a larger sd-card. Therefore it is possible to use larger micro-sd-cards as the original 8GB-one. Since Revision #2 it is possible to change the micro-sd-card of the netPi.

Win32 disk imager vs balenaetcher