Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

IBM ServerRaid blocked  logical drive with Linux 3.

Posted on 2008-10-13
7
Medium Priority
?
1,065 Views
Last Modified: 2013-12-15
I have an IBM Eserver running Red Hat Linux ES v3 i686.  This server is primary a web server and was running fine for years until recently when a user called to ask if there was something wrong the the server.  When I checked the console the server appeared to be completely hung, after restarting I received this message from the IBM ServerRaid manager - blocked logical drive hit F4 to continue or F5 to make no changes.  I hit F4 and the system comes up with no problems.  I contacted IBM and downloaded all the latest and greatest drivers for the hard drives, the raid controller, Linux drivers, even the system bios.  This seemed to solve the problem at least for awhile but it has come back again.  I have used fsck to check all the partitions for bad blocks, but his does help either.

A recent example: I used Linux update to install some updated rpms on the system - they downloaded and installed correctly when I went to click finish - all the drives in the raid 5 array pegged on a solid green and the system hung - upon reboot - the blocked logical driver message again.

Any help - this one is driving me insane.
0
Comment
Question by:interstate
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 29

Expert Comment

by:Michael Worsham
ID: 22712382
It quite possibly be that the latest drivers/firmware is no longer compliant with RHEL 3. I recommend checking with IBM and RedHat to see if there is a fix available for the problem you are having since it seems to be software related.

Also, are there any messages appearing under 'dmesg' in relation to the raid environment?
0
 

Author Comment

by:interstate
ID: 22712623
We were running relatively old drivers when the problem suddenly developed - moving to the latest drivers has not cured the problem completely as of the moment.  I have attached the dmesg file for those who may be able to see something ominous in that file - which could help solve the problem

Thanks

dmesg.txt
0
 

Author Comment

by:interstate
ID: 22731641
Here's some more information which may help.  This morning I noticed that when I went to open a web page on the server (this is a nuke site) I got the session has failed to initialize error, which is where it starts, wait a little while longer and the other nuke site on the server stops working.  If I ssh into the server a command like df -v may work or just return with an input/output error. Wait a little longer and I will no longer be able to connect to the sever at all.

At the console when I attempt to do a restart I get the following:
EXT3-FS Error (device sd(8,2) in start_transaction: Journal has aborted

I have to manually restart the system and at that point after the ServerRaid has initialized I get that blocked drive message.

hope this helps.

thanks
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 
LVL 88

Expert Comment

by:rindi
ID: 22737679
Check your HD's, it looks like there is a problem with at least one (sd8,2). Run fsck on the partitions.
0
 
LVL 20

Accepted Solution

by:
Gns earned 750 total points
ID: 22738699
(tagging on to rindis advice:-) And do the fsck from rescue mode, to ensure that it can do a thorough job on a quiscient filesystem.
It could be a marginal block in the journal itself... What you describe just tell us that the HW raid or the IO system is having problems. More or less what you can expect when one start talking about "years of uptime":-). The "blocked HDD" thing is just that... It is "dirty", so you need handle that after pulling the plug on it... More of a consequense than the reason, so to speak:-).
If I were you, I'd start looking at replacing the server altogether... a "total update" to newer distro on new HW.

Cheers
-- Glenn
0
 

Author Closing Comment

by:interstate
ID: 31406256
Got tired of battling IBM with hardware vs software issue - moving the apps to another server and shutting this thing down for now, perhaps on a rainy day will fire it up and take another look.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
Suggested Courses

660 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question