← Back to team overview

kernel-packages team mailing list archive

[Bug 1241822] Re: RAID 5 not available after upgrade from 13.04 to 13.10

 

Hi,

I've Just upgraded my (k)ubuntu to 13.10 and I cannot see also my RAID 5 Volume.
my motherboard is an GIGABYTE GA-Z68A-D3H-B3 1, the raid controleur is:
           00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] (rev 05)

My kernel is Linux 3.11.0-12-generic x86_64.

My RAID volume is a data volume (not system just photo, video,
music,...) which is not detected on boot with an error message about
raid45...

This is my tries to resolve my issue:

$ sudo dmraid -ay
ERROR: device-mapper target type "raid45" is not in the kernel       <---------------- again this problem with raid45
RAID set "isw_chgeejbadh_Volume_0000" was not activated

$ sudo modprobe -a dm-raid45
WARNING: Module dm-raid45 not found.
$ sudo modprobe -a raid45
WARNING: Module raid45 not found.

$  sudo dmraid -s
*** Group superset isw_chgeejbadh
--> Subset
name   : isw_chgeejbadh_Volume_0000
size   : 3907041792
stride : 128
type   : raid5_la
status : ok                                                                          .
subsets: 0
devs   : 3
spares : 0

$ sudo dmraid -r
/dev/sde: isw, "isw_chgeejbadh", GROUP, ok, 1953525166 sectors, data@ 0  <---------------- It's strange, in my memory, the letters of volumes was followed one after the others in 13.04 
/dev/sdc: isw, "isw_chgeejbadh", GROUP, ok, 1953525166 sectors, data@ 0
/dev/sdb: isw, "isw_chgeejbadh", GROUP, ok, 1953525166 sectors, data@ 0

$  cat /etc/fstab
...
# /media/BIGRAID was on /dev/md during installation UUID=F03C21CA3C218D22    
/dev/mapper/isw_chgeejbadh_Volume_0000p1  /media/BIGRAID  ntfs rw,nosuid,nodev,allow_other,blksize=4096    0       0

$ ll /dev/mapper
total 0
drwxr-xr-x  2 root root      60 oct.  19 22:04 ./
drwxr-xr-x 16 root root    4340 oct.  19 22:54 ../
crw-------  1 root root 10, 236 oct.  19 22:04 control

$ lsmod|grep raid45
raid456                77529  0                               <----------------  Strange again it's raid456 instead of raid45, it seems to be the problem...
async_memcpy           12650  1 raid456
async_raid6_recov      12955  1 raid456
async_pq               13154  1 raid456
async_xor              13019  2 async_pq,raid456
async_tx               13451  5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov

Thank you in advance for your help

-- 
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:
  Confirmed

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


References