Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on
a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You
:: could you confirm that these would be various different kernel
versions over time, and not ONLY on the 46 to 47 update?
That's probable. IIRC, my RAID1 MD devices have been blowing up
inexplicably over the past year, and I tend to stay quite current on
patches, applying them each week
@penalvch New bug filed as requested:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423
PS: I did not realize the kernel versions (using a dot for the last
digits) are different from the ubuntu ones (using a -). I'll also answer
latest questions by sconklin on the new bugreport.
--
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Steve Conklin (sconklin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190295
Title:
2.6.32-47 kernel update on 10.04 breaks software
It's possible that the patches which were linked are not related.
They're not in the delta between the two versions which are listed.
Here are some questions to try to narrow down the field of potential
issues.
1. You mention that this occurs on various upgrades, could you confirm that
these
I see and I'll try to flie the new report as soon as possible, even
though I think it is the same cause as this one.
I've had a look at the kernel log and see that only two patches affected
the md component between 2.6.32-46 (working kernel) and 2.6.32-47
(broken kernel, reported in this bug):
A1an, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control
team, and Ubuntu Bug Squad would like you to please file a new report by
executing the following in a terminal:
ubuntu-bug linux
For more on this, please see the Ubuntu Kernel team article:
Just updated to 2.6.32-49, issue still present an had to switch back to
2.6.32-46 which still works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190295
Title:
2.6.32-47 kernel update on
The array that does not start anymore has the following config:
level=raid1 metadata=1.2 num-devices=2
While a second array with metadata=1.0 seems to be recognized and
started correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190295
Title:
2.6.32-47 kernel update on 10.04 breaks software RAID (+ LVM)
To manage
bl8n8r, thank you for reporting this and helping make Ubuntu better. 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 BUGNUMBER
When
11 matches
Mail list logo
