ISST-LTE: pVM: warning message showed in dmesg after update-grub

Bug #1553181 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-prober (Ubuntu)
Triaged
Undecided
Mathieu Trudel-Lapierre

Bug Description

== Comment: #0 - Ping Tian Han - 2016-02-24 01:27:37 ==
After run update-grub, there are some warning message showed in dmesg:

% dmesg|tail -n 50
[ 1368.420636] FAT-fs (sdj1): Can't find a valid FAT filesystem
[ 1368.430463] XFS (sdj1): Invalid superblock magic number
[ 1368.435139] FAT-fs (sdj1): bogus number of reserved sectors
[ 1368.435153] FAT-fs (sdj1): Can't find a valid FAT filesystem
[ 1368.441715] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sdj1.
[ 1368.444377] hfsplus: unable to find HFS+ superblock
[ 1368.446243] qnx4: no qnx4 filesystem (no root dir).
[ 1368.447300] 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
[ 1368.448362] ufs: ufs_fill_super(): bad magic number
[ 1368.450876] hfs: can't find a HFS filesystem on dev sdj1
[ 1584.756560] EXT4-fs (sde1): VFS: Can't find ext4 filesystem
[ 1584.757936] EXT4-fs (sde1): VFS: Can't find ext4 filesystem
[ 1584.759326] EXT4-fs (sde1): VFS: Can't find ext4 filesystem
[ 1584.760860] FAT-fs (sde1): bogus number of reserved sectors
[ 1584.760864] FAT-fs (sde1): Can't find a valid FAT filesystem
[ 1584.769420] XFS (sde1): Invalid superblock magic number
[ 1584.772785] FAT-fs (sde1): bogus number of reserved sectors
[ 1584.772805] FAT-fs (sde1): Can't find a valid FAT filesystem
[ 1584.778630] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sde1.
[ 1584.780595] hfsplus: unable to find HFS+ superblock
[ 1584.782159] qnx4: no qnx4 filesystem (no root dir).
[ 1584.783449] 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
[ 1584.784190] ufs: ufs_fill_super(): bad magic number
[ 1584.786136] hfs: can't find a HFS filesystem on dev sde1
[ 1587.351905] EXT4-fs (sdj1): VFS: Can't find ext4 filesystem
[ 1587.353848] EXT4-fs (sdj1): VFS: Can't find ext4 filesystem
[ 1587.356665] EXT4-fs (sdj1): VFS: Can't find ext4 filesystem
[ 1587.358527] FAT-fs (sdj1): bogus number of reserved sectors
[ 1587.358535] FAT-fs (sdj1): Can't find a valid FAT filesystem
[ 1587.369653] XFS (sdj1): Invalid superblock magic number
[ 1587.374185] FAT-fs (sdj1): bogus number of reserved sectors
[ 1587.374207] FAT-fs (sdj1): Can't find a valid FAT filesystem
[ 1587.380672] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sdj1.
[ 1587.383023] hfsplus: unable to find HFS+ superblock
[ 1587.384816] qnx4: no qnx4 filesystem (no root dir).
[ 1587.385995] 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
[ 1587.387210] ufs: ufs_fill_super(): bad magic number
[ 1587.389515] hfs: can't find a HFS filesystem on dev sdj1

% sudo dpkg -l grub2-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============================================-============================-============================-=================================================================================================
ii grub2-common 2.02~beta2-36 ppc64el GRand Unified Bootloader (common files for version 2)

Revision history for this message
bugproxy (bugproxy) wrote : output of 'mount and 'lsblk'

Default Comment by Bridge

tags: added: architecture-ppc64le bugnameltc-137742 severity-medium targetmilestone-inin---
Changed in ubuntu:
assignee: nobody → Taco Screen team (taco-screen-team)
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1553181/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This is more likely os-prober trying to check any other partitions for other bootable OSes on the system, and the messages in dmesg being simply the resulting failures from trying to mount a partition with the wrong filesystem.

This is purely cosmetic; I'm not sure whether it's worth spending more time that has already been spent trying to better detect the filesystem types (which will need some amounts of probing anyway), as opposed to using a workaround on the system.

The probing for other OSes can be disabled by setting GRUB_DISABLE_OS_PROBER=true in /etc/default/grub.

affects: ubuntu → os-prober (Ubuntu)
Changed in os-prober (Ubuntu):
assignee: Taco Screen team (taco-screen-team) → Mathieu Trudel-Lapierre (mathieu-tl)
status: New → Triaged
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-03-16 09:34 EDT-------
Hello Canonical,

The suggested workaround works for us. This bug can be closed.

Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.