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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
