I have an XP amd x64 computer which I have just made dual boot with ubuntu (fiesty) = a partial return to linux after a an absence, but I remember Red Hat 9 fondly! Very rusty though, and never more than a beginner)

I have been following the directions given in "HOWTO - Discovering and using existing sata raid (eg sil3112)".

When I enter: dmraid -ay -v

I get the response:

RAID set "nvidia_fjfdaeag" already active
INFO: Activating stripe RAID set "nvidia_fjfdaeag"
RAID set "nvidia_fjfdaeag1" already active
INFO: Activating partition RAID set "nvidia_fjfdaeag1"

Then when I enter: mount -t ntfs -o users,owner,ro,umask=00 /dev/mapper/nvidia_fjfdaeag /mnt/raid0

I get the response:

mount: /dev/mapper/nvidia_fjfdaeag already mounted or /mnt/raid0 busy

After searching the web, I found a suggestions that the Device Mapper may be to blame, so followed instructions to comment out all of the md and dm-mod entries in modules.dep then rebooted - which has apparently solved the problem for others - but the problem remains unchanged.

Any ideas?

Other Info:

The two sata disks are /dev/sda and /dev/sdb

I CAN mount the second disk using the command: mount -t ntfs -o users,owner,ro,umask=00 /dev/mapper/nvidia_fjfdaeag1 /mnt/raid0

So it seem the problem is only with /dev/sda

fdisk -l /dev/sda:

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 48642 390716833+ 7 HPFS/NTFS


Mount:

/dev/hda2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-15-generic/volatile type tmpfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/dev/hda1 on /media/disk type ntfs (rw,nosuid,nodev,umask=222,utf8)
/dev/sda1 on /media/disk-1 type ntfs (rw,nosuid,nodev,umask=222,utf8)
/dev/mapper/nvidia_fjfdaeag1 on /mnt/raid0 type ntfs (ro,noexec,nosuid,nodev,umask=00)

fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda2
UUID=ae001c01-57ce-4f76-af91-dcab4cfde4a6 / ext3 defaults,error
s=remount-ro 0 1
# /dev/hda5
UUID=29db2d79-8908-46e8-8bf1-8c8fa888c35c none swap sw
0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

I do not use raid of any kind and I have a sata but you may like this post by kyleabaker

http://www.linuxquestions.org/questi...11#post2622911

RAID set "pdc_ecjdaedd1" already active is used (apparently) to this next step
you want to replace '/dev/sda1' (or your similar partition name) with the part that (in my case says) 'pdc_ecjdaedd1'......in your /etc/fstab.

and the links show

http://www.linux-ntfs.org/

http://wiki.linux-ntfs.org/doku.php?id=howto:mount

You actually want to mount a "partition" from the Device array. Partitions are listed as /dev/mapper/xxx_sdjflsdfj1 <- note the numeric value. Doing a fdisk -l /dev/mapper/xxx_volume <- will list all the partitions on that volume.

You're not actually mounting the second disk with this command, you're mounting the array. According to what you have posted, there is an array named "/dev/mapper/nvidia_fjfdaeag" which is configured as a RAID0 with the single partition "/dev/mapper/nvidia_fjfdaeag1". That partition is the only thing that is mountable. It is best NOT to mess with the raw devices that configure an array, i.e. /dev/sda and /dev/sdb in your case.

One more thing: during boot, you may see a bunch of messages stating that it's attempting to access past the end of the device. Ignore those errors. They're an artifact of the way that the mapper uses the partition table on the first device as the partition table for the whole array.