eph0ne，w9支持otg吗_百度知道
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。
eph0ne，w9支持otg吗
我有更好的答案
主要应用于各种不同的设备或移动设备间的联接、摄像机，进行数据交换。特别是PDA。直接致电手机售后电话，进行咨询，就是支持OTG的。通过网络搜索使用的手机型号，然后查看手机参数内是否支持OTG。OTG是On-The-Go的缩写，是近年发展起来的技术判断手机是否支持OTG的方法如下、移动电话、消费类设备。改变如数码照相机：直接插入OTG线，然后插入U盘等设备，看手机是否识别，如果识别。需要电信版本手机的可以直接登录安徽电信网上营业厅进行选购的、打印机等设备间多种不同制式连接器，多达7种制式的存储卡间数据交换的不便，日由USBImplementers Forum公布
中国电信，世界触手可及
主营：宽带、手机、充值缴费
为您推荐：
其他类似问题
您可能关注的内容
换一换
回答问题，赢新手礼包HTC One X Rooting Detailed Guide Part 1: Unlock the BootloaderSkip to NavigationSkip to the Content of this PageBack to the Accessibility MenuMenuLike Us on FacebookFollow Us on TwitterFollow Us on Google PlusSubscribe to Our NewsletterRSSShareLike This Page on FacebookTweet This PagePlus One on GoogleShare on LinkedInPin to PinterestEmail ThisPrint ThisWhatsapp+Yesterday I got my long awaited phone delivered to my doorstep – the HTC One X. The device is really some piece of work! If I were to describe the phone in one statement, I would say that the phone is a beauty in looks and a beast in performance. With 1.5 GHz quad core processor and 1 GB of RAM, its equivalent to the processing power of the laptop I had a year back.Using this phone for just calling, texting, updating status and playing games would be so contemptuous. Devices such as HTC One X are meant for a lot more, and it all starts with rooting. So today we are going to show you the first step for rooting your HTC One X, i.e. the unlocking of the bootloader.Warning: This guide was tested on HTC One X, but still I don’t take responsibility of any damage caused to your phone. If you don’t know what you are doing, I recommend you call up an in-house geek and take his help. Furthermore, unlocking bootloader will void all or parts of your warranty but trust me, it’s worth it!!Necessary PrerequisitesBackup your phone’s contacts, messages and apps as the process will factory reset your HTC One X.Download and install HTC Sync software on your computer.Your device battery should be at-least 70% charged.Download and extract Fastboot files to a folder on your computer. For the sake of simplicity, make a new folder at a drive’s root level and give the folder a simple name without spaces.Register for an account at HTCDev and verify yourself. It’s free of course.Go slow, no need to rush! Read a step twice if you have to but make sure you are doing it the right way.Let’s begin thenStep 1: On your computer, visit HTCDev homepage and login to your account. After you login, click on the Unlock Bootloader button to get started.Step 2: On the right hand side, under the Supported Devices, you will see a dropdown list. Select All Other Supported Models and click on the button Begin Unlock Bootloader.Step 3: You will have to confirm to some terms and condition accepting which you will be redirected to the Unlock Instruction Page.Note: Don’t follow the instruction provided on the website. Just follow the ones in the post.Step 4: Now power off your phone and press Volume Down and Power to start the device into Bootloader mode. Use the device Volume buttons to select up or down to highlight Fastboot (This option is available specifically on HTC bootloader) and then press the Power button. Now connect your phone to the computer using a data cable and rest the phone on your desk.Step 5: We will continue to work on computer now. First connect the phone to the computer and let Windows will
install the necessary drivers. After the drivers are installed, open Windows Device Manager to confirm if the drivers are installed correctly. At the same time, click on the Proceed button that you saw in Step 5 and then skip through the steps until Step 8 on the HTCDev instruction page (Yes you have to skip the steps).Step 6: Open
Command Prompt on your computer with administrative privileges (search for cmd in Start, right-click, click Run as administrator) and navigate to the folder where you have extracted the Fastboot files we asked you in the prerequisites.Step 7: Now type (copy/paste) fastboot devices on cmd prompt and press enter. If your HTC device shows up, you are good to go. If nothing is returned, there must be some issue with your HTC One X drivers.Step 8: Again on the command prompt type (copy/paste) fastboot oem get_identifier_token and press enter. You will see a long block of text. Right-click anywhere on CMD prompt and select mark. Highlight and copy the text (select the text just like the way it’s selected in the screenshot ignoring all the info there).Step 9: Switch to the HTCDev page on your browser and paste the text in the text box under the section My Device Identifier Token at the end of the page and press the Submit button.Step 10: You will now get a mail from HTCDev with a unique Unlock_code bin file. Download and save the file in the folder where you extracted the Fastboot files.Step 11: Now, copy/paste the command fastboot flash unlocktoken Unlock_code.bin in the command prompt to start the process on your phone.The Final Step: On your phone you will see a disclaimer that will say that unlocking the bootloader may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its factory default settings, and your bootloader will be unlocked.Voila! You have done it. You have successfully unlocked HTC One X bootloader, but that’s just the beginning. Stay tuned for when we tell you tomorrow how to root your phone. Before I conclude, I would love to share the official video of HTC One X showing off its capabilities.So what do you think about the phone? We would love to know. Oh, and let me remind again, the rooting process is not yet done..we’ve just unlocked the bootloader. Come back tomorrow to check out the part 2 of this series.
Get Guiding Tech articles delivered to your inbox.Follow Us
Ashish Mundhra
See more posts by this author.
AboutContactAdvertiseFacebookTwitter&
Guiding TechGT NewsletterTerms of UsePrivacy Policy
Best Paid Apps For Free - December Week 3
More PostsMore PostsMore PostsMore PostsMore PostsMore PostsMore PostsMore PostsFrom vincent at cojot.name
1 13:43:54 2012
From: vincent at cojot.name (vincent at cojot.name)
Date: Sun, 1 Jul :54 +0200 (CEST)
Subject: Dell T410 disk cage & cabling...
In-Reply-To:
References:
Message-ID:
Hi everyone,
Just another Quick Followup: What a difference did the Dell cable make. No
more SAS_A errors and everything boots up fine. The SAS-B cable isn't
connected (hence reducing my drive bays from 6 to 4) an reported an error,
which I cleared using omconfig, but this will do for now. My T410 works
very fine and actually has its 3Tb drives connected at 6GBps.
Thanks for the help!
On Wed, 20 Jun 2012, vincent at cojot.name wrote:
> Hi Everyone,
> Just a quick follow-up
> I got two 50cm SAS Multilane cables (SFF-8087
SFF-8087) and replaced
> the current SAS 6i/R with my LSI Megaraid e HBA. The new HBA is
> now able to detect the 3TB drives from the SAS Backplane and it works
> fine, -but-:
> - Upon bootup my T410 complains that the intergrated RAID is missing (I
> know that but I'd like to -ackwnowledge- this error).
> - It also complains that the SAS_A port isn't connected (it is - with the
> 3ware cable-, it's the SAS_B which isn't since I only have one SFF8087
> on my 9280).
> At any case, I ordered a Dell Dual SAS to SAS 2.5FT Controller/Backplane
> Cable (CK58H) because I need longer cables and maybe that one will clear
> the SAS_A error but then again I don't know how to clear the missing HBA
> error...
> Any help/hints apreciated,
> Thank you,
> On Thu, 7 Jun 2012, vincent at cojot.name wrote:
>> Hi everyone,
I Just got (for home) a PowerEdge T410 with a SAS 6/R (it's an additionnal
>> PCI-E Card) and a cabled hot-swap disk cage..
My problem is that I'd like to move everything (disks, ethernet,
>> NVidia) from my old workstation to the T410 server -including- my current
>> LSI Logic 9280-8i RAID adapter (does SATA/SAS 6Gbps).. In order to do
>> just that, I would need to replace the SAS cables that go from the
>> backplane to the Dell SAS 6 HBA..
>> On the HBA itself, it looks like I have two SFF-8484 connectors. On the
>> backplane itself, it looks like an SFF-8087 connector.. (I could be
>> wrong).
>> So am I correct in assuming I would need something like a pair of
>> SFF-8087
SFF-8087 cables (SFF-8087 is what I have on my 9280-8i, I
>> think).
>> Looking at http://www./iSAS-cables-NEW.htm, I seems I
>> would need something like the iSAS-7373-HT/.5m or iSAS-7373-HT/1m.
>> Does that sound correct?
>> Any comments, warnings, etc...?
>> Thanks for the help,
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge
> https://lists./mailman/listinfo/linux-poweredge
,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,
Vincent S. Cojot, Computer Engineering. STEP project. _.,-*~'`^`'~*-,._.,-*~
Ecole Polytechnique de Montreal, Comite Micro-Informatique. _.,-*~'`^`'~*-,.
Linux Xview/OpenLook resources page _.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'
http://step.polymtl.ca/~coyote
_.,-*~'`^`'~*-,._ coyote at NOSPAM4cojot.name
They cannot scare me with their empty spaces
Between stars - on stars where no human race is
I have it in me so much nearer home
To scare myself with my own desert places.
- Robert Frost
From vincent at cojot.name
1 14:02:36 2012
From: vincent at cojot.name (vincent at cojot.name)
Date: Sun, 1 Jul :36 +0200 (CEST)
Subject: Using a PCI-E graphics adapter in a PE T410?
In-Reply-To:
References:
Message-ID:
Hi everyone,
Just a quick Followup. I'm now running a Quadro 600 (1gb DDR3 Pro card) in
the x16 (x8 cabled) slot of my T410. I let the on-board VGA board active,
which means that the DVDI display will only display something when the
driver loads (for normal BIOS/bootup issues I'll use the VGA head) but it
works very fine, does great 3D and has reasonnable temp readings (around
50C). As for my Xorg.conf, after upgrading to the latest drivers (295.59)
and editing my config file to specify the BusID, it works 'normally'
under X, just like on a normal workstation.
For the record, here's the diff to the 'Device' section of my xorg.xonf
***************
*** 56,58 ****
VendorName
"NVIDIA Corporation"
"NVIDIA Quadro FX 1800"
EndSection
--- 74,77 ----
VendorName
"NVIDIA Corporation"
"NVIDIA Quadro 600"
"PCI:9:0:0"
EndSection
I rebuilt and I'll be uploading my new dkms-nvidia packages with 295.59
shortly to http://vscojot.free.fr/dist/dkms. Here's the pkg list:
-rw-r--r-- 1 raistlin users
Jun 30 17:18
dkms-nvidia-295.59-8.el5.src.rpm
-rw-r--r-- 1 raistlin users
Jun 30 17:19
dkms-nvidia-295.59-8.el5.x86_64.rpm
I did not try one more time to disable the on-board VGA in the BIOS since
my first and only attempt had me resetting the CMOS
to regain the
machine's console (No, I don't habe an iDRAC in my system). I may try that
again in the future since it would be convenient to avoid switching
between VGA and DVI
if I could get everything to go DVI only..
Thanks for all the help,
On Fri, 8 Jun 2012, vincent at cojot.name wrote:
> Hi everyone,
> What is needed to use a different graphics adapter (PCI-E NVidia) in a
> Dell PE T410? I suppose it should go in slot 4 or 5 but is something
> specific needed in the BIOS?
From chris at g2.nu
1 15:06:12 2012
From: chris at g2.nu (Chris Good)
Date: Sun, 1 Jul :12 +0000 (UTC)
Subject: dsm_om_connsvcd high cpu utilization
References:
Message-ID:
Ricardo Stella wrote:
> * Newbie alert *=20
> Trying to figure out what's causing high cpu utilization by dsm_om_connsvcd=
> . All of a sudden noticed this across 3 PE-R610 running RHEL6 (all mirror o=
> f each other). I've restarted the services, but process comes right back at=
high CPU usage.=20
> Any ideas? Running OMSA 6.5.0.=20
It's a leap-second bug.
/wiredenterprise/2012/07/leap-second-bug-wreaks-havoc-with-java-linux/
It's easily fixed with:
date -s "`date -u`"
From Michael.Walters
2 14:11:09 2012
From: Michael.Walters
(Michael.Walters )
Date: Mon, 2 Jul :09 +0000
Subject: ISSUE:
Dell Linux Repository Does Not Have Latest OpenManage Software
Message-ID:
I install the latest OpenManage software using the method recommended on the
wget -q -O - /repo/hardware/latest/bootstrap.cgi | bash
wget -q -O - /repo/community/bootstrap.cgi | bash
These repositories, however, do not contain the latest OpenManage 7 software (which is recommended by Dell Support for use on the latest M620 servers).
Can someone update the repos on ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/eff7178/attachment.html
From erinn.looneytriggs
2 14:17:47 2012
From: erinn.looneytriggs
(Erinn Looney-Triggs)
Date: Mon, 02 Jul :47 -0800
Subject: ISSUE:
Dell Linux Repository Does Not Have Latest OpenManage
In-Reply-To:
References:
Message-ID:
On 07/02/ AM, Michael.Walters
> I install the latest OpenManage software using the method recommended on
> wget -q -O - /repo/hardware/latest/bootstrap.cgi |
> wget -q -O - /repo/community/bootstrap.cgi | bash
> These repositories, however, do not contain the latest OpenManage 7
> software (which is recommended by Dell Support for use on the latest
> M620 servers).
> Can someone update the repos on ?
They are working on it, it was supposed to be done in June, they will
get there at some point, but this is a known issue.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
Url : http://lists./pipermail/linux-poweredge/attachments/768a8/attachment.bin
From Stuart_Hayes
2 15:50:49 2012
From: Stuart_Hayes
(Stuart_Hayes )
Date: Mon, 2 Jul :49 -0500
Subject: iDRAC 7/PowerEdge R720 console issues with Fedora 17
In-Reply-To:
References:
Message-ID:
Try kernel parameter ?usbcore.autosuspend=-1? to work around this issue.
From: linux-poweredge-bounces-Lists On Behalf Of Kevin White
Sent: Friday, June 22,
To: Stroller
Cc: linux-poweredge-Lists
Subject: Re: iDRAC 7/PowerEdge R720 console issues with Fedora 17
On 6/22/ AM, Stroller wrote:
I'm using IE 9 on Windows 7 to access the iDRAC 7.
It works: I can
watch the unit boot.
I can hit keys and go into the system setup
I can even interact with Grub when Fedora starts to boot...but
as soon as it finishes booting and drops to a login: prompt, I can't
type anything.
(This is a very basic install of F17, no GUI, booting to
a text console.)
I plugged a keyboard in directly to the unit, and it works.
actually see what I'm typing at the keyboard in the iDRAC remote session.
You appear to be missing a driver module that allows the PC to recognise the iDRAC as an input device.
$ zcat /proc/config.gz | grep -i keyb
Boot with a bunch of LiveCDs, see which ones work. On each - working and non-working - run `lsmod` and redirect the output to a text file. Compare the results.
I would try the installer CD first - if this does work then it should be relatively easy to find which module you're missing. Kernel versions should match up, too.
Also might be worth grabbing a copy of /proc/config.gz for your installed system and each liveCD.
Well, what is weird is that, twice (on Fedora 17, freshly booting), I've actually seen the DRAC console work, for a few seconds.
One, it was long enough to log in and type a command, and the second, it was enough to press "enter" a few times.
Then, it stops registering keyboard input.
(To make clear: on CentOS 6.2, none of this was a problem.)
This shows up in the dmesg:
2.881570] usb 1-1.6.1: new high-speed USB device number 5 using ehci_hcd
2.973520] usb 1-1.6.1: New USB device found, idVendor=0624, idProduct=0249
2.978932] usb 1-1.6.1: New USB device strings: Mfr=4, Product=5, SerialNumber=6
2.984341] usb 1-1.6.1: Product: Keyboard/Mouse Function
2.984344] usb 1-1.6.1: Manufacturer: Avocent
2.984346] usb 1-1.6.1: SerialNumber:
2.990493] input: Avocent Keyboard/Mouse Function as /devices/pci0:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.0/input/input3
2.990775] generic-usb 49.0003: input,hidraw2: USB HID v1.00 Keyboard [Avocent Keyboard/Mouse Function] on usb-a.0-1.6.1/input0
2.991812] input: Avocent Keyboard/Mouse Function as /devices/pci0:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.1/input/input4
2.991864] dracut: Scanning devices sda1
for LVM logical volumes vg_vmhost1/lv_root vg_vmhost1/lv_swap
2.992003] generic-usb 49.0004: input,hidraw3: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-a.0-1.6.1/input1
2.993035] input: Avocent Keyboard/Mouse Function as /devices/pci0:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.2/input/input5
2.993163] generic-usb 49.0005: input,hidraw4: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-a.0-1.6.1/input2
which tells me that the Avocent KVM stuff is detected.
I looked later to see if there were any errors on the device, something to make it stop working.
There weren't.
There's no /proc/config.gz in Fedora 17.
However, I think the same thing is in /boot/config-$(uname -r).
Although, since the driver for the device is loading (and has been seen to work, momentarily), I'm not sure what I'd be looking for here.
I'm pretty sure the KVM keyboard/mouse show up to the system as a USB HID, just like any other keyboard/mouse.
And, since a USB keyboard plugged in to the unit is still working, I know that it isn't the entire USB subsystem that has crashed, or the USB_HID driver or something.
Looking more at dmesg:
1.730237] usb 1-1: new high-speed USB device number 2 using ehci_hcd
1.848447] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
1.853025] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
1.857950] hub 1-1:1.0: USB hub found
1.862523] hub 1-1:1.0: 6 ports detected
Oh, and there's a hub attached to that hub:
2.456116] usb 1-1.6: New USB device found, idVendor=0624, idProduct=0248
2.460196] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2.557859] usb 1-1.6: Product: Gadget USB HUB
2.562405] usb 1-1.6: Manufacturer: no manufacturer
2.566798] usb 1-1.6: SerialNumber:
2.571479] hub 1-1.6:1.0: USB hub found
2.576019] hub 1-1.6:1.0: 6 ports detected
That tells me that when:
2.881570] usb 1-1.6.1: new high-speed USB device number 5 using ehci_hcd
is detected a second later, it is connected through two hubs, the hub that's on 1-1.6 and the one on 1-1.
I'm not really sure what could be going wrong...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/d4bc49d/attachment.html
From masc at web.de
2 18:47:30 2012
From: masc at web.de (=?utf-8?Q?Marco_Schr=C3=B6der?=)
Date: Tue, 3 Jul :30 +0200
Subject: ISSUE: Dell Linux Repository Does Not Have Latest OpenManage
In-Reply-To:
References:
Message-ID:
Thanks for sharing this information. I'm also waiting for the 7.0
Thx, Marco
On 02.07.2012, at 21:17, Erinn Looney-Triggs
> On 07/02/ AM, Michael.Walters
>> I install the latest OpenManage software using the method
>> recommended on
>> wget -q -O - /repo/hardware/latest/
>> bootstrap.cgi |
>> wget -q -O - /repo/community/bootstrap.cgi |
>> These repositories, however, do not contain the latest OpenManage 7
>> software (which is recommended by Dell Support for use on the latest
>> M620 servers).
>> Can someone update the repos on ?
>> Thanks,
> They are working on it, it was supposed to be done in June, they will
> get there at some point, but this is a known issue.
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge
> https://lists./mailman/listinfo/linux-poweredge
From kadafax
3 08:57:45 2012
From: kadafax
Date: Tue, 03 Jul :45 +0200
Subject: Mixing STSS and ST in a 2950
Message-ID:
Hello list,
Does anyone know if mixing Seagate STSS and ST will
work for a RAID 5 configuration in a (out of warranty) 2950 ?
The adapter is a LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04)
(PERC 5i ?).
On 6 HDD, 5 are STSS ( 1TB, 7200rpm, 16MB cache, SAS 3 Gb/s) and
we may replacing a faulting one with a ST (1TB, 7200rpm, 64MB
cache, SAS 6 Gb/s).
Will it blend work ?
Thanks, have a nice day
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/655ef/attachment.html
From sdowdy at ucar.edu
3 10:02:56 2012
From: sdowdy at ucar.edu (Stephen Dowdy)
Date: Tue, 03 Jul :56 -0600
Subject: Mixing STSS and ST in a 2950
In-Reply-To:
References:
Message-ID:
On 07/03/ AM, kfx wrote:
> Does anyone know if mixing Seagate STSS and ST will
> work for a RAID 5 configuration in a (out of warranty) 2950 ?
> The adapter is a LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04)
> (PERC 5i ?).
> On 6 HDD, 5 are STSS ( 1TB, 7200rpm, 16MB cache, SAS 3 Gb/s)
> and we may replacing a faulting one with a ST (1TB, 7200rpm,
> 64MB cache, SAS 6 Gb/s).
# /usr/local/LSI-Tools/megacli-overview
[Adapter 0]
ADP[0]=( PERC 6/i Integrated),FWPkg( 6.3.1-0003),FWVer( 1.22.32-1371)
BBU[0]=(Learning?=No, charge=99 %, status=Complete, isSOHGood=Yes)
PD[32:0]=(TOSHIBA/MK1001TRKB/DCA8/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
Spun Up,F=None
PD[32:1]=(SEAGATE/STSS/KS68/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
Spun Up,F=None
PD[32:2]=(WD/WD1000FYYG/D1B3/SERIALNUM) ME=0,OE=0,PF=0,FW=Online, Spun
PD[32:3]=(SEAGATE/STSS/MS0C/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
Spun Up,F=None
PD[32:4]=(SEAGATE/ST/PS04/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
Spun Up,F=None
PD[32:5]=(SEAGATE/STSS/MS0C/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
Spun Up,F=None
PD[32:6]=(SEAGATE/ST/PS06/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
Spun Up,F=None
PD[32:7]=(TOSHIBA/MK1001TRKB/DCA8/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
Spun Up,F=None
VD[0:0]=("OpSys",R(6,0,3),SZ= 124.998 GB,SS=512
KB,CP=(W=WB,R=ReadADP,IO=D),# 8,Optimal)
VD[0:1]=("Data",R(6,0,3),SZ= 5.333 TB,SS=512
KB,CP=(W=WB,R=ReadADP,IO=D),# 8,Optimal)
This system has had EVERY disk replaced at least once.
crappy seagate
(or were they STSS originally?)
As you can see, your two
devices exist
together in this system fine.
It is a PERC 6/i, but i'm pretty sure we
have other systems
with PERC5/i that this works in as well.
The LSI/PERC controllers are pretty good about working (whether
optimally or not may be
another question) with variant drive types and firmware.
From kadafax
3 10:07:58 2012
From: kadafax
Date: Tue, 03 Jul :58 +0200
Subject: Mixing STSS and ST in a 2950
In-Reply-To:
References:
Message-ID:
On 07/03/ PM, Stephen Dowdy wrote:
> On 07/03/ AM, kfx wrote:
>> Does anyone know if mixing Seagate STSS and ST will
>> work for a RAID 5 configuration in a (out of warranty) 2950 ?
>> The adapter is a LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04)
>> (PERC 5i ?).
>> On 6 HDD, 5 are STSS ( 1TB, 7200rpm, 16MB cache, SAS 3 Gb/s)
>> and we may replacing a faulting one with a ST (1TB, 7200rpm,
>> 64MB cache, SAS 6 Gb/s).
> # /usr/local/LSI-Tools/megacli-overview
> [Adapter 0]
> ADP[0]=( PERC 6/i Integrated),FWPkg( 6.3.1-0003),FWVer( 1.22.32-1371)
> BBU[0]=(Learning?=No, charge=99 %, status=Complete, isSOHGood=Yes)
> PD[32:0]=(TOSHIBA/MK1001TRKB/DCA8/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
> Spun Up,F=None
> PD[32:1]=(SEAGATE/STSS/KS68/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
> Spun Up,F=None
> PD[32:2]=(WD/WD1000FYYG/D1B3/SERIALNUM) ME=0,OE=0,PF=0,FW=Online, Spun
> Up,F=None
> PD[32:3]=(SEAGATE/STSS/MS0C/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
> Spun Up,F=None
> PD[32:4]=(SEAGATE/ST/PS04/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
> Spun Up,F=None
> PD[32:5]=(SEAGATE/STSS/MS0C/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
> Spun Up,F=None
> PD[32:6]=(SEAGATE/ST/PS06/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
> Spun Up,F=None
> PD[32:7]=(TOSHIBA/MK1001TRKB/DCA8/SERIALNUM) ME=0,OE=0,PF=0,FW=Online,
> Spun Up,F=None
> VD[0:0]=("OpSys",R(6,0,3),SZ= 124.998 GB,SS=512
> KB,CP=(W=WB,R=ReadADP,IO=D),# 8,Optimal)
> VD[0:1]=("Data",R(6,0,3),SZ= 5.333 TB,SS=512
> KB,CP=(W=WB,R=ReadADP,IO=D),# 8,Optimal)
> This system has had EVERY disk replaced at least once.
crappy seagate
> (or were they STSS originally?)
As you can see, your two
> devices exist
> together in this system fine.
It is a PERC 6/i, but i'm pretty sure we
> have other systems
> with PERC5/i that this works in as well.
> The LSI/PERC controllers are pretty good about working (whether
> optimally or not may be
> another question) with variant drive types and firmware.
> --stephen
Wow thank you for this report, that's pretty clear :)
best wishes
From matthew.garman
3 12:35:48 2012
From: matthew.garman
(Matt Garman)
Date: Tue, 3 Jul :48 -0500
Subject: R620/12G servers w/CentOS 5.7 and low-latency?
In-Reply-To:
References:
Message-ID:
I posted about this a while ago, see follow-up below...
On Fri, May 18, 2012 at 12:50 PM, Matt Garman
> I was just wondering if anyone else on this list happens to be using
> the new 12G servers (R620 in our case) with CentOS 5.7 in an ultra-low
> latency environment?
We have configured the standard BIOS settings
> appropriately (disable c-cstates/c1e, max performance, etc---a
> familiar drill from previous-gen servers).
> However, what we are seeing in our simulations and testing is
> inconsistent performance results.
Even doing the same exact test, one
> right after the other, the results vary substantially (up AND down).
> A full-on simulation one day to the next can vary by 50%.
> With the previous-gen (11G) servers, I had a similar performance issue
> that was ultimately fixed by a BIOS update (but six months after the
> 11G release).
I'm hoping to not see a repeat of this kind of issue.
> I'm working the formal channels with Dell on this, but just thought
> I'd throw a feeler out there to see if anyone else is seeing similar
I've been able to isolate at least one facet of the problem.
to me that contended pthread mutexes and condition variable signaling
is slower under Sandy Bridge than previous-gen CPUs.
What follows is a message I posted to the Linux Kernel Mailing L I
thought I'd reproduce it here for anyone who might be
interested/curious.
I include a link to a sample program which
demonstrates the issue.
LKML post:
I have been looking at the performance of two servers:
- dual Xeon XGHz (Nehalem, Dell R610)
- dual Xeon E5- GHz (Sandy Bridge, Dell R620 & HP dl360g8p)
For my particular (proprietary) application, the Sandy Bridge systems
are significantly slower.
At least one facet of this problem has to
- pthread condition variable signaling
- pthread mutex lock contention
I wrote a simple (<300 lines) C program that demonstrates this:
The program has two tests:
- "lc", a lock contention test, where two threads "fight" over
incrementing and decrementing an integer, arbitrated with a
pthread_mutex_t
- "cv", a condition variable signaling test, where two threads
"politely" take turns incrementing and decrementing an integer,
signaling each other with a condition variable
The program uses pthread_setaffinity_np() to pin each thread to its
own CPU core.
I would expect the SNB-based servers to be faster, since they have a
clockspeed and architecture advantage.
Results of X5550 @ 2.67 GHz server under CentOS 5.7:
# ./snb_slow_demo -c 3 -C 5 -t cv -n
runtime, seconds ........ 143.339958
# ./snb_slow_demo -c 3 -C 5 -t lc -n
runtime, seconds ........ 58.278671
Results of Dell E5-2690 @ 2.90 GHz under CentOS 5.7:
# ./snb_slow_demo -c 2 -C 4 -t cv -n
runtime, seconds ........ 179.272697
# ./snb_slow_demo -c 2 -C 4 -t lc -n
runtime, seconds ........ 103.437226
I upgraded the E5-2690 server to CentOS 6.2, then tried both the
current release kernel.org kernel version 3.4.4, and also 3.5.0-rc5.
The "lc" test results are about the same, but the "cv" tests are worse
yet: the same test takes about 229 seconds to run.
Also noteworthy is that the HP has generally better performance than
But the HP E5-2690 is still worse than the X5550.
In all cases, for all servers, I disabled power-saving features (cpu
frequency scaling, C-states, C1E).
I verified with i7z that all CPUs
spend 100% of their time in state C0.
Is this simply a corner case where Sandy Bridge is worse than its
predecessor?
Or is there an implementation problem?
From andy at time-domain.co.uk
4 01:44:09 2012
From: andy at time-domain.co.uk (andy thomas)
Date: Wed, 4 Jul :09 +0100 (BST)
Subject: c6220 ethernet changes on Rocks 5.3
In-Reply-To:
References:
Message-ID:
On Thu, 21 Jun 2012, Edsall, William (WJ) wrote:
> Hello list,
> We've added from C6220's in the mix with our C6100's, and the C6220's are not installing. They PXE boot and receive the image, but they do not receive the kickstart file. My assumption is that the NIC's in these machines requires a different driver.
> It looks like the c6220 comes with: Intel Ethernet Controller i350
> The previous c6100 came with: Intel Kawela(tm) 82576 Gb
> Has anyone experienced and resolved this issue?
Although this is not a Linux problem, I too am having problems with the
network interfaces on a new C6220. The interfaces fail to get a DHCP lease
when connected to a network that has a DHCP server on it so PXE boot
doesn't work. If the network lead is disconnected and then reconnected, it
sometimes gets an IP address but most of the time it doesn't. All 4 server
modules behave the same so it can't be a hardware fault.
I eventually installed Ubuntu Server 12.04 on one server module from a USB
CD drive - this has the latest igb NIC driver but the network connectivity
problems remain and connectivity is lost after a few minutes. The NIC link
LED stays lit and ethtool reports an active link even when the link is
apparently down and even setting a static IP address doesn't help. The
fact that these problems are apparent in PXE even before the server is
booted suggests problems with the Intel i350 NIC chipset.
The only thing I can think of that might have something to do with this is
the network it is connected to is 100 Mbit/s - maybe all works fine on a
gigabit network? But it's a lot of effort to move the server to a
different building where there's gigabit connectivity to check this.
Any ideas?
From sveniu
4 10:07:38 2012
From: sveniu
(Sven Ulland)
Date: Wed, 04 Jul :38 +0200
Subject: Dell IPMI OEM SEL event descriptions
Message-ID:
Are Dell's OEM SEL event descriptions freely available anywhere?
I'd like to use ipmi to retrieve the system event log (SEL), and then
extract useful information from it. Primarily, I'm looking for memory
and disk errors that can be used to trigger testing and possible
replacements, in as programmatic way as possible. I'm not interested
in using omsa.
Dell uses OEM-specific SEL event descriptions, and I'd like to get my
hands on those, instead of deducing it manually. An earlier post by
Fred Skrotzki explains how to deduce memory location from the ipmi sel
event data [1]. I assume he's been manually deducing this info by
correlating the ipmi sel log with the i/drac system event log, where
OEM data is included. This is prone to problems if the data changes
with hardware or i/drac releases and updates.
Dell's Wayne Weilnau says: "If you are using a Dell version of IPMI
Tool (its available on the Systems Management DVD), there should be an
option to use Dell extensions that will make the output a little more
user friendly." [2]. I'm unable to find any ipmitool in the OMSA
distributions. It could contain an oem file that can be fed directly
to 'ipmitool -O ', which would be brilliant.
Here's how a memory fault is reported in the SEL:
SEL Record ID
Record Type
: 05/30/:59
Generator ID
EvM Revision
Sensor Type
Sensor Number
Event Type
: Sensor-specific Discrete
Event Direction
: Assertion Event
Event Data
Description
: Uncorrectable ECC
This can be (easily) mapped to point to DIMM_A1. From there, I can
look up dmi data to find additional details like serial and asset
numbers. (Btw, the event data field is defined in the IPMI v2 spec,
section 29.7. 0xa = 1010b => 'oem code in next byte'.)
While manual mapping is certainly possible, I would like to avoid
such a brittle, hardcoded approach. Also, full OEM info can be applied
to other events, like disks and CPUs, and even the events that just
say "An OEM diagnostic event has occurred" (event data 0x210400, for
On a side note, some events are possible to look up in extra detail,
for example CPU errors. Just use 'sel get ', and in some cases
where it's supported, FRU details are shown:
$ ipmitool ... sel get 0x10
SEL Record ID
Record Type
: 06/02/:21
Generator ID
EvM Revision
Sensor Type
: Processor
Sensor Number
Event Type
: Sensor-specific Discrete
Event Direction
: Assertion Event
Event Data (RAW)
Event Interpretation Missing
Description
: Status (0x60)
Sensor Type (Discrete): Processor
States Asserted
: Processor
[Presence detected]
FRU Device Description : CPU1 (ID 176)
Device not present (Requested sensor, data, or record not found)
Let me know if anyone is already doing something like this, with
a minimum of fuss (in other words, as standards-compliant [ipmi] as
possible), and a minimum of megabytes (that again excludes omsa).
[1]: Linux-PowerEdge: memory test on Linux
Message-ID:
[2]: Linux-PowerEdge: how to enable BMC sensors
Message-ID:
From Brent.Kimberley at durham.ca
4 12:15:34 2012
From: Brent.Kimberley at durham.ca (Brent Kimberley)
Date: Wed, 04 Jul :34 -0400
Subject: R620/12G servers w/CentOS 5.7 and low-latency? (Matt Garman)
In-Reply-To:
References:
Message-ID:
Please excuse the
copy 'n paste....
Maximizing Performance involves ?System Level? optimizations
? OEM BIOS Settings: SMI, HyperThreading, C-States- All Off
- Experiment with EIST & Turbo On/Off
? On the application: Maximize your resources by?
- Pin Threads, Interrupts, and Processes to individual cores using
- Place ?communication? functions threads on adjacent cores
- Use PCM to determine L3 Cache Misses & Keep data in L3 Cache
? /file/41604
- Compile w/Performance Settings, Use PGO, Evaluate IPP / SSE 4.2
/en-us/articles/using-avx-without-writing-avx-code/
? Determine how many cores your trading strategy requires
- Can it run on 8 cores? If so, match up CPU+NIC per strategy
? /knowledge/solutions/53031
/sites/content/shared-content/data-sheets/en/Documents/configuring-low-latency-environments-on-dell-poweredge-12g-servers.pdf
/Content/UserFiles/Documents/Intel_Solarflare_Webinar_Paper.pdf
http://lse.sourceforge.net/
THIS MESSAGE IS FOR THE USE OF THE INTENDED RECIPIENT(S) ONLY AND MAY
CONTAIN INFORMATION THAT IS PRIVILEGED, PROPRIETARY, CONFIDENTIAL,
AND/OR EXEMPT FROM DISCLOSURE UNDER ANY RELEVANT PRIVACY LEGISLATION.
No rights to any privilege have been waived.
If you are not the
intended recipient, you are hereby notified that any review,
retransmission, dissemination, distribution, copying, conversion to hard
copy, taking of action in reliance on or other use of this communication
is strictly prohibited.
If you are not the intended recipient and have
received this message in error, please notify me by return e-mail and
delete or destroy all copies of this message.
From sdouche
5 06:55:24 2012
From: sdouche
(Sebastien Douche)
Date: Thu, 5 Jul :24 +0200
Subject: Debian Squeeze Backports Kernel 3.2
In-Reply-To:
References:
Message-ID:
On Fri, Jun 22, 2012 at 1:07 PM, Helmut Wollmersdorfer
> PowerEdge R510
> PERC H700 Integrated
> running as HA-Cluster with Kernel 2.6.32-5-xen-amd64
Hi Helmut,
not sure to understand your question but I backported the Linux 3.2.21
on Debian Lenny w/o problem.
Sebastien Douche
Twitter: @sdouche / G+: +sdouche
From rgraves at carleton.edu
6 12:21:00 2012
From: rgraves at carleton.edu (Rich Graves)
Date: Fri, 6 Jul :00 -0500 (CDT)
Subject: On-board bnx2 10G on R620: VLANs, iDRAC, iSCSI
In-Reply-To:
Message-ID:
I've got a couple R620's with iDRAC7 Express and the Broadcom G fiber + 2x1G copper daughtercard option.
They will be running RHEL 5.8.
Ideally, what I would like is:
1) iDRAC/IPMI goes to one of the 1G copper ports.
2) The 10G link is a trunk to several VLANs.
3) Over one of those VLANs -- I don't care it it's tagged or pvid -- boot from iSCSI.
The Google shows an awful lot of chaff from old problems, but I'm not sure where the current friendly manual is.
Some questions:
1) I see that eth0/eth4 and eth1/eth5 are pairs, presumably corresponding to "regular" and "iSCSI offload" instances of the same network port. Which is which?
2) How do I configure iDRAC/IPMI to use a different physical port?
3) Do I want to run the RHEL5.8 bnx2[i] drivers, or the *older* drivers available from Dell? The issues identified in linux_readme.txt were addressed in RHEL5.8.
4) How do I use the boot-from-iSCSI bits? I've avoided bnx2i, preferring software iSCSI and boot-from-FC due to past reliability issues, but it seems to have matured, yes? If there's any reason to be leery, FC is still an option.
Rich Graves /rcgraves
Carleton.edu Sr UNIX and Security Admin
From hithmazoz
8 09:15:12 2012
From: hithmazoz
(Hithm Azoz)
Date: Sun, 8 Jul :12 +0200
Subject: No subject
Message-ID:
how to install ubuntu 12.04 FOR SERVER DELL R720
*Best regards,*
Abd Elaziz Salah
Technical Supervisor
IT Professionals
*TeleFax : (+202) 37 49 45 53
Location: 34 Al Madenah Al Monawarah St.
Mohandeseen, Giza, Egypt.
Cell: 012 3181333*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments//deaaea14/attachment.html
From dell at epperson.homelinux.net
8 09:43:16 2012
From: dell at epperson.homelinux.net (dell at epperson.homelinux.net)
Date: Sun, 8 Jul :16 -0400
Message-ID:
On Sun, July 8, , Hithm Azoz wrote:
> how to install ubuntu 12.04 FOR SERVER DELL R720
Switch the boot mode setting from UEFI to BIOS.
From gp at apfeltalk.de
8 14:48:50 2012
From: gp at apfeltalk.de (Gerd Pleyer)
Date: Sun, 8 Jul :50 +0200
In-Reply-To:
References:
Message-ID:
> Switch the boot mode setting from UEFI to BIOS.
With ubuntu 12.04 LTS my grub2 menu sometimes forget to auto boot - anybody
with the same?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/54898/attachment.html
From giulioo
9 09:46:26 2012
From: giulioo
Date: Mon, 09 Jul :26 +0200
Subject: PE-T620/RHEL6x: Your BIOS has requested that x2apic be disabled.
Message-ID:
PE-T620 (E5-2620, 64GB RAM)
BIOS: 1.2.6, Linux CENTOS 6.x 2.6.32-220.23.1.el6.x86_64
On boot I get the message you find at t the system
appears to work normally.
If I boot with 'intremap=no_x2apic_optout', as dmesg message suggests, then
the message goes away.
I'd like to know what Dell recommends:
1) Just ignore the message, do not use intremap boot option
2) Use 'intremap=no_x2apic_optout' boot option
===== dmesg with standard boot options:
HPET id 0 under DRHD base 0xdf900000
------------[ cut here ]------------
WARNING: at drivers/pci/intr_remapping.c:715
enable_intr_remapping+0x73/0x2af()
(Not tainted)
Hardware name: PowerEdge T620
Your BIOS has requested that x2apic be disabled.
This will leave your machine vulnerable to irq-injection attacks.
Use 'intremap=no_x2apic_optout' to override BIOS request.
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.32-220.23.1.el6.x86_64 #1
Call Trace:
[] ? warn_slowpath_common+0x87/0xc0
[] ? warn_slowpath_fmt+0x46/0x50
[] ? enable_intr_remapping+0x73/0x2af
[] ? enable_IR+0x54/0x6e
[] ? enable_IR_x2apic+0xc0/0x221
[] ? native_smp_prepare_cpus+0x143/0x389
[] ? kernel_init+0x112/0x2fe
[] ? child_rip+0xa/0x20
[] ? kernel_init+0x0/0x2fe
[] ? child_rip+0x0/0x20
---[ end trace ac0a725 ]---
Enabled IRQ remapping in xapic mode
x2apic not enabled, IRQ remapping is in xapic mode
Setting APIC routing to physical flat
alloc irq_desc for 88 on node 0
alloc kstat_irqs on node 0
alloc irq_desc for 89 on node 0
alloc kstat_irqs on node 0
===== dmesg with intremap=no_x2apic_optout
HPET id 0 under DRHD base 0xdf900000
Enabled IRQ remapping in x2apic mode
Enabling x2apic
Enabled x2apic
Setting APIC routing to cluster x2apic
alloc irq_desc for 88 on node 0
alloc kstat_irqs on node 0
alloc irq_desc for 89 on node 0
alloc kstat_irqs on node 0
From hithmazoz
9 12:03:02 2012
From: hithmazoz
(Hithm Azoz)
Date: Mon, 9 Jul :02 +0200
Subject: Linux-PowerEdge Digest, Vol 98, Issue 9
In-Reply-To:
References:
Message-ID:
server dell Poweredge r720 support Ubuntu 64bit
*Best regards,*
Abd Elaziz Salah
Technical Supervisor
IT Professionals
*TeleFax : (+202) 37 49 45 53
Location: 34 Al Madenah Al Monawarah St.
Mohandeseen, Giza, Egypt.
Cell: 012 *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/d02beed/attachment.html
From Jose_De_La_Rosa
9 12:22:10 2012
From: Jose_De_La_Rosa
(Jose_De_La_Rosa )
Date: Mon, 9 Jul :10 -0500
Subject: PowerEdge R720 / Ubuntu 64bit
Message-ID:
Though Dell does not currently support Ubuntu Server on PowerEdge, you should be able to run Ubuntu Server 12.04 on the PowerEdge R720. However, we've seen some issues when using UEFI, so use legacy BIOS. We are working with Canonical to address the UEFI issue.
Jose De la Rosa
Linux Engineering
Dell | Enterprise Product Group
From: linux-poweredge-bounces-Lists On Behalf Of Hithm Azoz
Sent: Monday, July 09,
To: linux-poweredge-Lists
Subject: Re: Linux-PowerEdge Digest, Vol 98, Issue 9
server dell Poweredge r720 support Ubuntu 64bit
Best regards,
Abd Elaziz Salah
Technical Supervisor
IT Professionals
TeleFax : (+202) 37 49 45 53
Location: 34 Al Madenah Al Monawarah St.
Mohandeseen, Giza, Egypt.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/be7c08/attachment.html
From giulioo
9 13:24:02 2012
From: giulioo
Date: Mon, 09 Jul :02 +0200
Subject: PE-T620/RHEL6x: why does OMSA report "warning icon" for battery?
Message-ID:
PE-T620, BIOS: 1.2.6, CENTOS 6.x 2.6.32-220.23.1.el6.x86_64
OMSA: 7.0.0
PERC H710P:
Firmware Version 21.0.2-0001
Driver Version 00.00.05.40-rh2
PE-T620 is brand new, if this matters.
On the main OMSA web page
Health -> Components -> Storage
I get a warning icon (yellow triangle with black esclamation mark on top)
for "Storage".
I click on "Storage", then click on "PERC H710P", and I then can see that
the warning icon is for the "Battery".
I click on "Battery" and I get this info:
Name Battery 0
State Ready
Predicted Capacity Status Unknown
$ sudo omreport storage battery
List of Batteries in the System
Controller PERC H710P Adapter (Slot 4)
: Non-Critical
: Battery 0
Recharge Count
: Not Applicable
Max Recharge Count
: Not Applicable
Predicted Capacity Status : Unknown
Learn State
: Not Applicable
Next Learn Time
: Not Applicable
Maximum Learn Delay
: Not Applicable
I searched for "predicted capacity" (the only parameter that is "Unknown")
in the following docs
Dell OpenManage Server Administrator Version 7.0
Command Line Interface Guide
Dell OpenManage Server Administrator Version 7.0
Messages Reference Guide
and didn't find anything.
Is this normal?
If this is normal, how can I make the warning icon go away so that in the
future I won't be misled by it?
From gp at apfeltalk.de
9 13:41:10 2012
From: gp at apfeltalk.de (Gerd Pleyer)
Date: Mon, 9 Jul :10 +0200
Subject: repository for the new R420
Message-ID:
I just loaded the dell repository manager - and hooray - there is no R420.
Is this correct?
Thanks Gerd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/ae17902/attachment.html
From erinn.looneytriggs
9 15:17:51 2012
From: erinn.looneytriggs
(Erinn Looney-Triggs)
Date: Mon, 09 Jul :51 -0800
Subject: UEFI PXE boot
Message-ID:
Has anyone here had luck with UEFI based PXE booting in a Linux
environment?
I am essentially running into the same issue as this person here:
http://lists./pipermail/linux-poweredge/2011-November/045603.html
Basically it will boot grab the grub image, transfer the vmlinuz and
initrd and then just hang, with this error:
Trying to allocate 923 pages for VMLINUZ
[Linux-EFI, setup=0x1039, size=0x39a2c0]
[Initrd, addr=0x7de51000, size=0x1cabcd5]
Any insights?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
Url : http://lists./pipermail/linux-poweredge/attachments/c7799d/attachment.bin
From kajtzu at basen.net
Tue Jul 10 02:06:19 2012
From: kajtzu at basen.net (Kaj Niemi)
Date: Tue, 10 Jul :19 +0300
Subject: UEFI PXE boot
In-Reply-To:
References:
Message-ID:
No luck I'm afraid, I spent about a week last winter to try to get it to work. I had a bunch of R510s that I wanted to try to UEFI PXE boot but fortunately was able to skip that part as they had the 2 extra startup disks inside (which were smaller and could be booted from without UEFI).
If you get it to boot successfully all the way please write it up somewhere. ;)
Kaj J. Niemi
BaseN Corporation
FI +358 45 63 12000
KSA +966 54 899 7789
On Jul 9, 2012, at 23:17, Erinn Looney-Triggs wrote:
> Has anyone here had luck with UEFI based PXE booting in a Linux
> environment?
> I am essentially running into the same issue as this person here:
> http://lists./pipermail/linux-poweredge/2011-November/045603.html
> Basically it will boot grab the grub image, transfer the vmlinuz and
> initrd and then just hang, with this error:
> Trying to allocate 923 pages for VMLINUZ
> [Linux-EFI, setup=0x1039, size=0x39a2c0]
> [Initrd, addr=0x7de51000, size=0x1cabcd5]
> Any insights?
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge
> https://lists./mailman/listinfo/linux-poweredge
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4385 bytes
Desc: not available
Url : http://lists./pipermail/linux-poweredge/attachments/a22a4f0/attachment-0001.bin
From giulioo
Tue Jul 10 02:08:30 2012
From: giulioo
Date: Tue, 10 Jul :30 +0200
Subject: PE-T620/RHEL6x: why does OMSA report "warning icon" for battery?
In-Reply-To:
References:
Message-ID:
On Mon, Jul 9, 2012 at 8:24 PM, Giulio
> PE-T620, BIOS: 1.2.6, CENTOS 6.x 2.6.32-220.23.1.el6.x86_64
> On the main OMSA web page
Health -> Components -> Storage
> I get a warning icon (yellow triangle with black esclamation mark on top)
> for "Storage".
The warning icon went away after about 12 hours (server was new from factory).
> $ sudo omreport storage battery
> List of Batteries in the System
> Controller PERC H710P Adapter (Slot 4)
: Non-Critical
: Battery 0
> Recharge Count
: Not Applicable
> Max Recharge Count
: Not Applicable
> Predicted Capacity Status : Unknown
> Learn State
: Not Applicable
> Next Learn Time
: Not Applicable
> Maximum Learn Delay
: Not Applicable
Now it reads:
List of Batteries in the System
Controller PERC H710P Adapter (Slot 4)
: Battery 0
Recharge Count
: Not Applicable
Max Recharge Count
: Not Applicable
Predicted Capacity Status : Ready
Learn State
: Not Applicable
Next Learn Time
: Not Applicable
Maximum Learn Delay
: Not Applicable
Clearer docs would be welcome.
From inyong.hwang
Tue Jul 10 03:20:30 2012
From: inyong.hwang
(Inyong HWANG)
Date: Tue, 10 Jul :30 +0900
Subject: [q] megacli & other error count bug.
Message-ID:
Does anyone have an idea about this?
Everytime I query with MegaCli about status of
RAID, "Other Error Count"
=== Physical Drive Status ===
Enc/Slot/DevId
- Disk Size : Status /
Media/Other/Pre-ErrCount
--------------------------------------------------------------------------------
0/0/00 5QD5GDA3ST3750640NS 3BKS - 698.636 GB : status is Online,Spun
<------- Other error count !
0/1/01 5QD5EM4NST3750640NS 3BKS - 698.636 GB : status is Online,Spun
0/2/02 5QD5E7HLST3750640NS 3BKS - 698.636 GB : status is Online,Spun
0/3/03 5QD5GDBRST3750640NS 3BKS - 698.636 GB : status is Online,Spun
0/4/04 5QD5D9FXST3750640NS 3BKS - 698.636 GB : status is Online,Spun
0/5/05 5QD5GD8BST3750640NS 3BKS - 698.636 GB : status is Online,Spun
FwTermLog : I guess, other error count due to this "unexpected sense".
(only in SATA disk case)
Is there any workaround to reset "other error count"
or resolve this?
8:45:44: EVT#/12
8:45:44: 113=Unexpected sense: PD
00(e1/s0), CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 70 00 05 00 00 00 00
0a 00 00 00 00 24 0
0 00 00 00 0
8:45:44: EVT#/12
8:45:44: 113=Unexpected sense: PD
01(e1/s1), CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 70 00 05 00 00 00 00
0a 00 00 00 00 24 0
0 00 00 00 0
8:45:44: EVT#/12
8:45:44: 113=Unexpected sense: PD
02(e1/s2), CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 70 00 05 00 00 00 00
0a 00 00 00 00 24 0
0 00 00 00 0
8:45:44: EVT#/12
8:45:44: 113=Unexpected sense: PD
03(e1/s3), CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 70 00 05 00 00 00 00
0a 00 00 00 00 24 00 00 00 00 0
8:45:44: EVT#/12
8:45:44: 113=Unexpected sense: PD
04(e1/s4), CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 70 00 05 00 00 00 00
0a 00 00 00 00 24 00 00 00 00 0
8:45:44: EVT#/12
8:45:44: 113=Unexpected sense: PD
05(e1/s5), CDB: 4d 00 4d 00 00 00 00 00 20 00, Sense: 70 00 05 00 00 00 00
0a 00 00 00 00 24 00 00 00 00 0
/opt/MegaRAID/MegaCli/MegaCli64 -ShowSummary -aALL
Operating System:
Linux version 2.6.18-164.el5
Driver Version: 00.00.04.08-RH2
CLI Version: 8.04.07
Controller
ProductName
: PERC 5/i Integrated(Bus 0, Dev 0)
SAS Address
FW Package Version: 5.2.2-0072
Product Id
: BACKPLANE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments//aba27402/attachment.html
From tkrah at fachschaft.imn.htwk-leipzig.de
Tue Jul 10 08:17:07 2012
From: tkrah at fachschaft.imn.htwk-leipzig.de (Torsten Krah)
Date: Tue, 10 Jul :07 +0200
Subject: Perc 5/I fatal firmware error - DATA Abort Exception
Message-ID:
found my PE2950 server currently dead and console just prints out:
rejecting i/o to offline device
After reboot all seems fine but the perc controller log contains this:
07/10/12 12:40:53: *** DATA ABORT exception: sf=a00ffd58
07/10/12 12:40:53: CPSR=: N=0,Z=0,C=1,V=0,Q=0
I=0 F=0 T=0
MODE=13(SVC)
07/10/12 12:40:53:
r1=a141e000
r3=a0d84840
07/10/12 12:40:53:
r4=a1475c00
r7=a0d94ea0
07/10/12 12:40:53:
r8=a1475c00
r11=a00ffddc
07/10/12 12:40:53: r12=a1475c04
lr=a084fb44
pc=a0851bc4
EVT#/12 12:40:53:
15=Fatal firmware error: Line 1029
in ../../raid/verdeMain.c
I am currently running 5.2.1-0067 firmware on this device.
Anyone knows this problem? Is this fixed with a newer firmware revision?
Anyone some more input what this firmware error wants to tell me?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5590 bytes
Desc: not available
Url : http://lists./pipermail/linux-poweredge/attachments/c8411c9/attachment.bin
From jbaird
Tue Jul 10 12:29:34 2012
From: jbaird
(Baird, Josh)
Date: Tue, 10 Jul :34 +0000
Subject: PE-T620/RHEL6x: why does OMSA report "warning icon" for battery?
In-Reply-To:
References:
Message-ID:
There are virtually zero docs for any of this stuff.
Unfortunately.
-----Original Message-----
From: linux-poweredge-bounces
[mailto:linux-poweredge-bounces ] On Behalf Of Giulio
Sent: Tuesday, July 10,
To: linux-poweredge
Subject: Re: PE-T620/RHEL6x: why does OMSA report "warning icon" for battery?
On Mon, Jul 9, 2012 at 8:24 PM, Giulio
> PE-T620, BIOS: 1.2.6, CENTOS 6.x 2.6.32-220.23.1.el6.x86_64
> On the main OMSA web page
Health -> Components -> Storage
> I get a warning icon (yellow triangle with black esclamation mark on top)
> for "Storage".
The warning icon went away after about 12 hours (server was new from factory).
> $ sudo omreport storage battery
> List of Batteries in the System
> Controller PERC H710P Adapter (Slot 4)
: Non-Critical
: Battery 0
> Recharge Count
: Not Applicable
> Max Recharge Count
: Not Applicable
> Predicted Capacity Status : Unknown
> Learn State
: Not Applicable
> Next Learn Time
: Not Applicable
> Maximum Learn Delay
: Not Applicable
Now it reads:
List of Batteries in the System
Controller PERC H710P Adapter (Slot 4)
: Battery 0
Recharge Count
: Not Applicable
Max Recharge Count
: Not Applicable
Predicted Capacity Status : Ready
Learn State
: Not Applicable
Next Learn Time
: Not Applicable
Maximum Learn Delay
: Not Applicable
Clearer docs would be welcome.
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge
https://lists./mailman/listinfo/linux-poweredge
From cupertino at gmx.net
Tue Jul 10 12:47:38 2012
From: cupertino at gmx.net (cupertino at gmx.net)
Date: Tue, 10 Jul :38 +0200
Subject: Perc 5/I fatal firmware error - DATA Abort Exception
In-Reply-To:
References:
Message-ID:
haven't checked lately, but I think it is the most recent FW already.
you can try to re-flash the FW (or apply a newer one if there is any). if it then happens again you need to get the card replaced.
-------- Original-Nachricht --------
> Datum: Tue, 10 Jul :07 +0200
> Von: Torsten Krah
> An: linux-poweredge at lists.
> Betreff: Perc 5/I fatal firmware error - DATA Abort Exception
> found my PE2950 server currently dead and console just prints out:
> rejecting i/o to offline device
> After reboot all seems fine but the perc controller log contains this:
> 07/10/12 12:40:53: *** DATA ABORT exception: sf=a00ffd58
> 07/10/12 12:40:53: CPSR=: N=0,Z=0,C=1,V=0,Q=0
I=0 F=0 T=0
> MODE=13(SVC)
> 07/10/12 12:40:53:
r1=a141e000
> r3=a0d84840
> 07/10/12 12:40:53:
r4=a1475c00
> r7=a0d94ea0
> 07/10/12 12:40:53:
r8=a1475c00
> r11=a00ffddc
> 07/10/12 12:40:53: r12=a1475c04
lr=a084fb44
pc=a0851bc4
> EVT#/12 12:40:53:
15=Fatal firmware error: Line 1029
> in ../../raid/verdeMain.c
> I am currently running 5.2.1-0067 firmware on this device.
> Anyone knows this problem? Is this fixed with a newer firmware revision?
> Anyone some more input what this firmware error wants to tell me?
From tkrah at fachschaft.imn.htwk-leipzig.de
Wed Jul 11 03:10:10 2012
From: tkrah at fachschaft.imn.htwk-leipzig.de (Torsten Krah)
Date: Wed, 11 Jul :10 +0200
Subject: Perc 5/I fatal firmware error - DATA Abort Exception
In-Reply-To:
References:
Message-ID:
found /sas-raid/R189337.txt
5.2.2-0072 - but it does not mention anything in this direction to be a
problem or fixed.
What does this error mean? Why must the card be replaced?
Am Dienstag, den 10.07. +0200 schrieb cupertino at gmx.net:
> haven't checked lately, but I think it is the most recent FW already.
> you can try to re-flash the FW (or apply a newer one if there is any).
> if it then happens again you need to get the card replaced.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5590 bytes
Desc: not available
Url : http://lists./pipermail/linux-poweredge/attachments/caa426/attachment.bin
From cupertino at gmx.net
Wed Jul 11 03:24:26 2012
From: cupertino at gmx.net (cupertino at gmx.net)
Date: Wed, 11 Jul :26 +0200
Subject: Perc 5/I fatal firmware error - DATA Abort Exception
In-Reply-To:
References:
Message-ID:
that is something only D-)
there are a couple of posts out there about this issue and I remember they all ended up with either applying (re-applying) FW and/or drivers or a hardware replacement.
btw the log clearly states 'firmware fatal error', so FW would be a good thing to start with.
good luck!
-------- Original-Nachricht --------
> Datum: Wed, 11 Jul :10 +0200
> Von: Torsten Krah
> An: cupertino at gmx.net
> CC: linux-poweredge at lists.
> Betreff: Re: Perc 5/I fatal firmware error - DATA Abort Exception
> found /sas-raid/R189337.txt
> 5.2.2-0072 - but it does not mention anything in this direction to be a
> problem or fixed.
> What does this error mean? Why must the card be replaced?
> Am Dienstag, den 10.07. +0200 schrieb cupertino at gmx.net:
> > haven't checked lately, but I think it is the most recent FW already.
> > you can try to re-flash the FW (or apply a newer one if there is any).
> > if it then happens again you need to get the card replaced.
From Jason_Wang2
Wed Jul 11 03:42:22 2012
From: Jason_Wang2
(Jason_Wang2 )
Date: Wed, 11 Jul :22 +0800
Subject: the disk name
is inconsistent across reboot with with H200 on
CentOS 4.8
Message-ID:
Server : R510
CentOS 4.8
Perc H200, non-RAID
Disk: 2T x12
Firstly the disk name is out of order like the following table.
Secondly, the disk name is inconsistent across reboot except sda.
For example, the second disk is sdd
and the name change to sdf after reboot.
We also tried the H200 driver from , it does not work.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists./pipermail/linux-poweredge/attachments/abb240a/attachment-0001.html
From jagiello.lukasz
Wed Jul 11 04:30:14 2012
From: jagiello.lukasz
(=?UTF-8?B?xYF1a2FzeiBKYWdpZcWCxYJv?=)
Date: Wed, 11 Jul :14 +0200
Subject: the disk name is inconsistent across reboot with with H200 on
CentOS 4.8
In-Reply-To:
References:
Message-ID:
> Server : R510
CentOS 4.8
Perc H200, non-RAID
> Disk: 2T x12
> Firstly the disk name is out of order like the following table.
> Secondly, the disk name is inconsistent across reboot except sda.
> example, the second disk is sdd
and the name change to sdf after reboot.
> We also tried the H200 driver from , it does not work.
Upgrade CentOS to more recent and start use UUID. You will have always
same UUID for hdd.
?ukasz Jagie??o
lukaszjagielloorg
From dell at epperson.homelinux.net
Wed Jul 11 07:04:31 2012
From: dell at epperson.homelinux.net (dell at epperson.homelinux.net)
Date: Wed, 11 Jul :31 -0400
Subject: the disk name is inconsistent across reboot with with H200 on
CentOS 4.8
Message-ID:
On Wed, July 11, , ??ukasz Jagie????o wrote:
>> Server : R510
CentOS 4.8
Perc H200, non-RAID
>> Disk: 2T x12
>> Firstly the disk name is out of order like the following table.
>> Secondly, the disk name is inconsistent across reboot except sda.
>> example, the second disk is sdd
and the name change to sdf after
>> reboot.
>> We also tried the H200 driver from , it does not work.
> Upgrade CentOS to more recent and start use UUID. You will have always
> same UUID for hdd.
You don't say what problem is presented by the wandering device names, so
my presumption (and Lukasz's) is that you're using device names in
/etc/fstab to identify the filesystems.
You can use UUIDs or labels to
avoid the problem and both are available in RHEL4, so I presume they're in
Centos 4.8.
See -U and -L options of tune2fs.
You can also mess with
udev rules to "fix" the device names, I think, but it's not worth it since
uuid/label is so easy and reliable.
From peljasz at yahoo.co.uk
Wed Jul 11 08:48:24 2012
From: peljasz at yahoo.co.uk (lejeczek)
Date: Wed, 11 Jul :24 +0100
Subject: update_firmware
Message-ID:
hi everybody
I'm trying update_firmware out for the first time, on a R815
yum install $(bootstrap_firmware) got me barely five
packages(firmwares?)
my question would be - how long does it usually take?
also - is it normal to see the same device
(ven_0x14e4_dev_0x1639 in this case) reported several time
during the update? if not would it mean the the software got
itself looped in somehow?
at the same time it reports after each 100%
"Done: Update success. You must perform a reboot for the
update to take effect."
but I understand one must wait till it is all finished(?),
only this one same devices appearing multiple time boggles
my mind, and it takes long time, is it normal?
any info greatly appreciated,
From giulioo
Wed Jul 11 08:56:42 2012
From: giulioo
Date: Wed, 11 Jul :42 +0200
Subject: DSET 3.2: OS detection, SFCB service mandatory
Message-ID:
PE-T620, CENTOS 6.x 2.6.32-220.23.1.el6.x86_64
I'm running DSET 2.2 and I realized DSET 3.2 is available on Dell web site.
I had 2 issues with DSET 3.2 install:
1) OS DETECTION
When trying to instal DSET there's a new OS detection
OS_NAME1=`cat /etc/issue | grep ESX`
OS_NAME2=`cat /etc/issue | grep SUSE`
OS_NAME3=`cat /etc/issue | grep Red`
Since we use CentOS, I had already rewritten /etc/redhat-release to match
what OMSA and other Dell software expect to find in it.
But now DSET looks at /etc/issue instead of /etc/redhat-release,
unfortunately we customize /etc/issue and it doesn't contain "Red Hat" or
"CentOS" strings.
Is looking at /etc/issue the new way all Dell software will use for OS
detection going forward?
2) New service mandatory:
Upon install this is printed on the screen:
The Small Footprint CIM Broker (SFCB) is a network service that enables
remote collection of system configuration information.
To perform the option that you selected, it is necessary to install and
start this service and leave it running in background for future
configuration collection
Continue installing/activating the SFCB on this system to listen for
incoming collection requests from clients.
Old versions of DSET would allow you to just run the diagnostics to send the
zip file to Dell support w/o installin the new version
not only didn't allow me to do that, but it wants to install a permanent
service (I already have OMSA 7 installed with its services running).
Is this new DSET service really necessary?
From phil.gardnerjr
Wed Jul 11 09:09:30 2012
From: phil.gardnerjr
(Phil Gardner)
Date: Wed, 11 Jul :30 -0400
Subject: DSET 3.2: OS detection, SFCB service mandatory
In-Reply-To:
References:
Message-ID:
funny out we were just discussing this, and someone else has the same
problem...
/etc/issue is the file you need to edit. looks like it just needs "Red" :)
On 07/11/ AM, Giulio wrote:
> PE-T620, CENTOS 6.x 2.6.32-220.23.1.el6.x86_64
> I'm running DSET 2.2 and I realized DSET 3.2 is available on Dell web site.
> I had 2 issues with DSET 3.2 install:
> 1) OS DETECTION
> When trying to instal DSET there's a new OS detection
OS_NAME1=`cat /etc/issue | grep ESX`
OS_NAME2=`cat /etc/issue | grep SUSE`
OS_NAME3=`cat /etc/issue | grep Red`
> Since we use CentOS, I had already rewritten /etc/redhat-release to match
> what OMSA and other Dell software expect to find in it.
> But now DSET looks at /etc/issue instead of /etc/redhat-release,
> unfortunately we customize /etc/issue and it doesn't contain "Red Hat" or
> "CentOS" strings.
> Is looking at /etc/issue the new way all Dell software will use for OS
> detection going forward?
> 2) New service mandatory:
> Upon install this is printed on the screen:
The Small Footprint CIM Broker (SFCB) is a network service that enables
remote collection of system configuration information.
To perform the option that you selected, it is necessary to install and
start this service and leave it running in background for future
configuration collection
Continue installing/activating the SFCB on this system to listen for
incoming collection requests from clients.
> Old versions of DSET would allow you to just run the diagnostics to send the
> zip file to Dell support w/o installin the new version
> not only didn't allow me to do that, but it wants to install a permanent
> service (I already have OMSA 7 installed with its services running).
> Is this new DSET service really necessary?
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge
> https://lists./mailman/listinfo/linux-poweredge
_____________________
Phil Gardner
PGP Key ID 0xFECC890C
OTR Fingerprint
BD0FE8B 36D614E3 D2F80538
From David.Harding at brighthouse.co.uk
Wed Jul 11 09:09:36 2012
From: David.Harding at brighthouse.co.uk (David.Harding at brighthouse.co.uk)
Date: Wed, 11 Jul :36 +0100
Subject: update_firmware
In-Reply-To:
References:
Message-ID:
I assume that you have set up the appropriate Hardware Repositories that
"power" the yum-based FW update.
I can't answer to the number of Packages installed, but it may simply be
that there are only 5 major components that require Firmware.
The update_firmware usually does take "some" my experience is that
it isn't unusual for it to run 5 minutes or longer on an R300.
The same device reported may be, for example, multiple Ethernet cards,
does that make sense in your case?
Generally, the only Firmware update that requires a reboot, and hence puts
out the message, is a BIOS update. Other FW is updated in-situ.
It might be useful for the list to see the output of your update_firmware
command. You need to specify option "--yes" to make the FW update happen,
otherwise, you just get a dry-run.
You might also run inventory_firmware to see what components it believes
are present, and what their current FW revisions are.
Hope that helps.
"lejeczek"
update_firmware
hi everybody
I'm trying update_firmware out for the first time, on a R815
yum install $(bootstrap_firmware) got me barely five
packages(firmwares?)
my question would be - how long does it usually take?
also - is it normal to see the same device
(ven_0x14e4_dev_0x1639 in this case) reported several time
during the update? if not would it mean the the software got
itself looped in somehow?
at the same time it reports after each 100%
"Done: Update success. You must perform a reboot for the
update to take effect."
but I understand one must wait till it is all finished(?),
only this one same devices appearing multiple time boggles
my mind, and it takes long time, is it normal?
any info greatly appreciated,
_________