<br><br><div><span class="gmail_quote">On 2/19/06, <b class="gmail_sendername">Justin Conover</b> <<a href="mailto:justin.conover@gmail.com">justin.conover@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="e" id="q_10982ad2ccb4a210_0"><br><br><div><span class="gmail_quote">On 2/19/06, <b class="gmail_sendername">Justin Conover</b> <<a href="mailto:justin.conover@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
justin.conover@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span><br><br><div><span class="gmail_quote">On 2/18/06, <b class="gmail_sendername">Justin Conover</b> <<a href="mailto:justin.conover@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
justin.conover@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span><br><br><div><span class="gmail_quote">On 2/18/06, <b class="gmail_sendername">Justin Conover</b> <<a href="mailto:justin.conover@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
justin.conover@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I can't boot the kernel-xen-hypervisor on one of my systems. It bombs out when it wants to mount my /home<br>Which is a RAID 5 with LVM, "can't find superblock", however a normal kernel boots fine.<br><br><br>
<br>
lsmod | egrep 'ata|raid'<br>raid5 27585 1<br>xor 18249 1 raid5<br>raid1 24513 2<br>sata_sil 13641 4<br>libata 58189 1 sata_sil<br>scsi_mod 129257 5 sg,aic7xxx,scsi_transport_spi,libata,sd_mod
<br><br>
</blockquote></div><br></span></div>ls initrd-2.6.15-1.1955_FC5smp/lib/<br>aic7xxx.ko dm-snapshot.ko jbd.ko sata_sil.ko sd_mod.ko<br>dm-mirror.ko dm-zero.ko libata.ko scsi_mod.ko<br>dm-mod.ko
ext3.ko
raid1.ko scsi_transport_spi.ko<br><br>ls initrd-2.6.15-1.1955_FC5hypervisor/lib/<br>aic7xxx.ko dm-snapshot.ko jbd.ko sata_sil.ko sd_mod.ko<br>dm-mirror.ko dm-zero.ko libata.ko scsi_mod.ko<br>dm-mod.ko
ext3.ko raid1.ko scsi_transport_spi.ko<br><br><br>Same stuff is being loaded<br>
</blockquote></div><br><br></span></div>I thought it might have been just a bad raid5 when I built it after the install so I re-installed it. Same problem<br><br>fsck.ext3: Invalid argument while trying to open /dev/md2
<br>/dev/md2:
<br>The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
<br>e2fsck -b 8193 <device><br><br><br><br>Any ideas? Both md0/md1 boot fine and they are raid1's is there something about raid5 the xen kernel might not like?<br>
</blockquote></div><br></span></div>Some stuff from dmesg about md2 with the normal kernel booting it.<br><br>md: considering sdd1 ...<br>md: adding sdd1 ...<br>md: adding sdc1 ...<br>md: adding sdb1 ...<br>md: adding sda1 ...
<br>
md: created md2<br>md: bind<sda1><br>md: bind<sdb1><br>md: bind<sdc1><br>md: bind<sdd1><br>md: running: <sdd1><sdc1><sdb1><sda1><br>md: personality for level 5 is not loaded!
<br>md: do_md_run() returned -22<br>md: md2 stopped.<br>md: unbind<sdd1><br>md: export_rdev(sdd1)<br>md: unbind<sdc1><br>md: export_rdev(sdc1)<br>md: unbind<sdb1><br>md: export_rdev(sdb1)<br>md: unbind<sda1>
<br>md: export_rdev(sda1)<br>md: ... autorun DONE.<br>kjournald starting. Commit interval 5 seconds<br>EXT3-fs: mounted filesystem with ordered data mode.<br><br><SNIP><br><br>md: Autodetecting RAID arrays.<br>md: autorun ...
<br>md: considering sda1 ...<br>md: adding sda1 ...<br>md: adding sdb1 ...<br>md: adding sdc1 ...<br>md: adding sdd1 ...<br>md: created md2<br>md: bind<sdd1><br>md: bind<sdc1><br>md: bind<sdb1><br>md: bind<sda1>
<br>md: running: <sda1><sdb1><sdc1><sdd1><br>raid5: automatically using best checksumming function: pIII_sse<br> pIII_sse : 1733.000 MB/sec<br>raid5: using function: pIII_sse (1733.000 MB/sec)
<br>
md: raid5 personality registered for level 5<br>md: raid4 personality registered for level 4<br>raid5: device sda1 operational as raid disk 0<br>raid5: device sdb1 operational as raid disk 1<br>raid5: device sdc1 operational as raid disk 2
<br>raid5: device sdd1 operational as raid disk 3<br>raid5: allocated 4206kB for md2<br>raid5: raid level 5 set md2 active with 4 out of 4 devices, algorithm 2<br>RAID5 conf printout:<br> --- rd:4 wd:4 fd:0<br> disk 0, o:1, dev:sda1
<br> disk 1, o:1, dev:sdb1<br> disk 2, o:1, dev:sdc1<br> disk 3, o:1, dev:sdd1<br>md: ... autorun DONE.<br><br><SNIP><br><br>EXT3 FS on md2, internal journal<br>EXT3-fs: mounted filesystem with ordered data mode.<br>
SELinux: initialized (dev md2, type ext3), uses xattr<br><br>
</blockquote></div><br>Normal kernel<br><br>dumpe2fs /dev/md2 | grep Backup<br>dumpe2fs 1.38 (30-Jun-2005)<br> Backup superblock at 32768, Group descriptors at 32769-32812<br> Backup superblock at 98304, Group descriptors at 98305-98348
<br> Backup superblock at 163840, Group descriptors at 163841-163884<br> Backup superblock at 229376, Group descriptors at 229377-229420<br> Backup superblock at 294912, Group descriptors at 294913-294956<br> Backup superblock at 819200, Group descriptors at 819201-819244
<br> Backup superblock at 884736, Group descriptors at 884737-884780<br> Backup superblock at 1605632, Group descriptors at 1605633-1605676<br> Backup superblock at 2654208, Group descriptors at 2654209-2654252<br> Backup superblock at 4096000, Group descriptors at 4096001-4096044
<br> Backup superblock at 7962624, Group descriptors at 7962625-7962668<br> Backup superblock
at 11239424, Group descriptors at 11239425-11239468<br> Backup superblock at 20480000, Group descriptors at 20480001-20480044<br> Backup superblock at 23887872, Group descriptors at 23887873-23887916<br> Backup superblock at 71663616, Group descriptors at 71663617-71663660
<br> Backup superblock at 78675968, Group descriptors at 78675969-78676012<br> Backup superblock at 102400000, Group descriptors at 102400001-102400044<br><br> fsck.ext3 /dev/md2<br>e2fsck 1.38 (30-Jun-2005)<br>/dev/md2: clean, 11/91586560 files, 2925310/183146928 blocks
<br><br>e2fsck -b 32768 /dev/md2<br>e2fsck 1.38 (30-Jun-2005)<br>/dev/md2 was not cleanly unmounted, check forced.<br>Pass 1: Checking inodes, blocks, and sizes<br>Pass 2: Checking directory structure<br>Pass 3: Checking directory connectivity
<br>Pass 4: Checking reference counts<br>Pass 5: Checking group summary information<br><br>/dev/md2: ***** FILE SYSTEM WAS MODIFIED *****<br>/dev/md2: 11/91586560 files (9.1%
non-contiguous), 2925310/183146928 blocks<br>