Hello,
Short story: I replaced a drive with SMART errors. The new drive is the same as the replaced. A 3TB WD red. And now I receive DegradedArray events.
Long story:
I degraded the array before I removed the bad drive. I have done this before, to check the drive in a other PC. The recover worked fine every time (when I put back the SAME drive).
This time I build in a new drive. Same type, same sice, same vendor. I simply clicked Recover in the RAID Management, selected the new drive and the system started to synchronise the data. But now I receive degraded array events:
This is an automatically generated mail message from mdadm
running on pluto
A DegradedArray event had been detected on md device /dev/md/DATA.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid1]
md127 : active raid1 sdc[3](S) sdb[2]
2930265424 blocks super 1.2 [2/1] [_U]
unused devices: <none>
Alles anzeigen
And the detail view in the RAID Management shows me the new drive as a spare drive instead a mirror.
Version : 1.2
Creation Time : Thu Sep 26 22:07:35 2013
Raid Level : raid1
Array Size : 2930265424 (2794.52 GiB 3000.59 GB)
Used Dev Size : 2930265424 (2794.52 GiB 3000.59 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Tue Jul 26 19:42:02 2016
State : clean, degraded
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1
Name : pluto:DATA (local to host pluto)
UUID : e282c2db:a6042f4e:af0bb276:7652b009
Events : 155253
Number Major Minor RaidDevice State
0 0 0 0 removed
2 8 16 1 active sync /dev/sdb
3 8 32 - spare /dev/sdc
Alles anzeigen
I'm not sure, what to do know. Can I just degrade the array and try to recover it again?
I suspect there could be a problem in a config file or something like this.
Maybe it is importend to mention, that also the first drive (the drive with the data) start to throw SMART errors, too. I planned to recover the array and replace also the first drive before I run into this problems.
And there is a third drive in the PC. sda conatins only the OS and is not part of the Array.
Here a are the infos, mentioned in the pinned Thread above.
root@pluto:~# cat /proc/mdstat
Personalities : [raid1]
md127 : active raid1 sdc[3](S) sdb[2]
2930265424 blocks super 1.2 [2/1] [_U]
unused devices: <none>
root@pluto:~# blkid
/dev/sda1: UUID="0c8aa7c5-8de0-4a86-9b04-ec24d889a206" TYPE="ext4"
/dev/sda5: UUID="b875d1d9-898c-43bc-8ac3-88db0fa4925a" TYPE="swap"
/dev/md127: LABEL="data" UUID="48f49465-8540-4dd3-b579-a33e0d7f406a" TYPE="ext3" SEC_TYPE="ext2"
/dev/sdb: UUID="e282c2db-a604-2f4e-af0b-b2767652b009" UUID_SUB="7f0e24fc-87df-a794-fd30-accc7d2bb34b" LABEL="pluto:DATA" TYPE="linux_raid_member"
/dev/sdc: UUID="e282c2db-a604-2f4e-af0b-b2767652b009" UUID_SUB="79d1c966-1a26-06ad-469e-3c9ce3126d38" LABEL="pluto:DATA" TYPE="linux_raid_member"
root@pluto:~# fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000047f4
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 224860159 112429056 83 Linux
/dev/sda2 224862206 234440703 4789249 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 224862208 234440703 4789248 82 Linux swap / Solaris
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors 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
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors 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
Disk /dev/sdc doesn't contain a valid partition table
Disk /dev/md127: 3000.6 GB, 3000591794176 bytes
2 heads, 4 sectors/track, 732566356 cylinders, total 5860530848 sectors
Units = sectors 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
Disk /dev/md127 doesn't contain a valid partition table
Alles anzeigen
root@pluto:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md/DATA metadata=1.2 spares=1 name=pluto:DATA UUID=e282c2db:a6042f4e:af0bb276:7652b009
# instruct the monitoring daemon where to send mail alerts
MAILADDR robert@mymail.de
MAILFROM root
Alles anzeigen