You are not logged in.

#1 2012-01-01 17:01:20

danan
Member
Registered: 2011-01-19
Posts: 30

Intel Software Raid 0: Couldn't parse stripe destination

Hi,

just before Christmas I got a new work computer, and of course I would love to install arch on it. It came with Intel Software Raid and Win7 installed. For some tasks I need Windows, so I would like to leave it as it is. Installing on a raid seemed straight forward.

modprobe dm_mod
dmraid -ay

But it says

[...]stripe:Couldn't parse stripe destination
RAID set "isw_..._Volume0" was not detected
ERROR: device "isw_..._Volume0" could not be found'

I googled over a week and mostly found "bug" or "error in your version, try new one", "bug solved in newest version". No workaround or hints, what could be wrong; and I still have the problem. Just downloaded the bleeding edge newest daily build just from today, and it's still there.

I have no clue what's wrong. I'm always little suspiciouse with raid, because of total loss in case of a failure. On my research I also found a bunch of people, where dmraid stopped working after an update, which would be a desaster! I'm thinking of turning RAID off, put Windows on one and Arch on the other disk, but I thought I could gain some performance in RAID. Is it worth the trouble?

BTW: Ubuntu live CD finds raid and partitions without doing anything. What's the difference?

Thanks!
/André

Offline

#2 2012-01-01 18:01:04

TastyDr.Pepper
Member
From: Somewhere, in the US
Registered: 2011-11-23
Posts: 20

Re: Intel Software Raid 0: Couldn't parse stripe destination

Maybe edit your rc.conf file and enable the line that says fakeraid??? Because fakeraid on my computer works just fine after enabling this. ( Just acessing windows 7 off of 4 250gb drives in raid 0 )

Here's the line I changed:

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="yes"

And here's the entire file:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged, using "" makes hwclock fall back
#   to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
#   Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="America/Detroit"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=(vboxdrv vboxnetflt)

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="yes"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="Apex"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
#   - broadcast: broadcast address (ignored for DHCP) (optional)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
broadcast=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(hwclock @network syslog-ng @gpm @avahi-daemon @sshd @netfs @crond @alsa dbus @cupsd @samba)

Other than that I don't know much about RAID in general... I plan on getting rid of it anyways pretty soon.

Offline

#3 2012-01-01 22:30:26

danan
Member
Registered: 2011-01-19
Posts: 30

Re: Intel Software Raid 0: Couldn't parse stripe destination

This is true, it's off for me, too. But how am I supposed to enable it on a live CD? I can't even install arch in the first place. I thought modprobing could do the trick, but maybe not. Do I need any other module. Just googled this, no result...

Offline

#4 2012-01-01 23:35:01

TastyDr.Pepper
Member
From: Somewhere, in the US
Registered: 2011-11-23
Posts: 20

Re: Intel Software Raid 0: Couldn't parse stripe destination

Hmm, if the Ubuntu Live cd recognises it you could do an install from existing linux:

https://wiki.archlinux.org/index.php/In … ting_Linux

You'll have to compensate for a few things, such as when you install grub or any of the one of the boot managers you choose you will install it to /dev/mapper/something if I remember correctly.

I'd reccomend using alien to make packages out of the arch linux packages as found on the install from exsisting linux page, although it's just preferance.

It's not that much harder than doing it through the Arch Live CD. I did this when I put Arch on my flash drive, and did it again ( sort of ) when I put Gentoo on it.

Offline

#5 2012-01-02 19:09:39

danan
Member
Registered: 2011-01-19
Posts: 30

Re: Intel Software Raid 0: Couldn't parse stripe destination

Thanks for the tipps. Didn't know about this possibility to install from existing linux. But for whatever reason both ways won't work. unsquashfs produces an error (I'm not familiar with it at all) and after installing pacman it says "/usr/bin/pacman not found", but it's there and executable; no idea whats wrong. Also it doesn't really ensure that it would boot afterwards. I guess I'll disable the raid and separate Windows and Arch as planed (as I read, RAID doesn't give so much extra performance for everyday use).

Offline

#6 2012-01-04 02:33:30

TastyDr.Pepper
Member
From: Somewhere, in the US
Registered: 2011-11-23
Posts: 20

Re: Intel Software Raid 0: Couldn't parse stripe destination

I got 3 seconds off of my windows boot time with raid 0 and four drives. For me it wasn't worth it. Although my load times in other programs DID go down, it was barely noticeable.

Ironically I used linux to make an image of my windows install, and then copied it to my raid array later on, of course that was a year ago, when I was on OpenSUSE

Last edited by TastyDr.Pepper (2012-01-04 02:39:37)

Offline

#7 2012-01-04 03:10:55

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: Intel Software Raid 0: Couldn't parse stripe destination

With CF cards my raid0 bootable archlinux boots in nine seconds and performs snappy in apps.

Especially nice with jumanji as the browser and xfce4 as Desktop.

Bonus is quiet operation and low power sonsumption.


Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#8 2012-01-04 10:37:00

danan
Member
Registered: 2011-01-19
Posts: 30

Re: Intel Software Raid 0: Couldn't parse stripe destination

But is it due to the CF or the RAID? Personally I believe, the CF improves it, RAID maybe only a little extra, but not significant. But that's the point, I didn't mention: my computer came with 2 SSDs in a RAID. I separated the RAID, but had not time to get Windows bootable or install arch. I will do so now and see, if it's still as fast as before (Windows up and running in 16sec!). I'll let you know.

Offline

Board footer

Powered by FluxBB