DB2

The 2nd hdd with hdd password set in BIOS will be not availible when you remove it and then re-plug it back in. Once get in this case, you must reboot your Thinkpad with this 2nd hdd pluged in. Then the driver letter in the 2nd hdd come back.

Searched web, didn't get any solution or discussion about it. 

The answer is it's possible.

the APS(Active Protection System) feature of 2nd hdd on Ultra Slim is supported in the newer version of APS software. It requires version 1.30b or newer.

• Symptoms corrected by the latest Active Protection System
  http://www-306.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-58650
  

Install Red Hat Enterprise Linux 3 on 2nd hdd in my thinkpad with usb dvd-rom.

Choose Grub as boot selector and install grub on the first sector of 2nd hdd without lba support. Reboot, hit F12, choose 2nd hdd to boot up, during booting, screen showed GRUB 4 characters, then stop there. Grub can't continue to load boot menu.

Boot using linux cd in rescue mode, reinstall grub with on the first sector of 2nd hdd:

$ grub-install /dev/hdc

Reboot, hit F12, choose 2nd hdd, during boot, can't see the boot menu, but grub continues to load and get following error message:

• Cannot mount selected partition
• This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB.
  

$ cat /boot/grub/device.map

fd0  /dev/fda
hd0  /dev/hda
hd1  /dev/hdc 

$ cat /boot/grub/grub.conf 

title Linux
root (hd1,0)
kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/
initrd /initrd-2.4.21-4.EL.img

title Windows
root (hd0,0)
chainload (+1)

Finally, I caught the point. When choosing 2nd hdd as first boot device by F12 during booting, BIOS will see it as hda, and the ist native hdd will change from hda to hdc.

During the grub installing, grub will guess the boot devices list, and generate a device.map file and grub.conf with the detected settings. that time, grub is right, but when booting from 2nd hdd, the thing changes.

I had it working with following settings.

$ cat /boot/grub/device.map

fd0  /dev/fda
hd0  /dev/hda
hd1  /dev/hdc 

$ cat /boot/grub/grub.conf 

title Linux
root (hd0,0)
kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/
initrd /initrd-2.4.21-4.EL.img

title Windows
root (hd1,0)
chainload (+1)

But i am still wondering why linux could keep recognize /dev/hdc but grub not? needs answer.

refer to:

• http://www.gnu.org/software/grub/manual/html_node/Stage2-errors.html
  
• http://forums.gentoo.org/viewtopic.php?t=120802

I got a new 2.5" HDD and a HDD adapter for my thinkpad.

• Hitachi HTS541080G9AT00, 80G, 8M cache, 5400 RPM, UDMA 5
• Thinkpad 2nd HDD adapter for Ultrabay Slim 

the 2nd hdd on thinkpad needs the hdd adapter using Ultrabay Slim interface.

it's very easy to fix and plug in, but there's a little gappy between the hdd and adapter.

windows xp is able to install driver for the new hardware automatically, the 2nd hdd appears as a new ATA device on Secondary IDE Channel and works on UDMA 5(ATA-100) mode.

By copying files, the 2nd hdd is faster than the native one. I found my Primary IDE Channel is working on PIO mode, that's a problem.

I have fixed the problem above, now the native one works on UDMA 5. 

I query the warranty info at:

• http://www.hitachigst.com/warranty/jsp/arma71.jsp

I don't find China in regions list, so choose Hong Kong instead, enter serial number: XBGDN7DE

Result: