Recently I've been getting 2100 hard drive initialization errors on by X61 Tablet. It seems to be related to shocks as so far they've only occurred after the laptop has been bumped. This lead me to believe that the APS has been triggered. However, as I understand it that is a software based solution and, given that I run Linux, shouldn't cause the issue. Both times this has happened so far the laptop has been in sleep mode so not sure if that has anything to do with it.
Doing a search brings me to the solution of updating the
hard drive's firmware, but my WD hard drive does not appear to be on the list of supported drives.
Code:
*-disk
description: ATA Disk
product: WDC WD3200BEVT-2
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sda
version: 11.0
serial: WD-WXE508JYJ106
size: 298GiB (320GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=e11595f6
*-volume:0
description: EXT4 volume
vendor: Linux
physical id: 1
bus info: scsi@2:0.0.0,1
logical name: /dev/sda1
logical name: /
version: 1.0
serial: 8a5f1d5d-1b57-4c9a-8177-576e8b630d32
size: 288GiB
capacity: 288GiB
capabilities: primary bootable journaled extended_attributes large_files huge_files dir_nlink recover extents ext4 ext2 initialized
configuration: created=2011-07-14 22:19:43 filesystem=ext4 lastmountpoint=/ modified=2011-08-29 09:14:04 mount.fstype=ext4 mount.options=rw,noatime,errors=remount-ro,barrier=1,data=ordered mounted=2011-09-01 08:18:37 state=mounted
*-volume:1
description: Windows FAT volume
vendor: MSWIN4.1
physical id: 2
bus info: scsi@2:0.0.0,2
logical name: /dev/sda2
version: FAT32
serial: 34d1-a903
size: 6072MiB
capacity: 6091MiB
capabilities: primary boot fat initialized
configuration: FATs=2 filesystem=fat
*-volume:2
description: Linux swap volume
physical id: 3
bus info: scsi@2:0.0.0,3
logical name: /dev/sda3
version: 1
serial: 9240a86b-7430-44c1-9b25-cac1eeeb2e7f
size: 4GiB
capacity: 4GiB
capabilities: primary nofs swap initialized
configuration: filesystem=swap pagesize=4096
It seems that waiting awhile (10-15 minutes) causes the error to go away and then the laptop continues to run without any problems. I have pushed on the hard drive caddy during this time so I can't rule out the hard drive dislodging on impact, but I feel that's unlikely. In any case I'm not too worried at this point, but figured I should ask about it in case there's something I should be doing.
FAQ
Search
Login
Register
