Topic: miror sme 9

[mgb]

I start   Mirrors
 in admin/manager
my disk  is 4t
is not work

[mgb]

The question of whether I should prepare the disk in GPT.
I made the old disk with GPT .
I wish to allow adding a further Disk Mirror

[mgb]

pic

[mgb]

This is an automatically generated mail message from mdadm
running on radiu

A DegradedArray event had been detected on md device /dev/md0.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1]
md0 : active raid1 sda1[0]
      255936 blocks super 1.0 [2/1] [U_]
     
md1 : active raid1 sda2[0]
      3906629440 blocks super 1.1 [2/1] [U_]
      bitmap: 30/30 pages [120KB], 65536KB chunk

unused devices: <none>

[stephdl]

Hi

I recall I did an installation  of sme9 on a gpt partition of 4TB, without doing something, bought the drive, put it in the caddy and installed it. I'm not sure that el6 could do a gpt table, in generally I use the  systemrescuecd (on an usbKey) and I use gparted.

[mgb]

is not work

phpsysinfo

SCSI Devices
ATA WDC WD40EZRX-00S (Direct-Access)
ATA WDC WD40EZRZ-00W (Direct-Access)
log
radiu add_drive_to_raid: Warning: partition 1 does not end at a cylinder boundary
Jul 11 12:15:37 radiu add_drive_to_raid:
Jul 11 12:15:37 radiu add_drive_to_raid: Disk /dev/sdb: 486401 cylinders, 255 heads, 63 sectors/track
Jul 11 12:15:37 radiu add_drive_to_raid: Old situation:
Jul 11 12:15:37 radiu add_drive_to_raid: Units = blocks of 1024 bytes, counting from 0
Jul 11 12:15:37 radiu add_drive_to_raid:
Jul 11 12:15:37 radiu add_drive_to_raid:    Device Boot   Start       End    #blocks   Id  System
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb1   *        0+   256000     256000+  fd  Linux raid autodetect
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb2       256001  1759534935  1759278935   fd  Linux raid autodetect
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb3            0         -          0    0  Empty
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb4            0         -          0    0  Empty
Jul 11 12:15:37 radiu add_drive_to_raid: New situation:
Jul 11 12:15:37 radiu add_drive_to_raid: Units = blocks of 1024 bytes, counting from 0
Jul 11 12:15:37 radiu add_drive_to_raid:
Jul 11 12:15:37 radiu add_drive_to_raid:    Device Boot   Start       End    #blocks   Id  System
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb1   *        0+   256000     256000+  fd  Linux raid autodetect
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb2       256001  3907018583  3906762583   fd  Linux raid autodetect
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb3            0         -          0    0  Empty
Jul 11 12:15:37 radiu add_drive_to_raid: /dev/sdb4            0         -          0    0  Empty
Jul 11 12:15:37 radiu add_drive_to_raid: Successfully wrote the new partition table
Jul 11 12:15:37 radiu add_drive_to_raid:
Jul 11 12:15:37 radiu add_drive_to_raid: Re-reading the partition table ...
Jul 11 12:15:38 radiu kernel: sdb: sdb1 sdb2
Jul 11 12:15:38 radiu add_drive_to_raid: If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
Jul 11 12:15:38 radiu add_drive_to_raid: to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
Jul 11 12:15:38 radiu add_drive_to_raid: (See fdisk(.)
Jul 11 12:15:38 radiu add_drive_to_raid:
Jul 11 12:16:42 radiu add_drive_to_raid:
Jul 11 12:16:42 radiu add_drive_to_raid: Partitions on /dev/sdb aren't correct.  Reboot may be necessary.
Jul 11 12:16:42 radiu add_drive_to_raid:
Jul 11 12:16:42 radiu add_drive_to_raid: Checking partitions on /dev/sdb...
Jul 11 12:16:42 radiu add_drive_to_raid:
Jul 11 12:16:42 radiu add_drive_to_raid: Closing stdin pipe reported: