Bug 1074

Summary: failure to detect hard disk
Product: Mageia Reporter: Guillaume Rousse <guillomovitch>
Component: InstallerAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, pterjan, thierry.vignaud
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: drakx-installer-stage2 CVE:
Status comment:

Description Guillaume Rousse 2011-04-30 13:55:05 CEST 
The installer doesn't load sd_mod module, and installation process fails at disk detection stage. I'm attaching debug log.
Comment 1 Guillaume Rousse 2011-04-30 13:57:10 CEST 
The debug log is too large to be added. It is available at http://www.zarb.org/~guillomovitch/ddebug.log instead.
Comment 2 Thierry Vignaud 2011-05-06 14:27:44 CEST 
uh?
Your ddebug.log shows that sd_mod was nicely loaded before the partitioning step

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

Comment 3 Pascal Terjan 2011-05-06 14:31:28 CEST 
No it was loaded later (manually) and then the partitioning succeeded

See the following happening several times before sd_mod appears in the log :

* id2edd: 0x2b3f2b3e=>/sys/firmware/edd/int13_dev81 0x169f169e=>/sys/firmware/edd/int13_dev82 0xc126af56=>/sys/firmware/edd/int13_dev80
* error: Une erreur est survenue : aucun périphérique valide n'a été trouvé pour
créer de nouvelles partitions. Veuillez vérifier votre matériel. at /usr/lib/libDrakX/fs/any.pm line 17.
Comment 4 Marja Van Waes 2011-10-11 22:58:01 CEST 
(In reply to comment #3)
> No it was loaded later (manually) and then the partitioning succeeded
> 

@ Guillaume
Was this still an issue when installing Mageia 1?

CC: (none) => marja11
Source RPM: (none) => drakx-installer-stage2

Comment 5 Guillaume Rousse 2011-10-11 22:59:14 CEST 
No idea. I never installed mageia 1 on this host.
Comment 6 Marja Van Waes 2011-10-11 23:37:58 CEST 
(In reply to comment #5)
> No idea. I never installed mageia 1 on this host.

Thanks for replying, Guillaume.

I'm closing this bug as old. Feel free to reopen it if you encounter it again

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
Resolution: (none) => OLD