[SOLVED] RAID, deleted LUN: Repair File System problem on RHEL 5.1

AchyuthaRao · 05-22-2010, 11:53 AM

Hi,

I have a HP Proliant DL380 G4 server installed with RHEL 5.1 using 2 SCSI disks using RAID 1+0. This is, using the HP Smart Array 6i controller.
I had used one MSA20 array for creating LUN out of 4 disks - this, using HP Smart Array 642 SCSI controller. I had also mounted this partition and added to entry to /etc/fstab.
Since there was some problem in closing the terminal while running an IO on this LUN, I happened to reboot the system and deleted the logical drive at ORCA on the 642 controller.
Now, my RHEL 5.1 system is in "Repair File System" mode. I have got huge valuable data on this and cant afford to get it screwed. Kindly help me solve my problem.
Please, can you explain the steps in detail, as to what I need to do?
This is how it is seen:
Give root password for maintenance
(or type Control-D for normal startup):
At this point enter the root password then run fsck:
(repair file system) 1#

I have run fsck -A -y Also, it shows the entry that I had made to /etc/fstab (last line) as LABEL=/MSA20 ext3 defaults 1 2 and the fact that the contents in the directories are seen properly. Only problem is that am not able to resolve the "Repair File System"
Also, I am getting a message during booting the OS: "Unable to Resolve LABEL=/MSA20". This was the directory for the LUN which I had created and mounted....and had subsequently deleted the LUN during boot time, using ORCA.
Thanks in Advance,
Achyutha

tommylovell · 05-22-2010, 02:46 PM

You need to remove the "LABEL=/MSA20 ext3 defaults 1 2" entry from /etc/fstab. You are in "Repair File System" mode because because the system is trying to mount that filesystem and it no longer exists.

So, to remove that entry from /etc/fstab--

Make a backup copy before you start: cp -p /etc/fstab /etc/fstab.bad

Then remove the offending entry.

'vi /etc/fstab'
move to the "LABEL=/MSA20" line
type dd to delete it
then type <esc> followed by :wq

Your root file system may be mounted in read-only mode at this point. In which case when you 'cp' or 'vi' edit it, it will say the file is read only:

like:
cp -p /etc/fstab /etc/fstab.bad
cp: cannot create regular file `/etc/fstab.bad': Read-only file system

or in vi:
"/etc/fstab" [readonly] 18L, 959C

If that is the case, remount the root filesystem read-write (using the -o flag).

To do that, use the mount command to find where '/' is mounted; then remount it.

Example:
mount -o remount,rw /dev/cciss/c0d0p1 /

You didn't say if you were using LVM. If that's the case, it is a little more complicated.
You may need to vgchange -ay, then remount.

Example:
mount -o remount,rw /dev/mapper/volgrp-root /

(or something like that...)

Once mounted read-write, you can use the vi editor to remove the "LABEL=/MSA20" line.

When the line is removed, type <ctl> D to reboot.

I hope your valuable data is not on the MSA20 filesystem. That data may be gone.

Good luck.

AchyuthaRao · 05-23-2010, 06:53 AM

Hi Tommy!

Thanks a ton for your answer!
I was able to get my RHEL 5.1 working again by using the steps that you mentioned!!

Best Regards,
Achyutha

dharmendrajet · 07-10-2010, 03:48 PM

in fstab file
i remove " = " between LABEL=/
this is first line of fstab

now my system in maintienence mode plz slove my proble with out use rescue mode

DrLove73 · 07-10-2010, 04:57 PM

When you play with fire you get burned. Only Rescue mode from Installation CD or any other LiveCD can help you now.