各位大神好，
我用的F2-NAS2，双西数4T红盘做的raid0，使用3年多了。前几天频发发现下载器不在线，开始调试。发现在LAN里没有设备ip，虽然灯都正常。于是关机重启，还是不行。之后试过如下方法：
------------------------------------------------------------------------------------------------
用附件 putty软件连接NAS的后台，
不插硬盘开机NAS，搜索到NAS的IP后，
打开PUTTY软件，输入NAS的IP
选择“telnet”方式登录
进后台的用户是root   密码 admin（密码它不显示的，直接回车就行）
然后插硬盘进去，（不关NAS，直接插硬盘）
等 硬盘灯蓝色了，输入这个命令并回车，
/usr/init.d/userspace
------------------------------------------------------------------------------------------------


还是不行，联系客服，给了如下方法：
------------------------------------------------------------------------------------------------
用附件 putty软件连接NAS的后台，
1.先关机NAS,把NAS中的硬盘全拔下来，
2.不插硬盘开机NAS，搜索到NAS的IP后，
  进到NAS的初始化页面，
3.打开PUTTY软件，输入NAS的IP
  选择“telnet”方式登录
4.进后台的用户是root   密码 admin（密码它不显示的，直接回车就行）
  把硬盘全部插进NAS中（不关NAS，直接插硬盘）

等 硬盘灯蓝色了，执行以下五个命令（备注：一行一回车）
mdadm -A /dev/md0 /dev/sd[a-z]2 --force
mdadm -A /dev/md9 /dev/sd[a-z]1 --force
mke2fs -t ext4 /dev/md9
/usr/init.d/userspace
/usr/init.d/dataspace

------------------------------------------------------------------------------------------------
在进行过程中，
(nas)#mdadm -A /dev/md0 /dev/sd[a-z]2 --force
mdadm: /dev/md0 assembled from 1 drive - not enough to start the array.
(nas)#cat /proc/mdstat
Personalities:  ..........
md0 : inactive sda2[0](S)
          3906016256 blocks super 1.2
unused devices: <none>
(nas)#ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2

感觉HDD1挂了。即：不插盘，启动nas，可以有ip。插入盘后，有时只找到HDD2；有时2块盘都有，但操作命令后重启都是再看不到ip。
首先不知道到底怎么办了？
其次，做最坏打算，我还有什么方法自行找回做了raid0的两块盘中的数据吗？
灭顶之灾啊！！！求助各位大神的帮忙！

兄弟，找回数据了吗，和你遇到差不多的问题了

这是在后台挂载硬盘的，RAID0阵列，出现一块硬盘有问题，阵列就会有问题，请联系客服把硬盘寄到我们公司，我们试试恢复。

我今天做了这样的实验：
1.拔掉所有盘开机；
2.插入HDD1到盘位1，网页访问nas的ip地址，显示硬盘1自检，最后显示硬盘1正常；
3.插入HDD2到盘位2，刷新页面，显示HDD1正常，HDD2自检，最后也终于正常；
4.持续到最后一步做RAID，可以选2块盘，我点取消退出网页。
5.ssh，按你给的所有命令，操作依然是如下：
(nas)#mdadm -A /dev/md0 /dev/sd[a-z]2 --force
mdadm: /dev/md0 has been started with 2 drives.
(nas)#mdadm -A /dev/md9 /dev/sd[a-z]1 --force
mdadm: no recogniseable superblock on /dev/sda1
mdadm: /dev/sda1 has no superblock - assembly aborted
(nas)#mke2fs -t ext4 /dev/md9
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/md9 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
(nas)#/usr/init.d/userspace
mdadm: stopped /dev/md0
mdadm: No md superblock detected on /dev/sda1.
mdadm: No md superblock detected on /dev/sdb1.
mdadm: cannot open device /dev/block: Invalid argument
mdadm: /dev/block has no superblock - assembly aborted
/dev/block /dev/bsg /dev/btns /dev/bus /dev/cesa /dev/char /dev/console /dev/cpu_dma_latency /dev/crypto /dev/device-mapper /dev/fd /dev/full /dev/i2c-0 /dev/kmem /dev/kmsg /dev/log /dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/loop7 /dev/mapper /dev/mem /dev/mtd0 /dev/mtd0ro /dev/mtd1 /dev/mtd1ro /dev/mtd2 /dev/mtd2ro /dev/mtd3 /dev/mtd3ro /dev/mtd4 /dev/mtd4ro /dev/mtd5 /dev/mtd5ro /dev/mtdblock0 /dev/mtdblock1 /dev/mtdblock2 /dev/mtdblock3 /dev/mtdblock4 /dev/mtdblock5 /dev/mv_rtc /dev/network_latency /dev/network_throughput /dev/null /dev/port /dev/ptmx /dev/pts /dev/ptyp0 /dev/ptyp1 /dev/ptyp2 /dev/ptyp3 /dev/ptyp4 /dev/ptyp5 /dev/ptyp6 /dev/ptyp7 /dev/ptyp8 /dev/ptyp9 /dev/ptypa /dev/ptypb /dev/ptypc /dev/ptypd /dev/ptype /dev/ptypf /dev/ram0 /dev/ram1 /dev/ram10 /dev/ram11 /dev/ram12 /dev/ram13 /dev/ram14 /dev/ram15 /dev/ram2 /dev/ram3 /dev/ram4 /dev/ram5 /dev/ram6 /dev/ram7 /dev/ram8 /dev/ram9 /dev/random /dev/root /dev/rtc0 /dev/scst_user /dev/sda /dev/sda1 /dev/sda2 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sg0 /dev/sg1 /dev/shm /dev/stderr /dev/stdin /dev/stdout /dev/tgt /dev/tty /dev/tty0 /dev/tty1 /dev/tty10 /dev/tty11 /dev/tty12 /dev/tty13 /dev/tty14 /dev/tty15 /dev/tty16 /dev/tty17 /dev/tty18 /dev/tty19 /dev/tty2 /dev/tty20 /dev/tty21 /dev/tty22 /dev/tty23 /dev/tty24 /dev/tty25 /dev/tty26 /dev/tty27 /dev/tty28 /dev/tty29 /dev/tty3 /dev/tty30 /dev/tty31 /dev/tty32 /dev/tty33 /dev/tty34 /dev/tty35 /dev/tty36 /dev/tty37 /dev/tty38 /dev/tty39 /dev/tty4 /dev/tty40 /dev/tty41 /dev/tty42 /dev/tty43 /dev/tty44 /dev/tty45 /dev/tty46 /dev/tty47 /dev/tty48 /dev/tty49 /dev/tty5 /dev/tty50 /dev/tty51 /dev/tty52 /dev/tty53 /dev/tty54 /dev/tty55 /dev/tty56 /dev/tty57 /dev/tty58 /dev/tty59 /dev/tty6 /dev/tty60 /dev/tty61 /dev/tty62 /dev/tty63 /dev/tty7 /dev/tty8 /dev/tty9 /dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3 /dev/ttyp0 /dev/ttyp1 /dev/ttyp2 /dev/ttyp3 /dev/ttyp4 /dev/ttyp5 /dev/ttyp6 /dev/ttyp7 /dev/ttyp8 /dev/ttyp9 /dev/ttypa /dev/ttypb /dev/ttypc /dev/ttypd /dev/ttype /dev/ttypf /dev/urandom /dev/usbdev1.1 /dev/vcs /dev/vcs1 /dev/vcsa /dev/vcsa1 /dev/watchdog /dev/zero
(nas)#
(nas)#
(nas)#/usr/init.d/dataspace
mdadm: /dev/md0 has been started with 2 drives.
*****************************************************************************************************************
check filesystem on /dev/md0
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
quotacheck: Your kernel probably supports journaled quota but you are not using it. Consider switching to journaled quota to avoid running quotacheck after an unclean shutdown.
quotacheck: Scanning /dev/md0 [/mnt/md0] Connection closed by foreign host.

然后发现又是网络断开，硬盘灯还是2个都是蓝的。但路由上看不到NAS的IP了。由此是否可以判断是F2-NAS2本身坏了，而不是硬盘坏了？2块盘没有拔，直接关机，重启，路由器依然找不到其ip，感觉就是，只要2块盘一起插着，就无法启动网络。

下面是我执行客服给的方法的记录，最后直到死机（ip地址从路由器消失），只能强制关机
Processing /etc/profile... (nas)#hostname
Tnas-771661
(nas)#ls
bin  etc   lib      mnt  proc  sbin  tmp  var
dev  home  linuxrc  opt  run   sys   usr
(nas)#mdadm -A /dev/md0 /dev/sd[a-z]2 --force
mdadm: /dev/md0 has been started with 2 drives.
(nas)#mdadm -A /dev/md9 /dev/sd[a-z]1 --force
mdadm: no recogniseable superblock on /dev/sda1
mdadm: /dev/sda1 has no superblock - assembly aborted
(nas)#mdadm -A /dev/md9 /dev/sd[a-z]1 --force
mdadm: no recogniseable superblock on /dev/sda1
mdadm: /dev/sda1 has no superblock - assembly aborted
(nas)#mke2fs -t ext4 /dev/md9
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/md9 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
(nas)#
(nas)#
(nas)#/usr/init.d/userspace
mdadm: stopped /dev/md0
mdadm: No md superblock detected on /dev/sda1.
mdadm: /dev/md9 assembled from 0 drives and  1 rebuilding - not enough to start the array.
/dev/sdb1
prepare mount path:/mnt/base
check filesystem on /dev/md9
e2fsck: Invalid argument while trying to open /dev/md9
/dev/md9:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

mounting /dev/md9 on /mnt/base
mount: /dev/md9: can't read superblock
(nas)#/usr/init.d/dataspace
mdadm: /dev/md0 has been started with 2 drives.
*****************************************************************************************************************
check filesystem on /dev/md0
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
quotacheck: Your kernel probably supports journaled quota but you are not using it. Consider switching to journaled quota to avoid running quotacheck after an unclean shutdown.
quotacheck: Scanning /dev/md0 [/mnt/md0] Connection closed by foreign host.

请各位大神帮助！