The problem with mkinitrd described in this thread and in the two bugzilla tickets is still an open issue and some real SCSI controllers have now been identified, and not just VMWare images. This needs to be a blocker. On Mon, 2008-10-13 at 21:58 -0400, Michael H. Warfield wrote: > On Mon, 2008-10-13 at 14:47 -0400, Michael H. Warfield wrote: > > On Mon, 2008-10-13 at 18:37 +0200, Bruno GARDIN wrote: > > > Antonio i just tried your trick: > > > Up at line 1411 I changed "wait_for_scsi="no"" to "wait_for_scsi="yes"" > > > and rebuild the initrd > > > I worked just fine. Thanks a lot. > > > That was my trick. I think you got the attributions swapped around, > > but that's ok. It was getting a little thick. > > > Looks like the workaround has caught the attention of the folks on > > bugzilla for that bug. It's being discussed now what the best solution > > for the race condition is with an agreement that this race must be fix. > > In discussion over in bugzilla, we determined another workaround. You > can use the "--with=scsi_wait_scan" option when running mkinitrd OR > create the file /etc/sysconfig/mkinitrd with the following line in it: > > MODULES=scsi_wait_scan > > Then recreate your initrd. It works slightly differently but has the > same effect and you're not modifying mkinitrd. > > > > Bruno > > > Mike > > Mike > > > > On Mon, Oct 13, 2008 at 6:19 PM, Michael H. Warfield <mhw@xxxxxxxxxxxx> wrote: > > > > On Mon, 2008-10-13 at 08:42 -0700, Antonio Olivares wrote: > > > > > > > >> Michael, > > > > > > > >> You have a very valid point. My problem was that the partition(not > > > >> the boot partition) was ext4 and had ext4dev, and it was changed to > > > >> plainly ext4. I had to change /etc/fstab from ext4dev to ext4 then > > > >> reinstalled the kernel and it worked :) > > > > > > > > Yeah, reading the various threads, I had already come to the conclusion > > > > that we were dealing with at LEAST two different problems, one being the > > > > ext4dev/ext4 problem. But I wasn't using ext4 (in fact some of my > > > > testing is the 2.6.27 kernel on F9) and others were reporting that it > > > > wasn't fixing the problem. > > > > > > > >> But you are correct with the scsi/dm Volume group(lvms) > > > > > > > > Looks like there is at least one bug already filed on this. > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=466071 > > > > > > > > They're blaming this one on VMware but I'm not sure I would trust this > > > > not to arise on other scsi drivers. > > > > > > > >> Regards, > > > > > > > >> Antonio > > > > > > > > Regards, > > > > Mike > > > > -- > > > > Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw@xxxxxxxxxxxx > > > > /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ > > > > NIC whois: MHW9 | An optimist believes we live in the best of all > > > > PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it! > > > -- > > > BeGe Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw@xxxxxxxxxxxx /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
