From: Kai M. <ka...@fi...> - 2008-07-22 15:00:41
|
So I set up smartd (lucky me, it looks like) yesterday, and am getting some Unknown_Attribute lines. Your FAQ suggests I email you about it. I'll be taking care of the failed self-check disk. I'm just curious about the unknown attribute changing from 75 to 76 and back. What would this value be? These disks are attached to a 3ware 9650SE-12ML (12 port) card. I have the latest drivers for the card as of about 3 weeks ago. Jul 22 08:32:01 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_00], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 112 to 113 Jul 22 08:32:01 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_00], SMART Usage Attribute: 190 Unknown_Attribute changed from 76 to 75 Jul 22 08:32:01 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_00], SMART Usage Attribute: 194 Temperature_Celsius changed from 24 to 25 Jul 22 08:32:01 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_00], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 55 to 56 Jul 22 08:32:01 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_01], FAILED SMART self-check. BACK UP DATA NOW! Jul 22 08:32:02 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_01], SMART Usage Attribute: 190 Unknown_Attribute changed from 76 to 75 Jul 22 08:32:02 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_01], SMART Usage Attribute: 194 Temperature_Celsius changed from 24 to 25 Jul 22 08:32:02 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_04], SMART Usage Attribute: 190 Unknown_Attribute changed from 76 to 75 Jul 22 08:32:02 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_04], SMART Usage Attribute: 194 Temperature_Celsius changed from 24 to 25 Jul 22 08:32:03 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_09], SMART Usage Attribute: 190 Unknown_Attribute changed from 76 to 75 Jul 22 08:32:03 r1soft-monster smartd[22662]: Device: /dev/twa0 [3ware_disk_09], SMART Usage Attribute: 194 Temperature_Celsius changed from 24 to 25 I am also curious if anybody knows how to clearly define which 3ware disks are which /dev/sd* device? I have 12 identical drives set up in 6 identical raid-1 arrays for this particular box, and I'd like to verify which disks belong to which linux device. I am mostly interested in knowing for sure which one is /dev/sda, since that drive has my OS on it (for now). -Kai Meyer |
From: Bruce A. <ba...@gr...> - 2008-07-22 16:06:59
|
Hi Kai, > So I set up smartd (lucky me, it looks like) yesterday, and am getting > some Unknown_Attribute lines. Your FAQ suggests I email you about it. > I'll be taking care of the failed self-check disk. I'm just curious > about the unknown attribute changing from 75 to 76 and back. What would > this value be? > > These disks are attached to a 3ware 9650SE-12ML (12 port) card. I have > the latest drivers for the card as of about 3 weeks ago. > [3ware_disk_01], FAILED SMART self-check. BACK UP DATA NOW! This is a geniune warning and should not be ignored. I suggest that you run: smartctl -a /dev/twa0 -d 3ware,1 to see what Attribute is failing. The other output is not very significant or worrying. > I am also curious if anybody knows how to clearly define which 3ware > disks are which /dev/sd* device? I have 12 identical drives set up in 6 > identical raid-1 arrays for this particular box, and I'd like to verify > which disks belong to which linux device. I am mostly interested in > knowing for sure which one is /dev/sda, since that drive has my OS on it > (for now). Adam, could you respond to that? Cheers, Bruce |
From: Kai M. <ka...@fi...> - 2008-07-22 16:57:17
|
Bruce Allen wrote: > Hi Kai, >> [3ware_disk_01], FAILED SMART self-check. BACK UP DATA NOW! > > This is a geniune warning and should not be ignored. I suggest that > you run: > > smartctl -a /dev/twa0 -d 3ware,1 > > to see what Attribute is failing. The other output is not very > significant or worrying. Right. I'm already chasing down another drive for the replacement. I'm not to worried about this server. I could loose all the data, and not be put out more than an hour or so of work. What I'm more interested in is the Unknown_Attributes that are showing up (and the 3ware to linux device question below too). Looking into it a little more, I have a number of unknowns. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail Always - 79963729 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 7 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 029 028 030 Pre-fail Always FAILING_NOW 23600849005027 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 187 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 7 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 Unknown_Attribute 0x003a 091 091 000 Old_age Always - 9 190 Unknown_Attribute 0x0022 075 068 045 Old_age Always - 454557721 194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (Lifetime Min/Max 0/21) 195 Hardware_ECC_Recovered 0x001a 056 043 000 Old_age Always - 79963729 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 All 12 of my disks ahve these "Unknown_Attribute"s, and the FAQ suggested I asked this list to try and figure them out. These are brand-new Seagate disks. > >> I am also curious if anybody knows how to clearly define which 3ware >> disks are which /dev/sd* device? I have 12 identical drives set up in >> 6 identical raid-1 arrays for this particular box, and I'd like to >> verify which disks belong to which linux device. I am mostly >> interested in knowing for sure which one is /dev/sda, since that >> drive has my OS on it (for now). > > Adam, could you respond to that? > > Cheers, > Bruce Thanks, Kai |
From: Bruce A. <ba...@gr...> - 2008-07-22 17:39:54
|
>>> [3ware_disk_01], FAILED SMART self-check. BACK UP DATA NOW! >> >> This is a geniune warning and should not be ignored. I suggest that >> you run: >> >> smartctl -a /dev/twa0 -d 3ware,1 >> >> to see what Attribute is failing. The other output is not very >> significant or worrying. > Right. I'm already chasing down another drive for the replacement. I'm > not to worried about this server. I could loose all the data, and not be > put out more than an hour or so of work. What I'm more interested in is > the Unknown_Attributes that are showing up (and the 3ware to linux > device question below too). Looking into it a little more, I have a > number of unknowns. > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE > UPDATED WHEN_FAILED RAW_VALUE > 7 Seek_Error_Rate 0x000f 029 028 030 Pre-fail > Always FAILING_NOW 23600849005027 This is the problem. The drive is having mechanical/servo problems steering the head to the correct track. > 9 Power_On_Hours 0x0032 100 100 000 Old_age > Always - 187 Hmmm, 187 hours old, infant death. > 184 Unknown_Attribute 0x0032 100 100 099 Old_age > Always - 0 > 187 Unknown_Attribute 0x0032 100 100 000 Old_age > Always - 0 > 188 Unknown_Attribute 0x0032 100 100 000 Old_age > Always - 0 > 189 Unknown_Attribute 0x003a 091 091 000 Old_age > Always - 9 > 190 Unknown_Attribute 0x0022 075 068 045 Old_age > Always - 454557721 You'll have to ask the disk vendor if they can identify these Attributes and their interpretation. > 194 Temperature_Celsius 0x0022 025 040 000 Old_age > Always - 25 (Lifetime Min/Max 0/21) Very nice (cool!) operating temperatures! > All 12 of my disks ahve these "Unknown_Attribute"s, and the FAQ > suggested I asked this list to try and figure them out. These are > brand-new Seagate disks. I don't have much idea what these are. You can try contacting Seagate directly to ask. Cheers, Bruce |
From: Kai M. <ka...@fi...> - 2008-07-22 19:07:55
|
Bruce Allen wrote: >>>> [3ware_disk_01], FAILED SMART self-check. BACK UP DATA NOW! >>> >>> This is a geniune warning and should not be ignored. I suggest that >>> you run: >>> >>> smartctl -a /dev/twa0 -d 3ware,1 >>> >>> to see what Attribute is failing. The other output is not very >>> significant or worrying. >> Right. I'm already chasing down another drive for the replacement. I'm >> not to worried about this server. I could loose all the data, and not be >> put out more than an hour or so of work. What I'm more interested in is >> the Unknown_Attributes that are showing up (and the 3ware to linux >> device question below too). Looking into it a little more, I have a >> number of unknowns. >> >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE >> UPDATED WHEN_FAILED RAW_VALUE >> 7 Seek_Error_Rate 0x000f 029 028 030 Pre-fail >> Always FAILING_NOW 23600849005027 > > This is the problem. The drive is having mechanical/servo problems > steering the head to the correct track. > >> 9 Power_On_Hours 0x0032 100 100 000 Old_age >> Always - 187 > > Hmmm, 187 hours old, infant death. > >> 184 Unknown_Attribute 0x0032 100 100 099 Old_age >> Always - 0 >> 187 Unknown_Attribute 0x0032 100 100 000 Old_age >> Always - 0 >> 188 Unknown_Attribute 0x0032 100 100 000 Old_age >> Always - 0 >> 189 Unknown_Attribute 0x003a 091 091 000 Old_age >> Always - 9 >> 190 Unknown_Attribute 0x0022 075 068 045 Old_age >> Always - 454557721 > > You'll have to ask the disk vendor if they can identify these > Attributes and their interpretation. > >> 194 Temperature_Celsius 0x0022 025 040 000 Old_age >> Always - 25 (Lifetime Min/Max 0/21) > > Very nice (cool!) operating temperatures! > >> All 12 of my disks ahve these "Unknown_Attribute"s, and the FAQ >> suggested I asked this list to try and figure them out. These are >> brand-new Seagate disks. > > I don't have much idea what these are. You can try contacting Seagate > directly to ask. > > Cheers, > Bruce > The closest I've gotten is on wikipedia. http://en.wikipedia.org/wiki/Self-Monitoring,_Analysis,_and_Reporting_Technology#Attributes This page lists attribute 190 as 100-Temperature. Not really all that useful. I still don't know what 184-189 is though. Seagate's live chat was a dead end. I don't think the techs I chatted with knew much about SMART at all, and baulked at the usage of "3rd party" software. I can't blame them for not supporting other software, but there's gotta be a spreadsheet somewhere that lists SMART attributes IDs, names, and descriptions. The best I got out of them was a "3rd party" site: http://www.ariolic.com/activesmart/smart-attributes/ So, from the results that I'm seeing on this server, wikipedia's description of attribute 190 is accurate: Here's all 12 disks, and the 190 and 194 attributes. Each server at 25 degrees has 190 listed as 75. Each at 26 has 190 listed as 74. Seems a pretty safe bet that's what's going on. log.00.txt:190 Unknown_Attribute 0x0022 075 068 045 Old_age Always - 454557721 log.00.txt:194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (Lifetime Min/Max 0/21) log.01.txt:190 Unknown_Attribute 0x0022 075 068 045 Old_age Always - 454557721 log.01.txt:194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (Lifetime Min/Max 0/21) log.02.txt:190 Unknown_Attribute 0x0022 074 066 045 Old_age Always - 488243226 log.02.txt:194 Temperature_Celsius 0x0022 026 040 000 Old_age Always - 26 (Lifetime Min/Max 0/22) log.03.txt:190 Unknown_Attribute 0x0022 076 068 045 Old_age Always - 454492184 log.03.txt:194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/21) log.04.txt:190 Unknown_Attribute 0x0022 076 068 045 Old_age Always - 454557720 log.04.txt:194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/21) log.05.txt:190 Unknown_Attribute 0x0022 075 068 045 Old_age Always - 471334937 log.05.txt:194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (Lifetime Min/Max 0/21) log.06.txt:190 Unknown_Attribute 0x0022 076 068 045 Old_age Always - 454492184 log.06.txt:194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/21) log.07.txt:190 Unknown_Attribute 0x0022 076 068 045 Old_age Always - 454492184 log.07.txt:194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/21) log.08.txt:190 Unknown_Attribute 0x0022 076 068 045 Old_age Always - 454557720 log.08.txt:194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/21) log.09.txt:190 Unknown_Attribute 0x0022 075 068 045 Old_age Always - 454557721 log.09.txt:194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/22) log.10.txt:190 Unknown_Attribute 0x0022 077 069 045 Old_age Always - 437649431 log.10.txt:194 Temperature_Celsius 0x0022 023 040 000 Old_age Always - 23 (Lifetime Min/Max 0/21) log.11.txt:190 Unknown_Attribute 0x0022 076 067 045 Old_age Always - 454492184 log.11.txt:194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/21) -Kai Meyer |
From: Bruce A. <ba...@gr...> - 2008-07-22 19:12:58
|
Hi Kai, On current smartmontools releases, Attribute 190 is listed as Airflow_Temperature_Cel. This is how it is used by Western Digital. Apparently Seagate uses it for 100-temperature_in_Celsius. Cheers, Bruce On Tue, 22 Jul 2008, Kai Meyer wrote: > Bruce Allen wrote: >>>>> [3ware_disk_01], FAILED SMART self-check. BACK UP DATA NOW! >>>> >>>> This is a geniune warning and should not be ignored. I suggest that >>>> you run: >>>> >>>> smartctl -a /dev/twa0 -d 3ware,1 >>>> >>>> to see what Attribute is failing. The other output is not very >>>> significant or worrying. >>> Right. I'm already chasing down another drive for the replacement. I'm >>> not to worried about this server. I could loose all the data, and not be >>> put out more than an hour or so of work. What I'm more interested in is >>> the Unknown_Attributes that are showing up (and the 3ware to linux >>> device question below too). Looking into it a little more, I have a >>> number of unknowns. >>> >>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE >>> UPDATED WHEN_FAILED RAW_VALUE >>> 7 Seek_Error_Rate 0x000f 029 028 030 Pre-fail >>> Always FAILING_NOW 23600849005027 >> >> This is the problem. The drive is having mechanical/servo problems >> steering the head to the correct track. >> >>> 9 Power_On_Hours 0x0032 100 100 000 Old_age >>> Always - 187 >> >> Hmmm, 187 hours old, infant death. >> >>> 184 Unknown_Attribute 0x0032 100 100 099 Old_age >>> Always - 0 >>> 187 Unknown_Attribute 0x0032 100 100 000 Old_age >>> Always - 0 >>> 188 Unknown_Attribute 0x0032 100 100 000 Old_age >>> Always - 0 >>> 189 Unknown_Attribute 0x003a 091 091 000 Old_age >>> Always - 9 >>> 190 Unknown_Attribute 0x0022 075 068 045 Old_age >>> Always - 454557721 >> >> You'll have to ask the disk vendor if they can identify these >> Attributes and their interpretation. >> >>> 194 Temperature_Celsius 0x0022 025 040 000 Old_age >>> Always - 25 (Lifetime Min/Max 0/21) >> >> Very nice (cool!) operating temperatures! >> >>> All 12 of my disks ahve these "Unknown_Attribute"s, and the FAQ >>> suggested I asked this list to try and figure them out. These are >>> brand-new Seagate disks. >> >> I don't have much idea what these are. You can try contacting Seagate >> directly to ask. >> >> Cheers, >> Bruce >> > The closest I've gotten is on wikipedia. > http://en.wikipedia.org/wiki/Self-Monitoring,_Analysis,_and_Reporting_Technology#Attributes > This page lists attribute 190 as 100-Temperature. Not really all that > useful. I still don't know what 184-189 is though. Seagate's live chat > was a dead end. I don't think the techs I chatted with knew much about > SMART at all, and baulked at the usage of "3rd party" software. I can't > blame them for not supporting other software, but there's gotta be a > spreadsheet somewhere that lists SMART attributes IDs, names, and > descriptions. The best I got out of them was a "3rd party" site: > http://www.ariolic.com/activesmart/smart-attributes/ > > So, from the results that I'm seeing on this server, wikipedia's > description of attribute 190 is accurate: > > Here's all 12 disks, and the 190 and 194 attributes. Each server at 25 > degrees has 190 listed as 75. Each at 26 has 190 listed as 74. Seems a > pretty safe bet that's what's going on. > log.00.txt:190 Unknown_Attribute 0x0022 075 068 045 > Old_age Always - 454557721 > log.00.txt:194 Temperature_Celsius 0x0022 025 040 000 > Old_age Always - 25 (Lifetime Min/Max 0/21) > log.01.txt:190 Unknown_Attribute 0x0022 075 068 045 > Old_age Always - 454557721 > log.01.txt:194 Temperature_Celsius 0x0022 025 040 000 > Old_age Always - 25 (Lifetime Min/Max 0/21) > log.02.txt:190 Unknown_Attribute 0x0022 074 066 045 > Old_age Always - 488243226 > log.02.txt:194 Temperature_Celsius 0x0022 026 040 000 > Old_age Always - 26 (Lifetime Min/Max 0/22) > log.03.txt:190 Unknown_Attribute 0x0022 076 068 045 > Old_age Always - 454492184 > log.03.txt:194 Temperature_Celsius 0x0022 024 040 000 > Old_age Always - 24 (Lifetime Min/Max 0/21) > log.04.txt:190 Unknown_Attribute 0x0022 076 068 045 > Old_age Always - 454557720 > log.04.txt:194 Temperature_Celsius 0x0022 024 040 000 > Old_age Always - 24 (Lifetime Min/Max 0/21) > log.05.txt:190 Unknown_Attribute 0x0022 075 068 045 > Old_age Always - 471334937 > log.05.txt:194 Temperature_Celsius 0x0022 025 040 000 > Old_age Always - 25 (Lifetime Min/Max 0/21) > log.06.txt:190 Unknown_Attribute 0x0022 076 068 045 > Old_age Always - 454492184 > log.06.txt:194 Temperature_Celsius 0x0022 024 040 000 > Old_age Always - 24 (Lifetime Min/Max 0/21) > log.07.txt:190 Unknown_Attribute 0x0022 076 068 045 > Old_age Always - 454492184 > log.07.txt:194 Temperature_Celsius 0x0022 024 040 000 > Old_age Always - 24 (Lifetime Min/Max 0/21) > log.08.txt:190 Unknown_Attribute 0x0022 076 068 045 > Old_age Always - 454557720 > log.08.txt:194 Temperature_Celsius 0x0022 024 040 000 > Old_age Always - 24 (Lifetime Min/Max 0/21) > log.09.txt:190 Unknown_Attribute 0x0022 075 068 045 > Old_age Always - 454557721 > log.09.txt:194 Temperature_Celsius 0x0022 024 040 000 > Old_age Always - 24 (Lifetime Min/Max 0/22) > log.10.txt:190 Unknown_Attribute 0x0022 077 069 045 > Old_age Always - 437649431 > log.10.txt:194 Temperature_Celsius 0x0022 023 040 000 > Old_age Always - 23 (Lifetime Min/Max 0/21) > log.11.txt:190 Unknown_Attribute 0x0022 076 067 045 > Old_age Always - 454492184 > log.11.txt:194 Temperature_Celsius 0x0022 024 040 000 > Old_age Always - 24 (Lifetime Min/Max 0/21) > > > > -Kai Meyer > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Adam R. <ara...@am...> - 2008-07-22 21:20:10
|
> I am also curious if anybody knows how to clearly define which 3ware > disks are which /dev/sd* device? I have 12 identical drives set up in 6 > identical raid-1 arrays for this particular box, and I'd like to verify > which disks belong to which linux device. I am mostly interested in > knowing for sure which one is /dev/sda, since that drive has my OS on it > (for now). Kai, If you are confused about which disk is which, simply look in the /sys filesystem entry for that disk. [root@linux2 /]# cat /sys/block/sda/device/vendor ATA This is most likely a boot disk on a motherboard serial or parallel ata port. [root@linux2 /]# cat /sys/block/sdb/device/vendor 3ware This device is an older 3ware 5/6/7/8000 series raid unit or JBOD disk. [root@linux2 /]# cat /sys/block/sdc/device/vendor AMCC This device is a newer 3ware 9000 series raid unit or JBOD disk. You can also look in /var/log/messages or 'dmesg' output to see which disk device names (/dev/sda, etc) are assigned to which scsi devices (Host, Channel, ID, Lun): scsi1 : 3ware Storage Controller 3w-xxxx: scsi1: Found a 3ware Storage Controller at 0x9c00, IRQ: 225. Vendor: 3ware Model: Logical Disk 7 Rev: 1.2 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) sdb: Write Protect is off sdb: Mode Sense: 00 00 00 00 SCSI device sdb: drive cache: write back w/ FUA SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) sdb: Write Protect is off sdb: Mode Sense: 00 00 00 00 SCSI device sdb: drive cache: write back w/ FUA sdb: sdb1 sdb2 < sdb5 > sd 1:0:7:0: Attached scsi disk sdb Above note the "scsi1: 3ware Storage Controller" line, which indicates that the 3ware controller is on scsi "host 1". Above you see that disk '/dev/sdb' was assigned by the OS to Host: 1, Channel: 0, ID: 7, Lun: 0. as noted by the line: "sd 1:0:7:0: Attached scsi disk sdb" Therefore, you can tell that ID 7, (/dev/sdb) which is assigned to Host 1 is attached to a 3ware controller. Output from the tw_cli (3ware command line software) on the same system shows: [root@linux2 /]# /root/tw_cli //linux2> info Ctl Model (V)Ports Drives Units NotOpt RRate VRate BBU ------------------------------------------------------------------------ c1 8506-12 12 1 1 0 2 - - Here we see "c1" Controller 1, which is the same as "scsi host 1" or "scsi1" in the above output. //linux2> info c1 Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u7 JBOD OK - - - 149.051 ON - Port Status Unit Size Blocks Serial --------------------------------------------------------------- p0 NOT-PRESENT - - - - p1 NOT-PRESENT - - - - p2 NOT-PRESENT - - - - p3 NOT-PRESENT - - - - p4 NOT-PRESENT - - - - p5 NOT-PRESENT - - - - p6 NOT-PRESENT - - - - p7 OK u7 149.05 GB 312581808 WD-WCANM1024184 p8 NOT-PRESENT - - - - p9 NOT-PRESENT - - - - p10 NOT-PRESENT - - - - p11 NOT-PRESENT - - - - Here we see "u7" or "unit id 7" which is the same as "ID 7" in the above output. Therefore we can conclude that 3ware controller ID 1, unit 7 on port 7 is in fact /dev/sdb. -Adam -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. All unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. |
From: Kai M. <ka...@fi...> - 2008-07-22 21:42:19
|
Adam Radford wrote: > > > > I am also curious if anybody knows how to clearly define which 3ware > > disks are which /dev/sd* device? I have 12 identical drives set up in 6 > > identical raid-1 arrays for this particular box, and I'd like to verify > > which disks belong to which linux device. I am mostly interested in > > knowing for sure which one is /dev/sda, since that drive has my OS on it > > (for now). > > Kai, > > If you are confused about which disk is which, simply look in the /sys > filesystem > entry for that disk. > > [root@linux2 /]# cat /sys/block/sda/device/vendor > ATA > > This is most likely a boot disk on a motherboard serial or parallel > ata port. > > [root@linux2 /]# cat /sys/block/sdb/device/vendor > 3ware > > This device is an older 3ware 5/6/7/8000 series raid unit or JBOD disk. > > [root@linux2 /]# cat /sys/block/sdc/device/vendor > AMCC > > This device is a newer 3ware 9000 series raid unit or JBOD disk. > > > You can also look in /var/log/messages or 'dmesg' output to see which > disk device > names (/dev/sda, etc) are assigned to which scsi devices (Host, > Channel, ID, Lun): > > scsi1 : 3ware Storage Controller > 3w-xxxx: scsi1: Found a 3ware Storage Controller at 0x9c00, IRQ: 225. > Vendor: 3ware Model: Logical Disk 7 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) > sdb: Write Protect is off > sdb: Mode Sense: 00 00 00 00 > SCSI device sdb: drive cache: write back w/ FUA > SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) > sdb: Write Protect is off > sdb: Mode Sense: 00 00 00 00 > SCSI device sdb: drive cache: write back w/ FUA > sdb: sdb1 sdb2 < sdb5 > > sd 1:0:7:0: Attached scsi disk sdb > > Above note the "scsi1: 3ware Storage Controller" line, which indicates > that the 3ware controller is on scsi "host 1". > > Above you see that disk '/dev/sdb' was assigned by the OS to Host: 1, > Channel: 0, > ID: 7, Lun: 0. as noted by the line: "sd 1:0:7:0: Attached scsi disk sdb" > > Therefore, you can tell that ID 7, (/dev/sdb) which is assigned to > Host 1 is > attached to a 3ware controller. > > Output from the tw_cli (3ware command line software) on the same > system shows: > > [root@linux2 /]# /root/tw_cli > //linux2> info > > Ctl Model (V)Ports Drives Units NotOpt RRate VRate BBU > ------------------------------------------------------------------------ > c1 8506-12 12 1 1 0 2 - > - > > Here we see "c1" Controller 1, which is the same as "scsi host 1" or > "scsi1" in the > above output. > > //linux2> info c1 > > Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) > Cache AVrfy > ------------------------------------------------------------------------------ > u7 JBOD OK - - - 149.051 > ON - > > Port Status Unit Size Blocks Serial > --------------------------------------------------------------- > p0 NOT-PRESENT - - - - > p1 NOT-PRESENT - - - - > p2 NOT-PRESENT - - - - > p3 NOT-PRESENT - - - - > p4 NOT-PRESENT - - - - > p5 NOT-PRESENT - - - - > p6 NOT-PRESENT - - - - > p7 OK u7 149.05 GB 312581808 > WD-WCANM1024184 > p8 NOT-PRESENT - - - - > p9 NOT-PRESENT - - - - > p10 NOT-PRESENT - - - - > p11 NOT-PRESENT - - - - > > Here we see "u7" or "unit id 7" which is the same as "ID 7" in the above > output. Therefore we can conclude that 3ware controller ID 1, unit 7 > on port 7 > is in fact /dev/sdb. > > -Adam > > ------------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: This e-mail message, including any > attachments, is for the sole use of the intended recipient(s) and > contains information that is confidential and proprietary to Applied > Micro Circuits Corporation or its subsidiaries. It is to be used > solely for the purpose of furthering the parties' business > relationship. All unauthorized review, use, disclosure or distribution > is prohibited. If you are not the intended recipient, please contact > the sender by reply e-mail and destroy all copies of the original > message. Perfect. Thanks so much Adam. As I hoped/expected, 0-5 are a-f. Jul 15 15:08:17 localhost kernel: sd 0:0:0:0: Attached scsi disk sda Jul 15 15:08:17 localhost kernel: sd 0:0:1:0: Attached scsi disk sdb Jul 15 15:08:17 localhost kernel: sd 0:0:2:0: Attached scsi disk sdc Jul 15 15:08:17 localhost kernel: sd 0:0:3:0: Attached scsi disk sdd Jul 15 15:08:17 localhost kernel: sd 0:0:4:0: Attached scsi disk sde Jul 15 15:08:17 localhost kernel: sd 0:0:5:0: Attached scsi disk sdf -Kai Meyer |
From: Kai M. <ka...@fi...> - 2008-07-23 14:44:16
|
Adam Radford wrote: > > > > I am also curious if anybody knows how to clearly define which 3ware > > disks are which /dev/sd* device? I have 12 identical drives set up in 6 > > identical raid-1 arrays for this particular box, and I'd like to verify > > which disks belong to which linux device. I am mostly interested in > > knowing for sure which one is /dev/sda, since that drive has my OS on it > > (for now). > > Kai, > > If you are confused about which disk is which, simply look in the /sys > filesystem > entry for that disk. > > [root@linux2 /]# cat /sys/block/sda/device/vendor > ATA > > This is most likely a boot disk on a motherboard serial or parallel > ata port. > > [root@linux2 /]# cat /sys/block/sdb/device/vendor > 3ware > > This device is an older 3ware 5/6/7/8000 series raid unit or JBOD disk. > > [root@linux2 /]# cat /sys/block/sdc/device/vendor > AMCC > > This device is a newer 3ware 9000 series raid unit or JBOD disk. > > > You can also look in /var/log/messages or 'dmesg' output to see which > disk device > names (/dev/sda, etc) are assigned to which scsi devices (Host, > Channel, ID, Lun): > > scsi1 : 3ware Storage Controller > 3w-xxxx: scsi1: Found a 3ware Storage Controller at 0x9c00, IRQ: 225. > Vendor: 3ware Model: Logical Disk 7 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) > sdb: Write Protect is off > sdb: Mode Sense: 00 00 00 00 > SCSI device sdb: drive cache: write back w/ FUA > SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) > sdb: Write Protect is off > sdb: Mode Sense: 00 00 00 00 > SCSI device sdb: drive cache: write back w/ FUA > sdb: sdb1 sdb2 < sdb5 > > sd 1:0:7:0: Attached scsi disk sdb > > Above note the "scsi1: 3ware Storage Controller" line, which indicates > that the 3ware controller is on scsi "host 1". > > Above you see that disk '/dev/sdb' was assigned by the OS to Host: 1, > Channel: 0, > ID: 7, Lun: 0. as noted by the line: "sd 1:0:7:0: Attached scsi disk sdb" > > Therefore, you can tell that ID 7, (/dev/sdb) which is assigned to > Host 1 is > attached to a 3ware controller. > > Output from the tw_cli (3ware command line software) on the same > system shows: > > [root@linux2 /]# /root/tw_cli > //linux2> info > > Ctl Model (V)Ports Drives Units NotOpt RRate VRate BBU > ------------------------------------------------------------------------ > c1 8506-12 12 1 1 0 2 - > - > > Here we see "c1" Controller 1, which is the same as "scsi host 1" or > "scsi1" in the > above output. > > //linux2> info c1 > > Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) > Cache AVrfy > ------------------------------------------------------------------------------ > u7 JBOD OK - - - 149.051 > ON - > > Port Status Unit Size Blocks Serial > --------------------------------------------------------------- > p0 NOT-PRESENT - - - - > p1 NOT-PRESENT - - - - > p2 NOT-PRESENT - - - - > p3 NOT-PRESENT - - - - > p4 NOT-PRESENT - - - - > p5 NOT-PRESENT - - - - > p6 NOT-PRESENT - - - - > p7 OK u7 149.05 GB 312581808 > WD-WCANM1024184 > p8 NOT-PRESENT - - - - > p9 NOT-PRESENT - - - - > p10 NOT-PRESENT - - - - > p11 NOT-PRESENT - - - - > > Here we see "u7" or "unit id 7" which is the same as "ID 7" in the above > output. Therefore we can conclude that 3ware controller ID 1, unit 7 > on port 7 > is in fact /dev/sdb. > > -Adam > > ------------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: This e-mail message, including any > attachments, is for the sole use of the intended recipient(s) and > contains information that is confidential and proprietary to Applied > Micro Circuits Corporation or its subsidiaries. It is to be used > solely for the purpose of furthering the parties' business > relationship. All unauthorized review, use, disclosure or distribution > is prohibited. If you are not the intended recipient, please contact > the sender by reply e-mail and destroy all copies of the original > message. Again, thanks for your help Adam. One problem I've run into is that some of my systems have been up long enough that /var/log/messages has rolled over, and I no longer have these types of lines in /var/log/messages or dmesg: sd 1:0:7:0: Attached scsi disk sdb Is there anywhere else this relationship is described like this? Or a way to re-log this data? -Kai Meyer |
From: Kai M. <ka...@fi...> - 2008-07-23 14:47:15
|
Adam Radford wrote: > > > > I am also curious if anybody knows how to clearly define which 3ware > > disks are which /dev/sd* device? I have 12 identical drives set up in 6 > > identical raid-1 arrays for this particular box, and I'd like to verify > > which disks belong to which linux device. I am mostly interested in > > knowing for sure which one is /dev/sda, since that drive has my OS on it > > (for now). > > Kai, > > If you are confused about which disk is which, simply look in the /sys > filesystem > entry for that disk. > > [root@linux2 /]# cat /sys/block/sda/device/vendor > ATA > > This is most likely a boot disk on a motherboard serial or parallel > ata port. > > [root@linux2 /]# cat /sys/block/sdb/device/vendor > 3ware > > This device is an older 3ware 5/6/7/8000 series raid unit or JBOD disk. > > [root@linux2 /]# cat /sys/block/sdc/device/vendor > AMCC > > This device is a newer 3ware 9000 series raid unit or JBOD disk. > > > You can also look in /var/log/messages or 'dmesg' output to see which > disk device > names (/dev/sda, etc) are assigned to which scsi devices (Host, > Channel, ID, Lun): > > scsi1 : 3ware Storage Controller > 3w-xxxx: scsi1: Found a 3ware Storage Controller at 0x9c00, IRQ: 225. > Vendor: 3ware Model: Logical Disk 7 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) > sdb: Write Protect is off > sdb: Mode Sense: 00 00 00 00 > SCSI device sdb: drive cache: write back w/ FUA > SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) > sdb: Write Protect is off > sdb: Mode Sense: 00 00 00 00 > SCSI device sdb: drive cache: write back w/ FUA > sdb: sdb1 sdb2 < sdb5 > > sd 1:0:7:0: Attached scsi disk sdb > > Above note the "scsi1: 3ware Storage Controller" line, which indicates > that the 3ware controller is on scsi "host 1". > > Above you see that disk '/dev/sdb' was assigned by the OS to Host: 1, > Channel: 0, > ID: 7, Lun: 0. as noted by the line: "sd 1:0:7:0: Attached scsi disk sdb" > > Therefore, you can tell that ID 7, (/dev/sdb) which is assigned to > Host 1 is > attached to a 3ware controller. > > Output from the tw_cli (3ware command line software) on the same > system shows: > > [root@linux2 /]# /root/tw_cli > //linux2> info > > Ctl Model (V)Ports Drives Units NotOpt RRate VRate BBU > ------------------------------------------------------------------------ > c1 8506-12 12 1 1 0 2 - > - > > Here we see "c1" Controller 1, which is the same as "scsi host 1" or > "scsi1" in the > above output. > > //linux2> info c1 > > Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) > Cache AVrfy > ------------------------------------------------------------------------------ > u7 JBOD OK - - - 149.051 > ON - > > Port Status Unit Size Blocks Serial > --------------------------------------------------------------- > p0 NOT-PRESENT - - - - > p1 NOT-PRESENT - - - - > p2 NOT-PRESENT - - - - > p3 NOT-PRESENT - - - - > p4 NOT-PRESENT - - - - > p5 NOT-PRESENT - - - - > p6 NOT-PRESENT - - - - > p7 OK u7 149.05 GB 312581808 > WD-WCANM1024184 > p8 NOT-PRESENT - - - - > p9 NOT-PRESENT - - - - > p10 NOT-PRESENT - - - - > p11 NOT-PRESENT - - - - > > Here we see "u7" or "unit id 7" which is the same as "ID 7" in the above > output. Therefore we can conclude that 3ware controller ID 1, unit 7 > on port 7 > is in fact /dev/sdb. > > -Adam > > ------------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: This e-mail message, including any > attachments, is for the sole use of the intended recipient(s) and > contains information that is confidential and proprietary to Applied > Micro Circuits Corporation or its subsidiaries. It is to be used > solely for the purpose of furthering the parties' business > relationship. All unauthorized review, use, disclosure or distribution > is prohibited. If you are not the intended recipient, please contact > the sender by reply e-mail and destroy all copies of the original > message. Ah, nevermind, found it, thanks. :) I hate it when you find what you're looking for moments after you've asked for it.... /sys/block/sda/device/scsi_device:0:0:0:0 -> ../../../../../../../class/scsi_device/0:0:0:0 /sys/block/sdb/device/scsi_device:0:0:1:0 -> ../../../../../../../class/scsi_device/0:0:1:0 /sys/block/sdc/device/scsi_device:0:0:2:0 -> ../../../../../../../class/scsi_device/0:0:2:0 /sys/block/sdd/device/scsi_device:0:0:3:0 -> ../../../../../../../class/scsi_device/0:0:3:0 /sys/block/sde/device/scsi_device:0:0:4:0 -> ../../../../../../../class/scsi_device/0:0:4:0 /sys/block/sdf/device/scsi_device:0:0:5:0 -> ../../../../../../../class/scsi_device/0:0:5:0 |