Custom Query (1463 matches)

Hello,

I encountered this error when testing 3ware support under Windows (XP 32 bit and win7 64bit).

Suppose the drive behind the controller is /dev/sdd,2. Running "smartctl -s on (or off) on /dev/sdd,2" works. However, running "smartctl -s off /dev/sdd" says "Disable failed: Input/output error". After this, the SMART data is accessible neither on "/dev/sdd,2", nor "/dev/sdd". Trying to re-enable it says "Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)". The 3ware web interface also says that it cannot access SMART data on the drive. Only a reboot seems to help.

smartmontools: smartmontools-5.41-0-20110204-r3253.win32-setup.exe. Windows: observed under winxp (32-bit) and win7 (64-bit). Controller: 3ware 9690SA-4I4E, 1 drive attached to port 2.

This is the full log of my commands under winxp:

C:\>smartctl --scan-open
/dev/sda -d ata [ATA] (opened)
/dev/sdb -d ata [ATA] (opened)
/dev/sdc -d ata [ATA] (opened)
/dev/sdd,2 -d ata [ATA] (opened)

C:\>smartctl -s off /dev/sdd,2
smartctl 5.41 2011-02-04 r3253 [i686-w64-mingw32-xp-sp3] (cf-win32-20110204)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Disabled. Use option -s with argument 'on' to enable it.

C:\>smartctl -s on /dev/sdd,2
smartctl 5.41 2011-02-04 r3253 [i686-w64-mingw32-xp-sp3] (cf-win32-20110204)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.


C:\>smartctl -s off /dev/sdd,2
smartctl 5.41 2011-02-04 r3253 [i686-w64-mingw32-xp-sp3] (cf-win32-20110204)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Disabled. Use option -s with argument 'on' to enable it.

C:\>smartctl -s off /dev/sdd
smartctl 5.41 2011-02-04 r3253 [i686-w64-mingw32-xp-sp3] (cf-win32-20110204)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
Error SMART Disable failed: Input/output error
Smartctl: SMART Disable Failed.

A mandatory SMART command failed: exiting. To continue, add one or more '-T perm
issive' options.

C:\>smartctl -s on /dev/sdd,2
smartctl 5.41 2011-02-04 r3253 [i686-w64-mingw32-xp-sp3] (cf-win32-20110204)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

A mandatory SMART command failed: exiting. To continue, add one or more '-T perm
issive' options.

C:\>smartctl -i /dev/sdd
smartctl 5.41 2011-02-04 r3253 [i686-w64-mingw32-xp-sp3] (cf-win32-20110204)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

A mandatory SMART command failed: exiting. To continue, add one or more '-T perm
issive' options.

C:\>smartctl -i /dev/sdd,2
smartctl 5.41 2011-02-04 r3253 [i686-w64-mingw32-xp-sp3] (cf-win32-20110204)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

A mandatory SMART command failed: exiting. To continue, add one or more '-T perm
issive' options.

Thanks, Alexander

I get the following message when I run smartctl version 5.42-2:

program smartctl is using a deprecated SCSI iocto, please convert to SG-IO.

I have 2 USB adapters, one with a JMicron JM20337/8 chip, and another with JMicron JM20339.

The JM20339 is set up to use "-d usbjmicron" in drivedb.

• When I run "smartctl --xall pd1", it prints everything.
• When I run "smartctl --xall -d sat pd1", it prints "Read Device Identity failed: scsi error unsupported scsi opcode".
• Experience with IDE_COMMAND_SECURITY_UNLOCK is described in this ticket.
• There is nothing wrong with the JM20339 drivedb entry.

On the other hand, the JM20337/8, appears to behave differently.

• When I run "smartctl --xall pd1", it prints everything.
• When I run "smartctl --xall -d sat pd1", it also prints everything.
• When I run a custom command (IDE_COMMAND_SECURITY_UNLOCK), letting it use the JMicron pass-through, the command appears successful. Sense data empty, no check condition. But, the disk was not unlocked. Attempting this 5 times, even with the wrong password, does not result in exceeded attempts.
• When I run a custom command (IDE_COMMAND_SECURITY_UNLOCK), this time specifying "-d sat", the command appears successful. Sense data empty, no check condition. 2 differences though:
  1. With the correct password, the disk is actually unlocked.
  2. With the wrong password, there is still no sense data or check condition, but after 5 attempts, security data indicates attempts exceeded.

The "custom command" code is described here.

Conclusion: It is slightly beneficial to change the JM20337/8 drivedb device type to sat in order to improve the chances of certain commands succeeding. Exact line to be changed The JM20337/8 appears very buggy. It's even worse than the JM20339 which at least returned a check condition for failed commands. Changing JM20337/8 to sat makes a bad situation slightly better.