Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#20333 - [dmraid] device-mapper fails to find kernel module raid45

Attached to Project: Arch Linux
Opened by Daniel K. Attling (jingo) - Saturday, 31 July 2010, 22:42 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 09 March 2012, 08:11 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity High
Priority Normal
Reported Version 2010.05
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

`dmraid -ay` fails to activate my intel ich10r fake raid5 volume with a device-mapper error message stating that kernel module raid45 isn't loaded. raid45 was replaced by raid456 module in mainline in 2006.

`dmraid -s` and `dmraid -r` display both the volume and member disks just fine.

`dmraid --version`:
dmraid version: 1.0.0.rc16-3 (2010.01.12)
dmraid library version: 1.0.0.rc16-4 (2010.02.17)
device-mapper version: 4.17.0

`dmraid -ay`:
ERROR: device-mapper target type "raid45" is not in the kernel
RAID set "isw_dgcchegghf_Volume0" was not activated
ERROR: device "isw_dgcchegghf_Volume0" could not be found

The behavior is the same in 32 and 64-bit mode.

Googling for clues I stumbled across a old ubuntu bug report for this issue from 2007 which looks to still not having been resolved there.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411172
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 09 March 2012, 08:11 GMT
Reason for closing:  Upstream
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 08 December 2010, 20:19 GMT
  • Field changed: Attached to Project (Release Engineering → Arch Linux)
  • Field changed: Summary (dmraid: device-mapper fails to find kernel module raid45 → [dmraid] device-mapper fails to find kernel module raid45)
Moving this "lost" ticket to correct location.

What is the status of this issue?
Comment by Cédric M. Campos (cedricmc) - Tuesday, 07 February 2012, 08:19 GMT
  • Field changed: Percent Complete (100% → 0%)
The bug is still present on the installation release 2011.08.19.

I had to switch to another distro due to the impossibility of installaing ArchLinux.

PS: although dmraid was able to detect a RAID1 (in a previous setting), it could not load it.
Comment by Tobias Powalowski (tpowa) - Tuesday, 07 February 2012, 08:28 GMT
What is the other distro doing?
Comment by Cédric M. Campos (cedricmc) - Tuesday, 28 February 2012, 10:37 GMT
The other distro is doing fine, thx for asking ;)

As I guess you prefer a bit more details. The other distro I am referring to is Fedora 16. Steps I realized:

01) Boot into ArchLinux installation media (2011.08.19). It doesn't seem to recognize my RAID1 (I get the error described above). No problem, what I really want to do is to setup a new RAID5 (with an extra HD I got) and install ArchLinux on it.
02) Setup RAID5
03) Boot into ArchLinux installation media. I get the error mentioned in the bug details (and an extra complain about "sil" and "isw", but it chooses "isw" as expected).
04) I install ArchLinux in a USB pendrive.
05) Boot into ArchLinux USB pendrive "fully" updated system. dmraid still does not properly recognize the RAID5 (I don't remember exactly the error message, I think it was still the same, but not sure).
06) I swear and curse (a lot).
07) Boot into Fedora 16 installation media. It recognizes properly the RAID5 (through mdadm) and I succeed to install the distro on it (using GTP, bad since I want to install Win7 too).
08) Reboot into ArchLinux installation media with nodmraid kernel option. Surprisingly, mdadm recognizes the RAID5 on /dev/md126 ant its partitions.
09) Start installation process. Weird situation: even though the install program recognizes the partitions, they are not shown when defining the root structure.
10) I swear and curse (a lot more).
11) Reboot into F16. Everything is fine.
12) Reboot into ArchLinux installation media with nodmraid kernel option. It does no longer recognize the RAID5.
13) Reboot into ArchLinux USB pendrive "fully" updated system. Uninstall dmraid.
14) Reboot into ArchLinux USB pendrive "fully" updated system. mdadm recognizes the RAID5 on /dev/md126 ant its partitions.

The story continues with more tries, fails and the appropriate swearing and cursing, but none of it may bring more light to this problem.

Resuming:
+ On the ArchLinux installation media 2011.08.19:
- dmraid does not work as expected, it fails to recognize some chipsets or RAID configurations.
- mdraid idem.
+ On a fully updated ArchLinux system:
- dmraid still does not work as expected, it continue to fail to recognize some chipsets or RAID configurations.
- mdraid works fine.

Besides:
F16 no longer uses dmraid in favor of mdadm. For me it was surprising since, as far as I know, the main developer of dmraid was a redhat employee. It also seems that dmraid is no longer being developed.

Conclusion:
Due to outdated software, ArchLinux installation media fails to install on some RAID configurations.

Petition:
From all the above, it would be nice if you could update the ArchLinux installation media such that:
- dmraid is deprecated.
- mdraid is fully supported.
- grub2 is fully supported (note that this is the only way of having multiboot systems on almost all RAID configurations).

BTW https://bugs.archlinux.org/task/25888 seems to be a duplicate of this.
Comment by Tobias Powalowski (tpowa) - Friday, 09 March 2012, 08:11 GMT
This is pretty not fixable and depends on the hardware you use what is best for you.
mdadm is not the solution for everything as dmraid is not the solution for everything.

I cannot do anything here.

Loading...