ubuntu9 I was referring to the dmraid package, patch #9. If you are
having problems with ubuntu and intel raid 10, I suggest you upgrade
to intrepid or jaunty (testing).
"This bug was fixed in the package dmraid - 1.0.0.rc14-2ubuntu9"
On Mon, Dec 29, 2008 at 8:21 AM, Rch wrote:
> Hi,
>
> unfo
Thank you, as far as I can tell it works,
[EMAIL PROTECTED]:/# dmraid -r
/dev/sdd: isw, "isw_jceibccac", GROUP, ok, 976773165 sectors, data@ 0
/dev/sdc: isw, "isw_jceibccac", GROUP, ok, 976773165 sectors, data@ 0
/dev/sdb: isw, "isw_jceibccac", GROUP, ok, 976773165 sectors, data@ 0
/dev/sda: isw,
Tried it, didn't work. Maybe Giuseppe's patch needs to be applied if
possible.
[EMAIL PROTECTED]:/# dmraid -ay
ERROR: isw: Could not find disk /dev/sdd in the metadata
ERROR: isw: Could not find disk /dev/sdc in the metadata
ERROR: isw: Could not find disk /dev/sdb in the metadata
ERROR: isw: Cou
** Attachment added: "hdparam.txt stdout redirected"
http://launchpadlibrarian.net/20235347/hdparam.txt
--
dmraid rc15 isw raid 10 "could not find disk in metadata"
https://bugs.launchpad.net/bugs/305011
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Giuseppe fixed rc14 for my raid10.
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/292302
Fix #292302 and #267953
http://launchpadlibrarian.net/20226091/dmraid_1.0.0.rc14-2ubuntu12.2.debdiff
--
dmraid rc15 isw raid 10 "could not find disk in metadata"
https://bugs.launchpad.net/bugs/305011
It works fine, I did an apt-get install. I also updated libdmraid
There were no initramfs triggers, so I generated it myself. It boots
and I can use the disk.
[EMAIL PROTECTED]:/home/x$ dpkg -l | grep dmraid
ii dmraid1.0.0.rc14-2ubuntu12.2
-rD did not produce any files. The tar is the result of the dd.
[EMAIL PROTECTED]:/home/x$ sudo hdparm -i /dev/sd[abcd]
/dev/sda:
Model=ST3500630AS , FwRev=3.AAC ,
SerialNo=9QG0WPGY
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
** Attachment added: "sd_isw.tar"
http://launchpadlibrarian.net/20195689/sd_isw.tar
--
dmraid rc15 isw raid 10 "could not find disk in metadata"
https://bugs.launchpad.net/bugs/305011
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Public bug reported:
Binary package hint: dmraid
I have raid 10 (or Intel says I have raid 10). Removing debian patch
07_isw-raid10-nested.dpatch from dmraid rc14 made my raid setup unusable
(dmraid could not find metadata on startup). I have intrepid, I created
a jaunty partition and debootst
at 3:50 PM, Phillip Susi <[EMAIL PROTECTED]> wrote:
> indy2718 wrote:
>> I tried rc15 before and it didn't work, and I just tried jaunty dmraid
>> rc15. 'Could not find metadata' when I boot and try dmraid -ay at initram.
>>
>> https://bugs.launchpa
Phillip Susi wrote:
> Unfortunately fixing the raid10 patch is a lot more complicated than I
> thought so I have given up. The isw raid10 support apparently was
> implemented differently in rc15 and works properly so I suggest just
> backporting that.
>
>
Hello, thank you for the attempt.
I
# sudo fdisk -lu /dev/sda
Warning: invalid flag 0x of partition table 5 will be corrected by w(rite)
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x7e7498c6
Device B
metadata attached
** Attachment added: "iswdat.tar"
http://launchpadlibrarian.net/19435220/iswdat.tar
--
Raidset stays inactive due to wrong # of devices
https://bugs.launchpad.net/bugs/292302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Adding dmraid -rD outputs
** Attachment added: "isw.tar"
http://launchpadlibrarian.net/19393215/isw.tar
--
Raidset stays inactive due to wrong # of devices
https://bugs.launchpad.net/bugs/292302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I installed the package but didn't reboot.
[EMAIL PROTECTED]:/home/x# dmraid -rD
/dev/sdd: isw, "isw_jceibccac", GROUP, ok, 976773165 sectors, data@ 0
/dev/sdc: isw, "isw_jceibccac", GROUP, ok, 976773165 sectors, data@ 0
/dev/sdb: isw, "isw_jceibccac", GROUP, ok, 976773165 sectors, data@ 0
/dev/sd
Hello, I was the user that the raid 10 patch was re-added for. I tried
this new dmraid using apt-get on your repository and it doesn't work for
me. I am running a custom kernel, 2.6.27 with the latest ubuntu
intrepid. Core 2.
The screenshot is during bootup, it bails to the initram prompt.
My ra
ubuntu9 works for me now, thank you.
On Wed, Oct 8, 2008 at 1:07 AM, Chris <[EMAIL PROTECTED]> wrote:
> Hi,
> I believe I had checked that. The default build turns out to be
> non-local. When linux failed to boot, it dropped to the initram
> prompt, where I did a dmraid --version (or similar) an
Hi,
I believe I had checked that. The default build turns out to be
non-local. When linux failed to boot, it dropped to the initram
prompt, where I did a dmraid --version (or similar) and it gave rc15.
It was a static build I believe.
When it failed I was able to boot one of my older kernels tha
Thank you for the response.
I did generate a new initramfs, this packs the modules and necessary
dmraid into the initram file for when the kernel loads. Unfortunately
this rc15 dmraid did not work. (Could not find metadata). I did not
apply any dmraid "debian" patches to it, I thought that was th
Public bug reported:
My intel raid 10 (0+1) used to use fine, but the recent dmraid package
removed dmraid 10 support because of debian bug #494278. I was told to
wait for rc15. I downloaded rc15 myself, and it cannot find meta data.
(Maybe it needs a patch?) Please support my system, otherwise
I reopened it because of Rune.
** Changed in: vnc4 (Ubuntu)
Status: Invalid => New
--
Xorg module VNC cores on keyboard input
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
It seems that I did not enable the ubuntu remote desktop. When I did, I
attached to :1 display and it worked. Configuration error on my part.
It should not core the X server though if you do the process I
described.
** Changed in: vnc4 (Ubuntu)
Status: New => Invalid
--
Xorg module VNC
** Summary changed:
- Xorg module VNC aborts on keyboard input
+ Xorg module VNC cores on keyboard input
--
Xorg module VNC cores on keyboard input
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
** Summary changed:
- Xorg extension VNC aborts on keyboard input
+ Xorg module VNC aborts on keyboard input
--
Xorg module VNC aborts on keyboard input
https://bugs.launchpad.net/bugs/180619
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
Binary package hint: vnc4server
I have the latest hardy as of 1/05/2008
ii vnc4server 4.1.1+xorg1.0.2-0ubuntu6
Virtual network computing server software
ii xorg 1:7.3+9ubuntu2
25 matches
Mail list logo
