GNU GRUB - Bugs: bug #31843, grub doesn't work with encrypted...
You are not allowed to post comments on this tracker with your current authentication level.
bug #31843: grub doesn't work with encrypted disk (seagate momentus ST9250414ASG)
Submitter: | ju <theju> | ||
Submitted: | Fri 10 Dec 2010 07:46:13 AM UTC | ||
Category: | Disk & Partition | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Hardware-specific |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | theju |
Open/Closed: | Open | Release: | 1.98 |
Release: | Reproducibility: | Every Time | |
Planned Release: | 2.03+ |
Fri 07 Jan 2011 04:47:57 PM UTC, comment #3: |
Vladimir Serbinenko <phcoder>![]() |
Fri 07 Jan 2011 04:35:37 PM UTC, comment #2: There is no software. It is hardware full disk encryption. Untill disk encryption is activated via Wave software, the disk is lock at startup. You can unlock with a preboot manager provide by wave. |
ju <theju> |
Fri 07 Jan 2011 04:22:45 PM UTC, comment #1: What kind of disk encryption software is used? It seems to be the issue with the software in question rather than with GRUB. |
Vladimir Serbinenko <phcoder>![]() |
Fri 10 Dec 2010 07:46:13 AM UTC, original submission:
When crypted disk is enable grub did not recognize the disk at first boot :
|
ju <theju> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-03-02 | phcoder | Item Group | Software Error | ![]() |
Hardware-specific |
Planned Release | None | ![]() |
2.03+ |
Hard-disk level security is shown to be deactivated: "not locked", "not enabled".
A likely explanation is that BIOS caches few sectors and so GRUB still partially sees the encrypted data or the sectors from disk manufacturer software. You can try to circumvent this cache by installing with --disk-module=ata.
This is workaround and the real solution would be if manufacturer software somehow cleaned the BIOS cache.