[SOLVED] Error attempting to change filesystem label on partition

Questions about applications and software
Forum rules
Before you post please read how to get help
Post Reply
User avatar
slipstick
Level 6
Level 6
Posts: 1048
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

[SOLVED] Error attempting to change filesystem label on partition

Post by slipstick »

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:

Code: Select all

steve@steve-Z97X ~ $ sudo e2label /dev/sda5 LM19_root
e2label: Filesystem has unsupported read-only feature(s) while trying to open /dev/sda5
Couldn't find valid filesystem superblock.
steve@steve-Z97X ~ $ sudo tune2fs -L LM19_root /dev/sda5
tune2fs 1.42.13 (17-May-2015)
tune2fs: Filesystem has unsupported read-only feature(s) while trying to open /dev/sda5
Couldn't find valid filesystem superblock.
and this is the error message from the Disks utility:
Disks_error.png
What am I doing wrong?
Last edited by slipstick on Wed May 29, 2019 3:15 pm, edited 2 times in total.
In theory, theory and practice are the same. In practice, they ain't.
User avatar
WharfRat
Level 21
Level 21
Posts: 13909
Joined: Thu Apr 07, 2011 8:15 pm

Re: Error attempting to change filesystem label on partition

Post by WharfRat »

Could you paste back the results of sudo blkid
ImageImage
kreemoweet
Level 2
Level 2
Posts: 50
Joined: Sat Feb 20, 2016 12:08 am

Re: Error attempting to change filesystem label on partition

Post by kreemoweet »

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.
User avatar
slipstick
Level 6
Level 6
Posts: 1048
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Error attempting to change filesystem label on partition

Post by slipstick »

WharfRat wrote:
Tue May 28, 2019 11:38 pm
Could you paste back the results of sudo blkid

Code: Select all

steve@steve-Z97X ~ $ sudo blkid
[sudo] password for steve: 
/dev/sda1: UUID="12C3-4584" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b846fd17-d4b7-4fbf-bd8d-8e1759f56d67"
/dev/sda3: UUID="9C40C67D40C65E20" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d76e7701-0187-478c-ae93-60fbdf09a3b5"
/dev/sda4: LABEL="ESP_Backup" UUID="923D-9EA0" TYPE="vfat" PARTUUID="78bbb312-0cda-4e37-8b4d-45a8c42df506"
/dev/sda5: UUID="a3e65c35-55b4-4515-81c6-8d2b94627f57" TYPE="ext4" PARTLABEL="LM17_root" PARTUUID="6118a4f2-1bde-47f0-9103-c157027779e6"
/dev/sda6: UUID="a4c88c91-4ada-4e1b-9b27-302050ecf469" TYPE="ext4" PARTLABEL="LM17_home" PARTUUID="f091e287-6994-492a-a642-ce39c9b6d92b"
/dev/sda7: UUID="be736ee9-0a66-4b77-8943-75801d3c3fbd" TYPE="ext4" PARTLABEL="Data" PARTUUID="1dc6ce76-b320-420b-a2bc-0f0c574224d2"
/dev/sda8: UUID="0ef7b19e-daae-4249-afdc-99064e58f304" TYPE="swap" PARTLABEL="Swap" PARTUUID="98d4c8a0-aea5-492f-97c3-8f8081425ffb"
/dev/sda9: UUID="F055-D6BB" TYPE="vfat" PARTLABEL="Share" PARTUUID="8796c002-d01b-4eb6-b57a-0e4047838ca3"
/dev/sda10: LABEL="LM19_timeshift" UUID="38040990-0c90-4340-a7d9-0fbd39e4bc84" TYPE="ext4" PARTLABEL="LM17_timeshift" PARTUUID="e34e1d4d-470c-4b56-b9a0-cb0818320b0c"
/dev/sda11: UUID="ea610a0d-cc22-4e6a-ade2-48029233a620" TYPE="ext4" PARTLABEL="LM18_root" PARTUUID="2a7ffbb1-d76b-439b-b26f-890e0e61365c"
/dev/sda12: UUID="de7c6d71-89c0-45a0-b512-abc2aac505f3" TYPE="ext4" PARTLABEL="LM18_home" PARTUUID="9128049b-7d38-4e3f-ba3c-768e15687a89"
/dev/sda13: LABEL="LM18_timeshift" UUID="3bad929c-0dbf-40a6-89ce-5869c69ea79c" TYPE="ext4" PARTLABEL="LM18_timeshift" PARTUUID="d787c360-8efd-4334-a7c8-817379c56010"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="9bdf8b9f-7313-425b-9dfb-822adaed566c"
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.

Code: Select all

steve@steve-Z97X ~ $ sudo blkid
/dev/sda1: UUID="12C3-4584" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b846fd17-d4b7-4fbf-bd8d-8e1759f56d67"
/dev/sda3: UUID="9C40C67D40C65E20" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d76e7701-0187-478c-ae93-60fbdf09a3b5"
/dev/sda4: LABEL="ESP_Backup" UUID="923D-9EA0" TYPE="vfat" PARTUUID="78bbb312-0cda-4e37-8b4d-45a8c42df506"
/dev/sda5: UUID="a3e65c35-55b4-4515-81c6-8d2b94627f57" TYPE="ext4" PARTLABEL="LM17_root" PARTUUID="6118a4f2-1bde-47f0-9103-c157027779e6"
/dev/sda6: UUID="a4c88c91-4ada-4e1b-9b27-302050ecf469" TYPE="ext4" PARTLABEL="LM17_home" PARTUUID="f091e287-6994-492a-a642-ce39c9b6d92b"
/dev/sda7: UUID="be736ee9-0a66-4b77-8943-75801d3c3fbd" TYPE="ext4" PARTLABEL="Data" PARTUUID="1dc6ce76-b320-420b-a2bc-0f0c574224d2"
/dev/sda8: UUID="0ef7b19e-daae-4249-afdc-99064e58f304" TYPE="swap" PARTLABEL="Swap" PARTUUID="98d4c8a0-aea5-492f-97c3-8f8081425ffb"
/dev/sda9: UUID="F055-D6BB" TYPE="vfat" PARTLABEL="Share" PARTUUID="8796c002-d01b-4eb6-b57a-0e4047838ca3"
/dev/sda10: LABEL="LM19x_root" UUID="38040990-0c90-4340-a7d9-0fbd39e4bc84" TYPE="ext4" PARTLABEL="LM17_timeshift" PARTUUID="e34e1d4d-470c-4b56-b9a0-cb0818320b0c"
/dev/sda11: UUID="ea610a0d-cc22-4e6a-ade2-48029233a620" TYPE="ext4" PARTLABEL="LM18_root" PARTUUID="2a7ffbb1-d76b-439b-b26f-890e0e61365c"
/dev/sda12: UUID="de7c6d71-89c0-45a0-b512-abc2aac505f3" TYPE="ext4" PARTLABEL="LM18_home" PARTUUID="9128049b-7d38-4e3f-ba3c-768e15687a89"
/dev/sda13: LABEL="LM18_timeshift" UUID="3bad929c-0dbf-40a6-89ce-5869c69ea79c" TYPE="ext4" PARTLABEL="LM18_timeshift" PARTUUID="d787c360-8efd-4334-a7c8-817379c56010"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="9bdf8b9f-7313-425b-9dfb-822adaed566c"
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.
User avatar
slipstick
Level 6
Level 6
Posts: 1048
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Error attempting to change filesystem label on partition

Post by slipstick »

kreemoweet wrote:
Wed May 29, 2019 12:37 am
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.
User avatar
slipstick
Level 6
Level 6
Posts: 1048
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Error attempting to change filesystem label on partition

Post by slipstick »

@ kreemoweet:

There does appear to be some difference between the newer partition sda5 and the older sda10 (note the checksum on sda5):

Code: Select all

steve@steve-Z97X ~ $ sudo tune2fs -l /dev/sda5
tune2fs 1.42.13 (17-May-2015)
Filesystem volume name:   <none>
Last mounted on:          /media/steve/a3e65c35-55b4-4515-81c6-8d2b94627f57
Filesystem UUID:          a3e65c35-55b4-4515-81c6-8d2b94627f57
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1310720
Block count:              5242880
Reserved block count:     262144
Free blocks:              3220936
Free inodes:              1006553
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
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 May 25 16:32:40 2019
Last mount time:          Tue May 28 21:05:49 2019
Last write time:          Tue May 28 21:07:26 2019
Mount count:              12
Maximum mount count:      -1
Last checked:             Sat May 25 16:32:40 2019
Check interval:           0 (<none>)
Lifetime writes:          14 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      defbd7f4-4242-41ab-b02b-3459d48b781b
Journal backup:           inode blocks
Checksum:                 0xf7a7a618

Code: Select all

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.
User avatar
WharfRat
Level 21
Level 21
Posts: 13909
Joined: Thu Apr 07, 2011 8:15 pm

Re: Error attempting to change filesystem label on partition

Post by WharfRat »

The Filesystem features are different too.

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.
ImageImage
mediclaser
Level 4
Level 4
Posts: 402
Joined: Tue Mar 20, 2018 2:28 pm

Re: Error attempting to change filesystem label on partition

Post by mediclaser »

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. ;)
User avatar
slipstick
Level 6
Level 6
Posts: 1048
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Error attempting to change filesystem label on partition

Post by slipstick »

WharfRat wrote:
Wed May 29, 2019 8:25 am
The Filesystem features are different too.

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.
Post Reply

Return to “Software & Applications”