Fedora Installation :: I2O Controller - No Volume Groups Found Volume Group "VolGroup00" Not Found Unable To Access Resume Device
Apr 8, 2009
Dual PII 400, 512Mb with a Promise SuperTrak 100 IDE Array Controller. At present I have only one drive on the controller, configured for 1 JBOD array. I install FC9 with no problem. New partition is created and formatted, Grub is installed, and then... Grub is found and booted, but then I get:
Reading all physical volumes. This may take a while... No volume groups found Volume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) mount: could not find filesystem '/dev/root' I can boot in rescue mode, chroot to the installed system. I changed the kernel boot parm "root=/dev/VolGroup00/LogVol00"
View 2 Replies
ADVERTISEMENT
Feb 2, 2009
I already know "what" my problem is, however I am having difficulty fixing it. I recently upgraded our companies server to a HP ML150; decided to upgrade to FC10 hoping it would go smooth and it is not. It does not detect the SATA drives after the installation.
I get.
"Volume Group "VOLGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01
mount: error mounting /dev/root on /sysroot as ext3: No such file or directory
I know the problem is that my SATA is not enabled in the kernel or grub, but I don't know how to fix this. My internet searches are coming up a little short and LIVE discs are not working so I am having trouble figuring this out.
View 3 Replies
View Related
Nov 13, 2009
I have a dual boot system running FC8. I had a problem with an uninstaller on the Windows side that affected both the drives on the Windows and Linux sides. It froze my Linux archive drive. I removed the drive, and was able to boot the Windows side from a recovery disk, but not through Grub. I can't access Grub, but can start the Linux boot process with SuperGrub. The boot process gives the following errors:
No Volume groups found. Volume group "VolGroup00" not found. mount: could not find file system 'dev/root'.
View 4 Replies
View Related
Sep 29, 2009
This is my development virtual machine, I had Centos 5.3 on it and a lot of stuff I really can't afford to lose.
First off I'd like to say if there is any method anyone knows of recovering information off a VMWare disk, I'd love to trash it. I've already tried the drive mapping in VMWare workstation but only the boot partition comes up and I need /home and /etc.
I was screwing around with the LVM size of the disk and totally screwed it up. I can see the two partitions on /dev/sda, /dev/sda1 as the small partition and /dev/sda2 as my large data partition (the one I need access to).
If anyone could guide me into getting my data off or rebuilding my LVM to get it booted again that'd be amazing.
View 1 Replies
View Related
Sep 20, 2010
I am trying to extend my / size as its full. Well the volume group is VolGroup00 & logical volume is LogVol00 but when. I run the command vgextend VolGroup00 /dev/sda8. It says volume group not found. Can it be because I have WindowsXP in my /dev/sda1, which falls under same Volgroup??
View 1 Replies
View Related
Mar 20, 2011
I just imaged my RHEL 4 system that was running on a Dell Poweredge 2950 server using Acronis software and I restored the image to a VmWare virtual machine.
Dell Poweredge 2950 - RAID 5
VmWare - using ESX 4.0
OS - Red Hat Enterprise Linux 4 ES Update 5 x64
kernel - 2.6.9-55.0.9.ELsmp
I'm getting the following when I try to boot on the new virtual machine. I'm thinking it has to do with the fact that it's new hardware and it's having trouble either finding the right drivers or pointing to the correct place.
"No Volume Groups found
Volume Group "Volgroup00" not found
ERROR: /bin/lvm exited abnormally! (pid505)
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!"
I was able to boot into Linux rescue mode using the boot CD. Then I typed:
#chroot /mnt/sysimage
Here's all the info from the commands I typed:
#ldd /bin/bash
libtermcap.so.2 => /lib64/libtermcap.so.2
libdl.so.2 => /lib64/libdl.so.2
libc.so.6 => /lib64/tls/libc.so.6
/lib64/ld-linux-x86-64.so.2
#uname -a
Linux localhost.localdomain 2.6.9-89.EL x86_64
#df -h ....
I've tried the following:
1. mkinitrd -v -f /boot/initrd-2.6.9-55.0.9.EL.img 2.6.9-55.0.9.EL
2. modified the device.map to point to /dev/sda3
3. changed the SCSI controller in Vmware to use BusLogic instead of LSI Logic. (didn't work because I'm running 64 bit.. gave me an error message)
4. grub-install --recheck /dev/sda
5. tried booting to differerent OS versions (i.e. 2.6.9-55.0.6, etc.). I tried all of the versions listed in the boot menu.
None of these worked.
View 2 Replies
View Related
Jul 21, 2009
I made an image of a server(A). It did not work because It did not see /dev/sda. So I used another cd from indentical sever(B), cd which had work. Then mounted the nfs copy the image over. Server(B) had slightly older version of sles. And its not using lvm. But point is it had appropriate driver in the image cd.
Now situation is, This new image copied ever thing over.(I can mount it using LIVE CD). But When I boot up server it wont see vg volume group. I believe scsi driver is missing.After booting from LIVE CD I chroot in root used yast to add initrd modules, qla2xxx, mptbase, mptscsih(other server(B) had those). Still when I reboot it, it get stuck saying
Code:
No volume groups found
unable to find volume group
waitnit fot device /dev/vg1/root
to appear .... not found device nodes:
.....
......
.....
No root device found. exiting to /bin/sh
sh: cant access tty; job control turned off
View 1 Replies
View Related
Jan 18, 2010
I have run into some serious problems trying to start up RHEL AS4. I am trying to install Oracle on this box which by the way is running as a guest OS through VirtualBox. I was running with it fine yesterday. I was doing the prerequisites of updating the /etc/sysctl.conf file with additional kernel parameters. Prior to that I added another scsi virtual disk and extended a PV and left it at that for the night. I am since come back today and trying booting and am getting the following errors:
Volume group "VolGroup00" not found;
Couldn't find all physical volumes for volume group VolGroup00;
Couldn't find device with UUID "Some UUID of the device";
ERROR: /bin/lvm exited abnormally! (pid 318);
mount: error 6 mounting ext3;
mount: error 2 mounting none;
switchroot: mount failed: 22
umount /initrd/dev failed: Z
kernel panic - not syncing: Attempted to kill init!
I have tried running in rescue mode and it can find volume group VolGroup00. I also have installed Storage Foundation which includes veritas volume manager and other various veritas components. Does anyone have a clue what I am supposed to do here to get RHEL up and running again? I am running kernel version 2.6.9-42.EL if that helps as well.
View 3 Replies
View Related
Oct 5, 2010
Before creating this topic I googled a lot and found lots of forum topics and blog posts with similar problem. But that did not help me to fix it. So, I decided to describe it here. I have a virtual machine with CentOS 5.5 and it was working like a charm. But then I turned it off to make a backup copy of this virtual machine and after that it has a boot problem. If I just turn it on, it shows the following error message:
Activating logical volumes Volume group "VolGroup00" not found Trying to resume from /dev/VolGroup00/LogVol01 Unable to access resume device (/dev/VolGroup00/LogVol01) ... Kernel panic ...! During the reboot I can see 3 kernels and if I select the 2nd one the virtual machine starts fine, it founds the volume group etc. (But there is also a problem - it can not connect the network adapters.) So, it is not possible to boot it with the newest kernel (2.6.18-194.17.1.el5), but it is possible with an older one (2.6.18-194.11...)
I looked into GRUB's menu.lst and it seems to be fine. I also tried #mkinitrd /boot/initrd-2.6.18-92.el5.img 2.6.18-92.el5 no luck! Yes, I can insert DVD .iso and boot from it in "linux rescue" mode.
View 18 Replies
View Related
May 5, 2011
I'm working on a kickstart install to automate a lot of monotony doing installs. When i use the kickstart install i get an error on boot saying "File based locking initialization failed" "no volume groups found". Then it proceeds to boot up with no issues and appears to work just fine. Below is the section of my ks.cfg for creating the partitions: %include /tmp/partition.cfg is included where the partition info usually occurs. The user is prompted in the pre script for how large they would like the partitions to be and then the script below creates the included file with partition info
[code]...
View 3 Replies
View Related
Aug 7, 2015
This is a problem about linux-kernel-3.16-0-4-amd64 and LVM, I guess. I decided to write this here in case other users who installed their debian system with encryption enabled experience this problem with a recent kernel upgrade.
I use debian jessie. Today I gave the command:
Code: Select allapt-get upgrade
There was a linux-kernel upgrade to 3.16-0-4-amd64 among other packages to be upgraded.
After this upgrade my computer cannot boot anymore.
I get following error:
Code: Select allVolume group "ert-debian-vg" not found.
Skipping volume group "ert-debian-vg"
Unable to find LVM "volume ert-debian-vg/root"
Volume group "ert-debian-vg" not found
Skipping volume group "ert-debian-vg"
Unable to find LVM "volume ert-debian-vg/swap_1"
Please unlock disk sd3_crypt:
And it does not accept my password.
I used rescue environment on debian jessie netinst iso and decrypted the partition and took a backup of my /home. Now I have not much to lose if I reinstall my system but I still want to fix this problem if possible.
I have reinstalled the kernel using debian jessie netinst rescue iso but nothing changed.
I have Timeshift snapshots located at /home/Timeshift but timeshift --rescue command cannot find a backup device, it sees the device as crypted. If I could restore a snapshot it would be very easy to go back in time and get rid of this problem. It would not be a real solution, however.
There is not any old kernel option in GRUB menu. So removing the latest one does not seem as an option.
View 4 Replies
View Related
Jul 2, 2011
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.
View 3 Replies
View Related
Jan 22, 2011
I don't know much about lvm and I've managed to screw up a drive. I had a 500GB drive with FC14 on it and I wanted to copy over a load of data to my new 1TB that was replacing it. I set up my new install the same way as the old...including the same volume names (error number 1 I think) I successfully mounted the old/500GB drive (using vgscan and vgchange -a y etc.) using a laptop (running FC13) and an external hdd cradle. I could access the files I wanted but this wasn't the machine I wanted to copy them to (I was doing this while waiting for the install to finish on the new drive).
When I tried the same process on the new install I found that having two lvm with the same name meant I couldn't mount the external one. So I opened the disk utility (palimsest) and was going to change the name of the old volume group but it wouldn't let me do that. I then thought maybe I could get away with just changing the name of the partition where the files were and maybe I could add it to the mounted group or something so I changed it to lv_home2. This changed the name of my new/1TB lv_home to lv_home2 as well. So thinking that wasn't the answer I just changed the name of the new lv_home2 back to lv_home.
From that point on I haven't been able to see the old drives partitions (the new volume group still works so far). I has a physical volume but the volume group and volume names are gone from view. When I try to vgscan on my main computer or the laptop I had it working on earlier I get:
[Code]....
View 3 Replies
View Related
Feb 18, 2010
I am not well versed in using Ubuntu. I was using Win XP Pro SP3 on my old machine. I decided to make the move to Ubuntu. No problem since all files on the primary drive of the old machine were just OS related. I kept all of the important stuff (music, documents, reg codes, etc.) The computer had no problem importing the songs on the external drive to the music library. I am playing songs and loving it. Now the problem... when I am starting with ubuntu I don't find the drive and I can't mount it.
I get a box stating:
You are not privileged to mount this volume
DBus error org.freedesktop.DBus.Error.NoReply:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
View 5 Replies
View Related
Aug 22, 2010
im stock in here after recompiling my kernel
Quote:
[URL]
View 1 Replies
View Related
Jan 26, 2010
I'm trying to move an existing FC10 install (created by someone else) from a 160GB WD1600AAJS SATA disk to a 160GB WD1600AAJB PATA disk (cursed trend of horizontally mounting SATA connectors at the end of the motherboard means the latest rev mobo doesn't fit in our enclosure!). I've used DD to copy the disk image from one to the other, but when attempting to boot, I get the following error:
Code:
Unable to access resume device (UUID=946f216f-0c24-4b02-a996-f42059970de7)
mount: error mounting /dev/root on /sysroot as ext3: no such file or directory
That particular UUID maps to sda2, which is the swap partition. Interestingly, both the SATA and PATA disk come up as /dev/sda on the motherboard. I kind of grok that the UUIDs are substitutes for directly naming the disks, and that they're referred to in fstab, initrd-2.6.27.12-170.2.5.fc10.i686.img, and in /dev/disk/by-* I'm guessing the problem is that the GUIDs (at least the one for swap) are no longer the same. How are they assigned to the partitions during boot?
I tried doing
Code:
swapoff -a
mkswap /dev/sda2
swapon -a
and put that new GUID in fstab and into initrd-* (using some steps I found elsewhere on how to gunzip/rezip it).At that point, I get a kernel panic on boot
Code:
Kernel panic - not syncing: CFS: Unable to mount root fs on unknown-block(0,0)
So I'm guessing that the other UUUDs have changed as well and I need to update them. How would I figure out what they are? I suppose I could change the references to /dev/sda*, but I didn't build this original image and I'm thinking whoever did had a good reason to go with UUIDs.
View 10 Replies
View Related
Dec 1, 2010
I'm rearranging a bunch of disks on my server at home and I find myself in the position of wanting to move a bunch of LVM logical volumes to another volume group. Is there a simple way to do this? I saw mention of a cplv command but this seems to be either old or not something that was ever available for linux.
View 2 Replies
View Related
Jul 11, 2011
I'm hoping, now that I've recovered my partition tables, how to rebuild my LVM volume group. The trouble is that one of the volumes lost its partition table, and after rebuilding the table, LVM can no longer identify the drive. I'm trying to rebuild the 'fileserver' volume group.
pvscan produces the following:
Couldn't find device with uuid 'jsZAMq-LSa1-87Zb-WoGs-oi6v-u1As-h7YZMl'.
PV /dev/sdc5 VG dev lvm2 [232.64 GiB / 0 free]
PV unknown device VG fileserver lvm2 [1.36 TiB / 556.00 MiB free]
PV /dev/sda1 VG fileserver lvm2 [1.36 TiB / 556.00 MiB free]
Total: 3 [2.96 TiB] / in use: 3 [2.96 TiB] / in no VG: 0 [0 ]
View 2 Replies
View Related
Mar 18, 2010
How do you actually remove and install kernel when the system is not booting.
View 4 Replies
View Related
Oct 22, 2009
Fedora 11. I am trying to setup kickstart so it lays out a mirrored volume group. I have 2 disks sda and sdb. I want a primary partition on each disk 200mb in size for /boot. This is to be mirrored onto raid device md0 (raid 1). The rest of each disk is to be setup partition which grows to use the remaining space, and is also mirrored (raid 1) md1. Onto md1, I want an LVM volume group called rootvg, and logical volumes set up on there for /, /home, /usr, /tmp etc. I can lay this out manually, and it works fine. However, the code below, which is slightly amended from a previous anaconda-ks.cfg file doesn't work.
Code:
clearpart --linux --drives=sda,sdb --initlabel
part raid.11 --asprimary --size=200 --ondisk=sda
part raid.12 --grow --size=1 --ondisk=sda
part raid.21 --asprimary --size=200 --ondisk=sdb
part raid.22 --grow --size=1 --ondisk=sdb
raid /boot --fstype=ext3 --level=RAID1 --device=md0 raid.11 raid.21
raid pv.1 --level=1 --device=md1 raid.12 raid.22
volgroup rootvg --pesize=32768 pv.1
logvol / --fstype=ext4 --name=rootlv01 --vgname=rootvg --size=512
logvol /home --fstype=ext4 --name=rootlv02 --vgname=rootvg --size=256
logvol /tmp --fstype=ext4 --name=rootlv03 --vgname=rootvg --size=128
logvol /usr --fstype=ext4 --name=rootlv04 --vgname=rootvg --size=3072
logvol /var --fstype=ext4 --name=rootlv05 --vgname=rootvg --size=1024
logvol /opt --fstype=ext4 --name=rootlv06 --vgname=rootvg --size=1024
logvol swap --name=LogVol06 --vgname=rootvg --size=1024
View 2 Replies
View Related
Mar 7, 2010
I have FC6 system with kernel 2.6.22.14-72.fc6 When I rebooted my system, I got error message "unable to access resume device (LABEL=SWAP-sda8) then it went to fsck automatically to all the partition and then stop (failed)
Checking filesystems
/1:clean, 10543/2560864 files, 204494/2560359 blocks
fsck.ext3: unable to resolve 'LABEL=/backup'
/boot: clean, 155076/19546112 files, 13456168/39072080 blocks
[Code]...
View 14 Replies
View Related
Jun 20, 2010
Recently I bought a Toshiba NB100 from a family friend. All was going well until I installed some updates and now when I try to unmute my speakers I get this error message pop up.....
"No volume control GStreamer plugins and/or devices found"
View 2 Replies
View Related
Mar 17, 2011
I have one HD and a VG spanning it's entirety. I resized a LV and freed up 10GB within the VG, but I want the 10GB outside the boundary of the VG so I can install another OS for testing purposes. For some reason I'm not able to do this. I don't know if I understand LVMs correctly. Maybe there can be only one VG on a HD?
View 1 Replies
View Related
Mar 30, 2011
Currently, I am at 99% capacity with a 1TB hard drive (sda). I want to add an extra 2TB storage (sdc) by extending the current volume group using LVM.
[URL]
I can see that it is extended from the LVM GUI (System - Admin - LVM). However, when I download anything, the system says I am still at 99% capacity.
Code:
[root@localhost /]# fdisk -l
Disk /dev/sda: 1000.2 GB, 1000203804160 bytes
255 heads, 63 sectors/track, 121601 cylinders
[code]....
View 5 Replies
View Related
Mar 5, 2010
I wanted to take a current system with a working CentOS 4.7 LVM and move it to a 3ware 9650SE raid card so that I can mirror the drive and have a RAID1. The current system has 2 hard drives. One hard drive contains the CentOS 4.7 LVM install and the second drive is not part of the LVM. The second drive is being used for basic backups. I took a copy of the OS HD using dd and confirmed it worked by booting it up with the hard drive on the motherboard. When I connect it to the 3ware raid card with a new hard drive for the RAID1 and configure the 3ware raid card for RAID1, I get the "Volume Group "VolGroup00" not found" error. It gets past grub and then starts to load up but that is when the error occurs.
The error message exactly is:
Making device-mapper control node
Scanning logical volumes
Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumes
Volume group "VolGroup00" not found
ERROR: /bin/lvm exited abnormally! (pid 461)
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
View 2 Replies
View Related
Sep 2, 2010
I'm brand new to debian and quite new to unix based systems in general.
I just switched to debian from ubuntu in search of something different and I want to find a system that works for me before I settle down.
I DO NOT HAVE A SECONDARY OS
just two problems I have with debian:
No sound
Error message: No volume control GStreamer plugins and/or devices found.
When I try to open sound from the speaker icon at top right.
I think it's a driver issue but Its not as easy as ubuntu was lspci:
My trackpad also does not work so I have to open documents manually if I don't bring my mouse to class.
View 3 Replies
View Related
Jul 8, 2011
I am using a Dell Inspiron 14R laptop that came with Windows 7 Home Basic. The partitions of my hard disk before installing Fedora 15 were:
Dell (OEM Partition)
OS (C: ) (Primary Partition)
RECOVERY (Primary Partition)
New Volume (E: ) (Logical Drive)
I tried shrinking my C: drive (which has Windows) but couldn't do so hence performed the procedure on E: instead. I did this to create a 15GB unformatted space to install Fedora in. While installing Fedora, I chose the option "Use Free space" under Disk Partitioning Setup but the OS got installed in E: drive. Currently, I am able to use both Windows and Fedora under dual-boot but the problem I am facing is that when working with Windows, I am unable to see drive E: in Computer.
Windows Disk Manager is able to detect the partition and is showing it to be healthy (1st screenshot). Its name now is New Volume and neither am I able to change its path or letter (Error: incorrect parameters) nor am I able to check it using "chkdsk" (Error: cannot open volume for direct access/ GUI doesn't work as well) (2nd screenshot). On the other hand, I am able to access both the partitions in Fedora.
Another point to mention is that after finishing the installation of Fedora, when I started Windows, the Disk Manager as well as Dell DataSafe showed that the Windows Recovery drive had been formatted (maybe inappropriate terminology!) and was no longer retrievable. To rectify this problem, I restored my Windows to before Fedora was installed and I seem to have got the Recovery drive back (1st screenshot) (before doing this, it was nameless and empty).
View 4 Replies
View Related
Oct 16, 2009
This concerns the Logical Volume Manager (LVM).
1) Why would I create a new volume group to add a new hard drive to a system, rather than add the drive to an existing volume group?
2) If I created a new volume group and added a new hard drive to it, would I see the total free space (I see 30 GB now via the file browser)? For example, if I have 30 GB free on the main drive (with the OS), and I add a new drive of say 40 GB in a new volume group (using LVM) would I see 70 GB of free space? That doesn't seem to happen.
View 14 Replies
View Related
Mar 7, 2011
I'm running CentOS 5.5 with a hardware Areca controller (Raid 10). I initially installed a machine and rsynced the file system to a third machine; I'm then pulling in the file system to new machines and updating grub with a script to make it bootable.
I've done this before with other machines (no raid sets) but with these machines I'm running into errors code...
View 1 Replies
View Related
Sep 23, 2011
I face a problem with my server after i rebooted it i got a message on start up tell me that " Unable to access resume device (label=swap-sdb3) " and the system doesn't startup
the error message exactly is
Unable to access resume device (lable=swap-sdb3)
Creating root device.
Mounting root filesystem.
[ 3.305354] EXT-fs (md1) : error : unable to read superplock
mount: error mounting /dev/root on sysroot as ext3 : invalid argument
[Code]....
View 4 Replies
View Related
