3

Fedora 11 upgrade with LVM missing /boot partition

view full story
linux-howto

http://forums.fedoraforum.org – I've just (finally!) gotten around to upgrading a couple of machines at a company I do some work for. One machine had a problem when I rebooted onto the new system. During the boot sequence, when it was checking and mounting the filesystems, it was unable to find the /boot partition. Now, this machine does run LVM on all but the /boot partition. The two SATA drives are mirrored, and they have the same partition layout: Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000007b4 Device Boot Start End Blocks Id System /dev/sda1 * 1 25 200781 83 Linux /dev/sda2 26 38913 312367860 8e Linux LVM During the boot sequence, grub can find the sda1 partition without problem and boots the kernel just fine. During the boot, the kernel seems to recognize the partitions: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7: WDC WD3200YS-01PGB0, 21.00M21, max UDMA/133 ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 1) ata1.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA WDC WD3200YS-01P 21.0 PQ: 0 ANSI: 5 sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors: (320 GB/298 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 0:0:0:0: [sda] Attached SCSI disk But, when the system gets underway, the kernel seems to loose track of the sda1 and sdb1 partitions: # cat /proc/partitions major minor #blocks name 8 0 312571224 sda 8 16 312571224 sdb 8 18 312367860 sdb2 253 0 10485760 dm-0 253 1 41943040 dm-1 253 2 10485760 dm-2 253 3 1048576 dm-3 253 4 41943040 dm-4 253 5 10485760 dm-5 253 6 62914560 dm-6 253 7 5242880 dm-7 253 8 41943040 dm-8 253 9 41943040 dm-9 253 10 2031616 dm-10 I got the system to boot by commenting out the /boot partition in /etc/fstab, but this is certainly only a temporary solution. The other system that I upgraded came up just fine, as have several of my own. Unfortunately, I am doing these two systems by remote control via ssh as I have only limited plysical access to them. (I did have to get to it to figure out why it didn't boot up..) Thanks for any suggestions! Marcus Hall (HowTos)