Folks, I have a new dell laptop. I tried to install Fedora 33 on it, but it failed to find any disks. I searched the internet and discovered that if my BIOS has RAID enabled F33 is unable to find any drives. I disabled RAID and enable AHCI and was then able to install and boot F33. I then tried to boot Windows 10. This failed until I entered the bitlock key. I then went back into the BIOS and re-enabled RAID and verified Windows 10 boots without error, but Fedora 33 no longer does since it can't find any drives. What if I want RAID enabled? Is there a solution to this problem?
Paolo
Paolo Galtieri writes:
Folks, I have a new dell laptop. I tried to install Fedora 33 on it, but it failed to find any disks. I searched the internet and discovered that if my BIOS has RAID enabled F33 is unable to find any drives. I disabled RAID and enable AHCI and was then able to install and boot F33. I then tried to boot Windows 10. This failed until I entered the bitlock key. I then went back into the BIOS and re-enabled RAID and verified Windows 10 boots without error, but Fedora 33 no longer does since it can't find any drives. What if I want RAID enabled? Is there a solution to this problem?
I am not familiar with this laptop, but I'm curious what exactly RAID does, on it? Does it have two SSD drives in a RAID configuration? Why would someone want to do that?
On 1/29/21 2:54 PM, Sam Varshavchik wrote:
Paolo Galtieri writes:
Folks, I have a new dell laptop. I tried to install Fedora 33 on it, but it failed to find any disks. I searched the internet and discovered that if my BIOS has RAID enabled F33 is unable to find any drives. I disabled RAID and enable AHCI and was then able to install and boot F33. I then tried to boot Windows 10. This failed until I entered the bitlock key. I then went back into the BIOS and re-enabled RAID and verified Windows 10 boots without error, but Fedora 33 no longer does since it can't find any drives. What if I want RAID enabled? Is there a solution to this problem?
I am not familiar with this laptop, but I'm curious what exactly RAID does, on it? Does it have two SSD drives in a RAID configuration? Why would someone want to do that?
There are different varieties. One I've seen is a spinning drive with a small SSD used as a cache. I can't imagine why anyone would really want RAID on a laptop. It seems like a waste of space and power to me.
I had the same issue and this article worked for me.
https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-id...
On Fri, 2021-01-29 at 14:12 -0800, Paolo Galtieri wrote:
Folks, I have a new dell laptop. I tried to install Fedora 33 on it, but it failed to find any disks. I searched the internet and discovered that if my BIOS has RAID enabled F33 is unable to find any drives. I disabled RAID and enable AHCI and was then able to install and boot F33. I then tried to boot Windows 10. This failed until I entered the bitlock key. I then went back into the BIOS and re-enabled RAID and verified Windows 10 boots without error, but Fedora 33 no longer does since it can't find any drives. What if I want RAID enabled? Is there a solution to this problem?
Paolo _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On Fri, Jan 29, 2021 at 6:25 PM Kevin Becker kevin@kevinbecker.org wrote:
I had the same issue and this article worked for me.
https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-id...
Dell seems to be the "culprit". I have a Dell desktop where I had almost the same problem, except it was only with the NVME drive. If the BIOS was set to RAID mode, Windows boots and runs normally. Linux will also boot and run, since it is installed on a separate non-NVME drive, but it can't see the Windows partitions, which unfortunately includes /boot/efi. So I can't do any kernel updates (and who knows what else) unless I manually set the SATA mode to AHCI in the BIOS, in which case Linux will boot and see all the drives, but Windows will not boot. This has led to the very annoying position of having to fiddle with the BIOS every time I want to switch OS's. I'll try the process in that article. Thanks for the pointer!
Now if I can only figure out why this damn machine won't resume from hibernation properly. Windows can do it, so I'll bet it's a configuration issue somewhere.
--Greg
Yes, it was a Dell for me as well. I have an XPS 13 which is odd since you can buy it with Linux pre-loaded, but if you get the Windows version is ships with this weird RAID config by default. It has only one drive and I don’t even think there is an option for two so the RAID setting makes no sense.
On Jan 29, 2021, at 10:44 PM, Greg Woods greg@gregandeva.net wrote:
On Fri, Jan 29, 2021 at 6:25 PM Kevin Becker <kevin@kevinbecker.org mailto:kevin@kevinbecker.org> wrote: I had the same issue and this article worked for me.
https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-id... https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci
Dell seems to be the "culprit". I have a Dell desktop where I had almost the same problem, except it was only with the NVME drive. If the BIOS was set to RAID mode, Windows boots and runs normally. Linux will also boot and run, since it is installed on a separate non-NVME drive, but it can't see the Windows partitions, which unfortunately includes /boot/efi. So I can't do any kernel updates (and who knows what else) unless I manually set the SATA mode to AHCI in the BIOS, in which case Linux will boot and see all the drives, but Windows will not boot. This has led to the very annoying position of having to fiddle with the BIOS every time I want to switch OS's. I'll try the process in that article. Thanks for the pointer!
Now if I can only figure out why this damn machine won't resume from hibernation properly. Windows can do it, so I'll bet it's a configuration issue somewhere.
--Greg
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Folks, I tried the process described in the article and it worked for me. I can now boot up into Windows and Linux without issues.
Thank you very much for the pointer.
Paolo
On 1/29/21 7:44 PM, Greg Woods wrote:
On Fri, Jan 29, 2021 at 6:25 PM Kevin Becker <kevin@kevinbecker.org mailto:kevin@kevinbecker.org> wrote:
I had the same issue and this article worked for me. https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci <https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci>Dell seems to be the "culprit". I have a Dell desktop where I had almost the same problem, except it was only with the NVME drive. If the BIOS was set to RAID mode, Windows boots and runs normally. Linux will also boot and run, since it is installed on a separate non-NVME drive, but it can't see the Windows partitions, which unfortunately includes /boot/efi. So I can't do any kernel updates (and who knows what else) unless I manually set the SATA mode to AHCI in the BIOS, in which case Linux will boot and see all the drives, but Windows will not boot. This has led to the very annoying position of having to fiddle with the BIOS every time I want to switch OS's. I'll try the process in that article. Thanks for the pointer!
Now if I can only figure out why this damn machine won't resume from hibernation properly. Windows can do it, so I'll bet it's a configuration issue somewhere.
--Greg
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On Fri, Jan 29, 2021 at 8:45 PM Greg Woods greg@gregandeva.net wrote:
Now if I can only figure out why this damn machine won't resume from hibernation properly. Windows can do it, so I'll bet it's a configuration issue somewhere.
Hibernation is disabled when UEFI Secure Boot is enabled. And even if disabled, which I don't recommend, there are ACPI bugs galore. I don't know how Windows works around them. But it also does seem Microsoft, Apple and hardware vendors are focusing on S0 low power idle (and variations on that theme). Another idea is for the desktop to have some way of saving state but there's no single API that apps can use to do that. https://pagure.io/fedora-workstation/blob/master/f/hibernationstatus.md
On 1/31/21 1:00 AM, Chris Murphy wrote:
On Fri, Jan 29, 2021 at 8:45 PM Greg Woods greg@gregandeva.net wrote:
Now if I can only figure out why this damn machine won't resume from hibernation properly. Windows can do it, so I'll bet it's a configuration issue somewhere.
Hibernation is disabled when UEFI Secure Boot is enabled. And even if disabled, which I don't recommend, there are ACPI bugs galore. I don't know how Windows works around them. But it also does seem Microsoft, Apple and hardware vendors are focusing on S0 low power idle (and variations on that theme). Another idea is for the desktop to have some way of saving state but there's no single API that apps can use to do that. https://pagure.io/fedora-workstation/blob/master/f/hibernationstatus.md
This surrender to making hibernation work is one of the most shameful decision on Fedora side. The listed alternatives are laughable: how can "keep the machine on (with S3 or S0)" be an alternative to "power off the machine"? I'm personally using hibernation sometimes when the battery will not last enough for S3 or when I want to come back to my system after booting something else (including exchanging a disk, for example).
The "it may be broken, let's avoid it" approach is definitely in contrast to the "we are enabling it so bugs can be found" that we have heard for many problematic and disrupting new features.
Regards.
On Sat, Jan 30, 2021 at 5:01 PM Chris Murphy lists@colorremedies.com wrote:
On Fri, Jan 29, 2021 at 8:45 PM Greg Woods greg@gregandeva.net wrote:
Now if I can only figure out why this damn machine won't resume from
hibernation properly. Windows can do it, so I'll bet it's a configuration issue somewhere.
Hibernation is disabled when UEFI Secure Boot is enabled. And even if disabled, which I don't recommend, there are ACPI bugs galore.
I did manage to figure this out. I have to give a shout out to the Arch Linux people for doing an excellent job on their documentation. I frequently find things in there that help with my systems (all Fedora or Raspbian) even though I don't actually run Arch except in a VM for playing around and learning. I found their suspend and hibernate page at https://wiki.archlinux.org/index.php/Power_management/Suspend_and_hibernate to be very helpful. Arch uses something called "mkcpio" rather than "dracut" that Fedora uses, but the main thing it mentions is the need to rebuild the initramfs image to include the "resume" module. That works! And my Dell desktop will now hibernate. The command was just "dracut --add resume" (I first saved a copy of the current img file just in case). I find it interesting that I have been using hibernation on Fedora for years and never had to explicitly do this. I just checked my main Fedora server, and "lsinitrd" shows that there is no "resume" module in the initramfs file. But I have never tried hibernating the server. My laptop *does* have the resume module even though I never explicitly included it. There is nothing I can find in /etc/dracut that specifies that the resume module should be included, but it is there. There is still a lot about how all this works that I don't understand.
And to my embarrassment, I found a previous reference on this list to using dracut to add the resume module for hibernation, but it did not come up in my previous searches of my archived list messages. In there it is suggested that perhaps the resume module was only added in by default if you create a swap partition at install time, but I always do that so I'm not quite sure what happened this time.
I don't use Secure Boot on my desktop or my servers because it makes too many things a lot more painful (like third-party drivers such as nvidia) and since these systems never leave my house, the security risk is minimal.
--Greg
Regarding getting Windows to boot in AHCI mode instead of RAID:
On Fri, Jan 29, 2021 at 6:25 PM Kevin Becker kevin@kevinbecker.org wrote:
I had the same issue and this article worked for me.
https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-id...
This worked for me also. Thanks very much for the pointer.
--Greg
On 1/29/21 5:12 PM, Paolo Galtieri wrote:
Folks, I have a new dell laptop. I tried to install Fedora 33 on it, but it failed to find any disks. I searched the internet and discovered that if my BIOS has RAID enabled F33 is unable to find any drives. I disabled RAID and enable AHCI and was then able to install and boot F33. I then tried to boot Windows 10. This failed until I entered the bitlock key. I then went back into the BIOS and re-enabled RAID and verified Windows 10 boots without error, but Fedora 33 no longer does since it can't find any drives. What if I want RAID enabled? Is there a solution to this problem?
Paolo _______________________________________________
On this list 5/7/20: news://news.gmane.org:119/r9175f$2fqs$1@ciao.gmane.io
On 30/1/21 09:12, Paolo Galtieri wrote:
Folks, I have a new dell laptop. I tried to install Fedora 33 on it, but it failed to find any disks. I searched the internet and discovered that if my BIOS has RAID enabled F33 is unable to find any drives. I disabled RAID and enable AHCI and was then able to install and boot F33. I then tried to boot Windows 10. This failed until I entered the bitlock key. I then went back into the BIOS and re-enabled RAID and verified Windows 10 boots without error, but Fedora 33 no longer does since it can't find any drives. What if I want RAID enabled? Is there a solution to this problem?
Paolo
I had a similar issue but for me it was deliberate, I wanted a raid 5 system but couldn't get one so I settled for a motherboard that had raid 10 onboard. This motherboard had all sata ports as raid, so even though I didn't want raid on my SSD drive it was still on a raid controller along with 4 3TB hard disks to give me 6TB of usable disk space. Even though the raid bios allowed the SSD to be configured as legacy Fedora could still not see any drives (and this is not limited to F33, F32 was the same), but neither could windows 10 see any drives. The raid bios on the motherboard provided functionality to put Windows raid drivers on a flash disk to be loaded at windows install time so that windows could see the drives but it did not provide any linux drivers. From what I have read on the net Fedora Desktop cannot see raid drives at install time (it can work with software raid if the legacy drives are configured that way at linux install time) but Fedora Server can see and work with raid drives. The only way I could use Fedora was to install windows 10 on the raid devices and then install Fedora in a VM on the windows host.
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
-
Chris Murphy -
Greg Woods -
Kevin Becker -
Paolo Galtieri -
Roberto Ragusa -
Sam Varshavchik -
Samuel Sieb -
sean darcy -
Stephen Morris