[colug-432] fedora 17 kernels broke with raid system.

[Vince Herried]

Any one know where to post diagnosis info.

I'm seeing

Attempt to boot kernel-PAE-3.8.11-100.fc17.i686 gives me.
.
.
.
[ OK ] Started Monitoring of LVM2 mirrons,snapsshots etc. ....
[ TIME ] Timed out waiting for device dev-md125p3.device
[ DEPEND ] Dependency failed for /mnt/Win.
[ DEPEND ] Dependency failed for Local File System
[ DEPEND ] Dependency failed for Relabel all filesystems, if necessary.
[ DEPEND ] Dependency failed for Mark the need  to relabel after reboot.
Welcome to emergency mode. Use "systemctl default" or ^D to enter default
mode.
Give root password for maintence
(or type Control-D to continue)




after reboot I get raid out of sync problem....


May  5 14:17:30 lap3 kernel: [    3.198468] sdhci-pci 0000:03:01.2: SDHCI
controller found [1180:0822] (rev 21)
May  5 14:17:30 lap3 kernel: [    3.202043] md: bind<sdb>
May  5 14:17:30 lap3 kernel: [    3.202181] md: bind<sda>
May  5 14:17:30 lap3 kernel: [    3.204162] md: raid1 personality
registered for level 1
May  5 14:17:30 lap3 kernel: [    3.204357] md/raid1:md125: not clean --
starting background reconstruction
May  5 14:17:30 lap3 kernel: [    3.204360] md/raid1:md125: active with 2
out of 2 mirrors
May  5 14:17:30 lap3 kernel: [    3.204372] md125: detected capacity change
from 0 to 320070483968
May  5 14:17:30 lap3 kernel: [    3.211523]  md125: p1 p2 p3 p4 < p5 >
May  5 14:17:30 lap3 kernel: [    3.224096] mmc0: SDHCI controller on PCI
[0000:03:01.2] using DMA
May  5 14:17:30 lap3 kernel: [    3.227797] md: md125 switched to
read-write mode.
May  5 14:17:30 lap3 kernel: [    3.227918] md: resync of RAID array md125
May  5 14:17:30 lap3 kernel: [    3.227920] md: minimum _guaranteed_
speed: 1000 KB/sec/disk.
May  5 14:17:30 lap3 kernel: [    3.227922] md: using maximum available
idle IO bandwidth (but not more than 200000 KB/sec) for resync.
May  5 14:17:30 lap3 kernel: [    3.227924] md: using 128k window, over a
total of 312568964k.





and my raid is out of sync.
dmesg gives...
[    3.202043] md: bind<sdb>
[    3.202181] md: bind<sda>
[    3.204162] md: raid1 personality registered for level 1
[    3.204357] md/raid1:md125: not clean -- starting background
reconstruction
[    3.204360] md/raid1:md125: active with 2 out of 2 mirrors
[    3.204372] md125: detected capacity change from 0 to 320070483968
[    3.211523]  md125: p1 p2 p3 p4 < p5 >
[    3.224096] mmc0: SDHCI controller on PCI [0000:03:01.2] using DMA
[    3.227797] md: md125 switched to read-write mode.
[    3.227918] md: resync of RAID array md125
[    3.227920] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[    3.227922] md: using maximum available idle IO bandwidth (but not more
than 200000 KB/sec) for resync.
[    3.227924] md: using 128k window, over a total of 312568964k.


later...  i see:

[root at lap3 ~]# cat /proc/mdstat
Personalities : [raid1]
md125 : active raid1 sda[1] sdb[0]
      312568832 blocks super external:/md127/0 [2/2] [UU]
      [====>................]  resync = 20.7% (64950336/312568964)
finish=89.6min speed=46021K/sec

md127 : inactive sda[1](S) sdb[0](S)
      4520 blocks super external:imsm

unused devices: <none>
[root at lap3 ~]#



[root at lap3 ~]# ls -l /dev/md*
brw-rw---- 1 root disk   9, 125 May  5 14:17 /dev/md125
brw-rw---- 1 root disk 259,   0 May  5 14:17 /dev/md125p1
brw-rw---- 1 root disk 259,   1 May  5 14:17 /dev/md125p2
brw-rw---- 1 root disk 259,   2 May  5 14:17 /dev/md125p3
brw-rw---- 1 root disk 259,   3 May  5 14:17 /dev/md125p4
brw-rw---- 1 root disk 259,   4 May  5 14:17 /dev/md125p5
brw-rw---- 1 root disk   9, 127 May  5 14:17 /dev/md127

/dev/md:
total 12
-rw-r--r-- 1 root root   4 May  5 14:17 autorebuild.pid
-rw------- 1 root root   4 May  5 14:17 md127.pid
srwxr-xr-x 1 root root   0 May  5 14:17 md127.sock
-rw------- 1 root root 125 May  5 14:17 md-device-map
lrwxrwxrwx 1 root root   8 May  5 14:17 Volume0 -> ../md125
lrwxrwxrwx 1 root root  10 May  5 14:17 Volume0p1 -> ../md125p1
lrwxrwxrwx 1 root root  10 May  5 14:17 Volume0p2 -> ../md125p2
lrwxrwxrwx 1 root root  10 May  5 14:17 Volume0p3 -> ../md125p3
lrwxrwxrwx 1 root root  10 May  5 14:17 Volume0p4 -> ../md125p4
lrwxrwxrwx 1 root root  10 May  5 14:17 Volume0p5 -> ../md125p5
[root at lap3 ~]#



----------
A boot from  kernel-PAE-3.8.8-100.fc17.i686
and kernel-PAE-3.8.11-100.fc17.i686
fail but
3.8.4-102.fc17.i686.PAE

I don't want to have to stop installing kernel updates?
I discovered the problem with 3.8.8.100 and hoped for the best with next
one that
came along, sigh apparently was not to be...

So where to post this document so that it gets to the proper kernel folks?


-- 
Vince's outgoing mail address
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.colug.net/pipermail/colug-432/attachments/20130505/67e4d1ea/attachment-0001.html