From: Thomas Steudten <alpha@steudten.com>
To: rob <rob@fantinibakery.com>
Cc: alexander.weber@pta.de, linux-raid@vger.kernel.org
Subject: Re: RAID1-Device won't survive reboot
Date: Thu, 09 Oct 2003 14:00:28 +0200 [thread overview]
Message-ID: <3F854DDC.6060200@steudten.com> (raw)
In-Reply-To: <3F8483CE.2070309@fantinibakery.com>
I think the partition is not marked with type fd: like
mime: It must be type "fd"
[1021] (1) # fdisk -l /dev/sda
Disk /dev/sda: 64 heads, 32 sectors, 35003 cylinders
Units = cylinders of 2048 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 8676 8884208 fd Linux raid autodetect
/dev/sda2 8677 35003 26958848 83 Linux
rob wrote:
> I'm not familiar with SuSE 8.2, but here are some hints:
>
> -is it possible that either the mount of md0 is getting done before
> md0 is assembled, or hdb1 is getting mounted directly? check df -v
> right after boot.
>
>>
next prev parent reply other threads:[~2003-10-09 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 15:25 RAID1-Device won't survive reboot alexander.weber
2003-10-08 21:38 ` rob
2003-10-09 12:00 ` Thomas Steudten [this message]
2003-10-09 12:16 ` rob
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=3F854DDC.6060200@steudten.com \
--to=alpha@steudten.com \
--cc=alexander.weber@pta.de \
--cc=linux-raid@vger.kernel.org \
--cc=rob@fantinibakery.com \
/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).