General :: Unable To Access Intel Fake RAID 1 Array In Fedora 14 After Reboot
Jan 6, 2011
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:
2xHDD 300GB RAID1 - OS part 2xHDD 1TB RAID1 - data part. Both arrays were created inside the bios-like setup.
During the installation of fedora I "checkboxed" only the 300GB OS raid and used it for the installation. Everything is ok with it. After installation finished and I rebooted, I tried to initialize my second RAID1, that's 1TB - I was able, it was OK, I created 1 max-size filesystem there and put some data in it. After reboot this filesystem didn't want to mount for some reason - so I commented it in fstab and to my surprise, when I reached linux - the partition for it doesn't exist!!! Here is some data:
My guess would be that I am not fully and properly initializing the second array, (it's marked as auto read only in cat /proc/mdstat) but I'm not sure how to proceed.
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 have a fedora 11 server which can't access the ext4 partitions on lvm logical volumes on a raid array during boot-up. the problem manifested itself after a failed preupgrade to fedora 12; however, i think the attempt at upgrading to fc12 might not have anything to do with the problem, since i last rebooted the server over 250 days ago (sometime soon after the last fedora 11 kernel update). prior to the last reboot, i had successfully rebooted many times (usually after kernel updates) without any problems. i'm pretty sure the fc12 upgrade attempt didn't touch any of the existing files, since it hung on the dependency checking of the fc12 packages. when i try to reboot into my existing fedora 11 installation, though, i get the following screen: (click for full size) a description of the server filesystem (partitions may be different sizes now due to the growing of logical volumes):
Code:
- 250GB system drive 250MB/dev/sdh1/bootext3 lvm partition rest of driveVolGroup_System 10240VolGroup_System-LogVol_root/ext4
[code]....
except he's talking about fake raid and dmraid, whereas my raid is linux software raid using mdadm. this machine is a headless server which acts as my home file, mail, and web server. it also runs mythtv with four hd tuners. i connect remotely to the server using nx or vnc to run applications directly on the server. i also run an xp professional desktop in a qemu virtual machine on the server for times when i need to use windows. so needless to say, it's a major inconvenience to have the machine down.
I need to access each drive of a RAID array in order to update the firmware - I am completely new to linux. I think there are probably some potential challanges along the way to get this "working" For example, it seems to me that the array may present itself to application code as a single device. I need to drill down into the RAID and talk to each physical device in turn via some sort of pass-through mechanism. I'm currently pretty lost - can anyone point me in the "right" direction
I had some issues with my RAID6 array (with 15 disks), where 5 disks got disconnected (each five disks is connected to the motherboard via 1 SATA cable), which brought down the RAID array. I fixed this problem via readding the disks and running the array:
Code:
mdadm -R /dev/md1
However, after rebooting, the array appears inactive, and I have to go through the same motions to fix this and make it active. The array is present in the /etc/mdadm/mdadm.conf, though also 2 other raid arrays (3 arrays total):
Code:
DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes
I have a 10x2tb disk array that i'm trying to build into a single software raid 5 i have tried this 2 times now the first it made it to 58.7% and the machine locked up and the array would not restart after a reboot. On my 2nd try all was looking good until about 50% i noticed that the speed dropped in 1/2 and that ksoftirqd/2 is taking up a lot of cpu (about 90%) the md0_resync and md0_raid5 are also taking 60-90% when the build started they took 7%. when i do a dmesg i see a lot of the message compute_blocknr: map not correct.
For a little info on the physical setup this is running on an Atom 510 with 2GB of mem the drives are connected to an addonics 4-Port RAID 5 / JBOD SATA II PCI Controller using the sil3124 chipset. I'm using 2 addonics 5X1 SATA Port Multiplier connected to the controller to get the 10 drives attached. All drive show up and don't seem to have any issues. I'm running a fully updated as of 3/20/10 version of centos 5.4
I will let this continue to run over night but i expect it to be locked up by morning if it follows what the last attempt did.
I've tried to install Fedora 11, both 32 and 64 on my main machine.It could not install as it stops on the first install window. I've already filed a bug but really haven't seen any feed back yet.The bug has something to do with Anaconda and the Raid array but I really can't tell.
I have an Intel Board (see signature). I am running intel raid software under W7 currently.It works fine. But, I'm wondering, when I attempt to install F!!, is my current raid set-up causing problems? Do I need to get rid of the intel raid software and use a Fedor/Linux raid program to manage the raid array??
I'm running 64bit Lucid. I've recently had a severe problem with my softraid (5) array, and have had to recreate the array to fix it. However this now means that something is up with GRUB/initramfs, and booting times out while waiting for the root device (md0) to be ready. /boot is on a normal partition, not the raid array itself. A friend of mine has rebuilt my initramfs file with the new UUID, but now I get the message: 'Kernel panic not syncing: VFS: unable to mount root fs on unknown-block (9,0)'.So my question is either how do I sort this error, OR how do I rebuild initramfs/grub in a way that will boot?
I'm trying to switch to a new RAID5 array but can't get it to boot. My disks:/dev/sda: new RAID member
/dev/sdb: Windows disk /dev/sdc: new RAID member /dev/sdd: old disk, currently using /dev/sdd3 as /
The RAID array is /dev/md0, which is comprised of /dev/sda1 and /dev/sdc1. I have copied the contents of /dev/sdd3 to /dev/md0, and can mount /dev/md0 and chroot into it. I did this:
Code:
sudo mount /dev/md0 /mnt/raid sudo mount --bind /dev /mnt/raid/dev sudo mount --bind /proc /mnt/raid/proc
[code]....
This completes with no errors, and /boot/grub/grub.cfg looks correct[EDIT: No it doesn't. It has root='(md/0)' instead of root='(md0)']. For example, here's the first entry:
Code:
### BEGIN /etc/grub.d/10_linux ### menuentry 'Ubuntu, with Linux 2.6.35-25-generic' --class ubuntu --class gnu-linu x --class gnu --class os {
Been attempting to install ubuntu on my Intel fake raid on a new PC.The installer sees the raid, but errors out:Quote:The ext4 file system creation in partition #1 of Serial ATA RAID isw_ehbgbddej_Volume0 (mirror) failed.This seem to be the EXACT issue described in this bug report:I read all the way down this bug report, and at the bottom it says:Quote:Launchpad Janitor on 2010-06-25Changed in parted (Ubuntu Lucid):status: Fix Committed → Fix ReleasedA few weeks ago, a fix was "committed" and "released". I had been working with an earlier 10.04 ISO, so I downloaded 10.04 from the web site today. Still the same problem.Maybe I'm just reading the bug report wrong? If it says the fix is committed and released, I would naively assume that it is fixed. Do I need to patch to apply the fix or something? Doesn't seem likely.
I have a NETGEAR ReadyNAS NV+ with four 1TB drives in a RAID-5 array. This is our primary file storage. This has previously been backed up to a hardware RAID-0 array directly attached to our Windows server. The capacity of this backup array is no longer sufficient. So the plan was, take a bunch of 200GB to 320GB drives (And a 750) I had kicking around, chuck them in a couple of old SCSI drive enclosures I have collecting dust, attach them via IDA/SATA-to-USB adaptors to a USB hub, attach that to the server, create a JBOD array spanning the disks, and back up the NAS to that. Performance is not an issue as this is just to be used for backup, with the idea being as near to zero cost as possible (Spend so far = NZ$100�ish).
The first hurdle I struck was Windows not supporting Dynamic Disks on USB drives (Required to create a spanned volume). At first I resisted using another machine (i.e. a machine running Ubuntu) as I didn't want to dedicate a piece of hardware to backing up the NAS. I then decided it would be acceptable to do this via a VM, which is what I've done.So I have 10.04 running under VMWare Server 2.0.2 under Windows Server 2008 R2. The disks are all presented to the VM. I wasn't sure if I was going to end up creating the array under LVM or something else, but I noticed Disk Utility has an option to create an array, so I tried that. When I add two 250GB drives, the array size is 500GB. When I then add a 160GB drive, the array size drops to 480GB. Huh? If I keep adding disks (Regardless of order) the final array size comes out at 1.8 TB, as per the attached screenshot. Now with the following drives, I expected something more like:
I installed OpenSuSe 11.2 x64 on my PC.It's not work will:After installation, the system auto login KDE GUI.but when I reboot(or shutdown and open) my computer. Message on screen meaning:"can't find bootable partition".My PC's hardwareMother Board: DFI 790FXB-M3H5(South Bridge: SB750)Hard Disk: WD 500G*2 Raid 0(via SB750 Chip function)Oh, I'm sorry, It's Fakeraid, not hardraid.
I have two 150GB WD Raptors stripped in an INTEL ICH10R RAID0 array. Windows 7 is installed on it in a 100GB partition, there is a 150GB secondary partition, a 100MB system reserved partition created by Windows 7 and there is about 25GB unallocated space to install a linux distribution.My problem is the fake ICH10R RAID which does work only at the moment for me with Fedora Core 13 : Ubuntu 10.04 breaks it but i do not like FC13 very much. So i Googled and Googled for installation problems on this fakeraid and dmraid is involved there is a bug in it at least in Ubuntu 10.04 and openSUSE 11.2, with 11.3 my RAID is detected -> i have a MD RAID popup.
My question is : How to install properly 11.3 on the space left on my fake RAID array without breaking anything although i have a full backup of my system. I don't understand anything of the partitioning part of openSUSE in general. Do i must activate MD RAID, i tried once and my NTFS partitions were not displayed but RAID was detected with the correct size. I am totally lost with this installer.
I ve got a SATA HDD which I use for storage connected to a (now quite old) RAID PCI card (HighPoint Rocket RAID 1520). Ive added another (blank) HDD, same brand and size to the PCI card. Ubuntu (10.04) can see both hard drives and access data. Id like to mirror (raid 1?) these HDDs. Looking around this forum Ive noticed quite a few people mentioning FakeRAID. Turns out that's not quite the same as software RAID. Given how cheap the 1520 was, I suspect it's FakeRAID rather than Hardware. Perhaps someone can confirm? Given Ubuntu can see both HDDs, would this mean it ll have the correct drivers to work with a hardware/fake raid? A common recommendation is to use mdadm to create a software RAID. How does this work for partitions accessed from multiple Operating Systems including Windows XP?
I installed RC1, and never touched the disks that were raided previously, and the attached image is what i see for my raid array that was previously working fine.
Recently while using a Highpoint 2310 (raid 5) I lost the mother board and CPU. I had to reinstall Centos and found it needed to initialize the array to function. Total loss of date. Question: If I use a true hardware card (3ware 9650se) and experience a serious hardware loss or the C drive can the card be installed with the drives on a new motherboard and function without data loss even if the OS must be reinstalled.
I've been, for some years, an happy user of Highpoint HPT374 based RAID cards, using RAID 5 with decent performances (constantly around 90 MB/sec in read, and 60 MB/sec in write ). Old Athlon mobo , with 2.6.8 kernel. Now the mobo is dead, so I've got an Asrock A330GC (dual proc with 4giga ram), installed Debian with kernel 2.6.26 and moved the controller and disks , and the performances have dropped to a painful 9 MB/sec in write, measured with dd of a huge file (interrupted with kill -USR1 [pidof dd]).
Read performances are still around 90MB/sec, using hdparm -t , repeated many times , figures are constantly around 90MB/sec. I suspect some libata issue , in old kernel the raid was seen as hdb, now is sdb, some driver(s) of the PATA disks may be responsible. I've used the driver, from Highpoint v2.19 , the latest driver is broken (causes kernel oops during format of raid), I've informed Highpoint.
Here some info : hdparm -i /dev/sdb : HDIO_GET_IDENTITY failed: invalid argument .
I have a software RAID array using mdraid that consists of two 1.5TB drives that I use for storage, the array is mounted at /Storage. I am running out of space in the array so I ordered two more 1.5TB drives to create a 4 drive RAID 1+0 array which will be 3TB big. My question is how do I create the new array and not lose any data?
The drives and partitions are sdc1, sdd1, and soon to be sde1, sdf1. I currently have 4 RAID arrays (md0,md1,md2,md3). I think I can create the RAID 1+0 array with the two new drives, copy the data from my current array to the new one, remove the old array, then add the two original drives to the new array. But I wanted to ask on here first to make sure my data doesn't go poof.
I'm trying to install SL6 to a pair of 2TB harddisks in a RAID 1 array. The problem is that when the "Formatting" progress window that says "Creating ext4 filesystem on /dev/mapper/pdc_eahgdeafbgp1" comes up it appears to eventually freeze. It's been like that for 6 hours without the progress bar moving at least. I have another identical system that I booted up using the gparted live cd to see if I could get any more information using that. I first created a 500MB ext4 partition and mkfs.ext4 ran almost instantly. I then tried 5GB and it seemed to take maybe about a second or two and worked fine. I then jumped up to 500GB and it's been running for about 5 hours now. I'm pretty sure that I remember the creation of an ext4 filesystem occuring extremely fast even for very large partitions, but this is the first time I've played with RAID.
I'm running a Debian homeserver, with a 3-disk (1GB each) raid 5 array using mdadm (the OS is on a separate disk).Now, smartmontools noticed some bad sectors on one of the disks, and I'm not sure what to do next (except for backup of valuable data).I found some articles on how to fix these sectors, but I'm unaware what the result on the whole array will be.
I am attempting to install Maverick on an older pc. It has (2) mirrored 153 GB SATA drives. I set aside 33GB for a linux partition, by shrinking the partition in Vista.
Choosing to "Install along side windows" is not an available option. I can only choose use who disk, or use empty area. I choose use the empty area, and the Ubiquity installer gets hung up when attempting to format the empty space as EXT4. When I scroll up on the output I notice some error messages referencing NTFS. When I use Gparted it shows a possible problem.
Quote:
Warning: The device /dev/sda1 doesn't exist ntfsresize v2.0.0 (libntfs 10:0:0 ERROR(2):Failed to check 'dev/sda1' mount state: No such file or directory Probably /etc/mtab is missing. It's too risky to continue. You might try an another Linux ditro.
Unable to read the contents of this file system!Because of this some operations may be unavailable.
The following list of software packages is required for ntfs file system support: ntfsprogs.
I ran chkdsk /r on the Vista partiton, in case there was a problem there. The issue still persists.
I'm renting a dedicated server with a company that claims that the server has 2 hard drives in a software RAID 1 array, but I need to make sure that the server really has the 2 HDD, and the size of the 2nd drive... how to do that ?? system is Centos 5.3
I have a home server running Openfiler 2.3 x64 with 4x1.5TB software RAID 5 array (more details on the hardware and OS later). All was working well for two years until several weeks ago, the array failed with two faulty disks at the same time. Well, those thing could happen, especially if one is using desktop-grade disks instead of enterprise-grade ones (way too expensive for a home server). Since is was most likely a false positive, I've reassembled the array:
Code:
# mdadm --assemble --force /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 mdadm: forcing event count in /dev/sdb1(0) from 110 upto 122 mdadm: forcing event count in /dev/sdc1(1) from 110 upto 122
[code]....
Right. Once is just a coincident but twice in such a sort period of time means that something is wrong. I've reassembled the array and again, all the files were intact. But now was the time to think seriously about backing up my array, so I've ordered a 2TB external disk and in the meantime kept the server off. When I got the external drive, I hooked it up to my Windows desktop, turned on the server and started copying the files. After about 10 minutes two drives failed again. I've reassembled, rebooted and started copying again, but after a few MBs, the copy process reported a problem - the files were unavailable. A few retried and the process resumed, but a few MBs later it had to stop again, for the same reason. Several more stops like those and two disks failed again. Looking at the /var/log/messages file, I found a lot of error like these:
Quote:
Apr 12 22:44:02 NAS kernel: [77047.467686] ata1.00: configured for UDMA/33 Apr 12 22:44:02 NAS kernel: [77047.523714] ata1.01: configured for UDMA/133 Apr 12 22:44:02 NAS kernel: [77047.523727] ata1: EH complete
[code]....
The motherboard is Gigabyte GA-G31M-ES2L based on Intel's G31 chipset, the 4 disks are Seagate 7200.11 (with a version of a firmware that doesn't cause frequent data corruption).
I'm currently using Windows Vista 32-bit on a RAID 1 array; I'm using the RAID provided by my motherboard so it's fakeRAID. Anyway, I'd like to do some C development under Linux but I'm not exactly sure how to go about installing it on a software RAID 1 array without messing up Windows. I'm not sure which Linux distro I'm going to install, so I'm hoping that information isn't important. Would I just resize my Windows partition and put Linux on the newly created partition? Do I have to worry about where Linux will put its bootloader or will it manage that on its own? I didn't mean software RAID, I meant fakeRAID.
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
I recently upgraded a server from Fedora 6 to Fedora 14. In addition to the main hard drive where the OS is installed, I have 3 1TB hard drives configured for RAID5 (via software). After the upgrade, I noticed one of the hard drives had been removed from the raid array. I tried to add it back with mdadm --add, but it just put it in as a spare. I figured I'd get back to it later.Then, when performing a reboot, the system could not mount the raid array at all. I removed it from the fstab so I could boot the system, and now I'm trying to get the raid array back up.
I ran the following:mdadm --create /dev/md0 --assume-clean --level=5 --chunk=64 --raid-devices=3 missing /dev/sdc1 /dev/sdd1I know my chunk size is 64k, and "missing" is for the drive that got kicked out of the array (/dev/sdb1).That seemed to work, and mdadm reports that the array is running "clean, degraded" with the missing drive.However, I can't mount the raid array. When I try:mount -t ext3 /dev/md0 /mnt/fooI get:
mount: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try
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.
I am traveling outside US and trying to watch netflix from my computer. However, it is blocked in my region. Is there a way to fake the IP address to looks like i am viewing the content from the US?
