Why anaconda throws traceback messages when installation source DASD is used in s390x platform with Red Hat Enterprise Linux 5 ?
Issue
-
Why anaconda throws traceback messages when installation source DASD is used in s390x platform with Red Hat Enterprise Linux 5 ?
Traceback (most recent call first): File "/usr/lib/anaconda/partedUtils.py", line 895, in savePartitions disk.commit() File "/usr/lib/anaconda/packages.py", line 147, in turnOnFilesystems anaconda.id.diskset.savePartitions () File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext self.moveStep() File "/usr/lib/anaconda/text.py", line 588, in run anaconda.dispatch.gotoNext() File "/usr/bin/anaconda", line 982, in ? anaconda.intf.run(anaconda) error: Warning: The kernel was unable to re-read the partition table on /dev/dasdX (Device or resource busy). This means Linux wont know anything about the modifications you made until you reboot. You should reboot your computer before doing anything with /dev/dasdc.
Environment
- Red Hat Enterprise Linux 5 on s390x platform
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
