Hello All

 

Having a "small" storage issue i just upgraded my parity drive which i have done before with no problems, this time as soon as the array came online the web interface stopped working and the array would not online (flash share still worked tho). I have tracked the issue down to the plugins starting up, but the plugins themselves are all fine it seems to be the SSD that i use for storing them outside of the array i think.  The SSD is 3 months old and formated with EXT4 outside the array to handle my downloads and plugin storage.

 

My setup is a ESXI box running Unraid pro 5.0 setup as per the "ATLAS" thread on this forum.  I have a IBM ServeRAID M1015 sas controller running all 8 channels into an Intel RES2SV240 sas expander.  The unraid os has 4 cores of an I7-4770 (3.4Ghz) and 16GB Memory.  Total number of drives in the system 9.

 

Im at the final stages of rebuilding parity to the new 4TB drive (ST4000DM000-1F2168) i have no other 4tb drives in the system and all the other drives have spun down as its building past there capacity, but my rebuild speed is only 60MB/Sec at this stage which i would expect to be alot faster. 

 

Now whats this got to do with a faulty ssd your thinking? Well the activity light is always on for the bay the ssd is in (which now i think about it has always been on), which i think might be causing the slow rebuild? I have tried to run FSCK on the ssd and get the following:

 

e2fsck 1.41.11 (14-Mar-2010)

/sbin/e2fsck: Superblock invalid, trying backup blocks...

/sbin/e2fsck: Bad magic number in super-block while trying to open /dev/sdb

 

The superblock could not be read or does not describe a correct ext2

filesystem.  If the device 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 8193 <device>

 

The logs dont seem to show anything i can find but ill attach them anyway.

 

Any help or ideas anyone has would be gratefully received, i know its not strictly an unraid problem.

 

 

Many thanks - Rick

syslog-20141113-154600.zip

I could be way off base here, but shouldn't you be running the command on /dev/sdb1?

I could be way off base here, but shouldn't you be running the command on /dev/sdb1?

 

It seems your set firmly on the base, it comes back as clean.

Mostly i use windows, but looking at it the command make more sense now.

Which leaves me with more trouble shooting more to do.