Created attachment 357443 [details]
Photo of traceback
Description of problem:
When I want to boot into rescue mode from Fedora 11 x86_64 DVD, I got python exception and had to reboot system.
I think the source of problem could be I use LVM and crypted disks.
Steps to Reproduce:
1. Boot from DVD - Rescue mode
2. Chose the keyboard, enable/disable network, choose RW or RO mode - it is all irrelevant.
3. Enter passphrase for every disk.
Traceback (most recent call last):
File "/usr/bin/anaconda", line 729, in <module>
File "/usr/lib/anaconda/rescue.py", line 315, in runRescu
readOnly = readOnly)
File "/usr/lib/anaconda/storage/__init__.py", line 1187, in mountExistingSystem
File "/usr/lib/anaconda/storage/__init__.py", line 1520, in parseFSTab
File "/usr/lib/anaconda/storage/devicetree.py", line 601, in _addDevice
raise ValueError("device is already in tree")
ValueError: device is already in tree
install exited abnormally (1/1)
disabling /dev/loop0 LOOP_CLR_FD failed: 16
sending termination signals... done
sending kill signals... done
You may safely reboot your system
(rewritten from attached photo I took with my phone)
Boot into rescue mode
What does your /etc/fstab look like?
*** Bug 520135 has been marked as a duplicate of this bug. ***
A quick but dirty fix to this problem is to comment many useless lines in the /etc/fstab.
I encountered similar problem with a fstab like this :
/dev/sdb1 /media/foo vfat rw,user,noauto,owner,uid=500,gid=500 0 0
/dev/sdb1 /media/bar ntfs rw,user,noauto,owner,uid=500,gid=500 0 0
Even with 'noauto' option provided in the /etc/fstab, Anaconda looks for the device and fails if not found.
This will be fixed in the next build of anaconda. Thanks for the bug report.
After removing useless lines from the /etc/fstab it works!
But I have one relative question. After booting into rescue mode, mounting installation, chrooting and rebooting computer, my installed fedora runs SELinux relabeling. (I did nothing with SELinux in rescue mode). It took me a lot of time. It is the normal behaviour?