* On 2020 26 Mar 18:26 -0500, Nate Bargmann wrote:
> This is now resolved thanks to the help of user Klaus on the Olimex
> forum. The trick was to use dtrfstune to change the p2 UUID of the
> 4G micro-SD to match that of the p@ UUID of the 32 GB card.
s/dtrfstune/btrfstune/
s/p@/p2/
Sigh...
-
If you say so, it wasn't aparent that was what the problem was. Lots
of things can manipulate UUIDs. apropos uuid on this Pi says:
dbus-uuidgen (1) - Utility to generate UUIDs
FcDirCacheCreateUUID (3) - Create .uuid file at a directory
FcDirCacheDeleteUUID (3) - Delete .uuid file
findfs (8)
This is now resolved thanks to the help of user Klaus on the Olimex
forum. The trick was to use dtrfstune to change the p2 UUID of the
4G micro-SD to match that of the p@ UUID of the 32 GB card.
All is working well now. I now have the 32 GB card available to work
with the Raspberry Pi 4B that
On Wednesday 25 March 2020 09:51:03 gru...@mailfence.com wrote:
> On Wed, 25 Mar 2020, Gene Heskett wrote:
> > On Wednesday 25 March 2020 08:51:17 gru...@mailfence.com wrote:
> >> On Wed, 25 Mar 2020, Gene Heskett wrote:
> >>> On Wednesday 25 March 2020 04:18:20 Andrei POPESCU wrote:
> On
On Wed, 25 Mar 2020, Gene Heskett wrote:
On Wednesday 25 March 2020 08:51:17 gru...@mailfence.com wrote:
On Wed, 25 Mar 2020, Gene Heskett wrote:
On Wednesday 25 March 2020 04:18:20 Andrei POPESCU wrote:
On Ma, 24 mar 20, 19:12:46, Gene Heskett wrote:
And nothing so far, and I have been
On Wednesday 25 March 2020 08:51:17 gru...@mailfence.com wrote:
> On Wed, 25 Mar 2020, Gene Heskett wrote:
> > On Wednesday 25 March 2020 04:18:20 Andrei POPESCU wrote:
> >> On Ma, 24 mar 20, 19:12:46, Gene Heskett wrote:
> >>> And nothing so far, and I have been watching, in the way of
> >>>
On Wed, 25 Mar 2020, Gene Heskett wrote:
On Wednesday 25 March 2020 04:18:20 Andrei POPESCU wrote:
On Ma, 24 mar 20, 19:12:46, Gene Heskett wrote:
And nothing so far, and I have been watching, in the way of reducing
a filesystem to only the actual size occupied. Then it can be backed
up with
On Wednesday 25 March 2020 07:26:12 Nate Bargmann wrote:
> * On 2020 25 Mar 00:11 -0500, Alan Corey wrote:
> > Try your kernel config string. On this Pi /boot/cmdline.txt has
> > root=PARTUUID=d9b3f436-02
>
> Except I'm not working with a Pi. Yes, I've done the exact same thing
> in the past on
On Wednesday 25 March 2020 04:18:20 Andrei POPESCU wrote:
> On Ma, 24 mar 20, 19:12:46, Gene Heskett wrote:
> > And nothing so far, and I have been watching, in the way of reducing
> > a filesystem to only the actual size occupied. Then it can be backed
> > up with dd and recovered, rewritten by
* On 2020 25 Mar 00:11 -0500, Alan Corey wrote:
> Try your kernel config string. On this Pi /boot/cmdline.txt has
> root=PARTUUID=d9b3f436-02
Except I'm not working with a Pi. Yes, I've done the exact same thing
in the past on a Pi. Pi's are easy peasy. This is a different animal
that has
On Ma, 24 mar 20, 19:12:46, Gene Heskett wrote:
>
> And nothing so far, and I have been watching, in the way of reducing a
> filesystem to only the actual size occupied. Then it can be backed up
> with dd and recovered, rewritten by dd, at a reasonable size for
> storage. And re-expanded to
Try your kernel config string. On this Pi /boot/cmdline.txt has
root=PARTUUID=d9b3f436-02
I copied an sd to a hard drive once and it wouldn't boot until I put
the partuuid from the hard drive in there. That and the fstab were
the only changes I had to make. Should have put rootwait in there
Grep on the 32 GB card for the root UUID only turns up the value in
p2/etc/fstab. Nothing turned up in p1 though I can manually look into
either of the initrd images with Midnight Commander and find it in the
aforementioned dafault_root file.
I did see where the 32 GB card has p2 labeled as
Grep for the UUID? Including grep -r to recurse directories. You'll
probably need to do it once per partition. gpartid has some serous
bugs when it comes to resizing I think. If you're really careful with
your math you can control fdisk at a sector level. Actually I've done
it in OpenBSD, not
* On 2020 24 Mar 15:46 -0500, Alan Corey wrote:
> Downsizing requires that no files are in the part you trim off.
Ahhh. Makes sense.
The mmc has two partitions, p1 an ext2 of 128 MB and p2 a btrfs with the
rest of the space.
Since I had the files of p2 on the 4 GB card, I went ahead and
Have you tried partimage? Maybe it only does one partition, I was
looking for something that can make images like the ones you download
when youj insttall. Just saw this today, haven't tried it yet.
Partition Image is a partition imaging utility. It has support for the
following file systems:
On Tuesday 24 March 2020 16:44:42 Alan Corey wrote:
> Downsizing requires that no files are in the part you trim off.
> Upsizing can sometimes be done by deleting the partition and
> recreating letting fdisk use the maximum size. Don't format between
> or anything and in case you have to type
Downsizing requires that no files are in the part you trim off.
Upsizing can sometimes be done by deleting the partition and
recreating letting fdisk use the maximum size. Don't format between
or anything and in case you have to type the numbers in you should
have a copy of them handy like
Device
18 matches
Mail list logo
