Bug 198702
Summary: | Cannot upgrade FC2 with LVM to FC5 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew D. Stadler <stadler> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-15 18:32:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew D. Stadler
2006-07-12 22:11:00 UTC
I have also tried this with an FC4 installer DVD and although the look and feel were different, the two error message dialogs were exactly the same. (I was in graphical installer so I did not have an opportunity to view the logs) Since the data on my RAID is strictly user data - there are no system files - I decided to try upgrading without the RAID. Failed workaround: 1. Shut down system 2. Physically unplug RAID card 3. Reboot 4. Repeat installation attempt 5. No longer says "Error mounting file system on sda1: Invalid argument" 6. Still says "Error mounting device vg_raid/lv_homes as /home: No such file or directory" This workaround failed but provided a key clue: Anaconda is getting upset when it cannot (for whatever reason) satisfy a mount point in /etc/fstab. So I reinstalled the RAID card and tried a different workaround: 1. Boot into linux rescue 2. Ignore error messages 3. cd /sys/mntimage/etc 4. cp fstab fstab_backup_fc5 5. vi fstab 6. place '#' before the lines that mount from /dev/vg_raid/... 7. save and quit 8. reboot into FC5 anaconda Good news: This seems to get through the difficulties and get into the installation process. Does it then mount correctly after the upgrade? Sorry, I didn't update the bug after that. The results of the FC5 upgrade (in comment #2) were a non-booting FC5 system. I do not know why, but it was dying early in the kernel init phase. At this point I was out of time and needed to get the server back on line, so I wiped the boot partitions, made a new smaller partition, and reinstalled FC2 on it. Added my LVM mount points to /etc/fstab and the LVM volumes came right back on line with no errors reported. My next step will be to install a fresh (not upgrade) FC5 on a new partition on the boot drive (I left plenty of room for this sort of thing) and I expect I will then manually attach the LVM volumes, again. I will update the bug report when I do this. Upgrades from more than one release back are not supported in Fedora. You can upgrade FC2 to FC3, FC3 to FC4, and so on. But not FC2 to FC5. |