Fedora Core 4 Software Raid 1problems after reboot
Hi, I am trying to install zinf music player. It is a tar.gz file and needs to be configured. Here are the install instructions:- The simplest way to...
I have 2 80 GB disks (-dev-hda anddev-hdc)
I migrated from a Non-raid configuration to a raid configuration without a re-install.
I have it all working except one of the raid parbreastions degrades after a reboot.
$ df Filesystem 1K-blocks Used Available Use% Mounted ondev-md3 76233872 9282168 63079240 13%dev-md1 194366 45184 139147 25%bootdev-shm 111832 0 111832 0%dev-shmdev-hdb 38468940 33881392 2633416 93%disk3
$ catetc-mdadm.conf DEVICEdev-hda*dev-hdc* ARRAYdev-md2 level=raid1 num-devices=2 UUID=d35259e2:c0f1f20a:bcdc9650:001fe965 devices=-dev-hda2,-dev-hdc2 ARRAYdev-md3 level=raid1 num-devices=2 UUID=f7ea0b01:1ab955ce:4588cc15:e1eb2c7d devices=-dev-hda3,-dev-hdc3 ARRAYdev-md1 level=raid1 num-devices=2 UUID=ac770950:fd5b77b6:ee4bd665:4e224afd devices=-dev-hda1,-dev-hdc1
$ catetc-mdadm.conf DEVICEdev-hda*dev-hdc* ARRAYdev-md2 level=raid1 num-devices=2 UUID=d35259e2:c0f1f20a:bcdc9650:001fe965 devices=-dev-hda2,-dev-hdc2 ARRAYdev-md3 level=raid1 num-devices=2 UUID=f7ea0b01:1ab955ce:4588cc15:e1eb2c7d devices=-dev-hda3,-dev-hdc3 ARRAYdev-md1 level=raid1 num-devices=2 UUID=ac770950:fd5b77b6:ee4bd665:4e224afd devices=-dev-hda1,-dev-hdc1
Black Sun and said: (Plaigarized from Chris F.A. Johnson:) When using groups.google to reply to a Usenet article...
$ sudo mdadm --detaildev-md3dev-md3: Version : 00.90.03 Creation Time : Fri May 12 22:27:53 2006 Raid Level : raid1 Array Size : 77449280 (73.86 GiB 79.31 GB) Device Size : 77449280 (73.86 GiB 79.31 GB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 3 Persistence : Superblock is persistent
Update Time : Sat May 13 11:58:47 2006 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0
UUID : f7ea0b01:1ab955ce:4588cc15:e1eb2c7d Events : 0.50108
Number Major Minor RaidDevice State 0 0 0 - removed 1 22 3 1 active sync dev-hdc3
After I have run mdadm to adddev-hda3 to thedev-md3 raid I have run the necissary mkinitrd command to rebuild the initrd image for booting, but when I reboot I end up withdev-hda3 out of the raid configuration.
mdadm --managedev-md3 -adev-hda3
then wait for the raid to sync and then run
mkinitrd -f -vboot-initrd-2.6.16-1.2096FC4-md.img 2.6.16-1.2096FC4
the raid configuration fordev-md1 (-boot) anddev-md2 (swap) work like a champ, so I'm not sure whydev-hda3 is not sticking in thedev-md3 meta device when I reboot the system.
I'm sure I am missing something simple, I just don't see what it is, I have readdeddev-hda3 to the raid 3 times now, and it dissappears after each reboot.
Any suggestions would be greatly appreciated.
Cheers, -tyler
Linux groups from Newsgroups