PeterB Posted July 13, 2012 Share Posted July 13, 2012 This isn't meant to be a complaint, or even a fault report - more an observation. I've just purchased an e-SATA/usb hard drive docking station. When connected via e-SATA, everything appears to work well, and as expected. When I connect via usb, preclear reports : smartctl may not be able to run on /dev/sdh with the -d ata option. however this should not affect the clearing of a disk. smartctl exit status = 2 smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 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 permissive' options.$ If I add the -D option to the preclear command, the following is reported: smartctl may not be able to run on /dev/sdh. however this should not affect the clearing of a disk. smartctl exit status = 1 smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net /dev/sdh: Unknown USB bridge [0x152d:0x2509 (0x100)] Smartctl: please specify device type with the -d option. However, if I add the '-d usbjmicron' option to the command line, smartctl works. This is all well and good and, perhaps, understandable. The only odd thing is that unMENU is able to report SMART data via the usb connection without any fiddling - it seems to work things out for itself. Quote Link to comment
Joe L. Posted July 13, 2012 Share Posted July 13, 2012 This isn't meant to be a complaint, or even a fault report - more an observation. I've just purchased an e-SATA/usb hard drive docking station. When connected via e-SATA, everything appears to work well, and as expected. When I connect via usb, preclear reports : smartctl may not be able to run on /dev/sdh with the -d ata option. however this should not affect the clearing of a disk. smartctl exit status = 2 smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 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 permissive' options.$ If I add the -D option to the preclear command, the following is reported: smartctl may not be able to run on /dev/sdh. however this should not affect the clearing of a disk. smartctl exit status = 1 smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net /dev/sdh: Unknown USB bridge [0x152d:0x2509 (0x100)] Smartctl: please specify device type with the -d option. However, if I add the '-d usbjmicron' option to the command line, smartctl works. This is all well and good and, perhaps, understandable. The only odd thing is that unMENU is able to report SMART data via the usb connection without any fiddling - it seems to work things out for itself. Interesting observation. Glad you figured out the device option needed to access your USB connected drive. The "-d device_type" option exists for exactly the reason you've seen. for when smartctl is unable to figure it out on its own. Quote Link to comment
PeterB Posted July 13, 2012 Author Share Posted July 13, 2012 The "-d device_type" option exists for exactly the reason you've seen. for when smartctl is unable to figure it out on its own. Indeed ... but I just wonder how unMENU is handling it automatically. Quote Link to comment
kolla Posted November 25, 2014 Share Posted November 25, 2014 This is an older thread but I'm facing the exact same issue when trying to pre-clear a new Seagate 4T drive. Peter: How did you figure out "usbjmicron" as the correct option for -d for you? Is there a command I can run to get this info for my board? Quote Link to comment
jcarmi04 Posted July 2, 2015 Share Posted July 2, 2015 I know this is an old thread, but wanted to post for anyone else who might need this. The issue (from what I can tell) lies with the actual USB adapter used when preclearing a drive with a USB adapter, not necessarily the drive. I'm sure you could try swapping cables/etc, but I would recommend actually connecting the HDD internally or, if unable, trying a different USB adapter. The latter has worked for me. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.