Unknown file system warning messages during dist-upgrade operation

[bugproxy]

== Comment: #0 - SACHIN P. SANT <email address hidden> - 2015-01-28 06:06:54 ==
---Problem Description---
LVM & Unknown file system related warning messages during dist-upgrade operation

Contact Information = Sachin Sant / <email address hidden>

---uname output---
3.18.0-11-generic

Machine Type = POWER8

---Debugger---
A debugger is not configured

---Steps to Reproduce---
 1) Install Ubuntu 15.04 as a Power VM guest. I have used LVM based partition scheme during installation.
2) Post installation execute following commands :

apt-get update
apt-get dist-upgrade

While installing kernel package following warnings are displayed

Preparing to unpack .../linux-headers-3.18.0-11_3.18.0-11.12_all.deb ...
Unpacking linux-headers-3.18.0-11 (3.18.0-11.12) ...
Preparing to unpack .../linux-headers-3.18.0-11-generic_3.18.0-11.12_ppc64el.deb
 ...
Preparing to unpack .../linux-headers-generic_3.18.0.11.11_ppc64el.deb ...
Setting up libudev1:ppc64el (218-6ubuntu1) ...
udev stop/waiting
update-initramfs: deferring update (trigger activated)
Setting up libpam-systemd:ppc64el (218-6ubuntu1) ...
Setting up linux-image-3.18.0-11-generic (3.18.0-11.12) ...
update-initramfs: deferring update (hook will be called later)
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-11-generic /
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.18.0-11-generic /b
update-initramfs: Generating /boot/initrd.img-3.18.0-11-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.18.0-11-generic /bo
ot/vmlinux-3.18.0-11-generic
Generating grub configuration file ...
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8548: /usr/
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8548: /usr/
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8561: /usr/
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8561: /usr/
sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8574: /usr/
sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8574: /usr/
sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8587: /usr/
sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8587: /usr/
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 8646: /usr/
sbin/grub-probe
sbin/grub-probe
Found linux image: /boot/vmlinux-3.18.0-11-generic
Found initrd image: /boot/initrd.img-3.18.0-11-generic
Found linux image: /boot/vmlinux-3.18.0-9-generic
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 9079: /usr/
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 9079: /usr/
sbin/grub-probe
sh
[ 218.672660] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 218.675001] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 218.682513] FAT-fs (sda1): bogus number of reserved sectors
[ 218.695908] ufs: You didn't specify the type of your ufs filesystem
[ 218.695908] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextst
[ 218.695908]
is ufstype=old
done
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-11-generic /
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.18.0-11-generic /b
update-initramfs: Generating /boot/initrd.img-3.18.0-11-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.18.0-11-generic /bo
ot/vmlinux-3.18.0-11-generic
Generating grub configuration file ...
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15190: /usr
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15190: /usr
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15203: /usr
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15203: /usr
/sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15216: /usr
/sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15216: /usr
/sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15229: /usr
/sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15229: /usr
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15288: /usr
/sbin/grub-probe
/sbin/grub-probe
Found linux image: /boot/vmlinux-3.18.0-11-generic
Found initrd image: /boot/initrd.img-3.18.0-11-generic
Found linux image: /boot/vmlinux-3.18.0-9-generic
Found initrd image: /boot/initrd.img-3.18.0-9-generic
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15721: /usr
/sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on vgs invocation. Parent PID 15721: /usr
/sbin/grub-probe
File descriptor 26 (/dev/pts/0) leaked on lvs invocation. Parent PID 15815: /bin
/sh
[ 227.011930] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 227.013277] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 227.014432] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 227.015527] FAT-fs (sda1): bogus number of reserved sectors
[ 227.021841] FAT-fs (sda1): bogus number of reserved sectors
[ 227.027658] qnx4: no qnx4 filesystem (no root dir).
[ 227.028538] ufs: You didn't specify the type of your ufs filesystem
[ 227.028538]
[ 227.028538] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextst
ep|nextstep-cd|openstep ...
[ 227.028538]
[ 227.028538] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default
is ufstype=old
[ 227.029039] ufs: ufs_fill_super(): bad magic number
done
Setting up linux-image-generic (3.18.0.11.11) ...
Setting up linux-headers-3.18.0-11 (3.18.0-11.12) ...
Setting up linux-headers-3.18.0-11-generic (3.18.0-11.12) ...
Setting up linux-headers-generic (3.18.0.11.11) ...
Setting up perl-modules (5.20.1-5) ...
Setting up perl (5.20.1-5) ...
Processing triggers for libc-bin (2.19-13ubuntu3) ...
Processing triggers for initramfs-tools (0.103ubuntu9) ...
update-initramfs: Generating /boot/initrd.img-3.18.0-11-generic
root@lop824:~#

*Additional Instructions for Sachin Sant / <email address hidden>:
-Post a private note with access information to the machine that the bug is occuring on.
-Attach:
  /proc/partitions
  /proc/mounts/
  /etc/lvm/lvm.conf
  dmsetup ls
  dmsetup table
  dmsetup targets
  dmsetup version
  lvm version

Apart from these warnings there is no problem.

root@lop824:~# uname -r
3.18.0-11-generic

== Comment: #1 - SACHIN P. SANT <email address hidden> - 2015-01-28 06:07:37 ==
root@lop824:~# cat /proc/partitions
major minor #blocks name

  11 0 572960 sr0
   8 0 104857600 sda
   8 1 7168 sda1
   8 2 249856 sda2
   8 3 104598528 sda3
 252 0 6832128 dm-0
 252 1 4046848 dm-1
 252 2 93704192 dm-2

root@lop824:~# cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=2544192k,nr_inodes=39753,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=518400k,mode=755 0 0
/dev/mapper/lop824--vg-root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
none /sys/fs/cgroup tmpfs rw,relatime,size=64k,mode=755 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0
none /sys/fs/pstore pstore rw,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset,clone_children 0 0
cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct,release_agent=/run/cgmanager/agents/cgm-release-agent.cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory,release_agent=/run/cgmanager/agents/cgm-release-agent.memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices,release_agent=/run/cgmanager/agents/cgm-release-agent.devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer,release_agent=/run/cgmanager/agents/cgm-release-agent.freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,relatime,net_cls,release_agent=/run/cgmanager/agents/cgm-release-agent.net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio,release_agent=/run/cgmanager/agents/cgm-release-agent.blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event 0 0
cgroup /sys/fs/cgroup/net_prio cgroup rw,relatime,net_prio,release_agent=/run/cgmanager/agents/cgm-release-agent.net_prio 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb 0 0
lxcfs /var/lib/lxcfs fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/sda2 /boot ext2 rw,relatime 0 0
/dev/mapper/lop824--vg-home /home ext4 rw,relatime,data=ordered 0 0
/dev/mapper/lop824--vg-root /var/lib/docker/aufs ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
systemd /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/powerpc64le-linux-gnu/systemd-shim-cgroup-release-agent,name=systemd 0 0
tmpfs /run/user/0 tmpfs rw,nosuid,nodev,relatime,size=518400k,mode=700 0 0
root@lop824:~#

== Comment: #2 - SACHIN P. SANT <email address hidden> - 2015-01-28 06:08:42 ==
root@lop824:~# dmsetup table
lop824--vg-root: 0 13664256 linear 8:3 2048
lop824--vg-swap_1: 0 8093696 linear 8:3 13666304
lop824--vg-home: 0 187408384 linear 8:3 21760000

root@lop824:~# dmsetup ls
lop824--vg-root (252:0)
lop824--vg-swap_1 (252:1)
lop824--vg-home (252:2)

root@lop824:~# dmsetup version
Library version: 1.02.90 (2014-09-01)
Driver version: 4.28.0
root@lop824:~#

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1416396/+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.]

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-02-27 04:47 EDT-------
Hello Ubuntu,

Any comments/updates on this?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-04-16 06:51 EDT-------
Any updates on this?

[Mathieu Trudel-Lapierre (cyphermox)]

Could you also include the output for 'sudo fdisk -l' or 'sudo parted -l' ?

There is just one thing I'm not sure I understand properly. Are there any adverse side-effects encountered as you run dist-upgrade? Or is this bug only about the messages seen on the console but the upgrade process appears to complete successfully? It wasn't clear to me which was the case from the bug description.

If it's just cosmetic, it's probably the PReP partition that is confusing things. We can work around this directly in grub.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-06-23 18:56 EDT-------
(In reply to comment #13)
> Could you also include the output for 'sudo fdisk -l' or 'sudo parted -l' ?
>
> There is just one thing I'm not sure I understand properly. Are there any
> adverse side-effects encountered as you run dist-upgrade? Or is this bug
> only about the messages seen on the console but the upgrade process appears
> to complete successfully? It wasn't clear to me which was the case from the
> bug description.
>
> If it's just cosmetic, it's probably the PReP partition that is confusing
> things. We can work around this directly in grub.

There are no side-effects that I have encountered due to these warnings. The upgrade process completes successfully.

I will try to collect the output for fdisk -l / parted -l

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-07-03 09:18 EDT-------
Here is the requested data. This is captured with 15.10 release.

# fdisk -l
Disk /dev/vda: 80 GiB, 85899345920 bytes, 167772160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9D61740F-7959-4AFC-86C8-3B0F60C24E9E

Device Start End Sectors Size Type
/dev/vda1 2048 16383 14336 7M unknown
/dev/vda2 16384 516095 499712 244M Linux filesystem
/dev/vda3 516096 167770111 167254016 79.8G Linux LVM

Disk /dev/mapper/ub1510--vg-root: 76.4 GiB, 82065752064 bytes, 160284672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/ub1510--vg-swap_1: 3.3 GiB, 3527409664 bytes, 6889472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
#

parted o/p

# parted -l
Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ub1510--vg-root: 82.1GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 82.1GB 82.1GB ext4

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ub1510--vg-swap_1: 3527MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 3527MB 3527MB linux-swap(v1)

Model: Virtio Block Device (virtblk)
Disk /dev/vda: 85.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 8389kB 7340kB prep
2 8389kB 264MB 256MB ext2
3 264MB 85.9GB 85.6GB lvm

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-09-01 15:31 EDT-------
Hello Ubuntu,

Any comments/updates on this?

[Launchpad Janitor (janitor)]

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]

[Mathieu Trudel-Lapierre (cyphermox)]

Right, looks like this is probably grub-probe not being happy while it tries to probe the PReP partition. I'll need to look at how we could skip over it or otherwise avoid the errors.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-03-08 00:16 EDT-------
This issue is seen on Ubuntu 16.04 while doing dist-upgrade operation to upgrade from 4.4.0-8-generic -> 4.4.0-11-generic

Kernel version : 4.4.0-8-generic

[413567.554671] EXT4-fs (vda1): VFS: Can't find ext4 filesystem
[413567.556233] EXT4-fs (vda1): VFS: Can't find ext4 filesystem
[413567.557655] EXT4-fs (vda1): VFS: Can't find ext4 filesystem
[413567.558982] FAT-fs (vda1): bogus number of reserved sectors
[413567.566500] FAT-fs (vda1): bogus number of reserved sectors
[413567.575724] qnx4: no qnx4 filesystem (no root dir).
[413567.576994] ufs: You didn't specify the type of your ufs filesystem
[413567.576994]
[413567.576994] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[413567.576994]
[413567.576994] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[413567.577599] ufs: ufs_fill_super(): bad magic number
done

[Montblanc (montblanc)]

Same very identical warnings appeared in my case too when dist-upgrading xenial from 4.4.0-24 to 4.4.0-25.

[Andrew Cloke (andrew-cloke)]

Still assigned to taco-screen-team. Screen team reviewed and asked Foundations team to investigate.

[Mathieu Trudel-Lapierre (cyphermox)]

This isn't a grub2 bug, but an issue caused by the way os-prober does the filesystem probing to display other installs in the grub menu. I'm setting both the grub2 and os-prober tasks to "Won't Fix": if we really want to make these messages disappear, the changes will not happen in os-prober or grub2.

The ideal solution to this is to deactivate os-prober on the system; otherwise a lot of effort may be needed to reduce the severity of the messages (although they are relevant, and certainly meaningful, if someone goes to mount a filesystem with the wrong type). To figure out whether another install exists on the disks, os-prober needs to do some probing and mounting of the filesystems (we can't use only the partition table to guess the filesystem) to see if there are kernels, or configuration files, it understands and to read them to know what the other operating system is.

My recommendation is to set GRUB_DISABLE_OS_PROBER=true in /etc/default/grub to disable probing if no other operating systems are installed on this system; then no probing will happen on upgrades, so no messages will show up on the console.

[Phillip Susi (psusi)]

Actually, os-prober is exactly where this needs fixed. It should be using the silent mount option to suppress these messages. This use case is exactly what that option is for. For that matter, it really should not be war dialing mounts but should instead use blkid to see if there is a filesystem there to mount, and what kind it is if so.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-07-10 21:26 EDT-------
Any updates on this