Red Hat Bugzilla – Bug 804295
Running update using vmlinuz/initrd.img/squashfs.img on /boot fails
Last modified: 2013-01-10 01:45:05 EST
Description of problem:
I'm trying to upgrade my Fedora 16. As usual I have downloaded vmlinuz, initrd.img and (new for F17) LiveOS/squasfs.img from the F17 repo and installed them on /boot. I've created a grub2 entry to boot this install Linux with
linux /vmlinuz root=live:UUID=... rd.luks=0 rd.md=0 rd.dm=0
Then I reboot the machine and select this install entry in grub. Everything works fine:
- kernel boots
- initrd starts
- live image starts
- Anaconda starts
- Select "Basic storage"
- Anaconda scans disk, finds my LUKS
- enter LUKS password
- Select "Update existing Fedora 16" on my / partition
But now Anaconda fails with
"An error occurred mounting device /dev/sda1 as /boot: mount failed... /dev/sda1 is already mounted or /mnt/sysimage/boot busy..."
This is a fatal error and therefore Anaconda aborts the installation.
This comes as no surprise, because /dev/sda1 (=/boot) is busy serving the live image. Shouldn't Anaconda at least try a --bind mount instead?
Version-Release number of selected component (if applicable): boot Message says "Welcome to Anaconda 17.11"
How reproducible: Always
Please attach /tmp/anaconda.log, /tmp/program.log, and /tmp/syslog to this bug report.
Created attachment 570997 [details]
Created attachment 570998 [details]
Created attachment 570999 [details]
We don't automatically copy the root image off the install source into ram so that we save ram. However if you pass the 'inst.upgrade' boot option we will copy it off.