RAID driver in dual boot system?

I just installed SUSE 11.2 as dual-boot with WinXP on an older system that has a 160GB PATA drive and a 500GB SATA RAID drive. I left about 80GB on the PATA drive unpartitioned to accommodate SUSE. During the initial installation attempt, SUSE was determined to install on the RAID drive instead of the PATA drive, so I disabled the SATA drivers in the BIOS to force the installation on the PATA drive. This was successful, but now there is no access to the RAID drive from SUSE because there is no driver and it is not mounted. I reactivated the SATA drivers in the BIOS and the RAID drive reappeared in WinXP with everything intact. The SATA drives now appear in SUSE under Hardware Information as “/dev/sdb” and “/dev/sdc” and the listed driver is “sata_sil”.

So how do I get the RAID drivers installed in SUSE and then mount the drive so it can be browsed/modified from Dolphin? I would also like to be able to browse/change this drive from other computers on my home network through samba, just like with WinXP.

Thanks. Any help would be appreciated.

Very confused. :sarcastic: You say you have a single 500gig drive and it is using raid??

Sorry if that was confusing. The system contains three hard disk drives - one 160GB PATA drive and two 250GB SATA drives. The SATA drives are configured as one RAID 0, 500GB drive. The configuration is done in the BIOS, which allows for either two separate SATA drives or one RAID drive.

I disabled all SATA drives in the BIOS in order to force SUSE to install on the empty portion of the PATA drive. This was successful. Then I turned on the SATA+RAID drivers in the BIOS again, which restored the RAID drive in WinXP. I now would like to have that RAID drive be available in SUSE.

Hope that clears things up.

Since Suse did not see the drive it did not know you wanted to mount it.

Are you booting ok into both windows and Linux?

If so, boot to Linux and post results

su -c “fdisk -l” ( that’s lower case L not a one)

Then we will see whats up.

Also to be sure you simply want to mount the Windows file system right. You are not planning on putting new partitions on the raid.

  1. I am booting into both SUSE Linux and WinXp just fine.

  2. Yes, I want to keep the NTFS format on the RAID drive. It has music & videos I want to keep.

  3. I tried the command su-c fdisk-l as superuser from a terminal. What I got back was "f ‘su-c’ is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf su-c

Not sure what this means.

There are spaces in that su command. Better cut and paste if you cannot easily see the spaces in the current font.

Ok space between su and - and quotes arounf the fdisk -l

But lets make it easier in a terminal type

enter the root password ( note this does not echo to the screen)

then type
fdisk -l

Thanks for your patience. I am an old guy and my eyes aren’t that great. I’m also not used to the small terminal font.

Here’s the result:

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xfb0cfb0c

Device Boot Start End Blocks Id System
/dev/sda1 1 9159 73569636 7 HPFS/NTFS
/dev/sda2 * 9160 19457 82718685 f W95 Ext’d (LBA)
/dev/sda5 9160 9421 2104483+ 82 Linux swap / Solaris
/dev/sda6 9422 12032 20972826 83 Linux
/dev/sda7 12033 19457 59641281 83 Linux

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd745d745

Device Boot Start End Blocks Id System
/dev/sdb1 1 60802 488392033+ 7 HPFS/NTFS

Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdc doesn’t contain a valid partition table

Looks like it doesn’t recognize the two 250GB drives as part of one RAID drive.

Yes it looks like Linux only saw the first of the two drives as NTFS. I don’t know if you can get Linux to work with this setup.

However I will comment on the RAID-0. It’s just concatenating the two drives to form a larger “drive”. This gives you no redundancy and actually increases the risk of failure since losing either drive loses the system. Maybe you could break it up into two drives C: and D: in Windows, each of which can be mounted in Linux. But I don’t know how to do this in Windows without a reinstall. The disadvantage is of course that you don’t pool the free space on C: and D:.

Actually, I’ve had RAID 0 drives on all my systems since the Pentium 233 and never had a failure. I like them because I can concatenate two slow drives into a fairly fast drive and they use space more efficiently. I think I’ve had these two particular drives running for about five years.

But in any case, it’s not important as there is nothing vital on this system. I plan to use it as a server on my home network and for the kids/grandkids to send/receive pictures and videos over the internet. If it goes down, no big deal. I normally back everything up on another system with a 2TB RAID 0 drive and another 2TB of individual drives(big power supply).

I don’t know how to mount this since the raid drives are not being seen as raid.

Is this hardware raid or BIOS raid (fake Raid).

You could try mounting a read only and see if it will work

Become root in a terminal by

su -

then make a mount point

mkdir /windows or what ever you want to call it

mount -t ntfs ro /dev/sdb1 /windows

Now see if the files show up in /windows

If they do come back and we will see about doing it at boot
If not tell use the errors

I think the problem will be that it won’t mount half of a filesystem. He’s using sdb and sdc in RAID-0 (striping), not RAID-1 (mirroring). It’s almost certainly fakeraid in the BIOS. The only chance of success is if Linux handles this particular RAID controller.

If it does not mount it does not nothing lost in trying. The one hope is that the partitions on sbc are unknown. So it might work. I certainly would not try writing anything to that partition. :stuck_out_tongue: