Topic: Booting with Raid 1 Problem

[Bud]

hi guys hope you can help

i am running sme 7.4 with raid 1 (two 400g sata drives, sata 0 and sata 1) and two 500Gig Sata Drives for Data (sata 2 and sata 3)

this is my raid 1 setup

400g  ----
             : Raid 1 using Sata 0 and Sata 1 (400g drives)
400g  ----

500g ---- Data (Sata 2)

500g ---- Data (Sata 3)

My Problem is that on my Sata 0 (Raid Drive) the drive has gone down, i can still boot from my Sata 1 drive but i get an error: 
-------------------------------
 fsck.ext3: No such file of directory while trying to open /dev/sdd
 /dev/sdb: clean, 299661/48840704 files, 73261171/9761171 blocks
                                                                                   [FAILED]
*** An error occurred during file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
--------------------------------------

i urgently need to get this server up - what do i do?? 

any help greatly appreciated

[janet]

Bud

Sata 0 = sda
Sata 1 = sdb
Sata 2 = sdc
Sata 3 = sdd


>  fsck.ext3: No such file of directory while trying to open /dev/sdd

That's referring to your SATA3 drive. Perhaps it has also failed.

You should run drive manufacturer diagnostic tests on all the drives.

Do you have good backups, you may need to restore from those.

[Bud]

mary thanks for your quick reply 

i unpluged (removed) sata 0 (sda) and sata 2 (sdb - data drive 1) and sata 3 (sdd - data drive 2) from the motherboard
i now get a new error message 

sata 1 is on the sata 1 channel on the motherboard (this is the second drive on my raid 1 system - 400gig) which i can boot up but gives the error now

--------------------------------
Checking filesystems
/dev/md1: clean, 84,26104 files, 48756/104320 blocks
/dev/sdb:
The superblock could nor be read or does not describe a correct ext2 filesystem. If the defvice is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck - b 8192 <<device>

/dev/sdd:
The superblock could nor be read or does not describe a correct ext2 filesystem. If the defvice is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck - b 8192 <<device>

fsck.ext3: No such file or directory while trying to open /dev/sdb
fsck.ext3: No such file or directory while trying to open /dev/sdd
                                                                   [FAILED]
*** An error occurred during file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
--------------------------------------

the only drive that is running on my system is the raid 1 sata 1 drive on sata channel 1 - must i place this on the sata 0 channel (will that help)

what now 

[janet]

Bud

I assume you have those two data drives configured in fstab on your RAID1 system drives, so as they are both unplugged (or faulty) then your system is giving errors relating to them.

You say you can boot up to sata1 drive, but you get errors. I don't call that a very successful boot up.

As already stated, I suggest you test all the drives with manufacturers diagnostic test software. Search for the Ultimate Boot CD (UBCD), download the iso and burn yourself a test disk, and start testing. It contains a lot of different test software for various brands etc.

You can also boot to the sme server disk in rescue mode, and test the drives using smartctl. There is a Howto that describes what to do.

You could try connecting the drive to sata0 port to see if it boots correctly, but I have my doubts.

[chris burnat]

You can also boot to the sme server disk in rescue mode, and test the drives using smartctl. There is a Howto that describes what to do.

Mary, do you mean :
http://wiki.contribs.org/Monitor_Disk_Health

[CharlieBrady]

fsck.ext3: No such file of directory while trying to open /dev/sdd
 /dev/sdb: clean, 299661/48840704 files, 73261171/9761171 blocks
                                                                                   [FAILED]

Your problem is that you explicitly reference /dev/sdc and /dev/sdd in the modifications you have made to /etc/fstab. Comment out those lines, and then work out your RAID1 issue.

Then you can put the extra mount points back, but use file system labels or uuid or logical volume names instead of specific device names (which will change when you add or delete drives).

[janet]

Mary, do you mean :
http://wiki.contribs.org/Monitor_Disk_Health

Yes

[Bud]

CharlieBrady thanks for your reply

Your Answer

--------------------------------------

Your problem is that you explicitly reference /dev/sdc and /dev/sdd in the modifications you have made to /etc/fstab. Comment out those lines, and then work out your RAID1 issue.

Then you can put the extra mount points back, but use file system labels or uuid or logical volume names instead of specific device names (which will change when you add or delete drives).

---------------------------------------

what i did was to unplug the faulty 500gig Sata drive (Sata 0) and then i also unpluged both the two 400gig Sata Data Drives (Sata 2 and Sata 3)

I connected the good 400gig Sata 1 drive on to the First Sata Channel 0 on the Motherboard (Only this one drive is now connected to my motherboard which was part of my Raid 1 Two Drive System)

I then booted with the sme 7.4 cd and pressed the F5 Button (Rescue Mode)
After the cd boot i then typed in at the prompt: " #sme rescue " ( without the # )

It told me that my boot image is in " /mnt/sysimage "

i then did a " #cd /mnt/sysimage/etc "
then edit the fstab file using pico editor: " #pico fstab "

this gave me the abbility to edit the " fstab " and make changes to it
i edited out " /dev/sdc and /dev/sdd "
Saved the file ( press " ctrl x and then y " )

Rebooted the Server and i'm back up and running 

thanks so much to both mary and CharlieBrady for all your help

next i want to upgrade my 500gig Sata to 1T Drive with Raid 1 and connect both my two Sata Data Drives and Mount them with the System ( might need some help with this  )

Thanks again guys much appreciated