<div dir="ltr"><div><div dir="ltr"><br></div>Any one know where to post diagnosis info.<br><br></div>I'm seeing<br><br clear="all"><div><div>Attempt to boot kernel-PAE-3.8.11-100.fc17.i686 gives me.<br>.<br>.<br>.<br>[ OK ] Started Monitoring of LVM2 mirrons,snapsshots etc. ....<br>
[ TIME ] Timed out waiting for device dev-md125p3.device<br>[ DEPEND ] Dependency failed for /mnt/Win.<br>[ DEPEND ] Dependency failed for Local File System<br>[ DEPEND ] Dependency failed for Relabel all filesystems, if necessary.<br>
[ DEPEND ] Dependency failed for Mark the need to relabel after reboot.<br>Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.<br>Give root password for maintence<br>(or type Control-D to continue)<br>
<br><br><br><br>after reboot I get raid out of sync problem....<br><br><br>May 5 14:17:30 lap3 kernel: [ 3.198468] sdhci-pci 0000:03:01.2: SDHCI controller found [1180:0822] (rev 21)<br>May 5 14:17:30 lap3 kernel: [ 3.202043] md: bind<sdb><br>
May 5 14:17:30 lap3 kernel: [ 3.202181] md: bind<sda><br>May 5 14:17:30 lap3 kernel: [ 3.204162] md: raid1 personality registered for level 1<br>May 5 14:17:30 lap3 kernel: [ 3.204357] md/raid1:md125: not clean -- starting background reconstruction<br>
May 5 14:17:30 lap3 kernel: [ 3.204360] md/raid1:md125: active with 2 out of 2 mirrors<br>May 5 14:17:30 lap3 kernel: [ 3.204372] md125: detected capacity change from 0 to 320070483968<br>May 5 14:17:30 lap3 kernel: [ 3.211523] md125: p1 p2 p3 p4 < p5 ><br>
May 5 14:17:30 lap3 kernel: [ 3.224096] mmc0: SDHCI controller on PCI [0000:03:01.2] using DMA<br>May 5 14:17:30 lap3 kernel: [ 3.227797] md: md125 switched to read-write mode.<br>May 5 14:17:30 lap3 kernel: [ 3.227918] md: resync of RAID array md125<br>
May 5 14:17:30 lap3 kernel: [ 3.227920] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.<br>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.<br>
May 5 14:17:30 lap3 kernel: [ 3.227924] md: using 128k window, over a total of 312568964k.<br><br><br><br><br><br>and my raid is out of sync.<br>dmesg gives...<br>[ 3.202043] md: bind<sdb><br>[ 3.202181] md: bind<sda><br>
[ 3.204162] md: raid1 personality registered for level 1<br>[ 3.204357] md/raid1:md125: not clean -- starting background reconstruction<br>[ 3.204360] md/raid1:md125: active with 2 out of 2 mirrors<br>[ 3.204372] md125: detected capacity change from 0 to 320070483968<br>
[ 3.211523] md125: p1 p2 p3 p4 < p5 ><br>[ 3.224096] mmc0: SDHCI controller on PCI [0000:03:01.2] using DMA<br>[ 3.227797] md: md125 switched to read-write mode.<br>[ 3.227918] md: resync of RAID array md125<br>
[ 3.227920] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.<br>[ 3.227922] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.<br>[ 3.227924] md: using 128k window, over a total of 312568964k.<br>
<br><br>later... i see:<br><br>[root@lap3 ~]# cat /proc/mdstat<br>Personalities : [raid1]<br>md125 : active raid1 sda[1] sdb[0]<br> 312568832 blocks super external:/md127/0 [2/2] [UU]<br> [====>................] resync = 20.7% (64950336/312568964) finish=89.6min speed=46021K/sec<br>
<br>md127 : inactive sda[1](S) sdb[0](S)<br> 4520 blocks super external:imsm<br><br>unused devices: <none><br>[root@lap3 ~]#<br><br><br><br>[root@lap3 ~]# ls -l /dev/md*<br>brw-rw---- 1 root disk 9, 125 May 5 14:17 /dev/md125<br>
brw-rw---- 1 root disk 259, 0 May 5 14:17 /dev/md125p1<br>brw-rw---- 1 root disk 259, 1 May 5 14:17 /dev/md125p2<br>brw-rw---- 1 root disk 259, 2 May 5 14:17 /dev/md125p3<br>brw-rw---- 1 root disk 259, 3 May 5 14:17 /dev/md125p4<br>
brw-rw---- 1 root disk 259, 4 May 5 14:17 /dev/md125p5<br>brw-rw---- 1 root disk 9, 127 May 5 14:17 /dev/md127<br><br>/dev/md:<br>total 12<br>-rw-r--r-- 1 root root 4 May 5 14:17 autorebuild.pid<br>-rw------- 1 root root 4 May 5 14:17 md127.pid<br>
srwxr-xr-x 1 root root 0 May 5 14:17 md127.sock<br>-rw------- 1 root root 125 May 5 14:17 md-device-map<br>lrwxrwxrwx 1 root root 8 May 5 14:17 Volume0 -> ../md125<br>lrwxrwxrwx 1 root root 10 May 5 14:17 Volume0p1 -> ../md125p1<br>
lrwxrwxrwx 1 root root 10 May 5 14:17 Volume0p2 -> ../md125p2<br>lrwxrwxrwx 1 root root 10 May 5 14:17 Volume0p3 -> ../md125p3<br>lrwxrwxrwx 1 root root 10 May 5 14:17 Volume0p4 -> ../md125p4<br>lrwxrwxrwx 1 root root 10 May 5 14:17 Volume0p5 -> ../md125p5<br>
[root@lap3 ~]#<br><br><br><br>---------- <br></div><div>A boot from kernel-PAE-3.8.8-100.fc17.i686<br>and kernel-PAE-3.8.11-100.fc17.i686<br>fail but<br>3.8.4-102.fc17.i686.PAE<br><br></div><div>I don't want to have to stop installing kernel updates?<br>
</div><div>I discovered the problem with 3.8.8.100 and hoped for the best with next one that<br>came along, sigh apparently was not to be...<br><br></div><div>So where to post this document so that it gets to the proper kernel folks?<br>
<br></div><div><br></div><div>-- <br>Vince's outgoing mail address
</div></div></div>