So I decided to build a server using two HDDs and after checking the net I decided to go with Software RAID.Before I mess around and go ahead and buy two 500 GB HDD, I decided to try it out first in virtual box.(my system is F13 64bit with 4GB)
I set up a virtual machine with 2 X 10GB HDD.Mount the live CD (f13 32bit).Run regular install > choose custom layout and do as follows: SDA & SDB will both have Software RAID 500 MB and another software RAID of about 9500 MB I will have md0 /boot (sda1 & sda2 = 500 MB) And another md0 having LVM group loaded with / + SWAP I choose to install boot loader on md0 the first time and I receive the following error when I boot from HDD: FATAL: INT18: BOOT FAILURE I tried installing boot loader on sda same thing.
I have been messing around with F13 in VM VirtualBox for awhile now. I have read in some places that it is better to install F13 into its own partition on the hdd creating a dual boot system for, in my case, Vista and F13. Any truth to this? I have been having problems with system settings in F13 while using VB. i.e.: sometimes the system will see 3d support, other times it won't. Sometimes it will see ethernet eth0 and then other times it won't. All my hardware from my MB to Display is supported according to the documentation I have looked at.
I upgraded from F10 to F12 using preupgrade. The upgrade itself completed with no errors, but I'm unable to boot afterward.
Symptoms:...Grub starts, the initramfs loads, and the system begins to boot. After a few seconds I get error messages for buffer i/o errors on blocks 0-3 on certain dm devices (usually dm0 and dm2, but I can't get a shell to figure out what those are). An error appears from device-mapper that it couldn't read an LVM snapshot's metadata. I get the message to press "I" for interactive startup. UDEV loads and the system tries to mount all filesystems. Errors appear stating that it couldn't mount various LVM partitions. Startup fails due to the mount failure, the system reboots, and the steps repeat.
Troubleshooting done:...I have tried to run preupgrade again (the entry is still in my grub.conf file). The upgrade environment boots, but it fails to find the LVM devices and gives me a question to name my machine just like for a fresh install. I also tried booting from the full install DVD, but I get the same effect. Suspecting that the XFS drivers weren't being included, I have run dracut to create a new initramfs, making sure the XFS module was included. I have loaded the preupgrade environment and stopped at the initial GUI splash screen to get to a shell prompt. From there I can successfully assemble the raid arrays, activate the volume group, and mount all volumes -- all my data is still intact (yay!). I've run lvdisplay to check the LVM volumes, and most (all?) appear to have different UUIDs than what was in /etc/fstab before the upgrade -- not sure if preupgrade or a new LVM package somehow changed the UUIDs. I have modified my root partition's /etc/fstab to try calling the LVM volumes by name instead of UUID, but the problem persists (I also make sure to update the initramfs as well). From the device-mapper and I/O errors above, I suspect that either RAID or LVM aren't starting up properly, especially since prior OS upgrades had problems recognizing RAID/LVM combinations (it happened so regularly that I wrote a script so I could do a mkinitrd with the proper options running under SystemRescueCD with each upgrade).
I have tried booting with combinations of the rootfstype, rdinfo, rdshell, and rdinitdebug parameters, but the error happens so early in the startup process that the messages quickly scroll by and I just end up rebooting.
System details:4 1-TB drives set up in two RAID 1 pairs. FAT32 /boot partition RAIDed on the first drive pair. Two LVM partitions -- one RAIDed on the second drive pair and one on the remainder of the first drive pair. Root and other filesystems are in LVM; most (including /) are formatted in XFS.
I've made some progress in diagnosing the issue. The failure is happening because the third RAID array (md2) isn't being assembled at startup. That array contains the second physical volume in the LVM volume group, so if it doesn't start then several mount points can't be found.
The RAID array is listed in my /etc/mdadm.conf file and identified by its UUID but the Fedora 12 installer won't detect it by default. Booting the DVD in rescue mode does allow the filesystems to be detected and mounted, but the RAID device is set to be /dev/md127 instead of /dev/md2.
The arrays are on an MSI P35 motherboard (Intel ICH9R SATA chipset) but I'm using LInux software RAID. The motherboard is configured for AHCI only. This all worked correctly in Fedora 10.
I installed Fedora 12 and performed the normal updates. Now I can't reboot and get the following console error message.
ERROR: via: wrong # of devices in RAID set "via_cbcff jdief" [1/2] on /dev/sda ERROR: removing inconsistent RAID set "via_cbcff jdief" ERROR: no RAID set found No root device found Boot has failed, sleeping forever.
I'm waiting on a 2TB drive to come in so I can repurpose my gaming rig for Ubuntu. (Ok, its still going to be a gaming rig but I want to do 90% of my work/gaming in Linux) I'm thinking that rather than dual-booting I want to run the windows side of the house from a VM via Virtualbox.
Ubuntu runs fine with my hardware atm (have 10.10 installed on a secondary sata drive) and recognizes the RAID array that windows is currently installed on (gigabyte 870A-UD3 motherboard, I think Ubuntu's using fakeRAID to mount and view the drive, not very knowledgeable on raid and had the system built for me, but I know I'm using the gigabyte on-chip bios configuration for the raid)
I'd like to know:
1) if anyone knows of a good guide for dealing with this particular RAID controller beyond my owner's manual. (I read that 10.10 fakeRAID pretty much sets itself up)
2) should my win7 partition for the VM (I'd like it to be a dedicated partition so that I can boot into it if I have to do something in windows that Virtualbox can't handle) be on the Raid Array or the 2TB WD Caviar Green (low performance/power consumption drive)?
3. since I have a 2tb raid 0 array and a 2tb drive coming in, can I setup raid to mirror the contents of the 2 raid 0 drives onto the WD Caviar drive or do they all 3 have to be identical drives. (I think the other 2 are 1TB WD Caviar Black drives)
4. Any particular advice on partitioning? I was just thinking of /, /home and swap being separate on the raid but otherwise leaving the standalone drive as one big partition or splitting between windows partition and an otherwise large storage space.
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've been trying to setup RAID 10 with Fedora 11 on my desktop using this tutorial:[URL].. Everything has been going well, except when following the instructions and getting ready to format, it says I need to define / and boot partitions. This was never included in the instructions.
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.
Can anyone help me with how to create an init.d script that will startup a vm machine in virtualbox at boot? I found this script:[URL]..But it is for ubuntu. I am running fedora 12 x386 and using it as an Amahi server. Very cool, but it would be extra cool if I had a virtual windows machine startup when I booted up this server. Then I could just rdp into it when I needed something in windows.
I'm having a problem installing RHEL-5 on my system. I have Windows 7 installed so far on a Dell XPS workstation that came with hardware RAID 0. I have 2 x 500 gb hard drives. So I went in Win 7 and partitioned my disk to leave about 75 gb of unallocated space to install RHEL-5 on. I load the RHEL-5 DVD into my disk, restart my comp, and just follow installation steps. Use about 73 GB as an ext3 partition for the RHEL-5 and have about 2 GB reserved for swap space. RHEL-5 installs, and I'm all done. However, when I reboot the computer, the GRUB boot loader fails to load. I'm directly taken into Windows. How do I recover GRUB so I have the option of loading into RHEL-5?
Recently updated to kernel 2.5.32.11-99 and upon restart, failed to boot. Get stuck at a recovery prompt asking for root password or Ctrl-D to continue (which reboots system). I worked around this problem by reverting to the previous kernel 2.6.32.9-70. From what I can tell, with the newer kernel there is a problem with device enumeration of software raid volumes.
Wishing to test F12 final release, tried to install as guest on Virtualbox OSE/ Ubuntu 9.10. F12 installed text only and no X. Using 384Mb main and 16Mb video memory on 8Gb virtual hdd. Installed from tested DVD. F12 or Virtualbox? U9.10 guest install worked perfectly.
I am trying to take a look at Fedora for the 1st time and usually like to have a good tryout of a distro in VirtualBox.
Firstly, the live cd image boots up fine and seems to work ok except for a Kernel crash at the beginning of the gnome session, but it does enable basic usage within the live system.
But, when trying to do an actual hd install (still within VBox) Fedora 14 just keeps on crashing the VBox??, every install attempt just aborts, I have given the virtual machine a 20gb virtual hd, 2gb ram, 128mb video ram and have not applied any "unusual" extra settings. All versions of Ubuntu, Mint and PCLinuxOS work flawlessly within VBox.
Has anyone else tried installing into VirtualBox here?? (not just running the live environment)
I've wasted a good few hours with this, is it just that some distros dont like VirtualBox or is this indicative of what Fedora would be like on a real non virtual install??
ps, I have the latest VirtualBox fully updated and a flawless host (Mint 9), and perhaps I should add that I'm not a Linux expert and have only been using Linux for just under a year now.
Running VirtualBox 3.2.6 under some host OS (should be irrelevant which one, right?), I created a machine, intending to install Fedora 13 on it. Got the Fedora 13 Live CD iso image, and an 8.6 GB virtual hard drive, completely blank. I set the machine to boot off the Live CD image. The Live CD boots nicely and I get to its desktop. I open "Install to Hard Drive"...and nothing happens. No error message, zip, nada. Inspection of the system shows a series of odd file systems, but I have no clue what they are for and whether they're usable or not.
The sticky [URL] mentions that the blank virtual hard disk should be partitioned and formatted beforehand...So I did, using the Live CD's Disk Utility (Applications: System Tools: Disk Utility). Although the sticky states the small /boot partition should be ext2 or ext3, the Live CD installer proposes to reformat it as ext4. Shouldn't we have formatted it as ext4 right away, then? Also, the installer set the /boot partition's size to 524 MB, not 200 MB as recommended by the sticky.
OBSERVATION: This was not easy because VirtualBox sets the display to 800x600 at most, and the Disk Utility spills beyond those confines WITHOUT PROVIDING SLIDERS. It was sheer luck that the required buttons (create partition, format partition) were barely reachable (at the bottom edge of the screen). This is a serious problem, because increasing the VirtualBox display size can only be done *after* installation (see for instance[URL] - since this guest addition requires rebooting the guest OS, it probably won't stick to the Live CD).
Once those two partitions are prepared and the virtual machine rebooted, "Install to Hard Drive" works as expected.
OBSERVATION: It is absolutely inexcusable that the Live CD installer (Anaconda?) does not propose to do this partitioning and formatting for the user. It is even more inexcusable that it should fail without giving any feedback whatsoever to the user.
Aside: VirtualBox's guest additions does not work correctly (for 3.2.6 anyway). The Devices: Install Guest Additions menu merely mounts a CD image VBOXADDITIONS_3.2.6_63112) without any feedback (expected feedback because the menu ends with an ellipsis). The CD, once opened, has an Open Autorun Prompt button...which fails to do anything. Manually running autorun.sh also fails. I had to manually invoke VBoxLinuxAdditions-x86.run from a terminal to get anywhere. Even then I was unable to go higher than 1024x768.
I'm trying to get a fedora guest running reliable smp under VirtualBox 3.0.6. The VirtualBox manual says "Some Linux distributions, for example Fedora, ship a Linux kernel configured for a timer frequency of 1000Hz. We recommend to recompile the guest kernel and to select a timer frequency of 100Hz." So I tried recompiling the kernel. Being a responsible lad, when it came to setting the kernel specs:
Code: # Polite request for people who spin their own kernel rpms: # please modify the "buildid" define in a way that identifies # that the kernel isn't the stock distribution kernel, for example, # by setting the define to ".local" or ".bz123456" # # % define buildid .local %define buildid .rim_for_vbox I've successfully built and installed kernel, headers and firmware:kernel-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm kernel-firmware-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm kernel-headers-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm The system is working fine (well, so far). But trying to install the VirtualBox Guest Additions kernel add-ons still gives me
Please install the build and header files for your current Linux kernel. The current kernel version is 2.6.30.5-43.rim_for_vbox.fc11.x86_64. I'm pretty sure this is because my kernel doesn't match the development packagekernel-devel-2.6.30.5-43.fc11 (x86_64). So the key question is, how on Earth do I create a development package to match the responsibly-renamed kernel?
I have tried a few times already the following procedures: start a new installation (each time, I create a new VBox VM) with the Fedora 12 DVD iso attached to the DVD drive of the VM. I select the default setting, like US english, US keyboard, local time (GMT +8), standard installation ... etc). The installation process had been smooth to the screen the system asking for a reboot after installing something like 1100+ packages. Then I click the reboot button offered. The VM restarted but each and every time, it came up with the following error message:
Booting from local disk... FATAL: INT18: BOOT FAILURE
There was no other error message durint the installation process. It would be very much appreciated if some one can tell me what went wrong and how to solve it. I believe even I try again the same way, it will end up with same result. Is it a software or hardware problem? In case software problem, is it Fedora or VirtualBox?
I installed VirtualBox (and the virtualbox repo) a few months ago and it works brilliantly. The other day it informed me there was an update available. I downloaded: VirtualBox-3.1-3.1.2_56127_fedora11-1.x86_64.rpm from [URL]
Why doesn't yum update find these new versions of VirtualBox? Is the original repo file out of date? Here it is:
I have a virtual machine on VirtualBox.I had Fedora 11, all was well.I ran the "preupgrade" tool. It downloaded all successfully, it asked me to reboot.On reboot, it installed everything as it should. It finished by saying it was installed successfully and asked me to reboot one last time.Now when I start it, some text flashes rapidly on the screen. Then it stops.See attached file for screenshot of the last text shown.
I have a strange issue with my RAID5 array - it worked fine for a month, a couple days ago it didn't start on boot with mdadm reporting "Input/Output error" - I didn't panic restarted my computer, same error. Then opened a Disk utility and it reported State: Not running, partially assembled - don't know why, I've pressed Stop RAID Array and started it again, voila - it reported State: Running - I've checked components list and there was nothing wrong with it. So I run Check Array utility, waited almost 3 hours to finish it and it worked since than, till today's morning - I've started my computer, and here we go, same error.
See screenshots:
This is an initial state just after computer startup:
This is after I stop and start RAID5:
This is a components list:
I can see nothing wrong there yet not sure why mdadm fails on boot. I do not really like the windows solution I guess, when I check my array again, it will work fine again, but it then can fail in the same way without known reason.
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.
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.
trying to understand the two underlined sentences below I got to ask Step by step. I created a new group called usb. I inserted a usb printer and scanner. I tried to find the file usbfs and there is where get stuck already. I only can find a folder with that name. The sentence (3 -) makes almost no sense to me.
a) modify file /etc/fstab clear open terminal, go to etc, su gedit fstab
b) inserting a line yes I understand that!
c) the right path and the number corresponding the "usb" group :
i always run updates if i get prompted about it... this time i ran a couple or so updates and software updates and restarted, i realise my VirtualBox and Wine isn't running at all... i click on the icons but nothing fires up.. all my programs on Wine seem to fall under the same issue...
how do i view all the latest updates i just installed?
My USB-modem and my freerunner phone is no longer recognized by fedora. Last time this happened I just reinstalld Fedora because I had no id�a what caused the problem. But now I recognized that virtualbox was the last package I installed before the problem occured. I tried to uninstall virutalbox but the problem remained. Is there a way to reset all the network settings without reinstalling fedora?
I saw many linux OSes have a smooth stability with sun virtualbox.for example VBoxaddons already initially installed.I installed fedora 12 x86_x64 (within vbox in xp64bit)but only 800x600 resolution is avaible.Smooth Mouse jumping from Pc to vbox etc.
1.is there any good installer that have already packages initially installing for virtualbox ? 2.Which version listed below have x64 kernel?
I just tried to install Fedora 12 x_64 on a machine that is currently running Fedora 11 x_64. It's a new machine for use as a server and is running a Phenom II 4 core on a gigabyte M/B - 4GB RAM, onboard ATI graphics, an Adaptec 5405Z RAID Controller that is in the 16 lane PCIe slot, and 3 SSD SATA dives in a RAID 0.I installed Fedora 11 x_64 on this machine just last week and it went perfectly smooth. The install recognized the video hardware, controller card and the RAID, installed correctly, boots fine, runs solid.When I attempt to install Fedora 12 x_64 on the same machine, it does NOT recognize the controller, nor the RAID and doesn't seem to like the video hardware. I stuck on a floppy drive and made a driver disk from the Adaptec provided Linux drivers, but the install fails to mount the floppy when I try to add the driver during boot from DVD - although it tries. (It's possible that my floppy drive and/or disks are too old to be useful. Seriously, loading drivers from a FLOPPY? Most computers don't even HAVE one any more.Sheesh...). The video also seems squirrelly and works better using the "simple" video drivers.
Anyone got any clues on this. It seems odd that the newer version works less well than the previous one.Maybe I'll try a different .iso - CDs or a live version or something just to check - and maybe try an install on a different machine. Yes, I put the install DVD through the self-test and it passed. I have tried 2 different copies and both fail.LATER - tried with live CD - boots OK, splash screen is OK, after bootup finishes it looks like maybe it's trying to start a different video driver - then the screen goes black and stays that way. Tomorrow I may stick in a discrete video card and see if that makes any difference.
Still Later: I have tried discrete video card, tried moving the RAID controller to the 4 lane slot, tried to install a driver from floppy (still no go) and have tried noprobe on boot command line. Although the "noprobe" got the video to keep going (albeit at a low resolution) it STILL refuses to see the RAID controller. The LED indicators on the RAID card SEEM to be indicating that the card locks up during Fedora 12 boot, but I haven't checked on that just yet. Fedora 11 continues to boot and run fine on the same machine - I'm running it right now. as I type this.Later yet: Ubuntu 9.10 86_64 that was released a couple weeks ago DOES, IN FACT see the controller and the RAID when I run the install process. Looks like Fedora 12 is badly broken after all. (Damn those even numbered releases anyway.....{;>D)=) Guess I'm going to be "stuck" with either Ubuntu or Fedora 11 unless a solution appears pretty soon. I have sent an inquiry to Adaptec, but I'm guessing they are going to say, "we don't support Fedora linux except Fedora 5 and Fedora 6" as those are the only drivers they seem to have available
Friday 11/20 - I've attached a SATA drive to the same computer. By using the "basic" video driver from the install DVD I am able to install F12 to the SATA drive without issue - it installs fine, boots fine, runs fine. However, it still will NOT see the RAID controller. I tried installing the driver .rpm from the disk that came from Adaptec, but the vanilla linux driver doesn't seem to be effective. So far, Fedora 12 continues to be a big FAIL! as far as this particular machine goes.
