Even more on this. I've i've got Feisty on 2 of my servers (IDE and SCSI drives
in RAID1), these are the servers, so they aren't rebooted frequently. What I
found was that the machine with SCSI drives would eventually fall to busybox
upon reboot and I'd have to reboot it manually to get working.
My box did boot fine showing that mdadm message though. The trouble
began as I installed the server kernel and initrd images got
regenerated. The box became unbootable. The proposed fix worked out,
thanks for that, but I'm still getting an error message at system
shutdown (like Stopping MD0 [f
GUYS, PLEASE STOP HIJACKING EXISTING BUG REPORTS!
IF YOU ARE HAVING PROBLEMS BOOTING WITH MDADM, LVM2, EVMS OR DEVMAPPER
PLEASE
! FILE ! A ! NEW ! BUG !
If somebody else has already filed a new bug, DO NOT hijack it, please
FILE ANOTHER NEW ONE.
We have had several separate, different, problem
Thanks Quikee. I tried your latest, most elegant workaround, and it worked
great here.
I don't think that this is an lvm problem, especially since me and a lot of the
others here aren't using lvm.
I am going to add udev to affected packages, since upgrading to udev-105 from
debian unstable also
** Also affects: lvm2 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
linux software RAID not working after herd 3 installation..
https://bugs.launchpad.net/bugs/83231
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Same thing here, just done an install of Feisty server beta and done an
apt-get update && apt-get dist-upgrade, came up with the same problems
as before - have to manual mount the arrays in the busybox shell or use
the udevsettle temporary workaround. Just a basic install with a small
RAID1 array f
Got kicked out of #75681, rereporting here:
The race condition fixes in #75681 did not fix my boot problems, which
are like those above (raid not detected). Adding a udevsettle script as
above fixed my problem. I dist-upgraded and tested about 12 hours ago.
My package list now matches that with th
Confirmed this with the i386 3-29 daily build.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I've got the same problem with the desktop beta amd64.
I hope this will be fixed before final release...
I'll try your methods to correct it, thank you!!!
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I created a file "udevSettle" (attached) in the same folder as udev
(/usr/share/initramfs-tools/scripts/init-premount/), which is executed
after udev and should be unaffected if a package is updated. I don't
know if it still works correctly - it works for me.
** Attachment added: "udevSettle"
If you've put udevsettle in the udev script of initramfs-tools, you need to
replace the line at the end of file each time the package udev is updated.
2007/3/28, James <[EMAIL PROTECTED]>:
>
> This is disturbing.
>
> I was going to ask what happens if initramfs-tools is updated and the
> problem i
This is disturbing.
I was going to ask what happens if initramfs-tools is updated and the
problem is not fixed.
Just did an update on a working machine with the above work around and
initramfs-tools was one of the packages updated. This triggered an
update of the initrd. That computer no longer b
To the people that discussed the work around, thank you. I used the
udevsettle work around and it worked. That finished a rather frustrating
afternoon.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Just installed ubuntu-7.04-beta-server-i386 with / on software raid. I
am having the same problem. Mdadm being run before the drives are
detected. Leaving with a new install that won't boot.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubunt
** Changed in: initramfs-tools (Ubuntu)
Status: Unconfirmed => Confirmed
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Tags added: dmraid mdadm
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It's better as it is cleaner. For me the problem is from udev, so the
correction should be in udev.
udevsettle --timeout=10 waits for udev to end its works with a maximum
of 10sec. So it should be shorter than the sleep 10 solution.
--
linux software RAID not working after herd 3 installation..
udevsettle --timeout=10
Works for me too.
@ Quikee: Why is it a better solution? I'm just curious. Speed-wise, I think
they're about the same.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I tried "udevsettle" and it is a much better solution. It should be
"udevsettle --timeout=10".
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
the "udevsettle --timeout 10" at the end of /usr/share/initramfs-
tools/scripts/init-premount/udev works too.
We have now several solutions to propose to udev and dmraid packagers.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs ma
The "udevsettle" works. I'll try (tomorrow) to add the udevsettle at the
end of the udev populating script in /usr/share/initramfs-tools/scripts
/init-premount/udev.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubunt
I'm having the same problem on a dmraid root partition.
I've had a look at bug #85640 about problem on crypted root partition.
It seems their problem is due to the fact that /dev is not completely
populated when it try to decrypt. I wonder if we don't have the same
kind of problem here...
They so
Confirmed Feisty Herd 5 (AMD64) updated 12/mar/2007. Doesn't boot.
mdadm: no devices found for /dev/md1
Hardware:
Dual Core AMD Opteron 175
Raid 5
Kernel 2.6.20-9-server
Very annoying bug.
The "trick" posted by Quikee works.
Best regards,
neuromancer
--
linux software RAID not working after
I can confirm this in Feisty Herd 5 (i386).
mdadm: No devices listed in conf file were found.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu
Velociraptor said, "Edgy didn't exhibit this problem."
Yes. I didn't find this problem in Edgy as well.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Quikee's method works even with only "sleep 2" instead of "sleep 10".
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I too confirm this bug for dmraid on Feisty Herd 5 (amd64). When booting
from the HDD the only message I receive to the console is "no block
devices found". (I believe this message is issued by dmraid.) The
workaround suggested by Quikee solves the problem.
I used the update-manager to upgrade fro
I confirm Nyinge comment! I had a similar problem with feisty on a
fakeraid partition (dmraid) and i solved with Quikee 'hack'.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
I can comfirm this as well. However, in my case it is with dmraid but
with similar nature. The problem still exists as of today(Feisty herd-5
release date) with packages fully upgraded. Quikee's quick fix solves
the problem, but of course, a thorough patch would be super.
--
linux software RAI
I can confirm this in Herd 4.
The exact error message:
mdadm: No devices listed in conf file were found.
--
linux software RAID not working after herd 3 installation..
https://launchpad.net/bugs/83231
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
30 matches
Mail list logo
