From: Gordan B. <go...@bo...> - 2007-10-11 16:20:56
|
On Thu, 11 Oct 2007, Marc Grimme wrote: >> OK - my fault - I had done something stupid. >> I touched /etc/sysconfig/comoonics-chroot to silence the warning at time >> of building the initrd. >> I have now instead removed the inclusion of this file, and that gets >> further - it actually mount the GFS file system on /mnt/newroot! :-) >> >> It then proceeds to boot the GFS setup! :-) >> >> Then it deems to get stuck, printing endlessly: >> dlm: root: remove fr 0 ID 3 >> >> Now what... > > Good question ;-) > No we are in GFS/DLM. Which packages of GFS/DLM combi are you using and can > you manually mount the fs? (com-step before) No, wait - it was just me making a schoolbody mistake again. :-) I forgot to switch off the eth1 (iSCSI SAN) interface at boot-time, along with the iscsi inits (because they were started up by the initrd image). Switched those off and now it boots fully! :-) It throws up a worrying error when it boots: GFS: fsid=cluster:root.0: warning: assertion "gfs_glock_is_locked_by_me(ip->i_gl)" failed GFS: fsid=cluster:root.0 function = gfs_readpage GFS: fsid=cluster:root.0 file = /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/ops_address.c, line 279 GFS: fsid=cluster:root.0: time = 1192119131 I wonder if this may be caused by a file system perhaps not having been cleanly unmounted on a previous try while I was building it... Gordan |