You are not logged in.
A while ago I got a second hand computer with some kind of RAID controller. After a few investigations I figured out that it is some kind of fake RAID controller from jmicron. To get it running I had to face some naming problems, since the RAID controller filles the RAID partition name with whitespaces, leading to device nodes with whitespaces in their names causing problems with partitioning on installation time.
I solved these issues by filling up the RAID partition name with x-es, so my RAID is named "jmicron_GRAIDxxxxxxxxxxx" (the "jmicron_" prefix is added by the controller). When booting, dmraid tries to open "/dev/mapper/jmicron_GRAIDxxxxxxxxxxx" which worked well for a while.
On Thursday I ran "pacman -Syu" after a few weeks not using the computer in question and when I tried to boot it now, the RAID set "jmicron_GRAIDxxxxxxxxxxx" can be activated but "/dev/mapper/jmicron_GRAIDxxxxxxxxxxx" can not be opened. There is indeed no such file in /dev/mapper but a file named "jmicron_GRAIDxxxxxxxxxxx\x01".
And now I have no idea how to fix it or what to google.
Last edited by CAS (2012-04-14 20:10:34)
Offline
I figured out, that dmraid from my Arch live disc still works. A comparison of both programs versions showed as only difference that the live disc dmraid uses device mapper 4.20.0 and my boot image's dmraid uses divice mapper 4.22.0.
So my question changed to: How can I get the device mapper from my live disc to my boot image or how can I downgrade device mapper on my boot image?
Offline