Bug 604075
Summary: | FormatCreateError: ('invalid device specification', '/dev/dasda2') | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Hendrik Brueckner <brueckner> | ||||||
Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 6.0 | CC: | bugproxy, jstodola, mgrf | ||||||
Target Milestone: | rc | Keywords: | Reopened | ||||||
Target Release: | --- | ||||||||
Hardware: | s390x | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2011-06-10 16:11:28 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: |
|
Description
Hendrik Brueckner
2010-06-15 11:18:28 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Can you please attach the complete /tmp/*tb* file to this bug report? If you can provide the information requested in comment 3, please attach it to the bug and reopen. Reopening to provide the requested data... ------- Comment From michael.holzheu.com 2010-06-15 07:39 EDT------- Description of problem: Version-Release number of selected component (if applicable): How reproducible: Use one DASD with 5120 MB Steps to Reproduce: 1. Use "specialized storage devices" -> next 2. Select DASD -> next 3. Specify host name -> next 4. Select time zone (NOTE SELECTING CITY IS REALLY NOT USER FRIENDLY) -> next 5. Enter passwd -> next 6. Select "Create Custom Layout" -> next 7. Create 8. Select standard partition -> create 9. mount point=/home, size=2000MB, fixed size, fs=ext4 -> ok 10. Select standard partition -> create 11. size=2000MB, fixed size, fs=swap -> ok 12. Select standard partition -> create 13. mount point=/, (size=200), fill to maximum allowable size, fs=ext4 -> ok 14. Overview looks ok -> next 15. -> Write changes to disk 16. ERROR: Formatting failed (an error was encountered while formatting device /dev/dasda2) Details: Invalid device specification -> Exit intaller Actual results: Installation fails Expected results: Installation works ------- Comment From michael.holzheu.com 2010-06-15 07:55 EDT------- Problem is that I have a FBA disk. Bus-ID Status Name Device Type BlkSz Size Blocks ============================================================================== 0.0.4712 active dasda 94:0 FBA 512 5120MB 10485760 It is not possible to create partitions on FBA DASDs. ------- Comment From michael.holzheu.com 2010-06-15 08:00 EDT------- It is also not possible to specify only one partition "/" in order to use only dasda1 from the FBA disk. I get the error: mount failed: (9,None) ------- Comment From brueckner.ibm.com 2010-06-21 04:28 EDT------- Hi Luciano, (In reply to comment #5) > So is https://bugzilla.redhat.com/show_bug.cgi?id=604075 supposed to be mapped > to this bug? Why couldn't we forward mirror as usual to RHIT? At the moment Red > Hat is getting pretty strict on the content of the bugs we send over. However, > if there is a prior agreement that these bugs are supposed to go directly to > RHBZ as opposed to RHIT then please let me know. Thanks. Could you reverse mirror and attach the bug mentioned above to this one. The information you suggested for RHIT are already available in the RH BZ as this has been automatically reported by anaconda. Further please attach the logs.tgz to the RHBZ as this has been requested by anaconda team. Please also clear the NEEDINFO flag which is currently set for me. Thanks. Created attachment 426322 [details]
logs.tgz
------- Comment on attachment From michael.holzheu.com 2010-06-15 07:40 EDT-------
Additional info:
- Please create the following tar archive and contact your bug assistant:
tar --exclude=/tmp/install.img -cvzf /logs.tgz /tmp /etc
------- Comment From Praveen.Pandey.com 2010-07-20 03:05 EDT------- I check it on RHEL6.0 snap7 but I provide the normal DASD it having 7043 M.B space and go through all the reproducible steps and I do not find any issue means all installation works fine and also rebooting system it is boot able . If there is any issue regarding the DASD memory.Please clear that. ------- Comment From michael.holzheu.com 2010-07-20 05:29 EDT------- Just to be sure: Have you used an FBA DASD? What shows lsdasd? ------- Comment From Praveen.Pandey.com 2010-07-30 01:50 EDT------- I also verified it on RHEL6.0 snap8 but I provide the normal DASD it having 7043 M.B space and go through all the reproducible steps and I do not find any issue means all installation works fine and also rebooting system is boot able . ------- Comment From Praveen.Pandey.com 2010-07-30 03:17 EDT------- reply to comment #12 I am not using FBA DASD. Log : [root@h0530019 ~]# lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks ============================================================================== 0.0.5d36 active dasda 94:0 ECKD 4096 7043MB 1803060 ------- Comment From michael.holzheu.com 2010-07-30 05:14 EDT------- FBA DASDs are not working. Please test with FBA. You can define a temporary FBA dasd as follows: #cp def vfb-512 <devno> <blocks> ------- Comment From Praveen.Pandey.com 2010-07-30 07:18 EDT------- yes I verified it on RHEL6 snap8 using FBA DASD ,bug is still there means going through all reproducible step.on formatting step it shows that ERROR: Formatting failed (an error was encountered while formatting device /dev/dasda2) I also attach the sanpshot .. Created attachment 435530 [details]
FBA installation
------- Comment (attachment only) From Praveen.Pandey.com 2010-07-30 07:19 EDT-------
This looks like it might well be fixed by the parted patches from 629791 (and 634980). Fedora 14 uses parted 2.3 which is significantly different from parted 2.2 used in RHEL6 so those patches likely won't apply here. Can you partition the FBA DASD using fdisk or other tools from tty2 and then only format them using Anaconda? I'm trying to understand what is supposed to be possible with these devices and where the core problem lies. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Brian, I partitioned FBA DASD before starting vnc session: [anaconda root@rtt6 root]# lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks ============================================================================== 0.0.eeee active dasdb 94:4 FBA 512 953MB 1953128 [anaconda root@rtt6 root]# parted /dev/dasdb GNU Parted 2.1 Using /dev/dasdb Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) mklabel New disk label type? dasd Warning: The existing disk label on /dev/dasdb will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? yes Error: fdasd: Unsupported disk type -- This is not an ECKD disk! This disk type is not supported! (parted) mklabel New disk label type? msdos Warning: The existing disk label on /dev/dasdb will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? YES (parted) mkpart primary 0 900 (parted) quit Information: You may need to update /etc/fstab. During the installation I only formatted /dev/dasdb1 as ext4 and mounted it as /. Installation failed when writing changes to disk with message: An error occurred mounting device /dev/dasdb1 as /: mount failed: (9, None). This is a fatal error and the install cannot continue. *** This bug has been marked as a duplicate of bug 601855 *** The Installer is the value-added code from Red Hat. - Red Hat have to maintain this differentiator for RHEL - System z cannot take ownership for the installer For sure System z will offer help like in the past. If you want to track this via Fedora - fine but that makes no difference Although its obvious I re-call - it is very important that the installer get improved for our customers (In reply to comment #23) > The Installer is the value-added code from Red Hat. > - Red Hat have to maintain this differentiator for RHEL > - System z cannot take ownership for the installer > For sure System z will offer help like in the past. > > If you want to track this via Fedora - fine but that makes no difference > > Although its obvious I re-call > - it is very important that the installer get improved for our customers This bug has been closed as a duplicate of bug 601855, please do not reopen. *** This bug has been marked as a duplicate of bug 601855 *** |