Hi all
Why using command line? I presume because this leaves the administrator a
last way to influence the system. The old technique of "just search and use,
don't ask" may not be good if you crash the system by searching a not
working disk.
If you boot with command line automatic and face this kind of hang you can
change command line next time and don't need to unplug the faulty drive...
bye
Ulf
-----
Dipl.-Ing. Ulf Dambacher
Institut fur Werkzeugmaschinen und Betriebstechnik, Universitat Karlsruhe
Institute for machine tools and production science, university of Karlsruhe, Germany
Tel.: +49 721 608 4297
Fax: +49 721 69 91 53
[EMAIL PROTECTED]
http://www-wbk.mach.uni-karlsruhe.de
-----Ursprungliche Nachricht-----
Von: Mr. James W. Laferriere [SMTP:[EMAIL PROTECTED]]
Gesendet am: Freitag, 6. April 2001 16:47
An: Dambacher
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Betreff: Re: AW: Raid 1 autodection problems
Hello Ulf & All,
On Fri, 6 Apr 2001, Dambacher wrote:
> Hi Alexander
> I had the same problem with autodetect. It seems that they turned of the
> partitition detection mode in favor of a kernel command line. Look for
> ./linux/Documentation/md.txt
> Its something like md=<dev.nr>,<raidlevel>,<dev1>,<dev2>,<dev3>,...
> for new kernel.
Ulf, Thank you for the heads up .
If I remember correctly there is still some limit on the lilo/...
boot command line length ? Yes/No
What is the kicker in having to remove the autodetection ?
Tia , JimL
> -----Ursprungliche Nachricht-----
> Von: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Gesendet am: Freitag, 6. April 2001 12:49
> An: [EMAIL PROTECTED]
> Betreff: Raid 1 autodection problems
> Hi,
> I have a problem with autodection of RAID 1 arrays.
> I am running SuSE Linux 7.1 with an of-the-shelf kernel 2.4.3, where
> aic7xxx and qlogicfc are loaded as modules via initrd.
> I have 2 Raid 1 arrays configured:
> raiddev /dev/md0
...snip...
> The partition type for all partitions is set to 0xfd.
> The arrays work fine if started with raidstart /dev/md0 and raidstart
> /dev/md1.
> They are not autostarted, however, during system start. I tried both
> compiling
> md support into the kernel and as module.
> Here is what I see in /var/log/boot.msg
> ....
> <5>Trying to unmount old root ... okay
> <4>Freeing unused kernel memory: 116k freed
> <6>Adding Swap: 136512k swap-space (priority -1)
> <6>md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> <4>md.c: sizeof(mdp_super_t) = 4096
> <4>EXT2-fs: unable to read superblock
> <4>EXT2-fs: unable to read superblock
> (AW) here the kernel tries to mount /dev/md0 and /dev/md1
> Kernel logging (ksyslog) stopped.
> ....
> Can somebody help me?
> Many thanks in advance ...
> Alexander Warmuth
+----------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | 25416 22nd So | Give me Linux |
| [EMAIL PROTECTED] | DesMoines WA 98198 | only on AXP |
+----------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
