Even if they are compiler flags, they are referring to the exact same file (mdadm.conf) that my mdadm 3.0.2 completely ignores. It might be a complete coincidence, but it does look suspicious, doesn't it? I resend the attachment for the list to see On Mon, Sep 28, 2009 at 5:04 PM, Kristleifur Daðason <kristleifur@xxxxxxxxx> wrote: > Hi, > > it looks like we have actually started talking off-list :) (I think so at > least ...) > > Btw, Those "-Werror" things are compiler flags (it means "warn on error") -- > you're getting neither errors nor warnings there -- compilation is going > fine > > You'd better take this back to the list, there's probably smarter people > than me there ... and maybe also try the Ubuntu forums > > -- Kristleifur > > On Mon, Sep 28, 2009 at 1:52 PM, Aggelos Kyritsis <filodoksos@xxxxxxxxx> > wrote: >> >> I think I found the cause of the whole situation. >> >> During the compilation of mdadm 3.0.2 several error messages appear >> considering the mdadm.conf file. >> >> I attach a file with the compiler's output. I have a feeling that if >> we can pinpoint the cause of those errors, the problem will be solved. >> >> Maybe my system is missing some compilation libraries? I have already >> installed the build-essential and gcc packages. >> >> >> >> On Mon, Sep 28, 2009 at 3:53 PM, Kristleifur Daðason >> <kristleifur@xxxxxxxxx> wrote: >> > Hi again :) >> > >> > I forgot that I have the old mdadm 2.6.9 on this machine, so it's >> > probably >> > not 100% the same; I did have 3.0.x but not currently, sorry about that. >> > >> > The /etc/mdadm/mdadm.conf is probably copied automatically into the >> > initramdisk when you have the Ubuntu package for mdadm, but I'm not sure >> > what happens if you have a custom-built mdadm. >> > >> > I would guess that there is probably some config file for >> > update-initramfs >> > that tells it to take this and that file. >> > >> > Wish I could help you better. >> > >> > Have you tried expanding the updated initramfs and checking what the >> > mdadm.conf file in looks like? >> > >> > Good luck and by all means ask me any further questions you have! >> > >> > -- Kristleifur >> > >> > On Mon, Sep 28, 2009 at 12:36 PM, Aggelos Kyritsis >> > <filodoksos@xxxxxxxxx> >> > wrote: >> >> >> >> Thanks for the quick responce :-) >> >> >> >> I tried the "sudo update-initramfs -u -k all" command and it got the >> >> following two messages >> >> >> >> update-initramfs: Generating /boot/initrd.img-2.6.28-15-generic >> >> update-initramfs: Generating /boot/initrd.img-2.6.28-11-generic >> >> >> >> But still no luck with the mdadm >> >> >> >> I have found a guide on creating a custom initial ramdisk >> >> (http://www.ibm.com/developerworks/linux/library/l-initrd.html) but it >> >> still isn't clear to me how to place the mdadm.conf in it (and make >> >> mdadm read the file). >> >> >> >> Could you please elaborate? >> >> >> >> >> >> >> >> >> >> On Mon, Sep 28, 2009 at 12:18 PM, Kristleifur Daðason >> >> <kristleifur@xxxxxxxxx> wrote: >> >> > On Mon, Sep 28, 2009 at 7:13 AM, Aggelos Kyritsis >> >> > <filodoksos@xxxxxxxxx> >> >> > wrote: >> >> >> >> >> >> Dear sir/madam, >> >> >> >> >> >> I am running ubuntu 9.04. Until recently I used the mdadm version >> >> >> that >> >> >> exists in the ubuntu repositories, with perfect success. However, >> >> >> since that version is fairly old (2.6, I think), I decided to >> >> >> install >> >> >> the latest version 3.0.2. >> >> >> >> >> >> On a freshly formatted system with no mdadm I downloaded >> >> >> http://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-3.0.2.tar.gz, >> >> >> unzipped it and run the "sudo make" and "sudo make install" >> >> >> commands. >> >> >> According to mdadm --version, I succesfuly installed version 3.0.2 >> >> >> of >> >> >> the program. I was also successful on creating and mounting a fresh >> >> >> raid 5 array. >> >> >> >> >> >> However, the installation didn't create either the >> >> >> /etc/mdadm/mdadm.conf or the /etc/mdadm.conf file, where I need to >> >> >> specify the array details so that it is assembled during boot time. >> >> >> >> >> >> I manually created the mdadm.conf file in both locations and added >> >> >> the >> >> >> "DEVICE partitions" line and a line with the result from mdadm >> >> >> --examine --scan >> >> >> >> >> >> Even though this was enough on the old version of mdadm for auto >> >> >> assemble during the boot sequence (so that /etc/fstab could mount >> >> >> /dev/md0), on version 3.0.2 it made no diferrence at all, as if the >> >> >> mdadm I compiled and installed manually wouldn't read the >> >> >> mdadm.config >> >> >> file, neither on /etc/mdadm/mdadm.conf or on /etc/mdadm.conf >> >> >> >> >> >> Is there anything I could do to address this problem? Any way to >> >> >> permanently point the mdadm to its mdadm.conf file? is there an >> >> >> mdadm.conf file created on some other location on the disk, where I >> >> >> can add the array information? >> >> >> >> >> >> Thanks in advance >> >> >> >> >> >> Kind regards >> >> >> >> >> >> Angelos Kyritsis. >> >> > >> >> > Hi, >> >> > >> >> > I've tried almost exactly the same setup. I suspect that you may >> >> > simply need to update the initramfs, specifically to place the >> >> > mdadm.conf in the init-ramdisk. Try "sudo update-initramfs -u -k >> >> > all". >> >> > "-u" means update the initrd, "-k all" means to update for all >> >> > kernels. >> >> > >> >> > -- Kristleifur >> >> > >> > >> > > >
Attachment:
compiler-message
Description: Binary data
