disabled
> permanently, it will no longer create the metadata in the same place so you
> will never have this HPA problem agan, with ubuntu... ever, trust me, is
> painful but as long as you have the metadata inside the HPA area, nightmare
> is guaranteed.
>
>
> On Mon, Jul 5, 2
e HPA area, nightmare
is guaranteed.
On Mon, Jul 5, 2010 at 1:29 PM, NeCod wrote:
> I have tried EagleDM solution with HDAT2, and it doesn't works for me.
> If i disabled HPA, i cannot boot to RAID partition's: first member offline.
>
> My motheboard is GA-P35-DS4.
>
> --
&g
AS I already stated before and again, look for the HDAT2 utility, can be put
on a booteable CD (dos based)
Configure your hard disk as "IDE" (for the moment) boot with a booteable cd
and run HDAT2 (I think hdat2 comes with a booteable cd now)
Run HDAT2, and disable HPA from both disks.
Your pr
There is no way I can upload this.
Did everything you asked, when the login screen for Launchpad appears, I
put mail and password, but the "continue" option is greyed out, only
"cancel" is on blue, please, tell me, how do I suppose continue to
upload the log ???
--
Ubiquity does not detect /dev
Will do right away and post the log, thank you, hope this can be fixed.
--
Ubiquity does not detect /dev/sda (3 hdds)
https://bugs.launchpad.net/bugs/571007
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Public bug reported:
Binary package hint: ubiquity
using ISO dated 27-apr-2010 Ubuntu 10.04
Installing inside windows (wubi) after successfully booting, a screen
saying: "No root partition defined" appears and install can't procede.
using liveCD for full installation - After selecting custom
usi wrote:
> On 4/7/2010 12:14 PM, EagleDM wrote:
> > I do not agree.
> >
> > If you use the program HDAT2, boot from that and DISABLE HPA, the
> > program will disable it on the Firmware Level.
> >
> > At least in my case, with a Velociraptor RAID0 Arr
I do not agree.
If you use the program HDAT2, boot from that and DISABLE HPA, the
program will disable it on the Firmware Level.
At least in my case, with a Velociraptor RAID0 Array, both HPA's on both
disks were permanently disabled, I no longer have problems with Ubuntu
since I disabled it.
--
Strange
Upgraded to Karmic and the issue is Gone for me.
Now I have a new bug never present before Karmic, From time to time the cifs
responds something about memory error and I have to restart the Windows 7
server :(
On Fri, Jan 8, 2010 at 7:51 AM, Dicr wrote:
> This bug affect me too since
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
*** This bug is a duplicate of bug 219393 ***
https://bugs.launchpad.net/bugs/219393
thank you very much, will take a look at that bug and see if I can help in
any way.
On Fri, Jul 24, 2009 at 8:50 AM, danwood76 wrote:
> *** This bug is a duplicate of bug 219393 ***
> https://bugs.laun
*** This bug is a duplicate of bug 219393 ***
https://bugs.launchpad.net/bugs/219393
are you sure?
becasue libata.ignore_hpa=0 or libata.ignore_HPA=0 both gives me
"unknown kernel parameters - ignoring" at boot, and I can see the "HPA
Unlocked" after boot, but, when typing libata ignor
Let's hope, because, if they implement it, they will probably fix all
the error I am getting since Feisty, that, as of today, still aren't
fixed.
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/403733
--
dmraid / FakeRAID support should work automatically in installers.
https://bugs.launch
Public bug reported:
Binary package hint: dmraid
Either running with "libata ignore_hpa=0" option or ata_ignore_hpa=0
or no options at all, after correctly installing dmraid
sudo apt-get dmraid -ay
dmraid -ay
and RAID setup correctly, after shutdown, RAID information is lost
forever (HPA) an
** 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.
HPA ignore by default is a DISGRACE decision, basically what it does, is
if you are already using DMRAID for MatrixRAID, NVRAID, etc, etc, it
simply destroys the hpa information on boot, and this cannot be fixed.
After tedious testing I found out that, once a single boot is made with
HPA ignoring
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 K
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:~$
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
https:
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 firs
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 first
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 detaile
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
htt
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: hp
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 ICH1
DMRAID is so bugged that now I'm afraid of just using it and wasting my
entire array, someone should definetly post on the kernel bug tracker,
we don't need more bugs, with dmraid alone is enough.
--
system does not boot due to device-mapper error
https://bugs.launchpad.net/bugs/398059
You receiv
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, w
I can confirm this also, with ICH10R, I filed a bug and I am
experiencing the same problem, cannot get activated and cannot boot with
dmraid with the same message.
--
system does not boot due to device-mapper error
https://bugs.launchpad.net/bugs/398059
You received this bug notification because
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 subscri
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
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 di
I already did, thank you :)
--
host protected area prevents detection of isw (intel matrix storage manager)
raid arrays
https://bugs.launchpad.net/bugs/372170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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 detect
Public bug reported:
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_gsdeee
I manually wipe clean both disks with /dev/zero, I created both arrays
on BIOS, same thing, there is no way the second array becomes active, it
always stays in "inactive"
When succesfully installed dmraid and after creating second subset,
linux kernel will not boot correctly staying "sdc size too
I can confirm DMRAID does not work correctly on ICH10R controller.
I have 2 velociraptors 150Gb in RAID0 with 2 subsets, 1 - 100Gb 2-
178Gb (gaming - main)
The first array is correctly identified and activated, the second array stays
in "array inactive"
I have no messages of #wrong number
I already talked about this problem hundreads of times, I was an avid
supporter of RAID devices, being using them since 6 to 8 years now.
Ive stopped using RAID last year because toons of problems with Ubuntu.
First we have the terrible idea to simply ignore the HPA (which is a
setting that no OS
Phillip, I have a simple solution to this problem, could you pass this
suggestion to the guys at Intrepid Ibex development?
This could be simply "fixed" if the LiveCD / Installer "ask" for RAID
support BEFORE starting a machine.
A simple query that could tell ubuntu which parameter to ser "to
To eliminate CIFS mounts you only have to do this:
cd /etc/rc6.d
ls -la
Type:
sudo mv S31umountnfs.sh S14umountnfs.sh
then cd to rc6.0
type the same line as before.
That should fix the problem.
That 2 steps is the ONLY thing you have to do after installing ubuntu.
Daniel
On Sat, Jul 26,
Success !!
You are a genious !!
I could never find out on my own, but after doing dmraid -n as suggested
on the forums and by your suggestion of a possible broken RAID, whoala!
that bloody NVRAID was sitting right onto that disk, I deleted the
metadata with -E and that's it, the thing boots perf
Brilliant!
It maybe what your saying, will do right away and post results!
If I delete all the partitions on disk, does the nvraid partition data
gets deleted?
I believe that you answering that will pretty much resolve this whole
issue :)
--
dmraid package destroys initrd and render system unb
Yes i have, Vista is booting off the drive just perfect.
dmraid -ay just after installliut any problems, the caos begins just
when I restart the machine "after" installing dmraid.
I mean to tell you, this problem started to appear in hardy heron, I
didn't have any problems with dmraid with feisty
This thread talks about the SAME problem I have.
The solution offered there though is not working for me, I could not
mount device.
http://ubuntuforums.org/showthread.php?t=772107
Is there any plans to fix this on Intrepid and have dmraid by default?
--
dmraid package destroys initrd and rende
dmraid -b
/dev/sdc:625142448 total, "3QH01TSX"
/dev/sdb:625142448 total, "3QF0A6AT"
/dev/sda:625142448 total, "6RV010Q9"
fdisk -l
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier
Is there anybody out there that can confirm what I am experiencing?
This bug is soo much easy to reproduce it kills me how there is nobody
out there experiencing this issue.
--
dmraid package destroys initrd and render system unbooteable (ubuntu Hardy)
https://bugs.launchpad.net/bugs/245842
You
I am very sorry about not providing accurate information, you are right
indeed, menu.lst indeed says (hd0,1) and it WAS NOT touched in any way
by me.
Installed hardy, boot it correcly, as soon as I install dmraid and
restart PC the system becomes unbooteable, I am not touching any
menu.lst or anyt
Intel Matrix RAID (on ICH9R) created on Windows.
3 HDD-
0 - SATA320GB (3 partitions) Non-RAID =1-windows (16Gb) 2 linux
ext3 (16gb) 3 - ntfs (backup win/linux)
1- SATA320GB (RAID0) - NTFS
2- SATA320GB (RAID0) - NTFS
The linux boot disk is recognized as /dev/sda2 of course and this
** Description changed:
Binary package hint: dmraid
As the title says.
I work for a hardware reviews site and I've could reproduce this bug on
3 machines already.
It is pretty simple:
On any machine based on Intel ICH8R-ICH9R with Matrix RAID active
- installing windows on
Public bug reported:
Binary package hint: dmraid
As the title says.
I work for a hardware reviews site and I've could reproduce this bug on
3 machines already.
It is pretty simple:
On any machine based on Intel ICH8R-ICH9R with Matrix RAID active
installing windows on a separate disk, do a cl
Yes, totally agree, also, I reported this bug a while ago, when hardy was in
beta stage, this could had being easily patched, there are a lot of us that
are using cifs shares, this is not a minor issue.
On Thu, May 8, 2008 at 5:39 PM, Peter Schneider <[EMAIL PROTECTED]>
wrote:
> I can confirm thi
The fix provided Teih Han Hui quicky fix it for me (hardy heron final),
it's a shame it wans't included being so easy to implement, just a change in
the RC order.
On Wed, May 7, 2008 at 1:29 AM, Laurent Dinclaux <[EMAIL PROTECTED]>
wrote:
> problem still present in hardy at time of writing
>
>
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
Yes I know, i read a quick fix replacing order in rc and it works like a
charm, don't know why it wans't included being so easy
On Fri, May 2, 2008 at 6:58 AM, Jerry West <[EMAIL PROTECTED]>
wrote:
> *** This
me neither
On Wed, Apr 30, 2008 at 12:55 PM, aidave <[EMAIL PROTECTED]> wrote:
> I havent experienced it again either
>
> --
> compiz.real crashed with signal 7 in eventLoop()
> https://bugs.launchpad.net/bugs/191365
> You received this bug notification because you are a direct subscriber
> of th
Sorry, got confused with another bug number
I was referring to THIS patch
https://bugs.launchpad.net/bugs/153444
I did not try the sysvinit
the aparent problem with closing network CIFS shares is present here:
https://bugs.launchpad.net/bugs/153444
The problem seems related to the way ubuntu
I did not experienced any boot problems after applying the Patch.
The problem is more serious "without" the Patch than with it, because
basically, if you do not apply this patch, shutdown hangs waiting and you
have to manually shut down the pc or reset which is dangerous.
It should be an altern
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
Using this script with the following commands totally fixed the shutdown
problem.
I leave this I found in the forums, maybe the developers can include it
to totally fix this BUG that it's present since Edgy.
*** This bug is a duplicate of bug 42121 ***
https://bugs.launchpad.net/bugs/42121
I am also confirming this, I'm using Hardy Heron BETA release from daily
build (date april 2 2008) so you see, this is NOT fixed.
Have to manually "umount -a" before shutdown and everything works but
this SHO
Option to "add" custom settings in Hardy Heron should NOT depend on
simple-ccsm since is way underpowered compared to ccsm.
users should have the extra option link directly to simple-ccsm and give
the advanced users the ability to run "custom" with a direct link to
ccsm (if installed) not simple-c
This is the text from apt-get install compizconfig-settings-manager
(hardy heron)
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the s
59 matches
Mail list logo
