kernel-packages team mailing list archive

[LoungeLizard <1241822@xxxxxxxxxxxxxxxxxx>]

*** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1241822

Title:
  RAID 5 not available after upgrade from 13.04 to 13.10

Status in “linux” package in Ubuntu:
  Fix Committed
Status in “linux” source package in Saucy:
  Fix Committed

Bug description:
  Just upgraded my ubuntu to 13.10 and I cannot see my RAID 5 anywhere. Googling around led me to look at the "dmraid" which gives me this error: "device-mapper target type "raid45" is not in the kernel"
  I'm running an Asus Maximus iv Extreme and the RAID controller in question is the Intel controller. I've updated the BIOS to the latest version 3604 with the same reults.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC2:  mkh        2573 F.... pulseaudio
   /dev/snd/controlC0:  mkh        2573 F.... pulseaudio
   /dev/snd/controlC1:  mkh        2573 F.... pulseaudio
  Date: Fri Oct 18 23:29:40 2013
  HibernationDevice: RESUME=UUID=82842309-575f-492b-ab23-5868b737aa86
  InstallationDate: Installed on 2012-11-13 (338 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   eth0      no wireless extensions.
   
   eth1      no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c99bd7f6-910e-4c63-a63a-dc4777c456fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware                             1.116
  RfKill:
   0: hci0: Bluetooth
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Maximus IV Extreme
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd04/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusIVExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241822/+subscriptions