DMRAID only detect first subset on Intel ICH10R
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dmraid (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: dmraid
Ubuntu Karmic Koala build 20 July 2009
When running DMRAID in a newly created (from BIOS) pair of arrays on Velociraptors 150Gb
0 - 100Gb RAID0 - 32k Stripe (GAMING)
1- 178Gb RAID0 - 32k Stripe (MAIN)
dmraid -ay
I got the message
isw_gsdeeedfh_
isw_gsdeeedfh_MAIN is not active
(GAMING1 and MAIN1 are not displayed since I still didn't create any NTFS partition, when I first did it it was displaying
isw_gsdeeedfh_
isw_gsdeeedfh_MAIN is not active
isw_gsdeeedfh_
nor dmraid -ay -vvv nor -s gives any details on why the second subset is not being activated.
Already tried with the libata option for HPA ignore=0 on kernel but, not good, also, accidentally sometimes kernel will not boot with the message "/dev/sdc" too short repeating over and over getting stuck, only fix for now is to remove second subset and everything works, but I lost 178Gb of space, this does not seem to be related to HPA nor the famous "wrong # of devices" since I am creating the arrays on newly purchased disks.
My current machine:
Core i7 920
12Gb RAM
2 x velociraptors
ECS X58 with ICH10R
This bug is a total showstopper, I was planning to use this machine in conjuntion with Virtualbox to use multiple machines running directly from the RAID0
Related branches
Danny Wood (danwood76) wrote : | #1 |
EagleDM (eagle-maximopc) wrote : | #2 |
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
EagleDM (eagle-maximopc) wrote : | #3 |
Here we go:
daniel@Lizzie:~$ sudo dmraid -ay -ddd -vvv
WARN: locking /var/lock/
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: isw metadata discovered
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching isw_bhcifgjhfa
DEBUG: _find_set: not found isw_bhcifgjhfa
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: not found isw_bhcifgjhfa_
DEBUG: _find_set: not found isw_bhcifgjhfa_
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: not found isw_bhcifgjhfa_
DEBUG: _find_set: not found isw_bhcifgjhfa_
DEBUG: _find_set: not found isw_bhcifgjhfa_
NOTICE: added /dev/sdc to RAID set "isw_bhcifgjhfa"
DEBUG: _find_set: searching isw_bhcifgjhfa
DEBUG: _find_set: found isw_bhcifgjhfa
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: found isw_bhcifgjhfa_
DEBUG: _find_set: found isw_bhcifgjhfa_
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: searching isw_bhcifgjhfa_
DEBUG: _find_set: found isw_bhcifgjhfa_
DEBUG: _find_set: found isw_bhcifgjhfa_
NOTICE: added /dev/sdb to RAID set "isw_bhcifgjhfa"
DEBUG: checking isw device "/dev/sdb"
DEBUG: checking isw device "/dev/sdc"
DEBUG: set status of set "isw_bhcifgjhfa
DEBUG: checking isw device "/dev/sdb"
DEBUG: checking isw device "/dev/sdc"
DEBUG: set status of set "isw_bhcifgjhfa
RAID set "isw_bhcifgjhfa
RAID set "isw_bhcifgjhfa
INFO: Activating GROUP raid set "isw_bhcifgjhfa"
NOTICE: discovering partitions on "isw_bhcifgjhfa
NOTICE: /dev/mapper/
EagleDM (eagle-maximopc) wrote : | #4 |
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 it seems this is pretty serious.
EagleDM (eagle-maximopc) wrote : | #5 |
More testing, wipe clean both disk, creating a single RAID array of the entire disk bring about the same problem.
EagleDM (eagle-maximopc) wrote : | #6 |
my bug seems related to this bug
https:/
I am experiencing the same issues.
Danny Wood (danwood76) wrote : | #7 |
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.
Danny Wood (danwood76) wrote : | #8 |
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.
EagleDM (eagle-maximopc) wrote : | #9 |
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.
Danny Wood (danwood76) wrote : | #10 |
When you get to the stage of "cannot be activated" post the debug output for comparison.
sudo dmraid -ay -ddd -vvv
EagleDM (eagle-maximopc) wrote : | #11 |
Here you have:
daniel@Lizzie:~$ sudo dmraid -ay -ddd -vvv
NOTICE: creating directory /var/lock/dmraid
WARN: locking /var/lock/
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: isw metadata discovered
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching isw_bifiajiffg
DEBUG: _find_set: not found isw_bifiajiffg
DEBUG: _find_set: searching isw_bifiajiffg_
DEBUG: _find_set: searching isw_bifiajiffg_
DEBUG: _find_set: not found isw_bifiajiffg_
DEBUG: _find_set: not found isw_bifiajiffg_
NOTICE: added /dev/sdc to RAID set "isw_bifiajiffg"
DEBUG: _find_set: searching isw_bifiajiffg
DEBUG: _find_set: found isw_bifiajiffg
DEBUG: _find_set: searching isw_bifiajiffg_
DEBUG: _find_set: searching isw_bifiajiffg_
DEBUG: _find_set: found isw_bifiajiffg_
DEBUG: _find_set: found isw_bifiajiffg_
NOTICE: added /dev/sdb to RAID set "isw_bifiajiffg"
DEBUG: checking isw device "/dev/sdb"
DEBUG: checking isw device "/dev/sdc"
DEBUG: set status of set "isw_bifiajiffg
RAID set "isw_bifiajiffg
INFO: Activating GROUP raid set "isw_bifiajiffg"
WARN: unlocking /var/lock/
DEBUG: freeing devices of RAID set "isw_bifiajiffg
DEBUG: freeing device "isw_bifiajiffg
DEBUG: freeing device "isw_bifiajiffg
DEBUG: freeing devices of RAID set "isw_bifiajiffg"
DEBUG: freeing device "isw_bifiajiffg", path "/dev/sdb"
DEBUG: freeing device "isw_bifiajiffg", path "/dev/sdc"
daniel@Lizzie:~$
Giuseppe Iuculano (giuseppe-iuculano) wrote : Re: [Bug 401713] Re: DMRAID only detect first subset on Intel ICH10R | #12 |
Hi,
EagleDM ha scritto:
> RAID set "isw_bifiajiffg
I just uploaded a dmraid version in my PPA that should fix your issue, please
test it:
https:/
dmraid - 1.0.0.rc15-11~ppa1 for jaunty
dmraid - 1.0.0.rc15-11~ppa2 for karmic
Cheers,
Giuseppe.
EagleDM (eagle-maximopc) wrote : | #13 |
Will try it right away ! thank you !!
EagleDM (eagle-maximopc) wrote : | #14 |
Ok, here is getting really weird, take a look at this..
With only 1 array, same as before, with 2 arrays, this happens.
aniel@Lizzie:~$ sudo dmraid -ay
[sudo] password for daniel:
RAID set "isw_bhhagfbig_
RAID set "isw_bhhagfbig_
the detailed report says this:
daniel@Lizzie:~$ sudo dmraid -ay -ddd -vvv
WARN: locking /var/lock/
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
DEBUG: isw metadata found at 150039944192 from probe at 150039944192
NOTICE: /dev/sdc: isw metadata discovered
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
DEBUG: isw metadata found at 150039944192 from probe at 150039944192
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
DEBUG: not isw at 64105741312
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 64104659456
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching isw_bhhagfbig
DEBUG: _find_set: not found isw_bhhagfbig
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: not found isw_bhhagfbig_
DEBUG: _find_set: not found isw_bhhagfbig_
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: not found isw_bhhagfbig_
DEBUG: _find_set: not found isw_bhhagfbig_
DEBUG: _find_set: not found isw_bhhagfbig_
NOTICE: added /dev/sdc to RAID set "isw_bhhagfbig"
DEBUG: _find_set: searching isw_bhhagfbig
DEBUG: _find_set: found isw_bhhagfbig
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: found isw_bhhagfbig_
DEBUG: _find_set: found isw_bhhagfbig_
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: searching isw_bhhagfbig_
DEBUG: _find_set: found isw_bhhagfbig_
DEBUG: _find_set: found isw_bhhagfbig_
NOTIC...
EagleDM (eagle-maximopc) wrote : | #15 |
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 ?
Giuseppe Iuculano (giuseppe-iuculano) wrote : | #16 |
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 ignore_hpa=0
Cheers,
Giuseppe.
EagleDM (eagle-maximopc) wrote : | #17 |
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
Giuseppe Iuculano (giuseppe-iuculano) wrote : | #18 |
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
>
In case you are trying the patched dmraid version with karmic, can you try it
with jaunty please?
Cheers,
Giuseppe.
EagleDM (eagle-maximopc) wrote : | #19 |
I'm installing Jaunty right now :)
EagleDM (eagle-maximopc) wrote : | #20 |
Well well, Jaunty fresh install, libata.ignore_HPA=0 in kernel, sudo apt-get install dmraid
this is what I got:
daniel@Lizzie:~$ sudo dmraid -ay
[sudo] password for daniel:
RAID set "isw_dcjdajjhfa
RAID set "isw_dcjdajjhfa
daniel@Lizzie:~$ sudo dmraid -an
daniel@Lizzie:~$ sudo dmraid -ay -ddd -vvv
WARN: locking /var/lock/
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: isw metadata discovered
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching isw_dcjdajjhfa
DEBUG: _find_set: not found isw_dcjdajjhfa
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
NOTICE: added /dev/sdc to RAID set "isw_dcjdajjhfa"
DEBUG: _find_set: searching isw_dcjdajjhfa
DEBUG: _find_set: found isw_dcjdajjhfa
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: found isw_dcjdajjhfa_
DEBUG: _find_set: found isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdaj...
EagleDM (eagle-maximopc) wrote : | #21 |
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 Karmic due to this...
here it is the log with your patched version too:
daniel@Lizzie:~$ sudo dmraid -ay -ddd -vvv
WARN: locking /var/lock/
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
DEBUG: isw metadata found at 150039944192 from probe at 150039944192
NOTICE: /dev/sdc: isw metadata discovered
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
DEBUG: isw metadata found at 150039944192 from probe at 150039944192
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
DEBUG: not isw at 64105741312
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 64104659456
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching isw_dcjdajjhfa
DEBUG: _find_set: not found isw_dcjdajjhfa
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
DEBUG: _find_set: not found isw_dcjdajjhfa_
NOTICE: added /dev/sdc to RAID set "isw_dcjdajjhfa"
DEBUG: _find_set: searching isw_dcjdajjhfa
DEBUG: _find_set: found isw_dcjdajjhfa
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_
DEBUG: _find_set: found isw_dcjdajjhfa_
DEBUG: _find_set: found isw_dcjdajjhfa_
DEBUG: _find_set: searching isw_dcjdajjhfa_V...
Changed in dmraid (Ubuntu): | |
assignee: | nobody → Giuseppe Iuculano (giuseppe-iuculano) |
EagleDM (eagle-maximopc) wrote : | #22 |
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 HPA area on disks, and HDAT2 utility REALLY helped, not only does DMRAID now works with the new kernel, I am no longer experiencing the "Offline Member" message that drove me crazy since memorial times.
Thank you all for your effort!
PD: We need to spread this, most problems with RAID could be solved easily by eliminating the HPA area on HDDs.
Changed in dmraid (Ubuntu): | |
assignee: | Giuseppe Iuculano (giuseppe-iuculano) → nobody |
status: | New → Fix Released |
Tormod Volden (tormodvolden) wrote : | #23 |
I don't see 15_activate_
Changed in dmraid (Ubuntu): | |
status: | Fix Released → Fix Committed |
Launchpad Janitor (janitor) wrote : | #24 |
This bug was fixed in the package dmraid - 1.0.0.rc15-11build1
---------------
dmraid (1.0.0.
* Fakesync from Debian
dmraid (1.0.0.rc15-11) unstable; urgency=low
* [ce4e2dc] 15_activate_
raid sets instead of returning after processing the first. (LP: #401713)
* [58a1426] debian/
the exit code before parsing output, thanks to Tormod Volden.
(Closes: #542256) (LP: #415280, #376792)
* [91d2b67] Updated to standards version 3.8.3 (No changes needed)
-- Luke Yelavich <email address hidden> Thu, 27 Aug 2009 08:29:15 +1000
Changed in dmraid (Ubuntu): | |
status: | Fix Committed → Fix Released |
quequotion (quequotion) wrote : | #25 |
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.
Paul Smith (ubuntu-gaivota) wrote : | #26 |
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 thread, the reason for such configuration was just bare raw performance. Btw, didn't install Karmic on the first set because it's already being fully used for other purposes and OS's.
I'm most positive that unfortunately this will slip throw on to the final 9.10 release.
Tormod Volden (tormodvolden) wrote : | #27 |
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.
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