I have the same behaviour reported by TJ with my Via VT8237 chipset:
- dmraid_0.9.9+1.0.0.rc9-2ubuntu1_i386.deb WORKS
- dmraid_0.9.9+1.0.0.rc13-0ubuntu2_i386.deb DO NOT WORK
Dmraid from Feisty is working ok.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
Sorry, in my previous post i meant:
dmraid_0.9.9+1.0.0.rc13-0ubuntu1_i386.deb WORKS and
dmraid_0.9.9+1.0.0.rc13-0ubuntu2_i386.deb DOES NOT WORK
sorry for the confusion!
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
'dmraid_0.9.9+1.0.0.rc9-2ubuntu1_i386.deb'
package works for a Promise FastTrak TX2000 RAID 1+0 (Mirror + Stripe)
but
'dmraid_0.9.9+1.0.0.rc13-0ubuntu2_i386.deb'
fails to activate the set when doing dmraid -ay.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
TJ, what about the version from feisty?
https://launchpad.net/ubuntu/+source/dmraid/1.0.0.rc13-2ubuntu1
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm that the version in feisty works for me! I've tested it
with a vanilla kernel and the 2.6.20 in the feisty repository. The boot
though does still not work without adding break=mount on the grub
commandline. The symptom is that the boot process simply hangs while
polling the
dmraid lists the stripe factor in sectors, not kb, so those values are
correct. 256 sectors is 128 KB.
The stripe factor is the number of sectors written to each disk before
moving to the next disk in the stripe.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
I managed to activate apt-get with DVD repository, but am stuck with
Feisty glibc conflict at the moment. See the end of my post for some
ways to finish the installation. Any suggestions?
Steps: install dmraid udebs as above, dmraid -ay, partition with manager
Execute shell
{{{
# parted
Ok, I have tried harder:
I have found out how the /dev/mapper directory can be created.
I cannot create an ext3 partition with the partition manager.
I am verbose as always, hopefully this is ok.
# modprobe dm-mod
# ls /dev/mapper
control
# dmraid -ay
# ls /dev/mapper
control
What do you mean the stride is wrong? Is the set not using a 128 kb
stride?
Parted and the text installer do not support dmraid devices properly
yet. To install you will have to follow the howto at
https://wiki.ubuntu.com/FakeRaidHowto
--
DMRAID stopped to work in kernels 2.6.15
dmraid -s shows stride: 256
In the BIOS (Intel Matrix Storage Manager Option ROM Utility) a Strip
Size of 128 KB is default for RAID 0. In the manual, stripe size is
mentioned as well.
I am confused about the definitions. Is a stride the sum of all the
strips shared across the harddisk (2 HDD:
Asus P5B Deluxe: /dev/mapper not available, dmraid -ay does _not_ help
Hardware:
Asus P5B Deluxe BIOS 0804
[with
Intel P965+ICH8R
JMicron JMB363
Marvell 88E8056 PCIe Gigabit Ethernet
Marvell 88E8001 PCI Gigabit Ethernet
SoundMAX ADI1988
]
Intel Core2Duo E6700 (standard FSB 266 MHz)
Richard Bailey pronuncio' le seguenti parole il 16/12/2006 20:38:
Progress! dmraid in the Feisty archives is finally rc13. I've already
tested dmraid in feisty from the archives, can a couple of you test it
and post your (hopeful) success here?
Once we get two more successes the request to
Progress! dmraid in the Feisty archives is finally rc13. I've already
tested dmraid in feisty from the archives, can a couple of you test it
and post your (hopeful) success here?
Once we get two more successes the request to backport this working
dmraid to edgy will go through.
--
DMRAID
The new package in Feisty does not work for me. I boot from a NVIDIA two
disk stripe set. To get my system to boot I have to append break=mount
on the grub commandline and then do something like:
modprobe sata_nv
modprobe dm-mod
dmraid -ay
exit busybox and then it boots correctly.
It seems that
After a bit more investigation it turned out to be more related to the
order things were started on my system. Renaming the dmraid script to
zdmraid (so it's last in the sort order) seems to have helped on my
system.
If I did break=mount I could manually run dmraid -ay, and everything
would be
@Christian D. the new package in Feisty is the same broken package
that's in Edgy. I'm *trying* to get someone to get an updated version
into Feisty.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: dmraid (Ubuntu)
Importance: Undecided = Medium
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have tried both rc13-0ubuntu1 and rc13-0ubuntu2 and neither seems to
be populating /dev/mapper for me on my SI 3112 fakeraid adapter. If I
boot with break=mount (or wait until I'm dumped into a busybox shell), I
can see that dmraid is picking up my raid set with dmraid -tay, but
dmraid -ay does
Scratch that. rc13-0ubuntu1 DOES populate /dev/mapper, but does not activate
dmraid. Need to look into this more.. If I boot with break=mount, and manually
activate the raid set I can continue the boot.
Apologies for the noise.
--
DMRAID stopped to work in kernels 2.6.15
I found out what *my* problem was. I am trying to boot from this raidset, and
the script that runs dmraid -ay to activate the raidset was in
/usr/share/initramfs-tools/scripts/local-top/dmraid.
I needed to copy this into local-premount and regenerate my initrd. After that
my machine would boot
Disregard my modified packages. It seems that it is not as simple as I
thought to move the devices out of /dev/mapper. I spent a few hours
trying to debug it last night and I concluded that it will take a lot
more work to make this happen, so I won't bother.
Based on my IRC discussions with
I'have the same problem with a Nvidia sata raid controller (I installed
dmraid_0.9.9+1.0.0.rc13-0ubuntu2_i386.deb)...
Bye
Enrico
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've tried Richard Bailey's package and my RAID partitions show up under
/dev/mapper, but the install fails while trying to format the swap
partition.
The latest package from Phillip Susi loads but no RAID partitions show
up in /dev when I attempt an install from the Live CD (running install
To install edgy on dmraid is tricky at best. I put together a HOWTO
that's worked for me and a couple others here:
http://ubuntuforums.org/showpost.php?p=1708724postcount=11
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
Phillip, It doesn't seem to create the /dev nodes for me. I am running
on AMD64 and maybe that is why. I booted up with the AMD64 desktop
installer.
I downloaded the rc13-0ubuntu1 source from above and your diffs (the 3rd
one). Compile it with sudo pbuilder build
And the binary build...
** Attachment added: dmraid_0.9.9+1.0.0.rc13-0ubuntu2_i386.deb
http://librarian.launchpad.net/5009205/dmraid_0.9.9%2B1.0.0.rc13-0ubuntu2_i386.deb
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
I believe I patched dmraid to not create the dev nodes in /dev/mapper,
but just in /dev instead. This should fix the problem with the lvm boot
script. I also have been working with a user trying to install edgy
using this package and it sounds like the installer thinks they are lvm
volumes and
Ok, that one didn't work... found and fixed the bug I think, give this
one a try.
** Attachment added: dmraid_0.9.9+1.0.0.rc13-0ubuntu2.source.tgz
http://librarian.launchpad.net/5010538/dmraid_0.9.9%2B1.0.0.rc13-0ubuntu2.source.tgz
--
DMRAID stopped to work in kernels 2.6.15
And the binary build...
** Attachment added: dmraid_0.9.9+1.0.0.rc13-0ubuntu2_i386.deb
http://librarian.launchpad.net/5010539/dmraid_0.9.9%2B1.0.0.rc13-0ubuntu2_i386.deb
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
Third time's the charm right? Made a typeo and found a second instance
of the same bug.
** Attachment added: dmraid_0.9.9+1.0.0.rc13-0ubuntu2.source.tgz
http://librarian.launchpad.net/5011197/dmraid_0.9.9%2B1.0.0.rc13-0ubuntu2.source.tgz
--
DMRAID stopped to work in kernels 2.6.15
And the binary...
** Attachment added: dmraid_0.9.9+1.0.0.rc13-0ubuntu2_i386.deb
http://librarian.launchpad.net/5011216/dmraid_0.9.9%2B1.0.0.rc13-0ubuntu2_i386.deb
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
I finally succeeded in booting my edgy on dmraid.
(My problem was due to the missing lvm package on this install...)
So I confirm that this rc13 package is enough to solve the bug.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
I also got this LVM bug anybody have open a new bug report on LVM?
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The 3 min delay at boot is due to a change that was made to the lvm
package since dapper. It's script in the initramfs now checks to see if
the boot path starts with /dev/mapper and if so, assumes it is an LVM
volume and attempts to dissect the remaining part of the path into
volume group and
Good find, this sounds like a bug that should be filed against LVM.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
So I'm the last one for who it doesn't work ?
Can we list on wich fakeraid chipset it works ?
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I compiled this package from the source package and it worked for me on
Nvidia nforce4 chipset
This is my first package (I just unpacked the source and used sudo pbuilder
build dmraid_0.9.9+1.0.0.rc13-0ubuntu1.dsc) so its probboly not perfect but it
works
If someone can direct me to the
I had the same issue - no raid after upgrading to edgy. Note I don't
boot from the RAID drive - rather it is a seperate striped fakeraid
(nforce4) RAID disk set.
Installing Richard's package binary package listed above fixes it for me
- many thanks!
--
DMRAID stopped to work in kernels 2.6.15
After install the new version of dmraid (rc13), I can boot with the new
kernel (2.6.17), but now I have a new problem:
In the boot process, the system hangs during 2-3 minutes and then
continues booting normally. Anybody with the same problem? I need Help!
--
DMRAID stopped to work in kernels
I have this problem as well, after a while the messages: Buffer I/O
error on device sda3, logical block ... start to scroll down the
screen, and then it continues booting normally.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
If you want to get more information during boot, to troubleshoot why it
hangs for a few minutes or any other issue, when grub comes up edit the
grub command and remove the quiet and splash options from the end.
In fact, remove the splash option first and see if you can see your
error message,
My problem is the same as described by WattoDaToydarian, but if I wait
in the blank screen for 2-3 minutes, the system continues the boot
process normally.
I have booted the system without quiet splash, and the problem appears
after the message:
[17179575.812000] device-mapper: 4.6.0-ioctl
I can't get dmraid_0.9.9-1.0.0.rc13-0ubuntu1_i386.deb to function correctly. In
dev/mapper I am only getting the Volumes and not the RAID device. It looks like
this:
isw_cigbaiabcj_RAID_Volume0 I am guessing this is /boot
isw_cigbaiabcj_RAID_Volume01 NTFS partition 1 (WindowsXP)
Just to note, after assisting WattoDaToydarian and Eleazar they now have
their raid working in Edgy.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Mr Bailey,
your package dmraid_0.9.9-1.0.0.rc13-0ubuntu1_i386.deb works beautifully on my
vt8237 via sata fakeraid controller.
I'm writing this post from my freshly installed kubuntu edgy!
I hope it'll be included in the official repository ASAP. (also, it'd be great
if it were included in
Hi, Edgy official release is imminent, will the updated dmraid
1.0.0_rc13 find its way into the repos? Maybe, if it's too late for
official approval, you should add a comment in the release note (or
somewhere users can easily find) to warn the users against the
uncompatible rc9 and point them to
1.0.0.rc13 still doesn't work for me. By the way, I've a Silicon Image 3112
controller with 2 disks.
Even with single option, so without usplash, I can't get enough traces
about my root that is not mounted. I only have a waiting for filesystem or
something like that.
Is there is any option I can
Is there is any option I can try to have more traces about my missing
filesystem ?
For instance, you can boot with break=mount which gives you a shell
inside the initramfs before it tries to mount the root partition, or
break=bottom which is after. See /usr/share/initramfs-tools/init for
To Jeremy and others trying the new rc13 package, when you install it it
will update the initrd for the currently running kernel. If you need to
update an initrd for a kernel that's not currently running, but that you
intent to boot to issue a command like this:
update-initramfs -k kernel version
I've tried the break=mount option. I got a busybox shell, but no
keyboard to type in... so I can't get more information this way...
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This updated source package fixes the issue.
Note: package is based on a new upstream version, 1.0.0.rc13
** Attachment added: Updated source package based on 1.0.0.rc13
http://librarian.launchpad.net/493/dmraid_0.9.9%2B1.0.0.rc13.source.tgz
--
DMRAID stopped to work in kernels 2.6.15
The updates source package looks sane, except for debian/changelog which
has more spacing than is standard.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Source package with proper spacing in debian/changelog
** Attachment added: Source pkg based on rc13 with proper spacing in
debian/changelog
http://librarian.launchpad.net/4934470/dmraid_0.9.9%2B1.0.0.rc13.source.tgz
--
DMRAID stopped to work in kernels 2.6.15
Hey Mr. Bailey, I tried your new dmraid package and I still cant get my PC to
boot from the 2.6.17-10-generic kernel. It just displays the splash screen
(witch is different from the RC live cd) and the hdd light blinks a few times
then it goes to a black screen with a blinking cursor.
I think
I've packaged version 1.0.0.rc13, which I've attached. I'm working on
getting this into the repos, but you all can test it out.
DISCLAIMER - The Ubuntu team has not certified this package yet so you
will be doing this at your own risk.
However, it works for me.
** Attachment added: updated
** Changed in: dmraid (Ubuntu)
Assignee: (unassigned) = Richard Bailey
Status: Confirmed = In Progress
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm not sure as I really don't know a lot about upstart, but it doesn't seem
linked to.
I'll try to have a tty under busybox so I can check what's going wrong.
Does the package (rc13) solve the problem for people that don't boot on
dmraid ?
--
DMRAID stopped to work in kernels 2.6.15
A hint for those trying to package newer upstream versions:
Get the new upstream tar-ball, then try applying the most recent ubuntu-diff
that you can find here: http://packages.ubuntu.com/edgy/admin/dmraid
This way you don't have to reinvent the wheel :)
--
DMRAID stopped to work in kernels
apt-get source dmraid does the same and download the needed -dev package
for the build.
2006/10/20, Tormod Volden [EMAIL PROTECTED]:
A hint for those trying to package newer upstream versions:
Get the new upstream tar-ball, then try applying the most recent
ubuntu-diff that you can find
apt-get source dmraid will only download the old, original tar-ball
that was used for the old package. And to get all needed extra packages,
do sudo apt-get build-dep dmraid first. Once you have applied the
ubuntu diff on the upstream tar-ball, you can try building with debuild
-b -i -us -uc. See
I tried to package latest dmraid from RedHat (i.e 1.0.0.rc13) with additional
Ubuntu scripts for initramfs.
May someone try it ?
** Attachment added: dmraid_0.9.9+1.0.0.rc13-0_i386.deb
http://librarian.launchpad.net/4891009/dmraid_0.9.9%2B1.0.0.rc13-0_i386.deb
--
DMRAID stopped to work in
Could there be a problem with dmraid's init scripts and new the new init
system in edgy? (upstart)
Just speculating.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Even with the corrected scripts (that considers dmraid in /usr/sbin),
the /dev/mapper devices are not correctly set at startup.
As my / is on a such device, I can't have Edgy working correctly. I'll
get back to Dapper in a while if no correction is provided soon...
--
DMRAID stopped to work in
Can you post your new package? Even if it's not working? I'd like to try
it and take a look at it.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Well... I didn't package the modifications... I directly added the scripts and
modified them to use the right paths.
The worth is that I didn't noted the errors reported during boot... I'll try to
post more information lately.
--
DMRAID stopped to work in kernels 2.6.15
I'm trying to have it working right now...
It seems that the dmraid_1.0.0.rc11-1_i386.deb Olaf built have dmraid in
/usr/sbin and not in /sbin as it should be... that's (probably) why the
/usr/share/initramfs-tools/hooks/dmraid script does not work..
and that's why /dev/mapper devices are not
Ok. I guess we are at the same point we were last spring on this bug :
https://launchpad.net/distros/ubuntu/+source/initramfs-tools/+bug/22107
I'll try to add again /usr/share/initramfs-tools/scripts/local-
top/dmraid and test it again so we can improve the 1.0.0-rc11 package.
--
DMRAID stopped
Just booted without splash for another bug and saw this in the boot
screen:
device-mapper: dm-stripe: Target length not divisible by chunk size
This line came up after the following:
/dev/sda: via and nvidia formats discovered (using nvidia)!
/dev/sdb: via and nvidia formats discovered (using
Did you rebuild your initramfs after installing dmraid rc11?
:~$ sudo update-initramfs -k `uname -r` -u
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I didn't do that before now, if it needs to be done on install the
package should do it though.
I just did it and now I don't get the messages when I boot, but there
are still no entries in /dev/mapper when I boot and if I run sudo dmraid
-ay when I'm running the entries come up in /dev/mapper.
** Attachment added: /usr/share/initramfs-tools/hooks/dmraid
http://librarian.launchpad.net/4711487/dmraid
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: /usr/share/initramfs-tools/scripts/local-top/dmraid
http://librarian.launchpad.net/4711488/dmraid
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The dmraid package in edgy places update-initramfs hooks and rebuilds
the initrd correctly. You should see
/usr/share/initramfs-tools/hooks/dmraid
/usr/share/initramfs-tools/scripts/local-top/dmraid
in the output of locate dmraid
--
DMRAID stopped to work in kernels 2.6.15
The attached package works for me, but the dmraid is not set up on boot.
When I rebooted I had to run sudo dmraid -ay manually to get the proper
entries in /dev/mapper
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
Well... I'm not so sure it is ok.
It worked only once. I upgrade some packages, and it didn't worked anymore then.
Does it work correctly for someone ? I'll try some other tests. Maybe I've got
another problem on my installation.
--
DMRAID stopped to work in kernels 2.6.15
So we can confirm that the bug is fixed in rc11 of dmraid! It would be
really bad if dmraid rc11 would not bee included in edgy. Since this is
a bugfix for the otherwise not working dmraid in the current repo, I
guess there will be an exception made for that package to go into edgy!?
--
DMRAID
I also confirm that dmraid 1.0.0-rc11 makes it work !!
As it is a regression since Dapper, I hope we can expect to have it
uploaded for Edgy.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Since there's a repo freeze soon on edgy, will edgy not have fakeraid
support?
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I've built a .deb of dmraid 1.0.0rc11 that works for me on 2.6.17. Maybe
someone else could give this one a shot and see if it fixes the problem.
Please be gentle, this is my first time to build a .deb. :P Apologies if this
isn't properly packaged.
** Attachment added: dmraid version 1.0.0rc11
I build the latest dmraid (1.0.0-rc11), and tried it with my configuration
without any success.
(By the way, dmraid 1.0.0-rc11 does not build on gcc-4.1, but on gcc-4.0 it
does.)
** Changed in: Ubuntu
Sourcepackagename: None = dmraid
--
DMRAID stopped to work in kernels 2.6.15
I've removed the sanity check in drivers/kernel/dm/dm-stripe.c and built
my own kernel. I've not tested it recently with a new dmraid version,
but if you do it, don't forget to rebuild your initramfs!
I would appreciate to get this fixed soon, since many of my friends have
such a setup und
Does it work with this sanity check removed ?
I'll try it asap on my machine. Is this check easy to find ? or maybe you can
post a patch file on this bug so I will not have to look for this check.
--
DMRAID stopped to work in kernels 2.6.15
https://launchpad.net/bugs/54246
--
ubuntu-bugs
I've just ifdef'd out the sanity check. It does work this way but
remember, this check is a feature, not a bug ;-) It detects broken raid
bioses which assign an erroneous number of blocks (not divisible). So,
if you fill up a filesystem up to a non existing block, you will get an
I/O error and
Same problem here (dual Opteron 246 on Asus K8N-DL with 2 120gig SATA in
RAID0 configuration). It looks like this breaks any raid configuration
depending on dmraid - not only to boot from RAID, but also to simply
mount and access existing arrays. I'd think the latest version of dmraid
should
84 matches
Mail list logo
