Red Hat Bugzilla – Bug 967387
anaconda refuse '/usr/bin' as a valid mount point (it installs ok, but then id does not boot normally)
Last modified: 2013-05-31 20:00:37 EDT
Created attachment 753433 [details]
first boot after installing with a separate /usr/bin partition.
Description of problem:
Create a separate /usr/bin partition. I created a big one (1gb) and i was able to install F19b RC4. (Smaller partitions results in YumRPMTransError: Could not run transaction.)
After installation, systemd ask for maintenance mode. (sreenshot).
Version-Release number of selected component (if applicable):
F19b RC4 (19.30-1)
Steps to Reproduce:
1. Configure your favorite anaconda settings.
2. Enter custom partitoning
3. Create a 1gb /usr/bin mount point (ext4)
4. Create the other mount points. (/boot,swap,/)
5. Install F19b RC4
6. Reboot, systemd ask for maintenance mode
first boot after installation fails, due to /usr/bin being a separate
filesystem. (broken symlinks?)
refuse to accept '/usr/bin' as a valid mount point (or fix booting with such setup)
smaller /usr/bin are also accepted and result in a stop error and an aborted installation.
A separate /usr/bin isn't supported. We can't protect the user from every little thing they may try to do.