Re: repair a damaged vg
On Sunday 20 December 2009, Tom H wrote: Thnx Tom for trying to help me :) > Have you tried vgreduce and then vgextend again before the lvextend? no, sadly this was the sequence [23:08:12 r...@xxx ~ ]# pvcreate /dev/sdc Physical volume "/dev/sdc" successfully created [23:08:27 r...@xxx ~ ]# vgextend /dev/mapper/VolGroup01 /dev/sdc Volume group "VolGroup01" successfully extended [23:08:48 r...@xxx ~ ]# lvextend -l 100%VG /dev/mapper/VolGroup01-lvol0 Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Extending logical volume lvol0 to 329,99 GB Cannot update volume group VolGroup01 while physical volumes are missing. [23:09:19 r...@xxx ~ ]# lvextend -l 100%VG VolGroup01-lvol0 Path required for Logical Volume "VolGroup01-lvol0" Please provide a volume group name Run `lvextend --help' for more information. [23:09:47 r...@xxx ~ ]# lvextend -l 100%VG /dev/mapper/VolGroup01-lvol0 Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Extending logical volume lvol0 to 329,99 GB Cannot update volume group VolGroup01 while physical volumes are missing. [23:10:01 r...@xxx ~ ]# lvextend -l 100%free /dev/mapper/VolGroup01-lvol0 Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. New size given (20479 extents) not larger than existing size (63999 extents) Run `lvextend --help' for more information. [23:10:20 r...@xxx ~ ]# lvextend -l 100%free /dev/VolGroup01/lvol0 Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. New size given (20479 extents) not larger than existing size (63999 extents) Run `lvextend --help' for more information. [23:11:01 r...@xxx ~ ]# lvextend -l 100%VG /dev/VolGroup01/lvol0 Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Extending logical volume lvol0 to 329,99 GB Cannot update volume group VolGroup01 while physical volumes are missing. [23:11:08 r...@xxx ~ ]# lvdisplay Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. --- Logical volume --- LV Name/dev/VolGroup01/lvol0 VG NameVolGroup01 LV UUIDA507we-8Kda-srlT-1MjO-lR7F-k0Xo-powd5x LV Write Accessread/write LV Status available # open 1 LV Size250,00 GB Current LE 63999 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2 --- Logical volume --- LV Name/dev/VolGroup00/LogVol00 VG NameVolGroup00 LV UUIDvbuKvi-Kf9H-R8LV-iLH6-x1tp-5xdl-Zt1Pad LV Write Accessread/write LV Status available # open 1 LV Size6,88 GB Current LE 220 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Name/dev/VolGroup00/LogVol01 VG NameVolGroup00 LV UUIDLA27jO-aQbW-jlSn-5JrP-Cp2T-K3pS-vw7BnP LV Write Accessread/write LV Status available # open 1 LV Size1,00 GB Current LE 32 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 [23:11:19 r...@xxx ~ ]# [23:11:44 r...@xxx ~ ]# vgs Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. VG #PV #LV #SN Attr VSize VFree VolGroup00 1 2 0 wz--n- 7,88G 0 VolGroup01 2 1 0 wz-pn- 329,99G 80,00G [23:11:59 r...@xxx ~ ]# lvextend -l 100%VG /dev/mapper/VolGroup01-lvol0 Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Extending logical volume lvol0 to 329,99 GB Cannot update volume group VolGroup01 while physical volumes are missing. [23:14:03 r...@xxx ~ ]# pvs Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. PV VG Fmt Attr PSize PFree /dev/sda2 VolGroup00 lvm2 a- 7,88G 0 /dev/sdc VolGroup01 lvm2 a-80,00G 80,00G unknown device VolGroup01 lvm2 a- 250,00G 0 [23:14:21 r...@xxx ~ ]# vgs Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. VG #PV #LV #SN Attr VSize VFree VolGroup00 1 2 0 wz--n- 7,88G 0 VolGroup01 2 1 0 wz-pn- 329,99G 80,00G [23:15:13 r...@xxx ~ ]# vgreduce VolGroup01 /dev/sdc Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Cannot remove final metadata area on "/dev/sdc" from "VolGroup01" i am searching help on linux-lvm mlist, now Maurizio
repair a damaged vg
Hi there after: pvcreate /dev/sdc Physical volume "/dev/sdc" successfully created sadly i issued: vgextend /dev/mapper/VolGroup01 /dev/sdc Volume group "VolGroup01" successfully extended instead of doing: vgextend VolGroup01 /dev/sdc Volume group "VolGroup01" successfully extended then i tryied to extend lv lvextend -l 100%VG /dev/mapper/VolGroup01-lvol0 Couldn't find device with uuid 'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'. Extending logical volume lvol0 to 329,99 GB Cannot update volume group VolGroup01 while physical volumes are missing. is there some angel able to save me? Tia Maurizio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
gpg2, kgpg and kmail
Fedora 11 fully upgraded. I see that kgpg can be configured to use gpg or gpg2 or whatever you setup. Kmail, instaed, doesn't (or, better, i was not able to find it). In my ~/.gnupg file option was modified by fedora11 upgrade and these line were appended to it: ###+++--- GPGConf ---+++### utf8-strings debug-level basic log-file socket:///home/maumar/.gnupg/log-socket ###+++--- GPGConf ---+++### Wed 06 May 2009 09:34:17 AM CEST # GPGConf edited this configuration file. # It will disable options before this marked block, but it will # never change anything below these lines. Now, using gpg i get the obvious error gpg -d cryptato gpg: /home/maumar/.gnupg/options:119: invalid option gpg: /home/maumar/.gnupg/options:120: invalid option but using tha old one, i can get gpg to work fine: ~/.gnupg ]$ gpg --options options.gpgconf.bak -d cryptato You need a passphrase to unlock the secret key for user: "Maurizio Marini " 1024-bit ELG-E key, ID 33B888E3, created 2002-08-07 (main key ID 72094E5C) etc etc i wouldn't rename option -> option.gpg2 then options.gpgconf.bak -> option then configure kgpg to use /usr/bin/gpg2 --options $HOME/.gnupg/option.gpg2 i hope there is another solution, for example to configure default option file for either gpg and gpg2, without recompiling them, i dunno how is possible any suggestion is welcome :) -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: start_vms into /etc/init.d/vboxdrv
On Thursday 14 May 2009, Maurizio Marini wrote: > $VBOXMANAGE -nologo start $v -type vrdp i found that this a large discussed issue, start with http://quadirspace.blogspot.com/2009/05/virtualbox-service-for-ubuntu-linux.html follow links reported there basically $VBOXMANAGE -nologo start $v -type vrdp is correct -- Maurizio Marini -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
start_vms into /etc/init.d/vboxdrv
i note that start_vms is missing into /etc/init.d/vboxdrv
maybe it is intentionaly missing, for some reason that at the moment i can't
see
i will try this :
start_vms()
{
VMS=`$VBOXMANAGE -nologo list vms 2>/dev/null`
if [ -n "$VMS" ]; then
begin_msg "Starting VMs"
for v in $VMS; do
$VBOXMANAGE -nologo start $v -type vrdp
done
succ_msg
fi
}
i use -type vrdp as suggested here:
http://forums.virtualbox.org/viewtopic.php?f=7&t=11633
i suppose that i cannot boot a VirtualBox vm without booting it undetached, i
should do some tests, but at the moment it's my convintion
anyone could help on this issue?
tia
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
kmail does not use kwallet anymore
kontact has started loosing connection to kwallet; i was obliged to delete all the accounts and to recreate them now, password are stored into kmail, but i prefer to use again kwallet. Question is: how can i force kontact/kmail to use kwallet? tia Maurizio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 OpenOffice default page size
On Tuesday 06 January 2009, Tim wrote: > This is more of an OpenOffice.org question, than a Fedora one. eh eh eh this is an old issue; they came here even complaining that their small cat does not piss any more by the time they installed fedora; any suggestion to search small pets newsgroups does not change this habit m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Strange MTU-ish problem
On Tuesday 06 January 2009, Nifty Fedora Mitch wrote: > On Mon, Jan 05, 2009 at 06:57:05PM -0600, Frank Cox wrote: > > On Tue, 06 Jan 2009 01:47:11 +0100 > > > > Timothy Murphy wrote: > > > Is there a similar option for ping under Fedora? > > > > ping -s sizeyouwant www.google.com > > you must also set a do not fragment flag. > it's a known problem http://forum.ubuntu-it.org/index.php?topic=235535.msg1625049 i have appended in sysctl.conf net.ipv4.tcp_window_scaling = 0 not more not less -- Maurizio Marini -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
arrows keys are not recognized after upgrade F9 -> F10
the arrow keys are working well with xfce and gnome, and with a fresh account with fresh kde settings. so, there is something wrong into my account .kde/share there are many files there, and hopefully i would avoid to create a a fresh .kde under my account and add one file at the tiome from current .kde, very frustrating any help is apreciated maurizio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
SOLVED Re: firefox does not start after F10 upgrade
On Sunday 04 January 2009, Maurizio Marini wrote: > > 1. firefox does not start > $ firefox > Couldn't load XPCOM. firefox issue was fixed with yum update m. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
firefox does not start after F10 upgrade
Hi i have just upgraded F9 -> F10 using preupgrade. All went well. I have only 2 issues> 1. firefox does not start $ firefox Couldn't load XPCOM. i googled and i found something related to XUL http://ubuntuforums.org/showthread.php?t=638801&page=6 http://ubuntuforums.org/showthread.php?t=951615 but i am not able to have firefox starting, yet; anyone can help? 2. arrow keys do not work on kde, in xfce they works fine; so, this a kde settings issue related any hel wil be very apreciated Maurizio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: latest upgrade procedure
On Saturday 13 September 2008, Amadeus W.M. wrote: > Which is the latest document describing how to do upgrades/installs from > the new repositories? > > Thanks! just issue yum update if requested to accept some keys, alwys answer yes it's worked for me m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: (fedora) Re: VMware fails to build with the new kernel
On Friday 12 September 2008, Paul Smith wrote: > > "Unable to change virtual machine power state: The process exited with an > error: End of error message". > > Any ideas? > > Paul me too and no ideas m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Outlook Exchange Server to Open Source Alternatives?
On Monday 08 September 2008, Mike McMullen wrote: > Hi All, > > As part of a larger project to move our company away from Microsoft > products, I'm investigating options for replacing our enterprise > exchange server. i have many installation of zimbra (http://www.zimbra.com) and it is able to replace exchange, imho m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: wifi enabling
On Tuesday 02 September 2008, dexter wrote: > On Tue September 2 2008 18:09:36 narendraw1 palavalli wrote: > > hai i have installed fedora9 recently in my hp pavillion dv 9617nr laptop > > it has a broadcom802.11b/g wireless card > > i m not able to connect to the network i tried even giving the ip address > > and tryin its not possible so please can u help me with this i have a compaq n750 with this wifi card: # lspci 01:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02) try to use NetworkManager /etc/init.d/NetworkManager start it helped me on searching wifi ap to connect to -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: /b43#devicefirmware empty
On Friday 08 August 2008, g wrote:
> Maurizio Marini wrote:
> > i get this
> >
> > Aug 5 18:11:58 matanui kernel: b43-phy0 warning: You must go to
> > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download
> > the latest firmware (version 4).
>
> i have used linuxwireless.org before with great results.
>
> above link is good. you might try again and reread instructions.
no, the link is empty!
look at the screenshot
there is nothing at anchor #devicefirmware
the section is empty
>
>
> model?
01:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI
(rev 02)
Subsystem: Hewlett-Packard Company Unknown device 1375
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at 9130 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 1a-00-af-ff-ff-73-05-40
Capabilities: [16c] Power Budgeting
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
thnx for help :)
--
Maurizio Marini Via Collemare, 14 - 61039 San Costanzo (PU) - Italy
GSM +39-335-8259739 Milano +39.0245446-202 Skype: [EMAIL PROTECTED]
Fano Casa : +39-0721950396
C.F. MRNMRZ59E17G920X P. Iva: 01332360419
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
/b43#devicefirmware empty
i get this Aug 5 18:11:58 matanui kernel: b43-phy0 warning: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the latest firmware (version 4). on my logs the link is empty :( support IRC channel irc.freenode.net #bcm-users (English please) Mailing list http://lists.berlios.de/mailman/listinfo/bcm43xx-dev http://linuxwireless.org/en/users/Drivers/b43#devicefirmware [//] device firmware [empty] firmware installation The Broadcom wireless chip needs software, called "firmware", that runs on the wireless chip itself during operation. [...] where can i find them? -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: automount and autorun SOLVED
On Thursday 31 July 2008, Mikkel L. Ellertson wrote: > Maurizio Marini wrote: > > My target is to use an "autorun" bash script when an usb pen is > > automounted like http://linlog.skepticats.com/content/udevautorun/ > > describe. > > > > With recent kernels hotplug is vanished replaced by udev; there is > > no /etc/dev.d or /etc/hotplug, anymore. > > I am not able to find a place where put bash script to be executed. > > I read tons of google udev links w/out result, yet. > > Any advice would be apreciated > > > > Maurizio > > It is /etc/udev and /etc/hotplug.d. But HAL handles things like > mounting USB pen drives. So you will probably have to add a HAL rule > to do this... > > Mikkel cat /etc/udev/rules.d/81-programs-local.rules ACTION=="add", KERNEL=="sdb1", SUBSYSTEM=="block", RUN+="/root/usbpen" the key is to use the RUN option to autoRUN a script when usben is mounted thnx Maurizio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
automount and autorun
My target is to use an "autorun" bash script when an usb pen is automounted like http://linlog.skepticats.com/content/udevautorun/ describe. With recent kernels hotplug is vanished replaced by udev; there is no /etc/dev.d or /etc/hotplug, anymore. I am not able to find a place where put bash script to be executed. I read tons of google udev links w/out result, yet. Any advice would be apreciated Maurizio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
knotes notes sorted by year-month-day
Hi there i have the annoying issue that my notes are showed sorted by: month-day-year mm-dd-yy it would be nice to have them sorted by year-month-day is it allowed? tia for any advice -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: recent kernel upgrades damage mbr
On Wednesday 18 June 2008, Gene Heskett wrote: > While we're on the subject of mbr's, how big is it? The first 512 bytes of > the one I just saved is virtually empty. So I overwrote it with a 4kb > version, b but that is bearing some resemblance to a list of inodes. AFAIK, it is still 512, by Roman's time, Caesar decided it... i never have read anything about something different by 512 bytes. If your 512 bytes are all 00x0 using hexdump, something goes wrong, Which is the exact command do u issued? -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
missing file browser on kate sidebar
I dunno know and i dunno why, but this mornig after started kate, on the sidebar i can see open buffer "Documents" button, the very comfortable File Browser is missing any advice would be apreciated Maurizio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: recent kernel upgrades damage mbr
On Tuesday 17 June 2008, Mark Haney wrote: > Maurizio Marini wrote: > While I'm certainly an advocate for 'better safe than sorry', I've never > seen a problem with the MBR on a kernel upgrade or install. Ever. And > I've been building kernels since mid '97 or so. I never saw an mbr damaged after a distro upgrade, too! > > That said, this subject line is really misleading and should really be > more about grub than kernels, since grub upgrade do affect the mbr and > kernel upgrades (in my experience) don't. Yes, I 'now this a grub issue, but on friday, when i suffer mbr damage, i scan upgraded package on yum.log and i could see, among the dangerous packages: kernel and device-mapper-multipath (give a look at https://bugzilla.redhat.com/show_bug.cgi?id=450143) No grub upgrade was in place. My grub is: grub-0.97-33.fc9.i386 At this moment we cannot say if the mbr was damaged by kernel or device-mapper-multipath or whatsever. I feel that anyone at the moment can fall in this issue and i feel my obey to advice this community. Maybe my words are not the best and are misleading, i agree with you; for sure someone of fedora devs can describe this issue without misleading. my 2 cents -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
recent kernel upgrades damage mbr
I would advice any list member that it is in the wild a issue regarding grub and mbr. I invite who has not yet done it, to save mbr on a secure place before any kernel or grub related upgrade, dd is your friend. In the meantime fedora experts and developers are at work (hopefully) to investigate and solve this issue. https://bugzilla.redhat.com/show_bug.cgi?id=450143 man adviced, man half saved -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Recent updates caused Grub installation to be damaged?
On Sunday 15 June 2008, Brian Morrison wrote: > > It's also the first time I've had this problem since starting with RH7. yes. it is maybe the first time for every distro > > Sounds like someone needs to bugzilla it then, this really shouldn't > happen. Had I been on the road without an F9 DVD to hand it would have > been a lot more difficult to fix. we should advise every other fc9 user on this issue, but i dunno how... posting on a widely read mlist, like bugtraq, maybe -m -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Recent updates caused Grub installation to be damaged?
i got the same issue; i was unable in any way to chroot /mnt/sysimage after linux rescue as fstab and grub.conf have been changed by upgrade; i fixed them mounting disk on an external usb box. this was my changed fstab: UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb / ext3 defaults1 1 UUID=22309ffe-0180-41bd-a868-9d5b15660781 /home ext3 defaults1 2 UUID=c46f0b8e-ea34-47f5-8c7f-57a7f3a5d531 /boot ext3 defaults1 2 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 UUID=817d341a-8daa-43dd-8c97-2eea4c1f418f swapswap defaults0 0 i restored it to: [09:34:12 [EMAIL PROTECTED] /var/log ]# cat /etc/fstab /dev/VolGroup00/LogVol00 / ext3defaults1 1 /dev/VolGroup00/LogVol02 /home ext3defaults1 2 /dev/sda1 /boot ext3defaults1 2 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 /dev/VolGroup00/LogVol01 swapswapdefaults0 0 this was my grub.conf changed by upgrade: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.25.6-55.fc9.i686) root (hd0,0) kernel /vmlinuz-2.6.25.6-55.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet initrd /initrd-2.6.25.6-55.fc9.i686.img title Fedora (2.6.25.4-30.fc9.i686) root (hd0,0) kernel /vmlinuz-2.6.25.4-30.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet initrd /initrd-2.6.25.4-30.fc9.i686.img i restored it to: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.25.6-55.fc9.i686) root (hd0,0) kernel /vmlinuz-2.6.25.6-55.fc9.i686 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.25.6-55.fc9.i686.img title Fedora (2.6.25.6-55.fc9.i686) root (hd0,0) kernel /vmlinuz-2.6.25.6-55.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet initrd /initrd-2.6.25.6-55.fc9.i686.img title Fedora (2.6.25.4-30.fc9.i686) root (hd0,0) kernel /vmlinuz-2.6.25.4-30.fc9.i686 ro root=UUID=cf7cd8e9-13c6-4997-88cf-2b2e917736fb rhgb quiet initrd /initrd-2.6.25.4-30.fc9.i686.img at last i was able to chroot and then i issued: grub-install /dev/sda then i was able to boot my fc9. i investigated on /var/log/yum.log to find the *guilt*; here it is the excerpt: Jun 13 13:54:46 Updated: selinux-policy-3.3.1-64.fc9.noarch Jun 13 13:55:08 Updated: selinux-policy-targeted-3.3.1-64.fc9.noarch Jun 13 13:55:35 Updated: selinux-policy-devel-3.3.1-64.fc9.noarch Jun 13 13:55:40 Updated: logwatch-7.3.6-22.fc9.noarch Jun 13 13:55:47 Updated: kernel-headers-2.6.25.6-55.fc9.i386 Jun 13 13:57:04 Updated: 1:java-1.6.0-openjdk-javadoc-1.6.0.0-0.15.b09.fc9.i386 Jun 13 13:57:14 Installed: kernel-devel-2.6.25.6-55.fc9.i686 Jun 13 13:57:23 Updated: nspr-4.7.1-0.9.1.fc9.i386 Jun 13 13:57:28 Updated: nss-3.12.0.3-0.9.1.fc9.i386 Jun 13 13:57:55 Updated: 1:java-1.6.0-openjdk-1.6.0.0-0.15.b09.fc9.i386 Jun 13 13:57:57 Updated: postgresql-libs-8.3.3-1.fc9.i386 Jun 13 13:57:58 Updated: kpartx-0.4.7-15.fc9.i386 Jun 13 13:57:59 Updated: device-mapper-multipath-0.4.7-15.fc9.i386 Jun 13 13:58:00 Updated: 1:java-1.6.0-openjdk-plugin-1.6.0.0-0.15.b09.fc9.i386 Jun 13 13:58:02 Updated: nss-tools-3.12.0.3-0.9.1.fc9.i386 Jun 13 13:58:31 Installed: kernel-2.6.25.6-55.fc9.i686 Jun 13 13:58:32 Updated: gstreamer-plugins-farsight-0.12.7-2.fc9.i386 Jun 13 13:58:34 Updated: gdb-6.8-10.fc9.i386 Jun 13 13:58:35 Updated: nspr-devel-4.7.1-0.9.1.fc9.i386 Jun 13 13:58:36 Updated: nss-devel-3
