https://bugzilla.novell.com/show_bug.cgi?id=299267#c19
--- Comment #19 from Tejun Heo 2007-08-28 18:08:52 MST ---
HPA unlock support is now included in libata but it isn't enabled by default
for the following reasons.
* compatibility with older libata
* BIOSen got more involved with system operation (ACPI and stuff) and may
expect HPA to be in certain state.
* Not as necessary as before. HPA used to be used to limit disk size to work
around dumb BIOSen or OSes making HPA unlocking much more important but it
isn't the case anymore.
The magic parameter is libata.ignore_hpa. If set to 1, libata will unlock the
HPA area, which I don't think we should do by default. Here are possible
alternatives.
* Make a boot menu to enable HPA unlocking and instruct the user about it if
partition table doesn't make sense so that the user can restart.
* (More complex) HPA can be unlocked from the userland. If partition table
reaches over the end of the device, unlock HPA on all HDDs, detach all by
echoing to sysfs delete node and request rescan in order by echoing to
/sys/class/scsi_host/hostX/scan. When rescan is complete, the system is
running with HPA unlocked devices. Retry partitioning.
In both cases, the installer should remember that HPA needs unlocking and adds
'libata.ignore_hpa=1' to menu.lst during installation.
Thanks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.