[mythtv-users] Rebuild raid array ? [SOLVED]

Kevin Bailey keraba at gmail.com
Thu Nov 25 19:06:23 UTC 2010


On 11/25/2010 07:30 AM, Kevin Bailey wrote:
> On Wed, Nov 24, 2010 at 8:17 PM, Greg Oliver <oliver.greg at gmail.com
> <mailto:oliver.greg at gmail.com>> wrote:
>
>
>     You are pointing mkinitrd to the mdadm.conf so it gets included?
>     Beyond that I do not know - especially if rescur mode can see it.  Did
>     you chroot into your install before you rebooted and install the md
>     stuff into your initrd?
>
>
> The initrd has a good mdadm.conf. Its /etc/passwd, /etc/group
> and possibly something related to udev that's missing. All I did
> was search and replace /etc/apt/sources.list with lucid and
> let it update.
>
So I was wondering, if Lucid didn't update the kernel, shouldn't
the initramfs still work ? (There might be some incompatibility
but it should boot.) Sure enough, the Lucid update *had* touched
the initrd. Fortunately, it left a back-up copy. I swapped the two
and booted. It whined and mounted /dev/md0 read-only, but that's
easy to fix.

I wasn't sure what to do at this point, so I tried a hail, Mary: Just
install the latest kernel and pray. This worked perfectly. Not sure
why the previous update didn't. Maybe it didn't do a update-grub ? <shrug>

I think the "degraded array" and fsck problems were red herrings.
They needed to be fixed, for sure, but they weren't preventing the mount.

Thanks to all who responded. I think its awesome that this list
has maintained its helpfulness through the years. Go myth!
And have some pumpkin pie on me. :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20101125/dceb4db2/attachment.htm>


More information about the mythtv-users mailing list