I have a Dell R515 server that I upgraded so that all 8 hard-drives are solid state. Specifically, I have 8 of these SSDs in a RAID 10:
Code:
Samsung V-NAND SSD 860 EVO 1TB SATA 6Gbps
Model MZ-76E1T0
Model Code: MZ-76E1T0E
After a few months, Proxmox kept emailing me this error regarding disk 5 :
Code:
Device: /dev/bus/1 [megaraid_disk_05] [SAT], Read SMART Self-Test Log Failed
While, the server was on, I looked at the drive lights and noticed that disk 5 had no light at all. When I would reboot the server, though, the light on disk 5’s drive tray would come back on. But it wouldn’t be long before Proxmox would email me that same error above and the light would go back off, while the sever was running.
2 days ago, Proxmox emailed the same error again regarding that same drive. Yesterday, I removed that hot-swap-able drive (actually I’m not even sure that this SSD it is designed to be hot-swap-able) from the server while the server was running. I unscrewed it from the drive tray, and hooked it up to my Kubuntu 20.04 laptop via a USB drive dock.
I used gparted to view the drive, and it appeared like the drive had nothing on it, not even a partition table. So I created a GPT partition table, using Gparted, and then created an EXT4 partition at max size. These details probably don’t matter. I was just wanting to remove anything that might still be on the disk. After this, I removed the Ext4 partition, so that the drive had no partitions on it. I really didn’t know what RAID 10 wanted me to do to get that SSD into an optimal state for RAID 10 to rebuild the drive, but I’m just telling you what I did.
After this, I screwed the drive back into its drive tray, and re-inserted it back into the server’s drive bay. When I plugged it back in, its drive light came on, and I could see that drive 4 was rebuilding this drive 5, because both of their green lights were blinking rapidly while all of the other drive lights were at their normal activity levels.
Later that day, I check the lights again, and all lights were normal green with equal activity. So, I assume the drive was rebuilt by the RAID 10 successfully.
So far, everything is normal, and I’ve received no further notifications from Proxmox regarding drive 5.
I’m not sure my procedure was proper, so I’m not advising you follow it, I’m simply sharing what I did to make the error notifications go away. One dangerous thing I did, was hot-swaping that SSD without knowing if it was designed for hot-swapping. It would have been safer for me to perform these steps I did while the server was completely off (I suspect).
UPDATE: I was wrong. This didn’t fix my issue. I just got the same error again. I don’t know how to fix this. When I replaced all the hard drives in this server with SSDs, the guy I bought this from warned me that their could be consequences like this. I can’t remember exactly what he said, but I do recall him saying that it would work, but might generate some type of errors.
- Печать
Страницы: [1] Вниз
Тема: smartctl и внешний HDD (Прочитано 2634 раз)
0 Пользователей и 1 Гость просматривают эту тему.

mouserok
Добрый …
почему не показывает SMART … под WIN смарт показывал
smartctl -a /dev/sdd
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Device: Toshiba External USB HDD Version: 0
Device type: disk
Local Time is: Wed Oct 27 10:41:59 2010 EEST
Device supports SMART and is Enabled
Temperature Warning Disabled or Not Supported
SMART Health Status: OK
Error Counter logging not supported
Device does not support Self Test logging

Mam(O)n
Некоторые контроллеры usb <=> ide/sata ущербны в плане smart. Либо неправильно стандарт трактуют либо вообще smart не выдают. Под WIN smartctl -a тоже самое показывает?

mouserok
Некоторые контроллеры usb <=> ide/sata ущербны в плане smart. Либо неправильно стандарт трактуют либо вообще smart не выдают. Под WIN smartctl -a тоже самое показывает?
под WIN ползуюсь HardDiskSentinel

Mam(O)n
Я не про то, чем пользуешься спрашиваю, а конкретно, что говорит smartctl -a будучи запущенным из под венды.

mouserok
под виндой не пробовал smartctl

Sly_tom_cat
У меня веселее есть USBдиск — DiskUtility его SMART видит а smartctl — нет 
А другой USB-бокс вообще никак SMART не поддерживает.
Т.к. еще раз повторю слова 2-го сообщения темы — практически все USB контроллеры HDD ущербны в плане поддержки SMART.

mouserok
вообщем в linux не получается мониторить SMART и тем более внешние HDD

Mam(O)n
В общем в linux можно мониторить s.m.a.r.t. и тем более внешние HDD…. если железо вменяемое то это сделать еще проще…
Пользователь решил продолжить мысль 27 Октября 2010, 15:42:50:
Пробуй другие программы. Гугль подсказывает, что есть smartsuite и ide-smart.
« Последнее редактирование: 27 Октября 2010, 15:42:50 от Mam(O)n »

mouserok
mouse@Xubuntu-Cheese:~$ sudo apt-get install smartsuite
[sudo] password for mouse:
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Пакет smartsuite недоступен, но упомянут в списке зависимостей другого пакета.
Это может означать, что пакет отсутствует, устарел, или доступен из источников, не упомянутых в sources.list
E: Для пакета smartsuite не найдены кандидаты на установку

alecsartania
Добрый …
почему не показывает SMART … под WIN смарт показывал
smartctl -a /dev/sdd
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/Device: Toshiba External USB HDD Version: 0
Device type: disk
Local Time is: Wed Oct 27 10:41:59 2010 EEST
Device supports SMART and is Enabled
Temperature Warning Disabled or Not Supported
SMART Health Status: OKError Counter logging not supported
Device does not support Self Test logging
ну в общем он тебе же сказал что смарт ок. просто атрибуты н смог прочитать.
Пользователь решил продолжить мысль 27 Октября 2010, 22:21:42:
Вот цитата из инета про badblocks 
так уж вышло, что usb-винчестер, при скидывании с него информации случайно упал… невольно начали складваться подозрения на бэд блоки. нашел возможность проверить из Linux.
image
Программа badblocks позволяет проверить жесткий диск на наличие сбойных блоков. Проверка выполняется очень просто:
$ sudo badblocks -v <имя_устройства>
Например:
$ sudo badblocks -v /dev/sdb1
Параметр -v включает подробный режим работы — о каждом действии программа badblocks будет выводить отчет. Желательно выполнять программу в однопользовательском режиме, чтобы ее работе ничто не мешало.
« Последнее редактирование: 27 Октября 2010, 22:21:42 от alecsartania »
Дома Linux Mint 20.1 / 20.02

mouserok
а как же SMART параметры 

alecsartania
а как же SMART параметры
… от bad block винты не умирали
он тебе сказал что смарт ОК
Дома Linux Mint 20.1 / 20.02

mouserok
а как же SMART параметры
… от bad block винты не умирали
он тебе сказал что смарт ОК
этого не достаточно …. меня в принципе вполне устраивает smartmontools — так он почту не может прислать если изменились параметры (пробовал по всякому)
Пользователь решил продолжить мысль 28 Октября 2010, 17:22:25:
а не получится поставить виртуалку а на ней win … smart виртуалке передастся 
« Последнее редактирование: 28 Октября 2010, 17:22:25 от mouserok »
- Печать
Страницы: [1] Вверх
1
3
Завёлся у меня внешний диск Seagate Expansion Desk, подключён через usb 3.0. Используется параметр -d scsi иначе не опознаётся тип устройства.
# smartctl -a -d scsi /dev/sdc
=== START OF INFORMATION SECTION ===
Vendor: Seagate
Product: Expansion Desk
Revision: 9401
Compliance: SPC-4
User Capacity: 5,000,981,077,504 bytes [5.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
Logical Unit id: 0x5000000000000001
Serial number: MA4Z1FGT
Device type: disk
Local Time is: Sat Jan 7 19:22:42 2017 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
Temperature Warning: Disabled or Not Supported
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Error Counter logging not supported
Device does not support Self Test logging
Попытка включить с параметром —smart=on оказалась не успешна
# smartctl --smart=on -d scsi /dev/sdd
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
Informational Exceptions (SMART) disabled
Temperature warning disabled
Диагностика после этого не заработала. hddtemp для температуры выдал
# hddtemp /dev/sdc
/dev/sdd: Seagate Expansion Desk: drive supported, but it doesn't have a temperature sensor.
Вот и интересно, можно ли как-то его заставить показывать данные, в том числе и температуру было бы интересно. Вроде поддержка как бы есть.
Similar issue, smartctl fails to determine device type for HP Proliant G8 scsi hard disks on CentOS 7.
Somewhat misleading hint /dev/sda: requires option '-d cciss,N'
DOH DUH #1:
root$ smartctl -i /dev/sda /dev/sda: requires option '-d cciss,N' Please specify device type with the -d option.
DOH DUH #2:
root$ smartctl -i /dev/sda -d cciss,N # oops /dev/sda: Option -d cciss,N requires N to be a non-negative integer
=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntjmicron[,NSID], intelliprop,N[+TYPE], marvell, areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, cciss,N, auto, test <=======
‘-d csiss,N’ where N is a number.
Not sure why just csiss is suggested, maybe it is just the last item in the list when it is trying to automatically figure out type of device.
List device files under /dev to see disk devices.
The N is the last number in the name of the device.
e.g. for /dev/sda5 N is 5
$ ls -alstr /dev/sd*
0 brw-rw----. 1 root disk 8, 48 Jan 22 2020 /dev/sdd
0 brw-rw----. 1 root disk 8, 32 Jan 22 2020 /dev/sdc
0 brw-rw----. 1 root disk 8, 16 Jan 22 2020 /dev/sdb
0 brw-rw----. 1 root disk 8, 17 Jan 22 2020 /dev/sdb1
0 brw-rw----. 1 root disk 8, 33 Jan 22 2020 /dev/sdc1
0 brw-rw----. 1 root disk 8, 49 Jan 22 2020 /dev/sdd1
0 brw-rw----. 1 root disk 8, 0 Feb 10 10:56 /dev/sda
0 brw-rw----. 1 root disk 8, 4 Feb 10 10:56 /dev/sda4
0 brw-rw----. 1 root disk 8, 5 Feb 10 10:56 /dev/sda5
0 brw-rw----. 1 root disk 8, 3 Feb 10 10:56 /dev/sda3
0 brw-rw----. 1 root disk 8, 2 Feb 10 10:56 /dev/sda2
0 brw-rw----. 1 root disk 8, 6 Feb 10 10:56 /dev/sda6
0 brw-rw----. 1 root disk 8, 1 Feb 10 10:56 /dev/sda1
e.g. for /dev/sda0 N is 0
$ smartctl -i /dev/sda -d cciss,0
smartctl 6.2 2017-02-27 r4394 [x86_64-linux-3.10.0-693.21.1.el7.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda [cciss_disk_00] [SCSI]: Device open changed type from 'sat,auto+cciss' to 'cciss'
=== START OF INFORMATION SECTION ===
Vendor: HP
Product: EH0146FBQDC
Revision: HPD3
User Capacity: 146,815,737,856 bytes [146 GB]
Logical block size: 512 bytes
Rotation Rate: 15000 rpm
Form Factor: 2.5 inches
Logical Unit id: 0x5000c5005ab90277
Serial number: 6XM1WH6J0000B320CK84
Device type: disk
Transport protocol: SAS
Local Time is: Wed Feb 10 10:57:34 2021 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
e.g. for /dev/sda5 N is 5
The same info shows as for /dev/sda0 except Logical Unit id and Serial Number are different.
smartctl -i /dev/sda -d cciss,5
smartctl 6.2 2017-02-27 r4394 [x86_64-linux-3.10.0-693.21.1.el7.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sda [cciss_disk_05] [SCSI]: Device open changed type from 'sat,auto+cciss' to 'cciss'
=== START OF INFORMATION SECTION ===
Vendor: HP
Product: EH0146FBQDC
Revision: HPD3
User Capacity: 146,815,737,856 bytes [146 GB]
Logical block size: 512 bytes
Rotation Rate: 15000 rpm
Form Factor: 2.5 inches
Logical Unit id: 0x5000c5005abf9f07
Serial number: 6XM1WKTN0000B320ED0R
Device type: disk
Transport protocol: SAS
Local Time is: Fri Feb 19 18:46:59 2021 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Specifying ‘-d scsi’ shows quite believable info also, but …
root$ sudo smartctl -i /dev/sda -d scsi smartctl 7.0 2018-12-30 r4883 [x86_64-linux-3.10.0-1062.9.1.el7.x86_64] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HP Product: LOGICAL VOLUME Revision: 6.34 Compliance: SPC-3 User Capacity: 146,778,685,440 bytes [146 GB] Logical block size: 512 bytes Logical Unit id: 0x600508b1001c3aa4f41858962741ed49 Serial number: 00143802281D760 Device type: disk Local Time is: Fri Jan 24 16:11:48 2020 GMT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported root$ cat /etc/redhat-release CentOS Linux release 7.7.1908 (Core)
-
Summary
-
Files
-
Reviews
-
Support
-
Code
-
Mailing Lists
-
Old MLs
Menu
▾
▴
|
From: David Greaves <da…@dg…> — 2008-10-09 22:53:59 |
Hi
I just bought a usb/sata adapter like this:
http://www.thinkgeek.com/computing/drives/a7ea/?cpg=ab
lsusb -v is below
Works OK as a hot-plug SATA disk so I can check what's on that old disk in the
corner; but smartctl doesn't work so I can't see if it has any errors, run
selftests etc.
Kernel is 2.6.27-rc5 (I've also tried older kernels)
I plugged a previously zeroed drive in and...
root@ash:~ # smartctl -a /dev/sde
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Device: ST332062 0AS Version:
Device type: disk
Local Time is: Thu Oct 9 21:38:16 2008 BST
Device supports SMART and is Enabled
Temperature Warning Disabled or Not Supported
SMART Health Status: OK
Error Counter logging not supported
Device does not support Self Test logging
I've tried -dscsi and -dsat but they don't work.
More info below.
David
dmesg tail:
Initializing USB Mass Storage driver...
scsi8 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 8:0:0:0: Direct-Access ST332062 0AS PQ: 0 ANSI: 2
sd 8:0:0:0: [sde] 625134827 512-byte hardware sectors (320069 MB)
sd 8:0:0:0: [sde] Write Protect is off
sd 8:0:0:0: [sde] Mode Sense: 38 00 00 00
sd 8:0:0:0: [sde] Assuming drive cache: write through
sd 8:0:0:0: [sde] 625134827 512-byte hardware sectors (320069 MB)
sd 8:0:0:0: [sde] Write Protect is off
sd 8:0:0:0: [sde] Mode Sense: 38 00 00 00
sd 8:0:0:0: [sde] Assuming drive cache: write through
sde: unknown partition table
sd 8:0:0:0: [sde] Attached SCSI disk
sd 8:0:0:0: Attached scsi generic sg6 type 0
root@ash:~ # lsusb -v -s3:3
Bus 003 Device 003: ID 04fc:0c25 Sunplus Technology Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x04fc Sunplus Technology Co., Ltd
idProduct 0x0c25
bcdDevice 1.03
iManufacturer 2 Sunplus Technology Inc.
iProduct 3 USB to Serial-ATA bridge
iSerial 1 SAMSUNG HD472712CQ696126
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 Bulk Only Configuration
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 5 Bulk Only Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
|
|
From: David Greaves <da…@dg…> — 2008-10-10 08:10:02 |
David Greaves wrote: > Hi > > I just bought a usb/sata adapter like this: > http://www.thinkgeek.com/computing/drives/a7ea/?cpg=ab > lsusb -v is below > > Works OK as a hot-plug SATA disk so I can check what's on that old disk in the > corner; but smartctl doesn't work so I can't see if it has any errors, run > selftests etc. So, for the record since I had no luck on google, I had an off-list reply that pointed here: Smartmontools for FireWire, USB, and SATA disks/systems http://smartmontools.sourceforge.net/faq.html#testinghelp It's an odd URL target - it's actually about the fact that the usb/sata bridges built into the docks don't fully support the scsi command set in their hardware; so my SMART doesn't work and has no chance of being fixed by software. Future chipsets (and some current cypress ones) may have various developments in hardware to fix this. HTH someone else. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." |
|
From: Tejun Heo <tj…@ke…> — 2008-10-14 02:47:32 |
David Greaves wrote: > I just bought a usb/sata adapter like this: > http://www.thinkgeek.com/computing/drives/a7ea/?cpg=ab > lsusb -v is below > > Works OK as a hot-plug SATA disk so I can check what's on that old disk in the > corner; but smartctl doesn't work so I can't see if it has any errors, run > selftests etc. > > Kernel is 2.6.27-rc5 (I've also tried older kernels) > > I plugged a previously zeroed drive in and... > > root@ash:~ # smartctl -a /dev/sde > smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > Device: ST332062 0AS Version: > Device type: disk > Local Time is: Thu Oct 9 21:38:16 2008 BST > Device supports SMART and is Enabled > Temperature Warning Disabled or Not Supported > SMART Health Status: OK > > Error Counter logging not supported > Device does not support Self Test logging The USB bridge should support SAT (SCSI-ATA translation) and many don't. Nothing much can be done about it. The hardware just don't know how to do it. -- tejun |
|
From: Mark Lord <li…@rt…> — 2008-10-23 16:35:08 |
matthieu castet wrote:
> Hi,
>
> Tejun Heo wrote:
>> David Greaves wrote:
>>> Error Counter logging not supported
>>> Device does not support Self Test logging
>>
>> The USB bridge should support SAT (SCSI-ATA translation) and many
>> don't. Nothing much can be done about it. The hardware just don't know
>> how to do it.
>>
> That true that the hardware should support SAT, but even if it support
> it, linux need some patches to support SAT over USB. See
> http://thread.gmane.org/gmane.linux.scsi/43688 and the patch mentioned
> in the thread.
...
Ahh.. Great! This mostly fixes smartctl operation on at least two
of my USB drive enclosures here:
1. a recent rev. 2.5" NexStar-3 SATA enclosure.
2. a 250GB 2.5" WD "Passport" external USB drive/enclosure.
With the patch, this command line works for me:
smartctl -a -dsat -T permissive /dev/sdb
And hdparm just works regardless, with or without the patch.
>
> Unfortunately I am a bit busy to try to resubmit it. But I won't care if
> somebody improve it/resubmit it ;)
>
> Matthieu
>
> PS : there also http://thread.gmane.org/gmane.linux.usb.general/7145
> that is pending.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to major...@vg...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
|
|
From: matthieu castet <caste…@fr…> — 2008-10-23 18:58:37 |
Mark Lord wrote: > matthieu castet wrote: >> Hi, >> >> Tejun Heo wrote: >>> David Greaves wrote: >>>> Error Counter logging not supported >>>> Device does not support Self Test logging >>> >>> The USB bridge should support SAT (SCSI-ATA translation) and many >>> don't. Nothing much can be done about it. The hardware just don't know >>> how to do it. >>> >> That true that the hardware should support SAT, but even if it support >> it, linux need some patches to support SAT over USB. See >> http://thread.gmane.org/gmane.linux.scsi/43688 and the patch mentioned >> in the thread. > ... > > Ahh.. Great! This mostly fixes smartctl operation on at least two > of my USB drive enclosures here: > > 1. a recent rev. 2.5" NexStar-3 SATA enclosure. > 2. a 250GB 2.5" WD "Passport" external USB drive/enclosure. > > With the patch, this command line works for me: > > smartctl -a -dsat -T permissive /dev/sdb > And hdparm just works regardless, with or without the patch. > > It should work without permissive, permissive was need without the patch. You said hdparm works without the patch. I wonder how it work. IRRC it asks check condition stuff for every command. I am interested to see the hdparm --verbose output without the patch. BTW somebody is trying to push a patch similar to this one to usb-storage driver : https://lists.one-eyed-alien.net/pipermail/usb-storage/2008-October/004096.html Matthieu |
|
From: Mark Lord <li…@rt…> — 2008-10-23 16:18:25 |
Tejun Heo wrote: > David Greaves wrote: >> I just bought a usb/sata adapter like this: >> http://www.thinkgeek.com/computing/drives/a7ea/?cpg=ab >> lsusb -v is below >> >> Works OK as a hot-plug SATA disk so I can check what's on that old disk in the >> corner; but smartctl doesn't work so I can't see if it has any errors, run >> selftests etc. >> >> Kernel is 2.6.27-rc5 (I've also tried older kernels) >> >> I plugged a previously zeroed drive in and... >> >> root@ash:~ # smartctl -a /dev/sde >> smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen >> Home page is http://smartmontools.sourceforge.net/ >> >> Device: ST332062 0AS Version: >> Device type: disk >> Local Time is: Thu Oct 9 21:38:16 2008 BST >> Device supports SMART and is Enabled >> Temperature Warning Disabled or Not Supported >> SMART Health Status: OK >> >> Error Counter logging not supported >> Device does not support Self Test logging > > The USB bridge should support SAT (SCSI-ATA translation) and many > don't. Nothing much can be done about it. The hardware just don't know > how to do it. .. That may be true, or not. Try "hdparm -I /dev/sde" on it. If that *works*, then the USB interface *does* support SAT! Many, many new USB enclosures now have the modern InitIO bridge chips with SAT. Cheers |
|
From: Mark Lord <li…@rt…> — 2008-10-23 20:21:29 |
matthieu castet wrote:
> Mark Lord wrote:
>> matthieu castet wrote:
>>> Hi,
>>>
>>> Tejun Heo wrote:
>>>> David Greaves wrote:
>>>>> Error Counter logging not supported
>>>>> Device does not support Self Test logging
>>>>
>>>> The USB bridge should support SAT (SCSI-ATA translation) and many
>>>> don't. Nothing much can be done about it. The hardware just don't
>>>> know
>>>> how to do it.
>>>>
>>> That true that the hardware should support SAT, but even if it
>>> support it, linux need some patches to support SAT over USB. See
>>> http://thread.gmane.org/gmane.linux.scsi/43688 and the patch
>>> mentioned in the thread.
>> ...
>>
>> Ahh.. Great! This mostly fixes smartctl operation on at least two
>> of my USB drive enclosures here:
>>
>> 1. a recent rev. 2.5" NexStar-3 SATA enclosure.
>> 2. a 250GB 2.5" WD "Passport" external USB drive/enclosure.
>>
>> With the patch, this command line works for me:
>>
>> smartctl -a -dsat -T permissive /dev/sdb
>> And hdparm just works regardless, with or without the patch.
>>
>>
> It should work without permissive, permissive was need without the patch.
>
> You said hdparm works without the patch. I wonder how it work. IRRC it
> asks check condition stuff for every command. I am interested to see the
> hdparm --verbose output without the patch.
..
Mmm... actually, the "-dsat" flag seems to make smartctl mostly work
with and without the patch. This is on 2.6.25.6 on my notebook here.
Some month I'll update the kernel and fix VMware and wireless again
for a newer kernel, but for now that's what it runs.
Here's hdparm --verbose, sans patch:
hdparm --verbose -I /dev/sdb
/dev/sdb:
outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 ec 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[] = {72 00 00 00 00 00 00 0e}
SG_IO: desc[] = {09 0c .. }
ATA_16 tf->status=0x00 tf->error=0x00
ATA device, with non-removable media
Model Number: Hitachi HTS541612J9SA00
Serial Number: SB2D11E4GESWAB
Firmware Revision: SBDOC74P
...
And here is smartctl -a -dsat, without the -T permissive flag:
smartctl -a -dsat /dev/sdb
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Travelstar 5K160 series
Device Model: Hitachi HTS541612J9SA00
Serial Number: SB2D11E4GESWAB
Firmware Version: SBDOC74P
User Capacity: 120,034,123,776 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1
Local Time is: Thu Oct 23 16:21:45 2008 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Error SMART Status command failed
Please get assistance from http://smartmontools.sourceforge.net/
Values from ATA Return Descriptor are:
00 09 0c 00 00 50 00 00 00 c2 4f 00 00 00 00
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Cheers
|
|
From: Mark Lord <li…@rt…> — 2008-10-23 20:36:09 |
Mark Lord wrote:
> matthieu castet wrote:
>> Mark Lord wrote:
>>> matthieu castet wrote:
>>>> Hi,
>>>>
>>>> Tejun Heo wrote:
>>>>> David Greaves wrote:
>>>>>> Error Counter logging not supported
>>>>>> Device does not support Self Test logging
>>>>>
>>>>> The USB bridge should support SAT (SCSI-ATA translation) and many
>>>>> don't. Nothing much can be done about it. The hardware just don't
>>>>> know
>>>>> how to do it.
>>>>>
>>>> That true that the hardware should support SAT, but even if it
>>>> support it, linux need some patches to support SAT over USB. See
>>>> http://thread.gmane.org/gmane.linux.scsi/43688 and the patch
>>>> mentioned in the thread.
>>> ...
>>>
>>> Ahh.. Great! This mostly fixes smartctl operation on at least two
>>> of my USB drive enclosures here:
>>>
>>> 1. a recent rev. 2.5" NexStar-3 SATA enclosure.
>>> 2. a 250GB 2.5" WD "Passport" external USB drive/enclosure.
>>>
>>> With the patch, this command line works for me:
>>>
>>> smartctl -a -dsat -T permissive /dev/sdb
>>> And hdparm just works regardless, with or without the patch.
>>>
>>>
>> It should work without permissive, permissive was need without the patch.
>>
>> You said hdparm works without the patch. I wonder how it work. IRRC it
>> asks check condition stuff for every command. I am interested to see
>> the hdparm --verbose output without the patch.
> ..
>
> Mmm... actually, the "-dsat" flag seems to make smartctl mostly work
> with and without the patch. This is on 2.6.25.6 on my notebook here.
> Some month I'll update the kernel and fix VMware and wireless again
> for a newer kernel, but for now that's what it runs.
>
> Here's hdparm --verbose, sans patch:
>
> hdparm --verbose -I /dev/sdb
>
> /dev/sdb:
> outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 ec 00
> SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
> SG_IO: sb[] = {72 00 00 00 00 00 00 0e}
> SG_IO: desc[] = {09 0c .. }
> ATA_16 tf->status=0x00 tf->error=0x00
>
> ATA device, with non-removable media
> Model Number: Hitachi HTS541612J9SA00
> Serial Number: SB2D11E4GESWAB
> Firmware Revision: SBDOC74P
..
Here it is again, with the entire returned sense data shown:
hdparm --verbose -I /dev/sdb
/dev/sdb:
outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 ec 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[] = {72 00 00 00 00 00 00 0e}
SG_IO: desc[] = {09 0c 00 00 50 01 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
ATA_16 tf->status=0x00 tf->error=0x00
ATA device, with non-removable media
Model Number: Hitachi HTS541612J9SA00
Serial Number: SB2D11E4GESWAB
Firmware Revision: SBDOC74P
...
I guess it "works" by accident, since the 00 device status
doesn't have the ATA error bit set. But I suppose this also
means that a failed ATA command would not be noticed either..
At least not without the patch.
Cheers
|
|
From: matthieu castet <caste…@fr…> — 2008-10-24 18:54:54 |
Mark Lord wrote: > Mark Lord wrote: > I guess it "works" by accident, since the 00 device status > doesn't have the ATA error bit set. But I suppose this also > means that a failed ATA command would not be noticed either.. > At least not without the patch. Yes that seem to case. I wonder with the patch doesn't make smartctl work without permisive. May be your usb id wasn't in the patch. Matthieu |
|
From: Mark Lord <li…@rt…> — 2008-10-25 12:46:19 |
matthieu castet wrote: .. > I wonder with the patch doesn't make smartctl work without permisive. > May be your usb id wasn't in the patch. .. Heh.. I didn't even look at the patch itself. But if it is relying upon a whitelist to work, then it's broken by design. Most new USB drives will be supporting SAT, and requiring a kernel patch/update (or some other whitelist in userspace) is a silly way to support them. Cheers |


