Bug 1430145
| Summary: | Installation does not detect raid disks | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dr M C Nelson <drmcnelson> |
| Component: | dmraid | Assignee: | LVM and device-mapper development team <lvm-team> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | agk, bmr, heinzm, lvm-team, prajnoha, prockai, p.sherman, zkabelac |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:51:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dr M C Nelson
2017-03-07 23:37:48 UTC
It seems that this computer has Intel Rapid Storage Technology. If so, then perhaps the bug is that Linux is not recognizing and using the RST corrrectly. What's the raid config as of raid bios settings? FWIW: depending on the missing information, this may be the wrong component. could be mdadm rather. (In reply to Heinz Mauelshagen from comment #2) > What's the raid config as of raid bios settings? The raid config does not appear in the bios settings. For comparison, with the Ubuntu live usb, the disks utility shows the partitions within the raid partition on the hard drive, but again, cannot do anything with them. The install to disk program, similarly to the fedora program, does not show the hard drives. (In reply to Heinz Mauelshagen from comment #3) > FWIW: depending on the missing information, this may be the wrong component. > could be mdadm rather. I am open to that, you guys know the architecture best. If you want, you can send me a script or a list of commands to execute in the live system to generate more information. Similar problem on new Lenovo Legion Y520. Intel disk controller set to "RST Premium" mode. System has SSD and HDD. "Fast boot" option disabled. Win 10 shows two separate disk drives, no raid defined. Research indicates that Windows is using RST features to improve SSD longevity which suggests that new systems with SSD will all have this feature activated. Reset disk controller to AHCI mode and both disk drives became visible to F26 booted from DVD. Win 10, installed on SSD, will not boot with controller in this mode. There are no RAID definition options in the system setup screens, just the option to use the disk controler in AHCI or RST mode. (In reply to Philip Sherman from comment #7) That means this problem is going to be coming a lot more often and may even become ubiquitous. Therefore the Linux install needs to accommodate this. While not able to do that, an appropriate text needs to be added to the release notes. Workaround found. Windows can be altered to allow changing the disk controller to AHCI mode using the following procedure when no RAID is defined:
1. From running Win system, enter command using an administrator command prompt to force win to boot in "safe" mode.
2. Shutdown, enter hardware setup on restart and change disk controller to AHCI mode.
3. Let win boot into safe mode. Use the matching command to remove forced safe mode booting.
4. Reboot system verifying normal boot.
Win "safe" mode will try loading all available disk controller code, flagging the working one as the one to use for future boots. Normal boot only uses the controller code that worked on the last boot.
Once the disk controller is in AHCI mode, Fedora installed normally.
Win commands:
bcdedit /set {default} safeboot minimal
bcdedit /deletevalue {default} safeboot
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |