MD3000 firmware/NVSRAM update to support Linux multipath?

poweredgemark@gmail poweredgemark at gmail.com
Mon Jan 21 08:21:19 CST 2008


On Jan 16, 2008 10:15 AM, Simon Burrows <Simon.Burrows at haysystems.com>
wrote:

> Hi,
>
> I have an MD3000 hooked up to a 2900 (running RHEL 4) via a PERC 5/E
> card (one cable to each MD3000 controller). It recently came to light
> that the firmware revision the MD3000 is using does not support Linux
> multipath setups correctly and Dell have advised that we update to the
> firmware contained in R174600 (the latest version). Now, the server in
> question is live and we'd like to keep downtime to a minimum but in
> trying to get a handle on what to expect during the update process, I've
> found the supplied documentation somewhat confusing.
>
> Some basic facts about our current setup:
>
> uname -a:
> "Linux dbase 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:00:54 EDT 2005 x86_64
> x86_64 x86_64 GNU/Linux"
> RDAC version 09.01.B6.16 [installed from source].
> mptlinux, 3.02.83.12, 2.6.9-22.ELsmp , x86_64: installed (original_module
> exists) [installed using DKMS].
> MD3000 RAID controller module firmware version: PkgInfo 06.17.77.60
> MD3000 NVSRAM version: N133X-617890-015
>
> My current best guess at the update process (the update will be done
> from the host connected to the MD3000), partly culled from the Dell
> documentation is:
>
> 1. Stop I/O to the RAID enclosure (stop processes, unmount file
> systems).
>
> 2. Use the MD Storage Manager to "Gather Support Information".
>
> 3. Using the MD3000 Resource CD, run a pre-requisite check.
>
> 4. Make any updates that the pre-requisite check identifies.
>
> 5. Change the bootloader entry in /boot/grub/menu.lst to use the
> original default initrd - without mpp support.
>
> 6. Uninstall current RDAC Multipath driver - run "make uninstall" from
> the linuxrdac source directory.
>
> 7. DO NOT REBOOT. Rebooting may cause DATA corruption.
>
> 8. Update the version of MD Storage Manager installed on your host
> server using the Resource CD.
>
> 9. Using MD Storage Manager, update the MD3000 RAID controller firmware
> and NVSRAM by selecting Support->Download Firmware->Download RAID
> Controller Module Firmware. Select appropriate file locations for both
> the Firmware as well as NVSRAM update packages and click Transfer. When
> a successful download confirmation message is displayed, the firmware
> and NVSRAM have been updated.
>
> 10. Restart I/O (mount file systems, start processes).
>
>
> Step 7 concerns me: I found ominous references online regarding the
> dangers of loading and unloading RDAC modules with modprobe etc. and I'm
> not sure what to expect in this and step 8. I don't intend on manually
> fiddling with any RDAC stuff, but warnings like this are always
> concerning. I suppose it boils down to whether step 8 will cause updated
> (preferably DKMS'd RDAC drivers to be installed and once that's complete
> is everything supposed to be A-OK? I don't mind rebooting if necessary.
>
> Thanks and regards,
>
> Simon Burrows
> Hay Systems Limited
>
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom it is
> addressed. If you have received this email in error please notify Hay
> Systems Limited.
>
> Hay Systems Limited is a company incorporated under the Companies Acts
> (Registered Number SC201362) having its principal place of business at
> Watermark, Alba Campus, Livingston, EH54 7EG, UNITED KINGDOM.
>
> Opinions, conclusions and other information in this message which do not
> relate to the official business of Hay Systems Limited shall be
> understood as neither given nor endorsed by it.
>
>
>
The readme tends to suggest that it will install the driver for you, however
in our experience this didn't happen. Even selecting option 4 in the menu
didn't do anything. All I did was a make uninstall of the old driver and
then installed the RPM manually. The make uninstall nor the rpm will unload
your current driver on you, therefore after the install you should make sure
the new initrd is in /boot (note they aren't calling it mpp- anymore, it
backs up and overwrites your old initrd), and then reboot.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20080121/00ad45f2/attachment.htm 


More information about the Linux-PowerEdge mailing list