Ajuda urgente com raid 1 no debian [RESOLVIDO]

amdbuzat
(usa Debian)

Enviado em 26/10/2014 - 20:19h

Pessoal, não sei o que acontece, más meu server não segura o raid. Vou postar o que fiz para montá-lo:

login as: root
root@storage's password:
Linux Storage 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 26 12:58:30 2014 from 192.168.1.3
root@Storage:~# mount /dev/md1
mount: não foi possível localizar /dev/md1 em /etc/fstab ou /etc/mtab
root@Storage:~# blkid /dev/md0
root@Storage:~# watch -n 1 cat /proc/mdstat
root@Storage:~# blkid /dev/md1
root@Storage:~# cat /proc/mdstat
Personalities :
unused devices: <none>
root@Storage:~# ^C
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: /dev/sdb1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:37:26 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:37:26 2014
Continue creating array? Yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: cannot open /dev/sdb1: Device or resource busy
root@Storage:~# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: cannot open /dev/sdb1: Device or resource busy
root@Storage:~# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[bc]2
mdadm: /dev/sdb2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:38:04 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:38:04 2014
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md1 started.
root@Storage:~# cat /proc/mdstat
Personalities : [raid1]
md1 : active (auto-read-only) raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

md0 : active (auto-read-only) raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

unused devices: <none>
root@Storage:~# blkid /dev/sd0
root@Storage:~# cat /proc/mdstat
Personalities : [raid1]
md1 : active (auto-read-only) raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

md0 : active (auto-read-only) raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

unused devices: <none>
root@Storage:~# ^C
root@Storage:~# mdadm --readwrite /dev/md0
root@Storage:~# mdadm --readwrite /dev/md1
root@Storage:~# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=DELAYED

md0 : active raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
[>....................] resync = 0.0% (530496/976625472) finish=183.9min speed=88416K/sec

unused devices: <none>
root@Storage:~# blkid /dev/md0
/dev/md0: LABEL="Virtuais" UUID="a5ff3b40-f2c0-4085-bb07-8004eab6d85b" TYPE="ext4"
root@Storage:~# blkid /dev/md1
/dev/md1: LABEL="Programas" UUID="d4772b58-c0d0-4f6a-905d-bece0a95926d" TYPE="ext4"
root@Storage:~# vi /etc/fstab
root@Storage:~# cd /dev

root@Storage:/dev# mkdir 777 md0
mkdir: é impossível criar o diretório "md0": Arquivo existe
root@Storage:/dev# chmod 777 md0
root@Storage:/dev# chmod 777 md1
root@Storage:/dev# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=DELAYED

md0 : active raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
[=>...................] resync = 5.1% (50519104/976625472) finish=118.8min speed=129864K/sec

unused devices: <none>
root@Storage:/dev# watch -n 1 cat /proc/mdstat
root@Storage:/dev# watch -n 1 cat /proc/mdstat
root@Storage:/dev# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]

unused devices: <none>
root@Storage:/dev# mount md0
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@Storage:/dev# mount /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@Storage:/dev# blkid /dev/md1
/dev/md1: LABEL="Programas" UUID="d4772b58-c0d0-4f6a-905d-bece0a95926d" TYPE="ext4"
root@Storage:/dev# blkid /dev/md0
/dev/md0: LABEL="Virtuais" UUID="a5ff3b40-f2c0-4085-bb07-8004eab6d85b" TYPE="ext4"
root@Storage:/dev# login as: root
Linux Storage 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 26 12:58:30 2014 from 192.168.1.3
root@Storage:~# mount /dev/md1
mount: não foi possível localizar /dev/md1 em /etc/fstab ou /etc/mtab
root@Storage:~# blkid /dev/md0
root@Storage:~# watch -n 1 cat /proc/mdstat
root@Storage:~# blkid /dev/md1
root@Storage:~# cat /proc/mdstat
Personalities :
unused devices: <none>
root@Storage:~# ^C
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: /dev/sdb1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:37:26 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:37:26 2014
Continue creating array? Yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: cannot open /dev/sdb1: Device or resource busy
root@Storage:~# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: cannot open /dev/sdb1: Device or resource busy
root@Storage:~# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[bc]2
mdadm: /dev/sdb2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:38:04 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sat Oct 25 22:38:04 2014
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md1 started.
Senha:
Personalities : [raid1]
md1 : active (auto-read-only) raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

md0 : active (auto-read-only) raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

unused devices: <none>
root@Storage:~# blkid /dev/sd0
root@Storage:~# cat /proc/mdstat
Personalities : [raid1]
md1 : active (auto-read-only) raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

md0 : active (auto-read-only) raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

unused devices: <none>
root@Storage:~# ^C
root@Storage:~# mdadm --readwrite /dev/md0
root@Storage:~# mdadm --readwrite /dev/md1
root@Storage:~# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=DELAYED

md0 : active raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
[>....................] resync = 0.0% (530496/976625472) finish=183.9min speed=88416K/sec

unused devices: <none>
root@Storage:~# blkid /dev/md0
/dev/md0: LABEL="Virtuais" UUID="a5ff3b40-f2c0-4085-bb07-8004eab6d85b" TYPE="ext4"
root@Storage:~# blkid /dev/md1
/dev/md1: LABEL="Programas" UUID="d4772b58-c0d0-4f6a-905d-bece0a95926d" TYPE="ext4"
root@Storage:~# vi /etc/fstab
root@Storage:~# cd /dev
root@Storage:/dev# ls
autofs loop2 sda tty14 tty40 ttyS0
block loop3 sda1 tty15 tty41 ttyS1
bsg loop4 sda2 tty16 tty42 ttyS2
btrfs-control loop5 sda5 tty17 tty43 ttyS3
bus loop6 sdb tty18 tty44 uinput
cdrom loop7 sdb1 tty19 tty45 urandom
cdrw loop-control sdb2 tty2 tty46 usb
char MAKEDEV sdc tty20 tty47 vcs
console mapper sdc1 tty21 tty48 vcs1
core mcelog sdc2 tty22 tty49 vcs2
cpu md sg0 tty23 tty5 vcs3
cpu_dma_latency md0 sg1 tty24 tty50 vcs4
disk md1 sg2 tty25 tty51 vcs5
dri mem sg3 tty26 tty52 vcs6
dvd net shm tty27 tty53 vcs7
dvdrw network_latency snapshot tty28 tty54 vcsa
fb0 network_throughput snd tty29 tty55 vcsa1
fd null sndstat tty3 tty56 vcsa2
fd0 oldmem sr0 tty30 tty57 vcsa3
full port stderr tty31 tty58 vcsa4
fuse ppp stdin tty32 tty59 vcsa5
hidraw0 psaux stdout tty33 tty6 vcsa6
hidraw1 ptmx tty tty34 tty60 vcsa7
hpet pts tty0 tty35 tty61 vga_arbiter
input random tty1 tty36 tty62 watchdog
kmsg rfkill tty10 tty37 tty63 xconsole
log root tty11 tty38 tty7 zero
loop0 rtc tty12 tty39 tty8
loop1 rtc0 tty13 tty4 tty9
root@Storage:/dev# mkdir 777 md0
mkdir: é impossível criar o diretório "md0": Arquivo existe
root@Storage:/dev# chmod 777 md0
root@Storage:/dev# chmod 777 md1
root@Storage:/dev# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=DELAYED

md0 : active raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
[=>...................] resync = 5.1% (50519104/976625472) finish=118.8min speed=129864K/sec

unused devices: <none>
root@Storage:/dev# watch -n 1 cat /proc/mdstat
root@Storage:/dev# watch -n 1 cat /proc/mdstat
root@Storage:/dev# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2]

md0 : active raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]

unused devices: <none>
root@Storage:/dev# mount md0
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@Storage:/dev# mount /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@Storage:~# blkid /dev/md0
/dev/md0: LABEL="Virtuais" UUID="a5ff3b40-f2c0-4085-bb07-8004eab6d85b" TYPE="ext4"
root@Storage:~# blkid /dev/md1
/dev/md1: LABEL="Programas" UUID="d4772b58-c0d0-4f6a-905d-bece0a95926d" TYPE="ext4"
root@Storage:~#

_____________________________________________________


login as: root
root@storage's password:
Linux Storage 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 26 13:25:18 2014 from 192.168.1.3
root@Storage:~# mount /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@Storage:~# vi /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=ed176a16-8069-4a3b-b80c-0a6e00ecdc35 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=9b14d7dc-221c-4393-b56f-f7d3793768f1 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sdd1 /media/usb0 auto rw,user,noauto 0 0
UUID=d4772b58-c0d0-4f6a-905d-bece0a95926d /mnt/Programas auto default,errors=remount-ro 0 1
UUID=a5ff3b40-f2c0-4085-bb07-8004eab6d85b /mnt/Virtuais auto default,errors=remount-ro 0 1
#/dev/mdo /mnt/Programas auto default,errors=remount-ro 0 1
@
"/etc/fstab" 18L, 1119C 1,1 Topo

O PROBLEMA QUE QUANDO REINICIO ACONTECE O SEGUINTE:

login as: root
root@storage's password:
Linux Storage 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 26 19:53:11 2014 from 192.168.1.3
root@Storage:~# watch -n 1 cat /proc/mdstat
Every 1,0s: cat /proc/mdstat Sun Oct 26 20:00:45 2014

Personalities :
unused devices: <none>

login as: root
root@storage's password:
Linux Storage 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 26 20:00:36 2014 from 192.168.1.3
root@Storage:~# blkid /dev/sd1
root@Storage:~# mount /dev/md0
mount: não foi possível localizar /dev/md0 em /etc/fstab ou /etc/mtab
root@Storage:~# watch -n 1 cat /proc/mdstat
root@Storage:~# cat /proc/mdstat
Personalities :
unused devices: <none>
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: /dev/sdb1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:27 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:27 2014
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]2
mdadm: /dev/sdb2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
Continue creating array? yes
mdadm: /dev/md0 is already in use.
root@Storage:~# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[bc]2
mdadm: /dev/sdb2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md1 started.
root@Storage:~# watch -n 1 cat /proc/mdstat

login as: root
root@storage's password:
Linux Storage 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 26 20:00:36 2014 from 192.168.1.3
root@Storage:~# blkid /dev/sd1
root@Storage:~# mount /dev/md0
mount: não foi possível localizar /dev/md0 em /etc/fstab ou /etc/mtab
root@Storage:~# watch -n 1 cat /proc/mdstat
root@Storage:~# cat /proc/mdstat
Personalities :
unused devices: <none>
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]1
mdadm: /dev/sdb1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:27 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc1 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:27 2014
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@Storage:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[bc]2
mdadm: /dev/sdb2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
Continue creating array? yes
mdadm: /dev/md0 is already in use.
root@Storage:~# mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sd[bc]2
mdadm: /dev/sdb2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdb2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: /dev/sdc2 appears to contain an ext2fs file system
size=976756736K mtime=Wed Dec 31 21:00:00 1969
mdadm: /dev/sdc2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Oct 26 13:29:54 2014
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md1 started.
root@Storage:~# watch -n 1 cat /proc/mdstat
root@Storage:~# watch -n 1 cat /proc/mdstat
Every 1,0s: cat /proc/mdstat Sun Oct 26 20:12:19 2014

Personalities : [raid1]
md1 : active (auto-read-only) raid1 sdc2[1] sdb2[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

md0 : active (auto-read-only) raid1 sdc1[1] sdb1[0]
976625472 blocks super 1.2 [2/2] [UU]
resync=PENDING

unused devices: <none>

root@Storage:~#

____________________________________


root@Storage:~# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = setores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00021d3a

Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 2048 968388607 484193280 83 Linux
/dev/sda2 968390654 976771071 4190209 5 Estendida
Partition 2 does not start on physical sector boundary.
/dev/sda5 968390656 976771071 4190208 82 Linux swap / Solaris

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = setores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Dispositivo Boot Start End Blocks Id System
/dev/sdc1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = setores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Dispositivo Boot Start End Blocks Id System
/dev/sdb1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/md0: 1000.1 GB, 1000064483328 bytes
2 heads, 4 sectors/track, 244156368 cylinders, total 1953250944 sectors
Units = setores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

O disco /dev/md0 não contém uma tabela de partições válida

Disk /dev/md1: 1000.1 GB, 1000064483328 bytes
2 heads, 4 sectors/track, 244156368 cylinders, total 1953250944 sectors
Units = setores of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

O disco /dev/md1 não contém uma tabela de partições válida
root@Storage:~#



ALGUEM CONSEGUE ENTENDER O QUE ESTÁ ACONTECENDO??
jÁ FORMATEI, REFORMATEI PELO UTILITÁRIO DO DEBIAN, PELO GPARTED, PELO FDISK E NADA.
sÃO 2 HDS COM 2 PARTIÇÕES CADA IDÊNTICAS QUE ESTOU TENTANDO COLOCAR EM RAID1.
mAS QUANDO REINICIO PERDE TUDO.