Changes between Version 22 and Version 23 of FAQ
- Timestamp:
- Aug 23, 2010, 8:58:18 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQ
v22 v23 165 165 ---- 166 166 167 === Smartmontools for FireWire, USB, and SATA disks/systems ===168 169 As for USB and FireWire (IEEE 1394) disks and tape drives, the news167 === Smartmontools for !FireWire, USB, and SATA disks/systems === 168 169 As for USB and !FireWire (IEEE 1394) disks and tape drives, the news 170 170 is not good. They appear to the operating system as SCSI devices but their 171 171 implementations do not usually support those SCSI commands needed by … … 175 175 compliance means that they tend to only support the bare minimum of 176 176 commands needed for device operation (i.e. SMART support is an unsupported 177 extra). Hopefully external USB and Firewire devices will support SAT in177 extra). Hopefully external USB and !Firewire devices will support SAT in 178 178 the future, see below. Some USB device based on cypress chips support a 179 179 proprietary protocol (ATACB) that allow to send raw ATA commands (i.e. … … 239 239 ---- 240 240 241 === Smartmontools for SCSI disks and tapes ( TapeAlert) ===241 === Smartmontools for SCSI disks and tapes (!TapeAlert) === 242 242 243 243 Smartmontools for SCSI disks and tapes (including medium changers) is … … 262 262 263 263 '''If your drive is not in the database, pleaes check the 264 [http://sourceforge.net/project /showfiles.php?group_id=64297sourceforge project page]264 [http://sourceforge.net/projects/smartmontools/files/ sourceforge project page] 265 265 to be sure that you are using the latest smartmontools release. Each 266 266 new release has additional drives added to the database. Please do … … 360 360 forcing the reallocation to take place may entail some loss of data. 361 361 Because the commands that force such reallocation are 362 ''Vendor Specific'', most manufactu ers provide a utility for this362 ''Vendor Specific'', most manufacturers provide a utility for this 363 363 purpose. It may cause data loss but can repair damaged sectors (at 364 364 least, until it runs out of replacement sectors). … … 389 389 === {{{smartctl}}} aborts with the message "...SMART_GET_VERSION failed" on Windows. What is going wrong? === 390 390 391 A failing [http://msdn 2.microsoft.com/en-us/library/ms803644.aspx SMART_GET_VERSION] call means that the device driver does not implement the I/O controls (see [wiki:FAQ#OnWindowssmartctlprintsthemessage:...LogReadfailed:Functionnotimplemented below]) to access ATA SMART functionality.391 A failing [http://msdn.microsoft.com/en-us/library/ff566202.aspx SMART_GET_VERSION] call means that the device driver does not implement the I/O controls (see [wiki:FAQ#OnWindowssmartctlprintsthemessage:...LogReadfailed:Functionnotimplemented below]) to access ATA SMART functionality. 392 392 393 393 Some Windows drivers for (S)ATA controllers are implemented as SCSI class drivers. This is usually the case for drivers which support RAID. Unfortunately, such drivers do not support the ATA specific SMART I/O controls. … … 407 407 To access ATA SMART functionality on Windows, smartmontools uses the 408 408 I/O control calls 409 [http://msdn 2.microsoft.com/en-us/library/ms804269.aspx SMART_RCV_DRIVE_DATA] and410 [http://msdn 2.microsoft.com/en-us/library/ms803645.aspx SMART_SEND_DRIVE_CMD].409 [http://msdn.microsoft.com/en-us/library/ff566204.aspx SMART_RCV_DRIVE_DATA] and 410 [http://msdn.microsoft.com/en-us/library/ff566206.aspx SMART_SEND_DRIVE_CMD]. 411 411 These calls were available since Win95 OSR2. 412 412 An example program from Microsoft can be found … … 429 429 430 430 A new I/O control call 431 [http://msdn 2.microsoft.com/en-us/library/ms804551.aspx IOCTL_ATA_PASS_THROUGH]431 [http://msdn.microsoft.com/en-us/library/ff559309.aspx IOCTL_ATA_PASS_THROUGH] 432 432 is available since Win2003 and XP SP2. 433 433 It should be supported by most new drivers. Experimental code using … … 465 465 Apparently some of the older SMART firmware on IBM disks can 466 466 interfere with the regular operation of the disk. If you have this 467 problem, here are some links to an IBM Firmware Upgrade that fixes the problem: 468 469 [http://www.geocities.com/dtla_update/ Geocities Site][[BR]] 470 [http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42215 IBM Site #1][[BR]] 471 [http://www-1.ibm.com/support/docview.wss?uid=psg1MIGR-42215 IBM Site #2] 467 problem, here is a link to an 468 [http://www-307.ibm.com/pc/support/site.wss/MIGR-42215.html IBM DeskStar hard disk drive firmware update]. 472 469 473 470 ----