Bug 7505 - installer can't find disk space to install when there are lots of disks present and the os disk is the last disk detected
Summary: installer can't find disk space to install when there are lots of disks prese...
Status: RESOLVED DUPLICATE of bug 11105
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-09-17 16:32 CEST by jeff deifik
Modified: 2014-09-20 10:50 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description jeff deifik 2012-09-17 16:32:40 CEST
Description of problem:

When I try to install, the installer says it can't recognize partitions
on my hard drives and asks if I want to delete the existing partitions.
When I say no, it says it can't find any space to do the installation and
repeats the message.

If I agree to delete the existing partitions, I can access /dev/sdh
and do a normal installation.

I suspect that after finding a bunch of hard drives with unrecognized partitions, the installer gives up looking for usable partitions.

I have a gateway oem asus cur-dls motherboard.
I have installed a supermicro hba with 7 sata hard drives.
I have a md software raid 5 partition on the 7 sata hard drives.
I have installed a promise tx-100 controller with 1 pata hard drive.
The pata drive is where my operating system is (/dev/sdh).

Fedora 17 has no problem finding /dev/sdh to do an installation.
If I agree to lose all partitions, I can do an install with mageia-2.

Version-Release number of selected component (if applicable):

mageia-2

How reproducible:

100%

Steps to Reproduce:
1. install mageia 2 x86 cd
2. boot
3. refuse to delete partitions

I think it also a misfeature that the md partitioned disks are unrecognized.
Fedora 17 knows what they are, and builds the md array automatically during
installation.
jeff deifik 2012-09-17 16:33:49 CEST

Summary: installer can't find disk space to install when there are lots of disks present => installer can't find disk space to install when there are lots of disks present and the os disk is the last disk detected

Comment 1 Manuel Hiebel 2012-09-23 21:10:43 CEST
can you add the output of 'fdisk -l /dev/sd[a-z]' ?

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

Comment 2 jeff deifik 2012-09-23 21:18:09 CEST
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sde: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdg: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdh: 82.0 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders, total 160086528 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc6aec6ae

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1   *          63    20482874    10241406    7  HPFS/NTFS/exFAT
/dev/sdh2        20484096    21508095      512000   83  Linux
/dev/sdh3        21508096    41988095    10240000   83  Linux
Comment 3 Samuel Verschelde 2013-08-27 13:16:02 CEST
1. Changing version to cauldron since we can't fix installer for released versions (that's what alphas and betas are for)
2. Is this bug still valid with latest installer? (Mageia 4 alpha 1 as of today)

CC: (none) => stormi
Version: 2 => Cauldron

Comment 4 jeff deifik 2013-08-27 13:58:41 CEST
I have no idea. I have not tested it.
Samuel Verschelde 2013-08-27 19:15:11 CEST

Keywords: (none) => NEEDINFO

Comment 5 stephane FLAVIGNY 2014-09-20 10:50:37 CEST
Dear,

It's an old bug with the installer and md/dmraid.

*** This bug has been marked as a duplicate of bug 11105 ***

Status: NEW => RESOLVED
CC: (none) => megastorage
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.