Bug 227574 - dmraid on sil3114 controller gets array sizes wrong
dmraid on sil3114 controller gets array sizes wrong
Product: Fedora
Classification: Fedora
Component: dmraid (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Heinz Mauelshagen
Depends On:
  Show dependency treegraph
Reported: 2007-02-06 17:03 EST by Jarod Wilson
Modified: 2007-11-30 17:11 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-26 06:15:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jarod Wilson 2007-02-06 17:03:15 EST
Description of problem:
I've got a box with a Silicon Image 3114 SATA dmraid controller on it, with 4x
160GB drives attached. In the sil bios, I've created a RAID10 array (298GB in
size). While dmraid does see a RAID10 set, it reports a size much bigger than it

# dmraid -s
*** Superset
name   : sil_ahacacadbhej
size   : 542416197632
stride : 256
type   : raid10
status : ok
subsets: 2
devs   : 4
spares : 0

Anaconda refuses to try to use the dmraid array, instead presenting the
individual drives to install on. On vt4, this error gets logged:

<4>device-mapper: table: device /dev/sda too small for target

Version-Release number of selected component (if applicable):
dmraid 1.0.0.rc14

How reproducible:
Set up RAID10 array in sil bios, boot current rawhide installer

Additional info:
If so desired, I can hook this box up to a serial console, and/or boot it off a
live cd and provide remote access.
Comment 1 Heinz Mauelshagen 2007-10-24 12:57:57 EDT
Hrm, bz has been overlooked it seems.
In case you still have access to that configuration, please prvide files
created by "dmraid -rD" in a bzip2/tarball sil-bz227574-raid10.tar.bz2.
Comment 2 Jarod Wilson 2007-10-24 15:50:24 EDT
Unfortunately, that motherboard is toast, so I no longer have any way to
reproduce the problem. FWIW, it was an Asus K8N-DL motherboard (dual socket 940
Comment 3 Heinz Mauelshagen 2007-10-26 06:15:35 EDT
Closing this.
If the bug shows again for you later, please
reopen and attach metadata as described.

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