From: Guest section DW <dwguest@win.tue.nl>
To: "C. Linus Hicks" <lhicks@nc.rr.com>, <Remy.Card@linux.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: mkfs wrote to wrong partition
Date: Tue, 7 Aug 2001 02:59:13 +0200 [thread overview]
Message-ID: <20010807025913.A13266@win.tue.nl> (raw)
In-Reply-To: <006a01c11dce$b4338bb0$0a0a0a0a@k-6_iii-400.mindspring.com>
In-Reply-To: <006a01c11dce$b4338bb0$0a0a0a0a@k-6_iii-400.mindspring.com>; from C. Linus Hicks on Sun, Aug 05, 2001 at 12:50:16PM -0400
On Sun, Aug 05, 2001 at 12:50:16PM -0400, C. Linus Hicks wrote:
> The point of the following exercise was to move from a single CPU 400Mhz
> system to a dual 600Mhz and from an IDE disk to SCSI. I already had Redhat
> 7.1 with a 2.4.6 kernel running on the dual 600 and was replacing it with
> the system from the 400Mhz IDE system. All operations were performed on the
> dual 600.
>
> While running the system booted with root=/dev/sda2 I made partitions on
> /dev/sdb just like on /dev/sda, then copied all files over. I modified the
> lilo.conf in /etc on /dev/sda2 to have boot=/dev/sdb and set the
> root=/dev/sdb2 for each image. I ran lilo then booted the system.
>
> The system looked like I expected it to: mount showed /dev/sdb2 mounted as
> the root filesystem.
Note that this does not mean a thing:
If /etc/mtab is a link to /proc/mounts (bad idea) then the root fs is
usually just called /dev/root. Otherwise, mount will guess at the
appropriate name for the root filesystem by taking the one in /etc/fstab.
So, when mount showed /dev/sdb2 as root, this meant that you had
changed the root entry in /etc/fstab.
Probably you forgot to run lilo and booted the old kernel.
next prev parent reply other threads:[~2001-08-07 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 16:50 C. Linus Hicks
2001-08-07 0:59 ` Guest section DW [this message]
2001-08-06 15:15 C. Linus Hicks
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=20010807025913.A13266@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=Remy.Card@linux.org \
--cc=lhicks@nc.rr.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®