[Linux-PowerEdge] DSU Repository: September 2016

Sashi_K at Dell.com Sashi_K at Dell.com
Tue Oct 4 08:02:36 CDT 2016

Dell - Internal Use - Confidential


Can you please run the below steps to collect logs:

1.       Inventory collector binary will be located at /usr/libexec/dell_dup

2.       Execute inventory collector binary with -outc option (example: /usr/libexec/dell_dup/invcol_8G4DV_LN64_16_10_00_816_A00 -outc = /root/inventory.xml).

3.       Extract inventory collector by running the command  "/usr/libexec/dell_dup/invcol_8G4DV_LN64_16_10_00_816_A00 --extract invcol_ext_dir" (directory may need to be created for extracting the inventory collector).

4.       Change to the  extracted directory by running "cd invcol_ext_dir".

5.       Go to the location lx64\cmie\MaserAppsIE  inside   folder invcol_ext_dir.

6.       Run the command "./MaserIE -i -d > inv.xml" and collect the logs "inv.xml, Debug.log, SMAL_DBG.log"

Please attach the inventory.xml, Debug.log, and SMAL_DBG.log

Thank you,

Sashi K
Software Dev Senior Engineer
Dell EMC | PG Enterprise

From: Chris Cooke [mailto:cc at staffmail.ed.ac.uk]
Sent: Thursday, September 29, 2016 6:11 PM
To: V, Sriraj Ch_S <Sriraj_Ch_S_V at Dell.com>
Cc: linux-poweredge-Lists <linux-poweredge at lists.us.dell.com>; Moharla, Kalyan <Kalyan_Moharla at DELL.com>; Manekar, Salil <Salil_Manekar at DELL.com>; K, Sashi <Sashi_K at Dell.com>
Subject: Re: [Linux-PowerEdge] DSU Repository: September 2016


Firstly, thank you for DSU!  It's very popular here because it has made firmware updates so much easier to find and to apply.

Secondly, I'd like to report a problem with DSU v1.3.1.
After running it (e.g. with 'dsu --preview --non-interactive') two read-only mounts are left on the machine.
After 'dsu' has finished, the output of the 'mount' command has these extra two lines:

/dev/sdg on /tmp/SECUPD type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/sdh on /tmp/SECUPD type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)

If I then run 'dsu' a second time I get two more mounts of /tmp/SECUPD, making four in all:

/dev/sdg on /tmp/SECUPD type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/sdh on /tmp/SECUPD type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/sdi on /tmp/SECUPD type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/sdj on /tmp/SECUPD type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)

The above lines are from the 'mount' command on a PowerEdge R710 running Scientific Linux 7.2.
On a similar machine running Scientific Linux 6.8 the 'mount' output includes two lines like these for each run of 'dsu':

/dev/sdc on /tmp/SECUPD type vfat (rw,shortname=mixed)
/dev/sdd on /tmp/SECUPD type vfat (rw,shortname=mixed)

I don't remember this happening with previous versions of DSU.
It's inconvenient for us to have these read-only mounts left behind, not least because our hardware monitoring system flags an alert whenever it finds one.

Would it be possible for the /tmp/SECUPD mounts to be unmounted at the end of the 'dsu' run please?

Chris Cooke
School of Informatics, University of Edinburgh.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20161004/65634bae/attachment.html 

More information about the Linux-PowerEdge mailing list