Bugzilla – Bug 805250
installation does not recognize hard disks
Last modified: 2013-03-09 09:28:55 UTC
The installer complains about not finding any disks. 12.2 works just fine on that machine though.
Created attachment 526084 [details] dmesg from 12.2
Created attachment 526085 [details] hwinfo from 12.2
Created attachment 526086 [details] hwinfo from 12.3
Created attachment 526087 [details] y2logs
Could you get full dmesg from the 12.3 rescue/installation? For example by sending it over ssh somewhere? It is stored in /var/log/boot.msg IIRC...
This might be completely unrelated or irrelevant, but when I was debugging some iSCSI problem yesterday, I noticed some typos in /usr/share/Yast2/modules/StorageProposal.ycp. In a couple of places, I see "weigth" instead of "weight".
Created attachment 526532 [details] boot.msg from 12.3
Oh well, pata_acpi mess is used instead of pata_piix: pata_acpi 0000:00:03.2: setting latency timer to 64 pata_acpi 0000:00:1f.2: setting latency timer to 64 scsi0 : pata_acpi scsi1 : pata_acpi ata1: PATA max UDMA/133 cmd 0x2448 ctl 0x247c bmdma 0x2410 irq 19 ata2: PATA max UDMA/133 cmd 0x2440 ctl 0x2478 bmdma 0x2418 irq 19 pata_acpi 0000:00:1f.5: setting latency timer to 64 ata1: prereset failed (errno=-19) ata1: reset failed, giving up ata2: prereset failed (errno=-19) ata2: reset failed, giving up scsi2 : pata_acpi usbcore: registered new device driver usb scsi3 : pata_acpi Driver Activation Cmd: "modprobe pata_acpi" But /etc/modprobe.d/00-system.conf: blacklist pata_acpi So? Michal, any ideas what is going on here, why is the module is loaded?
(In reply to comment #8) > Oh well, pata_acpi mess is used instead of pata_piix: Perhaps ship_stopper as pata_acpi will work almost nowhere...
(In reply to comment #8) > Michal, any ideas what is going on here, why is the module is loaded? I see, this is modprobe, so blacklist is not considered... @Ludwig: adding brokenmodules=pata_acpi makes it work again, right? And what do you see when linuxrc prints: Activating kernel modules: drivers: ??? What drivers?
Created attachment 527250 [details] screenshot
Created attachment 527251 [details] screenshot with brokenmodule parameter
I probably see the bug. No 00-system.conf in 12.3 initrd. installation-images should include the newly added suse-module-tools, I think. There reside a base of all blacklists we have and could cause severe problems during installation (like this one) if omitted.
(In reply to comment #13) > I probably see the bug. No 00-system.conf in 12.3 initrd. installation-images > should include the newly added suse-module-tools, I think. SR 156733: accept or deny :).
This is an autogenerated message for OBS integration: This bug (805250) was mentioned in https://build.opensuse.org/request/show/156983 Factory / installation-images
fixed
Will you also commit the patch to the git repo?
it is, 12.3 branch
Ok, but what about master which I looked at?
I'll merge changes when 12.3 is done.
Ludwig, could you retry with GM? Hopefully there is no other bug in that path.