Bug 867895
| Summary: | FSError: mount failed: (32, 'mount: wrong fs type, bad option, bad superblock on /dev/sda2,\n missing codepage or helper program, or other error\n In some cases useful info is found in syslog - try\n dmesg | tail or so') | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Clyde E. Kunkel <clydekunkel7734> | ||||||||||||||||||||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||||||
| Version: | 18 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora | ||||||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:75ac243b90ef9c897c2207967b81fa37e84fe9265c6b1eaec6bb8d377103e3fe | ||||||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||||||
| Last Closed: | 2013-01-10 16:22:00 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: | |||||||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||||||
Created attachment 629428 [details]
File: anaconda-tb
Created attachment 629429 [details]
File: product
Created attachment 629430 [details]
File: type
Created attachment 629431 [details]
File: ifcfg.log
Created attachment 629432 [details]
File: storage.log
Created attachment 629433 [details]
File: version
Created attachment 629434 [details]
File: environ
Created attachment 629435 [details]
File: anaconda.log
Created attachment 629436 [details]
File: syslog
Created attachment 629437 [details]
File: hashmarkername
Created attachment 629438 [details]
File: packaging.log
Created attachment 629439 [details]
File: cmdline_file
Created attachment 629440 [details]
File: release
Created attachment 629441 [details]
File: program.log
Attempted to created btrrs /, /home and /data with redundancy and performance check boxes checked. Also created swap and /boot as standard partitions. Error occurred after selecting begin installation and while typing root password. This bz may be the same as closed 865985. Accepted LV auto partitioning on 4 VD VM except reduced /home to 10 GB and created btrfs /data partition to use up rest of space. Created root passward and back to installation then error while formatting (?). Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7 Sorry we've not gotten to this yet. Can you please retest with F18 beta and if you are still hitting it, attach the fresh traceback? Thanks. OK, so here goes. Tried to recreate as best I could with F18Beta, but I probably did not exactly duplicate the VM I used originally. I got an error, but bugzilla said it was a duplicate, bz 865985, which I do get frequently with VMs. That bug was closed as not a bug due to what looked like hardware problems. I wonder? I kept the logs. Here is what I tried with the 4 disk VM: selected standard partitioning and custom. Created /, /home and /data as standard partitions then customized them to btrfs with redundancy and performance. swap and /boot were standard. No errors found by the partitioner. After entering the root password the error occurred. Do you want the logs? Tried again. Deleted the partitions created in previous attempt and allowed automatic btrfs partitioning create layout. Got bz 865985 again. Did not keep logs. this problem was probably due to a malformed VD. Closing. |
Description of problem: In a 4 disk VM selected btrfs /, /home and /data with redundancy and performance. Created standard ext4 /boot and swap. After clicking begin installation and while entering root password, error occurred. Version-Release number of selected component: anaconda-18.18 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.18 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 630, in mount : raise FSError("mount failed: %s" % e) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 1137, in setup : return self.mount(*args, **kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2738, in mountFilesystems : chroot=rootPath) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1649, in mountFilesystems : readOnly=readOnly, skipRoot=skipRoot) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 215, in turnOnFilesystems : skipRoot=False) : File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 107, in doInstall : turnOnFilesystems(storage) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run : threading.Thread.run(self, *args, **kwargs) :FSError: mount failed: (32, 'mount: wrong fs type, bad option, bad superblock on /dev/sda2,\n missing codepage or helper program, or other error\n In some cases useful info is found in syslog - try\n dmesg | tail or so')