During the Dell Storage Forum in Paris, I’m have invited to be part of something called the ” Think Thank ” discussion,
where basically Partners , Customers and Dell brainstorm regarding several topics within the IT industry.
For the discussion moderation we had Simon Robinson, Research Vice President of 451 Research and representing partners & customers I was privileged to share ideas with
- Fabio Rapposelli, @fabiorapposelli
- Andrew Mauro, @andrea_mauro
- Barry Coombs, @virtualisedreal
- Didier Van Hoye, @WorkingHardInIT
- Rasmus Haslund, @haslund
- Charles Gillanders, @cgillanders
- Andreas Erson, @ersontech
- Tom Heskestad, @hypervfan
I was there “officially” with a Blogger hat on
, but I represented a end-customer / IT Architect perspective.
The conversation started off with an introduction of all the folks present at the table, and we had a nice mix of expertise around us , like storage administrators (obviously ! ), to systems architects, systems integrators.
Several topics were part of the discussions regarding Chargeback or cost-awareness also known as IT Show Back , systems/solutions convergence strategy , relationships between Dell, Partners (a reseller must deliver a very clear Value Added pitch or else is pointless) to trust towards/from the Vendor , manageability , roadmaps , build IT your own vs buy IT pre-configured , etc…
Quite interesting is the fact that despite the significantly different backgrounds we all have , the key concerns/ideas around all of us, were:
- the traditional storage model vs the so called software defined storage with their good and bad things
- flash …everyone understands flash and it would fix a lot of problems, however the problem is still the, high, cost
- scale-out vs scale-up approach
- who’s now in control ? the software vendors or the hardware vendors ?
- storage moved away from servers to shared environments, and now is going back to server again ?
- backup & restore .. how to deal with the fact that no one deletes data and we must be able to backup it up and restore it if needed
- bit expectations towards Windows 2013, HyperV 3, SMB3.0
- deduplication as an option we want vs a “necessary evil”
- Dell’s ability to execute their strategy based on buying a significant amount of companies, while keeping the support level as good as (if not better) and being able to integrate their IP rather than just sell it as a new product
- FcOE vs iSCSI (always a fun topic!)
- Management tools (or lack of )
- Cloud…we all agree that we use it , but we don’t adopt it ! 🙂
At the end of the discussion we all agree that there’s no technology that can meet everyone’s needs, and at the end of the day the most import thing is to make a solid design for your environment and see what’s the right tool for the job. The main key conclusion is that any business, independently from their size and area of business, must see IT as a business enabler and not as a cost center, and IT staff may need to learn a bit more of Business Politics 🙂
I honestly had a very pleasant time during the debate, and I look forward for the next opportunity to have a new discussion , to see if and how the discussed concerns have been mitigated/minimized.
As we all know that one image worths more than 1000 words here’s some , great, topics captured and illustrated during the session .
The session had a live stream, so you can check them out !
Based on the Dell Operating System Support Matrix this raid controller is only supported with Redhat / CentOS 5.5 , and this was a a major issue .
After digging around (Google is really your friend !) i was able to fix the problem by creating a device driver to be loaded during the installation of RedHat / CentOS 5.2 , either x86 or x86-64 bits platforms.
In short i had to download the already compiled driver available at the Supermicro support site , remove the signature from the driver and boot the system using the dd as an argument for the installer.
and dmesg will output something like
Have fun !
To make use of the driver follow this instructions :
Installing the driver on a Red Hat Enterprise Linux / CentOS system
Perform the following steps to install RHEL/CentOS (version 5)
using the Driver Update Disk (DDU):
1 Boot normally from the RHEL/CentOS installation media.
2 At the command prompt, type:
> linux dd
3 When the install prompts for a driver diskette, insert the driver update
disk (DUD) prepared earlier and press <Enter>.
4 Complete the installation as directed by the installation program.
– iDRAC –
When you use iDrac Enterprise it’s also possible to mount a driver image to a floppy disk, just like
it’s done for mounting an ISO file .
– Create a Driver Update Disk (DDU) —
Using a USB key:
Copy the driver image file(*.img or *.dd) into a USB key.
Using a USB floppy device :
1. Put a floppy disk into a USB floppy device, and plug the device into a USB slot of the system under test.
use “dmesg” to find out which device this USB floppy is enumerated to (for example, sdb, sdc, etc).
2. Then tranfer the driver image to the floppy:
Use > dd if=<image_file_name> of=/dev/sdx
Here the /dev/sdx is the device name found from dmesg in the above step.
3. Umount the USB floppy device before unplug it (preferred).
Using system floppy disk slot:
Insert a floppy disk into the system floppy disk slot, then at the prompt:
# dd if=<image_file_name> of=/dev/fd0
On most systems, the floppy drive is designated by the /dev/fd0 special file.
It is prefferred to execute the dd command before the floppy is mounted.
Module signature removal procedure :
I just fixed it. The signature should be removed from the kernel module:
# download mpt2sas-02.00.00.00-1-rhel5.3.x86_64.dd from ftp.supermicro.com
# mount driver disk as loop device
mount -o loop mpt2sas-02.00.00.00-1-rhel5.3.x86_64.dd /mnt/loop
# extract modules.cgz
mkdir -p /tmp/dd/cpio
gzip -dc /mnt/loop/modules.cgz > modules.cpio
cpio -idumv < ../modules.cpio
# check if the module is signed
readelf -S scsi_transport_sas.ko | grep module_sig
# remove signature from module
objcopy -R .module_sig scsi_transport_sas.ko
# check if signature was removed
readelf -S scsi_transport_sas.ko | grep module_sig
# rebuild modules.cgz
find . | cpio -ovBc > ../modules
gzip -9 -S .cgz modules
cp -f modules.cgz /mnt/loop
# unmount driver disk