08-27-2022, 05:18 AM
Except I'm getting a different runaround this time. After flashing, I discovered that it was automounted by DoubleCommander, so okay I turned it off, flashed again, resized partition and then needed to mount it to resize the filesystem.
This is where it gets weird. When I issue sudo df, it finde it as /dev/sdk2. Then blkid finds it as /dev/sdh2. Any attempt to mount fails. If I try to set up a mount point from the disks app (Mint 20.3), it gives me various kinds of errors, depending on options I choose, but it's either that the mount point doesn't exist or that there's already a file with such a name.
I've already learned that trying out a SD with resized partition but not resized filesystem won't work... so... now what. Will try resize2fs, just for kicks... and it still reports „bad magic number in superblock“.
So, guys... what am I doing wrong?
This is where it gets weird. When I issue sudo df, it finde it as /dev/sdk2. Then blkid finds it as /dev/sdh2. Any attempt to mount fails. If I try to set up a mount point from the disks app (Mint 20.3), it gives me various kinds of errors, depending on options I choose, but it's either that the mount point doesn't exist or that there's already a file with such a name.
I've already learned that trying out a SD with resized partition but not resized filesystem won't work... so... now what. Will try resize2fs, just for kicks... and it still reports „bad magic number in superblock“.
So, guys... what am I doing wrong?