← Back to team overview

kernel-packages team mailing list archive

[Bug 1103187] Re: xfs left inconsistent after reboot, causing grub to fail


as per your :
[    0.000000] Your BIOS doesn't leave a aperture memory hole
[    0.000000] Please enable the IOMMU option in the BIOS setup
[    0.000000] This costs you 64 MB of RAM
[    0.338295] mtrr: your CPUs had inconsistent variable MTRR settings
[    0.338296] mtrr: probably your BIOS does not setup all CPUs.

Hence, as per http://support.asus.com/download.aspx?SLanguage=en&m=M4A89GTD%20PRO/USB3&os=29 an update is available for your BIOS (3029). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it doesn't, could you please both specify what happened, and just provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see

Thank you for your understanding.

** Tags added: bios-outdated-3029

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  xfs left inconsistent after reboot, causing grub to fail

Status in “grub2” package in Ubuntu:
Status in “linux” package in Ubuntu:

Bug description:
  take a 12.10 with XFS root partition containing the /boot/ tree
  dpkg-reconfigure grub-pc ; sync
  reboot (either by command, or by menu)
  diverse error messages + grub rescue + /boot/ is partially accessible

  boot UBUNTU 12.10 pendrive + choose "try Ubuntu" + open a terminal
  sudo -s; mkdir foo; mount [the XFS root partition] foo; umount foo
  reboot into the "original" Ubuntu is NOW successful

  It appears that the kernel xfs filesystem driver leaves the fs in an inconsistent state even after a sync.  That is corrected by a journal playback done either via having the kernel mount or running fsck, but grub does not use the xfs journal.
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
   /dev/snd/controlC1:  prohlep    1969 F.... pulseaudio
   /dev/snd/controlC0:  prohlep    1969 F.... pulseaudio
   /dev/snd/seq:        timidity   1533 F.... timidity
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  DistroRelease: Ubuntu 12.10
  InstallationDate: Installed on 2012-10-19 (98 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
   eth0      no wireless extensions.
   lo        no wireless extensions.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  Package: linux
  PackageArchitecture: amd64
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=39082c0a-8360-4ade-8f2e-f557a8a65035 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/prohlep not ours.
   No PulseAudio daemon running, or not running as session daemon.
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware                            1.95
  Tags:  quantal package-from-proposed
  Uname: Linux 3.5.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to: