Ubuntu Installation :: RAID 5 (Intel) Not Recognized
Jun 21, 2010
I have a system with: - 1 SSD "boot" drive - 3 HDDs in RAID 5. I created my RAID 5 set in BIOS - P6X58D motherboard/Intel Software RAID - Looks and works fine in Windows 7 (Ultimate) 64-bit. I installed Ubuntu 10.04 using wubi - both Windows 7 and Ubuntu systems are on the SSD THE PROBLEM Ubuntu does not appear to recognize my RAID 5 set - when it loads I see a "/dev/sd_ 10 failed" error (sd_=sda, sdb or sdc) along with "no such file or directory" - I can see my 3 HDDs in 'Disk Utility,' but the space/partition information is incorrect - I reinstalled all packages related to RAID (dmraid, etc.)
I have recently installed Ubuntu 10.04.1 lts server on my Intel "fakeraid" (software raid) (2x250 sata).To test my RAID 1 I turned off one HD and start the system.The first screen (Intel software screen) show Status = Degraded, but the system starts normally with just one HD.Then I turned off the system and turned on the HD again, so the first screen (Intel software screen) shows Status = Rebuild. If I enter in the software raid panel the folowing message is showed: "Volumes with "Rebuild" status will be rebuilt within the operating system"The system starts normally... but this message status stays permanently even I restart the system again
This question is going to flag me as being a bit green to Ubuntu, but I must confess that in 15+ years in I.T., I have never had such a hard time understanding the partitioning scheme. Here's where I'm at.
I installed from the 9.10 live CD and selected the option to use the entire disk. The system has an Intel raid controller built in to the motherboard and two 80GB hard drives in a mirrored configuration. The system has previously been used with both XP and FreeBSD and never had an issue with partitioning or, more importantly, getting the boot manager to work.
So the live CD partitioned my hard drives, installed all the software and mount points, and claims that everything is finished. When I reboot, no boot device is found. If I then boot again from the live CD and select the option to boot from the hard disk, it does and I am in fact typing this message from the system. However, nothing I can do will make the thing boot without the bloody CD.
I've spent hours trying to figure out how to make grub work, or how to fix the MBR but no luck. The drives don't show up as /dev/hda or as anything logical that I can discern, so I can't even construct a workable install-grub command. Doing a df gives me this:
[Code]...
which is not very informative, is it? FreeBSD was never such a pain to make boot.Frankly, I'm not very impressed that a clean install (non dual boot) on such a standard hardware configuration could be so difficult to make the boot loader work. Documentation on this subject is voluminous but very shabby. I have searched and searched and I cannot find any mention of hardware mirrored IDE or SATA drives, nor what dev they would show up as. Very frustrating. Every tutorial I've read on installing grub2 or grub just doesn't work, usually because the dev is not right.
Can anyone shed some light on this bizarre behavior and perhaps offer some advice that will allow me to boot this system without the use of a live CD?
Currently running F10 on a RAID1 software raid array in Linux (not hardware or BIOS). I used the F13 install disk to boot and selected install/upgrade. Problem is that the Anaconda portion never sees the RAID device.
I tried passing the "nodmraid" argument to the kernel during boot. Other research suggested that the auto=md switch should be appended to the mdadm.conf file. No results from either solution.
Anaconda does not see the /dev/md0 or /dev/md1 and consequently it only offers an installation option.
I set up an array of 2 hhd in raid0 using intel ICH7R, and i have a win7 installed on it. I'd like to have a dual boot with karmic, too. I googled a little bit and i found that it's not so easy as i thought. Are there anyone who's experiencing my same situation?
As I understand, Fedora 12 sets up Intel ICH (when set in BIOS) as mdraid instead of dmraid.I would like to setup my 2 SATA hard drives so ultimately my /boot partition is RAID1, my / (ROOT) partition is RAID 1, and my swap is either RAID0, or fstab referencing 2 partitions on 2 of the drives, both set with pri=0 (which supposedly is equivalent to striping of RAID0, performance wise).
Assuming Fedora 12 uses mdraid for my configuration in either instance, am I better of enabling, or disabling the RAID mode in the BIOS? This system is strictly Fedora--no dual booting, no Windows. Any performance gains; reliability benefits between either scenario?It's a Intel P35 motherboard with ICH9R. Storage configuration is either "AHCI" or "RAID"
I ran into some strange issues with dropping drives with the RAID set on in BIOS. When it was set, that gave me two md devices of md126 (RAID0, swap) and 127 (RAID1 split between / and /boot). I think I had md126p1 for the SWAP, and md127p1 for /boot and md127p2 for / Within purely software, i have:
/dev/sda1 RAID /dev/sda2 swap /dev/sda3 RAID
[code]...
I suppose unless the BIOS enabled RAID is supposed to be faster, I'll stick with a purely software route and keep the BIOS set to AHCI.
Installing new Intel server S5000VSA (Sapello) motherboard with RAID 1. Downloaded F10 32 bit DVD and run install. Everything works fine and select Samba and all that. Install completes but on reboot get a blank screen.
I know with Windows one has to load the RAID driver off the Intel driver CD, so guess that is the problem. But how do I do this in Fedora? Question: How do I get to select the Intel RAID driver in the install process? There does not seem to be any place to stop and make this selection. I tried selecting the Red Hat and Suze installs on the Intel configuration assistant but it then reboots and that is it. In Windows it would ask to insert the Intel driver CD but that does not happen. So I am stuck. I loaded Fedora some 3 year ago and like it but then it was not on a RAID setup. I created a VMWare install on my desktop and did the same install options and it works. So the DVD seems fine.
my onboard soundcard (hda-intel ALC662) is not recognized in my new computer. It works fine with other distros, but ubuntu just does not seem to find it:
cat /proc/asound/cards --- no soundcards --- lspci -vvnn:
I've just completed an upgrade from Fedora 8 to 10 to 11. I'm using a Gigabyte GA-G33M-DS2R/S2 MB with the intel G33/G31 graphics chipset. I've never been able to get a valid xorg.conf file with this card. The monitor is being recognized correctly, but when I go into system-config-display and select intel nothing happens. And when I manually edit xorg.conf, X won't start.
I'm having a problem with the installation of Ubuntu Server 10.04 64bit on my IBM xSeries 346 Type 8840. During the installation the system won't recognize any disk, so it's asking which driver it should use for the RAID controller. There's a list of options, but nothing seems to work. I've been searching the IBM website for an appropriate driver, but there is no Ubuntu version (there is Red Hat, SUSE, etc). I was thinking about downloading the correct driver onto a floppy disk to finalize the installation, but apparently no 'general' Linux driver to solve the problem here.
I have got a mid-aged server which i upgraded with a simple SATA-Raid-Controller with a VT6421A chipset.I attached two Samsung 750 GB Hard disks and created directly after the POSt screen a nice Raid 1 array. Ubuntu will recognize it as well as windows (which I would never ever use... ;-)).SuSE 11.1 (we need this OS for confirmity) will simply just recognize both disks in the partitions overview. The point "RAID" remains empty.
Are there any hints out there how I can enable the whole raid stuff in open suse? Do I need to integrate other drivers / modules to get thinks working?
It gets stuck at the splash screen(the ubuntu logo) However it can boot in failsafe graphics mode and it boots with no problem if my second display is connected. It freezes if I try to change my display settings and it tells me my graphics card is not recognized. I'm using Lucid Lynx. I tried to do a fresh start but grub loads before the ubuntu cd and/or usb drive.
Motherboard:Asus Crosshair Formula IV CPU:AMD Phenom� II X6 1090T Black Edition 3.2GHz RAM:Corsair Vengeance 8GB DDR3 1600MHz CL8 Dual Channel Kit (2 x 4GB) HDD: 1 Sata 750 GB Hard Drive HighPoint 3120 PCI-E TrueRaid Controller, 2x250GB set as Mirroring.
So everything is working good. I have windows on the 750 GB Sata hard drive, and OpenSuse 11.3 on the Mirrored raid setup. I have grub as the bootloader, it loads windows and linux without error. So i have 8 gb of ram installed, but i have room for another 8 gb. This is where the error starts. After i install the other 8 gb of ram, which is corsair vengeance as well, windows will boot, but not linux. When i remove the newly installed ram, linux boots no problem. I tried putting the ram back in, then reinstalling linux again, but as i go through the setup, linux doesn't recognize the RAID setup. Like i can see it there, but i can't use it, partitions don't show up.Now i remove the install cd and tried to start linux again, still error. The error it gives me goes like this:
>Trying manual resume from /dev/disk/by-id<...>-part2 >resume device /dev/disk/by-id/<...>-part2 not found (ignoring) >Waiting for device /dev/disk/by-id/<...>-part1 to appear: ............. >Could not find /dev/disk/by-id/<...>-part1 >Want me to fall back to /dev/disk/by-id/<...>-part1? (Y/n)
Wether i select Y or N, it takes me to a shell. I tried using fdisk in the shell to check if /dev/sda the linux setup has any partitions on it, and no it does not recognize any of it. When i use fdisk on /dev/sdb to list the partitions it works. So only the raid setup gets affected by the increase in RAM.
I'm trying to make things work on my laptop. Almost done, but there is one hardware issue left. I have a Intel HD4400 graphic card. But it seems that it is not recognized. I had an issue loading Gnome3.
Code: Select allGNOME 3 Failed to Load
Unfortunately GNOME 3 failed to start properly and started in the fallback mode.
This most likely means your system (graphics hardware or driver) is not capable of delivering the full GNOME 3 experience
Another thing : Code: Select all$ grep EE /var/log/Xorg.0.log [ 29.117] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
Also, if I go in "applications" ->"system tools" -> "Preferences" -> "System settings" and then in "Details, under Graphics I have "Drivers : unknown", "Experience : Fallback".
And as a consequence, I can't use dual-screen. If I plug another sreen, I have an exact copy, not even with a good resolution.
I search on the web for solutions, but I didn't understand much. I don't know what Xorg is, x-window, etc...
I have a server with an Intel S875WP1-E motherboard and 4 HD of 400Gb each. If i use the raid utility from the motherboard it doesn't appear during disk detection, so i disabled it. I've rebooted and launch installer from the DVD and it displays correctly 4 HD. I've configured them, installed the OS and installed GRUB in MBR (grub install /dev/sda /dev/sdb /dev/sdc /dev/sdd). But when i reboot it asks me to switch for a correct system disk.
I've look into BIOS configuration. If i make a raid array using the bios utility, i can choose any array in boot device priority, but if there is no array defined, i can't select anythig (but the DVD drive).
I tried to install the latest stable version of Debian (download yesterday : Debian Wheezy 7.4.0) on my new computer Fujitsu Celsius W530.The version installed is exactly this one (given by the commande "uname -a") :
PCNAME 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux => A Debian Wheezy 64 bit
I have a problem with the Intel ethernet card : I217-LM (the model was verified on the Fujitsu specifications and also on the Windows 8 I use on another partition).During the install procedure, Debian did not find the ethernet card.I continued the install without it and after I tried to make it found.I got a Linux driver in the Intel Web Site but I saw after that Debian loaded yet this driver (e1000e), so I did not install the driver from Intel (I needed to get linux-headers and to compil the files).
So when I force the system to load the driver, it gives no error but the device is still not found when I try to bringup the network interface.URL...
- understand why I see the Device (with "lspci" command) and the module "e1000e" (I tried also the "e1000" one) loaded with "lsmod" command ? - make the card work to allow my debian for connecting to internet ?
Here some commands which can show you the problem : Code: Select all~# lsmod | grep e1000 e1000e 120822 0 root@PC-DEV-JB-debian:~# ll /lib/modules/3.2.0-4-amd64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko -rw-r--r-- 1 root root 184K févr. 2 02:04 /lib/modules/3.2.0-4-amd64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
We ran out of space on our server hard drive, so I installed 2 x 1GB drives, set them up as a software RAID1 array, copied the contents of /home to it, mounted it as /home for testing. Everything OK, so I unmounted it, deleted the contents of the /home folders (don't worry, we're backed up), then remounted the array. Everything was fine until we rebooted. Now I can't access the array at all; during booting the error "mount: special device /dev/md1 does not exist" comes up twice, and manually trying toe same issue. The relevant line from fstab reads:
/dev/md1 /home ext3 defaults 0 0
However, using webmin shows only md0, the RAID0 device on which the OSD was originally installed. There is no /dev/md1 device file. The mdadm.conf file reads as follows:
# mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md0 level=raid0 num-devices=2 uuid=76fd4050:fb820568:c9bd3a59:ad3e70b0
So it's not listed; I'm assuming this is significant. Am I right, and whether I am or not, what can I do?
I shall start off by saying that I have just jumped from Windows 7 to Ubuntu and am not regretting the decision one bit. I am however stuck with a problem. I have spent a few hours google'ing this and have read some interesting articles (probably way beyond what the problem actually is) but still don't think I have found the answer.I have installed:
I am running the install on an old Dell 8400. My PC has an Intel RAID Controller built into the MB. I have 1 HDD (without RAID) (which is houses my OS install) and then I have 2 1TB drives (These are just NTFS formatted drives with binary files on them nothing more.) in a RAID 1 (Mirroring) Array. The Intel RAID Controller on Boot recognizes the Array as it always has (irrespective of which OS is installed) however, unlike Windows 7 (where I was able to install the Intel RAID controller driver) .Does anyone know of a resolution (which doesn't involve formatting and / or use of some other software RAID solution) - to get this working which my searches have not taken me too?
I have been thinking about upgrading my RAID setup from a pair of Intel X25s running the software based RAID included with ubuntu to four Intel X25s running off a PCIe based controller. The controller is an HP P400 which I know works great on ubuntu (I have other machines running it with SAS drives). My desktop has an Intel S5000XVNSATAR mainboard and I have an open PCIe v1.0 8x (physical) slot that is wired 4x. The controller is 8x and will fit fine. How much of a performance hit do you think I will see running this 8x controller in the slot wired 4x with four Intel x25s in a RAID 10? Will I have enough bandwidth with the 4x for those SSD's?
Short story: Correct driver for 10.1 for the raid on the Intel S3000AH board? Long story: This system crashed due (I think) to a bad memory module, had been running fine for 2 years, had been an upgrade from Suse9. The hardware is fixed but I get "GRUB" repeating on the screen when booting and that is all. I can't seem to find opensuse drivers for 10.1 (that is what I believe is on the system, I believe the data is still intact and don't want to compromise it if possible) It will not load the 10.1 drivers from the intel site, presumably (?) because they are for SLES, not opensuse. I can boot from a 9.3 CD with the drivers from the intel site, and can see the original partitions.
Well, when I run alsaconf, it finds my 82801H and I go on to setting it up, it says it will run, but it doesnt run.
Quote:
Now ALSA is ready to use.
For adjustment of volumes, use your favorite mixer.
But my song don't work, ..... works, but no sound in that, and i have tried running alsamixer to raise the volume to the peak.
I have a vague idea that, this sound card has difficulty in linux but all I get is 3 year old patches for gutsy gibbon and fixes that are non-slackware so I dont have the files and what not.
I have been trying, but never seem to understand why it says it works when it doesnt work.
Oh turns out, from thinkwiki, [url]
Its AD1984 actually, and it didn't work on 2.6.24.2 mine is 2.6.29.2 .
I recently bought a new system that has an Intel Matrix Storage Manager "RAID controller" (ICH10R/DO) on it. I'm a bit baffled over what this really is. I see at [URL] that this controller is supported by the Linux dmraid and mdadm commands and supported in the 2.6 kernel version for quite a while. This looks as though it is some sort of convergence of a brain-dead hardware chipset that requires software installed in the OS to manage it. Kind of reminds me of the wimpy Windows modems of the past. How I deployed. I set up two Seagate ST31500541AS disks as a mirrored pair in the hardware controller interface (CTL-I setup after POST).
I installed Fedora 12 in the usual fashion, though was confusing considering I expected a single "RAID device" to be seen by Anaconda. I went ahead and set up the two native /dev/sda and /dev/sdb as a mirrored RAID device on installation (mdadm under the cover). Recently, Palimpsest is insisting that I have a disk problem with "Disk has many bad sectors" error on /dev/sdb. When I run "dmraid -s" it tells me that the meta device is OK and I see no hardware errors in the messages log. I'm not having kernel panics as others seem to have had on RHEL 5.x.
I want to build a 6xSATA RAID 5 system with on of the disks as spare disk. I think this give me a chance of 2 of 6 disks failing without losing data. I am right? Hardware: Intel ICH10R First I will creat a 3xSATA RAID 5, after I will add the spare disk and after that I will add the others disks. This is what I think I should do.
[code].....
EDIT:I'm thinking in put LVM with the RAID 5. What are the advantages and disadvantages of it (LVM over RAID 5). It is safe? My MB (Asus P5Q) have Chipset Intel P45 ICH10R. What kind of RAID have it? Hardware RAID, fake RAID, BIOS RAID, software RAID? This are the specs of storage
1st I am relatively new to linux (but not to *nix). I have 4 disks assembled in the following intel ahci bios fake raid arrays:
2x320GB RAID1 - used for operating systems md126 2x1TB RAID1 - used for data md125
I have used the raid of size 320GB to install my operating system and the second raid I didn't even select during the installation of Fedora 14. After successful partitioning and installation of Fedora, I tried to make the second array available, it was possible to make it visible in linux with mdadm --assembe --scan , after that I created one maximum size partition and 1 maximum size ext4 filesystem in it. Mounted, and used it. After restart - a few I/O errors during boot regarding md125 + inability to mount the filesystem on it and dropped into repair shell. I commented the filesystem in fstab and it booted. To my surprise, the array was marked as "auto read only":
[Code]...
and the partition in it was not available as device special file in /dev:
I have installed Ubuntu on my m1530 since 8.04 and currently dual boot Win7 and 10.10. I would like to dual boot on my PC, but I have run into a problem. I am not a pro at Ubuntu, but this problem I can not solve by reading forums like I have in the past.
I realize this is a common problem, but I have noticed people having success.
I have a M4A87TD EVO MB with two Seagate drives in Raid 0. (The raid controller is a SB850 on that MB) I use the raid utility to create the raid drive that Windows7x64 uses. I have 2 partitions and 1 unused space. Partition 1 is Windows, partition 2 is for media, and the remaining unused space is for Ubuntu.
I am running ubuntu-10.10-desktop-amd64 off a Cruzer 16GB flash drive that was installed via Universal-USB-Installer-1.8.1.4.
My problem like so many others is that when I load into Ubuntu, gparted detects two separate hard drives instead of the raid. I read that this is because kpartx is not installed on 10.10. I then went in LiveCD mode and downloaded kpartx from Synaptic Manager. Gparted still reported two drives. I opened terminal and run a few commands with kpartx. I received an error. (Forgive me I didn't write it down, but I believe it said something about a communication error. I will try again later and see.)
Currently I am reflashing the Cruzer with a persistence of 4GB. I am not familiar with this process, but I understand that my LiveCD boot will save information I download to it. I decided to try this method because I was going to install kpartx and reboot to see if this made a difference.
I am looking for any suggestions on a different method or perhaps someone to tell me that the raid controller or some hardware isn't supported. I did install ubuntu-10.10-alternate-amd64 on my flash drive, but fail to get past detecting my CD-ROM drive since it's not plugged in. If this method is viable, I will plug it in. I also watched the ..... video were a guy creates Raid 0 with the alternated CD, but it wasn't a dual boot and didn't use a raid controller from a MB.
The situation: computer based on Asus P6T motherboard. Two RAIDS:
- 'boot', on motherboard built-in RAID controller (CentOS 5.5 installed on this RAID) - 'data' on 3dware RAID card
At one moment a CPU fan fails and the system halts. After the fan is replaced, BIOS informs it's reset and all the inner controller data are forgotten. After I switch it to 'RAID' mode, it remembers it was a mirror raid (RAID 1) installed, but the file system on it is completely trashed.
The 'data' RAID run by external controller isn't affected by the system failure. Three questions:
- is it worth trying to install OS on the rebuilt 'boot' RAID once again? Looks like if BIOS settings are lost for some reason, there's chance of completely losing RAID data - has someone encountered similar problem with built-in RAID nd was it possible to recover data? - will the software RAID be worth creating instead of using hardware RAID to replace the 'boot' drive?
Could any RAID gurus kindly assist me on the following RAID-5 issue?I have an mdadm-created RAID5 array consisting of 4 discs. One of the discs was dropping out, so I decided to replace it. Somehow, this went terribly wrong and I succeeded in marking two of the drives as faulty, and the re-adding them as spare.
Now the array is (logically) no longer able to start:
mdadm: Not enough devices to start the array.Degraded and can't create RAID ,auto stop RAID [md1]
Code: mdadm --create --assume-clean --level=5 --raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 As I don't want to ruin the maybe small chance I have left to rescue my data, I would like to hear the input of this wise community.
It's been a real battle, but I am getting close.I won't go into all the details of the fight that I have had, but I've almost made it to the finish line. Here is the set up. ASUS Z8PE-D18 mother board 2 CPU, 8 Gig Ram. I recently added an OCZ Agility SSD, defined a raid 1 virtual disk on the 1 terabyte WD HDD drives, which will holds all of my user data, the SSD is for executables.The bios is set to AHCI. Windows 7 installed fine, recognizes the raid VD just fine.
I installed Ubuntu 10.04 by first booting into try and mode, then opening a terminal and issuing a "sudo dmraid -ay" command. Then performing the install. I told it to install the raid components, and told it to let me specify the partitions manually. When setting up the partitions, I told it to use the free space I set aside on the SSD from the Windows 7 install as ext4 and to mount root there. Ubuntu installed just fine, grub2 comes up just fine, and Windows 7 boots with out a hitch, recognizing the mirrored partition as I indicated previously. When I tell grub to boot linux however, it pauses and I get the "no block devices found" message. It will then boot, but it does not recognize the raid array. After Ubuntu starts up I can run "dmraid -ay" and it recognizes the raid array, but shows the two component disks of the raid array as well. It will not allow the component disks to be mounted, but they show up which is annoying. (I can live with that if I have to)
I have fixed a similar problem before by setting up a dmraid script in /etc/initramfs-tools/scripts/local-top ... following the instructions found at the bottom of this blog:[URL].. To recap: My problem is that after grub2 fires up Ubuntu 10.04.1 LTS (Lucid Lynx), it pauses, and I get "no block devices found" It then boots but does not recognize the raid array untill I manually run "dmraid -ay". I've hunted around for what to do but I have not found anything. It may be some timing issue or something, but I am so tired of beating my head against this wall.
