Bug 539273 - SATA RAID0 - Unbootable after F11->F12 upgrade with F12 kernel, F11 kernel OK
Summary: SATA RAID0 - Unbootable after F11->F12 upgrade with F12 kernel, F11 kernel OK
Keywords:
Status: CLOSED DUPLICATE of bug 539325
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-19 19:03 UTC by giles
Modified: 2009-11-19 21:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 539325 (view as bug list)
Environment:
Last Closed: 2009-11-19 21:19:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description giles 2009-11-19 19:03:26 UTC
Description of problem:
I have a VIA VT8237 SATA RAID controller, RAID-0 on two 250Gb disks. Has been working fine on F11. I upgraded from the commandline F11->F12, after boot I get 'no root device, sleeping forever'.

Rebooting and selecting an older F11 kernel boots OK.

Version-Release number of selected component (if applicable):
old kernel boots OK: 
2.6.30.9-90.fc11.x86_64
new kernel boot fails:
2.6.31.5-127.fc12.x86_64

Also, from the F12 install CD Anaconda reports that the disks must be initialized so no RAID appears not to be detected.

How reproducible:

Steps to Reproduce:
1. upgraded F11->F12 from commandline
2. reboot
  
Actual results:
boot halts 'no root device, sleeping forever'

Expected results:
boots

Additional info:
I read a similar bug id=522076, maybe related?

Here's some commands:

[root@katana giles]# parted /dev/mapper/via_djbccigdhe
GNU Parted 1.9.0
Using /dev/mapper/via_djbccigdhe
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p                                                                
Model: Linux device-mapper (striped) (dm)
Disk /dev/mapper/via_djbccigdhe: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type      File system  Flags
 1      32.3kB  210MB  210MB  primary   ext3         boot
 2      214MB   105GB  105GB  extended
 5      214MB   105GB  105GB  logical                lvm
 3      105GB   315GB  210GB  primary   ext4
 4      315GB   500GB  185GB  primary   ntfs

[giles@katana ~]$ sudo cat /boot/grub/menu.lst
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/mapper/VolGroup-lv_root
#          initrd /initrd-version.img
#boot=/dev/via_djbccigdhe
default=2
timeout=15
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.31.5-127.fc12.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.31.5-127.fc12.x86_64 ro root=/dev/mapping/VolGroup-lv_root
	initrd /initramfs-2.6.31.5-127.fc12.x86_64.img
title Fedora (2.6.31.5-122.fc12.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.31.5-122.fc12.x86_64 ro root=/dev/mapper/VolGroup-lv_root SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=uk
	initrd /initramfs-2.6.31.5-122.fc12.x86_64.img
title Fedora-base (2.6.30.9-90.fc11.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.30.9-90.fc11.x86_64 ro root=/dev/mapper/VolGroup-lv_root
	initrd /initrd-2.6.30.9-90.fc11.x86_64.img
title Other
	rootnoverify (hd0,3)
	chainloader +1

[root@katana giles]# blkid -o udev -p /dev/mapper/VolGroup-lv_root 
ID_FS_UUID=7da72cc3-e416-4c95-89eb-99d5934f95f0
ID_FS_UUID_ENC=7da72cc3-e416-4c95-89eb-99d5934f95f0
ID_FS_VERSION=1.0
ID_FS_TYPE=ext4
ID_FS_USAGE=filesystem

[root@katana giles]# rpm -q dmraid
dmraid-1.0.0.rc16-4.fc12.x86_64
[root@katana giles]# rpm -q dracut 
dracut-002-13.4.git8f397a9b.fc12.noarch
[root@katana giles]# rpm -qf /usr/share/dracut/modules.d/* | sort -u  
dracut-002-13.4.git8f397a9b.fc12.noarch

Comment 1 giles 2009-11-19 21:19:16 UTC

*** This bug has been marked as a duplicate of bug 539325 ***


Note You need to log in before you can comment on or make changes to this bug.