Ich hab seit ca 1 1/2 Jahren ein Rootserver mit zwei HDD's auf denen ich vier Raid1 partitionen mit mdadm eingerichtet habe.
Seit anfang des jahres degraden die mittleren zwei partitionen nach einem reboot.
In dmesg fehlen sda2 und sda3 einfach beim zusammenbau des Raids.
Ich denke als workaround (unschön) würde ich in der mdadm.conf die UUID's durch direkte Partitionsangaben ersetzen.
Dann müßte er zumindest einen Fehler bringen wenn sda* nichtmehr ins Raid past.
Code: Select all
~# cat /etc/mdadm/mdadm.conf
DEVICE /dev/sd*[0-9]
ARRAY /dev/md3 level=raid1 num-devices=2 UUID=a0f97025:c2564410:5eb01849:761506a6
devices=/dev/sda4,/dev/sdb4
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=9df52817:ae429b05:8e0c8200:846b324f
devices=/dev/sda3,/dev/sdb3
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=f7f3c5d1:cc8c0bc1:df01f22c:c0d22438
devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=4b0599e0:e23ee835:c125ff8b:e5a38489
devices=/dev/sda1,/dev/sdb1
Code: Select all
~# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda1[0] sdb1[1]
48064 blocks [2/2] [UU]
md3 : active raid1 sda4[0] sdb4[1]
104141248 blocks [2/2] [UU]
md1 : active raid1 sdb2[1]
50002240 blocks [2/1] [_U]
md2 : active raid1 sdb3[1]
2096384 blocks [2/1] [_U]
unused devices: <none>
Code: Select all
sata_via(0000:00:0f.0): routed to hard irq line 11
ata1: SATA max UDMA/133 cmd 0xE100 ctl 0xE202 bmdma 0xE500 irq 177
ata2: SATA max UDMA/133 cmd 0xE300 ctl 0xE402 bmdma 0xE508 irq 177
ata1: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7468 86:bc01 87:4023 88:80ff
ata1: dev 0 ATA, max UDMA7, 312581808 sectors: lba48
ata1: dev 0 configured for UDMA/133
scsi0 : sata_via
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01 87:4763 88:407f
ata2: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
ata2: dev 0 configured for UDMA/133
scsi1 : sata_via
Using anticipatory io scheduler
Vendor: ATA Model: SAMSUNG HD160JJ Rev: ZM10
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: Maxtor 6V160E0 Rev: VA11
Type: Direct-Access ANSI SCSI revision: 05
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sdb: drive cache: write back
/dev/scsi/host1/bus0/target0/lun0: p1 p2 p3 p4
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
md: md2 stopped.
md: bind<sdb3>
raid1: raid set md2 active with 1 out of 2 mirrors
md: md1 stopped.
md: bind<sdb2>
raid1: raid set md1 active with 1 out of 2 mirrors
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: md1: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 6225996
EXT3-fs: md1: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2096376k swap on /dev/md2. Priority:-1 extents:1
EXT3 FS on md1, internal journal
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com
md: md3 stopped.
md: bind<sdb4>
md: bind<sda4>
raid1: raid set md3 active with 2 out of 2 mirrors
md: md0 stopped.
md: bind<sdb1>
md: bind<sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on md3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NET: Registered protocol family 10