Find the answer to your Linux question:
Results 1 to 3 of 3
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 ...
  1. #1
    Just Joined!
    Join Date
    Jul 2009
    Posts
    5

    Repair File System problem on RHEL 5.1

    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 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#


    Please find the attached screenshots 1.jpg, 2.jpg and 3.jpg.
    It can be seen that I have run fsck -A -y Also, it shows the entry that I had made to /etc/fstab (last line) 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"
    Attachment 4.jpg shows the msg. that I am getting during booting the OS. It shows "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
    Attached Images Attached Images
    • File Type: jpg 1.jpg (93.0 KB, 10 views)
    • File Type: jpg 2.jpg (94.0 KB, 9 views)
    • File Type: jpg 3.jpg (96.5 KB, 7 views)
    • File Type: jpg 4.jpg (95.4 KB, 9 views)
    Last edited by AchyuthaRao; 05-22-2010 at 04:13 PM. Reason: Update screenshots

  2. #2
    Linux Newbie Mad Professor's Avatar
    Join Date
    May 2006
    Posts
    128
    I didn't fully understand your problem.

    You have scsi controller with 4 disks in 1+0, the system hung, you reset the machine then proceeded to delete the array?

    Well I would say you have a pretty high chance for dataloss.



    Perhaps it was move around.

    See if you can see the array of disks with fdisk -l

    if you see your array, try getting the blkid of array by running blkid and replace label= with uuid= of array of disks in fstab. Be sure to remove the quotes in the uuid. Be sure it's your logical disk/array of disk that you deleted not the drives individually.

    If you don't see any thing in fdisk, then you did delete array.


    if you did delete the array, there's a very slim chance of getting the data back. I'm not 100% sure on this method but if you want to give it a go, be my guest. See if you have the option of putting it back together without it being initialized, on my raid controller I have keep Old data. This may not be an option due to it being in raid, then I would stop here, it's very difficult to recover data from an raid array.

    With fdisk make a new partition, it has to be the same partition type and size and so on, must match exactly like before

    But don't format it. You'll erase the data

    Then try mounting it.

    If successful you should see data, I would suggest that you back up this data and rebuild your array and format to eliminate any future problems.

  3. #3
    Just Joined!
    Join Date
    Oct 2010
    Posts
    1
    Just give root password and after logging in give command "fsck -y /dev/hda1".In my case my partition is /dev/hda1 so as per your requirement give proper partition

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...