RAID Toleransondan Fazla Disk Kaybederseniz 1. Senaryo

Müşteri 4. diski değiştirdiğinden beriş Cihaz loading drive’da kalıyordu. Congif_util denemesi işe yaramadı ve 1. diskte problem görünüyordu.

çözüm olarak mdadm -E /dev/sda3 komutu ile diskleri taradım, ve 4. diskin raid yapısında olmadığını görüm. bu diski çıkartınca cihaz açıldı.

Layout : left-symmetric

Chunk Size : 64K

Number Major Minor RaidDevice State

this 0 8 3 0 active sync /dev/sda3

0 0 8 3 0 active sync /dev/sda3

1 1 8 19 1 active sync /dev/sdb3

2 2 8 35 2 active sync /dev/sdc3

3 3 0 0 3 faulty removed

4 4 8 67 4 active sync /dev/sde3

5 5 8 83 5 active sync /dev/sdf3

6 6 8 51 6 spare /dev/sdd3

[~] # mdadm -E /dev/sdb3

/dev/sdb3:

Magic : a92b4efc

Version : 00.90.00

UUID : 2bb0f18e:8ea3d649:f0048a8d:8241b829

Creation Time : Thu May 6 00:20:35 2010

Raid Level : raid5

Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)

Array Size : 9759728000 (9307.60 GiB 9993.96 GB)

Raid Devices : 6

Total Devices : 6

Preferred Minor : 0

Update Time : Tue Jul 24 16:05:22 2012

State : clean

Active Devices : 5

Working Devices : 6

Failed Devices : 1

Spare Devices : 1

Checksum : e658c8ce – correct

Events : 0.2371926

Layout : left-symmetric

Chunk Size : 64K

Number Major Minor RaidDevice State

this 1 8 19 1 active sync /dev/sdb3

0 0 8 3 0 active sync /dev/sda3

1 1 8 19 1 active sync /dev/sdb3

2 2 8 35 2 active sync /dev/sdc3

3 3 0 0 3 faulty removed

4 4 8 67 4 active sync /dev/sde3

5 5 8 83 5 active sync /dev/sdf3

6 6 8 51 6 spare /dev/sdd3

[~] # mdadm -E /dev/sdc3

/dev/sdc3:

Magic : a92b4efc

Version : 00.90.00

UUID : 2bb0f18e:8ea3d649:f0048a8d:8241b829

Creation Time : Thu May 6 00:20:35 2010

Raid Level : raid5

Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)

Array Size : 9759728000 (9307.60 GiB 9993.96 GB)

Raid Devices : 6

Total Devices : 6

Preferred Minor : 0

Update Time : Tue Jul 24 16:05:22 2012

State : clean

Active Devices : 5

Working Devices : 6

Failed Devices : 1

Spare Devices : 1

Checksum : e658c8e0 – correct

Events : 0.2371926

Layout : left-symmetric

Chunk Size : 64K

Number Major Minor RaidDevice State

this 2 8 35 2 active sync /dev/sdc3

0 0 8 3 0 active sync /dev/sda3

1 1 8 19 1 active sync /dev/sdb3

2 2 8 35 2 active sync /dev/sdc3

3 3 0 0 3 faulty removed

4 4 8 67 4 active sync /dev/sde3

5 5 8 83 5 active sync /dev/sdf3

6 6 8 51 6 spare /dev/sdd3

[~] # mdadm -E /dev/sdd3

/dev/sdd3:

Magic : a92b4efc

Version : 00.90.00

UUID : 2bb0f18e:8ea3d649:f0048a8d:8241b829

Creation Time : Thu May 6 00:20:35 2010

Raid Level : raid5

Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)

Array Size : 9759728000 (9307.60 GiB 9993.96 GB)

Raid Devices : 6

Total Devices : 6

Preferred Minor : 0

Update Time : Tue Jul 24 16:05:22 2012

State : clean

Active Devices : 5

Working Devices : 6

Failed Devices : 1

Spare Devices : 1

Checksum : e658c8f2 – correct

Events : 0.2371926

Layout : left-symmetric

Chunk Size : 64K

Number Major Minor RaidDevice State

this 6 8 51 6 spare /dev/sdd3

0 0 8 3 0 active sync /dev/sda3

1 1 8 19 1 active sync /dev/sdb3

2 2 8 35 2 active sync /dev/sdc3

3 3 0 0 3 faulty removed

4 4 8 67 4 active sync /dev/sde3

5 5 8 83 5 active sync /dev/sdf3

6 6 8 51 6 spare /dev/sdd3

[~] # mdadm -E /dev/sde3

/dev/sde3:

Magic : a92b4efc

Version : 00.90.00

UUID : 2bb0f18e:8ea3d649:f0048a8d:8241b829

Creation Time : Thu May 6 00:20:35 2010

Raid Level : raid5

Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)

Array Size : 9759728000 (9307.60 GiB 9993.96 GB)

Raid Devices : 6

Total Devices : 6

Preferred Minor : 0

Update Time : Tue Jul 24 16:05:22 2012

State : clean

Active Devices : 5

Working Devices : 6

Failed Devices : 1

Spare Devices : 1

Checksum : e658c904 – correct

Events : 0.2371926

Layout : left-symmetric

Chunk Size : 64K

Number Major Minor RaidDevice State

this 4 8 67 4 active sync /dev/sde3

0 0 8 3 0 active sync /dev/sda3

1 1 8 19 1 active sync /dev/sdb3

2 2 8 35 2 active sync /dev/sdc3

3 3 0 0 3 faulty removed

4 4 8 67 4 active sync /dev/sde3

5 5 8 83 5 active sync /dev/sdf3

6 6 8 51 6 spare /dev/sdd3

[~] # mdadm -E /dev/sdf3

/dev/sdf3:

Magic : a92b4efc

Version : 00.90.00

UUID : 2bb0f18e:8ea3d649:f0048a8d:8241b829

Creation Time : Thu May 6 00:20:35 2010

Raid Level : raid5

Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)

Array Size : 9759728000 (9307.60 GiB 9993.96 GB)

Raid Devices : 6

Total Devices : 6

Preferred Minor : 0

Update Time : Tue Jul 24 16:05:22 2012

State : clean

Active Devices : 5

Working Devices : 6

Failed Devices : 1

Spare Devices : 1

Checksum : e658c916 – correct

Events : 0.2371926

Layout : left-symmetric

Chunk Size : 64K

Number Major Minor RaidDevice State

this 5 8 83 5 active sync /dev/sdf3

0 0 8 3 0 active sync /dev/sda3

1 1 8 19 1 active sync /dev/sdb3

2 2 8 35 2 active sync /dev/sdc3

3 3 0 0 3 faulty removed

4 4 8 67 4 active sync /dev/sde3

5 5 8 83 5 active sync /dev/sdf3

6 6 8 51 6 spare /dev/sdd3

[~] # mdadm -Af /dev/md0 /dev/sd[a-f]3

mdadm: /dev/md0 has been started with 5 drives (out of 6) and 1 spare.

[~] # config_uti

[~] # config_uti 1

-sh: config_uti: command not found

[~] # config_util 1

Start to mirror ROOT part…

config_util: HD1 CONF_HWADDR_NOT_MATCH.

config_util: HD2 CONF_HWADDR_NOT_MATCH.

config_util: HD3 CONF_HWADDR_NOT_MATCH.

config_util: HD4 CONF_HWADDR_NOT_MATCH.

config_util: HD5 CONF_HWADDR_NOT_MATCH.

config_util: HD6 CONF_HWADDR_NOT_MATCH.

mdadm: /dev/md9 has been started with 6 drives.

Mirror of ROOT succeeded.

[~] #

[~] # storage_boot_init 1

storage_boot_init 1 …

Checking for bad blocks (read-only test): done

mdadm: /dev/sda2 appears to be part of a raid array:

level=raid1 devices=2 ctime=Tue Jul 24 16:04:24 2012

mdadm: array /dev/md6 started.

Checking for bad blocks (read-only test): done

mdadm: added /dev/sdb2

mdadm: added /dev/sdc2

mdadm: added /dev/sdd2

mdadm: added /dev/sde2

mdadm: added /dev/sdf2

mdadm: cannot get array info for /dev/sda4

mdadm: cannot get array info for /dev/sda4

mdadm: cannot get array info for /dev/sda4

mdadm: cannot get array info for /dev/sda4

mdadm: cannot get array info for /dev/sda4

mdadm: cannot get array info for /dev/sda4

[~] #

 

 

VN:F [1.9.22_1171]
Rating: 1.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: -1 (from 1 vote)
RAID Toleransondan Fazla Disk Kaybederseniz 1. SenaryoIf Loose More HDD than RAID Tolarete, Scenario 1, 1.0 out of 10 based on 1 rating

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>