linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Micah Anderson <micah@riseup.net>
To: linux-raid@vger.kernel.org
Subject: Unable to read superblock
Date: Wed, 17 Jul 2002 20:34:04 -0700	[thread overview]
Message-ID: <20020718033404.GR17829@riseup.net> (raw)

I'm confused, I've done this hundreds of times, but for some reason it
doesn't work now, I must be missing something, can someone poke me in
the eye with it?

I've currently got 2.2.20 with raid-1 devices booting fine:

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md5                139945     28617    104103  22% /
/dev/md0                  7683      4253      3034  58% /boot
/dev/hda5                69904        15     66280   0% /tmp
/dev/md4               1430864    933128    425048  69% /usr
/dev/md3               1438768    392848    972832  29% /var
/dev/md2              35990024   3980340  30181492  12% /var/spool
/dev/md1                233225    160199     60985  72% /home

cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [translucent] 
read_ahead 1024 sectors
md0 : active raid1 hdc2[0] hda2[1] 7936 blocks [2/2] [UU]
md5 : active raid1 hdc3[0] hda3[1] 144512 blocks [2/2] [UU]
md6 : active raid1 hdc5[0] hda5[1] 72192 blocks [2/2] [UU]
md4 : active raid1 hdc6[0] hda6[1] 1453760 blocks [2/2] [UU]
md3 : active raid1 hdc7[0] hda7[1] 1461760 blocks [2/2] [UU]
md2 : active raid1 hdc9[0] hda9[1] 36563840 blocks [2/2] [UU]
md1 : active raid1 hdc10[0] hda10[1] 240832 blocks [2/2] [UU]
unused devices: <none>

I had lilo set for:

boot=/dev/md0
root=/dev/md5
image=/boot/vmlinuz-2.2.20RAID
        label=RAID
        read-only
        alias=4
		
When I installed 2.4.18, all of a sudden I can't boot, EXT2-fs: unable
to read superblock. Yes, I selected all the RAID options on kernel
compile.

What the heck?

Ok, so I think it is a lilo problem, I wanted to toss lilo and put
grub on anyway:

My grub is set for:
kernel (hd0,1)/vmlinuz-2.2.20RAID root=/dev/md5

If I have grub set to:

kernel (hd0,1)/vmlinuz-2.4.18 root=/dev/md5

again with the unable to read superblock stuff....

if I have it set to:
kernel (hd0,1)/vmlinuz-2.4.18 root=/dev/hda3

request module [block major 3]: root fs not mounted
cannot open root device hda3
please append correct root= boot option

AGGGH?!

Thanks,
Micah

             reply	other threads:[~2002-07-18  3:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  3:34 Micah Anderson [this message]
2002-07-18 23:58 ` Unable to read superblock Micah Anderson
2002-07-22 23:45 ` Micah Anderson
2002-07-23  2:52   ` Ross Vandegrift
2002-07-23 21:01     ` Micah Anderson
2002-07-23  3:57   ` Neil Brown

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=20020718033404.GR17829@riseup.net \
    --to=micah@riseup.net \
    --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).