Bug #1374759 “>>>WARNING<<< Wrong ufstype may corrupt your files...” : Bugs : os-prober package : Ubuntu

Bug Description

[ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536
[ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE].
[ 556.792231] QNX4 filesystem 0.2.3 registered.
[ 557.922469] EXT4-fs (sda4): unable to read superblock
[ 557.925868] EXT4-fs (sda4): unable to read superblock
[ 557.928967] EXT4-fs (sda4): unable to read superblock
[ 557.931784] FAT-fs (sda4): bogus number of reserved sectors
[ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 557.946740] XFS (sda4): Invalid superblock magic number
[ 557.951904] FAT-fs (sda4): bogus number of reserved sectors
[ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 557.959099] MINIX-fs: unable to read superblock
[ 557.965712] attempt to access beyond end of device
[ 557.965721] sda4: rw=16, want=3, limit=2
[ 557.965725] hfsplus: unable to find HFS+ superblock
[ 557.968487] qnx4: no qnx4 filesystem (no root dir).
[ 557.971203] You didn't specify the type of your ufs filesystem

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 557.974459] hfs: can't find a HFS filesystem on dev sda4
[ 564.034208] EXT4-fs (sda4): unable to read superblock
[ 564.040322] EXT4-fs (sda4): unable to read superblock
[ 564.043485] EXT4-fs (sda4): unable to read superblock
[ 564.047076] FAT-fs (sda4): bogus number of reserved sectors
[ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 564.059578] XFS (sda4): Invalid superblock magic number
[ 564.064473] FAT-fs (sda4): bogus number of reserved sectors
[ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 564.072080] MINIX-fs: unable to read superblock
[ 564.074564] attempt to access beyond end of device
[ 564.074571] sda4: rw=16, want=3, limit=2
[ 564.074576] hfsplus: unable to find HFS+ superblock
[ 564.076688] qnx4: no qnx4 filesystem (no root dir).
[ 564.078847] You didn't specify the type of your ufs filesystem

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 564.080902] hfs: can't find a HFS filesystem on dev sda4
[ 570.554296] EXT4-fs (sda4): unable to read superblock
[ 570.557647] EXT4-fs (sda4): unable to read superblock
[ 570.560516] EXT4-fs (sda4): unable to read superblock
[ 570.563451] FAT-fs (sda4): bogus number of reserved sectors
[ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 570.574953] XFS (sda4): Invalid superblock magic number
[ 570.580796] FAT-fs (sda4): bogus number of reserved sectors
[ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 570.588340] MINIX-fs: unable to read superblock
[ 570.590983] attempt to access beyond end of device
[ 570.590993] sda4: rw=16, want=3, limit=2
[ 570.590999] hfsplus: unable to find HFS+ superblock
[ 570.593321] qnx4: no qnx4 filesystem (no root dir).
[ 570.595556] You didn't specify the type of your ufs filesystem

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 570.597775] hfs: can't find a HFS filesystem on dev sda4
[ 576.795014] EXT4-fs (sda4): unable to read superblock
[ 576.797554] EXT4-fs (sda4): unable to read superblock
[ 576.800063] EXT4-fs (sda4): unable to read superblock
[ 576.802647] FAT-fs (sda4): bogus number of reserved sectors
[ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 576.813305] XFS (sda4): Invalid superblock magic number
[ 576.820257] FAT-fs (sda4): bogus number of reserved sectors
[ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem
[ 576.830945] MINIX-fs: unable to read superblock
[ 576.834108] attempt to access beyond end of device
[ 576.834119] sda4: rw=16, want=3, limit=2
[ 576.834125] hfsplus: unable to find HFS+ superblock
[ 576.837264] qnx4: no qnx4 filesystem (no root dir).
[ 576.840408] You didn't specify the type of your ufs filesystem

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

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-18-generic 3.16.0-18.25
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: caravena 2117 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sat Sep 27 10:39:43 2014
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2014-09-25 (2 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-18-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-18-generic N/A
linux-backports-modules-3.16.0-18-generic N/A
linux-firmware 1.134
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Tags: Edit Tag help

Cristian Aravena Romero (caravena) wrote on 2014-09-27:

AlsaInfo.txt Edit (30.1 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (54.9 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (203 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (44.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (516 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (8.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (529 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.6 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (319 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.4 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (27.6 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (246 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (140.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (317.3 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (15.7 KiB, text/plain; charset="utf-8")

Brad Figg (brad-figg) wrote on 2014-09-27: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Joseph Salisbury (jsalisbury) wrote on 2014-09-29:

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Andy Whitcroft (apw) wrote on 2014-10-09:

Ok this message is being triggered by update-grub when it calls out to os-prober to work out if you have any alternative OSs installed. The message is benign as the ufs mount fails as the partitions in question are not actually in ufs format. That said it is rather scarey.

Changed in linux (Ubuntu):
status:	Incomplete → Triaged

Andy Whitcroft (apw) wrote on 2014-10-09:

It is possible that os-prober could use the "silent" mount option to quiet these.

Cristian Aravena Romero (caravena) wrote on 2014-10-09:

dmesg_3.17.0-031700-generic.txt Edit (66.1 KiB, text/plain)

[12864.655859] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[12864.670760] JFS: nTxBlock = 8192, nTxLock = 65536
[12864.688298] ntfs: driver 2.1.30 [Flags: R/O MODULE].
[12864.719542] QNX4 filesystem 0.2.3 registered.
[12866.185482] EXT4-fs (sda4): unable to read superblock
[12866.187771] EXT4-fs (sda4): unable to read superblock
[12866.189885] EXT4-fs (sda4): unable to read superblock
[12866.192107] FAT-fs (sda4): bogus number of reserved sectors
[12866.192114] FAT-fs (sda4): Can't find a valid FAT filesystem
[12866.204926] XFS (sda4): Invalid superblock magic number
[12866.209627] FAT-fs (sda4): bogus number of reserved sectors
[12866.209634] FAT-fs (sda4): Can't find a valid FAT filesystem
[12866.216223] MINIX-fs: unable to read superblock
[12866.222480] attempt to access beyond end of device
[12866.222486] sda4: rw=16, want=3, limit=2
[12866.222490] hfsplus: unable to find HFS+ superblock
[12866.224757] qnx4: no qnx4 filesystem (no root dir).
[12866.226745] ufs: You didn't specify the type of your ufs filesystem

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

tags:

added: kernel-bug-exists-upstream

Launchpad Janitor (janitor) wrote on 2014-10-22:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in os-prober (Ubuntu):
status:	New → Confirmed

Alberto Salvia Novella (es20490446e) on 2014-11-22

Changed in os-prober (Ubuntu):
importance:	Undecided → Medium

dino99 (9d9) wrote on 2014-11-26:

Download full text (12.0 KiB)

That is what is logged into /var/log/kern.log on Vivid i386 running 3.18.0.4 (canonical-kernel-team ppa), and using ext4 partitions for lts/current/dev ubuntu os, /home is on ext3 (aka sda3) (there is no other format around on that pc) :

Nov 25 17:54:35 u32 kernel: [29589.094552] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.095944] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.097316] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.098783] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:35 u32 kernel: [29589.098786] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:35 u32 kernel: [29589.103508] XFS (sda3): Invalid superblock magic number
Nov 25 17:54:35 u32 kernel: [29589.106556] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:35 u32 kernel: [29589.106559] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:35 u32 kernel: [29589.111064] MINIX-fs: unable to read superblock
Nov 25 17:54:35 u32 kernel: [29589.112470] attempt to access beyond end of device
Nov 25 17:54:35 u32 kernel: [29589.112473] sda3: rw=16, want=3, limit=2
Nov 25 17:54:35 u32 kernel: [29589.112476] hfsplus: unable to find HFS+ superblock
Nov 25 17:54:35 u32 kernel: [29589.113914] qnx4: no qnx4 filesystem (no root dir).
Nov 25 17:54:35 u32 kernel: [29589.115265] ufs: You didn't specify the type of your ufs filesystem
Nov 25 17:54:35 u32 kernel: [29589.115265]
Nov 25 17:54:35 u32 kernel: [29589.115265] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Nov 25 17:54:35 u32 kernel: [29589.115265]
Nov 25 17:54:35 u32 kernel: [29589.115265] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Nov 25 17:54:35 u32 kernel: [29589.118051] hfs: can't find a HFS filesystem on dev sda3
Nov 25 17:54:55 u32 kernel: [29609.377181] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.378565] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.379947] EXT4-fs (sda3): unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.381458] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:55 u32 kernel: [29609.381462] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:55 u32 kernel: [29609.386248] XFS (sda3): Invalid superblock magic number
Nov 25 17:54:55 u32 kernel: [29609.389318] FAT-fs (sda3): bogus number of reserved sectors
Nov 25 17:54:55 u32 kernel: [29609.389322] FAT-fs (sda3): Can't find a valid FAT filesystem
Nov 25 17:54:55 u32 kernel: [29609.395129] MINIX-fs: unable to read superblock
Nov 25 17:54:55 u32 kernel: [29609.396744] attempt to access beyond end of device
Nov 25 17:54:55 u32 kernel: [29609.396748] sda3: rw=16, want=3, limit=2
Nov 25 17:54:55 u32 kernel: [29609.396750] hfsplus: unable to find HFS+ superblock
Nov 25 17:54:55 u32 kernel: [29609.398259] qnx4: no qnx4 filesystem (no root dir).
Nov 25 17:54:55 u32 kernel: [29609.399623] ufs: You didn't specify the type of your ufs filesystem
Nov 25 17:54:55 u32 kernel: [29609.399623]
Nov 25 17:54:55 u32 kernel: [29609.399623] mount -t ufs -o ufstype=sun...

dino99 (9d9) wrote on 2014-11-26:

/etc/fstab used on that vivid system:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb3 during installation
UUID=5d8d1ee1-f5af-40a1-a45d-dbc570808523 /home ext3 defaults 0 2
# swap was on /dev/sdb2 during installation
UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 none swap sw 0 0

dino99 (9d9) wrote on 2014-11-26:

#10

Maybe INITRD fault ? http://lists.opensuse.org/opensuse-bugs/2013-11/msg01652.html

it is not ubuntu specific, and not new : https://www.google.fr/?gfe_rd=cr&ei=dJRkU7qcGov10gXrk4DIDw&gws_rd=ssl#q=ufs:+You+didn%27t+specify+the+type+of+your+ufs+filesystem

tags:

added: i386 vivid

Launchpad Janitor (janitor) wrote on 2014-11-27:

#11

Status changed to 'Confirmed' because the bug affects multiple users.

dino99 (9d9) on 2014-11-27

affects:

initramfs-tools → initramfs-tools (Ubuntu)

Launchpad Janitor (janitor) on 2014-11-27

Changed in initramfs-tools (Ubuntu):
status:	New → Confirmed

Launchpad Janitor (janitor) on 2014-12-15

Changed in initramfs-tools (Ubuntu):
status:	New → Confirmed

Alberto Salvia Novella (es20490446e) on 2014-12-15

Changed in initramfs-tools (Ubuntu):
importance:	Undecided → Medium

NoOp (glgxg) wrote on 2015-03-15:

#13

Download full text (4.5 KiB)

Unbuntu 14.10
Mainline kernel:
3.19.0-031900-generic #201502091451 SMP Mon Feb 9 15:10:05 UTC 2015 i686 i686 i686 GNU/Linux

$ apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.103ubuntu8
  Candidate: 0.103ubuntu8
  Version table:
*** 0.103ubuntu8 0
        500 http://us.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages
        100 /var/lib/dpkg/status

[ 979.692945] JFS: nTxBlock = 8192, nTxLock = 65536
[ 979.796239] ntfs: driver 2.1.31 [Flags: R/O MODULE].
[ 979.934461] QNX4 filesystem 0.2.3 registered.
[ 980.096064] raid6: mmxx1 1646 MB/s
[ 980.164021] raid6: mmxx2 1792 MB/s
[ 980.236142] raid6: sse1x1 912 MB/s
[ 980.304024] raid6: sse1x2 1638 MB/s
[ 980.372038] raid6: sse2x1 1822 MB/s
[ 980.440038] raid6: sse2x2 1967 MB/s
[ 980.440041] raid6: using algorithm sse2x2 (1967 MB/s)
[ 980.440044] raid6: using intx1 recovery algorithm
[ 980.479294] xor: measuring software checksum speed
[ 980.516018] pIII_sse : 2751.000 MB/sec
[ 980.556014] prefetch64-sse: 3007.000 MB/sec
[ 980.556020] xor: using function: prefetch64-sse (3007.000 MB/sec)
[ 980.705772] Btrfs loaded
[ 981.590141] EXT4-fs (sda2): unable to read superblock
[ 981.593759] EXT4-fs (sda2): unable to read superblock
[ 981.596992] EXT4-fs (sda2): unable to read superblock
[ 981.600080] FAT-fs (sda2): invalid media value (0x46)
[ 981.600089] FAT-fs (sda2): Can't find a valid FAT filesystem
[ 981.731192] XFS (sda2): Invalid superblock magic number
[ 981.741261] FAT-fs (sda2): invalid media value (0x46)
[ 981.741275] FAT-fs (sda2): Can't find a valid FAT filesystem
[ 981.751163] MINIX-fs: unable to read superblock
[ 981.786303] attempt to access beyond end of device
[ 981.786313] sda2: rw=16, want=3, limit=2
[ 981.786318] hfsplus: unable to find HFS+ superblock
[ 981.791298] qnx4: no qnx4 filesystem (no root dir).
[ 981.794200] ufs: You didn't specify the type of your ufs filesystem

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 981.798772] hfs: can't find a HFS filesystem on dev sda2
[ 1593.526237] audit_printk_skb: 39 callbacks suppressed
[ 1593.526246] audit: type=1400 audit(1426434262.893:36): apparmor="DENIED" operation="open" profile="/usr/bin/evince-thumbnailer" name="/usr/bin/fix-qdf" pid=5378 comm="evince-thumbnai" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 1593.544837] audit: type=1400 audit(1426434262.913:37): apparmor="DENIED" operation="open" profile="/usr/bin/evince-thumbnailer" name="/usr/bin/fix-qdf" pid=5378 comm="evince-thumbnai" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=da28d713-0881...

Michael Ellerman (michael-ellerman) wrote on 2015-04-07:

#14

I'm seeing this on a fresh install of vivid (3.19.0-12-generic) on ppc64le:

sudo update-grub
[sudo] password for michael:
Generating grub configuration file ...
Found linux image: /boot/vmlinux-3.19.0-12-generic
Found initrd image: /boot/initrd.img-3.19.0-12-generic
[ 14.787303] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 14.789751] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 14.791951] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 14.794039] FAT-fs (sda1): bogus number of reserved sectors
[ 14.808160] FAT-fs (sda1): bogus number of reserved sectors
[ 14.823019] qnx4: no qnx4 filesystem (no root dir).
[ 14.825187] ufs: You didn't specify the type of your ufs filesystem
[ 14.825187]
[ 14.825187] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 14.825187]
[ 14.825187] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 14.826020] ufs: ufs_fill_super(): bad magic number

Jeroen Ruigrok van der Werven (asmodai) wrote on 2015-08-19:

#15

This is still happening on a fresh 15.04 install and then updating it completely with apt/aptitude. Kernel version 3.19.0-26.

dino99 (9d9) on 2015-08-19

tags:

removed: kernel-bug-exists-upstream utopic

Danfun64 (danfun360) wrote on 2015-09-04:

#16

A few weeks ago I installed xubuntu 15.04 on my computer, without this bug. After hearing about 15.10 beta 1 being released I decided to wipe the partiton and start from scratch. sudo update-grub revealed this bug. I tried installing 15.10 beta 1 again, same bug. I then decided to use the 15.04 netinstall and then install the 15.10 packages over it. Same bug. Finally, I installed 15.04 netinstall without doing the 15.10 upgrade, and I still have the same bug. What Happened?

Danfun64 (danfun360) wrote on 2015-09-12:

#17

Something I want to note. When I installed xubuntu 15.04 using netinstall before, I installed xubuntu-desktop after the netinstall. When I installed the xubuntu desktop during the installation, I avoided this bug.

Janne Savikko (jsavikko) wrote on 2015-10-01:

#18

Bug exists in Ubuntu 15.10 beta2 server. Installed the system using guided partitioning with LVM, but changed ext4 root partition filesystem to btrfs.

Jared Fernandez (jared-fernandez) on 2015-10-01

tags:

added: wily

Joel (kreuz-j-r) wrote on 2015-10-06:

#19

I had the same problem with 1504 following the aided installation which created the swap as a logical partition. I them reinstall but manually created a primary partition for the swap and can no longer reproduce the error. In both cases the '/etc/fstab' where similar.

Dominique Ramaekers (dominique-ramaekers) wrote on 2015-10-06:

#20

I also have this issue with a Ubuntu 15.04 on a HP server with 3 disks in raid 5. It seems grub wants to test on one of the disks of my raid. This is really scary. Grub seems to want to mount the second disk of the raid separately???
Linux CmsrvVH3 3.19.0-30-generic #33-Ubuntu SMP Mon Sep 21 20:58:04 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
See log below...

(I have a the same server also with Ubuntu 14.04.3 LTS with 4 disks in raid 5 and 4 disks in raid 10. Here I don't have this issue.
Linux CmsrvVH2 3.19.0-30-generic #33~14.04.1-Ubuntu SMP Tue Sep 22 09:27:00 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux)

Oct 6 03:36:04 CmsrvVH3 kernel: [49638.681667] QNX4 filesystem 0.2.3 registered.
Oct 6 03:36:04 CmsrvVH3 kernel: [49638.684795] Request for unknown module key 'Magrathea: Glacier signing key: 08411dd668c266d59a96c625b3012497b2351542' err -11
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.928320] EXT4-fs (cciss!c0d0p2): unable to read superblock
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.960826] EXT4-fs (cciss!c0d0p2): unable to read superblock
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.962326] EXT4-fs (cciss!c0d0p2): unable to read superblock
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.963760] FAT-fs (cciss/c0d0p2): bogus number of reserved sectors
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.963853] FAT-fs (cciss/c0d0p2): Can't find a valid FAT filesystem
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.970120] XFS (cciss/c0d0p2): Invalid superblock magic number
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.972479] FAT-fs (cciss/c0d0p2): bogus number of reserved sectors
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.972569] FAT-fs (cciss/c0d0p2): Can't find a valid FAT filesystem
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.976369] MINIX-fs: unable to read superblock
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.978463] Request for unknown module key 'Magrathea: Glacier signing key: 08411dd668c266d59a96c625b3012497b2351542' err -11
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.983525] attempt to access beyond end of device
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.983528] cciss/c0d0p2: rw=16, want=3, limit=2
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.983531] hfsplus: unable to find HFS+ superblock
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.984786] qnx4: no qnx4 filesystem (no root dir).
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.986333] ufs: You didn't specify the type of your ufs filesystem
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.986333]
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.986333] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.986333]
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.986333] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Oct 6 03:36:05 CmsrvVH3 kernel: [49639.991044] hfs: can't find a HFS filesystem on dev cciss/c0d0p2

mrl586 (mrl586) on 2015-12-22

tags:

added: xenial

David Favor (davidfavor) wrote on 2015-12-22:

#21

This is a very ugly bug.

Sometimes this causes reboots to hang for long periods. Just timed it on a Wily system with all upgrades installed.

Takes 157 seconds, to shutdown system.

Above comments only mention 3.19 (Vivid) kernels. This problem persists in Wily...

net4-dev# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily

net4-dev# uname -a
Linux net4.bizcooker.com 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

David Favor (davidfavor) wrote on 2015-12-22:

#22

I see this bug is tagged xenial. Please post a fix which can be added to Wily, to escape the long shudown delay.

Thanks.

Josu Lazkano (josu-lazkano) wrote on 2016-01-06:

#23

Same happens in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772526

If you are not using multi boot, just remove the "os-prober" and it should work.

Regards.

Marko Stanković (sm4rk0) wrote on 2016-03-02:

#24

update the remote watch

Bug Watch Updater (bug-watch-updater) on 2016-03-02

Changed in os-prober (Debian):
status:	Unknown → Fix Released

Thiago Martins (martinx) wrote on 2016-03-08:

#25

I'm seeing this BUG on most recent Xenial Beta release (updated today).

Stefan Bader (smb) wrote on 2016-03-08:

#26

skip-msdos-extpart-sooner.debdiff Edit (1.2 KiB, text/plain)

Hm, so while in Xenial we did move to os-prober 1.70 (the Debian bug was closed by 1.68) it seems the check for it might be too late (50mounted-tests sound like a place that will never be reached as any attempt to mount the extended partition will be unsuccessful, of course *after* all the scary messages emitted during the mount attempts).

I believe the following addition directly in os-prober will do the trick. At least it seems to be good in local testing.

Ubuntu Foundations Team Bug Bot (crichton) on 2016-03-08

tags:

added: patch

Stefan Bader (smb) wrote on 2016-03-08:

#27

Also, just to confirm and clarify the bug report. It looks like the only package that would need to be fixed in the end is os-prober. Neither initramfs-tools nor the kernel need changes, right?

Phillip Susi (psusi) on 2016-03-09

no longer affects:	initramfs-tools (Ubuntu)
no longer affects:	linux (Ubuntu)

Phillip Susi (psusi) wrote on 2016-03-09:

#28

Looks like this was fixed upstream in 1.68 and Xenial has 1.70 so it should now be fixed.

Changed in os-prober (Ubuntu):
status:	Confirmed → Fix Released

Stefan Bader (smb) wrote on 2016-03-09:

#29

Phillip, sorry this is wrong. See comments #25 and #26

Changed in os-prober (Ubuntu):
status:	Fix Released → Confirmed

Stefan Bader (smb) wrote on 2016-03-09:

#30

Thiago, I was wondering whether you were able to confirm that the changes I was proposing in comment #26 would be looking good for you as well?

Doug Smythies (dsmythies) wrote on 2016-03-09:

#31

Stefan, the patch proposed in comment #26 works on my test 16.04 server.

Launchpad Janitor (janitor) wrote on 2016-03-11:

#32

This bug was fixed in the package os-prober - 1.70ubuntu3

---------------
os-prober (1.70ubuntu3) xenial; urgency=low

* Check for MSDOS extended partitions and skip any further tests which
would require the partition to be mounted (LP: #1374759).

-- Stefan Bader <email address hidden> Tue, 08 Mar 2016 09:35:20 +0100

Changed in os-prober (Ubuntu):
status:	Confirmed → Fix Released

Ross Patterson (rossp) wrote on 2016-07-14:

#33

This is still happening on my xenial system with os-prober 1.70.

Ross Patterson (rossp) wrote on 2016-07-14:

#34

In my case these same errors are happening when trying to probe a Windows recovery partition on a dual boot system. I've worked around this bug by adding the following content to /usr/lib/os-probes/00skip-unknown:

#!/bin/sh
# Skip unknown partitions to avoid syslog errors
set -e
partition="$1"

. /usr/share/os-prober/common.sh

if [ "$partition" = /dev/<your-recovery-partition-here> ]; then
debug "$partition is a Windows recovery partition; skipping"
exit 0
fi

# No tests found anything.
exit 1

Stefan Bader (smb) wrote on 2016-07-18:

#35

Ross, I would suggest to open a new bug report (run "ubuntu-bug os-prober"). Although the resulting symptoms (error messages) are the same, it is caused by a different case. Which needs more info to avoid. The snippet above does not work in the general case. Which means to avoid it automatically this needs more info about what to avoid.

David Favor (davidfavor) wrote on 2016-07-22: Re: [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

#36

Ross Patterson wrote:
> This is still happening on my xenial system with os-prober 1.70.

Still happens at boot time in Xenial too.

Vadim (hurryup) wrote on 2017-01-12:

#37

I still have the same problem.

I have grub2 + gpt + bios_grub 1Mb partition and every time when I install/delete a kernel I get:

Jan 12 10:59:08 h8 kernel: [34066.102516] SGI XFS with ACLs, security attributes, realtime, no debug enabled
Jan 12 10:59:08 h8 kernel: [34066.115584] JFS: nTxBlock = 8192, nTxLock = 65536
Jan 12 10:59:08 h8 kernel: [34066.145895] ntfs: driver 2.1.32 [Flags: R/O MODULE].
Jan 12 10:59:08 h8 kernel: [34066.180082] QNX4 filesystem 0.2.3 registered.
Jan 12 10:59:08 h8 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda1
Jan 12 10:59:08 h8 kernel: [34066.359360] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
Jan 12 10:59:08 h8 kernel: [34066.360493] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
Jan 12 10:59:08 h8 kernel: [34066.361601] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
Jan 12 10:59:08 h8 kernel: [34066.362843] squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda1
Jan 12 10:59:08 h8 kernel: [34066.363954] FAT-fs (sda1): invalid media value (0x7d)
Jan 12 10:59:08 h8 kernel: [34066.363969] FAT-fs (sda1): Can't find a valid FAT filesystem
Jan 12 10:59:08 h8 kernel: [34066.368287] XFS (sda1): Invalid superblock magic number
Jan 12 10:59:08 h8 kernel: [34066.370213] FAT-fs (sda1): invalid media value (0x7d)
Jan 12 10:59:08 h8 kernel: [34066.370228] FAT-fs (sda1): Can't find a valid FAT filesystem
Jan 12 10:59:08 h8 kernel: [34066.372862] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda1.
Jan 12 10:59:08 h8 kernel: [34066.379273] hfsplus: unable to find HFS+ superblock
Jan 12 10:59:08 h8 kernel: [34066.380230] qnx4: no qnx4 filesystem (no root dir).
Jan 12 10:59:08 h8 kernel: [34066.380955] ufs: You didn't specify the type of your ufs filesystem
Jan 12 10:59:08 h8 kernel: [34066.380955]
Jan 12 10:59:08 h8 kernel: [34066.380955] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Jan 12 10:59:08 h8 kernel: [34066.380955]
Jan 12 10:59:08 h8 kernel: [34066.380955] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Jan 12 10:59:08 h8 kernel: [34066.381543] ufs: ufs_fill_super(): bad magic number
Jan 12 10:59:08 h8 kernel: [34066.382849] hfs: can't find a HFS filesystem on dev sda1
Jan 12 10:59:08 h8 os-prober: debug: /dev/sda2: part of software raid array
Jan 12 10:59:08 h8 os-prober: debug: /dev/sda3: part of software raid array
Jan 12 10:59:08 h8 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdb1

And so on for all bios_grub partitions sd[a-d]1

Vadim (hurryup) wrote on 2017-01-12:

#38

uname -a
Linux h8 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

os-prober 1.70ubuntu3 amd64

Ubuntu
os-prober package

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

Bug Description

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntuos-prober package

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

Bug Description

Duplicates of this bug

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntu
os-prober package