From: Konstantin Kudin <konstantin_kudin@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Strange boot with multiple identical disks
Date: Thu, 12 Feb 2004 11:28:48 -0800 (PST) [thread overview]
Message-ID: <20040212192848.29083.qmail@web21204.mail.yahoo.com> (raw)
Hi everybody,
Here is the issue. A redhat 9 linux system had 2
drives, /hda and /hdb. Then /hda started developing
bad clusters {UncorrectableError}, so I got an
identical warranty replacement drive.
Then I hooked up the new drive as /hdc, and did a
sector by sector copy {dd if=/dev/hda of=/dev/hdc
conv=noerror,sync} Overall, I got ~2k of bad 512B
sectors.
Then I swaped the fresh one to /hda, and put aside
the failing one. I booted, did fsck on all partitions
and also raids, and things came up fine. So far so
good.
Now I am trying to add the failing one as /hdc, and
boot. Linux starts to display all kinds of weird
messages, and thinks that / partition was shut down
uncleanly. I just hit "reset". Then I disable /hdc via
the boot option hdc=noprobe, and things boot fine. If
I try to disable raid via raid=noautodetect, the bunch
of errors still appears and the boot is no go. Done
this several times, without /hdc things are fine, with
- all kinds of issues.
What is the problem for linux to boot on /hda when
/hdc is detected and has almost identical setup?
Where does it read all the garbage that starts to
screw up the boot process when /hdc is detected? I'd
like to hook up /hdc to wipe out the data there. The
drive is huge, so I'd rather wipe it out while working
then under other circumstances.
Thanks!
Konstantin
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
next reply other threads:[~2004-02-12 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 19:28 Konstantin Kudin [this message]
2004-02-12 19:38 ` Valdis.Kletnieks
2004-02-12 20:04 ` Konstantin Kudin
2004-02-12 20:08 ` Dave Kleikamp
2004-02-13 15:31 ` Ricky Beam
2004-02-15 3:05 ` Bill Davidsen
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=20040212192848.29083.qmail@web21204.mail.yahoo.com \
--to=konstantin_kudin@yahoo.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®