Unix Revolution

I don't necesarilly hope that I will need this procedure again soon... but I get the feeling I will need it someday and I had a hell of a time figuring this out this evening in a pinch. Power up the phone by pressing the VOL UP + VOL DOWN KEY together + PWR KEY . The device will enumerate with different BOOT OPTIONS Use the VOL DOWN Key to SCROLL and VOL UP Key to SELECT Select Recovery The device will start up with Motorola logo and power up to  a little Android man logo with Exclamation mark Press the VOL UP and VOL DOWN Key together at this screen The device will display BLUE Text on a Black background . Use the VOL DOWN Key to scroll DOWN and the PWR Key to SELECT the option desired . In this case , press the VOL DOWN key till the Wipe data / factory  reset  is selected and press the PWR key to confirm the selection . Use the VOL DOWN key again to select YES - delete all user data and press the PWR key to CONFIRM . The device will then start performing the

every past does not have the same future, but every future has the same past Your finest work Is not your proudest moment When history repeats itself and the people from the past still do not learn

Red Hat 5.6 running on VMware vSphere. Grab a snapshot before messing with any of this. This procedure is slightly different if you are messing with /dev/sda (if that's where your / is) # Determine what VGs are assigned to the disk you are messing with... #   in this case... /dev/sdb for PART in `fdisk -l /dev/sdb | grep ^/dev | awk '{ print $1 }'`; do pvdisplay $PART | grep VG\ Name | awk '{ print $3 }' | sort -u; done vg_test # Figure out what volumes are mounted on that VG df -h | grep SCOREDATA umount /SCORE_Data lvchange -a n /dev/SCOREDATA/SCORE_Data vgchange -a n SCOREDATA blockdev --rereadpt /dev/sdb fdisk -u /dev/sdb # n p 2 t 8e w partprobe /dev/sdb blockdev --rereadpt /dev/sdb fdisk -l /dev/sdb vgchange -a y SCOREDATA mount -a pvcreate /dev/sdb2 vgcreate SCOREARCH /dev/sdb2 FREEPE=`pvdisplay /dev/sdb2 | grep Free\ PE | awk '{ print $3 }'` echo $FREEPE lvcreate -l+${FREEPE} -nSCORE_Archive SCOREARCH mkfs /dev/SCOREARC

WORK IN PROGRESS - the more rocks I overturn, the more data I find that I am missing :-( I'm gathering information from a number of sources and I have not found a source that covers this entire topic.  You can find additional information elsewhere, if you need more detailed info. I anticipate this post will contain quite a bit of data at some point. This... is an example of the multipath device you would see from Red Hat.  Notice it is similar to your standard WWN, but not absolutely the same. # multipath -ll -v2 | tail -5 360060e800571c900000071c9000005f7 dm-5 HITACHI,OPEN-V size=200G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active   |- 5:0:0:0 sdb 8:16  active ready running   `- 6:0:0:0 sdh 8:112 active ready running Let's break this down. 36 0060e8 00 5 71c9 00 000071c9000005f7 36 - Vendor Code (For some reason this is NOT 50, as expected) 0060e8 - HDS OUI 00 5 - Front End Port

In our environment (which I have inherited) there were 2 profiles which would be displayed as a kickstart profile, but the had a red stop sign with an X in the column that said if it was RHN Satellite Managed? [root@prhnsat01 profiles.d]# cobbler list distros:    ks-rhel-i386-client-5    ks-rhel-i386-client-5-u1    ks-rhel-i386-client-5-u1xen    ks-rhel-i386-client-5-u2    ks-rhel-i386-client-5-u2xen    ks-rhel-i386-client-5-u3    ks-rhel-i386-client-5-u3xen    ks-rhel-i386-client-5-u4    ks-rhel-i386-client-5-u4xen    ks-rhel-i386-client-5-u5    ks-rhel-i386-client-5-u5xen    ks-rhel-i386-client-5-u6    ks-rhel-i386-client-5-u6xen    ks-rhel-i386-client-5xen    ks-rhel-i386-server-5    ks-rhel-i386-server-5-57    ks-rhel-i386-server-5-57xen    ks-rhel-i386-server-5-58    ks-rhel-i386-server-5-58xen    ks-rhel-i386-server-5-59    ks-rhel-i386-server-5-59-rc-30    ks-rhel-i386-server-5-59-rc-30xen    ks-rhel-i386-server-5-59xen    ks-rhel-i386-server-5-u1

vxtree.pl - a perl script to parse out the command line output of numerous iterative Vertias commands into a easy-to-read display of data.  I would do real work and validation with the vxassist/vxdisk/vxprint commands, but it was nice to have this command, just to double check my work. NOTE: I also found this on a brocade site listed as "vxdisplay".  However, their copy is the "vxtree.pl" command I had grown to love when I was working on Veritas day-in and day-out. Written by Richard Quixley JPMorgan, back in 2003!!! #!/usr/bin/perl # # vxtree.pl - provides a tty version of the "view layout" option in vmsa. # best viewed in wide xterm # # Aug 2003 - Richard Quixley JPMorgan # # # Identifies the following volume types: # # 1. concat # 2. stripe = (raid-0) # 3. mirror = (raid-1) # 4. raid = (raid-5) # 5. mirrored-stripe = (raid-0+1) # 6. [layered volume] - striped-mirror ("striped-pro") = (raid-1+0