Adding linux target since this is a kernel bug.
** Changed in: dmraid (Ubuntu)
Importance: Undecided = Medium
** Changed in: dmraid (Ubuntu)
Status: New = Triaged
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance:
** Description changed:
- Binary package hint: dmraid
+ When dmraid tries to activate a raid5 array, it appears to send down bad
+ parameters to device-mapper, causing it to print:
- Description: Ubuntu 10.10
- Release: 10.10
+ device-mapper: table: 252:9: raid45: Invalid RAID device
As requested sir, here is your metadata.
** Attachment added: Metadata of RAID 2 (Darkness)
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/666577/+attachment/1773416/+files/metadata.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm starting to think this is a bug in the raid4-5 driver. I'm seeing
this in my kernel log:
Dec 22 21:56:30 faldara kernel: [ 1939.397600] device-mapper: ioctl: device
doesn't appear to be in the dev hash table.
Dec 22 21:56:30 faldara kernel: [ 1939.417446] quiet_error: 9 callbacks
Hrm... the attached files only seem to contain the record for darkness
and so are incomplete and unrecognizable. Please run this and attach
the resulting file:
for f in sda sdb sdc ; do sudo dd if=/dev/$f of=$f.dat skip=625142320 ;
done ; tar cjf metadata.tar.bz2 sd[abc].dat
--
You received
I've found the problem and a work-around. dmraid is incapable of
handling metadata which is written into RAID arrays by Intel's Matrix
program. dmraid errors on the metadata and crashes. If someone would
be so kind as to code something into dmraid to either ignore or utilize
the metadata, it
No, dmraid certainly supports Intel's Matrix Raid. If it crashes with
your specific metadata, please post the exact command and output. I
notice that you appear to have the array divided up into two named
volumes, Light and Darkness. Last I heard there were problems with
doing that. I will try
Actually, I don't have the array itself divided into two volumes, I have
the three drives divided into two raid 5 arrays. Darkness doesn't get
used as much as it used to be my XP partition. However, I found that I
used my Vista and, later, Win 7 more often so I removed XP and left it
as a
I'm guessing nobody's going to be working on this anytime soon. For
some reason, it's still having trouble identifying my isw drive. I
think we might need to go about a different means of identifying and
adapting to it.
--
You received this bug notification because you are a member of Ubuntu
I'm compiling it using the source from synaptic. But this bug isn't
about compilation errors; it's about the startup error. I only put the
compilation error there as a point of reference should the source need
to be looked at.
--
dmraid fails on start with ICH9R under RAID 5
How are you compiling the Ubuntu kernel source?
You will need to use dpkg as there will be a lot of debian/ubuntu patches to
the main source!
This will quite often leave you with errors like you got above.
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
cannot install Ubuntu Server 10.10 on Intel fakeRAID5.
i get this message:
ERROR: device-mapper target type raid45 not in kernel.
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
You received this bug notification because you are a member of Ubuntu
Bugs,
Did you recompile or use a non-standard kernel than what came with
Ubuntu?
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Here is the output of dmraid from my terminal:
er...@ubuntu:~$ sudo dmraid -ay - -
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sde: asr discovering
NOTICE: /dev/sde: ddf1discovering
NOTICE: /dev/sde: hpt37x discovering
NOTICE: /dev/sde: hpt45x discovering
NOTICE: /dev/sde:
Okay everyone, it goes deeper! I tried recompiling the Linux kernel to
incorporate a few changes and to see if I could get dmraid to work
correctly. The following is my result:
ubuntu/built-in.o: In function `dm_rh_dec':
Okay, I'm going over the code now. I'm a novice so I might be wrong
here. But, I've changed uint32_t to unsigned long int and I've added a
LOT of semi-colons to void and struct statements. I think a number of
structs could have been changed to typeref, but I'm not a programmer.
If someone would
Well, I finished (sort of) and it wasn't pretty to say the least.
Basically, it needs to have a few punctuations moved and needs to have
the code refined quite a bit. There's also a problem with incompatible
types in one of the declared variables. If someone that knows what
they're doing would
I mean that it failed to mount my raid arrays. Using sudo dmraid -ay only
causes it to set there on the terminal with a blinking cursor doing nothing. I
can type in it like it's waiting for something, but it's to no avail.
As for ls /dev/mapper, it only shows the file control.
--
dmraid
Update to messages: When I try to run ubuntu without the nodmraid
option and quiet enabled, I receive a message device-mapper: table
252:5: raid45: Invalid RAID device offset parameter. Something tells
me that the problem isn't so much in dmraid itself as much as the RAID45
module.
--
dmraid
What do you mean it failed to mount? What does ls /dev/mapper show?
And sudo dmraid -ay?
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
21 matches
Mail list logo
