So in the middle of a Write session it just stopped working and from now I just can't seem to move or copy any data to the array.  I installed this new 2TB drive as a replacement for a failed 1TB and it's only not working when I try to write to disk 3...

 

I have attached a syslog.  Something seems to have happened during the copy but I don't understand.  Below is a screenshot of the part of the log where something went wrong that I just don't understand.

 

 

I'm running version 5.0.5, considering upgrading to Version 6 and I'd like to ask if I should upgrade to 5.0.6 and then use the upgrade method rather than the clean install method (that is what I would rather), but I guess I've got to read through that page for more details.  Do you think upgrading will fix my problem?

 

Any other ideas that should fix the problem writing to only disk 2??

syslog-2015-08-07.zip

You say disk2 but the log says disk3. Why do you think it is disk2?

So in the middle of a Write session it just stopped working and from now I just can't seem to move or copy any data to the array.  I installed this new 2TB drive as a replacement for a failed 1TB and it's only not working when I try to write to disk 2...

 

I have attached a syslog.  Something seems to have happened during the copy but I don't understand.  Below is a screenshot of the part of the log where something went wrong that I just don't understand.

...

I'm running version 5.0.5, considering upgrading to Version 6 and I'd like to ask if I should upgrade to 5.0.6 and then use the upgrade method rather than the clean install method (that is what I would rather), but I guess I've got to read through that page for more details.  Do you think upgrading will fix my problem?

 

Any other ideas that should fix the problem writing to only disk 2??

 

You have a hardware issue and a file system issue, both of which would be identical in any OS, so an upgrade won't change anything.  Note: There's no need to upgrade to v5.0.6, just upgrade directly to v6 with the 'upgrade' method.

 

For Disk 3 (the one with the file system corruption), see Check Disk File systems, use the appropriate section.

 

The syslog has been rotated, meaning there was a lot more of it previously, and while I can't say for sure, it's likely the drive attached to ata9.00 has been causing a lot of trouble.  Without the first part of the syslog, I can't confirm that the ata9 drive is Disk 3 or Disk 2, or something else instead.  Can you provide another syslog after a reboot?

 

The drive at ata9 has a strange interface issue, that is causing constant pauses.  It doesn't appear (from this short syslog piece) that it has a bad SATA cable.  That leaves the suspects as a defective SATA port (try switching it once we identify it), bad power connection, bad power, overheating drive?  May be something else, that's all I can think of, power to the drive is what I suspect most.

You say disk2 but the log says disk3. Why do you think it is disk2?

 

Sorry I meant disk3...

So in the middle of a Write session it just stopped working and from now I just can't seem to move or copy any data to the array.  I installed this new 2TB drive as a replacement for a failed 1TB and it's only not working when I try to write to disk 2...

 

I have attached a syslog.  Something seems to have happened during the copy but I don't understand.  Below is a screenshot of the part of the log where something went wrong that I just don't understand.

...

I'm running version 5.0.5, considering upgrading to Version 6 and I'd like to ask if I should upgrade to 5.0.6 and then use the upgrade method rather than the clean install method (that is what I would rather), but I guess I've got to read through that page for more details.  Do you think upgrading will fix my problem?

 

Any other ideas that should fix the problem writing to only disk 2??

 

You have a hardware issue and a file system issue, both of which would be identical in any OS, so an upgrade won't change anything.  Note: There's no need to upgrade to v5.0.6, just upgrade directly to v6 with the 'upgrade' method.

 

For Disk 3 (the one with the file system corruption), see Check Disk File systems, use the appropriate section.

 

The syslog has been rotated, meaning there was a lot more of it previously, and while I can't say for sure, it's likely the drive attached to ata9.00 has been causing a lot of trouble.  Without the first part of the syslog, I can't confirm that the ata9 drive is Disk 3 or Disk 2, or something else instead.  Can you provide another syslog after a reboot?

 

The drive at ata9 has a strange interface issue, that is causing constant pauses.  It doesn't appear (from this short syslog piece) that it has a bad SATA cable.  That leaves the suspects as a defective SATA port (try switching it once we identify it), bad power connection, bad power, overheating drive?  May be something else, that's all I can think of, power to the drive is what I suspect most.

 

Thanks for the help... Did you check the full syslog that I attached to the post because the screenshot was just a cut out part...

 

I did mean disk 3 not disk 2 so that is definitely a mistake in trying to get the right help... Dunno what to do.  I'll go through the checkdisk stuff but I'm scared of the reisrschk or whatever it is.

I've upgraded to V6 and nothing has changed... it seems like there is something wrong with the disk, or most likely the file system.  I upgraded to 6 so I could do the file system check in the GUI but I can't find the button that it says to press in that help page you linked me to.

 

I don't get it either... I just installed this drive, it's brand new... maybe it's failing, I just replaced a failed drive from this position in the stack.

 

Okay I've fixed it using the page linked by RobJ - http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

Thanks heaps.

The syslog has been rotated, meaning there was a lot more of it previously, and while I can't say for sure, it's likely the drive attached to ata9.00 has been causing a lot of trouble.  Without the first part of the syslog, I can't confirm that the ata9 drive is Disk 3 or Disk 2, or something else instead.  Can you provide another syslog after a reboot?

 

The drive at ata9 has a strange interface issue, that is causing constant pauses.  It doesn't appear (from this short syslog piece) that it has a bad SATA cable.  That leaves the suspects as a defective SATA port (try switching it once we identify it), bad power connection, bad power, overheating drive?  May be something else, that's all I can think of, power to the drive is what I suspect most.

 

Did you check the full syslog that I attached to the post because the screenshot was just a cut out part...

I of course was looking at the syslog you posted, but it's just a piece of the whole, the rest was rotated out.  The part that's gone has all of the setup, which is why I requested another syslog after a reboot, so we can figure out your other problem, why the drive attached to ata9 is causing pauses.  I'm glad you were able to fix the file system issue on Disk 3.  I don't doubt my wording could be clearer, I'm sorry for that.