From: "Chris Evans" <chris1@psyctc.org>
To: debian-user@lists.debian.org, linux-raid@vger.kernel.org
Subject: Re: md: can not impport hdb1, has active inodes!
Date: Wed, 03 Mar 2004 16:54:28 -0000 [thread overview]
Message-ID: <40460DC4.10744.659B232@localhost> (raw)
In-Reply-To: <200403030336.51772.maarten@vbvb.nl>
I thought I'd got this all cracked in the early hours of this
morning. I _think_ I'd been putting boot=/dev/hda1 when I tried to
write the revised lilo config to the MBR and perhaps that messed up
hdb. I don't know, anyway, I started again, did everything in that
howto pretty much to the letter and this time, after shifting boot to
/dev/hdc and rebooting, I could add /dev/hdb1. However, lilo would
not let me use a raid-extra-boot line and when I rebooted, the system
hung right at the start.
I moved hdb1 to hda1 and started again, this time it's all worked
except for boot=/dev/md0 and the raid-extra-boot. Now lilo allows
these and says it's written to both MBRs, but when I reboot lilo gets
to the first twenty or so of the dots after "Loading Linux" and hangs
there ... resolutely.
A lot of pratting around with rescuing from the installation CD (must
work out how to burn a rescue boot CDROM) and I am back to being able
to get everything find if I boot from boot=/dev/hdc with
root=/dev/md0 ... and I think I'll give up here as I must go back to
doing my real job and having a life. If anyone can tell me what
might be neeeded (I haven't tried things like bios=0x80 lines) I may
find the energy to try them but not if this machine has become my
working firewall!
So I'm left thinking there's something, perhaps idiosyncratic to some
BIOS or HDs or whatever, that means some of us have real problems
writing LILO boot instructions to the two drives in a RAID1 boot
array.
I've leflt Maarten's listing of a SuSE lilo.conf to see if anyone has
ideas.
Thank everyone,
Chris
> Neil had some interesting points, but in the meantime here's my
> working lilo.conf (which was written by the SuSE installer) in case it
> helps you:
>
> boot = /dev/hda
> change-rules
> reset
> default = linux
> disk=/dev/hda
> bios=0x80
> disk=/dev/hdc
> bios=0x81
> lba32
> prompt
> read-only
> timeout = 80
>
> image = /boot/vmlinuz
> label = linux
> initrd = /boot/initrd
> root = /dev/md0
>
>
> Greetings,
> Maarten
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
PSYCTC: Psychotherapy, Psychology, Psychiatry, Counselling
and Therapeutic Communities; practice, research,
teaching and consultancy.
Chris Evans & Jo-anne Carlyle
http://psyctc.org/ Email: chris@psyctc.org
next prev parent reply other threads:[~2004-03-03 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 22:17 md: can not impport hdb1, has active inodes! Chris Evans
2004-03-02 23:24 ` Cameron Moore
2004-03-03 0:36 ` Chris Evans
2004-03-02 23:40 ` Neil Brown
2004-03-03 0:36 ` Chris Evans
2004-03-03 1:04 ` Neil Brown
2004-03-03 1:13 ` Chris Evans
2004-03-03 1:24 ` Neil Brown
2004-03-03 9:11 ` Chris Evans
2004-03-03 15:36 ` Paul Clements
2004-03-04 18:56 ` Juri Haberland
2004-03-03 1:11 ` Maarten J H van den Berg
2004-03-03 1:20 ` Chris Evans
2004-03-03 2:36 ` Maarten J H van den Berg
2004-03-03 16:54 ` Chris Evans [this message]
[not found] ` <200403031109.17348.jguerin@cso.atmel.com>
2004-03-03 22:09 ` Chris Evans
2004-03-04 2:08 ` Maarten J H van den Berg
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=40460DC4.10744.659B232@localhost \
--to=chris1@psyctc.org \
--cc=debian-user@lists.debian.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).