kernel-packages team mailing list archive

[A1an <1209423@xxxxxxxxxxxxxxxxxx>]

Answering questions from the above linked bug:

> It's possible that the patches which were linked are not related.
They're not in the delta between the two versions which are isted.

I see, I did not realize the kernel versions (using a dot for the last
digits) are different from the ubuntu ones (using a -).

> 1. You mention that this occurs on various upgrades, could you confirm
that these would be various different kernel versions over time, and not
ONLY on the 46 to 47 update?

Indeed I tested it with each new update from 47 to 50 (current one) and
the issue is there on all of them while booting into 46 works fine

> 2. Have you seen this when doing any other reboots (not after system updates)?
> (such as might occur if this was a boot race - which could only shows up because the first boot after an update performs additional operations)

No, booting with 46 always bring the md0 array up while others 47-50
always fail to do so.


> 3. When this occurs you mention that you see the 'M' for manual recovery, do you also see the MD "degraded raid" prompt and if so how do you respond?

I did not try manual recovery (did not want to broke the array by
manipulating it with potentially "unsafe" environment)

> 4. On taking the 'M' that option LVM slices are missing which are
served from the RAID, can you provide the following information for
missing LVs (backed by md0):

I do not have LVM on my RAID device as the original reporter of the
other bug. One of the following applies however:

  E) what is the actual state of md0 as show in 'cat /proc/mdstat'?

md0 is not listed at all in /proc/mdstat


Furthermore I attach (mdadm-examine-broken.txt) the output of mdadm --examine on one of the RAID elements (/dev/sda6) which looks quite weird to me with a long series of failed where there should be only two elements in the array.


** Attachment added: "Output of mdadm --examine on a component of md0"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+attachment/3764186/+files/mdadm-examine-broken.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1209423

Title:
  [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at
  boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After update from 2.6.32-46 to 2.6.32-47 one of the md arrays does not
  start anymore at boot time. The RAID 1 md0 now causes message
  "Continue to wait; or Press S to skip mounting or M for manual
  recovery" at boot. I used "S" to create this report as requested in a
  similar bug report
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295) by user
  "penalvch"

  Booting back into 2.6.32-46 the md devices are correctly set up and
  the system boots normally. See the linked bug for further details,
  such as:

  The array that does not start anymore has the following config:
  level=raid1 metadata=1.2 num-devices=2

  While a second array with metadata=1.0 seems to be recognized and
  started correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-50-generic 2.6.32-50.112
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26
  Uname: Linux 2.6.32-50-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  alan       1991 F.... pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6220000 irq 22'
     Mixer name	: 'Realtek ALC888'
     Components	: 'HDA:10ec0888,80860034,00100202'
     Controls      : 28
     Simple ctrls  : 16
  Date: Thu Aug  8 02:01:09 2013
  HibernationDevice: RESUME=UUID=b1649a13-fffd-4e98-b42b-a5e9ea98f9fc
  InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-50-generic root=UUID=e69dddfa-14a0-499f-9267-edca27fbd7a4 ro quiet splash
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34.14
  RfKill:
   0: hci0: Bluetooth
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8192s_usb
  Title: [STAGING]
  dmi.bios.date: 04/19/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WBIBX10J.86A.0293.2010.0419.1819
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE64798-207
  dmi.chassis.type: 2
  dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0293.2010.0419.1819:bd04/19/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr:

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