Description of problem: Software raid is not started from fstab Version-Release number of selected component (if applicable): upstart-0.3.9-15.fc9.i386 How reproducible: always Steps to Reproduce: 1.boot-up 2. 3. Actual results: Drives are not found in /etc/fstab Expected results: drives to be mounted Additional info: manually running 'dmraid -ay' results in a perfect start.
What could have changed to cause this?
This has nothing to do with upstart. This is the job of mkinitrd?
Please attach /proc/partitions and /proc/mdstat after a successful boot, as well as the output of 'dmsetup ls', so we can assign this to the proper component.
I see at boot, Mounting other Filesystems :mount failed for /dev/mapper/pdc_bjebbjhcb1 mount failed for /dev/mapper/pdc_jgabafbj1 [FAILED] These are the drives I have listed in fstab. /proc/partitions is attached from boot. /proc/mdstat Personalities : unused devices: <none> dmsetup ls shows no devices. after dmraid -ay dmsetup ls shows pdc_bjebbjhcb1 (253, 3) pdc_bjebbjhcb (253, 1) pdc_jgabafbj (253, 0) pdc_jgabafbj1 (253, 2)
Created attachment 301721 [details] partitions
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
workaround: using dmraid -ay in /etc/rc.local for now.
Out of curiousity - what happens if you try the initscripts package currently in updates-testing?
No change with initscripts-8.76.2-1.i386 at start up. I'm also now being flooded with these messages: attempt to access beyond end of device sdc: rw=0, want=320159171, limit=160086528 Buffer I/O error on device sdc1, logical block 160079553 attempt to access beyond end of device sdc: rw=0, want=320159173, limit=160086528 Buffer I/O error on device sdc1, logical block 160079554 attempt to access beyond end of device sdc: rw=0, want=320159175, limit=160086528 attempt to access beyond end of device sdc: rw=0, want=320159369, limit=160086528 attempt to access beyond end of device sdc: rw=0, want=320159371, limit=160086528 attempt to access beyond end of device sdc: rw=0, want=320159373, limit=160086528 attempt to access beyond end of device sdc: rw=0, want=320159375, limit=160086528 [snip] where sdc & sdd 2x80Gb make up the fake raid.
wait I've been seeing this for sometime in rawhide also look at this dmesg: https://bugzilla.redhat.com/attachment.cgi?bugid=440189&action=viewall
I hit a similar issue after adding 3 hard disks to an already installed F9 x86_64 system. The disks make up an md RAID 5 array with LVM on top. Nothing I did with mkinitrd or fstab would ever bring up the array on boot, however when I created an /etc/mdadm.conf file it all started working and I was pretty sure I never had the config file before and it was just all autodetected. I still have the old system the drives came out of I can take a look at to grab any old config files if needed, but it all seems to work great now. I was always able to bring up the array & logical volumes manually by doing: mdadm -auto-detect pvscan vgchange -a y
Ok its getting worse, no kernel newer than 2.6.25.3-18.fc9 will boot all fail with this error, (hand written) Loading ata_generic module -"- dm_mod module device-mapper:uevent:ver 1.0.3 -"- :ioctl:4.13 .... @redhat Loading dm-mirror -"- dm-zero -"- dm-snapshot device-mapper:table:253:0:stripped:couldnt parse strip destination -"- :ioctl:error adding target to table -"- :reload ioctl failed:no such device -"- :table:253:0:linear:dm-linear:device lookup failed -"- :ioctl:error adding target to table -"- :reload ioctl failed:invalid argument -"- :table ioctl failed:no such device or address -"- :deps ioctl failed:no such device or address init[1]:segfault @ 10 ip 006d30fa sp bfbfbdfc error 4 in libdevmapper.so.1.02 more stuff about nash blowing up then freeze. kernel 2.6.25.6-55.fc9.i686
The opeing comment shows it's not a dmraid issue. Was the initrd updated properly ? If not so, outdated mapping tables could be used..
Thanks for replying Yes that sounds logical dmraid will start but only after manual intervention. I've also rebuilt initrd for all failing kernels which rules that out. As for mapping tables I have no knowledge of, if you can provide any test for me to perform or further information needed I'll do it but if nobody else has any ideas alpha 10 is here I'll try again. (Sulphur stinks!)
/etc/rc.d/rc.sysinit still checks for the old software raid instead of md If you replace if [ -f /etc/raidtab ]; then if [ -f /proc/mdstat -a -f /etc/raidtab ]; then (...) _RUN_QUOTACHECK=0 by if [ -f /proc/mdstat -a -f /etc/mdadm.conf ]; then echo $"Starting up RAID devices: " /sbin/mdadm --assemble --scan RETURN=$? # A non-zero return means there were problems. if [ $RETURN -gt 0 ]; then echo echo echo $"*** An error occurred during the RAID startup" echo $"*** Dropping you to a shell; the system will reboot" echo $"*** when you leave the shell." PS1=$"(RAID Repair) \# # "; export PS1 sulogin echo $"Unmounting file systems" umount -a mount -n -o remount,ro / echo $"Automatic reboot in progress." reboot -f fi fi _RUN_QUOTACHECK=0 The problem is solved. FWIIW, also applies to Red Hat
Herta, I'm not sure what version you're quoting there, but it's not Fedora 9.
times up!!!