Installer from a karmic AMD64 desktop version (10/13/09) didn't find the
second RAID set.
Even when full boot with Live CD, GParted also didn't properly see the
2nd set.
Details: Tested with 2 hard drives x 1.0TB, Raid0 (ICH10R), splitted in
two sets (300GB + 1.7GB). As mentioned before on the
Paul, did you wipe any HPA like in comment 22? Otherwise, you must have
a different issue (although the symptoms are the same) so please file
new bug report using ubuntu-bug dmraid and attach the dmraid -ay -ddd
-vvv output.
--
DMRAID only detect first subset on Intel ICH10R
Would this fix have any effect on the bug with installing a new system
to raid or upgrading a system already installed to raid? I'll give it a
try later but I'm far from my PC at the moment.
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
You received
This bug was fixed in the package dmraid - 1.0.0.rc15-11build1
---
dmraid (1.0.0.rc15-11build1) karmic; urgency=low
* Fakesync from Debian
dmraid (1.0.0.rc15-11) unstable; urgency=low
* [ce4e2dc] 15_activate_multiple_raid_sets.patch: Continue onto all
raid sets instead of
I don't see 15_activate_multiple_raid_sets.patch has been released in
Karmic yet, so setting back bug status.
** Changed in: dmraid (Ubuntu)
Status: Fix Released = Fix Committed
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
You received this
The road to success:
I'm happy to report that after doing this 2 steps, DMRAID is working, finally,
perfectly fine with Karmic.
1- use HDAT2 utility to completly wipe out the HPA from both disks.
2- update kernel to 2.6.31-5
I'm confident that most DMRAID problems are due to that freaking
Well well, Jaunty fresh install, libata.ignore_HPA=0 in kernel,
sudo apt-get install dmraid
this is what I got:
dan...@lizzie:~$ sudo dmraid -ay
[sudo] password for daniel:
RAID set isw_dcjdajjhfa_Volume0 already active
RAID set isw_dcjdajjhfa_Volume1 already active
dan...@lizzie:~$
Again, with your patched version, everything went perfectly fine in
Jaunty, I don't have your knoledge here, but, my gut instint tells me
this is definetly an issue with the kernel 2.6.31 in Karmic, we should
comment this to the kernel devs, it could be a disaster to have a non-
working dmraid in
** Changed in: dmraid (Ubuntu)
Assignee: (unassigned) = Giuseppe Iuculano (giuseppe-iuculano)
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm installing Jaunty right now :)
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
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
When you wiped the disk and created the single array could you post the output
of the above debug command for us. (sudo dmraid -ay -ddd -vvv)
Its a bit annoying trying to debug something when you don't give the full debug
output as you go.
--
DMRAID only detect first subset on Intel ICH10R
Also could you try installing Ubuntu 9.04 (Jaunty) with the two array setup.
It would be interesting to know weather this issue is visible in the stable
release.
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
You received this bug notification because
Going to try Jaunty right away and post results.
Created a single array, same results, cannot be activated
Strange, when I create 2 arrays, only the first one gets activated, when
I create a single one, it behaves exactly like the second one.
--
DMRAID only detect first subset on Intel
When you get to the stage of cannot be activated post the debug output for
comparison.
sudo dmraid -ay -ddd -vvv
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here you have:
dan...@lizzie:~$ sudo dmraid -ay -ddd -vvv
NOTICE: creating directory /var/lock/dmraid
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc:
Hi,
EagleDM ha scritto:
RAID set isw_bifiajiffg_raid0 was not activated
I just uploaded a dmraid version in my PPA that should fix your issue, please
test it:
https://edge.launchpad.net/~giuseppe-iuculano/+archive/ppa
dmraid - 1.0.0.rc15-11~ppa1 for jaunty
dmraid - 1.0.0.rc15-11~ppa2 for
Will try it right away ! thank you !!
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
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
Ok, here is getting really weird, take a look at this..
With only 1 array, same as before, with 2 arrays, this happens.
an...@lizzie:~$ sudo dmraid -ay
[sudo] password for daniel:
RAID set isw_bhhagfbig_Volume0 already active
RAID set isw_bhhagfbig_Volume1 was not activated
the detailed
It got my attention this line:
DEBUG: not isw at 64105741312
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 64104659456
which was not before with the standard dmraid rc15, could this has something to
do with ICR10R changing the way it creates arrays ?
--
DMRAID only detect
EagleDM ha scritto:
DEBUG: not isw at 64105741312
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 64104659456
which was not before with the standard dmraid rc15, could this has something
to do with ICR10R changing the way it creates arrays ?
Yes, but please try with
Already set to ignore_hpa=0
If I don't pass that parameter to the kernel, it just destroys my
complete array, next time I turn on the PC the array displays as
Failed and do not come alive never more :(
So, as I stated in the begining, I always use the ignore_hpa=0
--
DMRAID only detect first
EagleDM ha scritto:
Already set to ignore_hpa=0
If I don't pass that parameter to the kernel, it just destroys my
complete array, next time I turn on the PC the array displays as
Failed and do not come alive never more :(
So, as I stated in the begining, I always use the ignore_hpa=0
When you say you create 2 arrays why are you not creating 1 array and
partitioning it?
Could you post the output of 'sudo dmraid -ay -ddd -vvv' which will give
a detailed version of whats going on.
regards,
Danny
--
DMRAID only detect first subset on Intel ICH10R
shortstroking the first partition gives me better overall performance
than just partitioning, at least on every program I tried, but,
considering the problems I'm having I think I will have to do a single
array with partitions.
I will give you the output as soon as possible
--
DMRAID only
Here we go:
dan...@lizzie:~$ sudo dmraid -ay -ddd -vvv
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw
Also, right after making the array in BIOS, booting to Ubuntu and
installing dmraid you can get that, but, as soon as you try to boot the
PC again, it will get stuck in No such device (next boot) in an
infinite loop and the only way to fix it is to destroy the Volume1, boot
and remove dmraid, so
More testing, wipe clean both disk, creating a single RAID array of the
entire disk bring about the same problem.
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
You received this bug notification because you are a member of Ubuntu
Bugs, which is
my bug seems related to this bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/398059
I am experiencing the same issues.
--
DMRAID only detect first subset on Intel ICH10R
https://bugs.launchpad.net/bugs/401713
You received this bug notification because you are a member of Ubuntu
Bugs,
28 matches
Mail list logo
