This bug was fixed in the package dmraid - 1.0.0.rc15-11build1
---
dmraid (1.0.0.rc15-11build1) karmic; urgency=low
* Fakesync from Debian
dmraid (1.0.0.rc15-11) unstable; urgency=low
* [ce4e2dc] 15_activate_multiple_raid_sets.patch: Continue onto all
raid sets instead of
I'm attaching a new debdiff that adds a slight tweak to dmraid-activate
to output the command line params.
It shows, pretty clearly, that dmraid-activate is being called with
'no'
'block'
'devices'
'found'
I'm really not sure where to go from here :(
** Attachment added: 7ubuntu1-7ubuntu2
** Attachment added: boot dmraid.log
http://launchpadlibrarian.net/27319090/dmraid.log
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: dmraid-activate.log
http://launchpadlibrarian.net/27319106/dmraid-activate.log
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is cleaned up; it removes noise due to dmraid-activate not handling
dmraid errors properly when probing for raid names.
dmraid.log when configured to log on boot shows:
dmraid-activate run with no
dmraid -i -r -cr /dev/no
no block devices found
dmraid-activate run with block
dmraid -i -r -cr
Robert Collins ha scritto:
A bug can be confirmed without having enough information for a developer
to fix it; and as its assigned to me it does in fact have a dev working
I'm not expert with ubuntu bugs status, but in your wiki I read[1]:
Confirmed:
* Another reporter has experienced
On Sat, 2009-05-16 at 08:18 +, Giuseppe Iuculano wrote:
Robert Collins ha scritto:
A bug can be confirmed without having enough information for a developer
to fix it; and as its assigned to me it does in fact have a dev working
I'm not expert with ubuntu bugs status, but in your wiki
I tried -7 with my hpa patch applied, still fails to boot au naturale
:). So it looks like not a dupe to me, or my HPA patch interferes with
the fix.
I've modified dmraid-activate to allow debugging if invoked with
DMRAID_DEBUG=1, using your debug code, patch for both attached. I'll
attach log
** Attachment added: log from running with /dev/sda
http://launchpadlibrarian.net/26807882/dmraid.log.dev-sda.gz
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: log from running with sda
http://launchpadlibrarian.net/26807895/dmraid.log.gz
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: activate log from running with /dev/sda
http://launchpadlibrarian.net/26807905/dmraid-activate.log.dev-sda.gz
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: activate log from running with sda
http://launchpadlibrarian.net/26807921/dmraid-activate.log.gz
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So, these two logs are from udev running dmraid-activate, as opposed to
me running it by hand. This confirms that udev is running dmraid-
activate.
** Attachment added: dmraid log from udev running dmraid-activate
http://launchpadlibrarian.net/26808272/dmraid.log.boot.gz
--
dmraid not
** Attachment added: activate log from udev invoking dmraid-activate
http://launchpadlibrarian.net/26808229/dmraid-activate.log.boot.gz
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(Sorry for all the spam :P). Anyway, as I read the log, udev is invoking
dmraid-activate 4 times:
/sbin/dmraid-activate no
/sbin/dmraid-activate block
/sbin/dmraid-activate devices
/sbin/dmraid-activate found
(I base this by looking at grep -- --degraded boot/dmraid-activate.log,
which is the
Robert Collins ha scritto:
So, these two logs are from udev running dmraid-activate, as opposed to
me running it by hand. This confirms that udev is running dmraid-
activate.
ERROR: either the required RAID set not found or more options required
no raid sets and with names: no block devices
Robert Collins ha scritto:
(Sorry for all the spam :P). Anyway, as I read the log, udev is invoking
dmraid-activate 4 times:
/sbin/dmraid-activate no
/sbin/dmraid-activate block
/sbin/dmraid-activate devices
/sbin/dmraid-activate found
(I base this by looking at grep -- --degraded
Robert Collins ha scritto:
Now, I'm not sure how udev will precisely invoke dmraid-activate, but if
its using the former syntax, that would explain it. If its meant to use
the latter syntax, I have to assume udev is failing to invoke dmraid-
activate.
Udev invokes dmraid-activate node-name.
On Sat, 2009-05-16 at 11:11 +, Giuseppe Iuculano wrote:
Robert Collins ha scritto:
So, these two logs are from udev running dmraid-activate, as opposed to
me running it by hand. This confirms that udev is running dmraid-
activate.
ERROR: either the required RAID set not found or
edit d-a, log to /dev/.initramfs/foo, set -x
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 367553 ***
https://bugs.launchpad.net/bugs/367553
** This bug has been marked a duplicate of bug 367553
Raid is not activated automatically
--
dmraid not activating on boot
https://bugs.launchpad.net/bugs/376792
You received this bug notification
I appreciate it looks like a dup, but perhaps you could let me finish
investigating before marking as the duplicate of a fix-released bug.
If it is the same, sure, we'll collapse them - and we'll need to open a
bug task on jaunty, because if its a common issue jaunty is rather
broken ;)
** This
Robert Collins ha scritto:
I appreciate it looks like a dup, but perhaps you could let me finish
investigating before marking as the duplicate of a fix-released bug.
Good point, but perhaps you shouldn't mark as confirmed a bug that seems me
pretty incomplete :)
Cheers,
Giuseppe
--
dmraid
Robert Collins ha scritto:
edit d-a, log to /dev/.initramfs/foo, set -x
In case you need some debug logs, the tar.gz in attachment could help:
I need some debug logs.
Extract the attached .tar.gz, and you have a dmraid-debug directory
Backup /etc/udev/rules.d/85_dmraid.rules and
Giuseppe Iuculano ha scritto:
Robert Collins ha scritto:
edit d-a, log to /dev/.initramfs/foo, set -x
In case you need some debug logs, the tar.gz in attachment could help:
Oh yes, But I need also to attach that tar.gz :-)
Cheers,
Giuseppe.
** Attachment added: dmraid-debug.tar.gz
On Fri, 2009-05-15 at 15:26 +, Giuseppe Iuculano wrote:
Robert Collins ha scritto:
I appreciate it looks like a dup, but perhaps you could let me finish
investigating before marking as the duplicate of a fix-released bug.
Good point, but perhaps you shouldn't mark as confirmed a bug
On Fri, 2009-05-15 at 15:49 +, Giuseppe Iuculano wrote:
Giuseppe Iuculano ha scritto:
Robert Collins ha scritto:
edit d-a, log to /dev/.initramfs/foo, set -x
In case you need some debug logs, the tar.gz in attachment could help:
Thanks!
-Rob
--
dmraid not activating on boot
27 matches
Mail list logo
