http://blog.gmane.org/gmane.linux.hardware.dell.poweredge hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44206 <pre>Hi, I'm a bit worried by the temperatures reported on a dell R620 fitted with two Xeon E5-2690. Under load, both ipmi and psensor show that max temp reached is about 85°C (for core and processor) Googling around for the proc specs, I found various max operating temperature 85°C, 88.2°C, and a Tcase of 65°C, which doesn't help a lot. The fans seem to work correctly with speed variation according to the temperature. Inlet temperature is 25°C. Can anyone share its temperatures for comparison ? Any thought on my data ? _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> fribes 2013-06-18T07:44:43 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44202 <pre>I was able to sync the rhel5 channel but rhel6 gives me the error below and the Web page referenced gives a 404. Is dell-satellite-sync broken or is there a problem with linux.dell.com? [root&lt; at &gt;rhnsat ~]# /usr/bin/dell-satellite-sync --server-actions-only --user removed --satserver rhn.cssd.pitt.edu --channel rhel6 -v Password: Checking base channel 'rhel-x86_64-server-6' Channel 'rhel-x86_64-server-6' found. Checking child channel 'Dell OM on platform_independent for rhel-x86_64-server-6' Creating channel... + Creating temporary channel: dell-om-platform_independent-rhel-x86_64-server-6-tmp + Cloning temporary channel into real channel: dell-om-platform_independent-rhel-x86_64-server-6 + Deleting temporary channel: dell-om-platform_independent-rhel-x86_64-server-6-tmp Creating repo for channel... Associating repo to channel... Scheduling repo sync... Channel 'Dell OM on platform_independent for rhel-x86_64-server-6' created. Checking base channel 'rhel-i386-server-6' Channel 'rhel-i386-server-6' found. Repo requested 'http://linux.dell.com/repo/hardware/latest/platform_independent/rh60' does not exist. </pre> Jeff White 2013-06-17T14:10:42 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44195 <pre>Hello, I am trying to install OpenManage 7.1 on Debian wheezy (7.0) by following instructions: http://linux.dell.com/repo/community/deb/latest/ Unfortunately when I try to do an "apt-get install srvadmin-all" I get the following error messages: Reading package lists... Done Building dependency tree       Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies:  srvadmin-all : Depends: srvadmin-base (&gt;= 7.1.0) but it is not going to be installed                 Depends: srvadmin-storageservices (&gt;= 7.1.0) but it is not going to be installed                 Depends: srvadmin-webserver (&gt;= 7.1.0) but it is not going to be installed                 Depends: srvadmin-rac4 (&gt;= 7.1.0) but it is not going to be installed                 Depends: srvadmin-rac5 (&gt;= 7.1.0) but it is not going to be installed                 Depends: srvadmin-idrac (&gt;= 7.1.0) but it is not going to be installed                 Depends: srvadmin-idrac7 (&gt;= 7.1.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Does anyone have an idea why it doesn't let me install OM? Thanks! Regards, M.L. </pre> ML mail 2013-06-13T15:09:58 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44185 <pre>Has anyone successfully configured em1 &amp; em3 to be slaves to bond0 in redhat/centos 6.2+? With the config below, on boot, interfaces em1 &amp; em3 are not ‘enslaved’ to bond0, leaving it unconnected. If I run `ifenslave bond0 em1 em3` the bond0 interface does come up (but any change to em3 will fail saying the MAC address does not match). I found that if I remove the HWADDR from ifcfg-em1 &amp; 3, it does not configure those interfaces at all, saying, “em1 [or 3] does not seem to be present, delaying initialization.” Is there something I am missing? I have tried with miimon and the result is the same. /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE="bond0" BOOTPROTO=none NM_CONTROLLED=no USERCTL=no ONBOOT=yes IPADDR=192.168.101.11 PREFIX=24 GATEWAY=192.168.101.1 DNS1=127.0.0.1 DEFROUTE=yes BONDING_OPTS="mode=active-backup primary=em1 arp_interval=60 arp_validate=active arp_ip_target=192.168.101.1,192.168.101.2,192.168.101.5" /etc/sysconfig/network-scripts/ifcfg-em1 DEVICE="em1" BOOTPROTO=none NM_CONTROLLED=no USERCTL=no ONBOOT=yes Master=bond0 Slave=yes HWADDR=90:b1:1c:2c:8f:0f /etc/sysconfig/network-scripts/ifcfg-em3 DEVICE="em3" BOOTPROTO=none NM_CONTROLLED=no USERCTL=no ONBOOT=yes Master=bond0 Slave=yes HWADDR=90:b1:1c:2c:8f:11 Thanks, -- Benjamin Carrell bcarrell&lt; at &gt;connexionpoint.com _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> Benjamin Carrell 2013-06-11T00:01:51 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44180 <pre>In /23 subnetting, .255 and .0 at the top/bottom of the first /24 (respectively) are infrequently assigned but are perfectly valid host addresses. However, the iDRAC6 AJAX, the BIOS TUI, and the RACADM code all respectively reject them. Seriously, the underlying GNU/Linux on the iDRAC6 would happily accept this subnetting. Ironically I think we're looking at three different bugs in the different interfaces that are assuming that /24 subnetting. foo# racadm config -g cfgLanNetworking -o cfgNicNetmask 255.255.254.0 Object value modified successfully foo# racadm config -g cfgLanNetworking -o cfgNicIpAddress 10.XXX.162.255 ERROR: Failed to set the object value. Possible reason may be that Local Configuration using RACADM is disabled. foo# racadm config -g cfgLanNetworking -o cfgNicIpAddress 10.XXX.163.0 ERROR: Failed to set the object value. Possible reason may be that Local Configuration using RACADM is disabled. foo# racadm config -g cfgLanNetworking -o cfgNicIpAddress 10.XXX.163.1 Object value modified successfully This is an erroneous failure. /23 subnetting is very popular in enterprise LOM VLANs. It would be very difficult to write policy rules for automated IP address allocation system to skip over certain IPs in a pool based on subnetting and vendor MAC OUI Prefix conditions. Is there anyone on the Dell GNU/Linux team that can FWD this over to the OpenManage / iDRAC team? I suspect this wont be fixed in iDRAC6 or iDRAC7 since they're EOL, but its not too late to prevent it in iDRAC8? Thanks, -- Brian Seklecki TIA Midrange Systems PNC Financial Services The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender. This message may contain an advertisement of a product or service and thus may constitute a commercial electronic mail message under US Law. The postal address for PNC is 249 Fifth Avenue, Pittsburgh, PA 15222. If you do not wish to receive any additional advertising or promotional messages from PNC at this e-mail address, click here to unsubscribe. https://pnc.p.delivery.net/m/u/pnc/uni/p.asp By unsubscribing to this message, you will be unsubscribed from all advertising or promotional messages from PNC. Removing your e-mail address from this mailing list will not affect your subscription to alerts, e-newsletters or account servicing e-mails. _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> brian.seklecki.nonemployee< at >pnc.com 2013-06-10T13:52:24 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44179 <pre>These are now available at http://linux.dell.com/repo/community/ubuntu/ Note the new location and the new repository format. The new build is also done on Ubuntu 12.04, so the packages are not compatible with Ubuntu 10.04 without pulling in additional dependencies from Ubuntu 12.04. Also included is a "preview" build of the DTK packages (syscfg, raidcfg and dtk-scripts). Please report any issues to this list. --Jared </pre> D. Jared Dominguez 2013-06-10T13:33:52 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44178 <pre>I have a number of PE2850. It has 6 removable SCSI drive slots in the front. Can someone direct me to the documentation that will tell me the slot position mapping to the SCSI Host Adapter, Bus (or channel), Target, LUN numeric values? A typical report from a linux command "cat /proc/scsi/scsi" reports: Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: COMPAQ Model: BF072863BA Rev: HPB6 Type: Direct-Access ANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: COMPAQ Model: BF072863BA Rev: HPB4 Type: Direct-Access ANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: COMPAQ Model: BF072863BA Rev: HPB6 Type: Direct-Access ANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: COMPAQ Model: BF072863BA Rev: HPB6 Type: Direct-Access ANSI SCSI revision: 03 Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: PE/PV Model: 1x6 SCSI BP Rev: 1.0 Type: Processor ANSI SCSI revision: 02 Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: DELL Model: VSF Rev: 0123 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: DELL Model: VCD Rev: 0133 Type: CD-ROM ANSI SCSI revision: 05 You can see the COMPAQ devices- these are the SCSI drives (4 of them) which are inserted in the front slots. How do I know which is which? thanks, rich </pre> Rich Painter 2013-06-10T03:25:06 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44177 <pre>Good Evening- I have an issue with the 6Gbps SAS HBA Controller 07.03.06.00 firmware across 6 individual R720 servers -- all servers are identical and have 2 of the SAS controllers installed. OS: [root&lt; at &gt;server tmp]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.4 (Santiago) SMBIOS-SYS-INFO: [root&lt; at &gt;server tmp]# /usr/sbin/smbios-sys-info Libsmbios version: 2.2.27 Product Name: PowerEdge R720 Vendor: Dell Inc. BIOS Version: 1.6.0 System ID: 0x048C Service Tag: 4C0D4X1 Express Service Code: 9433336357 Asset Tag: 4C0D4X1 Property Ownership Tag: FIRMWARE: Checking 6Gbps SAS HBA Controller 0 Firmware - 07.03.05.00 Available: pci_firmware(ven_0x1000_dev_0x0072_subven_0x1028_subdev_0x1f1c) - 07.03.06.00 Found Update: pci_firmware(ven_0x1000_dev_0x0072_subven_0x1028_subdev_0x1f1c) - 07.03.06.00 Checking 6Gbps SAS HBA Controller 1 Firmware - 07.03.05.00 Available: pci_firmware(ven_0x1000_dev_0x0072_subven_0x1028_subdev_0x1f1c) - 07.03.06.00 Found Update: pci_firmware(ven_0x1000_dev_0x0072_subven_0x1028_subdev_0x1f1c) - 07.03.06.00 When the package is run, it starts the standard update process, but shortly I recieve the following warning on the console in an infinite loop: mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:5215/_scsih_add_device()! The system locks up and requires a forced hard power cycle to clear the error at this point. I have tried running the update through the OMSA firmware tools AND downloading the package directly from the Dell website and recieve the same error. Has anyone else seen anything like this? Are there any logs that I am not aware of that may provide some insight as to what is causing the error? Thanks so much! Justin _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> Justin Pauler 2013-06-09T00:29:58 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44172 <pre> We have taken delivery of some R720 boxes which are going to replace servers running Oracle Application Server under Scientific Linux (Red-Hat EL) 6.4 During the boot sequence it says it finds one quad-core CPU. That is was I expect. But a list of /proc/cpuinfo shows a whole lot more than just 4 CPUs/cores. It shows 0..7 What's up with that? </pre> Howard, Chris 2013-06-07T16:49:52 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44171 <pre>Hi all, Has anybody been able to get OMSA's DSM SA Shared services running properly under Debian Squeeze? Starting the service just results in the service reporting that it is being started with a single thread that keeps on running at 100%. I am running a PowerEdge R905. Cheers, Diederick_______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> Diederick Stoffers 2013-06-07T11:05:31 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44170 <pre>Hi, I have a Dell R820 powered by a Dell UPS Rack 5600W HV. We have monthly routine generator testing in our building meaning the mains is lost for a number of seconds before the generator kicks in. At the point the UPS takes over power provision I get a log full of messages - examples attached. Obviously they end with 'power normal' but is there any explanation? Thanks Stuart Jun 5 07:31:08 cardiogen kernel: CPU30: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU34: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU42: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU2: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU38: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU26: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU10: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU58: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU14: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU62: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU22: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU46: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU6: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU54: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU50: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU18: Core power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU34: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU42: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU2: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU38: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU26: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU10: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU58: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU14: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU62: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU22: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU46: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU6: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU54: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU50: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU18: Package power limit notification (total events = 24) Jun 5 07:31:08 cardiogen kernel: CPU30: Package power limit notification (total events = 24) Jun 5 07:31:09 cardiogen kernel: tg3 0000:02:00.0: em3: Link is down Jun 5 07:31:09 cardiogen kernel: CPU30: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU62: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU14: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU26: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU6: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU46: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU58: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU22: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU2: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU54: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU50: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU38: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU18: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU34: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU10: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU42: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU62: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU14: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU26: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU6: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU46: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU58: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU22: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU2: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU54: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU50: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU38: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU18: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU34: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU10: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU42: Core power limit normal Jun 5 07:31:09 cardiogen kernel: CPU62: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU14: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU26: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU6: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU46: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU58: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU22: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU2: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU54: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU50: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU38: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU18: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU34: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU10: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU42: Package power limit normal Jun 5 07:31:09 cardiogen kernel: CPU30: Package power limit normal _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> Stuart Meacham 2013-06-07T10:57:58 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44168 <pre> Hello, Anyone out there successfully running Dell Openmanage 7.1 on Ubuntu 13.04? Since upgrading ubuntu I'm unable to log into the open manage web interface. Immediately after it tries to authenticate I get a "this webpage is not available" and continue to get that until I restart the openmanage web service. Anyone else having similar issues? Kind regards, Elvar </pre> Elvar 2013-06-06T18:14:51 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44165 <pre> I saw earlier this week that someone was having trouble booting a server from a flash drive. I'm having a similar problem. I have a pair of R420 servers I need to install linux on. I made a bootable flash drive but the machines will not boot from it. I've double/triple checked that the flash drive is bootable. I tried 2 different flash drives. I swapped the keyboard and flash drives around. I was able to install linux with both of them on some Dell workstations. But the servers won't boot from the flash drives. One complication ... I'm blind. I got sighted assistance to tweak the BIOS. I can only repeat what the person told me which is that booting from the front USB ports is enabled. But I do think we may be doing something wrong because we happened to have a Dell service tech in here and he booted it from the USB flash drive in one of the front USB ports. I asked him to tell me the key sequence but he thought it was too complicated for me to repeat. But I'd like to try. I know he started with F11. Can anyone tell me what to press after that? </pre> John G. Heim 2013-06-05T17:34:42 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44156 <pre>Hi I have an almost 5 years old old Dell server with a Perc6/e controller attached to a MD1000 box with 2TB SATA drives in it. It also has a perc6/i and some internal disks. I used to monitor the disks hourly with megacli PDList, and it used to work. I run debian. When I upgraded to squeeze a few years ago I think I saw the problem for the first time. megacli did not work, I used megasasctl instead, and it worked but generated "unexpected sense" messages in the log. So I somehow got omreport to work and wrote some wrapper scripts and left it at that. New I have upgraded to wheezy and installed the latest megacli from http://hwraid.le-vert.net/debian/pool-wheezy/, and it works, I get the output I need. However, when I run it with PDList or -pdInfo -PhysDrv, I get the unexpected sense messages in the log. With -FwTermLog -Dsply -a1 they look like this: 06/03/13 14:10:59: EVT#11662-06/03/13 14:10:59: 113=Unexpected sense: PD 1b(e0x11/s12) Path 500221929641fc44, CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 5/24/00 06/03/13 14:10:59: Raw Sense for PD 1b: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 With megacli adpeventlog getevents -f ~/adpeventlog.txt a0 I get this: de: 0x00000071 Class: 0 Locale: 0x02 Event Description: Unexpected sense: PD 1a(e0x11/s13) Path 500221929641fc43, CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 5/24/00 Event Data:=========== Device ID: 26 Enclosure Index: 17 Slot Number: 13 CDB Length: 10 CDB Data: 004d 0000 004d 0000 0000 0000 0000 0000 0020 0000 0000 0000 0000 0000 0000 0000 Sense Length: 18 Sense Data: 0070 0000 0005 0000 0000 0000 0000 000a 0000 0000 0000 0000 0024 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00 00 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 I am trying to interpret this from http://trac.camsentry.com/wordpress/2013-03/interpreting-unexpected-sense-codes/ but it doesn't make sense to me. 4d would be "LOG SENSE", 0070 DECOMPRESSION EXCEPTION SHORT ALGORITHM ID OF NN and 0005 LOGICAL UNIT DOES NOT RESPOND TO SELECTION. Or maybe I read the numbers wrong. This is the perc6/e controller, perc6/i has a different operation code: CDB: 12 00 00 00 20 00 (meaning INQUIRY,according to http://trac.camsentry.com/wordpress/2013-03/interpreting-unexpected-sense-codes/) where the 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 is still the same. Can anyone provide a better interpretation, and/or tell me: Is this dangerous, should I stop megacli monitoring right away, or is this just noise in the log? Can I somehow get megacli to give me what I want (number of disk online, degraded, failed, and s.m.a.r.t. status if any) without doing this illegal operation or whatever it is? Running megacli with other parameters gives no error. E.g. -AdpAllInfo or -FwTermLog -Dsply. Thanks in advance for enlightening me. Med venlig hilsen / Best regards -- Hanne Munkholm Email: hanne&lt; at &gt;binf.ku.dk Systemadministrator Tlf: +45 35 32 13 49 Bioinformatik-centret Københavns Biocenter, Biologisk Institut Ole Maaløes Vej 5, 2200 København N </pre> Hanne Munkholm 2013-06-03T14:45:47 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44151 <pre>Hello, I have a R410 server with PERC 6/e attached to MD1000 enclosure. The enclosure contains 6 1GB SATA disks. From PERC 6/e integrated BIOS configuration utility I created a RAID5 array group using all 6 disks so I got a total of 5GB of total space. Then I created 3 virtual disks of 1.8GiB, 1.8GiB, 0.9GiB (VD0, VD1, VD2 respectively). I split the RAID5 array space like that because I want virtual disks &lt;2TB because of OS limitations. Now I want to expand the RAID5 array and I added 2 additional 1GB SATA disks into the MD1000. The expansion should be an online operation since I cannot shutdown the system. I would like to expand the RAID5 array _group_ and add an additional virtual disk, so I can stay under 2TB per VD. OMSA 7.1 is installed on my system. My questions are: 1. How can I expand the RAID5 array group adding the 2 physical disks and then create a new VD, all from OMSA web interface? 2. Does the "Reconfigure" task on a virtual disk, available on OMSA web interface, implicitly expand the RAID array group as well? Thanks Marco </pre> Marco Gigante 2013-06-03T10:40:42 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44146 <pre>Hello, I am unable to get raid controllers working on ANY of my PowerEdge 2850 series servers. Is there a working omsa version for PE 2850?? Regards, _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> [Digital^Dude] ® 2013-05-30T11:26:57 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44145 <pre>I have two 2950s with openmanage 7.1 installed on both. One works and the other doesn't. I note that the Bios on the version that doesn't work is version 1.1.0 and there is a 1.7 out (the working system has bios 1.3.7) I tried updating with the page http://www.ducea.com/2007/08/27/dell-bios-firmware-updates-on-debian/ but when I try to updated the bios i get (dell_rbu is loaded) $ dellBiosUpdate -u -f bios.hdr Performing BIOS update... Traceback (most recent call last): File "/usr/sbin/dellBiosUpdate", line 185, in &lt;module&gt; sys.exit( main() ) File "/usr/sbin/dellBiosUpdate", line 153, in main exit_code = updateBios(HdrFile(options.hdr), options) File "&lt;libsmbios_c._peak_util_decorators.rewrap wrapping libsmbios_c.rbu_update.updateBios at 0x02825A28&gt;", line 3, in updateBios File "/usr/lib/python2.6/dist-packages/libsmbios_c/trace_decorator.py", line 98, in trace result = func(*args, **kw) File "/usr/lib/python2.6/dist-packages/libsmbios_c/rbu_update.py", line 95, in updateBios if compareBiosVersions(ver, hdrfile.biosVersion()) &gt;= 0: File "&lt;libsmbios_c._peak_util_decorators.rewrap wrapping libsmbios_c.rbu_hdr.biosVersion at 0x0285C500&gt;", line 3, in biosVersion File "/usr/lib/python2.6/dist-packages/libsmbios_c/trace_decorator.py", line 98, in trace result = func(*args, **kw) File "/usr/lib/python2.6/dist-packages/libsmbios_c/rbu_hdr.py", line 86, in biosVersion ver = "%d.%d.%d" % struct.unpack("BBB", self.hdr.biosVersion) NameError: global name 'struct' is not defined Anybody have any ideas or more recent page to update the BIOS on a debian system ??? The one that works: $ smbios-sys-info Libsmbios version: 2.2.13 Product Name: PowerEdge 2950 Vendor: Dell Inc. BIOS Version: 1.3.7 System ID: 0x01B2 Service Tag: GTB8FD1 Express Service Code: 36600905413 Asset Tag: $ omreport system summary sh: /bin/rpm: not found System Summary ------------------ Software Profile ------------------ Systems Management Name : Server Administrator Version : 7.1.0 Description : Systems Management Software Operating System Name : Linux Version : Kernel 2.6.32-5-amd64 (x86_64) System Time : Wed May 29 14:32:44 2013 System Bootup Time : Wed Dec 12 14:34:19 2012 -------- System -------- System Host Name : dough System Location : Please set the value Lifecycle Controller : [N/A] --------------------- Main System Chassis --------------------- Chassis Information Chassis Model : PowerEdge 2950 Chassis Service Tag : GTB8FD1 Express Service Code : 36600905413 Chassis Lock : Present Chassis Asset Tag : ... -------------------- Storage Enclosures -------------------- Storage Enclosures Name : Backplane Service Tag : 77K02BV Express Service Code : 15694334923 Storage Enclosures Name : Backplane Service Tag : 77K02BV Express Service Code : 15694334923 Storage Enclosures Name : MD1000 Product ID : MD1000 Service Tag : 6MGMGD1 Express Service Code : 14418871381 Asset Tag : VS.. the one that doesn't $ smbios-sys-info Libsmbios version: 2.2.13 Product Name: PowerEdge 2950 Vendor: Dell Inc. BIOS Version: 1.1.0 System ID: 0x01B2 Service Tag: GN6RMB1 Express Service Code: 36230605741 Asset Tag: Property Ownership Tag: $ omreport system summary sh: /bin/rpm: not found System Summary ------------------ Software Profile ------------------ Systems Management Name : Server Administrator Version : 7.1.0 Description : Systems Management Software -------- System -------- System Host Name : flour System Location : </pre> kris kvilekval 2013-05-29T21:40:47 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44143 <pre>Hi, I'm totally new to this list. And I guess I have a simple question. What is the easiest way to upgrade firmwares C6100 and C6220 no matter of the OS? (We have a mixed envrionment.) Some googling around I ended up at the poweredgec.com site. Reading the Dell PowerEdge C System Management Quick Start Guide I was lead to believe that the "ipmiflash" tool is the easiest way to go? So I guess ipmiflash pushes the bios, bmc and fcb firmware against the receiving machines BMC? (or actually tells the BMC to download firmwares from a URL), so no OS is required? Am I correct in this assumption? So basically I can setup a "flash machine" with CentOS, apache, ipmitools, ipmiflash and from there push upgrades to all C chassis machines? If true, which is the simplest way to achieve this? * Getting ipmiflash and keeping it updated. * Getting the firmwares and keeping a local repo of firmwares updated. Thanks, Elias Abacioglu _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> Elias Abacioglu 2013-05-29T13:36:57 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44141 <pre>Anyone know if it's possible to boot an R620 using a USB dvd drive? The drive doesn't show up as an option from the Bios boot menu similar to how a usb drive setup using unetbootin would. Thanks, Sabuj </pre> Sabuj Pattanayek 2013-05-28T21:17:35 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44140 <pre>Hi, this mail was at the beginning a help request to my problem and i found a solution during writing it so it's just an information for you if you are concerned (Debian Squeeze and Dell PE R420 generation with Perc H310). i'm new on this list and i have a hundred Dell servers (different generations from PE1850 to R420/R720) running Debian GNU/Linux (some old Lenny (aka 5.0), many Squeeze (aka 6.0) and some Wheezy (aka 7.0) distrib). On these servers, we usually use homemade kernels (optimisations) but sometimes official Debian kernel too. I had problems with new R420 servers with H310 Perc RAID card, when using Debian Squeeze distribution. After all the BIOS tests passed (it takes near 2m30s ; quite slow but i'm used to see this on such servers with a lot of RAM, RAID card, PXE network, ...), when the grub menu is shown and an entry choosen, the kernel (2,3MB) is loading during about 30s and the ramdisk (11MB) is loading during about 1m50s. After that, when the system really starts, it takes less than 10s to go to "linux login" prompt (quick). So, to restart the server, il takes about 5m10s... I've tested it with 2 homemade kernels and 1 "official" (2.6.32-5-amd64) and i have the same results. I tested to upgrade to Debian wheezy (via dist-upgrade) and the problem disappears. The complete reboot takes "only" about 3m24s (only 50 seconds from grub menu to login prompt =&gt; normal time for a boot). Between these Debian distributions, i've the same kernel (homemade, based on 3.5.5). With Squeeze, grub is 1.98+20100804-14+squeeze1 With Wheezy, it's grub 1.99-27+deb7u1. I have to run these servers with Debian Squeeze for the moment so i had to find a solution to accelerate boot sequence... I wondered if the difference come from grub version because it's the only real difference before system boots... and it was the solution. On Debian Squeeze, i downloaded grub 1.99 and depends packages from wheezy repository and installed it with "dpkg -i ..." and now my server running Squeeze starts as quickly as i had with Wheezy installation (about 3m20s =&gt; 2 minutes less). To do this, i used the following commands (ok at this time but should be modified if version of these packages for Wheezy change in future ; see http://packages.debian.org/wheezy/grub-pc to get package and see depends) : cd /var/tmp apt-get install libfuse2 wget "http://ftp.fr.debian.org/debian/pool/main/g/grub2/grub2-common_1.99-27+deb7u1_amd64.deb" wget "http://ftp.us.debian.org/debian/pool/main/e/eglibc/multiarch-support_2.13-38_amd64.deb" wget "http://ftp.us.debian.org/debian/pool/main/x/xz-utils/liblzma5_5.1.1alpha+20120614-2_amd64.deb" wget "http://ftp.fr.debian.org/debian/pool/main/g/grub2/grub-pc-bin_1.99-27+deb7u1_amd64.deb" wget "http://ftp.fr.debian.org/debian/pool/main/g/grub2/grub-common_1.99-27+deb7u1_amd64.deb" wget "http://ftp.fr.debian.org/debian/pool/main/g/grub2/grub-pc_1.99-27+deb7u1_amd64.deb" dpkg -i multiarch-support_2.13-38_amd64.deb dpkg -i liblzma5_5.1.1alpha+20120614-2_amd64.deb dpkg -i grub*.deb Not really "clean" to do that but i didn't find a recent grub version for Debian Squeeze on official or backport repository. If it can help... B.R </pre> Joel Golliet 2013-05-28T15:48:39 http://comments.gmane.org/gmane.linux.hardware.dell.poweredge/44137 <pre>Hello, I have some 2950 machines with one power supply removed from the unit. OMSA does not even start on those servers and I cannot monitor anything on them. Single power supply is connected and is healthy. I believe omsa should report PS redundancy error but let me observer other statistics of the server. Is this a known function of OMSA or am I doing something wrong? Thanks. _______________________________________________ Linux-PowerEdge mailing list Linux-PowerEdge&lt; at &gt;dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge </pre> [Digital^Dude] ® 2013-05-27T10:12:12 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.hardware.dell.poweredge