> On Sunday August 4, faasen@xs4all.nl wrote:
>> Hi,
>>
>> i ran into a very strange problem.
>>
>> I booted my system this morning only to discover that I could no
>> longer mount my /dev/md0. I shut down my system last night without any
>> problems.
>>
>> The only way I can mount it again is with mdadm --assembly /dev/md0
>> /dev/sda9 /dev/sdb1 /dev/sdc1
>> I have to do this every time the system is rebooted.
>>
>> The distribution is debian unstable
>> mdadm - v1.0.1 - 20 May 2002
>> raidstart v0.3d compiled for md raidtools-0.90
>>
>> Is there any way to permanently fix this error?
>> How did this happen, as i didn't do anything i can see related to
>> this?
>
> Sounds to me like something changed in debian. 'unstable' is like that.
I can imagine you feel like that, but this was not the case.
> It would appear that you aren't using autodetect partitions, so you need
> to have either 'raidstart -a' or 'mdadm -As' run at boot time, with
> appropriate config files: /etc/raidtab or /etc/mdadm.conf.
> Check your rc scripts and config files, decide which one you want to
> use, and make sure the right script is enabled and the right
> configfile has appropriate information.
>
Well, that's just it, I was/am using autodetect partitions.
if I run raidstart -a or raidstart /dev/md0 it says something like "
strarting /dev/md0 succes!". However when I try to mount it it fails, only
the mdmadm command seems to work?
Tommy
> NeilBrown
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:30 EST