On Wed, 14 Aug 2013 15:49:37 -0500 (CDT) fixitdad5@xxxxxxxxxxx wrote: > If you are still offering help with raid corruption due to the bug in kernels 3.2 and 3.3, I would like some help. > > I load Ubuntu 12.04 precise (with kernel 3.2 since it was in the package) just 2 weeks ago. I had pre-existing raids and the raid's meta data was corrupted on the first boot after the successful installation so I have lost my data. I tried most of the suggestions that I found on the web, employing the intelligence in mdadm -assemble, etc. without success. > > I have now updated the kernel to 3.4.0 rc7 (3.4.0-030400-generic #201205210521 SMP) and built an empty raid. However, I cannot boot without disconnecting the RAID drives. With the RAID drives hooked up and the updated kernel with the additional parameters listed below, I I fall into busybox and cannot boot successfully. What do I do now? > > My configuration is > Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz > 7983 MiB > running SELinux > Raid is a simple stripping (level 0) for speed > I have set the noautodetect and nodmraid parameters for the kernel We would need lots more details to be able to help. I assume you have given up on the old data - is that correct? Sorry about that. Do you just have the one RAID (the RAID0)? Is it for the root filesystem or something else? Maybe there is something in your initrd that is causing confusion. zcat /boot/initrd | cpio -idv will explode it for you. Is there an 'mdadm.conf' in there? What does it contain? Maybe just run mkinitrd (or whatever the Ubuntu command is - mkinitramfs maybe). That might fix it. Are there any error messages during boot? You might need to get Ubuntu specific help as different distros have quite different boot sequences. NeilBrown
Attachment:
signature.asc
Description: PGP signature
