Carl Lowenstein wrote: > On Mon, Jan 5, 2009 at 9:02 PM, Lief Hendrickson <limaho...@cox.net> wrote: >> At 07:59 PM 1/5/2009, James A.Sack wrote: >>> 97.705%James G. Sack (jim) wrote: >>>> .. >>>> Did a grub menu show on the screen during the boot process? >>>> If not, I suspect the install operation needs to be repeated (as in last >>>> email) -- as root >>>> grub-install --recheck >>> Oh wait, I left something out: that should be >>> grub-install --recheck /dev/hda >>> >>>> .. >>> Regards, >>> ..jim >> >> I ran "grub-install --recheck /dev/hda" >> Result: It works! It boots into linux without having to use commands at the >> grub prompt (which I was getting good at :-) ) >> >> I don't see any difference in the grub.conf file. However the device.map >> file is different. >> It was: >> # this device map was generated by anaconda >> (fd0) /dev/fd0 >> (hd0) /dev/hda >> (hd1) /dev/hdb >> >> Is now: >> # this device map was generated by anaconda >> (fd0) /dev/fd0 >> (hd0) /dev/hda >> >> Any idea what happened to hdb? > > Isn't hdb the one you removed because it broke. Actually you > removed hda, and altered connections so that the remaining drive, > which had been hdb, became hda. > >> I booted into knoppix again. It shows hda1 and hda2 on the desktop. I can >> mount hda1 and open a window to see its contents, which is the same as what >> Fedora shows as hda >> However, knoppix will not let me mount hda2 even though it shows an icon on >> the desktop. The error statement says >> "mount: wrong fs type, bad option, bad superblock on /dev/hda2 >> missing codepage or other error" >> >> Does knoppix see a partition (hda2) which is missed by Fedora? > > Going way back in the history of this discussion, hda2 is a Linux LVM > partition, which contains data that is managed by the Logical Volume > Manager. > Knoppix does not by default deal with LVM partitions, although it can > be coerced into doing so. > > Again, back to history, and something you can see from the booted > Fedora system, is that the LVM partition consists of one Volume Group, > containing two Logical Volumes, one of which is used as swap, and the > other as the root file system. This is the way that default Fedora > installations set up the disk nowadays.
I think Carl's covered it all, but here are some non-destructive commands for displaying the storage components. Run these as root: fdisk -l /dev/hda fdisk -l /dev/hdb .. this will give no output as there is no hdb pvs .. physical device(s) given over to LVM management vgs .. volume group(s) (storage pools) created by LVM lvs .. logical volume(s) allocated from the VG(s) It's the LVs that can be formatted with a filesystem (or swap). In your case, we know from your grib.conf that you have a LV named /dev/VolGroup00/LogVol00 that contains your F10 filesystem (except for the boot partition which is /dev/hda1). Have a happy time! Regards, ..jim -- KPLUG-Newbie@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
