Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: Graham on June 10, 2008, 02:29:10 AM
-
When trying to run fsck on /dev/sdb2 I get the following error: The Superblock could not be read or does not describe a correct ext2 filesystem
If I run it on /dev/sdb1 it runs fine.
Is this normal!
-
When trying to run fsck on /dev/sdb2...
Why are you doing that?
-
Been having a issue with our raid, I've checked both drives and them seem fine so I through f2ck might find something.
-
Been having a issue with our raid, I've checked both drives and them seem fine so I through f2ck might find something.
Since you have RAID, the filesystem will be located on /dev/mdX (or on a Logical Volume contained within /dev/mdX), not on /dev/sdb1.
What "issue" did you have?
-
I keep having a report of a failed drive but it's not always the same one.
when I run fsck /dev/md2 I have the same issue
-
because you have LVM over raid
post here the result of
df -h
Ciao
Stefano
-
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/main-root
72G 1.5G 67G 3% /
/dev/md1 99M 13M 81M 14% /boot
none 506M 0 506M 0% /dev/shm
[root@server-1 ~]#
I started again, installed SME from fresh with only one hard drive /dev/sda I've now put a secound drive in and added it to the raid /dev/sdb problem is it gets to 67% then stops and goes back to 0%, been doing that for hours now.
-
so, you have to run fsck against what? :-)
Ciao
Stefano
-
I started again, installed SME from fresh with only one hard drive /dev/sda I've now put a secound drive in and added it to the raid /dev/sdb problem is it gets to 67% then stops and goes back to 0%, been doing that for hours now.
What have you done to check that there are no problems with that hard drive? Have you checked /var/log/messages, and used smartctl to get a report on the drive?
-
Did a smart check via the BIOS and they didn't report any issues the one via SME I can't make out what it all means.
-
How do you go about stopping a rebuild?
-
I keep having a report of a failed drive but it's not always the same one.
Are they SATA drives? If so check/change the cables. A few weeks ago I was having bother with a server which finally resulted in a fail event on one of the disks. I changed the disk, and the problem went away but I could find nothing wrong with the disk when I got it home. It was suggested to me somewhere else that the errors I was getting suggested an ill fitting or dodgy SATA cable.
Cheers.