Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30
Package: initramfs-tools Version: 0.93.4 Severity: critical Justification: breaks the whole system I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system over the new kernel. I still can boot it from the old 2.6.26 kernel. My root disk is on a mirror raid based on 2 SCSI disk. The boot process stopsand gives a message to the effect that the file system is unavailable. I have an extended knowledge on hardware (I used to be a DEC/Compaq/HP harware support engineer on pdp11/VAX/alpha under VMS and Tru64). I have no indepth knowledge of the linux system. I think there is a problem with the initramfs-tools because there is no mdadm.conf describing my md devices... In fact there is no mdadm directory under etc in the initrd.img-2.6.30.2.686 created by the upgrade. -- Package-specific info: -- /proc/cmdline root=/dev/md0 ro -- /proc/filesystems ext3 ext2 reiserfs xfs jfs msdos vfat ntfs minix hfs hfsplus qnx4 ufs -- lsmod Module Size Used by nls_utf81760 0 nls_cp437 5568 0 ufs64804 0 qnx47812 0 hfsplus66212 0 hfs37124 0 minix 23972 0 ntfs 185792 0 vfat9184 0 msdos 6944 0 fat40896 2 vfat,msdos jfs 148812 0 nls_base6820 8 nls_utf8,nls_cp437,hfsplus,hfs,ntfs,vfat,fat,jfs xfs 457976 0 reiserfs 189888 0 ext2 54504 0 ppdev 6500 0 lp 8164 0 cpufreq_userspace 3172 0 cpufreq_conservative 5960 0 cpufreq_stats 3776 0 cpufreq_ondemand6476 0 cpufreq_powersave 1856 0 freq_table 4224 2 cpufreq_stats,cpufreq_ondemand ipv6 235364 14 binfmt_misc 7528 1 loop 12748 0 mt20xx 10824 1 tea5767 6020 0 tda9887 9348 1 tda829012164 0 tuner 21960 0 msp340025260 0 bttv 148116 0 snd_via82xx20664 1 videodev 27520 3 tuner,msp3400,bttv snd_ac97_codec 88484 1 snd_via82xx v4l1_compat12260 1 videodev firmware_class 6816 1 bttv ac97_bus1728 1 snd_ac97_codec ir_common 39620 1 bttv snd_pcm62596 2 snd_via82xx,snd_ac97_codec compat_ioctl32 1312 1 bttv snd_page_alloc 7816 2 snd_via82xx,snd_pcm i2c_algo_bit5188 1 bttv snd_mpu401_uart 6368 1 snd_via82xx v4l2_common10240 3 tuner,msp3400,bttv videobuf_dma_sg11140 1 bttv i2c_viapro 6836 0 snd_seq_midi5728 0 videobuf_core 16100 2 bttv,videobuf_dma_sg via_ircc 15764 0 snd_seq_midi_event 6432 1 snd_seq_midi snd_rawmidi18528 2 snd_mpu401_uart,snd_seq_midi btcx_risc 4264 1 bttv snd_seq41456 2 snd_seq_midi,snd_seq_midi_event snd_timer 17800 2 snd_pcm,snd_seq snd_seq_device 6380 3 snd_seq_midi,snd_rawmidi,snd_seq tveeprom 10980 1 bttv irda 95512 1 via_ircc parport_pc 22500 1 parport30988 3 ppdev,lp,parport_pc psmouse32336 0 ns558 3712 0 gameport 10700 3 snd_via82xx,ns558 snd45604 10 snd_via82xx,snd_ac97_codec,snd_pcm,snd_mpu401_uart,snd_rawmidi,snd_seq,snd_timer,snd_seq_device serio_raw 4740 0 soundcore 6368 1 snd crc_ccitt 2080 1 irda pcspkr 2432 0 button 6096 0 shpchp 25528 0 i2c_core 19828 11 mt20xx,tea5767,tda9887,tda8290,tuner,msp3400,bttv,i2c_algo_bit,v4l2_common,i2c_viapro,tveeprom pci_hotplug23460 1 shpchp via_agp 7744 1 agpgart28776 1 via_agp evdev 8000 7 ext3 105512 2 jbd39444 1 ext3 mbcache 7108 2 ext2,ext3 raid456 117264 1 async_xor 3520 1 raid456 async_memcpy2304 1 raid456 async_tx6316 3 raid456,async_xor,async_memcpy xor14696 2 raid456,async_xor raid1 18016 2 md_mod 67068 5 raid456,raid1 ide_cd_mod 27652 0 cdrom 30176 1 ide_cd_mod ide_disk 10496 0 ata_generic 4676 0 libata140416 1 ata_generic dock8304 1 libata sd_mod 22200 16 via82cxxx 6948 0
Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30
also sprach Louis Richard Pirlet lrpir...@gmail.com [2010.01.22.0952 +1300]: I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system over the new kernel. I still can boot it from the old 2.6.26 kernel. My root disk is on a mirror raid based on 2 SCSI disk. The boot process stopsand gives a message to the effect that the file system is unavailable. Have you tried the rootdelay parameter? I think there is a problem with the initramfs-tools because there is no mdadm.conf describing my md devices... In fact there is no mdadm directory under etc in the initrd.img-2.6.30.2.686 created by the upgrade. This is not good but mdadm's initramfs is designed to work anyway. Once your system boots, it would be good to find out what's going on. Is there an /etc/mdadm/mdadm.conf there? -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Processed: Re: Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30
Processing commands for cont...@bugs.debian.org: reassign 566192 mdadm Bug #566192 [initramfs-tools] initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30 Bug reassigned from package 'initramfs-tools' to 'mdadm'. Bug No longer marked as found in versions initramfs-tools/0.93.4. severity 566192 grave Bug #566192 [mdadm] initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30 Severity set to 'grave' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30
reassign 566192 mdadm severity 566192 grave thanks On Thu, Jan 21, 2010 at 09:52:08PM +0100, Louis Richard Pirlet wrote: I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system over the new kernel. I still can boot it from the old 2.6.26 kernel. My root disk is on a mirror raid based on 2 SCSI disk. The boot process stopsand gives a message to the effect that the file system is unavailable. I have an extended knowledge on hardware (I used to be a DEC/Compaq/HP harware support engineer on pdp11/VAX/alpha under VMS and Tru64). I have no indepth knowledge of the linux system. I think there is a problem with the initramfs-tools because there is no mdadm.conf describing my md devices... In fact there is no mdadm directory under etc in the initrd.img-2.6.30.2.686 created by the upgrade. Inclusion of mdadm.conf in initramfs is the responsibility of the mdadm hook, not of initramfs-tools itself. Reassigning. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
