[Kernel-packages] [Bug 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Just curious, why is that still incomplete? Any info still missing? -- 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: Incomplete 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: USERPID 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 0xf622 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Attached the --examine for the other component of the array (sdc1), it shows similar output. ** Attachment added: Output of mdadm --examine on the other component of md0 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+attachment/3789526/+files/mdadm-examine-broken2.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: Incomplete 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: USERPID 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 0xf622 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
@Stefan: --scan command might be useless but thanks anyway since it helped me noticing the issue that make me solve it :) Here is the output of the scan command and the relevant content of the config file: $ sudo mdadm --misc --scan --detail ARRAY /dev/md0 level=raid1 num-devices=2 metadata=01.02 name=alan-desktop:0 UUID=d5119bd2:7491e0f3:df5db333:6e036bee ARRAY /dev/md3 level=raid1 num-devices=2 metadata=01.00 name=pca3:3 UUID=154f648b:6076c08b:76f5610a:9fbce7c7 $ cat /etc/mdadm/mdadm.conf | grep ARRAY ARRAY /dev/md/0 level=raid1 metadata=1.2 num-devices=2 UUID=d5119bd2:7491e0f3:df5db333:6e036bee name=pca3:1 ARRAY /dev/md/3 level=raid1 metadata=1.0 num-devices=2 UUID=154f648b:6076c08b:76f5610a:9fbce7c7 name=pca3:3 As you can see there is a mismatch in the configured and scanned names, the latter coming from the array creation since long ago. Now, I have no idea why they differ however changing the one in the config file to match the scanned one made the array build up at boot again. Just confirmed with 2.6.32-50-generic So, to reproduce the issue its probably enough to change the array name into mdadm.conf. A last notice/recommendation: I do not understand why there is a need for array information to be placed into a configuration file and even more why to rely so much on it, such a config file will belong to a single system while arrays would be used also in multi-boot environments or have to be read also from recovery system used to boot a machine. I think relying on metadata on the drives only to be a far better approach. Thank you for helping in solving the issue and let me know if you need more info for further development. -- 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: Incomplete 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: USERPID 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 0xf622 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1209423] [NEW] [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Public bug reported: 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: USERPID 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 0xf622 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: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kconfig lucid needs-upstream-testing regression-update staging -- 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: New 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: USERPID 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 0xf622 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
[Kernel-packages] [Bug 1190295] Re: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)
@penalvch New bug filed as requested: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423 PS: I did not realize the kernel versions (using a dot for the last digits) are different from the ubuntu ones (using a -). I'll also answer latest questions by sconklin on the new bugreport. -- 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/1190295 Title: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM) Status in “linux” package in Ubuntu: Incomplete Bug description: Been running 10.04 LTS on 8 similar AMD Opteron x86_64 servers for several years. The servers have been kept up-to-date with patches as they come out. These servers have been running 2.6.x kernels. Each server has some form of Linux software RAID running on it as well as 3Ware hardware RAID card using SATA disks. Software RAID is configured as RAID1 for all but one server running software RAID10. All servers had software raid configured to use single partitions on each disk of types of 0xFD (Linux Software Raid Autodetect). All servers were configured with LVM over the top of /dev/md0. In past year, mysterious problems have been happening with software RAID after applying system patches. Upon reboot, server is unable to mount LVM partitions on Linux software RAID and boot is interrupted with Continue to wait; or Press S to skip mounting or M for manual recovery requiring intervention from an operator. Upon pressing 'M' and logging in as root, the LVM slices on the software RAID partition are not mounted and sometimes appear to be missing from LVM. Oftentimes pvs, vgs and lvs will complain about leaking memory. Germane to the issue, LVM will sometimes show the problem partitions as Active while other times during the login, they will simply be gone. With LVM and /dev/md0 unstable, there is no way to discern the true state of the partitons in question. Starting the system from alternate boot media such as CDROM or USB drive, sometimes shows the software RAID and LVM in proper state which leads to suspicion of a kernel update on the afflicted system. Historically and subjectively, best practice in this instance seems to be booting from live media and starting the array degraded mode, and backing up the array. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
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: USERPID 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 0xf622 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 -- Mailing list:
[Kernel-packages] [Bug 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Just rebooted into -46 and noticed that the output of mdadm --examine /dev/sda6 seems exactly the same and shows the same long series of failed (so it might be normal for 1.2 metadata?). -- 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: USERPID 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 0xf622 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1190295] Re: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)
I see and I'll try to flie the new report as soon as possible, even though I think it is the same cause as this one. I've had a look at the kernel log and see that only two patches affected the md component between 2.6.32-46 (working kernel) and 2.6.32-47 (broken kernel, reported in this bug): https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-2.6.32.yid=c28f366a6ef9b6e14e069e7d750c32d7354e https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-2.6.32.yid=372994e9fd5cadbacdfcc8724b590193d136c947 A notification to the author might help solve this even quicker. -- 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/1190295 Title: 2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM) Status in “linux” package in Ubuntu: Incomplete Bug description: Been running 10.04 LTS on 8 similar AMD Opteron x86_64 servers for several years. The servers have been kept up-to-date with patches as they come out. These servers have been running 2.6.x kernels. Each server has some form of Linux software RAID running on it as well as 3Ware hardware RAID card using SATA disks. Software RAID is configured as RAID1 for all but one server running software RAID10. All servers had software raid configured to use single partitions on each disk of types of 0xFD (Linux Software Raid Autodetect). All servers were configured with LVM over the top of /dev/md0. In past year, mysterious problems have been happening with software RAID after applying system patches. Upon reboot, server is unable to mount LVM partitions on Linux software RAID and boot is interrupted with Continue to wait; or Press S to skip mounting or M for manual recovery requiring intervention from an operator. Upon pressing 'M' and logging in as root, the LVM slices on the software RAID partition are not mounted and sometimes appear to be missing from LVM. Oftentimes pvs, vgs and lvs will complain about leaking memory. Germane to the issue, LVM will sometimes show the problem partitions as Active while other times during the login, they will simply be gone. With LVM and /dev/md0 unstable, there is no way to discern the true state of the partitons in question. Starting the system from alternate boot media such as CDROM or USB drive, sometimes shows the software RAID and LVM in proper state which leads to suspicion of a kernel update on the afflicted system. Historically and subjectively, best practice in this instance seems to be booting from live media and starting the array degraded mode, and backing up the array. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
