running debian etch; drbd v0.7; along with HA; under ext3 filesystems; <br>
<p>both system were running fine, and drbd was working great. <br> assuming there was a power outage, now when I bring up the primary <br> system I get (during boot): <br> </p>
<div id="qhide_90906" style="display: block;" class="qt"> >><br></div>
fsck.ext3: no such file or directory while trying to open /dev/drbd0 <br>
the superblock could not be read or does not describe a correct ext2 <br>
filesystem. <br>
fsck died with exit status 8 ....[snip]... superblock may be <br>
corrupt. <br>
<< <br>
<p>/dev/drbd0 is drbd's device to /dev/sdb1; which DOES fsck PERFECTLY. (and I ran a forced check to ensure all bits say OK)<br> </p>
<p>this system isn't even coming up to runlevel 2... going into maint. <br> mode.... <br> </p>
What I believe is happening is: the drbd module isn't being loaded before the system boot process wants to run fsck process...<br>
I'm pretty sure this was working before power event; but not 100% sure...<br>
What I don't understand is: if this is true - why didn't the
installation of drbd make sure that modprobe drbd took place before any
fsck??<br>
<br>
And - what's the best way to fix this? I'm not 100% sure how the boot
process works, so I'm not sure what scripts might need to be mod'ed...<br>
<br>
Any help appreciated...<br>
TIA - Bob<br>
<br>
<br>