Martin,
first of all, thank you very much for the fast response.
martin f krafft schrieb:
> Yes, this may well be the problem. However, I would not be able to
> tell since you did not include any relevant information with your
> initial email. Please send me the mdadm -E and mdadm -D outputs you
> alluded to.
I have included the information at the end.
> If the problem is really because of a wrong homehost field, then
>
> mdadm -A /dev/mdX --homehost=whatever --update=homehost /dev/XXXX.....
>
> is the way to fix it, meaning you assemble the array and force the
> update of the superblock information. Neil Brown, the author, was
> kind enough to take a look at your problem and the above is his
> suggestion. If that doesn't work, we need more information.
This is very kind. Unfortunately,
mdadm -A /dev/md4 --homehost=mercury --update=homehost --auto=yes /dev/hde2
/dev/hdf2
didn't solve the problem, but there is another interesting point:
o as far as I understood from the available documentation, that homehost is
stored in UUID=A:B:<here>:<here>
o the arrays /dev/md0 and /dev/md1 had been created in 2005 and had been
"converted" while installing the
new package versions, showing now both a4b55d23:82b70df8
o for /dev/md3 being created after the package update, I tried already before
--homehost=mercury --update=homehost
and for /dev/md4 today, showing now both ef85aaf3:69789572 (which is
different)
Thank you all for further support in advance!
Ciao
Max
> mdadm -D --scan
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=3eae8d0d:8e2777a8:a4b55d23:82b70df8
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=dbf5842c:f9e1d0f0:a4b55d23:82b70df8
> mdadm -E --scan
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=dbf5842c:f9e1d0f0:a4b55d23:82b70df8
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=3eae8d0d:8e2777a8:a4b55d23:82b70df8
ARRAY /dev/md3 level=raid1 num-devices=2
UUID=673735db:f3bcbe6e:ef85aaf3:69789572
ARRAY /dev/md4 level=raid1 num-devices=2
UUID=5acae97b:8517e289:44e82faf:d72d3fc1
ARRAY /dev/md5 level=raid1 num-devices=2
UUID=f50f166e:d3e13df6:15c27e68:cee986f9
> mdadm -E /dev/md0
mdadm: No md superblock detected on /dev/md0.
> mdadm -E /dev/md1
mdadm: No md superblock detected on /dev/md1.
> mdadm -D /dev/md0
Version : 00.90.03
Creation Time : Sat Jul 9 18:08:07 2005
Raid Level : raid1
Array Size : 979840 (957.04 MiB 1003.36 MB)
Device Size : 979840 (957.04 MiB 1003.36 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sat Dec 16 16:45:56 2006
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : dbf5842c:f9e1d0f0:a4b55d23:82b70df8
Events : 0.526
Number Major Minor RaidDevice State
0 3 1 0 active sync /dev/hda1
1 3 65 1 active sync /dev/hdb1
> mdadm -D /dev/md1
Version : 00.90.03
Creation Time : Sat Jul 9 18:08:24 2005
Raid Level : raid1
Array Size : 44050112 (42.01 GiB 45.11 GB)
Device Size : 44050112 (42.01 GiB 45.11 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Sat Dec 16 16:45:57 2006
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 3eae8d0d:8e2777a8:a4b55d23:82b70df8
Events : 0.46754
Number Major Minor RaidDevice State
0 3 2 0 active sync /dev/hda2
1 3 66 1 active sync /dev/hdb2
> mdadm -A /dev/md4 --homehost=mercury --update=homehost --auto=yes /dev/hde2
> /dev/hdf2
> mdadm -E /dev/md4
mdadm: No md superblock detected on /dev/md4.
> mdadm -D /dev/md4
Version : 00.90.03
Creation Time : Tue Dec 12 20:07:06 2006
Raid Level : raid1
Array Size : 310126720 (295.76 GiB 317.57 GB)
Device Size : 310126720 (295.76 GiB 317.57 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 4
Persistence : Superblock is persistent
Update Time : Sat Dec 16 16:39:21 2006
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 5acae97b:8517e289:ef85aaf3:69789572
Events : 0.2
Number Major Minor RaidDevice State
0 33 2 0 active sync /dev/hde2
1 33 66 1 active sync /dev/hdf2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
