I have the same issues as described above. Running a clean install of 7.04
x86_64. Fakeraid 0 on an intel ICH7R controller.
When booting my / is not found, and after some time i get dumped to the
initfsram prompt. "ls /dev/mapper/" does not list my raid, and only "control".
Running "dmraid -ay"
** Changed in: dmraid (Ubuntu)
Status: Fix Committed => Fix Released
--
dmraid not starting on system boot
https://bugs.launchpad.net/bugs/93810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[E
Today I upgraded to the new version of dmraid and it works. Finally I
can omit break=mount - Thank you very much!
--
dmraid not starting on system boot
https://bugs.launchpad.net/bugs/93810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
** Changed in: dmraid (Ubuntu)
Status: In Progress => Fix Committed
--
dmraid not starting on system boot
https://bugs.launchpad.net/bugs/93810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 13 Apr 2007 16:02:00 -0400
Source: dmraid
Binary: dmraid-udeb dmraid
Architecture: source
Version: 1.0.0.rc13-2ubuntu3
Distribution: feisty
Urgency: high
Maintainer: Ubuntu MOTU Developers <[EMAIL PROTECTED]>
Changed-By: Richard
** Attachment added: "debdiff for update"
http://librarian.launchpad.net/7325537/dmraid.debdiff
** Changed in: dmraid (Ubuntu)
Assignee: (unassigned) => Richard Bailey
Status: Needs Info => In Progress
--
dmraid not starting on system boot
https://bugs.launchpad.net/bugs/93810
Yo
Ready for upload, would like this to get in before feisty since it
breaks upgrades from edgy for those that have / on FakeRAID.
--
dmraid not starting on system boot
https://bugs.launchpad.net/bugs/93810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Here is a patch for calling udevsettle before calling dmraid, like I did
in comment 17.
** Attachment added: "adds udevsettle to
/usr/share/initramfs/scripts/local-top/dmraid"
http://librarian.launchpad.net/7319667/dmraid.diff
--
dmraid not starting on system boot
https://bugs.launchpad.net/
For those interested and courageous enough, I have implemented the above
mentioned udev rule solution in bug #106177.
--
dmraid not starting on system boot
https://bugs.launchpad.net/bugs/93810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
I can confirm this bug on upgrading from Edgy to Feisty. I solved it by
inserting a "udevsettle --timeout=30" line before the modprobe lines in
/usr/share/initramfs/scripts/local-top/dmraid and building a new
initramfs with "update-initramfs -u -k all".
If you upgrade, do this _before_ you reboot
I do not have access to a feisty installation at hand but can someone
check what order dmraid is run relative to udev? You can check this is
/etc/rcS. dmraid should be initialised *after* udev for this same
reason. There was a bug about this in debian that was fixed, I opened a
bug here but that wa
** Attachment added: "updated debdiff with new maintainer & dmraid init move"
http://librarian.launchpad.net/6988898/dmraid.debdiff
--
dmraid not starting on system boot
https://launchpad.net/bugs/93810
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
** Attachment added: "debdiff to move dmraid to S11 in rcS.d"
http://librarian.launchpad.net/6988744/dmraid.debdiff
--
dmraid not starting on system boot
https://launchpad.net/bugs/93810
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
Can someone who is currently experiencing this error test with this new deb?
It's the same upstream version, the only difference is that dmraid is
initialised at S11 instead of S04, i.e. after udev.
I appended my username to the end of the file in case others want to try to
build a deb and attac
I just checked and yes, dmraid is initializing before udev in rcS.d.
What this means is that dmraid sets up the devices in /dev/mapper, then
udev is run and it completely rebuilds /dev, throwing out what dmraid
did. Currently udev is initialized at S10 and dmraid at S04, it should
be changed to S11
Maybe adding "udevplug -W" before the /sbin/dmraid line in the local-top/dmraid
script would do the job. Or, inspired by https://wiki.ubuntu.com/UdevLvm,
adding a udev rule like:
SUBSYSTEM=="block", RUN+="watershed /sbin/dmraid -ay -i"
There are similar issues for software raids, see bug #75681.
Sorry, I meant "break=mount" and not "break=bottom" !
--
dmraid not starting on system boot
https://launchpad.net/bugs/93810
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
what you means is change the menu.lst uses "kernel /vmlinuz break=bottom
root=/" to replace "kernel /vmlinuz break=mount root=/"?
I do so, and wait about 3 minutes to entering the initramfs shell.Then I wait
about 20 Sec, nothing happened.
So I use " "kernel /vmlinuz break=bottom break=m
I had the exact same problem, and it can be solved as Tormod Volden said
in the last post
--
dmraid not starting on system boot
https://launchpad.net/bugs/93810
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ok, I think I have figured out why it doesn't find the raid when
booting. First init-premount/udev is run, and starts to find devices.
However, local-top/dmraid is run straight after, before the raw disks
have been detected, so the dmraid does not set up any raid. Then the raw
disks come rolling in
"scripts/local-top/udev" not found. There are only "mdrun" and "dmraid" in the
path "scripts/local-top/".
Here is the output.txt you wanted.
** Attachment added: "sh -x /etc/init.d/dmraid start 2>output.txt"
http://librarian.launchpad.net/6935773/output.txt
--
dmraid not starting on system b
Alteeno, what do you mean by "doesn't work"? Can you please attach that
output.txt?
Can you also try this: boot with "break=mount" and run "scripts/local-
top/udev" and then exit the initramfs shell (without running dmraid). I
have a suspicion that dmraid is run too early, before udev has found th
"sudo /etc/init.d/dmraid start" doesn's work.
I guess that the dmraid doesn't work when system booting. Because when I add
"break=mount" to the kernel option in the /boot/grub/menu.lst, and run "dmraid
-ay" at the shell then exit when the system booting break, the dmraid works
fine. But without
Alteeno, so you are saying "sudo /etc/init.d/dmraid start" does not
work, and "dmraid -ay" works? Then run "sudo sh -x /etc/init.d/dmraid
start 2>output.txt" and attach output.txt, please.
That the reconfiguration of acpid fails is not related to dmraid AFAICS.
--
dmraid not starting on system b
I have the same problem, and "sudo /etc/init.d/dmraid start" doesn't work.
When I chroot to /target, run "dpkg-reconfigure --all", it report "acpid: can't
open /proc/acpi/event: Device or resource busy"
"invoke-rc.d: initscript acpid, action 'start' failed".
--
dmraid not starting on system
Does "sudo /etc/init.d/dmraid start" work?
** Changed in: dmraid (Ubuntu)
Status: Unconfirmed => Needs Info
--
dmraid not starting on system boot
https://launchpad.net/bugs/93810
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
26 matches
Mail list logo
