Ubuntu

How do I access Windows RAID1 drive in Ubuntu dual boot?

Asked by jrdecastro

System has 3 hard drives, one with Ubuntu in a single drive (non-RAID) and a RAID1 array of two drives containing Windows.
/sdc is a 350GB hard drive containing the entire Ubuntu installation, formatted ext3
/sda and /sdb are 500GB each and configured as a RAID1 array, fomratted NTFS, and hold Windows XP32 and XP64 in three partitions:
C: is 120GB and holds Windows XP32
D: is 200GB and holds user data
X: is 80GB and holds Windows XP64
The RAID1 configuration of the Windows disks predates the Ubuntu installation and is Intel RAID - motherboard is Intel DP35DP
Booting is triple boot - XP32, XP64, and Grub, which in turn loads Ubuntu 8.04.
 dmraid is installed and shows the RAID1 arrays
dmraid -ay shows :
sudo dmraid -ay
RAID set "isw_ebcfidajef_Volume0" already active
RAID set "isw_ebcfidajef_Volume01" already active
RAID set "isw_ebcfidajef_Volume05" already active
RAID set "isw_ebcfidajef_Volume06" already active

where isw .....Volume0 is the entire 500GB disk, 01 is the XP32 partition, 05 is the data partition, and 06 is the XP64 one.
When I look in Nautilus I see "Filessytem" which contains the Ubuntu files, and six other drives - two for XP32, two for data, and two for XP64, but I don't see the three RAID1 entries, so I suspect that if I write to any of the six partitions it will likely not get mirrored to the other one it is paired to...
How do I change this so my file system shows the Ubuntu file system and just 3 RAID1 entries somewhere for the 3 Windows RAID1 partitions? I would (perhaps naively) expect instead to see /dev/md0, md1, and md2 or something similar

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
jrdecastro
Solved:
Last query:
Last reply:
Revision history for this message
jrdecastro (decastro-netvigator) said : 		#1

Also, fstab does not list the RAID partitions :
cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdc1
UUID=40fa1aac-1681-4690-9b3b-6209d795da71 / ext3 relatime,errors=remount-ro 0 1
# /dev/sdc5
UUID=ccc25a40-e40e-41cc-a37a-d24a1b6c6135 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sdd /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

so somehow they are not being recognized?
Help please!

Revision history for this message
Marc D. (koshy) said : 		#2

Please show the contents of /proc/partitions and /proc/mounts.

Revision history for this message
jrdecastro (decastro-netvigator) said : 		#3

cat /proc/partitions
major minor #blocks name

   8 0 488386584 sda
   8 1 76798701 sda1
   8 2 1 sda2
   8 5 360370048 sda5
   8 6 51207156 sda6
   8 16 488386584 sdb
   8 17 76798701 sdb1
   8 18 1 sdb2
   8 21 360370048 sdb5
   8 22 51207156 sdb6
   8 32 312571224 sdc
   8 33 300897418 sdc1
   8 34 1 sdc2
   8 37 11671191 sdc5
 254 0 488383620 dm-0
 254 1 76798701 dm-1
 254 2 360370048 dm-2
 254 3 51207156 dm-3

cat /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/disk/by-uuid/40fa1aac-1681-4690-9b3b-6209d795da71 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/disk/by-uuid/40fa1aac-1681-4690-9b3b-6209d795da71 /dev/.static/dev ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /lib/modules/2.6.24-19-generic/volatile tmpfs rw,relatime 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
securityfs /sys/kernel/security securityfs rw,relatime 0 0
gvfs-fuse-daemon /home/jrc/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0

Hope this helps - thanks!

Revision history for this message
jrdecastro (decastro-netvigator) said : 		#4

Solved it separately by adding them as mounts in fstab -thanks!