[Bug 1435569] Re: Executing update-grub does create entries in dmesg

Sworddragon 1435569 at bugs.launchpad.net
Tue Mar 24 03:53:06 UTC 2015


root at ubuntu:~# blkid
/dev/sda2: UUID="44645410645406D8" TYPE="ntfs" PARTUUID="000aa70d-02"
/dev/sda1: UUID="05338ff8-a226-421b-90a4-1dd45199f783" TYPE="ext4" PARTUUID="000aa70d-01"
/dev/sda5: PARTUUID="000aa70d-05"
/dev/mapper/cryptswap1: UUID="8af7e701-be52-460b-ab50-938c63bcc2ce" TYPE="swap"
root at ubuntu:~# blkid /dev/sda3
/dev/sda3: PTUUID="29f1e303" PTTYPE="dos" PARTUUID="000aa70d-03"

** Changed in: grub2 (Ubuntu)
       Status: Incomplete => New

-- 
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/1435569

Title:
  Executing update-grub does create entries in dmesg

Status in grub2 package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 15.04 dev with grub2-common 2.02~beta2-21 and after
  executing update-grub I'm seeing this additional entries in dmesg:

  [ 1081.806815] SGI XFS with ACLs, security attributes, realtime, no debug enabled
  [ 1081.848057] JFS: nTxBlock = 8192, nTxLock = 65536
  [ 1081.989051] QNX4 filesystem 0.2.3 registered.
  [ 1082.137602] raid6: sse2x1    1215 MB/s
  [ 1082.205677] raid6: sse2x2    1809 MB/s
  [ 1082.273745] raid6: sse2x4    2280 MB/s
  [ 1082.273750] raid6: using algorithm sse2x4 (2280 MB/s)
  [ 1082.273755] raid6: using intx1 recovery algorithm
  [ 1082.290185] xor: measuring software checksum speed
  [ 1082.329805]    prefetch64-sse:  3174.000 MB/sec
  [ 1082.369855]    generic_sse:  3050.000 MB/sec
  [ 1082.369864] xor: using function: prefetch64-sse (3174.000 MB/sec)
  [ 1082.475188] Btrfs loaded
  [ 1082.824164] EXT4-fs (sda3): unable to read superblock
  [ 1082.827427] EXT4-fs (sda3): unable to read superblock
  [ 1082.830654] EXT4-fs (sda3): unable to read superblock
  [ 1082.834055] FAT-fs (sda3): invalid media value (0x77)
  [ 1082.834065] FAT-fs (sda3): Can't find a valid FAT filesystem
  [ 1082.837616] ntfs: (device sda3): is_boot_sector_ntfs(): Invalid boot sector checksum.
  [ 1082.837626] ntfs: (device sda3): read_ntfs_boot_sector(): Primary boot sector is invalid.
  [ 1082.837633] ntfs: (device sda3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
  [ 1082.837638] ntfs: (device sda3): ntfs_fill_super(): Not an NTFS volume.
  [ 1082.841627] XFS (sda3): Invalid superblock magic number
  [ 1082.848564] FAT-fs (sda3): invalid media value (0x77)
  [ 1082.848574] FAT-fs (sda3): Can't find a valid FAT filesystem
  [ 1082.851789] MINIX-fs: unable to read superblock
  [ 1082.854969] attempt to access beyond end of device
  [ 1082.854979] sda3: rw=16, want=3, limit=2
  [ 1082.854986] hfsplus: unable to find HFS+ superblock
  [ 1082.858374] qnx4: no qnx4 filesystem (no root dir).
  [ 1082.861744] ufs: You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
  [ 1082.864761] hfs: can't find a HFS filesystem on dev sda3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1435569/+subscriptions



More information about the foundations-bugs mailing list