Thread: [SSI-users] OpenSSI on RAID Level 1 in Debian possible?
Brought to you by:
brucewalker,
rogertsang
From: Jonathan T. <jon...@ut...> - 2005-04-28 00:51:29
|
Hi, Is it possible to have the boot filesystem of a small openssi cluster raid level 1? Using the debian sarge installation CD I set up a raid1 drive that contains the whole system. /dev/md0 that is. Then I followed the steps from the debian install document (which I have working on another non RAID based cluster). After apt-get install openssi I reboot to the new kernel but when init starts I get Error: /usr/something/bin/chroot not found. If I reboot with the normal debian 2.4.27 kernel everything works. Is this due to lack of support for raid in the openssi kernel? Thanks for any help. Sincerely, Jon Taylor. UofT Botany Bioinformatics Lab |
From: Jonathan T. <jon...@ut...> - 2005-04-28 01:09:09
|
The md module seems to be failing to set up the md0 device. It tries to insmod md-personality-3 but fails to find the module, then gives up on the md0 device. Is this module not in the kernel? :( Any solutions greatly appreciated. J. On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: > Hi, > > Is it possible to have the boot filesystem of a small openssi cluster > raid level 1? > > Using the debian sarge installation CD I set up a raid1 drive that > contains the whole system. /dev/md0 that is. > > Then I followed the steps from the debian install document (which I have > working on another non RAID based cluster). After apt-get install > openssi I reboot to the new kernel but when init starts I get > Error: /usr/something/bin/chroot not found. > > If I reboot with the normal debian 2.4.27 kernel everything works. Is > this due to lack of support for raid in the openssi kernel? > > Thanks for any help. > > Sincerely, > Jon Taylor. > UofT Botany Bioinformatics Lab > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > |
From: John B. <joh...@hp...> - 2005-04-28 01:19:05
|
Jonathan Taylor wrote: > The md module seems to be failing to set up the md0 device. It tries to > insmod md-personality-3 but fails to find the module, then gives up on > the md0 device. Is this module not in the kernel? :( > > Any solutions greatly appreciated. > > J. It is possible raid support was broken by our changes, because I don't think anyone has tested them on a md-raid system. As a workaround, you might try adding the md modules to /etc/mkinitrd/modules; that might work. Can you please tell us what version you are using? John > > On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: > >>Hi, >> >>Is it possible to have the boot filesystem of a small openssi cluster >>raid level 1? >> >>Using the debian sarge installation CD I set up a raid1 drive that >>contains the whole system. /dev/md0 that is. >> >>Then I followed the steps from the debian install document (which I have >>working on another non RAID based cluster). After apt-get install >>openssi I reboot to the new kernel but when init starts I get >>Error: /usr/something/bin/chroot not found. >> >>If I reboot with the normal debian 2.4.27 kernel everything works. Is >>this due to lack of support for raid in the openssi kernel? >> >>Thanks for any help. >> >>Sincerely, >>Jon Taylor. >>UofT Botany Bioinformatics Lab >> >> >> >>------------------------------------------------------- >>SF.Net email is sponsored by: Tell us your software development plans! >>Take this survey and enter to win a one-year sub to SourceForge.net >>Plus IDC's 2005 look-ahead and a copy of this survey >>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix >>_______________________________________________ >>Ssic-linux-users mailing list >>Ssi...@li... >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users >> > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > |
From: Jonathan T. <jon...@ut...> - 2005-04-28 19:23:08
|
Open SSI 1.2.2 On Wed, 2005-04-27 at 18:18 -0700, John Byrne wrote: > Jonathan Taylor wrote: > > The md module seems to be failing to set up the md0 device. It tries to > > insmod md-personality-3 but fails to find the module, then gives up on > > the md0 device. Is this module not in the kernel? :( > > > > Any solutions greatly appreciated. > > > > J. > > It is possible raid support was broken by our changes, because I don't > think anyone has tested them on a md-raid system. As a workaround, you > might try adding the md modules to /etc/mkinitrd/modules; that might work. > > Can you please tell us what version you are using? > > John > > > > > > On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: > > > >>Hi, > >> > >>Is it possible to have the boot filesystem of a small openssi cluster > >>raid level 1? > >> > >>Using the debian sarge installation CD I set up a raid1 drive that > >>contains the whole system. /dev/md0 that is. > >> > >>Then I followed the steps from the debian install document (which I have > >>working on another non RAID based cluster). After apt-get install > >>openssi I reboot to the new kernel but when init starts I get > >>Error: /usr/something/bin/chroot not found. > >> > >>If I reboot with the normal debian 2.4.27 kernel everything works. Is > >>this due to lack of support for raid in the openssi kernel? > >> > >>Thanks for any help. > >> > >>Sincerely, > >>Jon Taylor. > >>UofT Botany Bioinformatics Lab > >> > >> > >> > >>------------------------------------------------------- > >>SF.Net email is sponsored by: Tell us your software development plans! > >>Take this survey and enter to win a one-year sub to SourceForge.net > >>Plus IDC's 2005 look-ahead and a copy of this survey > >>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > >>_______________________________________________ > >>Ssic-linux-users mailing list > >>Ssi...@li... > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > >> > > > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Tell us your software development plans! > > Take this survey and enter to win a one-year sub to SourceForge.net > > Plus IDC's 2005 look-ahead and a copy of this survey > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > _______________________________________________ > > Ssic-linux-users mailing list > > Ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > |
From: Jonathan T. <jon...@ut...> - 2005-04-28 20:12:01
|
Hi, I am using openssi 1.2.2 (the latest from apt-get upgrade). I tried adding md and raid1 to /etc/mkinitrd modules and then dpkg-reconfigure kernel-image-ssi...etc to force reconstruction of the initrd. I still have the problem of insmod md-personality-3 failing. From google I see this can be solved in some circumstances by adding to /etc/modules.conf: alias md-personality-3 raid1 Alas this is not helping my case and it still fails. Any ideas or maybe I should go buy a hardware raid solution? Thanks for any help. J. On Wed, 2005-04-27 at 18:18 -0700, John Byrne wrote: > Jonathan Taylor wrote: > > The md module seems to be failing to set up the md0 device. It tries to > > insmod md-personality-3 but fails to find the module, then gives up on > > the md0 device. Is this module not in the kernel? :( > > > > Any solutions greatly appreciated. > > > > J. > > It is possible raid support was broken by our changes, because I don't > think anyone has tested them on a md-raid system. As a workaround, you > might try adding the md modules to /etc/mkinitrd/modules; that might work. > > Can you please tell us what version you are using? > > John > > > > > > On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: > > > >>Hi, > >> > >>Is it possible to have the boot filesystem of a small openssi cluster > >>raid level 1? > >> > >>Using the debian sarge installation CD I set up a raid1 drive that > >>contains the whole system. /dev/md0 that is. > >> > >>Then I followed the steps from the debian install document (which I have > >>working on another non RAID based cluster). After apt-get install > >>openssi I reboot to the new kernel but when init starts I get > >>Error: /usr/something/bin/chroot not found. > >> > >>If I reboot with the normal debian 2.4.27 kernel everything works. Is > >>this due to lack of support for raid in the openssi kernel? > >> > >>Thanks for any help. > >> > >>Sincerely, > >>Jon Taylor. > >>UofT Botany Bioinformatics Lab > >> > >> > >> > >>------------------------------------------------------- > >>SF.Net email is sponsored by: Tell us your software development plans! > >>Take this survey and enter to win a one-year sub to SourceForge.net > >>Plus IDC's 2005 look-ahead and a copy of this survey > >>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > >>_______________________________________________ > >>Ssic-linux-users mailing list > >>Ssi...@li... > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > >> > > > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Tell us your software development plans! > > Take this survey and enter to win a one-year sub to SourceForge.net > > Plus IDC's 2005 look-ahead and a copy of this survey > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > _______________________________________________ > > Ssic-linux-users mailing list > > Ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > |
From: Jonathan T. <jon...@ut...> - 2005-04-29 00:08:16
|
Hmm... I think I have tried almsot everything. It seems that if initrd tried to load md-personality-3 with modprobe instead of insmod then I could get this to work. Alas. ;( Is it possible to somehow downgrade to a working version of openssi + md? I think its a pretty good feature to have mirrored disks for your cluster, just in case of hard drive failure. Thanks for any help, Jon. On Thu, 2005-04-28 at 16:11 -0400, Jonathan Taylor wrote: > Hi, > > I am using openssi 1.2.2 (the latest from apt-get upgrade). I tried > adding md and raid1 to /etc/mkinitrd modules and then dpkg-reconfigure > kernel-image-ssi...etc to force reconstruction of the initrd. I still > have the problem of insmod md-personality-3 failing. From google I see > this can be solved in some circumstances by adding to /etc/modules.conf: > > alias md-personality-3 raid1 > > Alas this is not helping my case and it still fails. Any ideas or maybe > I should go buy a hardware raid solution? > > Thanks for any help. > J. > > On Wed, 2005-04-27 at 18:18 -0700, John Byrne wrote: > > Jonathan Taylor wrote: > > > The md module seems to be failing to set up the md0 device. It tries to > > > insmod md-personality-3 but fails to find the module, then gives up on > > > the md0 device. Is this module not in the kernel? :( > > > > > > Any solutions greatly appreciated. > > > > > > J. > > > > It is possible raid support was broken by our changes, because I don't > > think anyone has tested them on a md-raid system. As a workaround, you > > might try adding the md modules to /etc/mkinitrd/modules; that might work. > > > > Can you please tell us what version you are using? > > > > John > > > > > > > > > > On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: > > > > > >>Hi, > > >> > > >>Is it possible to have the boot filesystem of a small openssi cluster > > >>raid level 1? > > >> > > >>Using the debian sarge installation CD I set up a raid1 drive that > > >>contains the whole system. /dev/md0 that is. > > >> > > >>Then I followed the steps from the debian install document (which I have > > >>working on another non RAID based cluster). After apt-get install > > >>openssi I reboot to the new kernel but when init starts I get > > >>Error: /usr/something/bin/chroot not found. > > >> > > >>If I reboot with the normal debian 2.4.27 kernel everything works. Is > > >>this due to lack of support for raid in the openssi kernel? > > >> > > >>Thanks for any help. > > >> > > >>Sincerely, > > >>Jon Taylor. > > >>UofT Botany Bioinformatics Lab > > >> > > >> > > >> > > >>------------------------------------------------------- > > >>SF.Net email is sponsored by: Tell us your software development plans! > > >>Take this survey and enter to win a one-year sub to SourceForge.net > > >>Plus IDC's 2005 look-ahead and a copy of this survey > > >>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > >>_______________________________________________ > > >>Ssic-linux-users mailing list > > >>Ssi...@li... > > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > >> > > > > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net email is sponsored by: Tell us your software development plans! > > > Take this survey and enter to win a one-year sub to SourceForge.net > > > Plus IDC's 2005 look-ahead and a copy of this survey > > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > > _______________________________________________ > > > Ssic-linux-users mailing list > > > Ssi...@li... > > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > > > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > |
From: Roger T. <rog...@gm...> - 2005-04-29 00:46:04
|
If modprobe works, but insmod doesn't then obviously some modules weren't picked up during mkinitrd. I suppose. Check for dependencies by doing grep raid1 on lsmod after doing a modprobe vs. insmod. Maybe you'll find something. -Roger On 4/28/05, Jonathan Taylor <jon...@ut...> wrote: > Hmm... I think I have tried almsot everything. It seems that if initrd > tried to load md-personality-3 with modprobe instead of insmod then I > could get this to work. Alas. ;( >=20 > Is it possible to somehow downgrade to a working version of openssi + > md? I think its a pretty good feature to have mirrored disks for your > cluster, just in case of hard drive failure. >=20 > Thanks for any help, > Jon. >=20 > On Thu, 2005-04-28 at 16:11 -0400, Jonathan Taylor wrote: > > Hi, > > > > I am using openssi 1.2.2 (the latest from apt-get upgrade). I tried > > adding md and raid1 to /etc/mkinitrd modules and then dpkg-reconfigure > > kernel-image-ssi...etc to force reconstruction of the initrd. I still > > have the problem of insmod md-personality-3 failing. From google I see > > this can be solved in some circumstances by adding to /etc/modules.conf= : > > > > alias md-personality-3 raid1 > > > > Alas this is not helping my case and it still fails. Any ideas or mayb= e > > I should go buy a hardware raid solution? > > > > Thanks for any help. > > J. > > > > On Wed, 2005-04-27 at 18:18 -0700, John Byrne wrote: > > > Jonathan Taylor wrote: > > > > The md module seems to be failing to set up the md0 device. It tri= es to > > > > insmod md-personality-3 but fails to find the module, then gives up= on > > > > the md0 device. Is this module not in the kernel? :( > > > > > > > > Any solutions greatly appreciated. > > > > > > > > J. > > > > > > It is possible raid support was broken by our changes, because I don'= t > > > think anyone has tested them on a md-raid system. As a workaround, yo= u > > > might try adding the md modules to /etc/mkinitrd/modules; that might = work. > > > > > > Can you please tell us what version you are using? > > > > > > John > > > > > > > > > > > > > > On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: > > > > > > > >>Hi, > > > >> > > > >>Is it possible to have the boot filesystem of a small openssi clust= er > > > >>raid level 1? > > > >> > > > >>Using the debian sarge installation CD I set up a raid1 drive that > > > >>contains the whole system. /dev/md0 that is. > > > >> > > > >>Then I followed the steps from the debian install document (which I= have > > > >>working on another non RAID based cluster). After apt-get install > > > >>openssi I reboot to the new kernel but when init starts I get > > > >>Error: /usr/something/bin/chroot not found. > > > >> > > > >>If I reboot with the normal debian 2.4.27 kernel everything works. = Is > > > >>this due to lack of support for raid in the openssi kernel? > > > >> > > > >>Thanks for any help. > > > >> > > > >>Sincerely, > > > >>Jon Taylor. > > > >>UofT Botany Bioinformatics Lab > > > >> > > > >> > > > >> > > > >>------------------------------------------------------- > > > >>SF.Net email is sponsored by: Tell us your software development pla= ns! > > > >>Take this survey and enter to win a one-year sub to SourceForge.net > > > >>Plus IDC's 2005 look-ahead and a copy of this survey > > > >>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=3D10= 5hix > > > >>_______________________________________________ > > > >>Ssic-linux-users mailing list > > > >>Ssi...@li... > > > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > >> > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net email is sponsored by: Tell us your software development pla= ns! > > > > Take this survey and enter to win a one-year sub to SourceForge.net > > > > Plus IDC's 2005 look-ahead and a copy of this survey > > > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=3D10= 5hix > > > > _______________________________________________ > > > > Ssic-linux-users mailing list > > > > Ssi...@li... > > > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > > > > > > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Tell us your software development plans! > > Take this survey and enter to win a one-year sub to SourceForge.net > > Plus IDC's 2005 look-ahead and a copy of this survey > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=3D105hix > > _______________________________________________ > > Ssic-linux-users mailing list > > Ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=3D105hix > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > |
From: Jonathan T. <jon...@ut...> - 2005-04-29 01:01:44
|
Hmm... raid1 has no dependencies. insmod fails with the error that it cannot find md-personality-3 whereas modprobe seems to consul modules.conf, notices the alias md-personality-3 raid1 and instead uses the raid1 module which does exist in the initrd. Thanks for any help though... This is really getting me down :( J On Thu, 2005-04-28 at 20:45 -0400, Roger Tsang wrote: > If modprobe works, but insmod doesn't then obviously some modules > weren't picked up during mkinitrd. I suppose. Check for dependencies > by doing grep raid1 on lsmod after doing a modprobe vs. insmod. Maybe > you'll find something. > > -Roger > > > On 4/28/05, Jonathan Taylor <jon...@ut...> wrote: > > Hmm... I think I have tried almsot everything. It seems that if initrd > > tried to load md-personality-3 with modprobe instead of insmod then I > > could get this to work. Alas. ;( > > > > Is it possible to somehow downgrade to a working version of openssi + > > md? I think its a pretty good feature to have mirrored disks for your > > cluster, just in case of hard drive failure. > > > > Thanks for any help, > > Jon. > > > > On Thu, 2005-04-28 at 16:11 -0400, Jonathan Taylor wrote: > > > Hi, > > > > > > I am using openssi 1.2.2 (the latest from apt-get upgrade). I tried > > > adding md and raid1 to /etc/mkinitrd modules and then dpkg-reconfigure > > > kernel-image-ssi...etc to force reconstruction of the initrd. I still > > > have the problem of insmod md-personality-3 failing. From google I see > > > this can be solved in some circumstances by adding to /etc/modules.conf: > > > > > > alias md-personality-3 raid1 > > > > > > Alas this is not helping my case and it still fails. Any ideas or maybe > > > I should go buy a hardware raid solution? > > > > > > Thanks for any help. > > > J. > > > > > > On Wed, 2005-04-27 at 18:18 -0700, John Byrne wrote: > > > > Jonathan Taylor wrote: > > > > > The md module seems to be failing to set up the md0 device. It tries to > > > > > insmod md-personality-3 but fails to find the module, then gives up on > > > > > the md0 device. Is this module not in the kernel? :( > > > > > > > > > > Any solutions greatly appreciated. > > > > > > > > > > J. > > > > > > > > It is possible raid support was broken by our changes, because I don't > > > > think anyone has tested them on a md-raid system. As a workaround, you > > > > might try adding the md modules to /etc/mkinitrd/modules; that might work. > > > > > > > > Can you please tell us what version you are using? > > > > > > > > John > > > > > > > > > > > > > > > > > > On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: > > > > > > > > > >>Hi, > > > > >> > > > > >>Is it possible to have the boot filesystem of a small openssi cluster > > > > >>raid level 1? > > > > >> > > > > >>Using the debian sarge installation CD I set up a raid1 drive that > > > > >>contains the whole system. /dev/md0 that is. > > > > >> > > > > >>Then I followed the steps from the debian install document (which I have > > > > >>working on another non RAID based cluster). After apt-get install > > > > >>openssi I reboot to the new kernel but when init starts I get > > > > >>Error: /usr/something/bin/chroot not found. > > > > >> > > > > >>If I reboot with the normal debian 2.4.27 kernel everything works. Is > > > > >>this due to lack of support for raid in the openssi kernel? > > > > >> > > > > >>Thanks for any help. > > > > >> > > > > >>Sincerely, > > > > >>Jon Taylor. > > > > >>UofT Botany Bioinformatics Lab > > > > >> > > > > >> > > > > >> > > > > >>------------------------------------------------------- > > > > >>SF.Net email is sponsored by: Tell us your software development plans! > > > > >>Take this survey and enter to win a one-year sub to SourceForge.net > > > > >>Plus IDC's 2005 look-ahead and a copy of this survey > > > > >>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > > > >>_______________________________________________ > > > > >>Ssic-linux-users mailing list > > > > >>Ssi...@li... > > > > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net email is sponsored by: Tell us your software development plans! > > > > > Take this survey and enter to win a one-year sub to SourceForge.net > > > > > Plus IDC's 2005 look-ahead and a copy of this survey > > > > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > > > > _______________________________________________ > > > > > Ssic-linux-users mailing list > > > > > Ssi...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net email is sponsored by: Tell us your software development plans! > > > Take this survey and enter to win a one-year sub to SourceForge.net > > > Plus IDC's 2005 look-ahead and a copy of this survey > > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > > _______________________________________________ > > > Ssic-linux-users mailing list > > > Ssi...@li... > > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Tell us your software development plans! > > Take this survey and enter to win a one-year sub to SourceForge.net > > Plus IDC's 2005 look-ahead and a copy of this survey > > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix > > _______________________________________________ > > Ssic-linux-users mailing list > > Ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > |
From: John B. <joh...@hp...> - 2005-04-29 02:24:13
|
Jonathan Taylor wrote: > Hmm... raid1 has no dependencies. insmod fails with the error that it > cannot find md-personality-3 whereas modprobe seems to consul > modules.conf, notices the alias md-personality-3 raid1 and instead uses > the raid1 module which does exist in the initrd. > > Thanks for any help though... This is really getting me down :( > > J Bruce is supposed to have asked someone to look into this. John Byrne > > On Thu, 2005-04-28 at 20:45 -0400, Roger Tsang wrote: > >>If modprobe works, but insmod doesn't then obviously some modules >>weren't picked up during mkinitrd. I suppose. Check for dependencies >>by doing grep raid1 on lsmod after doing a modprobe vs. insmod. Maybe >>you'll find something. >> >>-Roger >> >> >>On 4/28/05, Jonathan Taylor <jon...@ut...> wrote: >> >>>Hmm... I think I have tried almsot everything. It seems that if initrd >>>tried to load md-personality-3 with modprobe instead of insmod then I >>>could get this to work. Alas. ;( >>> >>>Is it possible to somehow downgrade to a working version of openssi + >>>md? I think its a pretty good feature to have mirrored disks for your >>>cluster, just in case of hard drive failure. >>> >>>Thanks for any help, >>>Jon. >>> >>>On Thu, 2005-04-28 at 16:11 -0400, Jonathan Taylor wrote: >>> >>>>Hi, >>>> >>>>I am using openssi 1.2.2 (the latest from apt-get upgrade). I tried >>>>adding md and raid1 to /etc/mkinitrd modules and then dpkg-reconfigure >>>>kernel-image-ssi...etc to force reconstruction of the initrd. I still >>>>have the problem of insmod md-personality-3 failing. From google I see >>>>this can be solved in some circumstances by adding to /etc/modules.conf: >>>> >>>>alias md-personality-3 raid1 >>>> >>>>Alas this is not helping my case and it still fails. Any ideas or maybe >>>>I should go buy a hardware raid solution? >>>> >>>>Thanks for any help. >>>>J. >>>> >>>>On Wed, 2005-04-27 at 18:18 -0700, John Byrne wrote: >>>> >>>>>Jonathan Taylor wrote: >>>>> >>>>>>The md module seems to be failing to set up the md0 device. It tries to >>>>>>insmod md-personality-3 but fails to find the module, then gives up on >>>>>>the md0 device. Is this module not in the kernel? :( >>>>>> >>>>>>Any solutions greatly appreciated. >>>>>> >>>>>>J. >>>>> >>>>>It is possible raid support was broken by our changes, because I don't >>>>>think anyone has tested them on a md-raid system. As a workaround, you >>>>>might try adding the md modules to /etc/mkinitrd/modules; that might work. >>>>> >>>>>Can you please tell us what version you are using? >>>>> >>>>>John >>>>> >>>>> >>>>> >>>>>>On Wed, 2005-04-27 at 20:50 -0400, Jonathan Taylor wrote: >>>>>> >>>>>> >>>>>>>Hi, >>>>>>> >>>>>>>Is it possible to have the boot filesystem of a small openssi cluster >>>>>>>raid level 1? >>>>>>> >>>>>>>Using the debian sarge installation CD I set up a raid1 drive that >>>>>>>contains the whole system. /dev/md0 that is. >>>>>>> >>>>>>>Then I followed the steps from the debian install document (which I have >>>>>>>working on another non RAID based cluster). After apt-get install >>>>>>>openssi I reboot to the new kernel but when init starts I get >>>>>>>Error: /usr/something/bin/chroot not found. >>>>>>> >>>>>>>If I reboot with the normal debian 2.4.27 kernel everything works. Is >>>>>>>this due to lack of support for raid in the openssi kernel? >>>>>>> >>>>>>>Thanks for any help. >>>>>>> >>>>>>>Sincerely, >>>>>>>Jon Taylor. >>>>>>>UofT Botany Bioinformatics Lab >>>>>>> >>>>>>> >>>>>>> >>>>>>>------------------------------------------------------- >>>>>>>SF.Net email is sponsored by: Tell us your software development plans! >>>>>>>Take this survey and enter to win a one-year sub to SourceForge.net >>>>>>>Plus IDC's 2005 look-ahead and a copy of this survey >>>>>>>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix >>>>>>>_______________________________________________ >>>>>>>Ssic-linux-users mailing list >>>>>>>Ssi...@li... >>>>>>>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>------------------------------------------------------- >>>>>>SF.Net email is sponsored by: Tell us your software development plans! >>>>>>Take this survey and enter to win a one-year sub to SourceForge.net >>>>>>Plus IDC's 2005 look-ahead and a copy of this survey >>>>>>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix >>>>>>_______________________________________________ >>>>>>Ssic-linux-users mailing list >>>>>>Ssi...@li... >>>>>>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users >>>>>> >>>>> >>>> >>>> >>>>------------------------------------------------------- >>>>SF.Net email is sponsored by: Tell us your software development plans! >>>>Take this survey and enter to win a one-year sub to SourceForge.net >>>>Plus IDC's 2005 look-ahead and a copy of this survey >>>>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix >>>>_______________________________________________ >>>>Ssic-linux-users mailing list >>>>Ssi...@li... >>>>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users >>>> >>> >>>------------------------------------------------------- >>>SF.Net email is sponsored by: Tell us your software development plans! >>>Take this survey and enter to win a one-year sub to SourceForge.net >>>Plus IDC's 2005 look-ahead and a copy of this survey >>>Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix >>>_______________________________________________ >>>Ssic-linux-users mailing list >>>Ssi...@li... >>>https://lists.sourceforge.net/lists/listinfo/ssic-linux-users >>> >> > > |
From: Jonathan T. <jon...@ut...> - 2005-04-29 12:18:24
|
Yep, no problem. At boot time I see the md module detecting my raids. It then thinks it needs to load md-personality-3, which should result in raid1 module being loaded. It tries to load this via insmod and that fails. Before making initrd I have added: alias md-personality-3 raid1 to /etc/modutils/aliases ran update-modules and observed this line has moved into /etc/modules.conf and then regenerated initrd. I tried this with the mkinitrd -k option to verify that indeed raid1.o as well as the new modules.conf are in the new initrd. That said I believe it still fails because for some reason it is trying to use insmod to load md-personality-3 and I do not think insmod is smart enough to check the /etc/modules.conf file for an alias. I think if it was using modprobe to load md-personality-3 then it would resolve to raid1.o and work fine. Anything obvious I am missing? J. On Fri, 2005-04-29 at 12:26 +0530, Aneesh Kumar wrote: > On 4/29/05, Jonathan Taylor <jon...@ut...> wrote: > > Hmm... raid1 has no dependencies. insmod fails with the error that it > > cannot find md-personality-3 whereas modprobe seems to consul > > modules.conf, notices the alias md-personality-3 raid1 and instead uses > > the raid1 module which does exist in the initrd. > > > > Can you elaborate what you are trying to do. Are you trying to use > md-personality-3 in /etc/mkinitrd/modules. Do you have the alias > defiend properly in /etc/modules.conf. did you use update-modules to > modify /etc/modules.conf. I tried with the alias parport_lowlevel in > /etc/mkinitrd/modules and it worked for me. > > -aneesh > |
From: Aneesh K. <ane...@gm...> - 2005-04-29 06:56:58
|
On 4/29/05, Jonathan Taylor <jon...@ut...> wrote: > Hmm... raid1 has no dependencies. insmod fails with the error that it > cannot find md-personality-3 whereas modprobe seems to consul > modules.conf, notices the alias md-personality-3 raid1 and instead uses > the raid1 module which does exist in the initrd. >=20 Can you elaborate what you are trying to do. Are you trying to use md-personality-3 in /etc/mkinitrd/modules. Do you have the alias defiend properly in /etc/modules.conf. did you use update-modules to modify /etc/modules.conf. I tried with the alias parport_lowlevel in /etc/mkinitrd/modules and it worked for me. -aneesh |
From: Aneesh K. <ane...@gm...> - 2005-04-29 12:27:00
|
On 4/29/05, Jonathan Taylor <jon...@ut...> wrote: > Yep, no problem. >=20 > At boot time I see the md module detecting my raids. It then thinks it > needs to load md-personality-3, which should result in raid1 module > being loaded. It tries to load this via insmod and that fails. >=20 > Before making initrd I have added: >=20 > alias md-personality-3 raid1 >=20 > to /etc/modutils/aliases >=20 > ran update-modules and observed this line has moved > into /etc/modules.conf and then regenerated initrd. I tried this with > the mkinitrd -k option to verify that indeed raid1.o as well as the new > modules.conf are in the new initrd. That said I believe it still fails > because for some reason it is trying to use insmod to load > md-personality-3 and I do not think insmod is smart enough to check > the /etc/modules.conf file for an alias. I think if it was using > modprobe to load md-personality-3 then it would resolve to raid1.o and > work fine. > you can build the ramdisk with -k option. This will leave the files in a temporary directory. As far as i understand the script it uses modprobe to load the modules. The actual script will be in the temporary directory created using -k option as loadmodules. As a quick fix did you try using raid1.o direcly in /etc/mkinitrd/modules ? This should be a generic debian issue. -aneesh |
From: Jonathan T. <jon...@ut...> - 2005-04-29 12:55:37
|
On Fri, 2005-04-29 at 17:56 +0530, Aneesh Kumar wrote: > On 4/29/05, Jonathan Taylor <jon...@ut...> wrote: > > Yep, no problem. > > > > At boot time I see the md module detecting my raids. It then thinks it > > needs to load md-personality-3, which should result in raid1 module > > being loaded. It tries to load this via insmod and that fails. > > > > Before making initrd I have added: > > > > alias md-personality-3 raid1 > > > > to /etc/modutils/aliases > > > > ran update-modules and observed this line has moved > > into /etc/modules.conf and then regenerated initrd. I tried this with > > the mkinitrd -k option to verify that indeed raid1.o as well as the new > > modules.conf are in the new initrd. That said I believe it still fails > > because for some reason it is trying to use insmod to load > > md-personality-3 and I do not think insmod is smart enough to check > > the /etc/modules.conf file for an alias. I think if it was using > > modprobe to load md-personality-3 then it would resolve to raid1.o and > > work fine. > > > > you can build the ramdisk with -k option. This will leave the files in > a temporary directory. As far as i understand the script it uses > modprobe to load the modules. The actual script will be in the > temporary directory created using -k option as loadmodules. > > As a quick fix did you try using raid1.o direcly in > /etc/mkinitrd/modules ? This should be a generic debian issue. > > -aneesh > I think this is not being done by a script but rather when it detects the md raid device, it believes it depends on md-personality-3 and tries to insmod it. J. |