On Sun, 2007-05-13 at 18:44 +0200, Robert Millan wrote: 
> > I experimented some more. At the command prompt I entered 'insmod raid'
> > and got the message 'error: out of disk'. I assume that is because the
> > partition containing my RAID1 array extends past the area readably by
> > BIOS functions. However, I was able to ignore the message: if I then ran
> > 'ls', '(md0)' showed up in the list of devices just fine!
> 
> How strange.  If you can't access the disk, you wouldn't be able to insmod
> anything.  Can you check the following (before running 'insmod raid'):
> 
>   - That raid is not already loaded (with lsmod).

Check.

>   - The 'prefix' variable (with set).

It's set to '(hd1,2)/boot/grub', which corresponds to one of the disks
in my raid1 set.

>  - Whether you can access (ls) the directory pointed to by 'prefix'.

Yup, I guess that's where the modules are being loaded from.

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to