I have just installed LM19.1 on my computer (triple boot with W7 and LM18.3). I am currently using 18.3. The new 19.1 was installed over the old 17.3, so I want to add labels to my LM19.1 partitions (former 17.3 partitions): LM19_root and LM19_home. They currently do not have a label. Note - these are the filesystem names (LABEL) I want to change, not the GUID partition labels (PARTLABEL) - my system is UEFI/GPT. I have tried using e2label, tune2fs, and the GUI "Disks" program from the menu - everytime with an error. I get the same error on both partitions that I want to label. The system boots into 19.1 OK, so I don't think there is anything wrong with the filesystems or superblocks.
I have tried these terminal commands both with the partitions unmounted and mounted:
Searching online for that error message text seems to suggest it's caused by incompatability in older versions
of e2fsprogs when its trying to open and relabel ext4 filesystems which have newer features.
As you can see, I was able to change the label on sda10. And I just changed it to LM19x_root (oops - meant to change it to LM19x_timeshift) successfully using e2label.
I don't know what is different between sda5, sda6, which I can't label, and sda10 which I can re-label, except for the mountpoint (but none were mounted at the time).
Last edited by slipstick on Wed May 29, 2019 1:33 am, edited 1 time in total.
In theory, theory and practice are the same. In practice, they ain't.
Searching online for that error message text seems to suggest it's caused by incompatability in older versions
of e2fsprogs when its trying to open and relabel ext4 filesystems which have newer features.
See my last post - I can relabel sda10 with e2label. One note - the sda10 partition was created probably two years ago or more and hasn't been reformatted since. The partitions which fail to label, sda5 and sda6 were reformatted just a couple of days ago when I installed LM19.1.
EDIT: corrected typo - sda10 was mistakenly labeled sda17 in the second usage.
Last edited by slipstick on Sat Jun 08, 2019 1:53 am, edited 1 time in total.
In theory, theory and practice are the same. In practice, they ain't.
steve@steve-Z97X ~ $ sudo tune2fs -l /dev/sda10
tune2fs 1.42.13 (17-May-2015)
Filesystem volume name: LM19_timeshift
Last mounted on: /media/root/LM19_timeshift
Filesystem UUID: 38040990-0c90-4340-a7d9-0fbd39e4bc84
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 6397952
Block count: 25589760
Reserved block count: 1279488
Free blocks: 22434075
Free inodes: 5996855
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1017
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Sat Apr 22 17:59:02 2017
Last mount time: Sat May 25 17:43:18 2019
Last write time: Wed May 29 00:31:07 2019
Mount count: 63
Maximum mount count: -1
Last checked: Sat Apr 22 17:59:02 2017
Check interval: 0 (<none>)
Lifetime writes: 434 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 91c2b155-52cb-45b6-84ce-bed1eb65a781
Journal backup: inode blocks
I can try to boot into a LM19.1 live version and try to relabel from there (using 18.3 now) just in case 19.1 has a newer version of e2label. But it will have to wait till tomorrow - it's getting late here.
In theory, theory and practice are the same. In practice, they ain't.
I use GParted to label partitions on a multiboot machine I use. It is so easy...just make sure the partition you want to label is not mounted. If it is, simply unmount it, then click "Refresh Devices" in GParted. Then you can label the partition.
If you're looking for a greener Linux pasture, you won't find any that is greener than Linux Mint. ;)
You formatted sda5 last Saturday and I suspect it was with LM 19.1 so setting the label with LM 19.1 will most likely work,
I would be curious to know if you can label sda10 from LM 19.1 to see if tune2fs and e2label are backward compatible.
I booted into a live LM19.1 system and successfully used e2label to set labels on sda5 and sda6 (the newly formatted partitions). I was also able to change the label on sda10 (old partition). I forgot to try with tune2fs, but I expect that works too, as both that and e2label are part of the E2fsprogs package.
LM18.3 version of the E2fsprogs package is 1.42.13 May, 2015
LM19.1 version of the E2fsprogs package is 1.44.1 March, 2018
I will mark this solved - thanks to all for your help.
EDIT: The takeaway is don't use older version tools to work on filesystems formatted with a newer version of linux.
In theory, theory and practice are the same. In practice, they ain't.
