*** This bug is a duplicate of bug 1241086 ***
https://bugs.launchpad.net/bugs/1241086
I upgraded to kernel 3.13.0.32.28 (3.13.0-32-generic) after getting a
message about hardware updates for my system was coming to an end of
life and I should do a hardware update. Normally I use apt-get dist-
upgrade for such a thing but I had a friend over and I used the upgrade-
manager gui as an intro to how easy upgrades are etc. etc. etc....
only this time, dave and joe, we had a problem...
I previously was running 3.08.0-33-generic with a /data folder mapped to
a dmraid (software raid) array of 4 drives as type raid-5 but actually
mapped as 2-pair striped and mirrored on an ASUS motherboard having
NVIDIA chipset for onboard graphics, drive support, and other I/O. This
system has been running fairly stable for a few years with minor
upgrades since being built when 320Gb SATA2 HDs were coming down in
price. It is getting dated, though...
After upgrade, I get the same result as mimmo on this bug report. I've
never made a bug report so wouldn't know the protocol - but would like
to report the issue I just ran into - since it seemed that mimmo's was a
couple of major commits ago.
When I revert back to the previous kernel during boot on grub -
everything works as it did prior to upgrade, so I suffered no data loss
and no major problems. When I let it boot to the new build, and I run a
few dmraid commands, the drives are intact, just the kernel doesn't know
about it.
dmraid -s and dmraid -b reports the same metadata in both environments
If you want log data, please let me know protocol of what's needed.
I'll keep my workstation as is for a little bit before digging and
trying to fix on my own... I may eventually off-load my array to a
single 2TB disk so I have a good backup and rebuild the array with a new
set of 2TB drives (assuming I can rebuild)
-- da Lizard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241822
Title:
RAID 5 not available after upgrade from 13.04 to 13.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241822/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
