I recently upgraded to RC12a and all seemed fine with the array being OK and a parity check or two being carried out without a problem.

 

Next I decided to upgrade the parity to a 3Tb WD Red drive. I have removed the previous Parity drive from the array and assigned the 3Tb drive to parity and started to run a parity check.

 

Shortly after starting the parity check one of the Seagate 1.5Tb drives went offline showing no temp imformation etc. So I cancelled the parity check and restarted the array, at which point the ST 1.5Tb was shown as unformatted. I removed the drive and put it into my main PC and found I could read the dat on the drive and backed all the data off onto another drive.

 

I have tried installing another ST 1.5TB drive and a WD 2Tb EARS drive into the array in place of the problem drive and each time the drive shows as unformatted (the partition had been deleted in Windows) but each time I try to format the drive it does not complete just returning to the array showing an unformatted drive.

 

I have tried replacing the SATA cable, putting it onto another controller and onto another power cable all to no effect. Each time the syslog states see below and attached.

 

I have backed up this drive and I still have the original untouched Parity drive but I just want to replace the drive and start a parity check or remove the drive and replace it later. This makes three drives with similar problems this makes me think the problem must be elsewhere.

 

I was having problems a few weeks ago and replaced some of the drives and the cables to the Supermicro MV8 controller and changed the PSU for a Corsair TX650, I had thought that that had cured the problems.

 

Any ideas

 

********

 

May 28 18:31:30 Tower emhttp: shcmd (80): ps axc | grep -q rpc.mountd (Other emhttp)

May 28 18:31:30 Tower emhttp: _shcmd: shcmd (80): exit status: 1 (Other emhttp)

May 28 18:31:30 Tower emhttp: shcmd (81): /usr/local/sbin/emhttp_event svcs_restarted (Other emhttp)

May 28 18:31:30 Tower emhttp_event: svcs_restarted (Other emhttp)

May 28 18:31:37 Tower emhttp: shcmd (82): set -o pipefail ; mkreiserfs -q /dev/md5 |$stuff$ logger (Other emhttp)

May 28 18:31:37 Tower logger: mkreiserfs 3.6.21 (2009 www.namesys.com)

May 28 18:31:37 Tower logger:

May 28 18:31:38 Tower logger:

May 28 18:31:38 Tower logger: The problem has occurred looks like a hardware problem. If you have

May 28 18:31:38 Tower logger: bad blocks, we advise you to get a new hard drive, because once you

May 28 18:31:38 Tower logger: get one bad block  that the disk  drive internals  cannot hide from

May 28 18:31:38 Tower logger: your sight,the chances of getting more are generally said to become

May 28 18:31:38 Tower logger: much higher  (precise statistics are unknown to us), and  this disk

May 28 18:31:38 Tower logger: drive is probably not expensive enough  for you to you to risk your

May 28 18:31:38 Tower logger: time and  data on it.  If you don't want to follow that follow that

May 28 18:31:38 Tower logger: advice then  if you have just a few bad blocks,  try writing to the

May 28 18:31:38 Tower logger: bad blocks  and see if the drive remaps  the bad blocks (that means

May 28 18:31:38 Tower logger: it takes a block  it has  in reserve  and allocates  it for use for

May 28 18:31:38 Tower logger: of that block number).  If it cannot remap the block,  use badblock

May 28 18:31:38 Tower logger: option (-B) with  reiserfs utils to handle this block correctly.

May 28 18:31:38 Tower logger:

May 28 18:31:38 Tower logger: bread: Cannot read the block (0): (Input/output error). (Errors)

May 28 18:31:38 Tower logger:

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 0 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 1 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 2 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 3 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 4 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 5 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 6 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 7 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 8 (Errors)

May 28 18:31:38 Tower kernel: Buffer I/O error on device md5, logical block 9 (Errors)

May 28 18:31:38 Tower emhttp: _shcmd: shcmd (82): exit status: -122 (Other emhttp)

May 28 18:31:38 Tower emhttp: shcmd (83): :>/etc/samba/smb-shares.conf (Other emhttp)

May 28 18:31:38 Tower emhttp: shcmd (84): cp /etc/exports- /etc/exports (Other emhttp)

May 28 18:31:38 Tower emhttp: get_config_idx: fopen /boot/config/shares/System.cfg: No such file or directory - assigning defaults (Other emhttp)

May 28 18:31:38 Tower emhttp: Restart SMB... (Other emhttp)

May 28 18:31:38 Tower emhttp: shcmd (85): killall -HUP smbd (Minor Issues)

May 28 18:31:38 Tower emhttp: shcmd (86): ps axc | grep -q rpc.mountd (Other emhttp)

May 28 18:31:38 Tower emhttp: _shcmd: shcmd (86): exit status: 1 (Other emhttp)

May 28 18:31:38 Tower emhttp: shcmd (87): /usr/local/sbin/emhttp_event svcs_restarted (Other emhttp)

May 28 18:31:38 Tower emhttp_event: svcs_restarted (Other emhttp)

syslog-2013-05-28.txt

Did you Pre-Clear the drives before trying to add/format them?  This has been a recurring issue with RC12a ... see this thread:  http://lime-technology.com/forum/index.php?topic=27221.0