I have never used Linux before. In order to migrate from Windows I need everything to work.
I have an LiSI MegaRaid controller card with 7 SSD's in a RAID 0 that I have installed Ubuntu on
The problem is I have 4 HDD in a RAID 0 configuration on my Asrock 990fx Extreme 9 motherboard that all my movies are on so formating is out of the question.

I can see the 4 HDD RAID configuration in BIOS and if I unplug the
controller card and plug in a drive with windows on it windows sees the raid
configuration.

Disk Utility shows all fore drives

Can you pleas help me mount the RAID drive that I have my movies on?

Doesn't your hardware RAID have a setup/configuration utility in the BIOS? If you were using software raid I would tell you to look at mdadm but you don't.

Yes my RAID has a setup/configuration utility in the BIOS. I have set up all fore driver in Bios

Do not know if this helps.



Disk /dev/sda: 836.4 GB, 836411326464 bytes
255 heads, 63 sectors/track, 101687 cylinders, total 1633615872 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0009652e

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1566736383 783367168 83 Linux
/dev/sda2 1566738430 1633613823 33437697 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 1566738432 1633613823 33437696 82 Linux swap / Solaris

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xdcf17c97

Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xa996b1c8

Device Boot Start End Blocks Id System

Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xeefd06e2

Device Boot Start End Blocks Id System
/dev/sdd1 512 1073741311 536870400 7 HPFS/NTFS/exFAT

Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xa996b1ca

Device Boot Start End Blocks Id System
wayne@wayne-desktop:~$

So you have 7 drives in RAID 0 on a hardware controller that Ubuntu is seeing just fine and working well with.
You also have 4 drives in RAID 0 on your motherboard controller that Ubuntu is not recognizing but Windows is.

Is that correct?

If so, how did you configure the 4-drive RAID? Motherboards rarely have hardware RAID controllers on them, they're just a front end for software RAID, which your Windows OS set up and Linux probably won't recognize.

And why all the RAID 0s? RAID 0 shouldn't even be called RAID, it should be called "you-are-about-to-lose-all-of-your-data-AID". If the RAID is holding data that you don't want to lose, then RAID 0 is the absolute LAST option you should have chosen. I recommend you boot back into Windows, back up the data on your 4 drive RAID 0 to an external drive, wipe the RAID and reformat it as RAID 5 or 10 in Linux using mdadm, and then copy the data back.

Yes thet is correct.
I setup the fore drive ray in Raid 0 by hitting ctr f durring boot. the Raid configeration works flawlessly when I unplug the controler card and plug in a drive with windows instaled so why is it that Linux cannot see it?

I want Linux because it runs and runs and runs unlike windows were I have to do a weekly clean and reboot.

The more applications that are added and removed the larger the registry becomes. Windows NTFS does not write data to the hard drive in a very efficient manner and creates a need to derangement the drive often. Unnoticed temporary files build up over time and slow down the system. Windows tends to keep many services running in the background. The firewall and anti virus software needed to try and keep the system secure eat up a lot of resources. And that is just the beginning.
I thought if I had Linux to run my Plex and then do everything else on a virtual box it would give me the opportunity to learn Linux in a virtual environment and to do the things I need windows to do in a virtual environment

I am not getting any help from forum only stupid questions like “why all the RAID 0s? RAID 0 shouldn't even be called RAID, it should be called "you-are-about-to-lose-all-of-your-data-AID". If the RAID is holding data that you don't want to lose, then RAID 0 is the absolute LAST option you should have chosen. I recommend you boot back into Windows, back up the data on your 4 drive RAID 0 to an external drive, wipe the RAID and reformat it as RAID 5 or 10 in Linux using mdadm, and then copy the data back”

It is because I want what I want. Maybe I am asking the wrong questions.

I am going to reinstall windows until I can figure this out.

1 members found this post helpful.

You should look at fdisk -l output, how many drives you see? Then you should look at lspci -nnk output, what controllers you see? We need this information to get you out of that mess.

wayne@wayne-desktop:~$ sudo fdisk -l
[sudo] password for wayne:

Disk /dev/sda: 836.4 GB, 836411326464 bytes
255 heads, 63 sectors/track, 101687 cylinders, total 1633615872 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0009652e

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1566736383 783367168 83 Linux
/dev/sda2 1566738430 1633613823 33437697 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 1566738432 1633613823 33437696 82 Linux swap / Solaris

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xdcf17c97

Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xa996b1c8

Device Boot Start End Blocks Id System

Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xeefd06e2

Device Boot Start End Blocks Id System
/dev/sdd1 512 1073741311 536870400 7 HPFS/NTFS/exFAT

Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xa996b1ca

Device Boot Start End Blocks Id System
wayne@wayne-desktop:~$
----------------------------------------------------------------------------------------------------------------------------------------


wayne@wayne-desktop:~$ sudo lspci -nnk
[sudo] password for wayne:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] (rev 02)
Subsystem: ASRock Incorporation Device [1849:5a14]
00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16]
Kernel driver in use: pcieport
00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) [1002:5a18]
Kernel driver in use: pcieport
00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port E) [1002:5a19]
Kernel driver in use: pcieport
00:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port F) [1002:5a1a]
Kernel driver in use: pcieport
00:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port G) [1002:5a1b]
Kernel driver in use: pcieport
00:0c.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890S PCI Express bridge for GPP2 port 1 [1002:5a20]
Kernel driver in use: pcieport
00:11.0 RAID bus controller [0104]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [RAID5 mode] [1002:4393] (rev 40)
Subsystem: ASRock Incorporation Device [1849:4393]
Kernel driver in use: ahci
00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
Subsystem: ASRock Incorporation Device [1849:4397]
Kernel driver in use: ohci-pci
00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
Subsystem: ASRock Incorporation Device [1849:4396]
Kernel driver in use: ehci-pci
00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
Subsystem: ASRock Incorporation Device [1849:4397]
Kernel driver in use: ohci-pci
00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
Subsystem: ASRock Incorporation Device [1849:4396]
Kernel driver in use: ehci-pci
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
Subsystem: ASRock Incorporation Device [1849:4385]
Kernel driver in use: piix4_smbus
00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] (rev 40)
Subsystem: ASRock Incorporation Device [1849:439c]
Kernel driver in use: pata_atiixp
00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] (rev 40)
Subsystem: ASRock Incorporation Device [1849:0898]
Kernel driver in use: snd_hda_intel
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40)
Subsystem: ASRock Incorporation Device [1849:439d]
00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge [1002:4384] (rev 40)
00:14.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399]
Subsystem: ASRock Incorporation Device [1849:4399]
Kernel driver in use: ohci-pci
00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0]
Kernel driver in use: pcieport
00:15.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2) [1002:43a2]
Kernel driver in use: pcieport
00:16.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
Subsystem: ASRock Incorporation Device [1849:4397]
Kernel driver in use: ohci-pci
00:16.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
Subsystem: ASRock Incorporation Device [1849:4396]
Kernel driver in use: ehci-pci
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 [1022:1600]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 [1022:1601]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 [1022:1602]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 [1022:1603]
Kernel driver in use: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 [1022:1604]
Kernel driver in use: fam15h_power
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 [1022:1605]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:841f]
Kernel driver in use: nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio Controller [10de:0e0a] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:841f]
Kernel driver in use: snd_hda_intel
02:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
Subsystem: ASRock Incorporation Motherboard [1849:0612]
Kernel driver in use: ahci
03:00.0 USB controller [0c03]: Etron Technology, Inc. EJ188/EJ198 USB 3.0 Host Controller [1b6f:7052]
Subsystem: ASRock Incorporation Device [1849:7052]
Kernel driver in use: xhci_hcd
04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
Subsystem: ASRock Incorporation Motherboard [1849:0612]
Kernel driver in use: ahci
05:00.0 USB controller [0c03]: Etron Technology, Inc. EJ188/EJ198 USB 3.0 Host Controller [1b6f:7052]
Subsystem: ASRock Incorporation Device [1849:7052]
Kernel driver in use: xhci_hcd
06:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS 2208 [Thunderbolt] [1000:005b] (rev 05)
Subsystem: LSI Logic / Symbios Logic MegaRAID SAS 9271-8i [1000:9271]
Kernel driver in use: megaraid_sas
08:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403] (rev 01)
Subsystem: ASRock Incorporation Device [1849:3403]
Kernel driver in use: firewire_ohci
09:00.0 Ethernet controller [0200]: Intel Corporation 82583V Gigabit Network Connection [8086:150c]
Subsystem: ASRock Incorporation Device [1849:150c]
Kernel driver in use: e1000e
wayne@wayne-desktop:~$

This output is confusing, what is this 836.4 GB volume? A single drive? What is this 3000.6 GB volume?

Edit: You do know the motherboard RAID you have is not hardware RAID?

I have an MegaRAID SAS 9271-8i Controller card that I have 7 120GB SSD's in a RAID Configuration that i have installed Ubuntu on

I have 4 3TB HDD in a RAID 0 configuration on my Asrock 990fx Extreme 9 motherboard that all my movies are on

It is the drive with the movies that i want to mount

Hope this helps

Yes, it helps. You need to use dmraid utility ta assemble this RAID. It is fake RAID. Unfortunately I have no clue how dmraid works, never used it and never will. I'm sure Google helps you out. Opening another thread in these forums may help, too. Good luck.

1 members found this post helpful.

Thank you; I was about to give up hope

That's just because you don't want to hear it. The fact is you don't put information you care about on a RAID 0, end of story. You should expect to lose everything on a RAID 0 at any moment, that's the way it needs to be treated. You should have multiple backups of everything on a RAID 0, and you should not hesitate to use them. RAID 0 does have its uses, namely when you're after ultimate performance with zero regard for data integrity. That's fine, it has its applications, but RAID 0 is clearly at odds with your usage (archiving valuable data with no backup), which means you critically need to revisit what it is you're doing and why.

At LQ, we aren't just robots answering the exact question that's asked, because usually the person asking the question doesn't have a fundamental understanding of why they're asking what they're asking, or if they're even asking the right question. Part of what we do is try to get a deeper understanding of where the question is coming from, and if the poster is even approaching the problem from the right angle. Sometimes this means the original poster is told things that they don't want to hear, but it's for their own good.


Back to the original question - it does sound like dmraid is your answer, since you need to recover a fake RAID that Windows has been handling. Here are a few articles on the subject:
http://ubuntuforums.org/showthread.php?t=1776909
http://www.romaco.ca/blog/2012/05/28...y-with-dmraid/
https://help.ubuntu.com/community/FakeRaidHowto
http://techie.org/Blog/2010/09/03/ho...-isw-on-linux/
http://www.overclockers.com/how-to-d...ke-raid-array/

FWIW I have all my multimedia files on RAID-0 myself. Shall I lose it I can restore all files from original media (DVD, CD, I own all of them) - lots of work though.

I'm going to say it, raid 0 is utterly silly in your case unless you've left out some details. The 120MB/s odd speed the average hard-drive provides now-er-days is more than enough to watch your 1080P HBO "It's not porn" porn (I.E. Game of Thrones). However, by having raid 0 (Instead of singular drives), you're risking all your drives to fail in the case of just one actual physical disk failure. Absolutely silly, I'm sorry to say. You're not benefiting in the slightest by having half a gig per second sequential read speed, because, you're simply not processing the files that fast (I.E. 1 second video is still 1 second video, no matter if it's read at 1MB/s or 1000MB/s).

If you raid 5 that, my opinion completely changes, because, least then, you have redundancy, right now you're actively putting your files on the line for zero benefit.

That, being said of-course, by someone who has a 24TB setup sitting next to me filled with TV shows, so, I can't really argue, but, least it's raid 5.