Looks like this is NOT a filesystem issue: - mounted /dev/drbd1 and it behaves properly - did an fsck on /dev/drbd1 and it came back as clean
Digging a little deeper, looking at the console messages for a similarly configured domU, what I see is: ..... [ 31.088678] EXT3 FS on xvda1, internal journal [ 42.316654] NET: Registered protocol family 10 ..... I seem to be hanging right after mounting root, and just before networking starts up. Which brings me to two questions: 1. any thoughts on debugging network startup in a domU 2. my original question: how do I insert myself into the boot process - e.g., to bring the domU up in single-user mode, etc.? Petri Asikainen wrote: > Have you tried to mount/fsck filesystem xvd from dom0? > >> Hi Folks, >> >> I'm running (what's supposed to be) a 2-node high-availability >> configuration consisting of: >> - Xen3.x >> - Debian Stable Dom0 on each node >> - DRBD >> - Pacemaker >> - several Debian Stable DomUs >> >> One of my DomUs seems to have crashed and is stubbornly refusing to >> boot. On either node, it comes part way up and then hangs, with the >> (virtual) console reporting: >> >> .... >> [ 2.387986] EXT3-fs: mounted filesystem with ordered data mode. >> Begin: Running /scripts/local-bottom ... done. >> done. >> Begin: Running /scripts/init-bottom ... done. >> INIT: version 2.86 booting >> Starting the hotplug events dispatcher: udevd[ 5.467529] udevd >> version 125 started >> . >> Synthesizing the initial hotplug events...done. >> Waiting for /dev to be fully populated...done. >> Starting boot logger: bootlogd[ 6.190409] Adding 3145588k swap on >> /dev/xvda2. Priority:-1 extents:1 across:3145588k >> [ 89.796051] EXT3 FS on xvda1, internal journal >> <hang> >> >> I've also tried stopping it on one node, booting it on the other; reboot >> the underlying nodes; etc. >> >> The underlying RAID10 and DRBD arrays are reporting themselves as >> healthy, and during the boot process DRBD seems to shift from secondary >> to primary. >> >> So.... I know how I might proceed if I were booting a physical machine >> - try to come up in single user mode, failing that, boot with a live CD >> and start examining things. But with everything wired with CRM and Xen >> in the middle of the boot process, I'm a little lost as to how to insert >> myself into the domU boot process for diagnostic purposes. >> >> Any suggestions? >> >> Thanks very much, >> >> Miles Fidelman >> >> p.s. What makes this particularly vexing is that the DomU that refuses >> to come up has no purpose in life other than to handle nightly backups >> of other domUs. Sigh... >> >> -- >> In theory, there is no difference between theory and practice. >> In<fnord> practice, there is. .... Yogi Berra >> >> >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems >> > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > -- In theory, there is no difference between theory and practice. In<fnord> practice, there is. .... Yogi Berra _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
