Hardware

FreeBSD identifying failed disk

Posted by & filed under Hardware.

Using the sas2ircu utility from LSI, we can blink the drive LED to help ID the failed drive correctly. Of course this requires a LSI card. Some LSI cards may need to use the sas3ircu utility instead. There have been some reports from the interwebs that this utility failed to blink the correct drive, but I have not experienced this myself.

As always use the supercomputer between your ears to ensure the physical serial and the serial reported by the system match, etc etc.

[root@jetstore] ~# sas2ircu list
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.


         Adapter      Vendor  Device                       SubSys  SubSys
 Index    Type          ID      ID    Pci Address          Ven ID  Dev ID
 -----  ------------  ------  ------  -----------------    ------  ------
   0     SAS2308_2     1000h    87h   00h:06h:00h:00h      1000h   3020h

         Adapter      Vendor  Device                       SubSys  SubSys
 Index    Type          ID      ID    Pci Address          Ven ID  Dev ID
 -----  ------------  ------  ------  -----------------    ------  ------
   1     SAS2308_2     1000h    87h   00h:81h:00h:00h      1000h   3020h
SAS2IRCU: Utility Completed Successfully.

Back to the sas2ircu utility in a moment. We need to first acquire the serial number of the failed disk. For a system that is multipath, we can find the actual dev names by running the following to locate a disk in the fail state:

[root@jetstore] ~# gmultipath list | grep -i -B 10 fail
Consumers:
1. Name: da43
   Mediasize: 3000592982016 (2.7T)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
2. Name: da16
   Mediasize: 3000592982016 (2.7T)
   Sectorsize: 512
   Mode: r1w1e1
   State: FAIL

Now we can see da16 is failed. Time to get the serial number of that disk. Or da43. they are the same just multipaths.

[root@jetstore] ~# smartctl -a /dev/da16 | grep Serial
Serial number:        WMC1F0D5T1DF

Save that serial number for the next step.

Smartctl also outputs other useful information about the drive, statistics, etc. Worth checking out, but not relevant here.

Next, we can display the disks attached to one of those controllers. Be sure to input the correct serial number in the grep command:

[root@jetstore] ~# sas2ircu 0 display | grep -C 10 WMC1F0D5T1DF

Device is a Hard disk
  Enclosure #                             : 3
  Slot #                                  : 20
  SAS Address                             : 50000c0-f-01f9-f6eb
  State                                   : Ready (RDY)
  Size (in MB)/(in sectors)               : 2861588/5860533167
  Manufacturer                            : WD
  Model Number                            : WD3001FYYG-01SL3
  Firmware Revision                       : VR08
  Serial No                               : WDWMC1F0D5T1DF
  GUID                                    : N/A
  Protocol                                : SAS
  Drive Type                              : SAS_HDD

Get the enclosure and slot # of the failed drive and turn the led on:

sas2ircu 0 locate 3:20 ON

Turn the led off:

sas2ircu 0 locate 3:20 OFF

NOTE: If you are replacing a disk that is multipath, e.g. you see something like the following when you offline and remove a disk, ensure that the LED above is OFF or GEOM_MULTIPATH will not pickup the new disk as multipath. See the below log for what happens when a disk is inserted with the LED blinking Vs not blinking:

----------start drive detach event (already offline)------------
Aug 14 14:05:31 jetstore mps1: mpssas_prepare_remove: Sending reset for target ID 27
Aug 14 14:05:31 jetstore da43 at mps1 bus 0 scbus10 target 27 lun 0
Aug 14 14:05:31 jetstore da43: <WD WD3001FYYG-01SL3 VR08> s/n         WMC1F0D5T1DF detached
Aug 14 14:05:31 jetstore GEOM_MULTIPATH: da43 in disk17 was disconnected
Aug 14 14:05:31 jetstore mps1: GEOM_MULTIPATH: all paths in disk17 were marked FAIL, restore da16
Aug 14 14:05:31 jetstore Unfreezing devq for target ID 27
Aug 14 14:05:31 jetstore GEOM_MULTIPATH: da16 is now active path in disk17
Aug 14 14:05:31 jetstore GEOM_MULTIPATH: da43 removed from disk17
Aug 14 14:05:31 jetstore (da43:mps1:0:27:0): Periph destroyed
Aug 14 14:05:31 jetstore mps0: mpssas_prepare_remove: Sending reset for target ID 38
Aug 14 14:05:31 jetstore da16 at mps0 bus 0 scbus2 target 38 lun 0
Aug 14 14:05:31 jetstore da16: <WD WD3001FYYG-01SL3 VR08> s/n         WMC1F0D5T1DF detached
Aug 14 14:05:31 jetstore GEOM_MULTIPATH: da16 in disk17 was disconnected
Aug 14 14:05:31 jetstore mps0: GEOM_MULTIPATH: out of providers for disk17
Aug 14 14:05:31 jetstore Unfreezing devq for target ID 38
Aug 14 14:05:31 jetstore GEOM_MULTIPATH: da16 removed from disk17
Aug 14 14:05:31 jetstore GEOM_MULTIPATH: destroying disk17
Aug 14 14:05:31 jetstore GEOM_MULTIPATH: disk17 destroyed
Aug 14 14:05:31 jetstore (da16:mps0:0:38:0): Periph destroyed
----------end detach event-------------

----------start insert with LED BLINKING - note no GEOM_MULTIPATH----------
Aug 14 14:10:27 jetstore da16 at mps0 bus 0 scbus2 target 50 lun 0
Aug 14 14:10:27 jetstore da16: da43 at mps1 bus 0 scbus10 target 39 lun 0
Aug 14 14:10:27 jetstore syslog-ng[1426]: Error processing log message: <WD WD3001FYYG-01SL3 VR08> Fixed Direct Access SPC-4 SCSI device
Aug 14 14:10:27 jetstore da43: da16: Serial Number         WMC1F0D9UX1U
Aug 14 14:10:27 jetstore syslog-ng[1426]: Error processing log message: <WD WD3001FYYG-01SL3 VR08> Fixed Direct Access SPC-4 SCSI device
Aug 14 14:10:27 jetstore da16: 600.000MB/s transfersda43: Serial Number         WMC1F0D9UX1U
Aug 14 14:10:27 jetstore da43: 600.000MB/s transfersda16: Command Queueing enabled
Aug 14 14:10:27 jetstore da16: 2861588MB (5860533168 512 byte sectors)
Aug 14 14:10:27 jetstore da43: Command Queueing enabled
Aug 14 14:10:27 jetstore da43: 2861588MB (5860533168 512 byte sectors)
Aug 14 14:10:27 jetstore ses3: da43,pass47: Element descriptor: 'Slot 21'
Aug 14 14:10:27 jetstore ses0: da16,pass18: Element descriptor: 'Slot 21'
Aug 14 14:10:27 jetstore ses3: da43,pass47: SAS Device Slot Element: 1 Phys at Slot 20
Aug 14 14:10:27 jetstore ses0: da16,pass18: SAS Device Slot Element: 1 Phys at Slot 20
Aug 14 14:10:27 jetstore ses3:  phy 0: SAS device type 1 id 0
Aug 14 14:10:27 jetstore ses0:  phy 0: SAS device type 1 id 1
Aug 14 14:10:27 jetstore ses3:  phy 0: protocols: Initiator( None ) Target( SSP )
Aug 14 14:10:27 jetstore ses0:  phy 0: protocols: Initiator( None ) Target( SSP )
Aug 14 14:10:27 jetstore ses3:  phy 0: parent 50030480003c273f addr 50000c0f0137b686
Aug 14 14:10:27 jetstore ses0:  phy 0: parent 50030480003c27bf addr 50000c0f0137b687

-------end insert with LED BLINKING-------


------start insert with LED off----------------

Aug 14 14:28:53 jetstore da16 at mps0 bus 0 scbus2 target 50 lun 0
Aug 14 14:28:53 jetstore da43 at mps1 bus 0 scbus10 target 39 lun 0
Aug 14 14:28:53 jetstore da16: da43: <WD WD3001FYYG-01SL3 VR08> Fixed Direct Access SPC-4 SCSI device
Aug 14 14:28:53 jetstore syslog-ng[1426]: Error processing log message: <WD WD3001FYYG-01SL3 VR08> Fixed Direct Access SPC-4 SCSI device
Aug 14 14:28:53 jetstore da16: Serial Number         WMC1F0D9UX1U
Aug 14 14:28:53 jetstore da43: Serial Number         WMC1F0D9UX1U
Aug 14 14:28:53 jetstore da16: 600.000MB/s transfersda43: 600.000MB/s transfers
Aug 14 14:28:53 jetstore da16: Command Queueing enabled
Aug 14 14:28:53 jetstore da43: Command Queueing enabled
Aug 14 14:28:53 jetstore da16: 2861588MB (5860533168 512 byte sectors)
Aug 14 14:28:53 jetstore da43: 2861588MB (5860533168 512 byte sectors)
Aug 14 14:28:53 jetstore ses3: da43,pass47: Element descriptor: 'Slot 21'
Aug 14 14:28:53 jetstore ses0: da16,pass18: Element descriptor: 'Slot 21'
Aug 14 14:28:53 jetstore ses3: da43,pass47: SAS Device Slot Element: 1 Phys at Slot 20
Aug 14 14:28:53 jetstore ses0: da16,pass18: SAS Device Slot Element: 1 Phys at Slot 20
Aug 14 14:28:53 jetstore ses3:  phy 0: SAS device type 1 id 0
Aug 14 14:28:53 jetstore ses0:  phy 0: SAS device type 1 id 1
Aug 14 14:28:53 jetstore ses3:  phy 0: protocols: Initiator( None ) Target( SSP )
Aug 14 14:28:53 jetstore ses0:  phy 0: protocols: Initiator( None ) Target( SSP )
Aug 14 14:28:53 jetstore ses3:  phy 0: parent 50030480003c273f addr 50000c0f0137b686
Aug 14 14:28:53 jetstore ses0:  phy 0: parent 50030480003c27bf addr 50000c0f0137b687
Aug 14 14:29:07 jetstore GEOM_MULTIPATH: disk17 created
Aug 14 14:29:07 jetstore GEOM_MULTIPATH: da16 added to disk17
Aug 14 14:29:07 jetstore GEOM_MULTIPATH: da16 is now active path in disk17
Aug 14 14:29:07 jetstore GEOM_MULTIPATH: da43 added to disk17

------end insert with LED off----------------

 

PlatformIO

Posted by & filed under Adruino, Hardware, Hardware Development, Programming.

PlatformIO is an open source ecosystem for IoT development
Cross-platform build system. Continuous and IDE integration. Arduino and ARM mbed compatible

 

Came across this cool IDE, built on top of Atom for dev of iot. There is also a commercially supported offering. http://platformio.org/

OpenPilot – Open Source UAV Control System

Posted by & filed under 3D Printing, Hardware, Hardware Development.

OpenPilot is a next-generation Open Source UAV autopilot created by the OpenPilot Community (an all volunteer non-profit community). It is a highly capable platform for multirotors, helicopters, fixed wing aircraft, and other vehicles . It has been designed from the ground up by a community of passionate developers from around the globe, with its core design principles being quality, safety, and ease of use. Simplicity does not come with any compromises either: with no hard-coded settings, a complete flight plan scripting language and other powerful features, OpenPilot is an extremely capable UAV autopilot platform.

OpenPilot was started at the beginning of 2010 and is a serious use platform aimed at civilian and research purposes, with emphasis being placed on making the platform especially suitable for aerial photography and aerial video applications.

www.openpilot.org/

ESP2866 — WiFi for the Arduino

Posted by & filed under Adruino, Electronic, Hardware, Hardware Development.

This board is really freakin cool. It no only has a SoC chip that is essentially a UART to WiFi, it’s microprocessor is also programmable and has a PWM pin as well. On Arduino day, it was announced that the Arduino IDE now supports the ESP2866 making things a lot easier.

 

01-02
  • Article on the ESP2866: makezine.com/2015/04/01/esp8266-5-microc…
  • ESP2866 Forums: http://www.esp8266.com/viewforum.php?f=25
  • ESP2866 Arduino Source code: https://github.com/esp8266/arduino
  • ESP2866 Breakout Boards: http://www.esp8266.com/wiki/doku.php?id=esp8266-module-family
  • ESP2866 on eBay: http://www.ebay.com/itm/like/251690993989?lpid=82&chn=ps
  • Seeed studio ESP2866 Module: http://www.seeedstudio.com/depot/WiFi-Serial-Transceiver-Module-w-ESP8266-p-1994.html

Thermoelectric generators

Posted by & filed under Hardware.

Thermoelectric generators (also called thermogenerators) are devices which convert heat (temperature differences) directly into electrical energy, using a phenomenon called the “Seebeck effect” (or “thermoelectric effect”). Their typical efficiencies are around 5-10%. Older Seebeck-based devices used bimetallic junctions and were bulky while more recent devices use bismuth telluride (Bi2Te3) semiconductor p-n junctions and can have thicknesses in the millimeter range. These are solid state devices and unlike dynamos have no moving parts, with the occasional exception of a fan.

en.wikipedia.org/wiki/Thermoelectric_gen…

TEG Suppliers
theepicenter.com/cgi/order.cgi?page=camp…

biolitestove.com/campstove/camp-overview…

Prey – Open Source PC/MAC/iOS/Android Anti-Theft

Posted by & filed under Hardware.

Now this is cool — a open source anti-theft system for your laptop, iOS, or Android device.

From the website: Prey lets you keep track of your phone or laptop at all times, and will help you find it if it ever gets lost or stolen. It’s lightweight, open source software, and free for anyone to use. And it just works.

Website: preyproject.com/
git Repo: github.com/prey

Wi-Fi Protected Setup Vulnerability

Posted by & filed under Hardware, Networking, WiFi.

The Wi-Fi protected setup with which a large majority of new routers ship with enabled by default has a serious flaw opening it up to a brute force attack against the WPS pin. Additional flaws allow for a successful brute force attack in 11,000 attempts. This means the network key of a protected network can be retrieved within hours.

The best course of action right now is to disable WPS if possible. This is not a option on all routers, but the possibility may exist of re-flashing the router’s firmware to a different one such as Open-WRT, DD-WRT, Tomato, etc. to disable it.

CERT’s Release: www.kb.cert.org/vuls/id/723755
Vulnerability Technical Details: sviehb.files.wordpress.com/2011/12/viehb…
Reaver — Functional exploit: code.google.com/p/reaver-wps/

4:3 and 16:9 Screen Resolutions

Posted by & filed under Hardware.

List of 4:3 Monitor Resolutions
Resolution – Aspect ratio
640×480—–4:3
800×600—–4:3
1024×768—–4:3
1152×864—–4:3
1280×960—–4:3
1400×1050—–4:3
1600×1200—–4:3
2048×1536—–4:3
3200×2400—–4:3
4000×3000—–4:3
6400×4800—–4:3

List of 16:9 Widescreen Resolutions
Resolution – Aspect ratio
852×480—–16:9
1280×720—–16:9
1365×768—–16:9
1600×900—–16:9
1920×1080—–16:9

List of 16:10 Widescreen Resolutions
Resolution – Aspect ratio
1440×900—–16:10
1680×1050—–16:10
1920×1200—–16:10
2560×1600—–16:10
3840×2400—–16:10
7680×4800—–16:10

Bridging Amps and Ohm Loads

Posted by & filed under Audio, Electronic, Hardware.

Amplifier bridging is simply using 2 channels of an amplifier to drive a common load. For 2 channel amplifiers, one left signal and one right signal is used to drive a mono speaker load. Keep in mind that mono and bridging are not necessarily the same. Mono means that there’s only one output signal. There could be more than one speaker but each speaker will have the same output. Bridging means that you are using more than one source of power to drive a load (speaker). The sources of power are one each output from either channel of the amplifier. A long time ago, amplifiers had signal on the positive output speaker terminals only. To bridge one of those amplifiers, you’d have to use some means to invert the signal on one channel (remember the old ‘bridging modules’ for Orion amplifiers?). Today’s bridgeable amplifiers have an inverted channel as part of their design. For many amplifiers, the left positive and right negative are are the signal outputs. A few use the left negative and the right positive. Others still (mostly mono amplifiers that are to be used in bridged pairs) require that you choose 0° or 180° via a switch to invert the signal.

www.bcae1.com/bridging.htm

Configuring Wireless in Windows thru the Command Line

Posted by & filed under Networking, WiFi, Windows.

So using the netsh wlan command allows us to manipulate the various properties of a wireless connection. Other potentially cool stuff:

  • netsh wlan set tra yes – Enables wireless debug traces in %WINDIR%\tracing\wireless
  • netsh wlan
  • Creating/moving wireless profiles quickly

    • There is more, but this is prolly what I need to use when I write a app for a client to view wireless connection status.

    Source: www.windowsnetworking.com/articles_tutor…