here is a smart report.

smart.txt

anyone?

The physical drive is fine.

 

It is producing buffer I/O errors when mounting is attempted, but there are NO physical disk errors at all, and no exception handlers are called, so either the I/O errors are spurious or the errors come from an attempt to mount a corrupt *virtual* Disk 1.  Is there any data on Disk 1?  And is Parity valid (and important, protecting valuable data)?  If not, I would recommend unassigning Disk 1 and the Parity drive, then Preclear Disk 1 (sdh in this syslog) with the -n option (skips the preread and postread), start the array without it, then stop the array, and add Disk 1 back and attempt a format.

 

Just a comment about XFS, this is very new territory and there is little to no experience here working with XFS.  I have no experience at all, and I doubt others have much experience with its tools and troubleshooting.  This is also all very beta, and I'm not sure getting started with a new array using beta software is the best idea.  If you are comfortable with it, then OK, but you will have to expect extra problems.  When you are on the leading edge, you will have to do some of your own troubleshooting, because very few others have been there yet.

Well the problem with unRaid 5 is it wont read my addon card.

 

Now i had done a preclear of disk 1 and the parity before all of this. All of the HDs are empty

Well the problem with unRaid 5 is it wont read my addon card.

Tom has been criticized, one instance quite recently, for not sticking with older, more stable LTS kernels, but he constantly faces pressure to support new hardware, like yours, so has to stay up within reason.  At other times, he gets criticized for staying too far behind the latest kernel releases.  It's a tough balancing act.  For your addon card and for XFS, you will need to stay current (6.0-beta9 and up), but I was just trying to make sure you were aware of the potential difficulties.  You have arrived when UnRAID is going through a transitional period.

 

Now i had done a preclear of disk 1 and the parity before all of this. All of the HDs are empty

 

Without data to protect, you don't really need a parity drive, and that's why I suggested removing it.  It just makes life easier without it, until everything is working correctly, and you have begun storing data of value on the array.

 

I suggested the quick Preclear (preclear with -n) because there's something strange with the current formatting on the disk, and it makes sense to clean it off and start fresh again.  Because previous tests were good, we can skip the preread and postread, and that shortens the Preclear time dramatically.

Well I will try that.

I had also gotten an IBM M1501 raid card and unRAID is not seeing any of the HDs that is attached to the card. I was told that I need to flash the card but I don't understand on how to go about that. (Never had a need to flash firmware).

I'm at this current point I will pay someone to fix this thing. I've had it since July and haven't been able to put data on it without it redballing or just loosing drives all together.

I want to start putting stuff on it and start learning on what else I can do with the unRAID os.

Nobody?

I'm afraid I'm confused.  You seem to be waiting for a response, but your previous post did not appear to me to have anything to respond to.  You posted what you were going to do.  Once you do some of them, I assume you will report what worked and what didn't, with any errors or wrong behavior displayed.  That would be something we could respond to.

 

But I'm not a very good communicator, so may have missed what you were trying to ask.

I'm in the same boat as Rob here.  Want to help but was waiting for you to provide feedback on the last test to perform...

What I am asking is for someone to set it up for me. I can give you temporarily access to the server. Via remote desktop.

[uPDATE] as of 10/4/2014 22:04

 

I had put back in my SuperMicro AOC-SAS2LP-MV8 card and made sure all my drives are XFS file format. No issues with transferring files now and so far no issues on red-balling! 

 

Why does it appear that my RAM is being sucked down? I have 32Gigs of RAM.(Why do I have that much you ask. Because I can! )

 

This is in the middle of transferring a file folder as well. From a windows machine to my nas. Folder size 1.32TB Speed:113MB/second

 

[uPDATE] as of 10/4/2014 22:04

 

I had put back in my SuperMicro AOC-SAS2LP-MV8 card and made sure all my drives are XFS file format. No issues with transferring files now and so far no issues on red-balling! 

 

Why does it appear that my RAM is being sucked down? I have 32Gigs of RAM.(Why do I have that much you ask. Because I can! )

 

This is in the middle of transferring a file folder as well. From a windows machine to my nas. Folder size 1.32TB Speed:113MB/second

 

Quite simple, unRAID buffers writes to ram before spooling to disk.  The more ram you got, the more it'll utilize.

 

PS, glad to see this is all working for you!

Okay Maybe I had spoke too soon on this issue. It had ran for a little while then it had just dropped all the HDs that was connected to the card. Rebooted the machines and it was saying the HDs are there but the second drive is red balled. I have tested multiple different hard drive in that slot with the same redball outcome.

 

 

So what are my options here.

What model PSU? Are you referring to a physical disk "slot",i.e., a drive bay?

What model PSU? Are you referring to a physical disk "slot",i.e., a drive bay?

 

the PSU is a Corsair AX860. It will narrow down to a physical disk. But if its the drive bay how can it make all 8 of the drives connected to the card mess up as well?

What model PSU? Are you referring to a physical disk "slot",i.e., a drive bay?

 

the PSU is a Corsair AX860. It will narrow down to a physical disk. But if its the drive bay how can it make all 8 of the drives connected to the card mess up as well?

I have found that if a disk starts playing up it is not that unusual for it to take down the controller card thus affecting all drives connected to that card.

im starting to wonder if its the icy dock that is causing the issue.

but if that was the case wouldn't i see it when it was doing the pre-clear... for the (9th time)

A few people including myself had seen some strange issues with the controller going out and taking all the disks out as well as some strange IO problems.  For some reason if I boot under Xen the problem seems to go away and everything runs fine.  Have you tried booting under Xen to see what happens?

no not yet. I will however test it.

I booted it up in xen and so far its booted and I let the system rebuild it self. I haven't had time to check the data yet.

 

I did notice that the "bad" drive it was seeing was orange and once it got done it turned Green. However it still says unformatted. Do I format it even though its green?

If you want to erase the drive, format it. If you want to try to recover the data that was on it, don't.

I booted it up in xen and so far its booted and I let the system rebuild it self. I haven't had time to check the data yet.

 

I did notice that the "bad" drive it was seeing was orange and once it got done it turned Green. However it still says unformatted. Do I format it even though its green?

Do not format the drive bless you want to lose any data it might contain.  The "unformatted" state often means that unRAID failed to mount the drive due to some sort of file-system corruption.  With the latest beta it can also happen if the system loses track of what format the drive is meant to be (does it show the orrect format in the GUI?).

 

The normal way forward for filevsystem corruption is to put the array into maintenance mode and run the appropriate repair utility against the /dev/md? Device corresponding to the problem disk.  This is reiserfsck for ReiserFS format drives and xfs_repair for xfs drives.