| 2019-09-14 17:29:24 |
Jim Bray |
bug |
|
|
added bug |
| 2019-09-14 17:50:56 |
Jim Bray |
summary |
grub2 doesn't recognize ext4 with metadata_csum enabled |
grub2 doesn't recognize ext4 with metadata_csum_seed enabled |
|
| 2019-09-14 17:50:56 |
Jim Bray |
description |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum option fixes this.
Oddly enough it doesn't fail with this error, from grub-core/fs/ext2.c:
grub_error (GRUB_ERR_BAD_FS, "filesystem has unsupported incompatible features");
I will recreate the bug and get a precise error message and append it.
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
"metadata_csum
This ext4 feature enables metadata checksumming. This feature stores checksums for all of the filesystem metadata (superblock, group descriptor blocks, inode and block bitmaps, directories, and extent tree blocks).
The checksum algorithm used for the metadata blocks is different than the one used for group descriptors with the uninit_bg feature. These two features are incompatible and metadata_csum will be used preferentially
instead of uninit_bg." |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum option fixes this.
The failure is "unrecognized filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metata checksum seed in the superblock changes it beyond recognition for grub.
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
|
| 2019-09-14 17:50:56 |
Jim Bray |
tags |
ext4 grub metadata-csum |
ext4 grub metadata-csum-seed |
|
| 2019-09-14 17:58:07 |
Jim Bray |
description |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum option fixes this.
The failure is "unrecognized filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metata checksum seed in the superblock changes it beyond recognition for grub.
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
|
| 2019-09-14 17:58:39 |
Jim Bray |
description |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
|
| 2019-09-14 18:21:11 |
Jim Bray |
description |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metadata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
|
| 2019-09-14 18:23:43 |
Jim Bray |
description |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/vm etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metadata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/ etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metadata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
|
| 2019-09-14 18:25:55 |
Jim Bray |
description |
(probably)/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/ etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metadata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/ etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metadata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
which appears to probe for filesystems by calling the fs modules to attempt to mount it.
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
|
| 2019-09-15 01:27:47 |
Jim Bray |
description |
/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/ etc on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metadata checksum seed in the superblock changes it beyond recognition for grub. The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
which appears to probe for filesystems by calling the fs modules to attempt to mount it.
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
/usr/lib/grub/x86_64-efi/ext2.mod, from:
grub-efi-amd64-bin:
Installed: 2.02-2ubuntu8.13
Candidate: 2.02-2ubuntu8.13
doesn't recognize an ext4 filesystem with metadata_csum_seed set.
This is true in command-line grub, not just the update-grub software. Attempting
linux (hdx,gptx)/ etc
on an ext4 fs with metadata_csum enabled fails; removing the metadata_csum_seed option fixes this.
The failure is "unknown filesystem" for any ext4 fs with metadata_csum_seed set. Apparently saving the metadata checksum seed in the superblock changes it beyond recognition for grub.
The message appears to be coming from
grub-2.04/grub-core/kern /fs.c:
grub_fs_t
grub_fs_probe (grub_device_t device)
{....
grub_error (GRUB_ERR_UNKNOWN_FS, N_("unknown filesystem"));
}
which appears to probe for filesystems by calling the fs modules to attempt to mount it.
I tried to install latest grub from eaon to see if upstream has fixed this, but it depended on too much other unreleased software such as libc6.
I pulled the 2.04 source. There is nothing in the Changelog that appears to address this.
from `man ext4`:
metadata_csum_seed
This feature allows the filesystem to store the metadata checksum seed in the superblock, which allows the administrator to change the UUID of a filesystem using the metadata_csum feature while it is mounted. |
|
| 2019-09-16 22:58:08 |
Jim Bray |
bug watch added |
|
http://savannah.gnu.org/bugs/?56897 |
|
| 2020-11-05 15:41:51 |
Launchpad Janitor |
grub2 (Ubuntu): status |
New |
Confirmed |
|
| 2020-11-05 15:43:09 |
Adrien Beau |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866603 |
|
| 2020-11-05 15:43:09 |
Adrien Beau |
bug task added |
|
grub2 (Debian) |
|
| 2020-11-10 20:47:39 |
Bug Watch Updater |
grub2 (Debian): status |
Unknown |
Confirmed |
|
| 2023-07-28 12:21:34 |
Bug Watch Updater |
grub2 (Debian): status |
Confirmed |
Fix Released |
|
