Dell PowerEdge 1800 Server Logo
Posted on Jan 23, 2008
Answered by a Fixya Expert

Trustworthy Expert Solutions

At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.

View Our Top Experts

Same Problem Again - Mega Raid.... Unknown Error

Hello Dear,

I am using Dell Power Edger 1800 with Linux AS-3 ... i am copying here my error log messages here... Could you please help me to resolve this error... 3 Monhts ago; one HDD was demaged and i had replaced it...

Log is as under.....
Jan 21 14:16:01 localhost smbd[27854]: [2008/01/21 14:16:01, 0] lib/util_sock.c:read_socket_data(342)
Jan 21 14:16:01 localhost smbd[27854]: read_socket_data: recv failure for 4. Error = No route to host
Jan 21 16:05:08 localhost smbd[12290]: [2008/01/21 16:05:08, 0] lib/util_sock.c:read_socket_data(342)
Jan 21 16:05:08 localhost smbd[12290]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan 21 18:03:30 localhost smbd[12616]: [2008/01/21 18:03:30, 0] lib/util_sock.c:read_socket_data(342)
Jan 21 18:03:30 localhost smbd[12616]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan 21 18:30:55 localhost smbd[12957]: [2008/01/21 18:30:55, 0] lib/util_sock.c:read_socket_data(342)
Jan 21 18:30:55 localhost smbd[12957]: read_socket_data: recv failure for 4. Error = No route to host
Jan 21 18:47:22 localhost smbd[13045]: [2008/01/21 18:47:22, 0] lib/util_sock.c:get_socket_addr(919)
Jan 21 18:47:22 localhost smbd[13045]: getpeername failed. Error was Transport endpoint is not connected
Jan 21 18:47:22 localhost smbd[13045]: [2008/01/21 18:47:22, 0] lib/util_sock.c:get_socket_addr(919)
Jan 21 18:47:22 localhost smbd[13045]: getpeername failed. Error was Transport endpoint is not connected
Jan 21 18:47:22 localhost smbd[13045]: [2008/01/21 18:47:22, 0] lib/util_sock.c:write_socket_data(388)
Jan 21 18:47:22 localhost smbd[13045]: write_socket_data: write failure. Error = Connection reset by peer
Jan 21 18:47:22 localhost smbd[13045]: [2008/01/21 18:47:22, 0] lib/util_sock.c:write_socket(413)
Jan 21 18:47:22 localhost smbd[13045]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer
Jan 21 18:47:22 localhost smbd[13045]: [2008/01/21 18:47:22, 0] lib/util_sock.c:send_smb(585)
Jan 21 18:47:22 localhost smbd[13045]: Error writing 4 bytes to client. -1. (Connection reset by peer)
Jan 21 20:03:47 localhost smbd[13154]: [2008/01/21 20:03:47, 0] lib/util_sock.c:read_socket_data(342)
Jan 21 20:03:47 localhost smbd[13154]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan 21 20:10:56 localhost smbd[13236]: [2008/01/21 20:10:56, 0] lib/util_sock.c:read_socket_data(342)
Jan 21 20:10:56 localhost smbd[13236]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan 21 23:01:42 localhost smbd[13271]: [2008/01/21 23:01:42, 0] lib/util_sock.c:read_socket_data(342)
Jan 21 23:01:42 localhost smbd[13271]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan 22 03:18:35 localhost smbd[13675]: [2008/01/22 03:18:35, 0] lib/util_sock.c:read_socket_data(342)
Jan 22 03:18:35 localhost smbd[13675]: read_socket_data: recv failure for 4. Error = No route to host
Jan 22 10:11:19 localhost smbd[14834]: [2008/01/22 10:11:19, 0] lib/util_sock.c:read_socket_data(342)
Jan 22 10:11:19 localhost smbd[14834]: read_socket_data: recv failure for 4. Error = No route to host
Jan 22 14:15:41 localhost smbd[15625]: [2008/01/22 14:15:40, 0] lib/util_sock.c:read_socket_data(342)
Jan 22 14:15:41 localhost smbd[15625]: read_socket_data: recv failure for 4. Error = No route to host
Jan 22 20:04:30 localhost smbd[17144]: [2008/01/22 20:04:30, 0] lib/util_sock.c:read_socket_data(342)
Jan 22 20:04:30 localhost smbd[17144]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan 22 23:02:24 localhost smbd[17462]: [2008/01/22 23:02:24, 0] lib/util_sock.c:read_socket_data(342)
Jan 22 23:02:24 localhost smbd[17462]: read_socket_data: recv failure for 4. Error = Connection reset by peer

Jan 23 03:15:16 localhost smbd[17667]: [2008/01/23 03:15:16, 0] lib/util_sock.c:read_socket_data(342)
Jan 23 03:15:16 localhost smbd[17667]: read_socket_data: recv failure for 4. Error = No route to host
Jan 23 08:00:50 localhost smbd[18827]: [2008/01/23 08:00:50, 0] lib/util_sock.c:read_socket_data(342)
Jan 23 08:00:50 localhost smbd[18827]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Jan 23 10:16:14 localhost smbd[18884]: [2008/01/23 10:16:14, 0] lib/util_sock.c:read_socket_data(342)
Jan 23 10:16:14 localhost smbd[18884]: read_socket_data: recv failure for 4. Error = Connection reset by peer

Jan 23 16:03:47 localhost syslogd 1.4.1: restart.


When i see the Server at last, last 4 or 5 messages were displayed on Screen and Machine was in hang position. I restart it then its solve....

Please help me to solve this matter. Please also give you email id so that i can get some help from you....


Thanks & Best Regards

Aleem Asghar
[email protected]

1 Answer

Anonymous

Level 2:

An expert who has achieved level 2 by getting 100 points

MVP:

An expert that got 5 achievements.

Vice President:

An expert whose answer got voted for 100 times.

Novelist:

An expert who has written 50 answers of more than 400 characters.

  • Expert 156 Answers
  • Posted on Apr 13, 2008
Anonymous
Expert
Level 2:

An expert who has achieved level 2 by getting 100 points

MVP:

An expert that got 5 achievements.

Vice President:

An expert whose answer got voted for 100 times.

Novelist:

An expert who has written 50 answers of more than 400 characters.

Joined: Mar 22, 2008
Answers
156
Questions
0
Helped
283739
Points
379

Hi

The title of your post suggests that you have "Maga RAID" errors. Maga RAID messages would be in line with issues on the LSI PERC sub-system.

However, the extract posted in your suggests network problems.

Any number of physical to driver and configuration issues can result in network problems.

Try the basic checks;
1. Change or try a known patch cable
2. Run "ping" test to a known good system connected to same network switch or direct connect with a "cross-over" cable and check for dropped connections.
3. Is the NIC and switch set to Auto-Negotiation or static at 10, 100 or 1000Mbps speed
4. Can you try another switch
5. Check and load correct or latest manufacture's drivers

Reply with more info.

Mike

Add Your Answer

×

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

0helpful
1answer

Where is poweredge 1800 display led connector

http://www.dell.com/support/troubleshooting/us/en/19/KCS/KcsArticles/Print?he Embedded System Management (ESM) log - also called System Event Log (SEL) or hardware log - reports potential hardware problems in Dell PowerEdge servers. Sometimes, simply turning off the server and disconnecting it from the electrical outlet will remove the error message. Wait approximately 10 seconds, and then reconnect the power cable and restart the server.

Other times, you will need to clear the ESM log to remove the error message. For instance, error code SEL FULLindicates that you will need to clear the ESM log. (You will lose the server's event history.) There are different ways to clear the ESM log.

To use DSET to Clear the ESM Log
  1. Download and open the DSET utility.
  2. Click the plus (+) next to System, and then click the plus (+) next to Logs.
  3. Click ESM to highlight it.
  4. Click Clear ESM Log located in the upper-right corner of the page.
To use OpenManage Server Administrator (OMSA) to clear the ESM log
  1. Start OpenManage Server Administrator (OMSA).
  2. Log in to OMSA by entering your username and password, and then press Enter.
  3. Click the Logs tab, and then click Hardware.
  4. Click Clear Log located next to Options.
To use Dell IT Assistant to clear the ESM log
  1. Start IT Assistant.
  2. From the middle System Tree bar, select your server by clicking it.
  3. Click the Logs tab, and then click Clear Log in the upper-right corner of the page.
Find your Dell PowerEdge server model in the chart below for other ways to clear the ESM log:

PowerEdge server model How to clear the ESM log 2300, 2400, 2450, 2500, 2500SC, 2550, 4300, 4350, 4400, 6300, 6350, 6400, 6450
Use the Log2Txt.exe utility to clear the ESM log:
  1. Start your server to the Log2Txt utility.
  2. When you see the ESM Log main menu appear, press 2 on your keyboard to select Clear ESM log.
  3. When the ESM Log main menu reappears, press 5on your keyboard to exit the utility.
1650, 1850, 1800, 2600, 2650, 2800, 4600, 6600, 6650, 7150, 6800, 6850, R900
Use the DRAC or ERA to clear the ESM log:
  1. Type the IP address of the Remote Access Controller (RAC) in the web browser address bar, and then press Enter.
  2. Log in to the RAC.
  3. Click the Logs tab, and then click Hardware.
  4. Click Clear Logs located in the upper-right corner of the page.
1850, 2800, 2850, 6800, 6850
Use the program BMCCFG.exe to clear the ESM logs:
  1. Download and extract the Dell OpenManage Deployment Toolkit here.
  2. Go to x:\Dell\Toolkit\Tools, where x is your primary hard disk drive.
  3. Copy the file BMCCFG.exe to a bootable floppy disk.
  4. Start the server from the bootable floppy disk.
  5. At the command prompt, type bmcc - clearsel, and then press Enter.
    The message "Clearing SEL" will display while the log clears.
1950, 2900, 2950, DP500, DP600, NF500, NF600
Use the BMC/BIOS to clear the ESM log:
  1. To open the BMC menu, press the Control + Ekeys during POST.
  2. From the list, select System Event Log, and then press Enter.
  3. Select Clear System Event Log, and then pressEnter.
=8590&doclang=EN
1helpful
4answers

Dell error code 2000-0151 hard drive 0-incorrect stauts:5E

try this reset your bios.or check disk - goto run type - chkdsk. what result tell me.
0helpful
1answer

Dell power edge 2850 make 4 seconds beeps alarm without stopping and without show any error Msg on the screen.

I don't understand the beep code you describe, but the 2850 has many beep codes to help understand what is going on.

First ... Identify the beep. Does the beep start as soon as you power it on, or after several seconds? What is the pattern of the beep - is it a repeating set of beeps - 3 sets of beeps between 1 and 4 beeps ... like 1 beep-3 beeps-2 beeps, or 3 beeps, 3 beeps, 1 beep? Or is it a steady repeating beep - about once per second?

Second ... is the LCD panel on the server blue or orange? If orange, what is the error code(s) it is scrolling?

If it is a steady, once-per-second beep, it is probably your RAID controller. Does the system boot to Windows/OS ok? If so, use (or install) OpenManage Server Administrator (Managed Node from Dell's Support Site) to check the Hardware Logs and check the RAID array (under Storage/Virtual Disks). If it is not booting to the OS, then go into CTRL-M to see what the status of your array is.
0helpful
1answer

It's Urgent

Hi,
when you boot the server there is a menu that comes up before the bios screen, enter that menu there you can know which raid level is being used.

Further Queries are welcome
0helpful
1answer

Valid operating systems fro Power Edge 1800

During the Windows XP setup you will need to provide the RAID driver using a pre-formated floppy disk.
Windows will ask you if you want to provide additional drivers and give you the key combination to use to do that.
0helpful
1answer

Dell 9150

This system has onboard RAID, sometimes it is simply because the RAID controller is in error, to get it out of error:

* Disconnect the power cable
* Hold power button for 15 seconds
* Release the power button
* Plug in power cable
* Start the computer

If this does not work, please provide information, is is Windows XP or Vista?
0helpful
1answer

Service Tag 277MW0j-DY

The best solution is to get another power supply and back the data up.

If you can't do that, and you have SCSI drives, then I would suggest marking the drives (0, 1, 2, 3, etc) and putting them in another Dell Power Edge server with the same RAID card and reading them that way. It can be dangerous to your data if you don't know what you are doing.

There are programs out there that can help you re-construct your RAID if needed. CaptainNemo and RAID Reconstructor have helped me in the past. If you have a Dell Perc 3/DI in your existing server, I may have the parameters for those programs.

Let me know.

0helpful
3answers

Dell server poweredge 1800 frequently shutdown

is there an error message that appears? can you check error logs? I need more information to be able to help you. I would first try to blow dust out of the fans, as it may be over heating, another possibility is that there is software on the machine that is causing it to shut down.
7helpful
10answers

Flashing orange light

Power edge system are having two power input check the cables from the power outlet may be one is in contact otherwise one of your power supply gone means not working. Check the wires first then the power supply units
Not finding what you are looking for?

1,407 views

Ask a Question

Usually answered in minutes!

Top Dell Computers & Internet Experts

Grand Canyon Tech
Grand Canyon Tech

Level 3 Expert

3867 Answers

SmartAviator
SmartAviator

Level 3 Expert

1124 Answers

Brad Brown

Level 3 Expert

19187 Answers

Are you a Dell Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...