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 working on a server and noticed that the to RAID5 setup is showing 4 Raid devices but only 3 Total devices. It's on a fully updated CentOS 5 system that only has three SATA drives, as it can not hold anymore. I've done some researching but am unable to remove the fourth device, which is listed as removed. The full output of `mdadm -D /dev/md2` can be see below. I've never run into this situation before.Anyone have any pointers on how I can reduced the Raid Devices from 4 to 3? I have tried
mdadm /dev/md2 -r failed
mdadm /dev/md2 -r detached
but neither work and since there is no block device listed I'm not quite sure how to get things back in sync so it's only seeing the three drives.
/dev/md2:
Version : 0.90
Creation Time : Tue May 25 11:07:04 2010
Raid Level : raid5
[code]....
Adding a kernel parameter to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nodmraid" (not 100% it should go there grub2 is new to me, but that is another story) I noticed the following error when running update-grub.
ERROR: ddf1: wrong # of devices in RAID set "ddf1_Series1" [1/2] on /dev/sdb No volume groups found
Now I have not a clue where it is getting ddf1_Series1 from.sdf1 is part of a RAID1 group that has mdadm RAID1 > luks > LVM
md6 : active raid1 sdi1[1] sdf1[0]
1465135936 blocks [2/2] [UU]
bitmap: 0/175 pages [0KB], 4096KB chunk
Errors bug me.. as I am new to grub2 was wondering if anyone has an insight into the error / where to investigate Still reading the grub2 / grub manuals.
First post so please excuse my lack of correct terminolgy/understanding/etc. Running Fedora 12 with the following software raid setup...
Mount Device Underlying Partitions
/ /dev/md0 /dev/sda1 /dev/sdb1
swap /dev/md1 /dev/sda2 /dev/sdb2
/home /dev/md2 /dev/sda3 /dev/sdb3
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.
[Code]...
I was running Ubuntu 9.04 Desktop on a headless Pentium 4 machine which is our file, mail, web & fax server. The two x 250GB SATA hard disks were in a RAID 1 array with full disk encryption. Ran the 9.10 upgrade via WEBMIN and it failed. I should have known then to copy over everything to a backup disk, but instead I rebooted.
On restart the machine accepted my encryption passphrase but promptly hung with a mountall symbol lookup error - code 127. So I can't start the machine to get at the disks, and using a Live CD is useless as it has no way to open the RAID array to get at the encrypted partitions. Although we have data backed up (as at last night) I'd hoped not to have to rebuild the entire server from scratch. But its looking bad.I have taken one drive out and plugged it into another machine (Hercules), and the partitions show up as /dev/sdb1 /dev/sdb2 /dev/sdb3.
If it weren't for RAID, I could open /dev/sdb2 the main partition) in Disk Utility and enter my encryption passphrase to get access. But RAID adds a layer of obstruction that I have not yet overcome. I used mdadm to scan the above partitions and created the /etc/mdadm.conf file, which I edited to show the 2nd drive as missing (rather than risk corrupting both drives). I activated the RAID array with mdadm, and cat shows:
Code:
root@HERCULES# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb3[0]
1815232 blocks [2/1] [U_]
[Code]...
I've been searching the web for hours but have yet to find someone with a solution to this situation. If anyone has a thought on how to access this disk I'd be pleased to hear from you. In the meantime I will start building a new (9.10) machine from scratch, without RAID, 'cos that's probably going to be necessary.
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 been having this problem for the past couple days and have done my best to solve it, but to no avail. I am using mdadm, which I'm not the most experienced in, to make a raid5 array using three separate disks (dev/sda, dev/sdc, dev/sdd). For some reason not all three drives are being assembled at boot, but I can add the missing array without any problems later, its just that this takes hours to sync. Here is some information:
[Code]....
I have been working on a network problem and have found what the actual problem is. For some reason on boot the netmask for my eth0 is set to be 255.255.255.255 In the network GUI application it is set correctly to 255.255.255.0
I looked in the following files and it is set there correctly too.
/etc/sysconfig/networking/devices/ifcfg-eth0
/etc/sysconfig/networking/profile/default/ifcfg-eth0
/etc/sysconfig/networking-scripts/ifcfg-eth0
If I check the box to "controlled by network-manager" the eth0 interface is started at boot but with a netmask of 255.255.255.255. If I uncheck this box then the interface does not come up at boot and I have to go to the GIU application to start it. It still comes up with the netmask of 255.255.255.255
I have to use ifconfig to set it to the right netmask and then everything works until I reboot.
"ifconfig eth0 192.168.1.65 netmask 255.255.255.0"
How do I get this to work properly? I need it to come up with the correct netmask.
I downloaded the Fedora live dvd iso file, burned it to a dvd. I was wondering if I forgot to do something or did I do something wrong. When I try to install from the dvd I get this error message, isoLinux: Disk error 80 , AX = 42A7 , drive 9F Boot Failed: press key to retry When I press a key to retry I get the same error. I also tried to install virtual pc and get not boot disk found.
View 3 Replies View RelatedAfter tweeking some graphics settings, and replacing some hardware, ubuntu won't boot. Being left in the X session (CTRL + ALT + f7), it's what looks like a log:
[Code]....
^ and that's where it hangs. So I went into ctrl alt f1, and logged in with my user/pass, and did the command: startx the screen flashes, and brings me back to a failed to open devices report.
[Code]....
I tried re-installing GDM, but turns out that the PC isn't actually online, hence unable to install GDM after uninstallation. So I downloaded the gdm .deb, and tried to install it from a USB flash drive, but I get dependency errors. I'm at a loss here, I could really use some help, this is the PC that has all my data on it, 450 GB +, I'd love to not have to transfer that over to a new installation!
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.
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 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've just installed Fedora (F13) for the first time, on a new HDD, to give myself a dual-boot system. So currently I have:
So, at the appropriate stage in the install menu, there is an option for where to install GRUB, and a drop-down to choose which drive is the primary BIOS boot drive.
However, in both cases, no other drive except my new sdc is visible. So, I can install GRUB to MBR of sdc, or to first sector of boot partition - but no option to put it to my primary boot drive MBR on sda.
Likewise, in the GRUB configuration page, if I go to Add another OS, the only option it gives me is my new Fedora install. It doesn't list the Vista OS on sda at all.
The result is that I can boot to either OS by changing the boot drive priority in BIOS.
I guess my question is this:
- is this expected behaviour from the installer, meaning that I'll need to configure GRUB manually somehow? (gulp ) or
- did I do something wrong in the install process? or
- is this some weird bug manifesting itself?
The ext4 file system creation in partition #1 of Serial ATA RAID isw_fjidifbhi_Volume0 (mirror) failed. Not sure what's wrong? How do I solve this? This happens after I enter my login details and click next. Then it fails on the install screen with this error.
View 2 Replies View RelatedI am having problems creating an diskless fedora 12 workstation. I have my boot server set-up, dhcp works, tftp works, pxelinux.0 gets sent. I have installed fedora12 locally [to hdd from dvd] on the affected workstation and then copied the whole / [root] to my boot server. Then I have installed the dracut-network package and a new kernel. I have copied the /boot/vmlinuz-xxxx and /boot/initramfs-xxxx.img to my bootserver's /var/lib/tftpboot/images/F12-x86_64/vmlinuz and ..../initramfs.img Boot options are listed below (the whole pxe config file):
DEFAULT menu
PROMPT 0
MENU TITLE KBS1 BOOT SERVER
TIMEOUT 200
[code]....
the "deskless" client's ip is set statically to 192.168.0.114. Is there anything I am missing?
I get this error when trying to install 10.04 "The ext4 file system creation in partition #1 of Serial ATA RAID isw_dceecfcacg_Volume0 (stripe) failed".I have a sony Vaio with 2x256gb SSD running RAID0.
View 9 Replies View RelatedIt'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.
I have installed Fedora 12 on my HP laptop which has got a NVIDIA graphics card. I have got latest F12 kernel 2.6.32 as well as default kernel 2.6.31.I have installed Nvidia Proprietary Drivers and modified grub.conf file for 2.6.32 kernel saying blacklist nouvaue so that it can load NVIDIA drivers ...After that I am able to successfully boot into 2.6.32 kernel with Nvidia Proprietary Drivers.Everything seems to be fine .. But suddenly today when I tried to boot into F12 2.6.32 kernel I got the following error
Code:
No Root Device Found
Boot Failed, Sleeping Forever
[code]...
I had Ubuntu 10.10. Now in the free space remaining in my hard disk, I installed Fedora 15. But unfortunately, Fedora failed to detect ubuntu. Now when I start my computer, grub automatically loads fedora and also doesnt display the boot menu. How can I boot ubuntu and let the grub display a menu of operating system choices?
My /etc/grub.conf file in fedora is as follows:
Code:
I have 2 Debian OS's and wanted to put Fedora next to it.
Install went ok, but after rebooting it says: "No root device found. Boot has failed, sleeping forever."
During install from the live CD I didn't "v" the boot (efi or something?) because I thought Grub would take care of everything.
Should I just reinstall again and choose the Fedora bootloader? Won't it mess up Grub?
I have just upgraded my FC12 installation to FC13. The initial boot failed (just blank screen). Second time I received 'selinux targeted policy relabel is required'. I let that run, but still the boot did not suceed.
I then went in to verbose boot and saw that the boot would hang at libvirtd. So I disabled libvirtd for anything above run level 1. Next boot failed at atd, disabled atd. Next boot failed at 'monthly Smolt checkin'.
At that point and booted in to single user mode and dissabled SELinux, thinking that was the cause of all the problems. That did not help.
The update process has also removed my previous kernels, so I can't test a different kernel
I downloaded fedora 14 64 image then created a bootable flash drive and put the image on the flash drive. I rebooted and tried booting from the flash drive and that's the message I received. What do I do?
View 6 Replies View RelatedAfter upgrading to Lucid 10.4, I find that after booting I can no-longer auto-mount any USB drive when they are plugged in. They simply doesn't appear on the desktop as they did. Swap my PATA drive back to the one with 9.10 still installed on it is well.However, if I have USB drives plugged in before boot, they appears on the desktop, but are not auto-mounted as previously. Also when I click on any drive icon for the first time there is no response. Try again (on any drive) an the devices will all auto-mount revealing their contents in the window that subsequently opens. Everything them seems fine. I can unmount and remount at my leisure with any number of devices.
I do not have the problem of root only access that others have mentioned. I have played with usbmount and pmount as others have suggested, to no avail. They have both been removed.I have the HAL installed as default, and have already ecked media_automount_open for Nautilus on the gconf-editor.Disabling the floppy in the BIOS has not effect and I do not use autologin option.With (say) two USB drives attached, whether the devices are recognised at boot or not after boot,lsusb reveals:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[code]...
I have created software raid 5 configurations on the second harddrive its working fine and i have edited fstab file for auto mounting when it reboot but when i reboot the computer raid doesn't work i have to re-create the arrays by typing "mdadm --create" command again and mount again manually ,is there anywhere i can do this once without retyping the commands again after rebooting and i am also using redhat 5
View 1 Replies View RelatedI found a workaround of sorts. It looks like this is related to a 9.04 bug [URL] and the loopback workaround brings back the array. It is not clear how I will handle this long term.
Note: before using this technique, I used gparted to tag the partitions as "raid". They disappeared again on reboot, so I had to do it again. I am not sure how this is going to work out long-term
Note: I suspect some of this is related to the embedded "HOMEHOST" that is written into the RAID metadata on the paritions. The server was misnamed when first built and the name was changed later (cerebus -> cerberus) and the old name has surfaced in the name of a phanton device reported by gparted - /dev/mapper/jmicron_cerebus_root
I have a mythbuntu 9.10 system that I have upgraded from 8.10 to 9.04 to 9.10 in the last 2 days. I am on my way to 10.x, but need to make sure it works after every step.
The basic problem is that in its current incarnation, it is not recognizing the underlying partitions for one of the RAID devices, and therefore not happy.
As a 8.10 system I had 2 raid devices:
/dev/md16 -> /dev/sda5 and /dev/sdb5
/dev/md21 -> /dev/sdc1 and /dev/sdd1
/etc/fstab looked like this (in part):
/dev/md16 /var/lib xfs defaults 0 2
[Code]....
I don't *really* want to repartition the drive as there is a small amount of data loss between recent backups and what is on the drive, plus it would take me 2 days to move the data back.
I've got a Gentoo box that I'm interested in switching over to an Ubuntu box.
I currently have the partitions laid out using a mixture of RAID (mdadm) and LVM2, as specified in this document [1].
Ideally I'd like to just wipe out the non /home partition, as it's got data I'd like to keep.
Is it possible to reuse the current setup, or do I need to restart? vgdisplay, vgchange -a y, etc don't yield any results from the Ubuntu LiveCD, and I'm wary to run any commands that might wipe my data.
[1] [url]
My old server machine running Ubuntu 6 experienced hardware failure, so I built a new machine with spare parts and decided to install 10.10. I used the 2 HDDs from the old machine and decided to use existing partitions for the 10.10 installation. I specified the existing partitions on a 250 GB PATA drive for root, /boot, /home, and swap. For some reason when I booted up 10.10 for the first time, the other HDD (750 GB SATA) was mounted as /boot. I never specified the second drive to be used for anything during the installation, so I have no idea why this happened.and how can I change the mount point for /boot? I would like the highlighted partition in the attached screenshot to be /boot. I really hope nothing on the 750 GB drive was overwritten in this whole process, because it contains all of my photo and video backup.
View 1 Replies View RelatedI just updated my server from Ubuntu 8.04 to 10.04 and now it cannot go past grub, at boot time, it would "give up waiting for root device", asking me to check whether I gave the right "root=..." or if I should increase the "rootdelay=..." in the command line argument and end up with the initramfs.
The machine is a Dell Poweredge 2900 with a HW RAID controller (I hope that should not matter, but just in case...). I tried to follow the instructions there to make sure grub is setup correctly, but without any luck.
Below is the output from the bootinfoscript (while running on the LiveCD). Anybody has any idea what can be the problem or what I could do to debug this ? I am running out of ideas.
[Code]...
One question: should F13 mount all attached USB devices after boot automatically? I guess it should. However, what I've experienced is that after boot and login, my USB modem + flash memory is not mounted. I need to manually unplug it and plug it again, and then it's mounted
View 1 Replies View Related