From: Guillaume Filion <gfk@logidac.com>
To: linux-raid@vger.kernel.org
Subject: Re: Crooked raid
Date: Wed, 16 Nov 2005 18:55:31 -0500 [thread overview]
Message-ID: <437BC6F3.5070704@logidac.com> (raw)
In-Reply-To: <437B60B3.5030601@logidac.com>
Guillaume Filion a écrit :
> Andrew Burgess a écrit :
>> Do you recall why it didn't want to boot?
I retried to boot and here's the error that I'm getting:
EXT3-fs: unable to read superblock
cramfs: wrong magic
>> Do you know why the system sometimes says
>> ide/host0/bus1/target0/lun0/part2 and
>> sometimes says hd[cg]2 ? Its confusing...
>
> No, that's something that confuses me too. I installed devfsd sometime
> in the past but deinstalled it because I didn't need it.
I decided to resintall devfsd to correct that problem. I think it
helped, at least I'm seeing ide/host0/... everywhere now.
One thing that's strange is that mdadm doesn't seem to recognise
/dev/md0 (or /dev/md/0) but it's clearly mounted and working...
gfk@ali:~$ sudo mdadm -D /dev/md0
mdadm: md device /dev/md0 does not appear to be active.
gfk@ali:~$ mount
/dev/md/0 on / type ext3 (rw,errors=remount-ro)
/dev/ide/host2/bus0/target0/lun0/part1 on /boot type ext2
(rw,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
gfk@ali:~$ cat /proc/mdstat
Personalities : [raid1]
read_ahead not set
md0 : inactive ide/host2/bus1/target0/lun0/part2[0]
0 blocks
unused devices: <none>
>> And any raid autodetect partitions around?
>> fdisk -l | grep raid
>
> fdisk -l doesn't output anything.
After reinstalling devfds, fdisk -l is working:
gfk@ali:~$ sudo fdisk -l | fgrep raid
/dev/ide/host2/bus1/target0/lun0/part2 * 1276 155061
77508144 fd Linux raid autodetect
/dev/ide/host0/bus1/target0/lun0/part2 * 1276 155061
77508144 fd Linux raid autodetect
--
Guillaume Filion, ing. jr
Logidac Tech., Beaumont, Québec, Canada - http://logidac.com/
PGP Key and more: http://guillaume.filion.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-11-16 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 15:41 Crooked raid Andrew Burgess
2005-11-16 16:39 ` Guillaume Filion
2005-11-16 23:55 ` Guillaume Filion [this message]
2005-11-21 3:50 ` Crooked raid [solved] Guillaume Filion
-- strict thread matches above, loose matches on Subject: below --
2005-11-16 16:07 Crooked raid Andrew Burgess
2005-11-15 18:44 Andrew Burgess
2005-11-15 23:24 ` Guillaume Filion
2005-11-15 15:20 Guillaume Filion
2005-11-15 23:07 ` Neil Brown
2005-11-16 13:47 ` Guillaume Filion
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=437BC6F3.5070704@logidac.com \
--to=gfk@logidac.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.