** Tags added: iso-testing
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
** Changed in: mdadm (Ubuntu)
Status: Needs Info => Fix Released
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTEC
Great news! Using the 04/14 Daily Build, all of my previous
difficulries have vanished. All the arrays that I built (I've tried 2
different schemes) now boot flawlessly.
Not sure what the culprit was but it was something that changed between
the 04/12 build and today.
--
Feisty beta1 raid is b
All of my problems are resolved with the latest -15 kernel...
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https
I had very similar problems (bug 106238). These were "cured" when I
force booted with "init=/bin/sh" and then ran "/sbin/init" from the bash
prompt. After Gnome came up, I then did apt-get update/upgrade, and
the installation of the newest initramfs-tools update fixed my RAID boot
issues.
But I
I am seeing this problem as well...
To continue the boot, I mount -t ext3 /dev/md0 /root and hit CTL-D, then
the system boots. I installed the alternate beta, and installed all of
the updates. The mdadm update ran a update-initramfs command to update
the initrd.img files, but still fails the same
;marcw" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Thursday, April 12, 2007 2:31:46 PM (GMT-0600) US/Central
Subject: [Bug 96511] Re: Feisty beta1 raid is broken
Not positive if the package should be mdadm or not.
** Changed in: mdadm (Ubuntu)
Sourcepackagename: None => mdadm
--
Not positive if the package should be mdadm or not.
** Changed in: mdadm (Ubuntu)
Sourcepackagename: None => mdadm
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Trying once again, I grabbed the latest AMD64 Server daily (04/11.1) but
to no avail - it still fails. This time I'm including screen photos in
case it can help diagnose wherever the heck is happening.
The first 8 prints include the extent of the terminal buffer up to the
initramfs prompt.
Then
Tried the 04/10 alternate daily AMD64 tonight hoping that something's
been fixed. Nope, Still broke. This isn't looking good for using
Feisty for my server.
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubunt
Well, it was time to try something else. So I grabbed the daily build
(04/09) of the i386 Ubuntu Server instead of my usual AMD64.
Unfortunately I had exactly the same luck with that one as I've had with
the others.
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You receive
I tried the 04/06 (or was it 04/05?) daily build of the AMD64 Ubuntu
Server just to see if there's been any improvement. No change. Still
broke.
Then just on a lark, and because I didn't have anything better to do, I
loaded up the Debian Etch Rc2 AMD64 netinstall daily build (04/06) just
to see
Brian,
I started from scratch tonight building the arrays again as I spec'd in the
first post using the beta1 server install disk.. After a successful install
and a few reboots I was able to get a normal prompt from which I performed a
apt-get dist-upgrade. I noticed this time that I was promp
Tried it, no joy. If I get time tomorrow I'm going to experiment with
manual changes to the initrd to see if I can work around the module
problem that way. I looked, and while I thought I remembered an mdadm
mailing list, it seems my memory was faulty or it no longer exists. If
you have any othe
There have been some recent updates to udev and mdadm that may resolve
this issue. Could you please try updating your system and rebooting?
Thanks again.
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubuntu
Bug
I think I may have found it. Attempting to boot from RAID,
/proc/ide/ide0/hda/driver is "ide-default version 0.9.newide" whereas
booting successfully via non-RAID, /proc/ide/ide0/hda/driver is "ide-
disk version 1.18".
Googling "ide-default ide-disk" reveals some bugs/race conditions that
were su
I had a XenExpress 3.2 cd handy to boot in this same machine, and one
thing I note is that it assigns the same hardware/drives significantly
differently.
XenExpress 2.6.16.38 Feisty 2.6.20.13
hd[a-d] Promise Controller 1 hd[a-d] Onboard VIA controller
I did, but still the same thing, I think because break=mount doesn't
come into play until later in initrd.
FWIW, I reinstalled the first disk with yesterdays daily build, and I
still get the same thing (namely when I boot off RAID, /dev/hda* and
/dev/hdc* don't show up at all in /proc/partitions w
Bullcreek - have you tried booting with the kernel option 'break=mount'
and manually assembling your RAID array?
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
I spent part of this afternoon battling the same thing I think using
feisty BETA also. I'm quite familiar with software RAID on linux, and a
few comments:
1. It seems that unlike in older distros, /etc/mdadm/mdadm.conf in
feisty is fairly important. Without adding the ARRAYs entries to it, my
a
Ok, thanks for those instructions. Unfortunately, I don't believe
anything good came of it.
First off, trying to get a normal prompt is more difficult than I
originally said; it's probably closer to 1 out of 30 reboots that will
get me to a normal login prompt.
Secondly, I assume the busybox she
In your '/boot/grub/menu.lst' file you will want to modify the default
kernel boot options:
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=break=mount
and add 'break=mount' as I have done. After
Thanks Brian. I'd be happy to but can you write, or point me to , a
little step by step of what you're asking?
--
Feisty beta1 raid is broken
https://launchpad.net/bugs/96511
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for taking the time to report this bug and helping to make Ubuntu
better. This sounds like another bug regarding md and sata devices.
Please try booting Feisty with the kernel option 'break=mount' and
assembling the RAID devices manually and let us know the results.
Thanks in advance.
** C
24 matches
Mail list logo
