Dell PowerEdge 2500 - Errors on Boot Up

Hello,
I had a reason to put a monitor on my headless server here... and I noticed on the Arch bootup there is a bunch of errors.
First off, on the boot, first error that popped up was
MP-BIOS bug: 8254 timer not connected to IO-APIC
Now, I have read that there is a fix to that on alternative forums in my DuckDuckGo search., just haven't found one.
Secondly, the error that comes seconds after the first one...
aic7xxx: no multichannel peer found!
Didn't see anything to really fix to that.
Third, this one spams like a couple hundred times on bootup, but continues to boot.
udevd[56]: timeout: killing '/sbin/modprobe -bv pci:v00009005d000000CFsv00001028sd000000D9bc01sc00i00' [108]
There is another error that comes up while in the terminal about echoing something to fix the problem.... but I typed exit just after because I was done managing the server.... >.< Stupid me.
Any ideas to fix the errors, I can post any information if needed.

Since it just happened (it was 2hrs before I got it into rice), is it for sure corrosion?
If you tried to use the phone, or even didn't power it off, before putting in rice to dry, there is likely hardware damage. You can try again after leaving it in the rice for 3-4 days, but even if it works, it's likely to fail again in the near future.
It certainly wasn't hacked/jailbroken as I got it directly from Apple and never did that to it.
Yet you mentioned using tinyumbrella, which is hacking software.
I don't care to save the phone as much as the data
Does that mean you didn't backup that valuable data?
Lastly, if I may ask without being offensive.... how do you know your information?
All things that occur to me are the Truth By Definition...

Similar Messages

Solaris 8 installation problem on Dell PowerEdge 500SC

Hi,
I am having TWO PROBLEMS installing Solaris 8 on Dell PowerEdge 500SC.
This hardware spec is:
Pentium-III at 1GHz
256MB 133MHz ECC SDRAM
20GB 7200RPM ATA100 EIDE hard drive (on integrated ATA-100 controller)
48X EIDE CD-ROM drive (on integrated ATA-100 controller)
Motherboard: unknown
more details: http://www.dell.com/us/en/esg/topics/esg_pedge_sc_towermain_servers_3_pedge_500sc.htm
FIRST PROBLEM is the following message was shown at the hardware probe.
WARNING: ACPI Tables not in Reclaim Memory
Warning: Resource Conflict - both devices are added
NON-ACPI device: PNP0C01
Port: C00-C01, C06-C08, C14, C50-C52, C6C-C6F,
CD6-CD7
F50-F57
ACPI device: PNP0C01
Port 814-85B, 580-58F, C00-CD7, F50-F58
At this time, I was using "Solaris 8 (Intel Platform Edition) 10/01" released version.
I am not sure what this means, but it was RESOLVED with using newer "x86 DCA boot diskette (Patch-ID# 110930-05)".
But, the SECOND REAL PROBLEM is another one. It just happens booting the kernel after the hardware probe. I get the following messages about 2 minutes later, after beginning to load kernel.
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: abort request, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: about device, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: reset target, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: reset bus, target=0 lun=0
After another 1 or 2 minutes I get more error and the system reboots.
Please give me any suggestion or advice!
Thanks.
Kazuyoshi

I've been having the exact same problems on a PowerEdge 500SC. I have managed to get Solaris up and running on the machine, however. I booted the DCA from the floppy disk and installed from the CD-ROM. When the DCA is ready to scan for devices I use the "Specific Scan" option to tell it to look for specific devices. I tell it to scan for all devices in the listing and in doing so the DCA finds ISA-based IDE controllers. After it provides a listing of the devices it found I use the "Device Tasks" option and the "View/Edit Devices" menu item then delete the Bus Mastering IDE controller device. Once the screen comes up to ask for a boot device, the drives will show up as on the ISA controllers.
I have to go through this process every time I boot the machine but I am able to make the system run at least.
I haven't figured out the ACPI problem, yet.
Regards,
Doug

Problem with Installation on DELL Poweredge with Hardware RAID 1

Hello Arch LInux community,
I am a newbee with good linux knowledge of working on linux but not much of systems administration. I am very much interested to install Arch Linux on my new desktop which is a Dell poweredge having hardware RAID 1(PERC .... controller). It has windows 7 OS on its first partition.
I saw on the controller's BIOS menu that there are 2 1tb hard drives with something like --:--:00 and --:--:01 labels. And they were partitioned into two logical volumes which are visible once I boot into Arch linux live CD as, /dev/sda (about 250GB, and has windows OS on it) and /dev/sdb (about 700GB).
Firstly, I am confused with the hard disk labels: even though they are logical partitions (i.e: combined by RAID 1, they are seen as /dev/sda and /dev/sdb). In the arch linux Beginner's wiki, there is some description on configuring for RAID, which included mdadm or mdadm_udev module specification. I did include these modules, and followed the installatin instructions carefully. I was trying to install on /dev/sdb, with the following partitioning:
Sector map of partitions on /dev/sdb : 1542848512 : 735.7 GiB
Disk identifier (GUID) : 967BF308-6E5E-43AD-AB2E-94EB975C3603
First usable sector = 34 Last usable sector = 1542848478
Total free space is 2023 sectors
Number    Start End    Size    Code Name
   34 2047       FREE
1    2048 2099199    1024.0 MiB EF00    EFI System
2    2099200 2103295    2.0 MiB EF02 BIOS boot partition
3    2103296 2615295    250.0 MiB 8300 Linux filesystem
4    2615296 212330495    100.0 GiB 8300 Linux filesystem
5    212330496 317188095 50.0 GiB 8300 Linux filesystem
6    317188096 1541924863 584.0 GiB 8300    Linux filesystem
   1541924864 1542848478       FREE
The instruction on the Beginner's wiki is somewhat difficult to understand for beginners. Especially I wasn't sure whether to make EFI System partition and BIOS boot partition or just EFI system partition. So I made both as per the instructions.
Is using UEFI compulsory, on UEFI based systems?
A little bit more sub-headings or division of instructions, in the Beginner's wiki, based on the usage scenarios can be very beneficial for newbees like me.
I am finally getting the following error when I select the Arch Linux from the GRUB menu. Why it can't find the device? I shall wait for your initial responses, and will give more specifics of my installation to find out any wrong step that I may have made.
[ 0.748399] megasas: INIT adapter done
ERROR: device 'UUID=40e603e9-7285-4ec8-8a06-a579358a52a0' not found. Skipping fsck
ERROR: Unable to find root device 'UUID=40e603e9-7285-4ec8-8a06-a579358a52a0' .
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
Sh: can't access tty; job control turned off
[rootfs /]#

Well, you can see your RAID partitions and you're getting GRUB to load, and you are even being dropped to the recovery shell which means that the /boot partition is being found and is accessible. All vary, vary good things.
I would boot into the Arch live CD/USB again. Then check the UUID of the / Root partition. To do this I just check the log listing of /dev/disk/by-uuid
ls -l /dev/disk/by-uuid
Hopefully the UUID for the /root partition in the /boot/grub/grub.cfg is incorrect, and all you need to do is change it from 'UUID=40e603e9-7285-4ec8-8a06-a579358a52a0' to the correct UUID.
If the UUID is correct... then maybe the correct driver module is not complied into the initramfs. You could try adding that mdadm to the MODULES= list in /etc/mkinitcpio.conf then rebuild the initramfs again.
mkinitcpio -p linux
Hum..., the whole /dev/sda and /dev/sdb.... hum, You know... Maybe you need to change the line in /boot/grub/grub.cfg
set root='hd1,msdos1'
The hd1 is the equivalent to /dev/sda and the msdos1 is the equivalent of the First Partition i.e. /dev/sda1.. (note this is my disk yours may correctly have different numbers and not be a msdos partition)... owe wait... hum, you know I am fairly sure that like is really the root disk where the /boot partition is and has no relation to the / Root partition... Someone clear that up please.... It is hard for me to recall and I have my / Root parition encrypted, so It is hard for me to make heads or tails of that one right now, but that could be the problem too i.e. try changing hd1 to hd2 or hd0 or something.
Owe, and it may be faster if you just make temporary corrections to the GRUB menu by hitting the "e" key on the menu entry you want to change then hit.. I think F10 to boot the modified entry. That way you don't need to keep booting into the Live CD/USB
Last edited by hunterthomson (2012-09-20 05:52:33)

Problems installing Solaris 10 on Dell PowerEdge 800

Hi,
I am experiencing some trouble when I attempt to install Solaris 10 on a Dell PowerEdge 800. It is equipped with two RAID disks controlled by a Dell CERC SATA 1.5/6ch (according to the BIOS).
The installation program reports that it cannot write to the disk. This happens when it is about to start installing files. Tried setting it to a single volume and disable RAID. Same thing. Read another article saying something about disabling IDE, well it doesn't seem to help ...
Any hints?

I have the same problem on a dell 750 with the SERC controller. I can add some more information but if you get a solution I would appreciate the detail.
1) If I install Solaris via the SERC in RAID 1 mode then the alarm on the SERC goes off as soon as I start to write to the disk.
2) I bypassed the SERC and installed on a single disk straight off the motherboard. Time the install crashed at the same point but this time the error message told me that the first available cylinder was number 3! Ah
3) I reconnected the disk via the SERC, rebuilt the RAID array and made a mistake. I created a RAID 0 (striped) array and installed the software starting from cylinder 3. I got a complete solaris install that rebooted fine and is fully working.
BUT I NEED A MIRRORED SYSTEM SO
4) I rebuild the machine again this time RAID 1 and again the crash occured at exactly the same point i.e. as soo as I start to write to the disk.
Whether or not DELL / Adaptec support Solaris should not be an issue. This is a BIOS configurable RAID controller that can be fully serviced (e.g. disks replaced) from the BIOS. The system sees the array as a disk via the controller and indeed it is seeing it.
The SERCs own data configuration data should be on sectors which are not visible to solaris VIA the SERC so we shouldnt be able to damage them but I suspect that this may not be the case.
I suspect that the answer is in the partition layout and who or what creates them (I dont mean the Solaris slices but the FDISK partitions)
To make matters worse, since I need the machine working I went back to disks straight of the motherboard and configured again and used metadevices to set up a fully mirrored systemas I have done many times before on sparc (but never on Solaris x86)
This worked fine but I thought that I would test bootability in the event of disk failure. There isnt any!
if disk 1 fails then the motherboard wont accept disk 2 unless you swap the cables and move it do disk 1 and by then the boot sectors are wrong for the address of the device. I can probably solve this by building both disks in slot one but who wants a mirrored server that you have to open up and move a cable when the disk fails. I think I may have to ditch SATA and go back to SCSI !

Dell PowerEdge SC1420 with Ultra 320 scsi dirves

I am having a problem with installing Solaris 10 on the Dell PowerEdge SC1420 with Ultra 320 SCSI drives using PERC 320/DC Controller. The installation hangs at Configuring Devices and gives me some output messages:
NOTICE: MSG From Adapter: NMI ISR: NMI_BUS_INTERFACE_UNIT_ERROR
NOTICE: MSG From Adapter: NormPrioCommand was received with Fib StructType = 0xf
The notices keeps cycling.
Has anyone experience this issue?
Any suggestions are appreciated.
Thank you,
Brian

Update:
I've got the box to install Solaris 10, however, I had to remove 2 sticks of memory. Originally, the box came with 4GB of memory but now I am down to 2GB. Don't know why this is the case but I am able to proceed with the installation without any error or notice messages. Can someone explain to me why this is the case? I will put the memory sticks back in and boot with the OS installed to see what happens and will update my results.
Thanks,
Brian

Dell Poweredge 2800 Solaris?

Hi,
I have a Dell PowerEdge 2800 server. It has three 73Gig SCSI diska and three 146 Gig SCSI disks.
This system comes with LSI 53c1030 controllers. The drives are hot plug and the dell backplane has a device that appears on the SCSI bus PE/PV 1 x8 SCSI bp.
This machine hangs in configuring devices Solaris 10 GA.
In solaris 9 it sort of works with the Driver from LSI but the I/O rate is limited to 8 Megabytes/ Second (if your lucky, normally running at 1 meg/second). The file systems on the diska have been corrupted three times in 1 day. The messages file has a repeated error message
ID 3658 kern.info <Default cyl 8921 alt 2 hd 255 sec 63>
The verify disks in the controller bios takes around 100 minutes for the 73 gig scsi and says its complete at 86%!
Has anybody got any idea how to get this box working?
Please Help!

OK guys,
I've got it rocking. thanks to the new itmpt driver released by LSIlogic a couple of days ago for download on their site.
these are the exact steps, how to install Solaris 10 x86 (03/05 release) on a Dell 1850 Dual Xeon 3Ghz, with 2x73GB SCSI disks, using an LSI 1030 controller.
1. go into the bios in the Dell, and disable the Raid mode, this is done in the Integrated Peripherals, just set the raid card to SCSI enabled. Also, make sure the boot device has the diskette above the hard drive or CD.
2. download yourself the 119376-01 SD.ITU from sun.
3. make yourself a DCA diskette (you can get the file called d1_image from the DVD, which you can mount on another pc)
4. mount that DCA diskette on some linux box, or wincrap box, it is a DOS formatted diskette, and edit the file [solaris/bootenv.rc] file and add a line at the bottom with the following:
setprop acpi-user-options 0x4
5. boot the machine with the DCA diskette, and the DVD in the drive (make sure the diskette is booting), and then F4 to add a driver, and add the SD.ITU diskette. Then continue as always (F2....)
6. When asked what boot option, choose Interactive installation text in CONSOLE MODE (option 4) (believe me, you will need this due to a bug in the graphical install)
7. continue with the full install, you will notice that even though the e1000g0 is "skipped" on the test, it actually recognizes that you are networked, weird.
8. at the end of the full install it will ask you to add the SD_11... diskette again, so do that, and press enter. If at this point it complains that it cannot find the sd driver in the diskette, then press enter again, and it will find it (this may or may not occur randomly).
9. the box will reboot, and the bootup will take a long while doing some SMF stuff (i.e. how to hide inetd so that noone can telnet in any longer hahhaa). During this process, go to the lsilogic.com site, and download yourself the following file: itmpt-x86-5.06.00.zip
10. unzip that file, and you will notice that it contains itmpt-x86-50600-itu.dd and also itmpt-x86-50600.tar.Z
the itmpt-x86-50600-itu.dd is an ITU, but it only contains a solaris 9 version of the thing, so it wont be useful at boot time. Ergo, we will use the package file itmpt-x86-50600.tar.Z
11. Now that you are networked, copy that itmpt-x86-50600.tar.Z file into your dell, and uncompress untar it. Then change into the install folder it creates, and just type pkgadd -d . Go ahead and install the thing.
12. not it is important that you make sure you do exactly as the installpkg tells you. You need to vi /etc/driver_aliases and comment out the mpt "pci1000,30" and mpt "pci1000,50" lines (i.e. add a # as the first char of the line).
and UNCOMMENT the ones you will see at the bottom, called itmpt "pci1000,30" and itmpt "pci1000,50"
in my case the itmpt "pci1000,54" is already uncommented, leave as is.
13. touch /reconfigure
14. reboot
15. PTG.
The key end effect that was desired:
- I now get 50-100 megabytes / sec sending data from disk to disk, which is paaaarfect !.
- Hyperthreading is recognized properly, I can now see 4 cpus,
- The 8GB of swap I have is recognized.
In response to Solaris being junk, and moving to Linux or BSD, well, this is not an OS-War thread, but I can guarantee the following premises are true:
a. the easier to install an OS, the more latent incompatibilities are added to a running system, which invariably manifest themselves at 4 AM, or when you least expect them.
b. wincrap is not and OS, it's just a bad, sad joke on humanity.
c. BSD will invariably freeze your whole operation as soon as you have 10 heavy applications accessing the disks heavily for more than a minute.
d. Linux will invariably need a reboot once in a while, specially when you run more than 5 different heavy apps with lots of ram manipulation, and disk action. (note, if using heavy NFS, then the reboot will be needed once a week or less)
e. Solaris (sparc or X86) is the only one that allows me to sleep and smile (once it's installed of course), and will not freeze no matter what you throw at it, I have a dual cpu x86 at constant load 3 or 4, doing webserver, database, php runner, and batch image processing, with an uptime of 1200 days.
cheers to all, wish you luck.

Need Help! Dell poweredge T630 cannot reboot after trying to add new memory card

What errors are you seeing on the screen?

hi, can any one please advise what should I do for my server? Dell poweredge T630 cannot reboot after trying to add new memory card. Even I remove the newly added memory card and only keep the original one there, it still cannot reboot. Before I try to add the memory card, it works well without any rebooting issues.
Thank you so much for help
steven
This topic first appeared in the Spiceworks Community

Stuck Dell PowerEdge 2550 not REALLY supported?

Hi all,
I've been trying to get Solaris 8 installed on a Dell PowerEdge 2550 I just got in, and I'm not having any luck. This is unfortunate, as its my one sole server for a small biz I'm trying to get going. Sigh. Anyway, the problem is that after booting off the CD and installing the boot image onto the HD (which seems to go fine), I reboot and it hangs at the:
Solaris Boot Loader Version 2.0
And that's it... can't get to the blue screen boot manager and continue. I've tried the latest drivers from Dell for the 7899, the Ultra160 drivers straight from Adaptec... all for naught. Tried reconfiguring (mostly turning stuff off) on the Adaptec, nada.
I called up Dell support, who were basically useless. Told me some load of crap about "Well, we can't get Solaris 8 to work on any of our stuff". Which is odd, coz Sun lists this system as a supported configuration, along with a bunch of other Dells. Not to mention the tech on the sales call that told me it would work, along with the built-in PERC3 raid controller. Which doesn't, of course.
Anyone had a similar problem that they've managed to get around? Otherwise I'll have to call them to come pick it back up. Which'll set me back another 2 weeks, sigh. Anyway,
Gory details:
PIII 1.26mhz
2 18.2GIG Fujitsu drives
Adaptec 7899
Built in PERC3/DI RAID controller (currently disabled and completely unsupported)
2x2 split backplane.
I've also been trying the Solaris 9 EA install, but I can't get it to configure the jumpstart directory correctly. Anyone have a step-by-step for doing it? Thanks,
Lucas.

Lucas,
We had similar problems with a PowerEdge 1550 a few weeks back, but found that turning off the ACPI settings (see below) and using the latest DCA diskette from the Sun website, everything worked perfectly including the AIC-7899 and dual NIC detection.
A possible workaround is to disable the kernel ACPI module. If the problem
is happening during installation, the boot floppy must be modified. Mount the
boot floppy and add the following line to bootenv.rc:
setprop acpi-user-options '0x2'
Run the installation again, ACPI should be disabled and the installation
should continue without a problem.
If the problem occurs after installation the same line can be added to
the top of /etc/bootrc and ACPI will be disabled on the next reboot.
Hi all,
I've been trying to get Solaris 8 installed on a Dell
PowerEdge 2550 I just got in, and I'm not having any
luck. This is unfortunate, as its my one sole server
for a small biz I'm trying to get going. Sigh.
Anyway, the problem is that after booting off the CD
and installing the boot image onto the HD (which
seems to go fine), I reboot and it hangs at the:
Solaris Boot Loader Version 2.0
And that's it... can't get to the blue screen boot
manager and continue. I've tried the latest drivers
from Dell for the 7899, the Ultra160 drivers straight
from Adaptec... all for naught. Tried reconfiguring
(mostly turning stuff off) on the Adaptec, nada.
I called up Dell support, who were basically useless.
Told me some load of crap about "Well, we can't get
Solaris 8 to work on any of our stuff". Which is
odd, coz Sun lists this system as a supported
configuration, along with a bunch of other Dells.
Not to mention the tech on the sales call that told
d me it would work, along with the built-in PERC3 raid
controller. Which doesn't, of course.
Anyone had a similar problem that they've managed to
get around? Otherwise I'll have to call them to come
pick it back up. Which'll set me back another 2
weeks, sigh. Anyway,
Gory details:
PIII 1.26mhz
2 18.2GIG Fujitsu drives
Adaptec 7899
Built in PERC3/DI RAID controller (currently disabled
and completely unsupported)
2x2 split backplane.
I've also been trying the Solaris 9 EA install, but I
can't get it to configure the jumpstart directory
correctly. Anyone have a step-by-step for doing it?
Thanks,
Lucas.

Are Dell Poweredge 2900 servers compatible with Oracle VM?

I am seeking information on installing Oracle VM on a new model dell poweredge 2950 server. The existing hardware is pre-installed with "validated" Virtualization – VMware® ESX software 3.x.
This pre-installed "validated" Virtualization is partly installed on an SD-Card/USB device attached to the mother board. The existing white paper at DELL does not address this SD-Card/USB configuration [http://www.dell.com/downloads/global/solutions/ovm_ref_config_final.pdf?c=us&cs=04SP10&l=en&s=bsd] . I prefer a response from the Oracle VM team or Dell Employee.
Edited by: Rajendra on Oct 9, 2008 2:03 PM
Edited by: Rajendra on Oct 9, 2008 2:03 PM

I am not sure if Oracle VM server 2.1.2 will install in a Dell PE 2950 but I have installed it on a PE 1950 with no problems. After installation I turrned on VM in the bios and I have been able to install and run a couple of PVMs on it. If the 1950 and 2850 use the same motherboards then it should work for you too.
However, I have to admit to a concern with this server which may require me to reinstall the OS on it. I have a dual port qlogic HBA installed on it. "Lsmod |grep ql " indicates that the qlogic modules are installed but there are no relevant entries in /proc/scsi. If I boot up the server and use the qlogic firmware, i am able to verify that the card is installed and I am able to get the MAC addresses.
I have installed VM server on 2850's with older qlogic cards and did not encounter this sort of problem. I am not sure if this is caused by the newer qlogic card, the 1950 Motherboard, or some other factor.
Unfortunately, this server is physically located 50 miles away from me and I am unable to test out different theories. The first chance I get , I plan to install RH Linux and the usual EMC software on this server, configure it to see LUNS on the SAN then reinstall VM server on it. That should either eliminate a lot of question marks for me or give me some directions to address the issues.

All RAM is not shown by Dell PowerEdge 2650 redhat 4 linux system

Hi,
I have Dell™ PowerEdge™ 2650 server having 4 GB ram and i install Redhat 4 linux on it. But in the bios it shows 4 GB and 256 MB ram which i checked physically but in my OS it shows like.
[root@htss06 ~]# free -m
                   total       used       free     shared    buffers     cached
Mem:           248        247          1          0          4         59
-/+ buffers/cache:        182         65
Swap:          511         10        501It's very strange i am not very good about servers. after googled i found
re-map the missing
ram from where your bios hole is located
but don't know how.
Thanks
umesh

[root@htss06 ~]# cat /boot/grub/grub.conf
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux AS (2.6.9-5.ELhugemem)
root (hd0,0)
kernel /vmlinuz-2.6.9-5.ELhugemem ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-5.ELhugemem.img
title Red Hat Enterprise Linux AS (2.6.9-5.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-5.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-5.ELsmp.img
title Red Hat Enterprise Linux AS-up (2.6.9-5.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-5.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-5.EL.img
[root@htss06 ~]# uname -a
Linux htss06.htss.com 2.6.9-5.ELhugemem #1 SMP Wed Jan 5 19:38:36 EST 2005 i686 i686 i386 GNU/Linux
[root@htss06 ~]#

Dell PowerEdge Servers with non-dell storage

yes I do I have a few 2950's that I run with WD red drives they work fine. moslty that stuff is to keep warranties upheld and to keep repeat customers coming back. its up to you how much you want to deal with. some of the raid functions and raid configurations may not be available if they have custom firmware from Xbyte or require custom firmware installed.personally if the server hardware is past dell's warranty I am using the cheapest most reliable drives I can get my hands on because at that point its on me any way. that also means wiping the PERC controller to default and rolling with default settings and then modifying them to what I need.Then again it goes back to how much responsibility do you want on you for this hardware. if you want as little as possible play by your distributors rules and have little or take it all yourself...

Hi,
I am pricing out some refurbished Dell PowerEdge servers primarily from xbyte.com and received feedback from them that they are extremely apprehensive about using non-dell storage in the server due to the custom firmware in the drives themselves. That being said they offer non-dell hard drives with custom xbyte firmware which apparently work... and yet they will still report a non-mission critical error in the manager.
Does anyone run production servers with 3rd party drives? If it is not recommended to do so, does anyone run the "Xbyte drive firmware" in production servers?
Thanks!
This topic first appeared in the Spiceworks Community

BMR hints? W2k8r2 BMR from Dell Poweredge T310 to different Dell machine

Hello,
I've seen some other questions about this problem, but haven't read any responses that quite help me get to the other side of the problem I'm having.
I have a situation where I need to restore a bare metal backup from a Dell PowerEdge T310 server to an off the shelf computer. It fails, of course, and I'm stuck about what's causing the failure so I can try to remedy it.
Both machines have the same storage space. The T310 utilizes DELL PERC 6/i Adapter and contains 3 500 GB drives. The other machine does not have this hardware. I'm wondering if this is the trouble.
I was able to successfully restore this server, without any trouble whatsoever, to an old Dell OptiPlex 330 workstation with a single 1TB drive, but cannot get the same result when a Dell Inspiron i7 is used.
Both machines are ACPI x64-based PCs.
Do you think it's the missing PERC that's causing the problem? From your experience, what are all the not-so-obvious things I should check?
The fact that I can do a BMR to an old OptiPlex is amazing. I didn't expect any problems with the new computer.
Thanks in advance for your assistance!
Beth

Hi,
We do not support restoring a system state backup from one computer to a second computer of a different make, model, or hardware configuration. We only provide commercially reasonable efforts to support this process. Even if the source and destination
computers seem to be identical makes and models, the source computers may have different drivers, hardware, or firmware than the destination computers.
According to your description, the two server have different RAID controller. BMR between the two servers will cause BSOD or system not boot issue.
How to: Bare Metal Restore of SBS2008 to different hardware with a different RAID controller?
http://social.technet.microsoft.com/Forums/en-US/019a504e-c109-4d18-a85f-4f03944ada05/how-to-bare-metal-restore-of-sbs2008-to-different-hardware-with-a-different-raid-controller?forum=windowsbackup
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Solaris 10 on Dell PowerEdge 2950

I have a Dell PowerEdge 2950 server with bellow spec.
- Dual Core Xeon Processor 5130 4MB Cache * 2 EA
- SAS 5/i Integrated Controller Card(LSI Logic 1068)
- 300 GB, 3.5 inch 10K RPM SAS HDD
When I try to install the Solaris 10 6/06, I got a message there is no discs.
How to solve it?
Please help me.
Thank you.

I solved this problem.
In grub, add "kernel/unix" option like thefollowing:
root (hd0,0,a)
kernel /platform/i86pc/multiboot
kernel/unix
module /platform/i86pc/boot_archive
But I don't know why this problem is.It seems you're forcing to use the 32-bit kernel.
Is that a machine with a 64-bit x86 processor, buta
64-bit disk device driver for the root disk wasn't
installed?Juergen.Keil, you are right!
I force boot 32-bit kernel because my server could't
boot correctly.
My Dell 2950 Server has two Dual Core Xeon
Processor(Intel Xeon CPU 5130 @ 2.00GHz CPU).
And LSI Logic1068 driver, the package name is
ITMPT-5.07.01, has two drivers.
I found the installed driver files:
/kernel/drv/itmpt
/kernel/drv/amd64/itmpt
I have 2 questions.
(1) Is Solaris 10 support 64-bit kernel for my
processor?
(2) How to boot 64-bit kernel or install?
Thank you again.I have 2 questions.
(1) Is Solaris 10 support 64-bit kernel for my
processor?
There is a problem with this processor (Woodcrest ) when you boot 64-bit. There is a ptach already released by Sun, but is only avaibale for those who request. Please try calling Sun.
(2) How to boot 64-bit kernel or install?
By default after the first CD installation, the OS should boot in 64-bit kernel. Because of this issue, you will not be able to boot in 64-bit. Continue booting in 32-bit , complete the installation and then apply this patch in 32-bit, the system after reboot should boot in 64-bit.
-Mallik

Errors on boot - failed command: READ DMA

I've started to get failed command: READ DMA errors on boot. What do they mean? Is there any way to fix them?
[ 114.232991] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 114.233001] ata1.00: BMDMA stat 0x25
[ 114.233006] ata1.00: failed command: READ DMA
[ 114.233017] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 114.233022] ata1.00: status: { DRDY ERR }
[ 114.233026] ata1.00: error: { UNC }
[ 114.290536] ata1.00: configured for UDMA/133
[ 114.290566] sd 0:0:0:0: [sda] Unhandled sense code
[ 114.290573] sd 0:0:0:0: [sda]
[ 114.290577] Result: hostbyte=0x00 driverbyte=0x08
[ 114.290584] sd 0:0:0:0: [sda]
[ 114.290588] Sense Key : 0x3 [current] [descriptor]
[ 114.290596] Descriptor sense data with sense descriptors (in hex):
[ 114.290601] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 114.290624] 02 a6 57 02
[ 114.290636] sd 0:0:0:0: [sda]
[ 114.290640] ASC=0x11 ASCQ=0x4
[ 114.290647] sd 0:0:0:0: [sda] CDB:
[ 114.290651] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 114.290671] end_request: I/O error, dev sda, sector 44455682
[ 114.290700] ata1: EH complete
[ 115.677517] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 115.677529] ata1.00: BMDMA stat 0x25
[ 115.677538] ata1.00: failed command: READ DMA
[ 115.677555] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 115.677565] ata1.00: status: { DRDY ERR }
[ 115.677570] ata1.00: error: { UNC }
[ 115.713838] ata1.00: configured for UDMA/133
[ 115.713870] sd 0:0:0:0: [sda] Unhandled sense code
[ 115.713877] sd 0:0:0:0: [sda]
[ 115.713882] Result: hostbyte=0x00 driverbyte=0x08
[ 115.713889] sd 0:0:0:0: [sda]
[ 115.713893] Sense Key : 0x3 [current] [descriptor]
[ 115.713901] Descriptor sense data with sense descriptors (in hex):
[ 115.713905] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 115.713929] 02 a6 57 02
[ 115.713940] sd 0:0:0:0: [sda]
[ 115.713945] ASC=0x11 ASCQ=0x4
[ 115.713951] sd 0:0:0:0: [sda] CDB:
[ 115.713956] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 115.713976] end_request: I/O error, dev sda, sector 44455682
[ 115.714006] ata1: EH complete
[ 117.055388] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 117.055400] ata1.00: BMDMA stat 0x25
[ 117.055409] ata1.00: failed command: READ DMA
[ 117.055427] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 117.055436] ata1.00: status: { DRDY ERR }
[ 117.055442] ata1.00: error: { UNC }
[ 117.090462] ata1.00: configured for UDMA/133
[ 117.090494] sd 0:0:0:0: [sda] Unhandled sense code
[ 117.090501] sd 0:0:0:0: [sda]
[ 117.090506] Result: hostbyte=0x00 driverbyte=0x08
[ 117.090512] sd 0:0:0:0: [sda]
[ 117.090516] Sense Key : 0x3 [current] [descriptor]
[ 117.090524] Descriptor sense data with sense descriptors (in hex):
[ 117.090529] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 117.090552] 02 a6 57 02
[ 117.090564] sd 0:0:0:0: [sda]
[ 117.090568] ASC=0x11 ASCQ=0x4
[ 117.090575] sd 0:0:0:0: [sda] CDB:
[ 117.090579] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 117.090599] end_request: I/O error, dev sda, sector 44455682
[ 117.090648] ata1: EH complete
[ 118.344345] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 118.344356] ata1.00: BMDMA stat 0x25
[ 118.344365] ata1.00: failed command: READ DMA
[ 118.344382] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 118.344391] ata1.00: status: { DRDY ERR }
[ 118.344397] ata1.00: error: { UNC }
[ 118.427170] ata1.00: configured for UDMA/133
[ 118.427198] sd 0:0:0:0: [sda] Unhandled sense code
[ 118.427240] sd 0:0:0:0: [sda]
[ 118.427246] Result: hostbyte=0x00 driverbyte=0x08
[ 118.427252] sd 0:0:0:0: [sda]
[ 118.427257] Sense Key : 0x3 [current] [descriptor]
[ 118.427265] Descriptor sense data with sense descriptors (in hex):
[ 118.427269] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 118.427293] 02 a6 57 02
[ 118.427304] sd 0:0:0:0: [sda]
[ 118.427309] ASC=0x11 ASCQ=0x4
[ 118.427315] sd 0:0:0:0: [sda] CDB:
[ 118.427320] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 118.427340] end_request: I/O error, dev sda, sector 44455682
[ 118.430078] ata1: EH complete
[ 725.193320] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
Here's some info about the hard drive itself:
/dev/sda:
ATA device, with non-removable media
Model Number: SAMSUNG HM040HI
Serial Number: S07WJ10Y711599
Firmware Revision: YA100-02
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 0
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 78242976
LBA48 user addressable sectors: 78242976
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 38204 MBytes
device size with M = 1000*1000: 40060 MBytes (40 GB)
cache/buffer size = 8192 KBytes (type=DualPortCache)
Last edited by β ™ (2014-01-14 10:31:39)

I've started to get failed command: READ DMA errors on boot. What do they mean? Is there any way to fix them?
[ 114.232991] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 114.233001] ata1.00: BMDMA stat 0x25
[ 114.233006] ata1.00: failed command: READ DMA
[ 114.233017] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 114.233022] ata1.00: status: { DRDY ERR }
[ 114.233026] ata1.00: error: { UNC }
[ 114.290536] ata1.00: configured for UDMA/133
[ 114.290566] sd 0:0:0:0: [sda] Unhandled sense code
[ 114.290573] sd 0:0:0:0: [sda]
[ 114.290577] Result: hostbyte=0x00 driverbyte=0x08
[ 114.290584] sd 0:0:0:0: [sda]
[ 114.290588] Sense Key : 0x3 [current] [descriptor]
[ 114.290596] Descriptor sense data with sense descriptors (in hex):
[ 114.290601] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 114.290624] 02 a6 57 02
[ 114.290636] sd 0:0:0:0: [sda]
[ 114.290640] ASC=0x11 ASCQ=0x4
[ 114.290647] sd 0:0:0:0: [sda] CDB:
[ 114.290651] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 114.290671] end_request: I/O error, dev sda, sector 44455682
[ 114.290700] ata1: EH complete
[ 115.677517] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 115.677529] ata1.00: BMDMA stat 0x25
[ 115.677538] ata1.00: failed command: READ DMA
[ 115.677555] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 115.677565] ata1.00: status: { DRDY ERR }
[ 115.677570] ata1.00: error: { UNC }
[ 115.713838] ata1.00: configured for UDMA/133
[ 115.713870] sd 0:0:0:0: [sda] Unhandled sense code
[ 115.713877] sd 0:0:0:0: [sda]
[ 115.713882] Result: hostbyte=0x00 driverbyte=0x08
[ 115.713889] sd 0:0:0:0: [sda]
[ 115.713893] Sense Key : 0x3 [current] [descriptor]
[ 115.713901] Descriptor sense data with sense descriptors (in hex):
[ 115.713905] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 115.713929] 02 a6 57 02
[ 115.713940] sd 0:0:0:0: [sda]
[ 115.713945] ASC=0x11 ASCQ=0x4
[ 115.713951] sd 0:0:0:0: [sda] CDB:
[ 115.713956] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 115.713976] end_request: I/O error, dev sda, sector 44455682
[ 115.714006] ata1: EH complete
[ 117.055388] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 117.055400] ata1.00: BMDMA stat 0x25
[ 117.055409] ata1.00: failed command: READ DMA
[ 117.055427] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 117.055436] ata1.00: status: { DRDY ERR }
[ 117.055442] ata1.00: error: { UNC }
[ 117.090462] ata1.00: configured for UDMA/133
[ 117.090494] sd 0:0:0:0: [sda] Unhandled sense code
[ 117.090501] sd 0:0:0:0: [sda]
[ 117.090506] Result: hostbyte=0x00 driverbyte=0x08
[ 117.090512] sd 0:0:0:0: [sda]
[ 117.090516] Sense Key : 0x3 [current] [descriptor]
[ 117.090524] Descriptor sense data with sense descriptors (in hex):
[ 117.090529] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 117.090552] 02 a6 57 02
[ 117.090564] sd 0:0:0:0: [sda]
[ 117.090568] ASC=0x11 ASCQ=0x4
[ 117.090575] sd 0:0:0:0: [sda] CDB:
[ 117.090579] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 117.090599] end_request: I/O error, dev sda, sector 44455682
[ 117.090648] ata1: EH complete
[ 118.344345] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 118.344356] ata1.00: BMDMA stat 0x25
[ 118.344365] ata1.00: failed command: READ DMA
[ 118.344382] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 118.344391] ata1.00: status: { DRDY ERR }
[ 118.344397] ata1.00: error: { UNC }
[ 118.427170] ata1.00: configured for UDMA/133
[ 118.427198] sd 0:0:0:0: [sda] Unhandled sense code
[ 118.427240] sd 0:0:0:0: [sda]
[ 118.427246] Result: hostbyte=0x00 driverbyte=0x08
[ 118.427252] sd 0:0:0:0: [sda]
[ 118.427257] Sense Key : 0x3 [current] [descriptor]
[ 118.427265] Descriptor sense data with sense descriptors (in hex):
[ 118.427269] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 118.427293] 02 a6 57 02
[ 118.427304] sd 0:0:0:0: [sda]
[ 118.427309] ASC=0x11 ASCQ=0x4
[ 118.427315] sd 0:0:0:0: [sda] CDB:
[ 118.427320] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 118.427340] end_request: I/O error, dev sda, sector 44455682
[ 118.430078] ata1: EH complete
[ 725.193320] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
Here's some info about the hard drive itself:
/dev/sda:
ATA device, with non-removable media
Model Number: SAMSUNG HM040HI
Serial Number: S07WJ10Y711599
Firmware Revision: YA100-02
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 0
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 78242976
LBA48 user addressable sectors: 78242976
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 38204 MBytes
device size with M = 1000*1000: 40060 MBytes (40 GB)
cache/buffer size = 8192 KBytes (type=DualPortCache)
Last edited by β ™ (2014-01-14 10:31:39)

Install in a Dell PowerEdge 2900

Hi there, I have an Dell PowerEdge 2900 Server. But it do not boot arch. I read that need some certified or something like that. Iso image is good, it boot from other computers without problem. Any idea?

Uranio-235 wrote:it bot, but sayd "isolinux.bin missing or corrupt"
Are you sure your CD is valid? (Is it a real CD or USB key?). Are booting in BIOS or in UEFI mode? If it is UEFI, disable secure boot in the firmware. How have you created your CD? If you simply copy all the files, I think it will boot in UEFI mode, because the firmware looks for a file; but not in BIOS mode, where you have to burn the raw image. If you have still some problems, be sure to describe the problem and what you have done in details.
Last edited by olive (2015-02-02 16:47:59)

Dell PowerEdge 2500 - Errors on Boot Up

Similar Messages

Maybe you are looking for