amd64 packages are fine. It seems to not solve the issue: Only the timeout seems to be at a higher value?!
I get also the "no response from drbd driver" message. Here the output from the different Commands: [EMAIL PROTECTED]:~# cat /proc/drbd version: 8.2.7~rc1 (api:88/proto:86-88) GIT-hash: b00832ffcf713b24f7547423c3d55e1f192d01d3 build by [EMAIL PROTECTED], 2008-09-29 20:28:51 [EMAIL PROTECTED]:~# drbdadm attach r0 No response from the DRBD driver! Is the module loaded? Bad: fgets returned NULL while waiting for data: Interrupted system call [EMAIL PROTECTED]:~# /etc/init.d/drbd start Starting DRBD resources: [ d(r0) No response from the DRBD driver! Is the module loaded? s(r0) No response from the DRBD driver! Is the module loaded? n(r0) No response from the DRBD driver! Is the module loaded? ]. .......... *************************************************************** DRBD's startup script waits for the peer node(s) to appear. - In case this node was already a degraded cluster before the reboot the timeout is 120 seconds. [degr-wfc-timeout] - If the peer was available before the reboot the timeout will expire after 0 seconds. [wfc-timeout] (These values are for resource 'r0'; 0 sec -> wait forever) To abort waiting enter 'yes' [ 119]:No response from the DRBD driver! Is the module loaded? yes [ 679]: [EMAIL PROTECTED]:~# And in /var/log/messages: Oct 1 12:20:07 corvus kernel: [ 4283.482632] drbd: module cleanup done. Oct 1 12:21:51 corvus kernel: [ 4386.640204] drbd: initialised. Version: 8.2.7~rc1 (api:88/proto:86-88) Oct 1 12:21:51 corvus kernel: [ 4386.640212] drbd: GIT-hash: b00832ffcf713b24f7547423c3d55e1f192d01d3 build by [EMAIL PROTECTED], 2008-09-29 20:28:51 Oct 1 12:21:51 corvus kernel: [ 4386.640214] drbd: registered as block device major 147 Oct 1 12:21:51 corvus kernel: [ 4386.640217] drbd: minor_table @ 0xffff8808238f2500 -- drbd doesn't start: "No response from the DRBD driver! Is the module loaded?" but module is loaded https://bugs.launchpad.net/bugs/271254 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
