Re: check superblock
On Wednesday 21 February 2007 04:35, pinniped wrote:
> Make sure the RAID device is set to be 'persistent'.
It seems they are:
# mdadm --detail /dev/md0
/dev/md0:
[...]
Persistence : Superblock is persistent
[...]
# mdadm --detail /dev/md1
/dev/md1:
[...]
Persistence : Superblock is persistent
> Also check backwards
> through scripts to see where md2 might fail.
md2 is no failing, md0 and md1 are failing, which are / and swap. I haven't
written any scripts myself, any ideas about what I should check?
--
José Pablo Fernández
pablo.fernandez@rs.com.ar
PS: full outputs:
# mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.01
Creation Time : Tue Feb 7 14:58:18 2006
Raid Level : raid1
Array Size : 15623104 (14.90 GiB 16.00 GB)
Device Size : 15623104 (14.90 GiB 16.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Wed Feb 21 14:19:48 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : a1a07d14:64ab7244:8a585e9b:fbee0505
Events : 0.6126578
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
# mdadm --detail /dev/md1
/dev/md1:
Version : 00.90.01
Creation Time : Tue Feb 7 14:59:06 2006
Raid Level : raid1
Array Size : 979840 (956.88 MiB 1003.36 MB)
Device Size : 979840 (956.88 MiB 1003.36 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Wed Feb 21 01:14:59 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 2e8d1e91:1db84b53:602c6a7d:b9fb162a
Events : 0.1411
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
Reply to: