How to hotswap Ultrabay devices - Revision history

ThinkGNU: R400 etc is not the latest generation anymore. The userland software is not merely tools. Spelling and grammar. Hdparm sets the password, not Linux.

2025-10-27T02:53:54Z

R400 etc is not the latest generation anymore. The userland software is not merely tools. Spelling and grammar. Hdparm sets the password, not Linux.

Kevinoid: Remove hdparm -Y from eject script (see discussion for rationale)

2024-01-11T00:58:05Z

Remove hdparm -Y from eject script (see discussion for rationale)

Korgman: /* Script for Ultrabay eject */

2020-12-31T20:21:31Z

‎Script for Ultrabay eject

Kevinoid: Check docked only if $ULTRABAY_SYSDIR does not exist to avoid problems due to incorrect docked value (see talk page)

2017-03-14T19:49:36Z

Check docked only if $ULTRABAY_SYSDIR does not exist to avoid problems due to incorrect docked value (see talk page)

Schmutzfinger: /* Modern systems (using the ahci or ata_piix drivers) */

2011-07-09T20:55:29Z

‎Modern systems (using the ahci or ata_piix drivers)

Tonko: add T410

2010-11-07T11:26:17Z

add T410

Jicama: add T510

2010-11-07T02:02:13Z

add T510

CanadianGuy: /* Letting the BIOS unlock the disk by suspending the computer */ step-by-step probably overkill

2010-10-29T01:44:32Z

‎Letting the BIOS unlock the disk by suspending the computer: step-by-step probably overkill

CanadianGuy: /* Letting the BIOS unlock the disk by suspending the computer */

2010-10-29T01:39:06Z

‎Letting the BIOS unlock the disk by suspending the computer

CanadianGuy: /* Letting the BIOS unlock the disk by suspending the computer */

2010-10-29T01:37:35Z

‎Letting the BIOS unlock the disk by suspending the computer

@@ Line 14: / Line 14: @@
 ThinkPads like the R60, T60 and Z60 series are also hybrids, but they use a native SATA HDD internal. Ultrabay still uses legacy IDE (PATA) though. So just like with the previous models you end up with two separate drivers for the internal HDD and the Ultrabay.
-The latest generation ThinkPads like the R400, R500, T400, T500, W500, W700, X200, and X301 are all fully SATA for both the internal HDD and the Ultrabay device, so both are handled by the same SATA driver.
+Newer generation ThinkPads like the R400, R500, T400, T500, W500, W700, X200, and X301 are all fully SATA for both the internal HDD and the Ultrabay device, so both are handled by the same SATA driver.
 {{Todo|Figure out in which category the X60 series ThinkPads truly belong. Some of these machines might have been shipped with a 1.8" HDD which is likely to be PATA, in fact the HMM even states so. But tabook and ltwbook only lists SATA models, so the 1.8" model might never have shipped. But even if it did there will be a SATA-PATA bridge chip, so from the OS it will look like SATA.}}
@@ Line 63: / Line 63: @@
 The following applies when using the <tt>ahci</tt> or <tt>ata_piix</tt> driver (which supercedes the old <tt>ide_disk</tt> driver).
-You should at least be using a distribution with kernel 2.6.23. If you have a distribution with an older kernel, please update your distribution, as in addition to a newer kernel, you will need some of the newer userland tools.
+You should at least be using a distribution with kernel 2.6.23. If you have a distribution with an older kernel, please update your distribution, as in addition to a newer kernel, you will need some of the newer userland software.
 ===Using libata-acpi and udev===
@@ Line 397: / Line 397: @@
 ===Disable ultrabay at boot time===
-To safe some energy you can create an init.d start script to automatically "eject" the ultrabay at boot time<br />
+To save some energy you can create an init.d start script to automatically "eject" the ultrabay at boot time<br />
 vim /etc/init.d/stop-ultrabay
@@ Line 411: / Line 411: @@
   # Script to shutdown ultrabay at boot time. To reenable, simply push the ultrabay eject lever
-  # and put it again.
+  # and put it in again.
   # By Frank Doelitzscher, 2010-08-04
+  #
@@ Line 475: / Line 475: @@
 ==Password protected HDD==
-{{WARN|Do not attempt to set a new HDD password from Linux, if you succeed you may find you can no longer unlock the drive or remove the password in any way}}
+{{WARN|Do not attempt to set a new HDD password with hdparm - if you succeed, it is likely that the drive will not unlock and it will not be possible to remove the password either.}}
 There are multiple issues with hotplugging a password protected HDD. In short, it does not work from within the operating system. You will need to reboot, or use the suspend/wakeup procedure below, and let the BIOS do the unlock.
 ===hdparm===
@@ Line 489: / Line 489: @@
 But a fatal flaw is to use hdparm to actually set a password, if you do you will find the following issues
 * setting a Master password will appear to succeed, but in fact does nothing
-* setting a User password does succeed, but you will no longer be able to unlock or remove the password using either hdparm or the BIOS. hdparm will just give IO errors, and the BIOS will report the password being wrong. It is speculated that the BIOS does some kind of hashing to the password, which is why setting the PW from the BIOS and setting the PW with hdparm is incompatible.
+* setting a User password does succeed, but you will no longer be able to unlock or remove the password using either hdparm or the BIOS. hdparm will just give IO errors, and the BIOS will report the password being wrong. It is speculated that the BIOS applies some kind of hashing to the password, which is why setting the PW from the BIOS and setting the PW with hdparm is incompatible.
   # hdparm --verbose --user-master u --security-disable test /dev/sdb

@@ Line 147: / Line 147: @@
          exit 1 if $bad;
 EOPERL
+}
@@ Line 170: / Line 163: @@
+	}
 	sync
-	# Nicely power off the device
+	# Let HAL+KDE notice the unmount
 	sleep 0.5
 	# Unregister this SCSI device:

@@ Line 95: / Line 95: @@
 # To find the right value, insert the UltraBay optical drive and run:
 # udevadm info --query=path --name=/dev/sr0 | perl -pe 's!/block/...$!!'
 if [ "$DEVPATH" = "" ]
-then
+# Try to guess DEVPATH. It works with optical drive or Hard disk (or SSD)
-   DEVPATH="/devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0"
+if [ "$DEVPATH" = "" ]; then
 fi

@@ Line 148: / Line 148: @@
+}
-if [ $( cat $dock/docked ) == 0 ]; then
+if [ -d $ULTRABAY_SYSDIR ]; then
          logger ultrabay_eject dock reports empty
 else
-	if [ -d $ULTRABAY_SYSDIR ]; then
+	logger ultrabay_eject bay occupied but incorrect device path $DEVPATH
-		logger ultrabay_eject dock occupied, shutting down storage device $DEVPATH
+	notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Bay occupied but incorrect device path"
-		sync
+	echo 2 > /proc/acpi/ibm/beep  # triple error tone
-		# Unmount filesystems backed by this device
+	exit 1
 fi

← Older revision		Revision as of 20:55, 9 July 2011
Line 246:		Line 246:
	This was tested on a T61p running Gentoo with tuxonice 2.6.28-r8 without any issues.		This was tested on a T61p running Gentoo with tuxonice 2.6.28-r8 without any issues.

		+	===udisks support===
		+	Just like the HAL support mentioned below this is only about marking the device as hotpluggable.

		+	Recently distributions do not use HAL anymore. On these systems Gnome, KDE, etc. use udisks instead to discover installed disks. So today most people will have to tell udisks that the ultrabay device is a removeable device. The HAL configuration described below does not work anymore.
		+
		+	Udisks reads device properties from udev. In order to force a device to be considered "removeable" we have to set the udev property "UDISKS_SYSTEM_INTERNAL" to "0". (man 7 udisks)
		+	In order for this to work you need at least version 1.0.3 of udisks.
		+
		+	Here is an example of a udev rule that adds the property. You can add it to the file that contains the other utrabay rules (i.e. {{path\|/etc/udev/rules.d/50-thinkpad-ultrabay.rules}}). You may have to adjust the DEVPATH.
		+	<pre>
		+	SUBSYSTEMS=="block", DEVPATH=="/devices/pci0000:00/0000:00:1f.1/host4/*", ENV{UDISKS_SYSTEM_INTERNAL}="0"
		+	</pre>
		+
		+	Now tell udev to reread the rules:
		+	<pre>
		+	udevadm control --reload-rules
		+	</pre>
		+
		+	Now your window manager should give you a notification when you plug in a disk into the ultrabay.

	===HAL support===		===HAL support===

@@ Line 357: / Line 357: @@
          </match>
-         <!-- Lenovo ThinkPad T510 -->
+         <!-- Lenovo ThinkPad T410, T510 -->
-         <match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="T510">
+         <match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="T410;T510">
            <match key="storage.bus" string_outof="pci;scsi">
              <match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_3b2f_scsi_host_0_scsi_device_lun0">

@@ Line 488: / Line 488: @@
 ===Letting the BIOS unlock the disk by suspending the computer===
-A password protected disk can be unlocked by ensuring the laptop has been suspended '''before''' inserting the disk into the Ultrabay.  Upon waking up the computer the BIOS should prompt for the password, and provided you enter it correctly, will unlock the disk.  Once Linux regains control it may be necessary to re-scan the SCSI bus to find the disk and make it available, using the command "sudo rescan-scsi-bus.sh".
+A password protected disk can be unlocked by ensuring the laptop has been suspended '''before''' inserting the disk into the Ultrabay.  The device being removed should still be ejected before suspending the laptop.
-In Step-by-Step format, assuming the Ultrabay device is device #1 on the SCSI bus:
+Upon waking up (resuming) the computer the BIOS should prompt for the password, and provided you enter it correctly, will unlock the disk.  Once Linux regains control it may be necessary to re-scan the SCSI bus to find the disk and make it available, using the command "sudo rescan-scsi-bus.sh".
-Step 1: Eject the current Ultrabay device by issuing the command "echo 1 |sudo tee /sys/bus/scsi/devices/1:0:0:0/delete" in a terminal window or console, and then physically remove the device that's being ejected.
+This is confirmed to work on a T61 running Ubuntu 8.04, (kernel 2.6.24) with the scsitools package installed.
 ===libata EH going crazy===

@@ Line 496: / Line 496: @@
 Step 2: Suspend the computer using Fn-F4
-Step 3: Once the computer has finished suspending, insert the locked drive into the Ultrabay.
+Step 3: Once the computer is suspended, insert the locked drive into the Ultrabay.
-Step 4: Wake up the laptop, and enter your HD password when prompted (the fingerprint reader won't work, sorry)
+Step 4: Wake up (resume) the laptop, and enter your HD password when prompted (the fingerprint reader won't work, sorry)
 Step 5: Once the OS regains control, enter the command "sudo rescan-scsi-bus.sh" at a command prompt.