Sorry, I was distracted by other things. So I will be attaching a proposed update to dmraid and some pre-built package to test. I just cannot promise that change will be accepted.
About converting to mdadm: That would be an option that might be more future proof but only if you do not want to use the RAIDed disks in parallel with Windows. The drivers that come with the motherboard rely on the BIOS signatures and I am not aware (I never had need, so I never searched) of any generic RAID driver for Windows that would recognize the DDF signatures that mdadm creates. If you only will be using Linux it is a different story. Then moving to mdadm (you can then use even the normal superblock format, no strict need for DDF) would have the additional benefit of being able to replace the motherboard or move the disks to a different computer and have the RAID still working. But of course its a tedious task: you need some place to backup all data, also better make sure the backup has no bits corrupted (maybe rare but happened), erase the RAID signatures (if possible, from the BIOS), either plug the disks to a different controller or switch the current one into SATA/AHCI mode, set up the mdamd RAID and finally copy the backup back (and possibly again check for consistency). A lot of work... ** Patch added: "Proposed update for dmraid" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611277/+attachment/4723888/+files/disable-removable-test.debdiff -- 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/1611277 Title: Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid Status in dmraid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in dmraid source package in Xenial: New Status in linux source package in Xenial: Invalid Bug description: Kernel shipped with Ubuntu 16.04.1 cannot recognize fakeRaid created from Ubuntu 14.04. I've tried three ways but none of them work. 1. Update 14.04.4 to 16.04.1 2. Fresh install 16.04.1 3. Update kernel to linux-images-4.4.0-34-generic only The result is that the mapper was seperated into /dev/sdb and /dev/sdc and cannot be rebuild with dmraid (said no raid disk) or mdadm (said no superblock). Something interesting is that when I reinstall Ubuntu 14.04.2 with my old CD, during the installation Ubuntu is able to recognize /dev/mapper/.... But when I do a fresh install in Ubuntu 16.04 with the CD, I get /dev/sdb and /dev/sdc The motherboard I'm using is Gigabyte X79-UP4 The fakeRaid with Marvell chipset on my motherboard shows the following information with fdisk in Ubuntu 16.04.1. /dev/sda is where the system is installed. It is a normal hard drive. /dev/sdb and /dev/sdc are using raid 1. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000b7321 Device Boot Start End Blocks Id System /dev/sda1 * 2048 499711 248832 83 Linux /dev/sda2 501758 1953523711 976510977 5 Extended Partition 2 does not start on physical sector boundary. /dev/sda5 501760 1953523711 976510976 8e Linux LVM Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdc doesn't contain a valid partition table Disk /dev/mapper/ubuntu--vg-root: 982.8 GB, 982805118976 bytes 255 heads, 63 sectors/track, 119485 cylinders, total 1919541248 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition table Disk /dev/mapper/ubuntu--vg-swap_1: 17.1 GB, 17091788800 bytes 255 heads, 63 sectors/track, 2077 cylinders, total 33382400 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition table The fakeRaid with Marvell chipset on my motherboard shows the following information with fdisk in Ubuntu 14.04.4. Disk /dev/mapper/ddf1_00000000000000004b1b92914b1b92914b0400004b040001: 2000.3 GB, 2000315047936 bytes 255 heads, 63 sectors/track, 243191 cylinders, total 3906865328 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x3b9fee89 Device Boot Start End Blocks Id System /dev/mapper/ddf1_00000000000000004b1b92914b1b92914b0400004b040001p1 2048 3906865151 1953431552 83 Linux Disk /dev/mapper/ddf1_00000000000000004b1b92914b1b92914b0400004b040001p1: 2000.3 GB, 2000313909248 bytes 255 heads, 63 sectors/track, 243190 cylinders, total 3906863104 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/mapper/ddf1_00000000000000004b1b92914b1b92914b0400004b040001p1 doesn't contain a valid partition table --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: bblab 6762 F.... pulseaudio /dev/snd/controlC0: bblab 6762 F.... pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=433bcdda-b73d-47e7-abb8-8fab93db4123 InstallationDate: Installed on 2016-07-26 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X79-UP4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UP4:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1611277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp