［救急］Arch下如何使用Raid 0？

echofrompat

两个硬件raid都被认成SCSI硬盘了，但kernel认不出分区。我没有用过nv的硬件raid，不清楚怎么做了。你可以试试到archlinux的maillist去发个问，把情况说明一下，看有没有人能帮你。

blance

大哥，我不清楚maillist是什么啊。。。如果是国外的网站我的英语也不怎么样，麻烦帮我问问？顺便给我一个链接，我想我应该还能看懂别人的回答

echofrompat

我试试吧~ 呵呵
你可以到http://www.archlinux.org/mailman/listinfo/arch 申请加入maillist

fallen

有人发过了，失败，失败
If I remember well, this chipset is often used for "fake" RAID. That is you
still need a specific driver on top of your hardware if you want RAID (that's
what is done under Windows).

I suggest you use Linux's Software RAID; and if you need your RAID array both
under Windows *and* Linux, you should consider buying a real controller.

echofrompat

Post by fallen
有人发过了，失败，失败
If I remember well, this chipset is often used for "fake" RAID. That is you
still need a specific driver on top of your hardware if you want RAID (that's
what is done under Windows).

I suggest you use Linux's Software RAID; and if you need your RAID array both
under Windows *and* Linux, you should consider buying a real controller.

那就是我在Maillist上帮问的.

详细的回复:

               
Tobias Powalowski        
<t.powa@gmx.de> to General
         More options          7:09 pm (3 hours ago)
Are you using initrd or initcpio image?
greetings
tpowa
--
Tobias Powalowski
Archlinux Developer & Package Maintainer (tpowa)
http://www.archlinux.org
tpowa@archlinux.org


               
Benoit Myard        
<mb@taudis.fr> to arch
         More options          7:28 pm (3 hours ago)
On Sat, Aug 26, 2006 at 04:00:30AM -0700, Lin, Zihui wrote:
> I've got a NForce4 mainborad with RAID support, and two RAID 0 arrays
> configured on it. Windows can read the partitions on the arrays well,
> but my Arch failed to do so.

If I remember well, this chipset is often used for "fake" RAID. That is you
still need a specific driver on top of your hardware if you want RAID (that's
what is done under Windows).

I suggest you use Linux's Software RAID; and if you need your RAID array both
under Windows *and* Linux, you should consider buying a real controller.

You may also try to use a device mapper such as `dmraid' [1].

There are information on these subjects on the Web, but I can't help more
without your motherboard maker/model.

Good luck.

[1] I have no clue if this will work. Use it at your *own* risks.



Varun Acharya        
<ganja.guru.x64@gmail.com> to General
         More options          8:46 pm (1½ hours ago)
Benoit Myard wrote:
> On Sat, Aug 26, 2006 at 04:00:30AM -0700, Lin, Zihui wrote:
>
>> I've got a NForce4 mainborad with RAID support, and two RAID 0 arrays
>> configured on it. Windows can read the partitions on the arrays well,
>> but my Arch failed to do so.
>>

The nforce4 RAID is purely a software raid and getting both windows and
linux to play nicely with the partitions is a difficult task(if not
impossible). You need to get a real Hardware RAID controller like the
3ware 8506-4LP (for SATA drives). Works flawlessly and recognizes
partitions in both linux and windows. The drivers for the 3ware are
built into the kernel by the way. Hardware RAID also puts less stress on
your CPU

ganja_guru



看完回复，我想这个芯片其实还在Windows下做的软件RAID。
我的想法是，除非你能找到Nvidia对此RAID芯片的官方驱动（或是某个牛人做的驱动），Linux是不能读写你的RAID分区了。

blance

...
看来是无望了

blance

Question
  Does NVIDIA provide NVRAID support for Linux?


  Answer
  NVIDIA does not ship a retail Linux RAID driver. We support an open source RAID effort called, "dmraid". dmraid allows Linux to support multi-vendor BIOS RAID solutions. This means that you can create a RAID set using the NVRAID BIOS and then use it within Linux via the dmraid software. dmraid is currently not shipping in any distributions other than Fedora. For more information on dmraid see http://people.redhat.com/~heinzm/sw/dmraid/

我在nvidia官网找到的，地址是：

http://nvidia.custhelp.com/cgi-b ... li=&p_topview=1


麻烦哪位大大能解释一下？我的理解是好像要编译一个驱动吧，下载地址是：
http://people.redhat.com/~heinzm/sw/dmraid/

我打开一看有好几个，不知道应该编译哪个好

fallen

不需要自己编译模块
需要得是你的sata的模块
dmraid只是一个工具帮你识别那些soft raid的分区
http://aur.archlinux.org/package ... mp;SO=&

blance

[php][root@ccnu-blance 1.0.0.rc12-pre1]# ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for gawk... gawk
checking for a BSD-compatible install... /bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking for unistd.h... (cached) yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for struct stat.st_rdev... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether to enable debugging...
no
checking whether to enable malloc debugging...
no
checking whether to disable native metadata logging...
yes
checking whether to disable testing with mapped devices...
no
checking whether gcc needs -traditional... no
checking return type of signal handlers... void
checking for vprintf... yes
checking for _doprnt... no
checking for mkdir... yes
checking for rmdir... yes
checking for uname... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
configure: creating ./config.status
config.status: creating include/Makefile
config.status: creating lib/Makefile
config.status: creating man/Makefile
config.status: creating tools/Makefile
config.status: creating tools/version.h
config.status: creating Makefile
config.status: creating make.tmpl
[root@ccnu-blance 1.0.0.rc12-pre1]# make
make -C include
make[1]: Entering directory `/home/blance/dmraid/1.0.0.rc12-pre1/include'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/blance/dmraid/1.0.0.rc12-pre1/include'
make -C lib
make[1]: Entering directory `/home/blance/dmraid/1.0.0.rc12-pre1/lib'
gcc -MM -MF activate/activate.d -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/activate.c; \
        gcc -c -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/activate.c -o activate/activate.o
gcc -MM -MF activate/devmapper.d -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/devmapper.c; \
        gcc -c -I. -I../include -I../lib -O2 -DDMRAID_NATIVE_LOG -DHAVE_GETOPTLONG -fPIC -Wall -Wundef -Wcast-align -Wwrite-strings -Winline -DDMRAID_TEST -O2 -D_LARGEFILE64_SOURCE activate/devmapper.c -o activate/devmapper.o
activate/devmapper.c:12:26: 错误：libdevmapper.h：没有那个文件或目录
activate/devmapper.c: 在函数 ‘mkdm_path’ 中：
activate/devmapper.c:29: 警告：隐式声明函数 ‘dm_dir’
activate/devmapper.c:29: 警告：初始化时将整数赋给指针，未作类型转换
activate/devmapper.c: 在函数 ‘_init_dm’ 中：
activate/devmapper.c:49: 警告：隐式声明函数 ‘dm_log_init’
activate/devmapper.c: 在顶层：
activate/devmapper.c:53: 警告：‘struct dm_task’ 在形参表内部声明
activate/devmapper.c:53: 警告：它的作用域仅限于此定义或声明，这可能并不是您想要 的
activate/devmapper.c: 在函数 ‘_exit_dm’ 中：
activate/devmapper.c:56: 警告：隐式声明函数 ‘dm_task_destroy’
activate/devmapper.c:58: 警告：隐式声明函数 ‘dm_lib_release’
activate/devmapper.c:59: 警告：隐式声明函数 ‘dm_lib_exit’
activate/devmapper.c: 在函数 ‘get_target_list’ 中：
activate/devmapper.c:71: 警告：隐式声明函数 ‘dm_task_create’
activate/devmapper.c:71: 错误：‘DM_DEVICE_LIST_VERSIONS’ 未声明 (在此函数内第一 次使用)
activate/devmapper.c:71: 错误：(即使在一个函数内多次出现，每个未声明的标识符在其
activate/devmapper.c:71: 错误：所在的函数内只报告一次。)
activate/devmapper.c:71: 警告：赋值时将整数赋给指针，未作类型转换
activate/devmapper.c:72: 警告：隐式声明函数 ‘dm_task_run’
activate/devmapper.c:72: 警告：隐式声明函数 ‘dm_task_get_versions’
activate/devmapper.c:72: 警告：条件表达式中指针/整数类型不匹配
activate/devmapper.c: 在函数 ‘valid_ttype’ 中：
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:92: 错误：提领指向不完全类型的指针
activate/devmapper.c:96: 错误：提领指向不完全类型的指针
activate/devmapper.c: 在顶层：
activate/devmapper.c:107: 警告：‘struct dm_task’ 在形参表内部声明
activate/devmapper.c: 在函数 ‘handle_table’ 中：
activate/devmapper.c:131: 警告：隐式声明函数 ‘dm_task_add_target’
activate/devmapper.c: 在顶层：
activate/devmapper.c:140: 警告：‘struct dm_task’ 在形参表内部声明
activate/devmapper.c: 在函数 ‘parse_table’ 中：
activate/devmapper.c:142: 警告：传递参数 2 (属于 ‘handle_table’)时在不兼容的指针类型间转换
activate/devmapper.c: 在函数 ‘dm_create’ 中：
activate/devmapper.c:160: 错误：‘DM_DEVICE_CREATE’ 未声明 (在此函数内第一次使用)
activate/devmapper.c:160: 警告：赋值时将整数赋给指针，未作类型转换
activate/devmapper.c:161: 警告：隐式声明函数 ‘dm_task_set_name’
activate/devmapper.c:162: 警告：传递参数 2 (属于 ‘parse_table’)时在不兼容的指针 类型间转换
activate/devmapper.c:172: 警告：传递参数 1 (属于 ‘_exit_dm’)时在不兼容的指针类型间转换
activate/devmapper.c: 在函数 ‘dm_remove’ 中：
activate/devmapper.c:186: 错误：‘DM_DEVICE_REMOVE’ 未声明 (在此函数内第一次使用)
activate/devmapper.c:186: 警告：赋值时将整数赋给指针，未作类型转换
activate/devmapper.c:190: 警告：传递参数 1 (属于 ‘_exit_dm’)时在不兼容的指针类型间转换
activate/devmapper.c: 在函数 ‘dm_status’ 中：
activate/devmapper.c:201: 错误：‘info’ 的存储大小未知
activate/devmapper.c:206: 错误：‘DM_DEVICE_STATUS’ 未声明 (在此函数内第一次使用)
activate/devmapper.c:206: 警告：赋值时将整数赋给指针，未作类型转换
activate/devmapper.c:209: 警告：隐式声明函数 ‘dm_task_get_info’
activate/devmapper.c:212: 警告：传递参数 1 (属于 ‘_exit_dm’)时在不兼容的指针类型间转换
activate/devmapper.c:201: 警告：未使用的变量 ‘info’
activate/devmapper.c: 在函数 ‘dm_version’ 中：
activate/devmapper.c:228: 错误：‘DM_DEVICE_VERSION’ 未声明 (在此函数内第一次使用)
activate/devmapper.c:228: 警告：赋值时将整数赋给指针，未作类型转换
activate/devmapper.c:230: 警告：隐式声明函数 ‘dm_task_get_driver_version’
activate/devmapper.c:232: 警告：传递参数 1 (属于 ‘_exit_dm’)时在不兼容的指针类型间转换
make[1]: *** [activate/devmapper.o] 错误 1
make[1]: Leaving directory `/home/blance/dmraid/1.0.0.rc12-pre1/lib'
make: *** [lib] 错误 2
[root@ccnu-blance 1.0.0.rc12-pre1]#  [/php]

安装不上去？

blance

再顶上去～～～～