[Bug 1274320] Re: Error: diskfilter writes are not supported
Bug Watch Updater
1274320 at bugs.launchpad.net
Thu Oct 26 15:19:15 UTC 2017
Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1006289.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2013-09-10T11:50:08+00:00 Harald wrote:
Created attachment 795965
photo of bootscreen
after upgrade to F19 GRUB2 comes up with "error: diskfilter writes are
not supported" and waits some seconds to press a key and thanks god
boots after that automatically to not break wakeup-on-lan (see also
attachment)
but what is this nonsense?
Personalities : [raid1] [raid10]
md2 : active raid10 sda3[0] sdc3[1] sdb3[3] sdd3[2]
3875222528 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU]
bitmap: 2/29 pages [8KB], 65536KB chunk
md1 : active raid10 sda2[0] sdc2[1] sdb2[3] sdd2[2]
30716928 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU]
bitmap: 0/1 pages [0KB], 65536KB chunk
md0 : active raid1 sda1[0] sdc1[1] sdd1[2] sdb1[3]
511988 blocks super 1.0 [4/4] [UUUU]
unused devices: <none>
_________________________________________________
[root at rh:~]$ cat /boot/grub2/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="${saved_entry}"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
terminal_output console
set timeout=1
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora, with Linux 3.10.11-200.fc19.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.10.11-200.fc19.x86_64-advanced-b935b5db-0051-4f7f-83ac-6a6651fe0988' {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod ext2
set root='mduuid/1d691642baed26df1d1974964fb00ff8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='mduuid/1d691642baed26df1d1974964fb00ff8' 1de836e4-e97c-43ee-b65c-400b0c29d3aa
else
search --no-floppy --fs-uuid --set=root 1de836e4-e97c-43ee-b65c-400b0c29d3aa
fi
linux /vmlinuz-3.10.11-200.fc19.x86_64 root=UUID=b935b5db-0051-4f7f-83ac-6a6651fe0988 ro divider=10 audit=0 rd.plymouth=0 plymouth.enable=0 rd.md.uuid=b7475879:c95d9a47:c5043c02:0c5ae720 rd.md.uuid=1d691642:baed26df:1d197496:4fb00ff8 rd.md.uuid=ea253255:cb915401:f32794ad:ce0fe396 rd.luks=0 rd.lvm=0 rd.dm=0 elevator=deadline selinux=0 net.ifnames=0 biosdevname=0 clocksource=hpet noisapnp noresume nf_conntrack.acct=1 printk.time=0 nmi_watchdog=0 pcie_aspm=force i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 consoleblank=0 acpi_osi=Linux vconsole.font=latarcyrheb-sun16 vconsole.keymap=de-latin1-nodeadkeys locale.LANG=de_DE.UTF-8
initrd /initramfs-3.10.11-200.fc19.x86_64.img
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_ppc_terminfo ###
### END /etc/grub.d/20_ppc_terminfo ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/0
------------------------------------------------------------------------
On 2013-09-10T14:12:41+00:00 Harald wrote:
oh, and remove the line "insmod diskfilter" from "grub.cfg" does not
change anything
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/1
------------------------------------------------------------------------
On 2013-10-08T08:21:52+00:00 Michal wrote:
I'm seeing the same error. I found the message mysterious, so I took a look at the code and discovered the following:
- "diskfilter" is GRUB's implementation detail for working with LVM and MD RAID
devices.
- Writing to these kinds of devices is not implemented in GRUB.
- The error may have always been there, but
0085-grub-core-disk-diskfilter.c-grub_diskfilter_write-Ca.patch made it more
visible.
- The reason GRUB is trying to write to the device could be it's following
the "save_env" commands in the config file.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/2
------------------------------------------------------------------------
On 2013-10-08T08:30:44+00:00 Harald wrote:
interesting - why does GRUB try to write anything?
it has not to touch any FS at boot
GRUB2 is such a large step backwards because it is more or less it's own
operating system with the most ugly configuration one could design while
grub-legacy was a boot-manager and nothing else
finally we end in 3 full operating systems
* grub
* dracut
* linux
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/3
------------------------------------------------------------------------
On 2013-10-08T08:44:18+00:00 Harald wrote:
/etc/default/grub with these options avoids a lot of crap on Fedora-Only
machines
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="Fedora"
GRUB_SAVEDEFAULT="false"
GRUB_TERMINAL_OUTPUT="console"
GRUB_DISABLE_RECOVERY="true"
GRUB_DISABLE_SUBMENU="true"
GRUB_DISABLE_OS_PROBER="true"
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/4
------------------------------------------------------------------------
On 2013-10-08T12:52:39+00:00 Michal wrote:
Note that GRUB Legacy had a similar feature: the "savedefault" command.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/5
------------------------------------------------------------------------
On 2013-10-08T12:54:53+00:00 Harald wrote:
but it did not halt boot for some seconds with a useless error message
and "press any key to continue" as well it did not mess up with
submenues and whatever nor did it freeze the machine while edit the
kernel line which happens with GRUB2 way too often if you need to edit
it
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/6
------------------------------------------------------------------------
On 2013-10-08T13:15:05+00:00 Michal wrote:
My comment #5 was just to show that the assertion "it has not to touch any FS at boot" is false and that GRUB Legacy was no different in this regard.
I already commented on the increased visibility of the error, in comment #2.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/7
------------------------------------------------------------------------
On 2014-04-10T14:06:06+00:00 eileon wrote:
For Fedora 20 in /etc/default/grub
GRUB_SAVEDEFAULT="false"
makes the difference (after grub2-mkconfig)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/34
------------------------------------------------------------------------
On 2015-01-09T19:47:14+00:00 Fedora wrote:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/108
------------------------------------------------------------------------
On 2015-02-17T17:08:00+00:00 Fedora wrote:
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1274320/comments/110
** Changed in: grub2 (Fedora)
Status: Unknown => Won't Fix
** Changed in: grub2 (Fedora)
Importance: Unknown => Undecided
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1274320
Title:
Error: diskfilter writes are not supported
Status in grub:
Unknown
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2-signed package in Ubuntu:
Fix Released
Status in grub2 source package in Trusty:
Fix Released
Status in grub2-signed source package in Trusty:
Fix Released
Status in grub2 source package in Vivid:
Fix Released
Status in grub2-signed source package in Vivid:
Fix Released
Status in grub2 package in Debian:
Fix Released
Status in grub2 package in Fedora:
Won't Fix
Bug description:
[Impact]
RAID and LVM users may run into a cryptic warning on boot from GRUB; because some variants of RAID and LVM are not supported for writing by GRUB itself. GRUB would typically try to write a tiny file to the boot partition for things like remembering the last selected boot entry.
[Test Case]
On an affected system (typically any RAID/LVM setup where the boot device is on RAID or on a LVM device), try to boot. Without the patch, the message will appear, otherwise it will not.
[Regression Potential]
The potential for regression is minimal as the patch involves enforcing the fact that diskfilter writes are unsupported by grub in menu building scripts, which will automatically avoid enabling recordfail (the offending feature which saves GRUB's state) if the boot partition is detected to be on a device which does not support diskfilter writes.
----
Once grub chooses what to boot to, an error shows up and will sit on
the screen for approx. 5 seconds
"Error: diskfilter writes are not supported.
Press any key to continue..."
From what I understand, this error is related to raid partitions, and
I have two of them (md0, md1). Both partitions are used (root and
swap). Raid is assembled with mdadm and are raid0
This error message started appearing right after grub2 was updated on
01/27/2014.
System: Kernel: 3.13.0-5-generic x86_64 (64 bit) Desktop: KDE 4.11.5 Distro: Ubuntu 14.04 trusty
Drives: HDD Total Size: 1064.2GB (10.9% used)
1: id: /dev/sda model: SanDisk_SDSSDRC0 size: 32.0GB
2: id: /dev/sdb model: SanDisk_SDSSDRC0 size: 32.0GB
3: id: /dev/sdc model: ST31000528AS size: 1000.2GB
RAID: Device-1: /dev/md1 - active raid: 0 components: online: sdb2 sda3 (swap) Device-2: /dev/md0 - active raid: 0 components: online: sdb1 sda1 ( / )
Grub2: grub-efi-amd64 version 2.02~beta2-5
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: grub-efi-amd64 2.02~beta2-5
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Jan 29 17:37:59 2014
SourcePackage: grub2
UpgradeStatus: Upgraded to trusty on 2014-01-23 (6 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1274320/+subscriptions
More information about the foundations-bugs
mailing list