[opensuse] What means this disk error? (Possible kernel bug)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I see thousands of these, for days: <0.6> 2016-10-03T15:30:15.566575+02:00 AmonLanc kernel - - - [1211541.009792] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566605+02:00 AmonLanc kernel - - - [1211541.009800] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.566608+02:00 AmonLanc kernel - - - [1211541.009803] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566610+02:00 AmonLanc kernel - - - [1211541.009806] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.566613+02:00 AmonLanc kernel - - - [1211541.009810] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.566615+02:00 AmonLanc kernel - - - [1211541.009813] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 ff 00 00 <0.6> 2016-10-03T15:30:15.566618+02:00 AmonLanc kernel - - - [1211541.009823] 00 00 00 00 40 50 <0.6> 2016-10-03T15:30:15.566620+02:00 AmonLanc kernel - - - [1211541.009829] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566623+02:00 AmonLanc kernel - - - [1211541.009832] Add. Sense: No additional sense information <0.6> 2016-10-03T15:30:15.566625+02:00 AmonLanc kernel - - - [1211541.009835] sd 2:0:0:0: [sdb] CDB: <0.4> 2016-10-03T15:30:15.566627+02:00 AmonLanc kernel - - - [1211541.009838] ATA command pass through(12)/Blank: a1 06 20 00 00 00 00 00 00 e5 00 00 <0.6> 2016-10-03T15:30:15.646589+02:00 AmonLanc kernel - - - [1211541.087910] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.646628+02:00 AmonLanc kernel - - - [1211541.087919] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.646632+02:00 AmonLanc kernel - - - [1211541.087922] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.646634+02:00 AmonLanc kernel - - - [1211541.087925] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.646636+02:00 AmonLanc kernel - - - [1211541.087929] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.646639+02:00 AmonLanc kernel - - - [1211541.087931] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 00 00 00 <0.6> 2016-10-03T15:30:15.646641+02:00 AmonLanc kernel - - - [1211541.087942] 00 4f 00 c2 40 50 <0.6> 2016-10-03T15:30:15.646643+02:00 AmonLanc kernel - - - [1211541.087948] sd 2:0:0:0: [sdb] and <0.6> 2016-10-03T15:30:15.870565+02:00 AmonLanc kernel - - - [1211541.313729] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870594+02:00 AmonLanc kernel - - - [1211541.313738] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.870597+02:00 AmonLanc kernel - - - [1211541.313741] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870599+02:00 AmonLanc kernel - - - [1211541.313744] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.870602+02:00 AmonLanc kernel - - - [1211541.313748] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.870604+02:00 AmonLanc kernel - - - [1211541.313750] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 ff 00 00 <0.6> 2016-10-03T15:30:15.870607+02:00 AmonLanc kernel - - - [1211541.313760] 00 00 00 00 40 50 <0.6> 2016-10-03T15:30:15.870609+02:00 AmonLanc kernel - - - [1211541.313766] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870611+02:00 AmonLanc kernel - - - [1211541.313769] Add. Sense: No additional sense information <0.6> 2016-10-03T15:30:15.870614+02:00 AmonLanc kernel - - - [1211541.313772] sd 3:0:0:0: [sdc] CDB: <0.4> 2016-10-03T15:30:15.870616+02:00 AmonLanc kernel - - - [1211541.313775] ATA command pass through(12)/Blank: a1 06 20 00 00 00 00 00 00 e5 00 00 <0.6> 2016-10-03T15:30:15.969692+02:00 AmonLanc kernel - - - [1211541.409337] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969719+02:00 AmonLanc kernel - - - [1211541.409345] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.969722+02:00 AmonLanc kernel - - - [1211541.409348] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969724+02:00 AmonLanc kernel - - - [1211541.409351] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.969726+02:00 AmonLanc kernel - - - [1211541.409355] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.969729+02:00 AmonLanc kernel - - - [1211541.409358] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 00 00 00 <0.6> 2016-10-03T15:30:15.969731+02:00 AmonLanc kernel - - - [1211541.409368] 00 4f 00 c2 40 50 <0.6> 2016-10-03T15:30:15.969734+02:00 AmonLanc kernel - - - [1211541.409373] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969736+02:00 AmonLanc kernel - - - [1211541.409376] Add. Sense: No additional sense information < What should I look at? The disks are inside an USB enclosure, connected to a 13.1-32b machine. To run smartctl on it I have to stop the machine and take the disk to another machine that has SATA, because: AmonLanc:~ # smartctl -a /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.62-52-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)] Please specify device type with the -d option. Use smartctl -h to get a usage summary AmonLanc:~ # Looking carefully, messages start on 2016-09-19T14:58:37.943377+02:00, just after I applied a kernel update and rebooted: 2016-09-19 14:58:36+02:00 - Booting the system now ================================================================================ Linux AmonLanc 3.12.62-52-default #1 SMP Wed Aug 10 18:37:26 UTC 2016 (069dc39) i686 i686 i386 GNU/Linux I will have to revert that upgrade :-( - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlfyYGQACgkQtTMYHG2NR9UYOgCeOWfumK0cGuCDrb7GDZXQdztz gHAAn2Ila9UbqyeyNgMQUXzJv9duTtAE =owxI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
What should I look at?
The disks are inside an USB enclosure, connected to a 13.1-32b machine.
To run smartctl on it I have to stop the machine and take the disk to another machine that has SATA, because:
AmonLanc:~ # smartctl -a /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.62-52-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)]
You ought to report that to the smartmontools people, but try adding "-d usbsunplus" when you run smartctl. -- Per Jessen, Zürich (15.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-03 15:48, Per Jessen wrote:
Carlos E. R. wrote:
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)]
You ought to report that to the smartmontools people,
It is 13.1... no point. :-(
but try adding "-d usbsunplus" when you run smartctl.
AmonLanc:~ # smartctl -d usbsunplus /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.59-47-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org ATA device successfully opened Use 'smartctl -a' (or '-x') to print SMART (and more) information AmonLanc:~ # Now it works... Wow, thanks. ... Oh, no... it doesn't. AmonLanc:~ # smartctl -d usbsunplus -a /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.59-47-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: �@S�@ Serial Number: *`�@\ �e]��e]��eR��@ Firmware Version: �@T �@S� Device is: Not in smartctl database [for details use: -P showall] ATA Version is: [No Information Found] Local Time is: Mon Oct 3 16:05:36 2016 CEST SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. AmonLanc:~ # AmonLanc:~ # smartctl -d usbsunplus -a /dev/sdc smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.59-47-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported scsi opcode A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. AmonLanc:~ # I have stopped the main problem by rebooting to previous kernel. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-10-03 15:48, Per Jessen wrote:
Carlos E. R. wrote:
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)]
You ought to report that to the smartmontools people,
It is 13.1... no point. :-(
They don't care which openSUSE you're running.
but try adding "-d usbsunplus" when you run smartctl.
AmonLanc:~ # smartctl -d usbsunplus /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.59-47-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
ATA device successfully opened
Use 'smartctl -a' (or '-x') to print SMART (and more) information
AmonLanc:~ #
Now it works... Wow, thanks. ... Oh, no... it doesn't.
Ah well, it was a reasonable guess based on the USB compatibility list: https://www.smartmontools.org/wiki/Supported_USB-Devices (b136 is not far from b159). -- Per Jessen, Zürich (15.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-03 16:24, Per Jessen wrote:
Carlos E. R. wrote:
On 2016-10-03 15:48, Per Jessen wrote:
Carlos E. R. wrote:
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)]
You ought to report that to the smartmontools people,
It is 13.1... no point. :-(
They don't care which openSUSE you're running.
Ok, but it may have been corrected in a newer release which I can't try, and if they add that chipset I will not see it because 13.1 gets no updates.
Now it works... Wow, thanks. ... Oh, no... it doesn't.
Ah well, it was a reasonable guess based on the USB compatibility list:
https://www.smartmontools.org/wiki/Supported_USB-Devices
(b136 is not far from b159).
I see. Well, we tried :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-10-03 16:24, Per Jessen wrote:
Carlos E. R. wrote:
On 2016-10-03 15:48, Per Jessen wrote:
Carlos E. R. wrote:
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)]
You ought to report that to the smartmontools people,
It is 13.1... no point. :-(
They don't care which openSUSE you're running.
Ok, but it may have been corrected in a newer release which I can't try,
s/can't/wont/. You could try it, just compile it yourself. It's not a big deal, Carlos.
and if they add that chipset I will not see it because 13.1 gets no updates.
Don't be so stubborn. Join the community and report it - future users might benefit from it even if you refuse to. -- Per Jessen, Zürich (11.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-03 21:13, Per Jessen wrote:
Carlos E. R. wrote:
On 2016-10-03 16:24, Per Jessen wrote:
Carlos E. R. wrote:
On 2016-10-03 15:48, Per Jessen wrote:
Carlos E. R. wrote:
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)]
You ought to report that to the smartmontools people,
It is 13.1... no point. :-(
They don't care which openSUSE you're running.
Ok, but it may have been corrected in a newer release which I can't try,
s/can't/wont/. You could try it, just compile it yourself. It's not a big deal, Carlos.
and if they add that chipset I will not see it because 13.1 gets no updates.
Don't be so stubborn. Join the community and report it - future users might benefit from it even if you refuse to.
Please think. I have version 6.2, and their current version is 6.5. The first thing they will surely tell me is to upgrade. Well, it is not available for 13.1, so I would have to build it myself. I have seen that there is version 6.4 available in repo "hardware", so I will try that one just now. [...] Same problem: AmonLanc:~ # smartctl -a /dev/sdb smartctl 6.4 2016-01-06 r4199 [i686-linux-3.12.59-47-default] (SUSE RPM) Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x0aec:0x3050 (0x100)] Please specify device type with the -d option. Use smartctl -h to get a usage summary AmonLanc:~ # So the next step is me downloading and building from source version 6.5. If I succeed, then I have to test it, and if it doesn't work, then I can report. If I don't succeed building, I can do nothing, because I can't test with the latest release. [...] ----------------------------------------------------------------------------- smartmontools-6.5 configuration: host operating system: i686-pc-linux-gnu C++ compiler: g++ C compiler: gcc preprocessor flags: C++ compiler flags: -g -O2 -Wall -W C compiler flags: -g -O2 linker flags: OS specific modules: os_linux.o cciss.o dev_areca.o binary install path: /usr/local/sbin man page install path: /usr/local/share/man doc file install path: /usr/local/share/doc/smartmontools examples install path: /usr/local/share/doc/smartmontools/examplescripts drive database file: /usr/local/share/smartmontools/drivedb.h database update script: /usr/local/sbin/update-smart-drivedb download tools: curl wget lynx svn local drive database: /usr/local/etc/smart_drivedb.h smartd config file: /usr/local/etc/smartd.conf smartd warning script: /usr/local/etc/smartd_warning.sh smartd plugin path: /usr/local/etc/smartd_warning.d smartd initd script: /usr/local/etc/init.d/smartd.initd smartd save files: [disabled] smartd attribute logs: [disabled] libcap-ng support: no SELinux support: no NVMe DEVICESCAN: no ----------------------------------------------------------------------------- Built. But it still fails to run: AmonLanc:/home/cer/Compilaciones/hardware/smartmontools-6.5 # ./smartctl -a /dev/sdb smartctl 6.5 2016-05-07 r4318 [i686-linux-3.12.59-47-default] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x0aec:0x3050 (0x100)] Please specify device type with the -d option. Use smartctl -h to get a usage summary AmonLanc:/home/cer/Compilaciones/hardware/smartmontools-6.5 # Now, and only now, I can think about reporting. Where to? Mail list, bugzilla? I see two mail lists. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-10-03 21:13, Per Jessen wrote:
Carlos E. R. wrote:
and if they add that chipset I will not see it because 13.1 gets no updates.
Don't be so stubborn. Join the community and report it - future users might benefit from it even if you refuse to.
Please think. I have version 6.2, and their current version is 6.5. The first thing they will surely tell me is to upgrade. Well, it is not available for 13.1, so I would have to build it myself.
Yep.
I have seen that there is version 6.4 available in repo "hardware", so I will try that one just now.
I am assuming the USB controller compatibility is up-to-date, so any newer version would likely still not work. Except possibly the very latest from sourceforge.
AmonLanc:~ # smartctl -a /dev/sdb smartctl 6.4 2016-01-06 r4199 [i686-linux-3.12.59-47-default] (SUSE RPM) Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x0aec:0x3050 (0x100)] Please specify device type with the -d option.
That's a different box? Your other one was 0x0c0b:0xb136 (Dura Micro, Inc. (Acomdata)), this one is Neodio Technologies Corp. Probably doesn't matter, neither one seems to be supported.
So the next step is me downloading and building from source version 6.5. If I succeed, then I have to test it, and if it doesn't work, then I can report. If I don't succeed building, I can do nothing, because I can't test with the latest release.
That's not a very optimistic attitude :-)
Built. But it still fails to run:
AmonLanc:/home/cer/Compilaciones/hardware/smartmontools-6.5 # ./smartctl -a /dev/sdb smartctl 6.5 2016-05-07 r4318 [i686-linux-3.12.59-47-default] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x0aec:0x3050 (0x100)] Please specify device type with the -d option.
I guess you haven't opened the box to see which kind of USB chip it has, but you could try with the usual suspects: https://www.smartmontools.org/wiki/USB -d sat -d usbsunplus -d usbprolific etc.
Now, and only now, I can think about reporting. Where to? Mail list, bugzilla? I see two mail lists.
I would start with the smartmontools-support mailing list and see if anyone has experience with those enclosures. -- Per Jessen, Zürich (8.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-04 08:34, Per Jessen wrote:
/dev/sdb: Unknown USB bridge [0x0aec:0x3050 (0x100)] Please specify device type with the -d option.
That's a different box? Your other one was 0x0c0b:0xb136 (Dura Micro, Inc. (Acomdata)), this one is Neodio Technologies Corp. Probably doesn't matter, neither one seems to be supported.
Oh. Two disks with the same brand of enclosure: /dev/sdb: Unknown USB bridge [0x0aec:0x3050 (0x100)] /dev/sdc: Unknown USB bridge [0x0c0b:0xb136 (0x108)] I never looked carefully, I thought it would be the same ID.
So the next step is me downloading and building from source version 6.5. If I succeed, then I have to test it, and if it doesn't work, then I can report. If I don't succeed building, I can do nothing, because I can't test with the latest release.
That's not a very optimistic attitude :-)
Yes, they taught me to consider the worst case scenario. O:-)
I guess you haven't opened the box to see which kind of USB chip it has, but you could try with the usual suspects:
Not recently, no. The lettering, as I remember, was ridiculously small. I have to stop the server to try again. I will need a microscope.
I would start with the smartmontools-support mailing list and see if anyone has experience with those enclosures.
I subscribed and posted at 00:07 (+1 UTC). No answers yet. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
So the next step is me downloading and building from source version 6.5. If I succeed, then I have to test it, and if it doesn't work, then I can report. If I don't succeed building, I can do nothing, because I can't test with the latest release.
That's not a very optimistic attitude :-)
Yes, they taught me to consider the worst case scenario. O:-)
I guess you haven't opened the box to see which kind of USB chip it has, but you could try with the usual suspects:
Not recently, no. The lettering, as I remember, was ridiculously small. I have to stop the server to try again. I will need a microscope.
Sometimes it is useful to identify the chip and then the USB identifiers can be easily added (if the chip is already supported). -- Per Jessen, Zürich (12.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-04 11:50, Per Jessen wrote:
Carlos E. R. wrote:
Not recently, no. The lettering, as I remember, was ridiculously small. I have to stop the server to try again. I will need a microscope.
Sometimes it is useful to identify the chip and then the USB identifiers can be easily added (if the chip is already supported).
Ok... I will try. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-10-04 12:12, Carlos E. R. wrote:
On 2016-10-04 11:50, Per Jessen wrote:
Carlos E. R. wrote:
Not recently, no. The lettering, as I remember, was ridiculously small. I have to stop the server to try again. I will need a microscope.
Sometimes it is useful to identify the chip and then the USB identifiers can be easily added (if the chip is already supported).
Ok... I will try.
I had to open it and remove the pcb, the chip is underneath. I can't read it, about 8*8 mm, even with magnifier lense. I had to photograph it and expand the photo. I can upload or email it. It reads: initio INIC-???OPL A41 8367??512 122? The question marks are because it has a yellow pencil or ink line drawn across it. Some type of quality check. I have tried with sdc. Does it ring any bell? Reassembling. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-10-04 13:19, Carlos E. R. wrote:
On 2016-10-04 12:12, Carlos E. R. wrote:
On 2016-10-04 11:50, Per Jessen wrote:
I had to open it and remove the pcb, the chip is underneath. I can't read it, about 8*8 mm, even with magnifier lense. I had to photograph it and expand the photo. I can upload or email it. It reads:
initio INIC-???OPL A41 8367??512 122?
The question marks are because it has a yellow pencil or ink line drawn across it. Some type of quality check.
I have tried with sdc.
sdb: initio INIC-1810PL A41 E36734512 ?220 Same chip. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-10-04 13:19, Carlos E. R. wrote:
On 2016-10-04 12:12, Carlos E. R. wrote:
On 2016-10-04 11:50, Per Jessen wrote:
I had to open it and remove the pcb, the chip is underneath. I can't read it, about 8*8 mm, even with magnifier lense. I had to photograph it and expand the photo. I can upload or email it. It reads:
initio INIC-???OPL A41 8367??512 122?
The question marks are because it has a yellow pencil or ink line drawn across it. Some type of quality check.
I have tried with sdc.
sdb:
initio
Initio is mentioned on the smartmontools page, it supports SATA pass-through: Try adding "-d sat,12" or "-d sat,16" to your command. -- Per Jessen, Zürich (14.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-04 14:05, Per Jessen wrote:
Carlos E. R. wrote:
initio
Initio is mentioned on the smartmontools page, it supports SATA pass-through:
Try adding "-d sat,12" or "-d sat,16" to your command.
I'll try later, now the enclosures are connected to my desktop machine via their eSATA plug. Yes, they are both eSATA and USB, which coincides with what you say above. I'm running a long smart test on them (via eSATA). -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-10-04 14:42, Carlos E. R. wrote:
On 2016-10-04 14:05, Per Jessen wrote:
Carlos E. R. wrote:
initio
Initio is mentioned on the smartmontools page, it supports SATA pass-through:
Try adding "-d sat,12" or "-d sat,16" to your command.
I'll try later, now the enclosures are connected to my desktop machine via their eSATA plug. Yes, they are both eSATA and USB, which coincides with what you say above. I'm running a long smart test on them (via eSATA).
Wow! It works with both. :-o Even with the original smartctl version. Now I need help with something else. I need to replace the tools with the version I built, because at least one test (-H) fails with one of the disks, sdb. My problem is here: ./configure ... ----------------------------------------------------------------------------- smartmontools-6.5 configuration: host operating system: i686-pc-linux-gnu C++ compiler: g++ C compiler: gcc preprocessor flags: C++ compiler flags: -g -O2 -Wall -W C compiler flags: -g -O2 linker flags: OS specific modules: os_linux.o cciss.o dev_areca.o binary install path: /usr/local/sbin man page install path: /usr/local/share/man doc file install path: /usr/local/share/doc/smartmontools examples install path: /usr/local/share/doc/smartmontools/examplescripts drive database file: /usr/local/share/smartmontools/drivedb.h database update script: /usr/local/sbin/update-smart-drivedb download tools: curl wget lynx svn local drive database: /usr/local/etc/smart_drivedb.h smartd config file: /usr/local/etc/smartd.conf smartd warning script: /usr/local/etc/smartd_warning.sh smartd plugin path: /usr/local/etc/smartd_warning.d smartd initd script: /usr/local/etc/init.d/smartd.initd smartd save files: [disabled] smartd attribute logs: [disabled] libcap-ng support: no SELinux support: no NVMe DEVICESCAN: no ----------------------------------------------------------------------------- I have to change the destination to /sbin and /etc. I try "./configure --prefix=/" and I get: binary install path: //sbin man page install path: //share/man <== doc file install path: //share/doc/smartmontools examples install path: //share/doc/smartmontools/examplescripts drive database file: //share/smartmontools/drivedb.h database update script: //sbin/update-smart-drivedb download tools: curl wget lynx svn local drive database: //etc/smart_drivedb.h smartd config file: //etc/smartd.conf smartd warning script: //etc/smartd_warning.sh smartd plugin path: //etc/smartd_warning.d which is not correct. I don't see what prefix to use to get the correct path for the binaries and the config, one gets wrong. ./configure --prefix=/usr ... binary install path: /usr/sbin man page install path: /usr/share/man doc file install path: /usr/share/doc/smartmontools examples install path: /usr/share/doc/smartmontools/examplescripts drive database file: /usr/share/smartmontools/drivedb.h database update script: /usr/sbin/update-smart-drivedb download tools: curl wget lynx svn local drive database: /usr/etc/smart_drivedb.h smartd config file: /usr/etc/smartd.conf smartd warning script: /usr/etc/smartd_warning.sh smartd plugin path: /usr/etc/smartd_warning.d smartd initd script: /usr/etc/init.d/smartd.initd How is it done? I always have built for /usr/local, but not this time, and I'm stuck. Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir=DIR program executables [EPREFIX/libexec] --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include] --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] --datadir=DIR read-only architecture-independent data [DATAROOTDIR] --infodir=DIR info documentation [DATAROOTDIR/info] --localedir=DIR locale-dependent data [DATAROOTDIR/locale] --mandir=DIR man documentation [DATAROOTDIR/man] --docdir=DIR documentation root [DATAROOTDIR/doc/smartmontools] --htmldir=DIR html documentation [DOCDIR] --dvidir=DIR dvi documentation [DOCDIR] --pdfdir=DIR pdf documentation [DOCDIR] --psdir=DIR ps documentation [DOCDIR] It seems I may have to tune almost each single path, and that doesn't seem correct to me. :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
04.10.2016 23:19, Carlos E. R. пишет: ...
./configure --prefix=/usr ... binary install path: /usr/sbin man page install path: /usr/share/man doc file install path: /usr/share/doc/smartmontools examples install path: /usr/share/doc/smartmontools/examplescripts drive database file: /usr/share/smartmontools/drivedb.h database update script: /usr/sbin/update-smart-drivedb download tools: curl wget lynx svn local drive database: /usr/etc/smart_drivedb.h smartd config file: /usr/etc/smartd.conf smartd warning script: /usr/etc/smartd_warning.sh smartd plugin path: /usr/etc/smartd_warning.d smartd initd script: /usr/etc/init.d/smartd.initd
How is it done? I always have built for /usr/local, but not this time, and I'm stuck.
Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir=DIR program executables [EPREFIX/libexec] --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include] --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] --datadir=DIR read-only architecture-independent data [DATAROOTDIR] --infodir=DIR info documentation [DATAROOTDIR/info] --localedir=DIR locale-dependent data [DATAROOTDIR/locale] --mandir=DIR man documentation [DATAROOTDIR/man] --docdir=DIR documentation root [DATAROOTDIR/doc/smartmontools] --htmldir=DIR html documentation [DOCDIR] --dvidir=DIR dvi documentation [DOCDIR] --pdfdir=DIR pdf documentation [DOCDIR] --psdir=DIR ps documentation [DOCDIR]
It seems I may have to tune almost each single path, and that doesn't seem correct to me. :-?
Actually you just need to additionally set --sysconfdir and may be --libexecdir, everything else looks to default to correct path under /usr. That is what build system does. "rpm --eval %configure" shows configure invocation used by default when building packages. Or you can look into smartmontools spec file to call configure exactly as package does.
Andrei Borzenkov wrote:
configure invocation used by default when building packages. Or you can look into smartmontools spec file to call configure exactly as package does.
Yes, that is what I usually do when I want to build a package for an outdated system. Get the latest source, then check the openSUSE source package for the config. -- Per Jessen, Zürich (8.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-05 05:30, Andrei Borzenkov wrote:
04.10.2016 23:19, Carlos E. R. пишет:
It seems I may have to tune almost each single path, and that doesn't seem correct to me. :-?
Actually you just need to additionally set --sysconfdir and may be --libexecdir, everything else looks to default to correct path under /usr. That is what build system does. "rpm --eval %configure" shows configure invocation used by default when building packages. Or you can look into smartmontools spec file to call configure exactly as package does.
Thanks both Andrei and Per :-) Ah, the rpm source package, yes. %configure\ --with-docdir=%{_defaultdocdir}/%{name}\ --with-selinux\ --with-systemdsystemunitdir=%{_unitdir}\ --enable-drivedb\ --enable-savestates\ --enable-attributelog Mmmm.... It is using some macros, so what it does is not directly clear. rpm --eval %configure smartmontools yields the syntax help page. Ah, must be rpmbuild. cer@AmonLanc:~/Compilaciones/hardware/smartmontools-6.5> rpmbuild --eval %configure smartmontools CFLAGS="${CFLAGS:--O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables}" ; export CFLAGS ; CXXFLAGS="${CXXFLAGS:--O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables}" ; export CXXFLAGS ; FFLAGS="${FFLAGS:--O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables}" ; export FFLAGS ; ./configure --host=i586-suse-linux-gnu --build=i586-suse-linux-gnu \ --program-prefix= \ --disable-dependency-tracking \ --prefix=/usr \ --exec-prefix=/usr \ --bindir=/usr/bin \ --sbindir=/usr/sbin \ --sysconfdir=/etc \ --datadir=/usr/share \ --includedir=/usr/include \ --libdir=/usr/lib \ --libexecdir=/usr/lib \ --localstatedir=/var \ --sharedstatedir=/usr/com \ --mandir=/usr/share/man \ --infodir=/usr/share/info \ --disable-dependency-tracking error: failed to stat /home/cer/Compilaciones/hardware/smartmontools-6.5/smartmontools: No such file or directory cer@AmonLanc:~/Compilaciones/hardware/smartmontools-6.5> AH!!! Very interesting. Although the package is not found. Well, I haven't installed the source package. Doing now... similar result, except the final error is: error: failed to stat /home/cer/Compilaciones/hardware/smartmontools-6.5/smartmontools: No such file or directory I'll ignore that. Ok, trying: ./configure --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/lib --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking which produces: ----------------------------------------------------------------------------- smartmontools-6.5 configuration: host operating system: i686-pc-linux-gnu C++ compiler: g++ C compiler: gcc preprocessor flags: C++ compiler flags: -g -O2 -Wall -W C compiler flags: -g -O2 linker flags: OS specific modules: os_linux.o cciss.o dev_areca.o binary install path: /usr/sbin man page install path: /usr/share/man doc file install path: /usr/share/doc/smartmontools examples install path: /usr/share/doc/smartmontools/examplescripts drive database file: /usr/share/smartmontools/drivedb.h database update script: /usr/sbin/update-smart-drivedb download tools: curl wget lynx svn local drive database: /etc/smart_drivedb.h smartd config file: /etc/smartd.conf smartd warning script: /etc/smartd_warning.sh smartd plugin path: /etc/smartd_warning.d smartd initd script: /etc/init.d/smartd.initd smartd save files: [disabled] smartd attribute logs: [disabled] libcap-ng support: no SELinux support: no NVMe DEVICESCAN: no ----------------------------------------------------------------------------- which builds for 686, preferable than 586. Even better, I'll use CFLAGS="-g -O2 --march=pentium4". CXXFLAGS doesn't accept "--march=pentium4", but that is not important. Ah, single dash! Ok. However, I see it will create "/etc/init.d/smartd.initd", and not the systemd service file. I think I may need: --with-systemdsystemunitdir=%{_unitdir} but that one is not in the rpmbuild output. :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wed, Oct 5, 2016 at 3:55 PM, Carlos E. R.
However, I see it will create "/etc/init.d/smartd.initd", and not the systemd service file. I think I may need:
--with-systemdsystemunitdir=%{_unitdir}
but that one is not in the rpmbuild output. :-?
https://build.opensuse.org/package/view_file/openSUSE:Leap:42.1/systemd-rpm-... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2016-10-04 14:42, Carlos E. R. wrote:
On 2016-10-04 14:05, Per Jessen wrote:
Carlos E. R. wrote:
initio
Initio is mentioned on the smartmontools page, it supports SATA pass-through:
Try adding "-d sat,12" or "-d sat,16" to your command.
I'll try later, now the enclosures are connected to my desktop machine via their eSATA plug. Yes, they are both eSATA and USB, which coincides with what you say above. I'm running a long smart test on them (via eSATA).
Wow! It works with both. :-o
That's great - that is certainly worth reporting to the smartmontools people: https://www.smartmontools.org/wiki/Supported_USB-Devices I can't see how to report it though. -- Per Jessen, Zürich (9.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Carlos E. R. wrote:
On 2016-10-04 14:42, Carlos E. R. wrote:
On 2016-10-04 14:05, Per Jessen wrote:
Carlos E. R. wrote:
initio
Initio is mentioned on the smartmontools page, it supports SATA pass-through:
Try adding "-d sat,12" or "-d sat,16" to your command.
I'll try later, now the enclosures are connected to my desktop machine via their eSATA plug. Yes, they are both eSATA and USB, which coincides with what you say above. I'm running a long smart test on them (via eSATA).
Wow! It works with both. :-o
That's great - that is certainly worth reporting to the smartmontools people:
https://www.smartmontools.org/wiki/Supported_USB-Devices
I can't see how to report it though.
Found it - either update the page yourself and/or send an email to the smartmontools-database mailinglist. -- Per Jessen, Zürich (8.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-05 08:28, Per Jessen wrote:
Found it - either update the page yourself and/or send an email to the smartmontools-database mailinglist.
I did that already, no answer at all. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-10-05 08:28, Per Jessen wrote:
Found it - either update the page yourself and/or send an email to the smartmontools-database mailinglist.
I did that already, no answer at all.
I wouldn't expect any on the database-list, you're only reporting success with hardware A and B, not much to say other than 'ok'. :-) -- Per Jessen, Zürich (10.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-05 12:08, Per Jessen wrote:
Carlos E. R. wrote:
On 2016-10-05 08:28, Per Jessen wrote:
Found it - either update the page yourself and/or send an email to the smartmontools-database mailinglist.
I did that already, no answer at all.
I wouldn't expect any on the database-list, you're only reporting success with hardware A and B, not much to say other than 'ok'. :-)
Ah, I did not write on the database mail list, but on the general mail list, which is what they recommend on their site. The wonderful help I got from you, they didn't give any. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Google hits would suggest the drive is failing, can not allocate replacement sectors, or some such.
http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-...
However there are other indications that it is spurious, and the message results from a kernel bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1351305 <---Fairly new bug report
On 10/03/2016 06:43 AM, Carlos E. R. wrote:
Hi,
I see thousands of these, for days:
<0.6> 2016-10-03T15:30:15.566575+02:00 AmonLanc kernel - - - [1211541.009792] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566605+02:00 AmonLanc kernel - - - [1211541.009800] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.566608+02:00 AmonLanc kernel - - - [1211541.009803] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566610+02:00 AmonLanc kernel - - - [1211541.009806] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.566613+02:00 AmonLanc kernel - - - [1211541.009810] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.566615+02:00 AmonLanc kernel - - - [1211541.009813] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 ff 00 00 <0.6> 2016-10-03T15:30:15.566618+02:00 AmonLanc kernel - - - [1211541.009823] 00 00 00 00 40 50 <0.6> 2016-10-03T15:30:15.566620+02:00 AmonLanc kernel - - [1211541.009829] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566623+02:00 AmonLanc kernel - - - [1211541.009832] Add. Sense: No additional sense information <0.6> 2016-10-03T15:30:15.566625+02:00 AmonLanc kernel - - - [1211541.009835] sd 2:0:0:0: [sdb] CDB: <0.4> 2016-10-03T15:30:15.566627+02:00 AmonLanc kernel - - - [1211541.009838] ATA command pass through(12)/Blank: a1 06 20 00 00 00 00 00 00 e5 00 00 <0.6> 2016-10-03T15:30:15.646589+02:00 AmonLanc kernel - - - [1211541.087910] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.646628+02:00 AmonLanc kernel - - - [1211541.087919] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.646632+02:00 AmonLanc kernel - - - [1211541.087922] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.646634+02:00 AmonLanc kernel - - - [1211541.087925] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.646636+02:00 AmonLanc kernel - - - [1211541.087929] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.646639+02:00 AmonLanc kernel - - - [1211541.087931] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 00 00 00 <0.6> 2016-10-03T15:30:15.646641+02:00 AmonLanc kernel - - - [1211541.087942] 00 4f 00 c2 40 50 <0.6> 2016-10-03T15:30:15.646643+02:00 AmonLanc kernel - - [1211541.087948] sd 2:0:0:0: [sdb]
and
<0.6> 2016-10-03T15:30:15.870565+02:00 AmonLanc kernel - - - [1211541.313729] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870594+02:00 AmonLanc kernel - - - [1211541.313738] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.870597+02:00 AmonLanc kernel - - - [1211541.313741] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870599+02:00 AmonLanc kernel - - - [1211541.313744] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.870602+02:00 AmonLanc kernel - - - [1211541.313748] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.870604+02:00 AmonLanc kernel - - - [1211541.313750] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 ff 00 00 <0.6> 2016-10-03T15:30:15.870607+02:00 AmonLanc kernel - - - [1211541.313760] 00 00 00 00 40 50 <0.6> 2016-10-03T15:30:15.870609+02:00 AmonLanc kernel - - [1211541.313766] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870611+02:00 AmonLanc kernel - - - [1211541.313769] Add. Sense: No additional sense information <0.6> 2016-10-03T15:30:15.870614+02:00 AmonLanc kernel - - - [1211541.313772] sd 3:0:0:0: [sdc] CDB: <0.4> 2016-10-03T15:30:15.870616+02:00 AmonLanc kernel - - - [1211541.313775] ATA command pass through(12)/Blank: a1 06 20 00 00 00 00 00 00 e5 00 00 <0.6> 2016-10-03T15:30:15.969692+02:00 AmonLanc kernel - - - [1211541.409337] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969719+02:00 AmonLanc kernel - - - [1211541.409345] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.969722+02:00 AmonLanc kernel - - - [1211541.409348] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969724+02:00 AmonLanc kernel - - - [1211541.409351] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.969726+02:00 AmonLanc kernel - - - [1211541.409355] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.969729+02:00 AmonLanc kernel - - - [1211541.409358] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 00 00 00 <0.6> 2016-10-03T15:30:15.969731+02:00 AmonLanc kernel - - - [1211541.409368] 00 4f 00 c2 40 50 <0.6> 2016-10-03T15:30:15.969734+02:00 AmonLanc kernel - - [1211541.409373] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969736+02:00 AmonLanc kernel - - - [1211541.409376] Add. Sense: No additional sense information <
What should I look at?
The disks are inside an USB enclosure, connected to a 13.1-32b machine.
To run smartctl on it I have to stop the machine and take the disk to another machine that has SATA, because:
AmonLanc:~ # smartctl -a /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.62-52-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)] Please specify device type with the -d option.
Use smartctl -h to get a usage summary
AmonLanc:~ #
Looking carefully, messages start on 2016-09-19T14:58:37.943377+02:00, just after I applied a kernel update and rebooted:
2016-09-19 14:58:36+02:00 - Booting the system now ================================================================================ Linux AmonLanc 3.12.62-52-default #1 SMP Wed Aug 10 18:37:26 UTC 2016 (069dc39) i686 i686 i386 GNU/Linux
I will have to revert that upgrade :-(
-- Cheers
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-- After all is said and done, more is said than done.
On 2016-10-03 19:12, John Andersen wrote:
Google hits would suggest the drive is failing, can not allocate replacement sectors, or some such.
http://serverfault.com/questions/407007/what-do-these-disk-errors-in-syslog-...
However there are other indications that it is spurious, and the message results from a kernel bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1351305 <---Fairly new bug report
I see. But this machine has kernel 3.12.62-52-default. Older with new patches, I guess. Reverting the upgrade made the problem to disappear, apparently. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Mon, Oct 3, 2016 at 9:43 AM, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I see thousands of these, for days:
<0.6> 2016-10-03T15:30:15.566575+02:00 AmonLanc kernel - - - [1211541.009792] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566605+02:00 AmonLanc kernel - - - [1211541.009800] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.566608+02:00 AmonLanc kernel - - - [1211541.009803] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566610+02:00 AmonLanc kernel - - - [1211541.009806] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.566613+02:00 AmonLanc kernel - - - [1211541.009810] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.566615+02:00 AmonLanc kernel - - - [1211541.009813] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 ff 00 00 <0.6> 2016-10-03T15:30:15.566618+02:00 AmonLanc kernel - - - [1211541.009823] 00 00 00 00 40 50 <0.6> 2016-10-03T15:30:15.566620+02:00 AmonLanc kernel - - - [1211541.009829] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.566623+02:00 AmonLanc kernel - - - [1211541.009832] Add. Sense: No additional sense information <0.6> 2016-10-03T15:30:15.566625+02:00 AmonLanc kernel - - - [1211541.009835] sd 2:0:0:0: [sdb] CDB: <0.4> 2016-10-03T15:30:15.566627+02:00 AmonLanc kernel - - - [1211541.009838] ATA command pass through(12)/Blank: a1 06 20 00 00 00 00 00 00 e5 00 00 <0.6> 2016-10-03T15:30:15.646589+02:00 AmonLanc kernel - - - [1211541.087910] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.646628+02:00 AmonLanc kernel - - - [1211541.087919] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.646632+02:00 AmonLanc kernel - - - [1211541.087922] sd 2:0:0:0: [sdb] <0.4> 2016-10-03T15:30:15.646634+02:00 AmonLanc kernel - - - [1211541.087925] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.646636+02:00 AmonLanc kernel - - - [1211541.087929] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.646639+02:00 AmonLanc kernel - - - [1211541.087931] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 00 00 00 <0.6> 2016-10-03T15:30:15.646641+02:00 AmonLanc kernel - - - [1211541.087942] 00 4f 00 c2 40 50 <0.6> 2016-10-03T15:30:15.646643+02:00 AmonLanc kernel - - - [1211541.087948] sd 2:0:0:0: [sdb]
and
<0.6> 2016-10-03T15:30:15.870565+02:00 AmonLanc kernel - - - [1211541.313729] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870594+02:00 AmonLanc kernel - - - [1211541.313738] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.870597+02:00 AmonLanc kernel - - - [1211541.313741] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870599+02:00 AmonLanc kernel - - - [1211541.313744] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.870602+02:00 AmonLanc kernel - - - [1211541.313748] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.870604+02:00 AmonLanc kernel - - - [1211541.313750] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 ff 00 00 <0.6> 2016-10-03T15:30:15.870607+02:00 AmonLanc kernel - - - [1211541.313760] 00 00 00 00 40 50 <0.6> 2016-10-03T15:30:15.870609+02:00 AmonLanc kernel - - - [1211541.313766] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.870611+02:00 AmonLanc kernel - - - [1211541.313769] Add. Sense: No additional sense information <0.6> 2016-10-03T15:30:15.870614+02:00 AmonLanc kernel - - - [1211541.313772] sd 3:0:0:0: [sdc] CDB: <0.4> 2016-10-03T15:30:15.870616+02:00 AmonLanc kernel - - - [1211541.313775] ATA command pass through(12)/Blank: a1 06 20 00 00 00 00 00 00 e5 00 00 <0.6> 2016-10-03T15:30:15.969692+02:00 AmonLanc kernel - - - [1211541.409337] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969719+02:00 AmonLanc kernel - - - [1211541.409345] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE <0.6> 2016-10-03T15:30:15.969722+02:00 AmonLanc kernel - - - [1211541.409348] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969724+02:00 AmonLanc kernel - - - [1211541.409351] Sense Key : Hardware Error [current] [descriptor] <0.4> 2016-10-03T15:30:15.969726+02:00 AmonLanc kernel - - - [1211541.409355] Descriptor sense data with sense descriptors (in hex): <0.6> 2016-10-03T15:30:15.969729+02:00 AmonLanc kernel - - - [1211541.409358] 72 04 00 00 00 00 00 0e 09 0c 00 00 00 00 00 00 <0.6> 2016-10-03T15:30:15.969731+02:00 AmonLanc kernel - - - [1211541.409368] 00 4f 00 c2 40 50 <0.6> 2016-10-03T15:30:15.969734+02:00 AmonLanc kernel - - - [1211541.409373] sd 3:0:0:0: [sdc] <0.4> 2016-10-03T15:30:15.969736+02:00 AmonLanc kernel - - - [1211541.409376] Add. Sense: No additional sense information <
What should I look at?
The disks are inside an USB enclosure, connected to a 13.1-32b machine.
To run smartctl on it I have to stop the machine and take the disk to another machine that has SATA, because:
AmonLanc:~ # smartctl -a /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.12.62-52-default] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x0c0b:0xb136 (0x108)] Please specify device type with the -d option.
Use smartctl -h to get a usage summary
AmonLanc:~ #
Looking carefully, messages start on 2016-09-19T14:58:37.943377+02:00, just after I applied a kernel update and rebooted:
2016-09-19 14:58:36+02:00 - Booting the system now ================================================================================ Linux AmonLanc 3.12.62-52-default #1 SMP Wed Aug 10 18:37:26 UTC 2016 (069dc39) i686 i686 i386 GNU/Linux
I will have to revert that upgrade :-(
When I see semi-unrecognizable SATA errors like that, I blame the cables, enclosures, etc. It is rarely the drive itself in my experience. As tot he kernel update, I be that turns out to be a coincidence. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/03/2016 10:26 AM, Greg Freemyer wrote:
As tot he kernel update, I be that turns out to be a coincidence.
I'd take that bet. I already posted about a Redhat bug related to a recent kernel update. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-03 19:26, Greg Freemyer wrote:
On Mon, Oct 3, 2016 at 9:43 AM, Carlos E. R. <> wrote:
When I see semi-unrecognizable SATA errors like that, I blame the cables, enclosures, etc.
It is rarely the drive itself in my experience.
As tot he kernel update, I be that turns out to be a coincidence.
Well, I reverted the upgrade and problem disappeared. :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 10/03/2016 12:10 PM, Carlos E. R. wrote:
On 2016-10-03 19:26, Greg Freemyer wrote:
On Mon, Oct 3, 2016 at 9:43 AM, Carlos E. R. <> wrote:
When I see semi-unrecognizable SATA errors like that, I blame the cables, enclosures, etc.
It is rarely the drive itself in my experience.
As tot he kernel update, I be that turns out to be a coincidence.
Well, I reverted the upgrade and problem disappeared. :-?
Known kernel bug, as I posted. What? Am I on your Plonk list or something Carlos? -- After all is said and done, more is said than done.
On 2016-10-03 21:13, John Andersen wrote:
On 10/03/2016 12:10 PM, Carlos E. R. wrote:
On 2016-10-03 19:26, Greg Freemyer wrote:
On Mon, Oct 3, 2016 at 9:43 AM, Carlos E. R. <> wrote:
When I see semi-unrecognizable SATA errors like that, I blame the cables, enclosures, etc.
It is rarely the drive itself in my experience.
As tot he kernel update, I be that turns out to be a coincidence.
Well, I reverted the upgrade and problem disappeared. :-?
Known kernel bug, as I posted. What? Am I on your Plonk list or something Carlos?
No, of course not. Why? But that bugzilla is about kernel kernel-4.6.4, and I have 3.12.62-52. That is my doubt. It is very strange that I get a new kernel bug when I'm using an old kernel. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 10/03/2016 02:13 PM, Carlos E. R. wrote:
That is my doubt. It is very strange that I get a new kernel bug when I'm using an old kernel.
Well, Opensuse has always stated the backport a ton of stuff into older kernels. Lost of distros don't even bother to do that. You've pretty well proven that it is kernel related, and maybe that gets fixed or maybe not. Bug report might be in order. -- After all is said and done, more is said than done.
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Greg Freemyer -
John Andersen -
Per Jessen