The list you gave, sda-sdd are the only drives smartctl can find. Looking
again at the info below, sg5 isn't a disk. sd is the scsi disk driver,
while sg is the scsi generic driver.
Based on my limited knowledge of such devices, I would *GUESS* it's one of
two things:
1) There really is only 1 drive, or at least one drive that's not totally
dead. I've seen physically connected drives not show. In most of those
cases, the drive didn't even spin up.
2) You need some switch to see the second drive, for example -d sat
megaraid,0 (this is NOT the correct one, just an example).
If possible, I'd say pull the second drive out and connect it via directly
via sata cable to the computer and see what the smartctl --scan command
shows. The sdd has a serial number of WD-WCAU4C000000, so use the drive's
serial number to tell which one isn't recognized, assuming they are the
same type and size.
> The thing is there's no separate device for the second drive. It was
> so long before I could see the SMART for it via SAT.
>
> # smartctl --scan
> /dev/sda -d scsi # /dev/sda, SCSI device
> /dev/sdb -d scsi # /dev/sdb, SCSI device
> /dev/sdc -d scsi # /dev/sdc, SCSI device
> /dev/sdd -d sat # /dev/sdd [SAT], ATA device
>
> On Thu, Sep 25, 2014 at 10:32 AM, <[email protected]> wrote:
>> You have to get the correct name. Two ways that work for me:
>>
>> fdisk -l (that's a l as in llama)
>> or
>> smartctl --scan
>>
>> Post the output of either of those commands. Sometimes, especially when
>> dealing with drives behind a RAID controller, the second works better.
>>
>>> Hello
>>>
>>> How do I see SMART for a second drive in a multi-drive enclosure
>>> accessible over SAT layer?
>>>
>>> Here's what I could get for now:
>>>
>>> # smartctl -i /dev/sdd
>>>
>>> smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14-2-amd64] (local build)
>>> Copyright (C) 2002-13, Bruce Allen, Christian Franke,
>>> www.smartmontools.org
>>>
>>> === START OF INFORMATION SECTION ===
>>> Model Family: Western Digital Caviar Green
>>> Device Model: WDC WD10EADS-00L5B1
>>> Serial Number: WD-WCAU4C000000
>>> LU WWN Device Id: 5 0014ee 1ac7ee3f6
>>> Firmware Version: 01.01A01
>>> User Capacity: 1 000 204 886 016 bytes [1,00 TB]
>>> Sector Size: 512 bytes logical/physical
>>> Device is: In smartctl database [for details use: -P show]
>>> ATA Version is: ATA8-ACS (minor revision not indicated)
>>> SATA Version is: SATA 2.5, 3.0 Gb/s
>>> Local Time is: Thu Sep 25 09:57:12 2014 JST
>>> SMART support is: Available - device has SMART capability.
>>> SMART support is: Enabled
>>>
>>> # dmesg
>>>
>>> usb 2-1.6: new high-speed USB device number 8 using ehci-pci
>>> usb 2-1.6: New USB device found, idVendor=1058, idProduct=1105
>>> usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>> usb 2-1.6: Product: My Book
>>> usb 2-1.6: Manufacturer: Western Digital
>>> usb 2-1.6: SerialNumber: 0000000000000000000
>>> usb-storage 2-1.6:1.0: USB Mass Storage device detected
>>> scsi27 : usb-storage 2-1.6:1.0
>>> input: Western Digital My Book as
>>> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.1/0003:1058:1105.0006/input/input17
>>> hid-generic 0003:1058:1105.0006: input,hidraw3: USB HID v1.11 Device
>>> [Western Digital My Book] on usb-0000:00:1d.0-1.6/input1
>>> scsi 27:0:0:0: Direct-Access WD My Book 1017 PQ: 0
>>> ANSI: 4
>>> scsi 27:0:0:1: Enclosure WD My Book Device 1017 PQ: 0
>>> ANSI: 4
>>> sd 27:0:0:0: Attached scsi generic sg4 type 0
>>> ses 27:0:0:1: Attached Enclosure device
>>> ses 27:0:0:1: Attached scsi generic sg5 type 13
>>> sd 27:0:0:0: [sdd] Spinning up disk...
>>>
>>> # lsscsi -g | grep 27:0
>>>
>>> [27:0:0:0] disk WD My Book 1017 /dev/sdd
>>> /dev/sg4
>>> [27:0:0:1] enclosu WD My Book Device 1017 -
>>> /dev/sg5
>>>
>>> # smartctl -i /dev/sg4
>>>
>>> smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14-2-amd64] (local build)
>>> Copyright (C) 2002-13, Bruce Allen, Christian Franke,
>>> www.smartmontools.org
>>>
>>> === START OF INFORMATION SECTION ===
>>> Vendor: WD
>>> Product: My Book
>>> Revision: 1017
>>> User Capacity: 1 000 196 497 408 bytes [1,00 TB]
>>> Logical block size: 512 bytes
>>> Logical Unit id: error: designator length
>>> Serial number: WU2Q10000000
>>> Device type: disk
>>> Local Time is: Thu Sep 25 09:59:19 2014 JST
>>> SMART support is: Unavailable - device lacks SMART capability.
>>>
>>> # smartctl -i /dev/sg5
>>>
>>> smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14-2-amd64] (local build)
>>> Copyright (C) 2002-13, Bruce Allen, Christian Franke,
>>> www.smartmontools.org
>>>
>>> === START OF INFORMATION SECTION ===
>>> Vendor: WD
>>> Product: My Book Device
>>> Revision: 1017
>>> Logical Unit id: error: designator length
>>> Serial number: WU2Q10000000
>>> Device type: enclosure
>>> Local Time is: Thu Sep 25 09:59:58 2014 JST
>>> SMART support is: Unavailable - device lacks SMART capability.
>>>
>>> -Alexey
>>>
>>> ------------------------------------------------------------------------------
>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>>> Reports
>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Smartmontools-support mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>>>
>>
>>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Smartmontools-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.