Thanks for the reply. I tried the --assmemble command not the --create command. If I run create I am afraid I will destroy the existing array (such as it is).
I have no idea what is going on on. My mdadm.conf file looks like:
cat /etc/mdadm/mdadm.conf ARRAY /dev/md2 level=raid1 num-devices=2 UUID=bf0fdc1c:7831246c:cd2a4a74:fa419930 ARRAY /dev/md1 level=raid1 num-devices=2 /dev/hd[ac]6 ARRAY /dev/md0 level=raid1 num-devices=2 /dev/hd[ac]7 UUID=bd37878c:e24b3b3d:fcb4335e:9761b852
when I do mdadm -Es I get: mdadm: only give one device per ARRAY line: /dev/md1 and /dev/hd[ac]6 mdadm: ARRAY line /dev/md1 has no identity information. mdadm: only give one device per ARRAY line: /dev/md0 and /dev/hd[ac]7 mdadm: No devices listed in /etc/mdadm/mdadm.conf
However when I do: mdadm --detail /dev/md2 /dev/md2: Version : 00.90.03 Creation Time : Mon Feb 19 11:28:16 2007 Raid Level : raid1 Array Size : 89747072 (85.59 GiB 91.90 GB) Device Size : 89747072 (85.59 GiB 91.90 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is not persistent
Update Time : Tue Feb 20 22:12:33 2007 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0
Number Major Minor RaidDevice State 0 3 7 0 active sync /dev/hda7 1 22 7 1 active sync /dev/hdc7
which is what I expect!
But mdadm -Es -vv /dev/md2 /dev/md2: Magic : a92b4efc Version : 00.90.00 UUID : bf0fdc1c:7831246c:cd2a4a74:fa419930 Creation Time : Sat Feb 7 13:42:02 2004 Raid Level : raid1 Raid Devices : 2 Total Devices : 1 Preferred Minor : 4
Update Time : Wed Jan 31 05:47:51 2007 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Checksum : 33961742 - correct Events : 0.4149720
Number Major Minor RaidDevice State
this 1 22 7 1 active sync /dev/hdc7
0 0 0 0 0 removed 1 1 22 7 1 active sync /dev/hdc7
tells me something different.
Now looking at df it tells me that md2 is mounted. #df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hdb5 5162796 2399004 2501536 49% / varrun 518076 92 517984 1% /var/run varlock 518076 4 518072 1% /var/lock udev 518076 168 517908 1% /dev devshm 518076 0 518076 0% /dev/shm lrm 518076 18856 499220 4% /lib/modules/2.6.15-27-386/volatile /dev/hdb1 37604 22531 13067 64% /boot /dev/hdb6 4134900 131260 3793592 4% /opt /dev/hdb7 2925300 731416 2045288 27% /var /dev/md2 88338256 27919288 55931620 34% /home
I suspect that the array is functioning with only one drive, how do I fix this so it will work with two drives? It is crucial I don't delete any of the data on the drive.
Would mdadm /dev/md2 -a /dev/hda7
add /dev/hda7 back into the array and bring it up to date?
----------------------------------
On a slightly different subject, reading the manual I don't understand what is meant by partitions in this context. A few more examples would be very helpful. For example what a mdadm.conf file looks like and how to produce one. What the difference is between create, assemble and build. Why you sometimes get persistent superblock and sometimes not and why this makes any difference?
Your attention to this is very much appreciated, if you need any more detail please let me know.
many thanks
Robert
