Bug 5788 - Installer fail finding ANY drive - regression
Summary: Installer fail finding ANY drive - regression
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-08 00:26 CEST by Morgan Leijström
Modified: 2012-05-08 23:32 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
report.bug (101.85 KB, text/plain)
2012-05-08 00:27 CEST, Morgan Leijström 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Morgan Leijström 2012-05-08 00:26:25 CEST 
This may be related to Bug 5667 but on an completely different drive, main board, CPU... Only same thing is the table, me, and mageia, and possibly the boot.iso 32 bit fetched last hour.

Machine: Laptop IBM Thinkpad T40
Drive: PATA 80 GB mechanical, Win XP boots on it OK

I took pictures of the text terminals, tell med if you need.
I will grab report.bug now.
Comment 1 Morgan Leijström 2012-05-08 00:27:09 CEST 
Created attachment 2212 [details]
report.bug
Comment 2 Morgan Leijström 2012-05-08 00:57:51 CEST 
Now i have also tried
 § Another PATA drive
 § Only A SATA drive in the ultrabay
 § Only A PATA on USB-PATA adapter.
And no drive is ever found
First I did not reboot, just plugged in, waited some seconds after USB messages or docking message appeared in kernel log (Alt-F4) and had it retry.
Now i also tried having them all attached and rebooted: none is found.

So, actually NO drive type is found!
Morgan Leijström 2012-05-08 00:59:22 CEST

Priority: Normal => High
Summary: Installer fail finding PATA drive - regression => Installer fail finding ANY drive - regression

Morgan Leijström 2012-05-08 02:14:53 CEST

CC: (none) => pterjan, thierry.vignaud

Comment 3 Morgan Leijström 2012-05-08 23:32:45 CEST 
When i found out more computers had same problem i purged stage2 from urpmi-proxy cache, and then it worked.

Either urpmi-proxy sent old cached version instead of a new available, or it coincided with a new stage 2 becoming available?  -> Bug 5797 

Sorry for the noise here.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.