dmraid setup for si3112r ?

[anethema]

I had so much luck with you guys i just thought i'd try it again.

This is the last thing im having trouble with getting working:

I found out dmraid was the way to go when trying to get a raid array set up. The drives are NTFS in a RAID-0 config.

I run dmraid -ay sil (which is supposed to find and activate any raid type starting with sil. It finds both drives, adds them to the raid, then for a reason i cant fathom, frees them. Unless its makign a device that i dont know about...i dunno.

Anyways, ill post the output of dmraid when it's run.

root@wheinbox:~# dmraid -ay sil -vvv -d
WARN: locking /var/lock/dmraid/.lock
ERROR: unsupported sector size 2048 on /dev/hdc.
NOTICE: /dev/hda: hpt37x discovering
NOTICE: /dev/hda: hpt45x discovering
NOTICE: /dev/hda: isw discovering
NOTICE: /dev/hda: lsi discovering
NOTICE: /dev/hda: nvidia discovering
NOTICE: /dev/hda: pdc discovering
NOTICE: /dev/hda: sil discovering
NOTICE: /dev/hde: hpt37x discovering
NOTICE: /dev/hde: hpt45x discovering
NOTICE: /dev/hde: isw discovering
NOTICE: /dev/hde: lsi discovering
NOTICE: /dev/hde: nvidia discovering
NOTICE: /dev/hde: pdc discovering
NOTICE: /dev/hde: sil discovering
INFO: sil: areas 1,2,3,4[4] are valid
NOTICE: /dev/hde: sil metadata discovered
NOTICE: /dev/hdg: hpt37x discovering
NOTICE: /dev/hdg: hpt45x discovering
NOTICE: /dev/hdg: isw discovering
NOTICE: /dev/hdg: lsi discovering
NOTICE: /dev/hdg: nvidia discovering
NOTICE: /dev/hdg: pdc discovering
NOTICE: /dev/hdg: sil discovering
INFO: sil: areas 1,2,3,4[4] are valid
NOTICE: /dev/hdg: sil metadata discoveredDEBUG: _find_set: searching sil
DEBUG: _find_set: not found sil
DEBUG: _find_set: searching sil_aeagaidfbcfgb
DEBUG: _find_set: not found sil_aeagaidfbcfgb
DEBUG: _find_set: searching sil_aeagaidfbcfgb
DEBUG: _find_set: not found sil_aeagaidfbcfgb
NOTICE: added /dev/hde to RAID set "sil_aeagaidfbcfgb"
DEBUG: _find_set: searching sil_aeagaidfbcfgb
DEBUG: _find_set: found sil_aeagaidfbcfgb
DEBUG: _find_set: searching sil_aeagaidfbcfgb
DEBUG: _find_set: found sil_aeagaidfbcfgb
NOTICE: added /dev/hdg to RAID set "sil_aeagaidfbcfgb"
DEBUG: checking sil device "/dev/hdg"
DEBUG: checking sil device "/dev/hde"
DEBUG: set status of set "sil_aeagaidfbcfgb" to 16
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "sil_aeagaidfbcfgb"
DEBUG: freeing device "sil_aeagaidfbcfgb", path "/dev/hdg"
DEBUG: freeing device "sil_aeagaidfbcfgb", path "/dev/hde"

As you can see dev/hde and hdg are the drives in the array, im not sure why it is freeing them. Something to do with that sector size error? But i mean, hdc is a cdrom drive, not sure why it would complain about that....

Can anyone help? All my stuff is on those drives and i hate booting to windows when i remember something i need to copy it over to hda (hda too small to keep archive stuff)

I also wanted to run some stuff from the RAID paritition like installing games there, etc to keep load times low.

Anyways, again, any help is greatly apreciated, you guys fixed my last problem fast. I've done a ton of googling and cant find the problem here

EDIT: Forgot to say i was running slack 10, 2.6.7 kernel from the slack cd, A7N8X-E mobo, amd 3200+ xp cpu, 512mb ram

[anethema]

No one has any idea whats going on here or why this is happening? Been trying to fix it since i posted this message and nothin.

TYIA again.

[anethema]

Just gonna bump this once more in dire hopes of getting help. Does ANYONE know what could be going wrong or have any dmraid experiance?

[ajkrishock]

It seems we're trying to slay the same dragon..

I have a SII3112 SATA RAID-0 array onto which I'm trying to install fedora core 3. Here's what I know..

You're using the right tool. You have to use dmraid for 2.6 generation kernels. As root, you should type "dmraid -ay" and you should be able to mount your array. For whatever reason, I have to type "/sbin/dmraid -ay" but you get the same result.

When I do this, I get no response.. but that's a good thing. Now, if you look in the /dev/mapper/ directory, you should see something similar to this:

[tony@localhost mapper]$ ls -la
total 0
drwxr-xr-x 2 root root 160 Mar 17 18:16 .
drwxr-xr-x 11 root root 7780 Mar 17 18:16 ..
crw------- 1 root root 10, 63 Mar 17 13:13 control
brw-r----- 1 root root 253, 2 Mar 17 18:16 sil_afadagcdcgahb
brw-r----- 1 root root 253, 3 Mar 17 18:16 sil_afadagcdcgahb1
brw-r----- 1 root root 253, 4 Mar 17 18:16 sil_afadagcdcgahb2
brw------- 1 root root 253, 0 Mar 17 13:13 VolGroup00-LogVol00
brw------- 1 root root 253, 1 Mar 17 13:13 VolGroup00-LogVol01


The "sil_afadagcdcgahb" entries are the partitions detected on your array (don't ask me why they are named like that). For my system, I have a 160Gb array partitioned in half.. the "sil_afadagcdcgahb1" entry is my NTFS partition and the "sil_afadagcdcgahb2" entry is an unallocated partition that eventually will hold Fedora core 3.

I am trying to get Gerte's "dmraidinitrd" script to run now, but I'm having some issues. I am starting to reach the limit of my knowledge with this. Not sure how much farther I can go.

Any luck on your end?

Regards

Anthony Krishock