Wednesday, March 30, 2011

Re: Pogoplug V2 Hardware Description

Memory can be found in MB using:

 [root@Plugbox Vault]# free -m              total       used       free     shared    buffers     cached Mem:           247         31        215          0          3         13 -/+ buffers/cache:         15        231 Swap:            0          0          0 [root@Plugbox Vault]#  


On Wed, Mar 30, 2011 at 1:23 PM, Stan Hughes <hughes.stan@gmail.com> wrote:

General description of plug type hardware.


Memory:  256M
Internal Storage:  128M

Description of Pogoplug V2 hardware.


External

  • 1 Front-Facing USB 2.0 Port
  • 3 Rear USB 2.0 Ports
  • 1 Gigabit Ethernet Port
  • Regular Power cable (Not a brick)
  • Power/Activity LED

Internal

  • 256MB RAM
  • 128MB NAND (32MB root partition, 92MB mtdblock3 partition)
  • Marvell Sheeva CPU, 1.2GHz
  • Serial port

iRODS seems to be running pretty well on this.  Run as server only without iCAT.




Pogoplug V2 Hardware Description


General description of plug type hardware.


Memory:  256M
Internal Storage:  128M

Description of Pogoplug V2 hardware.


External

  • 1 Front-Facing USB 2.0 Port
  • 3 Rear USB 2.0 Ports
  • 1 Gigabit Ethernet Port
  • Regular Power cable (Not a brick)
  • Power/Activity LED

Internal

  • 256MB RAM
  • 128MB NAND (32MB root partition, 92MB mtdblock3 partition)
  • Marvell Sheeva CPU, 1.2GHz
  • Serial port

iRODS seems to be running pretty well on this.  Run as server only without iCAT.



Tuesday, March 29, 2011

2 TB Fantom Drive for $90


Server w/o iCAT Problesm

https://confluence.crbs.ucsd.edu/display/CRBS/iRODS+Troubleshooting#iRODSTroubleshooting-I%27mgetting%22rcAuthResponsefailedwitherror826000CATINVALIDAUTHENTICATION%22inthelog.What%27swrong%3F

Figuring Out Devices and Storage on the Pogoplug

On a normal Pogoplug V2 4 USB storage devices looks like this:

-bash-3.2# df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/mtdblock2           32768     15872     16896  48% /
none                    128004        12    127992   0% /tmp
/tmp/.cemnt/sda1     1953512000    125684 1953386316   0% /tmp/.cemnt/mnt_sda1
/tmp/.cemnt/sdb1     1953512000    125732 1953386268   0% /tmp/.cemnt/mnt_sdb1
/tmp/.cemnt/sdc1     1953512000    125732 1953386268   0% /tmp/.cemnt/mnt_sdc1
/tmp/.cemnt/sdd1     1953512000    125732 1953386268   0% /tmp/.cemnt/mnt_sdd1

OK, this makes sense.

-bash-3.2# /sbin/fdisk /tmp/.cemnt/sda

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /tmp/.cemnt/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

          Device Boot      Start         End      Blocks  Id System
/tmp/.cemnt/sda1               1      243201  1953512001   7 HPFS/NTFS

OK, it see the USB devices.  Now I have to get it to mount them.  I can do that later.

[root@Plugbox ~]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 05dc:a761 Lexar Media, Inc. 
Bus 001 Device 004: ID 13fd:1340 Initio Corporation Hi-Speed USB to SATA Bridge
Bus 001 Device 005: ID 13fd:1340 Initio Corporation Hi-Speed USB to SATA Bridge
Bus 001 Device 006: ID 13fd:1340 Initio Corporation Hi-Speed USB to SATA Bridge



Monday, March 28, 2011

Getting Disk Info

 
 df -h
 fdisk -l hdparm -i device &#40;probably /dev/hda&#41;
 Using the 'sudo hdparm -i /sda' command I was able to get the following data:
 /dev/sda:   Model=WDC, FwRev=01.04A01, SerialNo=WD-WXEY07X26552  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50  BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=312581808  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}  PIO modes:  pio0 pio3 pio4   DMA modes:  mdma0 mdma1 mdma2   UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5   AdvancedPM=yes: unknown setting WriteCache=enabled  Drive conforms to: Unspecified:  ATA/ATAPI-1,2,3,4,5,6,7   * signifies the current active mode 
 However, this didn't work for the new Fantom Drives.  I get the following error instead:
 /dev/sdb:  HDIO_DRIVE_CMD(identify) failed: Invalid exchange  HDIO_GET_IDENTITY failed: Invalid argument 

I would guess that this has something to do with it being a USB drive.

Will this be fixed by USB3?

How did linux know if was a Fantom Drive?

USB Info

Using 'lsusb --verbose' I still don't see anything that would enable to ID drive.




Friday, March 18, 2011

Dedicated Lin Broadband Speeds and Internet2



T-1 :  1.544 megabits per second (24 DS0 lines)
T-3 :  43.232 megabits per second (28 T-1s)
OC-3 : 155 megabits per second (100 T-1s)
OC-12 622 megabits per second (4 OC3s)
OC-48 - 2.5 gigabits per second (4 OC12s)
OC-192 - 9.6 gigabits per second (4 OC48s)


IPv6 Category : 9.08 gigabits per second
IPv4 Category : 8.80 gigabits per second


Crash Course for iRODS Commands



I had to refresh myself today to do some simple work in iRODS.

Main command is 'iadmin'
Main command for environment is 'ienv'
Main command for starting and stopping is 'irodsctl'

This was enough to get me through.

Setting Up Environment Variables


Need to setup my environment to use the iRODS icommands and control command.  Added the following lines to the bottom of the ~/.bashrc file.

# add poath for iRODS icommands
export PATH=$PATH:~/iRODS/clients/icommands/bin

# add pa;th for iRODS mangment commands
export PATH=$PATH:~/iRODS

(note:  I replace implicit path '~' with the actual)

Fantom 2TB Green External Hard Drive $90


http://www.circuitcity.com/applications/searchtools/item-details.asp?EdpNo=5384379&pagenumber=2&RSort=1&csid=ITD&recordsPerPage=5&body=&SRCCODE=CCDGOOKEY&cm_mmc_o=mH4CjC7BBTkwCjCECjCE

Circuit City is having a sale.


Thursday, March 17, 2011

Steps to Building a Pogoplug iRODS: Prepare USB Boot Disk

The notes are a little sparse on the Pogoplug site.

Starting at this link:


I believe that I am working with a Pgogoplug V2.

The Pogoplug Pro stuff using Linux kernel version 2.6.31.6.

The Pogoplug V2, Pogoplug Biz, and Pogoplug V1 using Linux kernel version 2.6.22.18.

This doesn't match what I read on the web.


Pogoplug v2 (Pink/Gray)


This is a real nice page and really what I need.


Nice page on connecting to the SSH.  Seems to be up to date.  Yes, the page was updated Feb 10, 2011.


OK, part of this is to load the U-Boot boot loader onto the Pogoplug.

The format of the USB drive is being done from the Pogoplug itself.
.
Instead of creating the USB boot drive from the Pogoplug, I am going to be doing it from my linux box

You can't tell that the pogoplug processes have been killed.

What is the current system?

Linux Pogoplug 2.6.22.18 #44 Mon Aug 10 12:57:36 PDT 2009 armv5tejl unknown

Didn't add the boot loader.

Trying to reboot.

It doesn't seem to be coming back.

Testing the drive on my linux box.

Can't really test ARM code on an Intel box :-)

Pacman is the