I actually have two questions related to this topic. Let me give a brief rundown of my system setup, though.
The system is running Red Hat Linux 7.2. I am using Software-RAID for the root partition (/dev/hda3 and /dev/hdd1 as /dev/md0 RAID-1), and a standard ext3 partition for /boot. I am also using kernel-2.4.9-34, but would like to upgrade as soon as possible. (Please note that most of the logs or config files I show will be trimmed to only show what is needed) * Problem #1: I am trying to upgrade to kernel-2.4.20-18.7, but am having some difficulty with Software-RAID working once I have installed the RPM. After installing the RPM with up2date, I made sure the changes to LILO were made, and rebooted. It looked like everything was okay after that, but I wasn't getting any statistics from the second drive in the array (hdd1). I ran procinfo from the shell, and it confirmed that only drive 1 (hda3) was getting any read/writes. I went through /var/spool/messages, and found the following: Jun 25 19:45:08 us1 kernel: kmod: failed to exec /sbin/modprobe -s -k md- personality-3, errno = 2 Jun 25 19:45:08 us1 kernel: md: personality 3 is not loaded! Jun 25 19:45:08 us1 kernel: md :do_md_run() returned -22 Jun 25 19:45:08 us1 kernel: md: md0 stopped. Jun 25 19:45:08 us1 kernel: md: unbind<hdd1,1> Jun 25 19:45:08 us1 kernel: md: export_rdev(hdd1) Jun 25 19:45:08 us1 kernel: md: unbind<hda3,0> Jun 25 19:45:08 us1 kernel: md: export_rdev(hda3) I checked /sbin/modprobe -c and it had an alias set up that looked okay: alias md-personality-3 raid1 More or less, I'm stumped at this point. I noticed that I have kernel- headers-2.4.9-34 installed, but there aren't any upgrades for it that I can see on RHN. I tried kernel-source, but it didn't seem to help either. Eventually I switched back to 2.4.9-34 and removed the updated RPM. Any ideas? Am I missing a step somewhere? * Problem 2: Probably not as weird as my first problem, but nonetheless a problem. I've had hardware issues recently with drive 1 (hda3) of the array, and since having it replaced completely. Before doing this I was able to clone the partition table, /boot, and repopulate the root partition to that drive without incident. However, someone recommended that I check out the mdadm utility, which they said often is a little more robust then the raidtools set that comes standard with RH. I ran a detail report on /dev/md0, and noticed the array state was "dirty, no errors". Is there any way to make this "clean"? Or is this even a problem? Thanks in advance for any help you may be able to provide. :) -- Ricky -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
