From: Alain Williams <addw-5g5TjK4KYV/QXOPxS62xeg@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Help needed on hardware change
Date: Wed, 18 Dec 2013 17:00:31 +0000 [thread overview]
Message-ID: <20131218170030.GA16342@phcomp.co.uk> (raw)
I moved hard disks into a new machine. Previously when I have done this I just
booted off CD, ran mkinitrd in a chrooted file system to make a new initrd in /boot.
I did that, rebooted and straight after the grub prompt expires (ie the kernel
loaded) the monitor is put into some graphics mode (no characters/text is
visible, just horisontal streaks) and the system stops with caps lock & scroll
lock flashing.
I (as a temporary measure) installed another SATA disk and installed a small
system there (same distro version). It worked as expected.
I copied the /boot/initramfs... over into /boot on the original disks and if I
use that - it all works. I rebuild using dracut and it fails as described above.
I notice that the /boot/initramfs* files are very different sizes:
15M the one that works - new install to temp disk
23M the one that fails - rebuilt with dracut
What can I do to make this work ? This has been a few weeks on & off.
The old hardware was 32 bit intel something, the new is 64 bit AMD. There are
prob lots of other changes, but I don't think that the details matter too much -
I should be able to just rebuild the initrd.
The Operating system is CentOS 6.5. Kernel 2.6.32-358
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
#include <std_disclaimer.h>
reply other threads:[~2013-12-18 17:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131218170030.GA16342@phcomp.co.uk \
--to=addw-5g5tjk4kyv/qxopxs62xeg@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.