how to reconstruct MD RAID device?
Hi,
a Debian 3.1 system which uses md devices for all its file systems and
swap was reset by a power failure. On startup, the root file systems
md device failed to configure and is in degraded mode now. I think the
failed device is probably fine, but md configuration failed due to
parity errors or similar. After skimming through mdadm(8)'s man page
I still can't figure out what I need to do now, so help is appreciated.
Some data:
$ mount
/dev/md2 on / type ext3 (rw,errors=remount-ro)
[...]
$ cat /etc/mdadm/mdadm.conf
DEVICE partitions
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=[...]
devices=/dev/hda3,/dev/hdb3
[...]
$ mdadm -D /dev/md2
/dev/md2:
Version : 00.90.01
Creation Time : Fri Dec 17 12:05:14 2004
Raid Level : raid1
Array Size : 39107264 (37.30 GiB 40.05 GB)
Device Size : 39107264 (37.30 GiB 40.05 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Wed Aug 24 14:35:53 2005
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : b631314e:ec41bac8:9656de45:6591d219
Events : 0.2461867
Number Major Minor RaidDevice State
0 3 3 0 active sync /dev/hda3
1 0 0 - removed
$ dmesg
[...]
Kernel command line: root=/dev/md2 ro
[...]
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: raid1 personality registered as nr 3
[...]
hda: max request size: 128KiB
hda: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3
hdb: max request size: 128KiB
hdb: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target1/lun0: p1 p2 p3
md: md1 stopped.
md: bind<hdb2>
md: bind<hda2>
raid1: raid set md1 active with 2 out of 2 mirrors
md: md2 stopped.
md: bind<hdb3>
md: bind<hda3>
md: kicking non-fresh hdb3 from array!
md: unbind<hdb3>
md: export_rdev(hdb3)
raid1: raid set md2 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: md2: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 1667940
EXT3-fs: md2: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 976632k swap on /dev/md1. Priority:-1 extents:1
EXT3 FS on md2, internal journal
Generic RTC Driver v1.07
SCSI subsystem initialized
Capability LSM initialized
md: md0 stopped.
md: bind<hdb1>
md: bind<hda1>
raid1: raid set md0 active with 2 out of 2 mirrors
[...]
TIA, Jukka
--
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~
Reply to: