I've been posting install failures over at the fedora-devel list and thought I might try over here, so please forgive me if for this cut and paste. I have three seperate SATA RAID controllers at my disposal, Adaptec 1210SA, SiL 3118 and an Nvidia ck804. All three fail on installation, i.e. the /dev/mapper/mapper0 device that is created fails when the file system is created. In addition, anaconda seems to always try and use dmraid when I connect two SATA drives to any of the three RAID controllers, even if I do not configure any RAID containers on the controller. I'm willing to learn a bit here and to do any debugging with my system(x86_64) that you folks feel is needed or desired, so just let me know! So, here is my previous posts to fedora-list and fedora-devel: https://www.redhat.com/archives/fedora-devel-list/2007-July/msg00498.html and https://www.redhat.com/archives/fedora-devel-list/2007-July/msg00385.html <quote> I quickly browsed through bugzilla to see if I was the only one having issues with dmraid. It looks like there are a few tickets, but not as many as I would have thought. A quick search shows only ten or so tickets: https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora&component=dmraid&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc= However, they are being masked as installer failures in anaconda. I went through the first page or so and came up with these: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=155979 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242252 https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=156161 https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=157773 https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=128766 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234719 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227186 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217291 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213738 https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=139765 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175586 There's even one or two that I have commented on and one or two that completely duplicate my issues. I have three dmraid compatible controllers at my disposal and all three fail to install(anaconda barfs). Anyone want to suggest a troubleshooting methodology? Should I be contacting the upstream dmraid maintainers for the failures? </quote> <quote> I spent some time trying to arm wrestle my machines fake raid controllers(ck804, sil 3118) and a pci board I had lying around(adaptec 1210sa), and came to the conclusion that dmraid was causing me serious grief. First off, I could _not_ get dmraid to go away during the install on x86_64. Even the nodmraid kernel option failed me. Each time I booted up with two disks connected to any controller, the only drive I had at my disposal was /dev/mapper/mapper0. I did notice that there was a 'disable dmraid' toggle in the advanced setup button in the installer, however this option was grayed out in all situations that I could come up with. Second, all three of the SATA raid controllers I tested failed in similar, yet different ways during the install process. They mainly failed during file system creation, but there was some variances in behavior that were interesting. For example, some would cause anaconda to dump and crash, others would simply cause the installer to abort and reboot the machine. Third, and the most annoying, was that I couldn't install a plain s/w raid configuration with 2 drives connected. There was just no way to keep the system from assuming that I meant to use /dev/mapper/mapper0 even after I ensured that the superblock metadata was wiped out with a quick call to 'dmraid -Er /dev/sdX' to be sure that it was really gone. In a related note, it would be nice if the installer would allow you to create a broken raid 1 in the installer, anaconda should definitely warn you and tell you that what you are doing is loopy, but there should be a way to just say, "go ahead if you really wanna". I was unable to find this magic, and had to install on a single drive. I guess I'll have to migrate to s/w raid after the install is finished. I am more than interested now in diagnosing and fixing the issues I've spewed forth here. I've even gone so far as to start some bugzilla goodness on tkt:246817 Any takers in dev land want to give me a hand with this one? </quote> Sean _______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
