-------------------------------BCCD ISO TESTING REPORT------------------------------------------------
=====Author:             Mobeen Ludin (example)
=====Date Generated:     Dec 07 /2011    (example)
=====Date Tested:        Dec 08 /2011
=====Release revision#:  r?????
-------------------------------------------------------------------------------------------------------
====================== Whats new in this ISO? ============================
This iso was generated to fix some of the network issues that new BCCD users were having. 
Skylar made the changes with regards to Karl, and Brad's comments and suggestions on the bug. 
In this ISO (only 64-bit) MPI is working, Bluetooth is working ok. 

-- Test suit was not working 

-- Network/pxe booting was not working 

-- Liberating failed on 1 test which is a race condition.... emails for more info on bug. 

---------------------------------------------------------------------------

==============Downloading and Making Bootable USB:=========================

First Downloading the ISO form a repository on earlham cs cluster:

//first downloading the script for making bootable USB drive 
$ svn co svn+ssh://mmludin08@cluster.earlham.edu/cluster/svnroot/bccd-ng/trunk/bin BCCD
$ cd BCCD 
//This is where the the script exits for making bootable USB from BCCD ISO

//Download the ISO from appropriate links
$ sudo wget http://cluster.earlham.edu/bccd-ng/snapshot/bccd_latest.amd64.iso.md5
$ sudo wget http://cluster.earlham.edu/bccd-ng/snapshot/bccd_latest.amd64.iso

CheckSum Report: 
//To see if the ISO was downloaded 100% correctly
$ md5sum bccd_latest.amd64.iso
f740590493b49ef3f18b90fa265c21bc  bccd_latest.amd64.iso

$ cat bccd_latest.amd64.iso.md5 
MD5 (bccd_latest.amd64.iso) = f740590493b49ef3f18b90fa265c21bc 

NOTE:if can compare by reading: copy both results to two seperate files. 
And run diff on them. It will tell you the difference if exist. 

----------------------------------
Second Making Bootable USB:

The next step will be to insert the 4G USB drive (the Intel one) into
the machine, wait a couple seconds, and then do

$ sudo ./build_bootable_USB.sh /dev/sdb bccd_latest.amd64.iso

This is the usual procedure for running the script.  The thing that
can vary is /dev/sdb; usually this will be the location of the USB,
but if there is another USB connected it might actually be /dev/sdc. 

----------------------------------------------------------------------------

====================== ISO TESTING REPORT ============================
-----LIVEMODE --From USB ---:
           --- 32-bit: N/A
           --- 64-bit 
	Test_suite: Failed.
	$ bccd-nic-setup 
		[Generated the same errors as the last time:] 
	Not ok 0 - Removing  /var/lib/dhcp/dhclient.leases.
/bin/bccd-nic-setup: ERROR: run_nic_dhcp: Couldn't remove /var/lib/dhcp/dhclient/leases/
at /bin/bccd-nic-setup line 43
	
	$ sudo /bin/bccd-reset-network 
		Worked fine: and generated no errors. 
	
	at /bin/bccd-nic-setup line 65
	ok 11 - Starting networking
	Configuring network interfaces...done.
	Configuring network interfaces...done.
	Starting ISC DHCP server: dhcpd.
	
	Liberating BCCD
	$ sudo perl /root/liberate.pl --libdev /dev/sda
	 	Liberation failed on test 8. same way as reported before. 
	
[Got this error: ERROR START]

not ok 8 - Set LVM PV partition type
WARNING: DOS-compatible mode is deprecated.  It's strongly recommended
to switch off the mode (command 'c') and change display units to
sectors (command 'u').

Command (m for help): Partition number (1-4): Hex code (type L to list
codes): Changed system type of partition 2 to 8e (Linux LVM)

Command (m for help): The partition table has been altered!

Calling ioctl() to re-read partition table.

Warning: Re-reading the partition table failed with error 16: Device
or resource busy.
The kernel still uses the old table.  The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.

...
Passed 77 out of 78 total tests.
[ERROR END ]

-------------------------------------------
----LIBERATED -- From Hard Disk--
           --- 32-bit: N/A
           
	   --- 64-bit   
    -  After Liberation when i restarted, it got hanged up at a point. and message said: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. 
		(i.e., without -a or -p options)
	fsk died with exit status 4 
	failed (code 4). 
File system check fialed. A log is being saved in /var/log/fsk/checkfs if that location is writable. please repair the file system manually. ..failed!
A Maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ...(WARNING)
Give root password for mainntenance
or type control-d to continue: 

    -  I entered control-d, bccd user started with gui interfce. 

    - PXE-Booting is working now. On my LittleFe, all the six nodes are up and GalaxSee is running on them. 
    
    - I will work on the Test_suite tomorrow (Dec 8/2011). 
    
    - openmpi, mpich2 modules worked fine. 
   
    - When i compiled the Cuda module, I got the error for symbolic link missing:
Here is the compiler error:
   /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.4.5/libstdc++.so when searching for -lstdc++

Here is the soft-link that fixes the problem:
               $ sudo ln -s /usr/lib32/libstdc++.so.6 /usr/lib32/libstdc++.so
--------------------------------------------------------------------------------

============ Final: Comments/Suggestions/Objection/Question/?/? =================
   -  Bluetoot is still picking up all the bluetood devices around. 
   -  I think we should also work on the 32-bit mpi
   
 P.S. Mores notes to come on this. 
-----------------------------------------------------------------------------