Re: 2850 very slow cp compared to identical hardware
On Fri, December 10, 2010 22:22, Jefferson Ogata wrote: On 2010-12-10 20:40, Brian A. Seklecki wrote: 5A2D BIOS H433 and the fast one has fw 516A and BIOS H418. RAID adapter and container settings match across systems, as do e2fstune -l Just to confirm; same cache settings for each volume? And same RAID battery state? Will have to check on Monday--my VPN token seems to have given up the ghost. Luckily I'm not on call. I'm pretty sure I drilled into everything on the problem server and would have noticed a battery anomaly, but can't specifically recall checking it. If bad, that would negate the writeback setting, I guess. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
2850 very slow cp compared to identical hardware
We just had the PCI riser replaced on a 2850 because the embedded PERC 4 had failed. While reloading the Oracle applications, the DBA reported that 17Gb copy that took 10 minutes on the development server with identical hardware and software (to the extent possible), took over an hour on the prod system with the new board. He showed me strace cp results like: read(3, \6\242\0\0p\2C\4\27k\324\366\0\0\1\6\241\251\0\0\2\0\0..., 32768) = 32768 write(4, \6\242\0\0p\2C\4\27k\324\366\0\0\1\6\241\251\0\0\2\0\0..., 32768) = 32768 on the fast system and read(3, \6\242\0\0^H\5\35\340\250\257\270\0\0\1\4\375\265\0\0\2..., 4096) = 4096 write(4, \6\242\0\0^H\5\35\340\250\257\270\0\0\1\4\375\265\0\0\2..., 4096) = 4096 Trying to get clueful about the 4096 vs. 32768 differences and whether they have a bearing on the copy speed differences is presenting me with a steep curve. Can anyone shed any light on this for me? BTW, the only differences I'm aware of on the systems is that the slow system has PERC firmware 5A2D BIOS H433 and the fast one has fw 516A and BIOS H418. RAID adapter and container settings match across systems, as do e2fstune -l settings. No hardware errors showing up in /var/log/messages or dmesg. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: disk caddy's
On Wed, December 8, 2010 11:30, Michael Tiernan wrote: On 12/8/10 11:23 AM, Ted Taichuan Lu wrote: We bought these hot-swappable trays, which worked fine: http://www.provantage.com/datastor-dlpwrsata~7DTTS03K.htm That seems extreme when you can get them for less than half that here: http://www.scsi4me.com/dell-tray1.html You can get them for less than half THAT on eBay if you shop a bit to get the quantities you need. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: Consistent Network Device Naming for LOMs coming
On Tue, November 16, 2010 10:27, spike_wh...@dell.com wrote: On RHEL 3/4/5, it's even easier. You just modify the HWADDR= lines in /etc/sysconfig/network-scripts/ifcfg-eth*. Here's an example ifcfg-eth0 entry. HWADDR=00:24:E8:6D:FD:B6 This is what I do. And keep a file with mac addresses, server names, IP addresses, and interface names. Simple scripts can reach out and adjust all the device names from one place with a little PKI trust. Doesn't solve the install/firstboot case, though. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Perc 6/i Puncturing bad blocks
On Thu, November 11, 2010 10:25, Jacob P wrote: Hello, I'm having an issue with a PERC 6/i card and I was hoping to get some guidance from the gurus on this list. We're having an issue with the controller 'puncturing bad blocks', but it's 'remembering' the sectors after swapping out with a hotspare. Looks like the infamous and somewhat nebulous punctured stripe. Your PERC is presenting the RAID volume as an emulated hard disk, and when you end up with emulated bad blocks, they'll move around WRT the actual physical drives. The only sure way to get rid of them is said to be recreating the volume from scratch and reloading the files from backup. There are people participating on this list who understand this far better than I do, and I hope one or more of them elaborate for us. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: CentOS 5.5 - Deleted Partition
On Sat, October 30, 2010 12:28, Arno van der Veen wrote: But, if I do an fdisk l on /dev/sdb, I have no partitions listed. The kernel won't re-read the partition table if there are open partitions, so whatever you do, DON'T REBOOT (it'll be gone then). Do you know the particulars of the old partition table? If so, just re-run fdisk and recreate the partition(s) to match. If not, I'm not sure if there is a way to see what the running kernel thinks the partition table looks like. In my proc there is a partitions : cat /proc/partitions which in my case give an output like this: ban...@goloka-vrindaban:~$ cat /proc/partitions major minor #blocks name 80 78150744 sda 81 77902848 sda1 82 1 sda2 85 244736 sda5 8 321931264 sdc 8 33 1927768 sdc1 So, then you have at least the sizes (number of blocks) back then according to this faq run fdisk -l http://www.faqs.org/docs/Linux-mini/Partition-Rescue.html I hope you'll save your weekend.. ;-) I did this in June-July, the whole partition table on a mounted /dev/sda. Search the archive for subject Blew away my partition table for a thread that details what I encountered and the excellent advice I got, particularly from Bond Masuda and Jefferson Ogata. You can definitely recover from this. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: libcmpiCppImpl0 conflict
On Tue, October 12, 2010 20:56, Robin Bowes wrote: On 12/10/10 19:35, Aaron McKinnon wrote: libcmpiCppImpl0-2.0.0Dell-1.2.el5.i386 from installed has depsolving problems -- libcmpiCppImpl0 conflicts with tog-pegasus Error: libcmpiCppImpl0 conflicts with tog-pegasus I suspect one or both of two things: 1. you are trying to install an x86_64 RPM but an i386 rpm is already installed. 2. there is an i386 RPM missing from the repository. Uninstall tog-pegasus, unless you know you need it more than OMSA. It's probably gratuitous on your systems, was on mine. Previously on the list: http://lists.us.dell.com/pipermail/linux-poweredge/2010-April/042080.html ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: Advice for a debian server
On Tue, September 7, 2010 06:44, Morten P.D. Stevens wrote: On Tue, Sep 7, 2010 at 3:01 AM, Tim Connors tim.w.conn...@gmail.com wrote: But if you know what you're doing, often debian is better. Depends on your needs and skills. We run debian fine here, with no difficulty talking to the raid cards and hardware sensors etc that we use, and because debian is a far better quality distribution than redhat (and thus centos), and is a bit more engineered (rather than slapped together with 100mph masking tape) than ubuntu, you might get a lot better mileage out of it. FYI: RHEL is a commercial enterprise linux distri and debian is a not reliable opensource project with hobby developers. Hehehe. The origin of the Debian name is similar to that of many tattoos. Red Hat is not named after a Cornell jock strap. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: PE2850 RAID1 upgrade drives
On Sat, September 4, 2010 10:24, Stroller wrote: On 4 Sep 2010, at 13:15, Raymond Kolbe wrote: ... 1) Create a Ghost image of OS/data, etc. for backup and restore. 2) Turn off the server and replace both drives with the newer 300GB drives. 3) Turn on the server and create a new RAID1 array. 4) Restore the Ghost image from step 1. 5) Use gParted or another partition resizing program to increase my partitions. However, no one has confirmed that these methods worked for them. Now, both ways sound like they would work, but I am extremely nervous about this because I have also found forum postings and articles about having to manually copy over partition information, and that disk block sizes matter, etc. (not exactly sure about the technical issues here), etc. This is also a mission critical production server so uptime is key. So my question is, are either of the two methods above realistic, and/or has anyone actually upgraded RAID1 in a PE2850 or PE server before without having to reinstall their OS? I've definitely done this sort of thing with another model of PowerEdge, the 2800. I think I've done it with a 2850, although mine doesn't have the RAID key. The drives will just appear to the o/s as block devices - if you boot from a LiveCD (well, as long as it's one that supports the RAID controller) you'll see the current array as (something like) /dev/sda. Take a note of the current configuration, just so you're completely confident (e.g. `ls -l /dev/disk/* /mnt/floppy/file.txt`). Shutdown the system, slap the new drives in (don't remove the existing ones), create an array of them in the RAID BIOS, and reboot again to the Live CD. You'll see the existing /dev/sda as it was before (compare /dev/disk/by-id/* with what you had before) and a new /dev/ sdb. The RAID controller consolidates the drives (hardware RAID) and presents them to the o/s as the single /dev/sdb block device. You can simply `dd if=/dev/sda of=/dev/sdb`, shutdown the system, remove the original array, power up and change the boot device in the RAID BIOS and boot to the cloned system. I personally don't use Ghost - Linux has `dd` which is perfectly adequate. I trust it more than Ghost. You can ghost to backup image file on an external USB drive with `dd if=/dev/sda of=/mnt/seagate/ file.img`. Nor do I use gParted, but the command-line parted. `sudo parted /dev/sda p` should show that the new array is larger. It can be a pain to manipulate in Linux the partitions of Windows Server, as I've mentioned in the past. I'm tending to assume 2 system drives in a RAID1 here, so that you have enough empty bays for the two replacement disks. You can unmount and remove data arrays whilst you're upgrading the system drives. I perform all partition / filesystem resizes from the LiveCD, with the disks unmounted. DON'T do this sort of thing on a production system without a backup. This mailing-list posting confers no warranty, express or implied. If, like me, you're a lone IT consultant working on a client's only mission-critical server (or even one of your own) this kinda stuff can be tremendously stressful. There is potential for you to foul-up at any time if you just once confuse your source and destination drives. This demonstrates the need for backups constantly throughout the system's life - really, as soon as you've commissioned the system you should be taking backups, you should test them; you should do a full restore just to prove you can, before you have any important data on there. Of course there are many occasions when we are not so perfect, but this migration is perfectly manageable if you're careful; 99 times out of 100 there will be no problems, but it can be a bit nerve- wracking. You ought to be confident about this before you start, so if you can't get (or afford) someone more experienced to help then my best recommendation is to practice it on another system first. I got my 2850 at least 6 months ago, and they were going for less than £200 on eBay then - I wouldn't be surprised if they're less than £100 now. This is a really straightforward migration that most of the guys on this list - or any other experienced Linux system administrator - would have no trouble at all with. I'm surprised you can't find confirmation of this working (although I think few of us would use Ghost, if that's part of your search criteria) because I think there are probably people doing this on a daily basis with no problems. But one can't write exact instructions for you at one remove like this - the block devices may be named differently on your system, for example as /dev/hda instead of /dev/sda, and of course there's the liability that a single tiny omission can foul you up. But, yes, this technique, generally speaking, does work. I can vet pretty much everything Stroller says, have done a number of variations of this, often using g4l (Sourceforge) which just glues
Re: R710/PERC H700/H800/MD1200 disk naming
On Tue, August 3, 2010 09:41, Dameon Wagner wrote: On Tue, Aug 03, 2010 at 12:19:53PM +0100, John Hodrien scribbled in Re: R710/PERC H700/H800/MD1200 disk naming: LVM merely gives you options that you don't have without it. It's really not a pain; treat it simply and there's really very little to it. There's times I am annoyed by a lack of LVM on machines because I find it handy to use what LVM can offer me, but it's too late. There aren't times I find the inverse to be the case. Not an overriding argument, but I've found the inverse to be the case in imaging scenarios. It's simple to backup/restore /dev/sdax from a partition image, /dev/mapper/VolGroup00-LogVolxx not so much. OTOH you can snapshot LVMs without having to unmount them. But I'm a dinosaur with an IS degree from 30 years ago, and my mind just wraps around physical partition scenarios better. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: OSMA does not work on PowerEdge 1435SC
On Sat, July 31, 2010 15:05, Lazy wrote: omsa 6.2 may not support SC1435 but 5.5 works on PE SC1435 fine #omreport chassis info Chassis Information Index: 0 Chassis Name : Main System Chassis Host Name: BMC Version : 1.78 Chassis Model: PowerEdge SC1435 Chassis Lock : Present Chassis Service Tag : XXX Chassis Asset Tag: Flash chassis identify LED state : Off Flash chassis identify LED timeout value : 300 -- Interesting. How did you install it? IIRC, 5.5.0 was what was shipped with my old 1435SC servers, and reported not a supported server when you tried to install it. Same thing happened if you downloaded 5.5.1 and tried with that. Dell support was adamant at the time that the 1435SC was not supported in spite of having shipped OMSA with it. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: OSMA does not work on PowerEdge 1435SC
On Thu, July 29, 2010 10:25, Nick Solin wrote: Yes, but no matter what I have done the OSMA does not work on my computer. I've read most of the OSMA documents and they tell you how to install and use the OSMA but they skip any sort of configuration for the OSMA. For instance when I try to use omreport: [snip] The ones I need most are fans and temps. I've read through a few of the letters in the archives pertaining to the 1435SC, but none have helped. Other than the fact that it's OMSA, not OSMA, your original subject line was correct: OMSA does not work on PowerEdge 1435SC. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: OSMA does not work on PowerEdge 1435SC
On Mon, July 26, 2010 08:21, Nick Solin wrote: Subject: OSMA does not work on PowerEdge 1435SC Correct. This has been discussed more than once on the list, check the archives. It's unfortunate that there's Dell doc that says the 1435SC is supported for systems management, implying that OMSA should work. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Vendor provided support
On Tue, July 20, 2010 12:41, Matt Domsch wrote: On Mon, Jul 19, 2010 at 05:09:47PM -0700, Wiley Sanders wrote: Thanks for the quick replies. I only bought RHEL support to guarantee Server Manager compatibility. It's been a while since I bought a new Dell, and I was very pleased that Server Manager worked right out of the box this time and didn't need ANY fiddling to get working. It survived the RHEL4 to 5 upgrade too. It probably works on CentOS as well, but I really need Server Manager to work consistently in this hosts' case. We actually have a site license for Novell which includes SuSE. Is Server Manager support as solid in SuSE as it is in RHEL/CentOS? I hardly ever see anyone asking about it on this list. Yes, OMSA is fully supported in both environments, albeit only on 64-bit SLES, not 32-bit. Which is really kind of amusing, given that one of the bugaboos of running it on 64bit RHEL is that it requires a bunch of 32bit packages. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Blew away my partition table
On Wed, June 30, 2010 09:31, J. Epperson wrote: On Tue, June 29, 2010 22:16, Jefferson Ogata wrote: On 2010-06-30 01:53, J. Epperson wrote: On Tue, June 29, 2010 21:27, Jefferson Ogata wrote: Number Start End SizeType File system Flags 1 63s 401622s 401560s primary ext3 boot 2 401625s 139299608s 138897984s primary ext3 3 139299616s 143380124s 4080509sprimary swap I would say those end sectors on partitions 1 and 2 should be one less than the following partition's start sector. The end sector of partition 3 looks correct; though the last sector on the disk is 143380479, when you round down to a cylinder boundary you end up at 143380124. I was thinking the same thing, but that's what the parted rescue found, so I assumed it was correct. Looking at another F12 system, what you say is how that one is. Not sure what to do, try it as is or make the adjustment. I do notice from the other system that I should probably mark the swap as FS type linux-swap(v1). The other system looks like: I don't think it would actually matter with partition 1. If your filesystem has a 2kB or 4kB block size, then those extra 2 sectors won't ever be addressed. With partition 2, however, the additional 7 sectors extend the volume by one or two filesystem blocks (with 3 extra sectors on the end). I would go ahead and extend the partitions to the n-1 values. It's always safe to have a filesystem on a block device that is larger than the filesystem, but the converse is not true. You can also check the superblock with tune2fs -l to see how big the filesytem thinks the block device is. Block count * Block size / 512 should be = the number of sectors. I understand and will take that advice. Hilariously, although gparted blithely let me blow away the previous partition table without a whimper and parted let me build a new one with the partitions mounted, parted now refuses to let me adjust the partition end points because they are mounted. I suppose I could blow the whole thing away again and redo from scratch, but I think I'm going to boot rescue and do with it with them not mounted. Just got around to doing the live boot and making the adjustments suggested by Jefferson Ogata. I ended up removing the partitions and adding back with correct end points rather than using move in parted. All is well. I did have to manually redo swap after reboot with: mkswap -c -Umy_uuid /dev/sda3 with uuid gleaned from /etc/fstab. Thanks to all who offered help, and particularly to Jefferson Ogata and to Bond Masuda. Happy Fourth of July. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Blew away my partition table
On Tue, June 29, 2010 22:16, Jefferson Ogata wrote: On 2010-06-30 01:53, J. Epperson wrote: On Tue, June 29, 2010 21:27, Jefferson Ogata wrote: Number Start End SizeType File system Flags 1 63s 401622s 401560s primary ext3 boot 2 401625s 139299608s 138897984s primary ext3 3 139299616s 143380124s 4080509sprimary swap I would say those end sectors on partitions 1 and 2 should be one less than the following partition's start sector. The end sector of partition 3 looks correct; though the last sector on the disk is 143380479, when you round down to a cylinder boundary you end up at 143380124. I was thinking the same thing, but that's what the parted rescue found, so I assumed it was correct. Looking at another F12 system, what you say is how that one is. Not sure what to do, try it as is or make the adjustment. I do notice from the other system that I should probably mark the swap as FS type linux-swap(v1). The other system looks like: I don't think it would actually matter with partition 1. If your filesystem has a 2kB or 4kB block size, then those extra 2 sectors won't ever be addressed. With partition 2, however, the additional 7 sectors extend the volume by one or two filesystem blocks (with 3 extra sectors on the end). I would go ahead and extend the partitions to the n-1 values. It's always safe to have a filesystem on a block device that is larger than the filesystem, but the converse is not true. You can also check the superblock with tune2fs -l to see how big the filesytem thinks the block device is. Block count * Block size / 512 should be = the number of sectors. I understand and will take that advice. Hilariously, although gparted blithely let me blow away the previous partition table without a whimper and parted let me build a new one with the partitions mounted, parted now refuses to let me adjust the partition end points because they are mounted. I suppose I could blow the whole thing away again and redo from scratch, but I think I'm going to boot rescue and do with it with them not mounted. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Blew away my partition table
Arrived home very tired and in a lapse of judgement tried to configure a new USB backup drive on my PERC3 based home server, with a new cat roaming between me and the monitor. Created a new partition on the existing /dev/sda instead of the new /dev/sdb. System is still running, and Im doing an rsync to the new drive now. Can some kind soul help me remember how to repair this surgically instead of rebuilding the filesystem and reloading it? If not, I deserve it. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Blew away my partition table
On Tue, June 29, 2010 21:01, Jefferson Ogata wrote: On 2010-06-30 00:54, J. Epperson wrote: Still have to do a grub-install /dev/sda (probably after booting rescue). I won't get around to testing this on a reboot for a day or two, need to wait until I know I'll have time to restore from an image I took a few months ago and reload from rsync if I didn't get it right. Not sure you'll need the grub-install. I don't know why the MBR would be harmed. I read your posts regularly, and learn from you often. Does the rest of it look right, or at least plausible? ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: unsupported
On Mon, June 28, 2010 14:01, Robin Bowes wrote: On 28/06/10 18:42, Simon wrote: Greetings, I know this is unsupported, but I'm trying to install osma on a fedora core 12 system. Any pointers would be greatly appreciated. How about a bit more detail? What did you do? What happened? What did you expect to happen? For more than 20 years I've been hammering into techs, systems engineers, and users, er, customers, that those are the three questions that must be answered by any usable problem report. I can't even remember where I first saw them succinctly listed, but I think it was on some early BBS. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: PERC S300 - can it be made to work?
On Sat, June 26, 2010 22:59, Rodrigo Trevisaneli wrote: Well, I started that thread and DELL told me this board will not run in Linux. They will send to me a SAS 6/iR (I guess) as replacement. I dont know about this alternative methods. Here, I was in hurry to put that server in production, so the solution was: remove the board, install 2 disks in the Serial ATA ports on the main board, and setup a software RAID1 with CentOS 5.5 64. As I could understand (may be wrong) this board does a Software RAID in Windows, so I could not see any advantage in keep this board in Linux, since Linux already has built in Sofware RAID. Thanks for clueing us in, Rodrigo. The Dell white paper on the Sxxx cards does imply this, but I'm shocked that they've put the PERC label on a fakeraid card. Perhaps they've done it before, but I've worked with PERCs since the original in the PEx300 (still have one heating the basement at my church), and have never encountered one that wasn't a full hardware raid implementation. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Buyback Program?
On Fri, June 18, 2010 14:03, Cris Rhea wrote: From: Chase Bolt cb...@denirostaff.com Subject: Buyback Program? We are looking at replacing about 50 servers and was wondering if Dell has a buyback program? Or does anyone know of a company that purchases old Dell equipment? I don't know about Dell itself, but I'd suggest: Stallard Technologies (http://www.stikc.com/We-Buy) This Old Store (http://thisoldstore.com/Vendors.shtml) I've used both of these companies to purchase older Dell equipment. They're decent to deal with. I can attest to Stallard also. I'm still running machines bought from them 5 years ago. They're good merchants, so I'd expect they're good to sell to as well. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: anyone tried converting PE1900 to PE2900?
On Sun, June 6, 2010 18:24, Bond Masuda wrote: i might be able to get my hands on a PE1900 w/ PERC5/I for a few hundred US$, but it would be immensely more useful to me if it also had the hotplug SATA/SAS drive cage/backplane and dual power supply. i'm just wondering what it would take to convert the 1900 to basically what is a 2900. has anyone done this before? would you happen to have a parts list handy? searching parts catalog on Dell's website isn't always that helpful There are 2950 and 2900 units on eBay, looks like they go for about $400-800 without drives. I mention this because a number of them have the original specs in the ads, with part numbers for power supplies, backplanes, etc. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: dell 2850 initrd problem.
On Fri, June 4, 2010 12:08, Jefferson Ogata wrote: On 2010-06-04 15:42, Ron Croonenberg wrote: it says that /dev/sda2 is an LVM volume In case it isn't clear to you, BTW, this means that /dev/sda2 is NOT /. ?Does it? ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: dell 2850 initrd problem.
On Fri, June 4, 2010 13:03, Jefferson Ogata wrote: On 2010-06-04 16:58, Robin Bowes wrote: On 04/06/10 17:51, J. Epperson wrote: On Fri, June 4, 2010 12:08, Jefferson Ogata wrote: On 2010-06-04 15:42, Ron Croonenberg wrote: it says that /dev/sda2 is an LVM volume In case it isn't clear to you, BTW, this means that /dev/sda2 is NOT /. ?Does it? Hmm, I queried that statement too. Why does this mean that /dev/sda2 is not / ? As I understand it, the default RH/Fedora install is two partitions: a small /boot, and the rest an LVM PV assigned to a VG (VolGroup00) with root on an LV inside VolGroup00 ? Regardless of default install layout, we have a bad superblock on /dev/sda2 and /dev/sda2 marked as an LVM device. The evidence is strong that / is an LV within the PV that is on /dev/sda2. If you tried to recover a superblock directly on /dev/sda2 you would wipe out who knows what. Ah. Quite literally, you're correct. You didn't say that /dev/sda2 did not _contain_ /. This kind of mess is why I always blow away the default PV/LV scheme in the installer and make / on a physical partition. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: Mounting an LVM disk
On Mon, May 24, 2010 13:56, Bond Masuda wrote: If your disk were intact, yeah, you should be able to vgimport the volume group and mount it. But the partition table results you're seeing are consistent with someone trying to clone a 1Tb disk to a 2Tb one and getting the source and target mixed up, overwriting the partition table on the 1Tb with the table from the 2Tb. In which case, fuhgeddaboudit . well, actually, if the data portion is untouched, if one can guess or restore the partition table, everything should be just fine. if the partition table has gotten corrupted, mistakenly overwritten, etc., I would make a 'dd' image of it and mess with the image or copy of the image. there is also 'gpart', which can scan and try to guess what the partition table was originally. you might need to figure out if the entire 1tb disk (/dev/sdc) was used as a LVM2 PV, or if the disk was a single partition (/dev/sdc1) marked as 'lvm' and the partition was used as a PV. if the former, you don't need to worry much about the partition table. Some good points, but having had this hole in my own foot, I'll say that it's very unlikely that it's _just_ the partition table that got wiped. I also never had any luck getting a partition editor to work with a disk that had a table saying it was bigger than it actually was. Always had to wipe it at a hardware level to get it repartitioned. I hope OP's luck is better. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Liquidation Sales Cisco AS5350 AS5400 XM HPX
He's aka Russ Bazarre, aka nete...@hotmail.com. He's been doing this for quite some time. On Sun, May 23, 2010 17:06, Support @ Technologist.si wrote: Abusement of this forum is rewarded by filing reports @ several rbl-db your isp. Op zondag 23-05-2010 om 09:16 uur [tijdzone -0700], schreef techres...@att.net: We are accepting best offers on all Cisco have more than 40 gw's in stock Cisco VOIP Gateways Guaranteed Lowest Prices World Wide Techresell will give you $1000 discount from any quote you get from other vendors...why we are the lowest cost voip provider WE operate on margins of only 5% profit and give you 1 Year warranty full technical support Free Network Design even if you do not buy from us WE stock all AS5300, AS5350, AS5400, AS5850 gateways access servers AS53-4E1-120-AC-V $2700 OBO AS53-4T1-96-AC-V $2300 AS535-8T1-192-AC-V $5150 AS535-8E1-216-AC-V $5200 OBO AS5400-8E1-240-AC-V $5500 OBO AS5400-8E1-216-AC-V $5000 AS54HPX-CT3-648-AC-V $4500 AS54HPX-8T1-192-AC-V $7500 AS54HPX-16T1-384-AC-V $10,200 AS54HPX-8E1-240-AC-V $7800 AS54HPX-16E1-492-AC-V $12,500 OBO AS54XM-CT3-648-AC-V $14,000 AS54XM-16E1-492-AC-V $19,500 many in stock NEW in Box AS54XM-16T1-384-AC-V $19,380 New in Box AS5850 all models in stock DC units in stock available for all AS5400 chassis We have any combination you need email us what you need and we will send you a quote same day SS7 C7 solutions Softswitch and Billing solutions from $2500 usd Factory Refurbished Cisco and New Cisco 1 Year warranty Free Network Design and Support CCIE CCNA engineers on staff techres...@att.net 954 924-1800 tel USA ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: disabling boot devices on poweredge servers?
On Wed, May 5, 2010 20:57, Adam Nielsen wrote: I think most if not all machines have a hardware method to reset the BIOS settings (jumper, dipswitch, etc.) At the very least simply popping out the CMOS battery for a few seconds (while the machine is off) will do it. Yes, securing the chassis is the only way around this, but then if your chassis is secured properly, nobody is going to be able to boot off a CD or USB drive anyway. Or remove your hot swappable disks and walk off with them ;-) And likewise, in any environment where subversion of the boot process is a concern meriting such lockdown, the network should be secured in such a fashion as to prevent rogue PXE boot vectors. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: CPU pinning on Xen
On Wed, April 14, 2010 01:29, Tapas Mishra wrote: Hi,I have a Quad Core CPU Dell PowerEdge R710 which has 4 Virtual Hosts running on top of it. I want to allocate a CPU core to each of the hosts.How can I do that on Xen.I am using Debian Lenny. 1) RTFM 2) Post to an appropriate forum/list, like xen-users 3) RTFM ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: how to access 4 application servers web based.
I've kind of lost track of how this relates to Linux on Poweredges. You might want to try the Xen-users list: http://lists.xensource.com/mailman/listinfo/xen-users On Mon, April 12, 2010 08:24, Tapas Mishra wrote: I read a lot of blog and tutorials about name based and IP based hostings and also about mod_proxy. But I am unable to do. Here is what I am trying to do. I have a webserver on public IP.Which is running Xen on it. There are 4 Guest Operating systems installed on top of Dom0 which are Dom1,Dom2,Dom3,Dom4 These are application servers which are going to serve the requests that come from the main server.Which is Dom0. I right now have no clue. All I see is It works on all 4 of the hosts. On my LAN on any machine on same subnet if I do http://Ip of Domu1 message comes [code] It Works [/code]. Same thing happens with remaining 3 DomU's. http://IP of DomU2 http://Ip of Domu3 http://Ip of Domu4 in browser from LAN gives me a message [code] It works. [/code] What do I need to do on Dom0 so that requests are forwarded to the appropriate DomUs apache2 is running on all of them including Dom0. -- Tapas ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: how to access 4 application servers web based.
On Mon, April 12, 2010 09:56, Tapas Mishra wrote: Ohh sorry about that I wish if some one who are using PowerEdge for this may let me know any how by the time you messaged some one replied and suggested to use apache proxy. Since you'll need help with that, I'd suggest posting on the Apache list: http://httpd.apache.org/userslist.html ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: ENCLOSUREWARN
On Fri, March 26, 2010 08:06, mohan_g_mur...@dell.com wrote: Hi Nick, Looks like you got an alert from the LRA you had set. Check the alert log in OMSA to figure out what went wrong. And also check the Enclosure and it's components in OMSA to see which component of Enclosure had went wrong. Below is the message(alert) reference guide which explains the alerts and corrective actions. http://support.dell.com/support/edocs/software/svradmin/6.2/en/MSG/HTML/ msgch40.htm#wp1194853 Thanks, Mohan -Original Message- From: linux-poweredge-boun...@dell.com [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Nick Lunt Sent: Friday, March 26, 2010 5:03 PM To: linux-poweredge-Lists; linux-poweredge-Lists Subject: ENCLOSUREWARN Hi folks in the docs the only mention I can find of ENCLOSUREWARN is the following Sets actions when an enclosure detects a warning value. I've just had an email from OMSA specifying ENCLOSUREWARN, can anyone tell me what this means please ? Nick, did you find any reference to ENCLOSUREWARN in the doc cited by Mohan? I didn't. I've seen this alert before and not been able to track it down. I can find the event=enclosurewarn doc, but it doesn't shed any light on what triggers it. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: Changing BIOS Boot Order from Linux Command Line w/out Complete OM Install
On Thu, March 25, 2010 14:15, Donald Harper wrote:
dmidecode -s system-serial-number
gives me the Service tag number on my host. RHEL 5, M610...
or:
dmidecode | grep -A4 'System Information' | tail -n1 | awk '{print $NF}'
if you have an older version of dmidecode.
Now, resetting it is a different ball of wax...
And that's the ball of wax I need to melt. Original post stated that, I
guess I trimmed too much in my rant about the Dell repos. I have means of
querying service tag, but it's blank on systems where MB has been
replaced, under warranty, by Dell field support.
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Re: External array showing as /dev/sda
On Mon, March 22, 2010 00:22, Matt Domsch wrote: On Sat, Mar 20, 2010 at 03:17:52PM -0400, David Hubbard wrote: Got a PowerEdge T510 with internal raid plus an H800 controller hooked to an MD1200 external array. Trying to install centos; raid controllers are bus 2 device 0 internal bus 7 device 0 external During setup its identifying /dev/sda as external storage which I don't want. Is there anything I can tweak to make it detect the storage in an order that results in the internal being /dev/sda? Aside from the great suggestions in this thread already (install with the external enclosure disconnected, make sure BIOS boot order is set to use the internal disk first, set up your initrd to load drivers for the internal disk controller first), there's yet another trick which Dell included in Anaconda exactly to handle this... http://linux.dell.com/installermagic.shtml The interesting part is this kickstart directive: part /boot --fstype ext3 --size=1844 --onbiosdisk=80 --asprimary where 80 is the (hex) value for the first int13 disk. And of course you set the int13 disk order in BIOS SETUP (or using DTK). The magic bit is that you really want to use parted or fdisk to first create an empty partition table on every (logical) disk in the system. You don't want to just write zeros to the MBR of every disk. parted and fdisk know how to fill in a unique signature in the appropriate MBR field, which anaconda uses to recognize and pair up the BIOS list of disks with the Linux list of disks. And the Oscar for Best Performance in a Contentious Thread goes to ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: External array showing as /dev/sda
On Sat, March 20, 2010 17:05, David Hubbard wrote: From: linux-poweredge-boun...@dell.com Probably. But it may not be worth it. Why does it matter to you? Not saying that it doesn't matter, just trying to understand why. Getting it to be /dev/sda during install, for instance, wouldn't guarantee that it would be that when you booted the installed kernel. Because I can't figure out how to get the OS installed otherwise. As it stands currently, I would like to use RAID 50 on both the internal and external arrays. Dell's raid controllers do not allow you to create anything other than one logical drive presenting 100% of the physical raid 50 array size to the OS as a drive, so basically this means my external /dev/sda drive shows as 24 TB, my internal /dev/sdb drive shows as 4.5 TB. So, trying to install RHEL 5.4 x86_64, the LVM wizard cranks up and since the external array is /dev/sda I un-check the box to tell the installer to not look at that 'drive'. I leave /dev/sdb checked which is my 4.5 TB internal drive. Proceed and then the installer tells me my boot drive is managed by GPT but the system cannot boot with GPT and I'm done. As far as I can tell there is not currently a supported way to get RHEL 5 installed with the server in UEFI boot mode, or at least I can't figure it out, I did try putting it in UEFI mode but it refused to boot off an ISO on DVD or a native DVD. So you can't boot off a GPT drive and you can't install to a MBR drive lol. As best I can tell, this leaves me with the only option being get internal to show as /dev/sda, waste a bunch of money by being forced to reconfigure that array as a RAID 1 of two drives for the sole purpose of being able to present a 'drive' of less than 2 TB to the OS so RHEL will install on it using MBR as /dev/sda, do the remaining six disks as RAID 50 and let them become /dev/sdb, keep the external array as RAID 50 /dev/sdc now. I can't accomplish this without the internal raid controller being /dev/sda though so the installer will make it past the partitioning step. Also quite unhappy that the two 750 GB drives that should have been part of my RAID 50 internal will effectively be used to store about 2 GB of boot and OS files but I think I'm stuck. I'm somehow missing how getting the non-installable smaller GPT VD to be /dev/sda will change that scenario. The other responder echoed one of my initial thoughts when he suggested turning off the external array. That should do it. I did run across a post over on the Centos forums where a guy said that he got around a Centos refusal to install on GPT by dropping to an alternate console (Ctrl-Alt-F2) and wiping the beginning of the drive with dd if=/dev/urandom of=/dev/sda. Said that on reboot it didn't quibble about the drive. No other details; you might end up with only 2Tb usable as I think about it. Perhaps worth a try. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: External array showing as /dev/sda
On Sat, March 20, 2010 15:17, David Hubbard wrote: Got a PowerEdge T510 with internal raid plus an H800 controller hooked to an MD1200 external array. Trying to install centos; raid controllers are bus 2 device 0 internal bus 7 device 0 external During setup its identifying /dev/sda as external storage which I don't want. Is there anything I can tweak to make it detect the storage in an order that results in the internal being /dev/sda? Probably. But it may not be worth it. Why does it matter to you? Not saying that it doesn't matter, just trying to understand why. Getting it to be /dev/sda during install, for instance, wouldn't guarantee that it would be that when you booted the installed kernel. There's a seminal paper by Matt Domsch of Dell, about Linux device naming at http://www.dell.com/downloads/global/power/ps1q07-20060392-Domsch.pdf That might give some insight. It's several years old, but pretty much still valid, although UUIDs seem to be displacing labels for identifying partitions for mounting. I still use labels. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: swapping RAID1 disk and hot-swap disk for restore image test
On Fri, March 19, 2010 04:33, jens_he...@dell.com wrote: It should work this way: 1. goto RAID BIOS 2. offline both RAID1 HDDs 3. create a RAID0 in hotspare drive 4. change 'bootable VD' 5. do your restore tests To go back to your original configuration I would recommend to just online one of your both RAID1 HDDs and rebuild the other if all is fine. Just to preserve as many options as possible, I'd return the RAID0 to hotspare status, online one of the RAID1 HDDs, and let it rebuild on the hotspare. Then designate the offlined drive as new hotspare. If something bad happens during the rebuild, you still have the offlined member untouched. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: RAID-5 and database servers
On Thu, March 11, 2010 11:17, Dan Pritts wrote: On Tue, Mar 09, 2010 at 04:54:44PM -0600, John G. Heim wrote: Has anyone configured a database server with RAID-5? Is it really a bad idea http://www.orafaq.com/wiki/RAID Which says that unless money is no object, go with RAID 5. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Dell R710 + PERC 6/i Raid Controller Card + Linux Fedora 11/12 System
On Mon, March 1, 2010 22:29, Edward S.P. Leung wrote: Dear Wadud, What different between MegaCLi and LSiutil ? MegaCLi for megaraid-driven interfaces LSIutil for other, e.g. mpt-driven, interfaces ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Dell R710 + PERC 6/i Raid Controller Card + Linux Fedora 11/12 System
On Tue, March 2, 2010 20:20, Edward S.P. Leung wrote: Dear you, Would you mind to tell me how to install and run it ? Is there doc ( quick giude ) for installing and running ? Thanks ! Edward. On Tue, March 2, 2010 09:23, Edward S.P. Leung wrote: Hello, So, which is suitable for the raid adapter ( PERC 6/i ) and FC Linux system ? Perc 6/i is megaraid. Please ask your questions on the list. http://tools.rapidsoft.de/perc/perc-cheat-sheet.html Has links to the software and the User Guide, as well as explains basic usage. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: Centos Update 1950 wont boot 2.6.18-164.11.1.el5
On Tue, March 2, 2010 20:58, Steve Tempest wrote: Hi, I took your advice and tried recreating the initrd without any success. I ended out performing the upgrade on another server with identical hardware and copying the boot files over from it and that has sorted out my problem. Thanks for the help Sorry the hunch didn't work out for you, glad you found a path out of the darkness. Apparently something else in the install/postinstall of that kernel broke. Good chance that removing and reinstalling the new kernel rpm would also have fixed it. But that's another hunch, and I'm 0-1 with you already ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: Third-party drives not permitted on Gen 11 servers
On Wed, February 10, 2010 12:27, Joe Gooch wrote: -Original Message- From: linux-poweredge-boun...@dell.com [mailto:linux-poweredge- boun...@dell.com] On Behalf Of J. Epperson Sent: Wednesday, February 10, 2010 11:37 AM To: Seriously, some of us used to re-flash some of the older LSI PERCs with the firmware for their LSI-branded counterpart. Could something like that be a possibility here? Could the H700 be reflashed with the LSI Megaraid 9260/9280 firmware? I guess someone would have to risk a brick to find out. I'd rather flash the drive firmware. If it's really superior with Dell equipment, why not make the firmware available? It's not like Dell is manufacturing the drive, and they already provide drive firmware upgrades on the support site. Agreed. But the controller firmware is available. If Dell specified/required certain mfr/drive models and made their proprietary firmware available to reflash them from the mfr default firmware, I don't think they'd get nearly the backwash they're going to have from their current stance. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: CPU Upgrade for Dell PowerEdge 1435SC
On Mon, February 8, 2010 16:54, Jonathan B. Horen wrote: First of all, it would be a Good Thing if the mailing-list archives were made searchable; this might have obviated my posting this message. However, it's not (yet) so. Sure they are. http://tinyurl.com/yljevh2 ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Third-party drives not permitted on Gen 11 servers
Top posting due to the length of Stroller's eloquent and thoughtful post. Well said, and entirely seconded. I think it's particularly bad timing for Dell to be doing this at a time when Oracle has purchased a hardware arm and is picking off Red Hat Linux (a Dell partner) software support customers with lowball pricing. If the hardware is going to be proprietary anyway, why risk having multiple parties accountable for OS/drivers/hw support, a risk that has plagued the Unix/Linux community since the onset of X86 platforms? I'm sure there are others who experienced the nightmare of SCO Unix on EISA bus machines with third part cards and fourth party drivers. Open source has vastly improved this, but in commercial production environments there's always a yearning for accountability for support. Take away the open hardware part of the equation and the choices appear different. I'm just sayin On Sat, February 6, 2010 08:26, Stroller wrote: Thanks for posting this. That Dell are doing this seemed to be hinted at in another post a couple of days ago, and I wasn't sure if I was reading right. Out of concern that I might be miscomprehending I really wanted to do some homework before kicking up a fuss. I have to say I'm gob-smacked to read this confirmed. £79 ($123) for a 250GB SATA hard-drive is, these days, a little pricey. We can get those for £25 anywhere else, but we tolerated the mark-up when we ordered recently because Dell have always been good value to us otherwise - let them have their cream. We bought a handful of these small drives because we figured they'd include the caddies. Those are worth £25 or so to us (that's what we paid for secondhand caddies for a 4 year old server last month), so we bought a good number of low capacity drives to include those, expecting to upgrade the drives themselves in a year or two. Markups on larger drives are taking the piss, however. £220 for 1TB - £53 elsewhere, £740 for 2TB drives that are £100 from the local warehouse! And the commodity drives have longer warranties! Dell give only 1 year as standard, AND THE PRICE ISN'T EVEN THE POINT! The point is the lock-in - if you sell us something that takes SATA hard-drives, I expect ANY standard SATA hard-drive to run in it. Why wouldn't it? I have to say I'm a bit gob-smacked by this. Half of me wants to refuse to accept Dell's delivery on Monday, half of me figures this ain't such a big deal; we'll tolerate the limitation on this machine maybe it'll all blow over. I'm just completely WTF!?!? over this, I'm at a loss how to respond. We certainly won't buy another machine from Dell whilst they carry this policy. I just find it completely stunning that Dell, without some kind of a warning, would sell me a SATA computer that doesn't accept standard SATA drives. I've spent years defending Dell. I encounter people who assume from the price that Dells are low-quality mass-produced crap, and I correct them. When someone has (rarely) told me a horror story of shitty customer service from Dell, then I have replied that every manufacturer has some dissatisfied customers; that might not reassure the recipient of bad service, but I discourage other people I meet from taking these anecdotes at face value, and contrast with the great customer service I have always experienced from Dell. I cannot count the number of computers Dell have sold on my recommendation. In the last fortnight I have dropped a software product (for Windows) that I have deployed at hundreds of sites. It's no longer part of new installs, it's being removed replaced on systems as they come in for service. Other people I meet tell me they're dropping the same software now, too. I guess I saw this coming 18 - 24 months ago, when I was cussing the vendor for a new feature, and asking out loud what did they do _this_ for?. I was cussing them a year ago, and within the last 6 months the bugs in their software have *really* been taking the mickey. This really feels like Dell going the same way. I drafted a rant about that vendor in (I see from my notes) June 2008, and never quite got around to polishing it and blogging it. Hopefully, since I've found the time on this quiet Saturday morning to complete this email, someone at Dell will bother to read it. Stroller. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Public key for Server_BIOS rpm is not installed
On Wed, February 3, 2010 20:44, Rodney McKee wrote: Updating the BIOS etc on an RHEL systems results in the following: yum install $(bootstrap_firmware) ... Package Arch Version Repository Size Installing: 32_Bit_Diagnostics_componentid_00196_for_system_ven_0x1028_dev_0x0235 noarch5130.1-1 dell-omsa-indep3.9 M Lifecycle_Controller_componentid_18980_for_system_ven_0x1028_dev_0x0235 noarcha00-1 dell-omsa-indep5.2 M OS_Drivers_Pack_componentid_18981_for_system_ven_0x1028_dev_0x0235 noarcha00-1 dell-omsa-indep 70 M SAS_Backplane_Firmware_componentid_11204 noarcha01-21 fwupdate 1.7 M Seagate_3_5_15K6_SAS_450GB_DU_componentid_15305 noarcha05-21 fwupdate 2.2 M Server_BIOS_11G_componentid_00159_for_system_ven_0x1028_dev_0x0235 noarch1.3.6-21 fwupdate 3.4 M iDRAC6_componentid_20137_for_system_ven_0x1028_dev_0x0235 noarcha02-1 dell-omsa-indep 37 M Installing for dependencies: dell_ie_maser_diags noarch1.0.8-1 dell-omsa-indep278 k dell_ie_maser_dp noarch1.0.8-1 dell-omsa-indep278 k dell_ie_maser_usc noarch1.0.8-1 dell-omsa-indep278 k dell_ie_nitrogen noarch1.0.8-1 dell-omsa-indep677 k Transaction Summary Install 11 Package(s) Update 0 Package(s) Remove 0 Package(s) Total size: 125 M Total download size: 3.4 M Is this ok [y/N]: y Downloading Packages: Server_BIOS_11G_componentid_00159_for_system_ven_0x1028_dev_0x0235-1.3.6-21.noarch.rpm | 3.4 MB 00:07 warning: rpmts_HdrFromFdno: Header V4 DSA signature: NOKEY, key ID 5e3d7775 fwupdate/gpgkey | 1.4 kB 00:00 Public key for Server_BIOS_11G_componentid_00159_for_system_ven_0x1028_dev_0x0235-1.3.6-21.noarch.rpm is not installed yum --nogpgcheck install $(bootstrap_firmware) will make it work. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: support.dell.com out to lunch?
On Fri, January 29, 2010 12:10, Matt Domsch wrote: On Wed, Jan 27, 2010 at 10:17:21AM +, Stroller wrote: Since this is a concern, where does Dell stand upon source releases? Dell uses and contributes to open source software in a lot of ways - including using the SBLIM and openwsman stack on Linux for future systems management projects. The iDRAC itself is running Linux (yes, source code is available, minus any non-open-source components of course). But there are also components which are not open source licensed, for a variety of reasons (strategic choice, license by the authors if not Dell, ...). Over time we have made more and more of our systems management software either open source or at least more Linux-friendly, and I expect that trend to continue. The overall hardware segment support for Linux is quite spotty, and IMHO Dell is one of the brighter spots. In addition to their active Linux support for their server and laptop product lines, they also contribute, for instance, Matt. Who pretty much wrote DKMS, contributes to maintenance of a number of kernel modules, and sits on the Fedora Projects board. He's wired in pretty high at Dell these days, and I trust what he says here. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: PowerEdge 2650 specification - SCSI controller
On Fri, January 1, 2010 21:12, Stroller wrote: Hi there, Can anyone tell me if the drives on the PowerEdge 2650 were hot-swap as standard, please? This review http://www.pcmag.com/article2/0,2817,31750,00.asp says that: Featuring ... hot-swappable hard drives, redundant power supplies... An integrated PERC3/Di dual-channel RAID controller ... is optional, or you can configure the 2650 with a choice of two- or four-channel RAID cards or a dual-channel SCSI adapter card. ... two redundant 500-watt power supplies are standard, although you can opt for a single nonredundant power supply. From that it's not really clear to me whether or not hot-swap was a feature of all the possible RAID card choices, or just some of them. Does anyone know what chipset was used on the PERC3 for the other RAID controller options? I'm assuming that RAID cards are the sort of thing that are still supported in the Linux kernel even when they're 5+ years old. Does that seem reasonable? There is one of these available locally to me, on eBay for (perhaps) not too much money, and it might just hep a scratch I have that needs itching. I appreciate the 2650 isn't a current model and requires Ultra3 SCSI drives, but neither performance nor storage capacity are an issue for this application. Service manual (http://support.dell.com/support/edocs/systems/pe2650/en/sm/index.htm) says: Support for up to five 1-inch, internal Ultra3 SCSI hard drives (with hot-plug capacity when using the optional ROMB card). The 3/Di ROMB was Adaptec, still supported in Linux by the aacraid driver. The 3/SC and 3/DC add-in cards were LSI, still supported by megaraid driver. I run a 3/DC in my venerable Precision 530 home server on Fedora 12. Haven't seen a 2650 with the internal drive backplane connected to a SC or DC add-in, but the drives should also be hot-swappable in such a config. You just can't hot-swap if connected to vanilla SCSI. BTW, Ultra3 is not required, just the practical speed limit for the PERC 3 generation. You can drop U320s in and they'll just step down to U160 speed. Throw in an Ultra2 and they'll all step down to that speed. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: PowerEdge 2650 specification - SCSI controller
On Fri, January 1, 2010 22:29, Stroller wrote: I assume, then, that the moatherboard in fact has 2 RAID controllers - this PERC 3/Di and another, non-hotswap one - and the ROMB key was used simply to enable the higher-specification option at a different price-point? There's the 3/Di RAID controller, requiring the key to enable, shame on Dell, and a vanilla SCSI non-raid onboard. My use for it was always for a tape drive, never saw one with the disks in the nominal base configuration of plain SCSI, although you could certainly do that and use software RAID. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Re: RAID Perc 5 monitoring
On Fri, January 1, 2010 22:25, Rick Bragg wrote: Hi, Thanks, I should have mentioned that I have a 64 bit platform. It seems all that is available for download is megactl-0.4.1.i386.tar.gz. Will this work with 64 bit OS? Even better, is there a Debian 64 bit package for this somewhere? Source is available. But the binary release notes say: Notes: This is a binary build for i386 of the initial release. It runs on i386 or x86_64 platforms of Red Hat Enterprise Linux 3, 4, and 5. It may run on Debian if appropriate compatibility libraries are installed. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: megactl
On Mon, December 28, 2009 15:51, P.A wrote: unable to open device /dev/megaraid_sas_ioctl_node: No such file or directory How do I create that file? I read somewhere that it's a udev issue but im not sure. On the megactl README it says to run the megasasrpt script, which I did and it didn't create that missing file. IIRC, mknod /dev/megaraid_sas_ioctl_node c 253 0 should do it. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: SAS5/E with MD1000 for JBOD
On Fri, December 18, 2009 15:25, Preston Hagar wrote: On Thu, Dec 17, 2009 at 4:22 PM, Philip Tait phi...@subaru.naoj.org wrote: On 12/17/2009 11:39 AM, Jose-Marcio Martins da Cruz wrote: Philip Tait wrote: We want to attach an MD1000 to a PE2900 in a non -RAID configuration. The Dell sales people are very convinced that we have to have a PERC6/E to connect an MD1000, but they are doing further research. We have two MD1000 attached to a PE2950. We have a PERC5/E. With the PERC5/E you can have RAID 0 (stripe). So, if I understood what you're wanting, you shall be able to create one RAID 0 volume for each disk, or a single RAID0 for all disks. Thanks for the response, but I believe this would not work for our application because the disks would require a PERC-equipped computer for them to be readable. We want these drives to be readable on any PC with a SATA interface. Honestly (an maybe someone can correct me) I don't think it is possible. I have pretty much never found a way to connect drives with a PERC5/E and MD1000 or even connected directly to a PERC5/i for that matter that doesn't add Dell mojo in between. The best solution we found was to buy multiple PERC cards, save the configs once we had everything like we wanted it (doing RAID 0 on the hard drives to fake JBOD), and then loading that config on other machines to be backups. Still, if the MD1000 went out, we still might be up a creek. Although I generally love Dell hardware, it is one drawback I have found to the MD1000 and PERC cards is that they want their Dell specific voodoo in between. We have even found that just buying drives for a third party vendor will seem to work sometimes, but often lead to flakiness. Apparently they all have to be matched drives with Dell firmware on the drives themselves to be fully supported (or at least that is what we have been told). I guess you can't connect one of these with a plain SAS controller and have the drives presented as plain physical drives? You could do that with the old SCSI Powervaults. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
