BTW, I had to add the 'mdadm -Ss --wait-clean' command to a KDE shutdown
script (instead of one of the normal system shutdown scripts under
/etc/init.d) because the shutdown scripts would not wait for this
command to complete. It takes long enough to '--wait-clean' that
something during shutdown wo
The files that have to be customized or overridden by adding hooks under
/etc are:
/lib/udev/rules.d/64-md-raid.rules
/usr/share/initramfs-tools/hooks/mdadm
so I think this is more of an MDADM issue instead of a generic
setup/config issue. But, that depends on which package actually owns
thes
Ben McCann, it would be most helpful if this documented procedure is
noted in the Ubuntu Community documentation https://help.ubuntu.com/ .
Would you say the fact you have to make post-default configuration MDAM
hooks to get RAID to work would be a bug in MDAM or a
setup/configuration issue (ex. b
I found and fixed this problem and it has nothing to do with the kernel.
Intel RAID is *extremely* finicky and I remembered that it required two
tweaks to the initrd build process. I originally implemented those
tweaks in a couple of the MDADM 'hook' files under /usr/share. That was
my mistake. Th
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210104
Title:
Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3
Thanks for the feedback, Ben. Can you test the 3.2.45 kernel, since 3.2.46
does not have an amd64 kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.45-precise/
If 3.2.45 is good, I'll build a 3.2.46 kernel for testing.
--
You received this bug notification because you are a member of
I can't test 3.2.46 because there are no amd64 packages available in
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.46-precise. (There
were no Intel CPU packages at all). I did test 3.2.47 and 3.2.48 images
and *both* of them fail to detect my Intel fakeraid array.
I also looked into updating
I'd like to perform a bisect to figure out what commit caused this regression.
We first need to identify the earliest kernel where the issue started happening
as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for
the e
I'm reluctant to upgrade the BIOS on a PC that is otherwise working fine
but I agree that my BIOS is quite out of date. So, I'll probably upgrade
tomorrow. (Have to go to work now).
That said, I'm skeptical upgrading the BIOS would matter because Linux
3.2.0-49 works fine and 3.2.0-51 doesn't. Som
Ben McCann, as per
http://www.asus.com/Motherboards/P8Z77V/#support_Download_8 an update is
available for your BIOS (2003). If you update to this, does it change
anything?
If not, could you please both specify what happened, and provide the output of
the following terminal command:
sudo dmidecode
The bug exists in the latest upstream kernel (v3.11-rc4-saucy). I see
identical behavior to the originally reported bug. MD fails to see my
intel fakeraid array but both physical members of the array are online
and readable.
--
You received this bug notification because you are a member of Kernel
Can you also test the latest mainline kernel to see if the bug exists there as
well:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/
We can then either bisect the 3.2 kernel to find the commit that
introduced this regression or reverse bisect the mainline kernel if it
fixes this bu
Tested upstream kernel as requested. Regression exists upstream too.
Added kernel-bug-exists-upstream tag.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210104
Title:
Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51
Status in “linux” package in
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.2 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
OK. I added the apport data. Note that I am currently running 3.2.0-49,
which works, because my machine is almost useless with 3.2.0-51.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
apport information
** Tags added: apport-collected precise staging
** Description changed:
I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu
12.04 for months. I'm using the MDADM version and not DMRAID. It has
been working fine other than a couple minor issues with cle
Ben McCann, thank you for taking the time to report this bug and helping to
make Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1210104
When reporting bugs in the future please use apport by using 'ubuntu-b
3.2.0-51 kernel log
** Attachment added: "Kernel log from 3.2.0-51 (that fails to start FakeRAID)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210104/+attachment/3764809/+files/3.2.0-51.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
19 matches
Mail list logo
