On Tue, 2007-06-12 at 17:55 +1000, Steve Granger wrote:
> david wrote:
> > On Tue, 2007-06-12 at 17:11 +1000, Steve Granger wrote:
> >> Hi David,
> >>
> >> Removing mdadm is okay, no hotplug devices use it and it only required
> >> if you have a software RAID device/setup.
> >>
> >> >From the bug report that you posted, this is a new "feature" that gets
> >> you to make sure the mdadm.conf file is the same as the out of a mdadm
> >> scan. This causes the failure of your initrd creation as initrd builds
> >> depend on mdadm being happy (because you can include modules related to
> >> mdadm to be built into your initrd to bring up hardware devices before
> >> mdadm tries to create md devices) before they are built.
> >>
> > 
> > 
> > yes... I removed, but then re-installed because of all the nasty
> > warnings I was getting. I'm not entirely sure where I'm at now - not
> > quite game to re-boot just yet. Nothing is simple :(
> > 
> > 
> 
> So you've removed mdadm?
> 
> what happens when you run dpkg-configure -a? does the install process
> finish?
> 
> run
> 
> update-initramfs -k all -u
> 
> to get your initrd to build again, it should do this without complaining
>  now. Seems like a few people in the bug thread ignored the error,
> rebooted and didn't have their systems come up... Good way to learn how
> to use a rescue CD...
> 

Ha! rescue CD's are great things to NOT need ;-) I had some fstab
disasters and learned about rescue CD's then.

I'm doing dpkg-reconfigure -a while I'm writing this. I did get this
message:

update-initramfs: Generating /boot/initrd.img-2.6.20-16-386
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.

then later:

update-initramfs: Generating /boot/initrd.img-2.6.20-16-386
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.20-16-386
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.


Bear in mind that I apt-get removed mdadm but then apt-get installed it
again because the error messages scared me ;-)


Oh what fun when you don't know what you are doing ;-)

> >> --
> >> Steve
> >>
> >> (sorry, just hit reply before thinking.. must be from my intense three
> >> day session on "forgetting all about work") :-}
> >>
> >> david wrote:
> >>> I'm getting error messages about mdadm. There are suggestions that this
> >>> can be removed if not using RAID (I don't). [1]
> >>>
> >>> Are there any other issues with removing it? EG: hotplug devices like
> >>> USB storage devices etc. Google isn't really making this clear.
> >>>
> >>> thanks...
> >>>
> >>> David
> >>>
> >>>
> >>> p[1]
> >>> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/98911
> >>>
> >>
> >> ______________________________________________________________________
> >> This email has been scanned by the MessageLabs Email Security System.
> >> For more information please visit http://www.messagelabs.com/email 
> >> ______________________________________________________________________
> > 
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> 

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to