i get "no volume groups found", volume group "volgroup00" not found, then the kernel panic. this has happened twice, once friday (99 updates available) and once today (125 updates available). each time has been a fresh install from livecd, then updates via package updater. i see this on a desktop system and on a laptop. on a side note, i also noticed that clicking on the reboot button after the "install to hard drive" completes drops me to the desktop, never reboots. I have to go up to the system menu, shutdown, restart. anyone else seeing these?
On Mon, 2 Apr 2007, mack sessoms wrote:
i get "no volume groups found", volume group "volgroup00" not found, then the kernel panic. this has happened twice, once friday (99 updates available) and once today (125 updates available). each time has been a fresh install from livecd, then updates via package updater. i see this on a desktop system and on a laptop.
I think there is still something wrong with mkinitrd and new IDE drivers structure.
In past here it was explained that one should not update e.g. FC6 to F7 because this change, it seems is also applies to F7TX updates. I am still far from understnading why this happens and mkinitrd creates "invalid" initrd. But I really would like to, because I fear this will be really common problem with F7 comming. (I had to drop F7TX installation for that reason too as new kernel installation deleted the only working one and I was not able to create initrd for any existing kernel.)
Adam Pribyl
mack sessoms schrieb:
i get "no volume groups found", volume group "volgroup00" not found, then the kernel panic. this has happened twice, once friday (99 updates available) and once today (125 updates available). each time has been a fresh install from livecd, then updates via package updater. i see this on a desktop system and on a laptop. on a side note, i also noticed that clicking on the reboot button after the "install to hard drive" completes drops me to the desktop, never reboots. I have to go up to the system menu, shutdown, restart. anyone else seeing these?
Hi,
I get this directly after installing. The problem on my system is caused by anaconda or the kernel loading the wrong drivers for storage devices.
cu romal