OK, I see now what you were doing different. I think I could deal with leaving the /data partition the same size and increasing the two filesystems. I was just trying to save myself the hassle of performing a mender update down the road and forgetting that the data in ~/ wasn't persistent.
I guess it is something to try for now (tomorrow), and then flesh out the /data problem after having a better understanding of what is going on (hopefully). On Jun 19, 2019, at 8:21 PM, Chris Gobbett <go...@tpg.com.au<mailto:go...@tpg.com.au>> wrote: My understanding of the partiitons on the card are (in order); <boot><filesystem+kernel A><filesystem+kernel B><persistent data><empty space> Mender allows you to boot from one of the A/B partitions as your primary filesystem (mounted as /), plus the persistent data (mounted as /home/ or /data or similar). My experience is if you perform resizing while keeping the partitions contiguous (no free space between them), and have the A and B partitions identical in size, it "just works". So my steps in the previous reply would look like: <boot><filesystem+kernel A><filesystem+kernel B><persistent data><----------empty space---------------> # original image on large SD Card <boot><filesystem+kernel A><filesystem+kernel B><-------------empty space------------><persistent data> # shift persistent data to the end <boot><----------filesystem+kernel A---------><----------filesystem+kernel B---------><persistent data> # maximise A/B partitions, keeping A and B the same size Rather than extending the data partition, I wanted to add new libraries and applications in /usr, which is located on the A/B partitions. Hence my instructions involve me resizing those partitions instead of the data partition. If you're simply extending the size of the persistent data partition without shifting it's start point (while leaving the other partitions alone) I'm at a loss as to why it wouldn't work. But when you do this you may need some extra linux-fu to shift your new binary/library locations to that partition rather than the default /usr. Cheers, Chris ----- Original Message ----- From: "Jason Matusiak" <ja...@gardettoengineering.com> To: "Chris Gobbett" <go...@tpg.com.au> Cc: "Ettus Mail List" <usrp-users@lists.ettus.com> Sent: Wed, 19 Jun 2019 23:12:40 +0000 Subject: Re: [USRP-users] E320 with larger SD card Chris, thanks for the tips. So I put a fresh load on a card, then used gparted to extend the data partition to fill things out. That isn't enough, and your instructions certainly show more steps. But I don't understand what you mean with the partitions in the middle. I'll read up on Mender and see if that answers it for me. Thanks again. On Jun 19, 2019, at 6:56 PM, Chris Gobbett < go...@tpg.com.au<mailto:go...@tpg.com.au>> wrote: Hi Jason, I've had luck with the following: - backup/clone the original SDCard image to disk and/or larger SDCard (using dd or otherwise) - on the new card, resize/shift the data partion to the end of the card (using gparted) - resize the two filesystem/kernel partitions to fill in the empty space in the middle, but they need to be the same size (using gparted) Read up on Mender for more info on the partition layout (https://docs.mender.io/1.7/devices/general-system-requirements#partition-layout). It's a pain that they went with Mender for the default E320 card; it cuts the 'usable' file system space in half, at the benefit of having 2 independent filesystem partitions... I haven't had time to fiddle around and ditch the mender for a 'normal' partition layout, but I'd assume it's possible. Cheers, Chris ----- Original Message ----- From: "Jason Matusiak" <ja...@gardettoengineering.com> To: "Ettus Mail List" <usrp-users@lists.ettus.com> Cc: Sent: Wed, 19 Jun 2019 16:29:38 +0000 Subject: [USRP-users] E320 with larger SD card I wanted to use a larger SD card than the one that as supplied, but I am having issues. I loaded up the card, and then extended the data partition to use up the rest of the free space (about 100GB). But then it doesn't boot. I am wondering if the change to a partition size screwed up something in a config file somewhere. Is there a way to fix this without rebuilding a docker image? I am using the UHD 3.14.0.0. that has the smaller data partition (UHD 3.14.1.0 has a larger data partition, but doesn't include any GR/python packages, so I need to use the older image). Thanks.
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
