Does FC6 not like installing on systems that already have LVM setup?

Jongi · 11-03-2006, 04:56 AM

I have tested the DVD iso I downloaded. The SHA1SUM and testing it when booting from the disk show the iso as being a valid Fedora Core 6 DVD.

I have tried to run the install with all of the following options at the prompt:

<Enter>
linux
linux reiserfs selinux=0
inux reiserfs selinux=0 ide=nodma
linux reiserfs selinux=0 acpi=off
linux reiserfs selinux=0 text
linux selinux=0
linux rescue (you will see below why I did this one)

No matter which of the above options I use, the installer will freeze 10-15 after the "Searching for Fedora Core installations" dialog box appears.

I currently have FC5 (amongst other distros) installed on this system. So I thought to myself what would happen if I tried to install FC5. I went with: linux reiserfs selinux=0

At the "Searching for Fedora Core installations" the following error message pops up:

Quote:

Error mounting file system on hdd8:
Operation not supported

The same error occurs for sda12 and sda13. Interestingly hdd8, sda12, sda13 and sda14 are part of LVM. When I press OK after each error message the installation continues. What was also of interest is that the error message did not pop up for sda14. The same happens when I boot of the FC5 DVD and run: linux rescue.

Quote:

[root:~#] pvscan
PV /dev/sda14 VG Home lvm2 [32.88 GB / 0 free]
PV /dev/sda13 VG Store lvm2 [30.00 GB / 0 free]
PV /dev/hdd8 VG Store lvm2 [30.31 GB / 0 free]
PV /dev/sda12 VG Games lvm2 [39.99 GB / 0 free]
Total: 4 [133.18 GB] / in use: 4 [133.18 GB] / in no VG: 0 [0 ]

For completeness sake I will also include the output of fdisk l

Quote:

[root:~#] fdisk -l

Disk /dev/hda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 9963 80027766 7 HPFS/NTFS

Disk /dev/hdd: 81.9 GB, 81964302336 bytes
16 heads, 63 sectors/track, 158816 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System

/dev/hdd1 * 1 31222 15735636 c W95 FAT32 (LBA)
/dev/hdd2 31222 158816 64307565+ 5 Extended
/dev/hdd5 31222 62444 15735636 83 Linux
/dev/hdd6 62444 93665 15735636 83 Linux

/dev/hdd7 93665 95753 1052226 82 Linux swap / Solaris
/dev/hdd8 95754 158816 31783718+ 83 Linux

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 5 Extended
/dev/sda5 1 2611 20972794+ 83 Linux

/dev/sda6 2612 5222 20972826 83 Linux
/dev/sda7 5223 7180 15727603+ 83 Linux
/dev/sda8 7181 9138 15727603+ 83 Linux
/dev/sda9 9139 11096 15727603+ 83 Linux

/dev/sda10 11097 13054 15727603+ 83 Linux
/dev/sda11 13055 16971 31463271 7 HPFS/NTFS
/dev/sda12 16972 22192 41937651 83 Linux
/dev/sda13 22193 26108 31455238+ 83 Linux

/dev/sda14 26109 30401 34483491 83 Linux

Disk /dev/dm-0: 35.3 GB, 35307651072 bytes
255 heads, 63 sectors/track, 4292 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 64.7 GB, 64751665152 bytes
255 heads, 63 sectors/track, 7872 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 42.9 GB, 42941284352 bytes
255 heads, 63 sectors/track, 5220 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-2 doesn't contain a valid partition table

PTrenholme · 11-04-2006, 03:27 PM

When the search for installations is being done, the installer attempts to process any fstab it finds. I discovered this when I yanked a FC5 boot drive from one system and mounted it in a USB removable HD box. When I connected the USB drive to my laptop, and tried to upgrade the FC5 on the USB drive to FC6, I couldn't do it until I booted into linux rescue and commented out all the lines in /etc/fstab that referred to drives in the box from which it was pulled.

Is it possible that your problem could be related to this installer behavior?

Digession:

In order to get my upgrade to run, I had to rename the logical volume on the USB drive. This was because my laptop had a working FC6 installed on it, so both the laptop drive and the USB drive were set up as containing VolGroup00, the Fedora default. If anyone's interested, what I had to do was boot into rescue mode, rename the working FC6 VG (the first one seen, so the only one activated), rename the second one, and then rename the first on back to the default name. Then both VGs could be activated at the same time, and the installer could find them both so I could upgrade the USB FC5.

The reason for the above digression is that I noticed that your pvscan lists two PVs as containing the "Store" LV. Now it's possible -- even likely -- that your "Store" LV spans two PVs so pvscan lists it twice. But it's also possible that the duplication is confusing things. Note: I'm no LVM expert, so, please, treat my comments as suggestions of where you might look, not recommendations for action. From your fdisk output, I think you must know a lot more than I do in this area.

Jongi · 11-04-2006, 04:44 PM

The "Store" Volume Group (VG) is comprised of two partitions, hdd8 and sda13. There is no error there.

Jongi · 11-08-2006, 05:36 AM

So what I did was to remove the SATA drive, unplugged the SATA cable from the
motherboard. Put in the FC6 install DVD and when it got to the same point, it
moved on to the point where it asked me to upgrade or install. I chose install
and the screen went blank and froze (waited for less than 5 minutes at that screen).

So my SATA suspicions have proved to be somewhat correct I would suspect. This
is the SATA info from FC5:

Code:

[root:~#] lsmod | grep sata
sata_via               10693  3
libata                 99161  1 sata_via

Code:

[root:~#] lspci | grep SATA
00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller
(rev 80)

Code:

[root:~#]lspci -v (selected portion)
00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller
(rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
        Subsystem: Giga-byte Technology GA-7VM400AM(F) Motherboard
        Flags: bus master, medium devsel, latency 32, IRQ 169
        I/O ports at 9400 [size=8]
        I/O ports at 9800 [size=4]
        I/O ports at 9c00 [size=8]
        I/O ports at a000 [size=4]
        I/O ports at a400 [size=16]
        I/O ports at a800 [size=256]
        Capabilities: [c0] Power Management version 2

Code:

[root:~#] lspci -n | grep 00:0f.0
00:0f.0 0101: 1106:3149 (rev 80)

Code:

[root:~#] grep 1106 /lib/modules/2.6.18-1.2200.fc5/modules.pcimap | grep 3149
sata_via             0x00001106 0x00003149 0xffffffff 0xffffffff 0x00000000
0x00000000 0x0

Code:

[root:~#] modinfo sata_via
filename:       /lib/modules/2.6.18-1.2200.fc5/kernel/drivers/scsi/sata_via.ko
author:         Jeff Garzik
description:    SCSI low-level driver for VIA SATA controllers
license:        GPL
version:        2.0
vermagic:       2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS gcc-4.1
depends:        libata
alias:          pci:v00001106d00000591sv*sd*bc*sc*i*
alias:          pci:v00001106d00003149sv*sd*bc*sc*i*
alias:          pci:v00001106d00003249sv*sd*bc*sc*i*
srcversion:     826D41190D62A5FFC744E90

Jongi · 11-30-2006, 12:14 PM

To solve the problem I ran fsck.reiserfs --rebuild-tree on the logical volume partitions (they all happen to be reiserfs). I did this after I noticed that running gparted (it would just freeze) and Acronis Disk Director in XP (error messages appeared when I started it up) indicated there were problems.

After running fsck, I was able to install fc6 without problems.