diff options
author | Robin H. Johnson <robbat2@gentoo.org> | 2013-12-16 09:31:19 -0800 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2013-12-16 12:41:57 -0500 |
commit | b8bd6dc36186fe99afa7b73e9e2d9a98ad5c4865 (patch) | |
tree | ead6b981a436b07c0dc8f40f568777d323fdabd9 /Documentation/kernel-parameters.txt | |
parent | 6fec88712cea016b1fc929fee53f67e3993194a6 (diff) | |
download | talos-obmc-linux-b8bd6dc36186fe99afa7b73e9e2d9a98ad5c4865.tar.gz talos-obmc-linux-b8bd6dc36186fe99afa7b73e9e2d9a98ad5c4865.zip |
libata: disable a disk via libata.force params
A user on StackExchange had a failing SSD that's soldered directly
onto the motherboard of his system. The BIOS does not give any option
to disable it at all, so he can't just hide it from the OS via the
BIOS.
The old IDE layer had hdX=noprobe override for situations like this,
but that was never ported to the libata layer.
This patch implements a disable flag for libata.force.
Example use:
libata.force=2.0:disable
[v2 of the patch, removed the nodisable flag per Tejun Heo]
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: stable@vger.kernel.org
Link: http://unix.stackexchange.com/questions/102648/how-to-tell-linux-kernel-3-0-to-completely-ignore-a-failing-disk
Link: http://askubuntu.com/questions/352836/how-can-i-tell-linux-kernel-to-completely-ignore-a-disk-as-if-it-was-not-even-co
Link: http://superuser.com/questions/599333/how-to-disable-kernel-probing-for-drive
Diffstat (limited to 'Documentation/kernel-parameters.txt')
-rw-r--r-- | Documentation/kernel-parameters.txt | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 50680a59a2ff..b9e9bd854298 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1529,6 +1529,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted. * atapi_dmadir: Enable ATAPI DMADIR bridge support + * disable: Disable this device. + If there are multiple matching configurations changing the same attribute, the last one is used. |