I'm trying to finish up messing around in my case but barely brushed a sata cable evidently.  Ok, when it booted up it started a parity check by itself and after that red ball on disk2.  I thought I remembered what to do.  I stopped the array, unassigned disk2.  Then I reassigned disk2 and looked on the main page.  It now shows the disk2 with a blue ball and the parity disk has what looks like a pink ball.

 

So I went back and read the posting again and it actually said to unassign, start, stop and then reassign the drive.  Have I lost my data?

 

syslog-2010-02-27.zip

I'm trying to finish up messing around in my case but barely brushed a sata cable evidently.  Ok, when it booted up it started a parity check by itself and after that red ball on disk2.  I thought I remembered what to do.  I stopped the array, unassigned disk2.  Then I reassigned disk2 and looked on the main page.  It now shows the disk2 with a blue ball and the parity disk has what looks like a pink ball.

 

So I went back and read the posting again and it actually said to unassign, start, stop and then reassign the drive.  Have I lost my data?

 

 

As long as you did not press the button labeled "Restore" (which actually is a set disk configuration button)  you should not have lost your data. 

 

What steps did you perform?  What does it say next to the "Start" button?

 

Joe L.

According to the the syslog, at this time the array thinks:

Feb 27 00:39:30 Queeg kernel: md: disk0 wrong

Feb 27 00:39:30 Queeg kernel: md: disk1 removed

 

I thought you were talking about disk2 in your prior post?  I'm a bit confused.

According to the the syslog, at this time the array thinks:

Feb 27 00:39:30 Queeg kernel: md: disk0 wrong

Feb 27 00:39:30 Queeg kernel: md: disk1 removed

 

I thought you were talking about disk2 in your prior post?  I'm a bit confused.

 

Disk1 is right, I incorrectly said disk2 in my original post.  Just nerves I guess.

What steps did you perform?  What does it say next to the "Start" button?

Joe L.

I haven't pressed Restore.  I remembered not to do that.

Next to Start it says "Too many wrong and/or missing disks!".

At this point I have: Stop, unassign disk1, assigned disk1, unassigned disk1.  

The Start button has been grayed out following the Stop.

 

 

Why is it saying that disk0 (your parity disk) is the wrong disk? Did you change it?  Or, did you change the port it is plugged into?

Why is it saying that disk0 (your parity disk) is the wrong disk? Did you change it?  Or, did you change the port it is plugged into?

I don't know why it's saying that.  I didn't unassign it or change it in any way.  I haven't moved any of the disks or cables.

 

Edit:  I run a parity check every time I boot the machine and the last one was a couple of hours before this happened.  The parity disk changed status after  re-assigned the disk1 and I'd never seen that happen before so I stopped right there and posted for help.

Wow!  I decided to shutdown unRAID and reseat the cables for drive1 and the parity drive.  Both are locking cables and I had to press on the locking clip to get them off.  Drive1 was really securely attached.  The parity drive cable was well attached but not as snug as the other. 

Anyway, after booting up again the parity drive was a green ball again.  So only drive1 is red again.  I think I'll rebuild it.

Wow!  I decided to shutdown unRAID and reseat the cables for drive1 and the parity drive.  Both are locking cables and I had to press on the locking clip to get them off.  Drive1 was really securely attached.  The parity drive cable was well attached but not as snug as the other. 

Anyway, after booting up again the parity drive was a green ball again.  So only drive1 is red again.  I think I'll rebuild it.

Sounds good.

 

Joe L.

Ok, the drive is rebuilding.

 

I've ordered more sata cables (again).  Every one I have is a locking cable but two have straight ends going into the drives which I think makes them a little easier to nudge than right-angle connectors.  The new cables are also shorter at 9 inches instead of 18.  In my case the ends of the drives are right on top of the motherboard sata sockets and that leaves the excess cables coiled up which again probably increases nudgeability. 

Also, I'm going to probably tack them onto the drives with hotglue.  I had to do that for an esata cable and it worked miracles.  It keeps them from wiggling at all. 

 

Who invented sata cables connectors anyway?  Must have been the same person that came up with the S-Video connector.  The weight of the cable can pull them out of the socket! 

I wanted to follow up with some information.  One of my drives (disk2) has a defective latch mechanism.  Using several different latching cables I have discovered that I can brush against or tug the cable and it loosens up little at a time and will come completely out of the drive socket.  No other drives have that problem.  It's still under warranty so I'm going to see if I can get Seagate to replace it.  Until then, I'm using a little bit of hotglue to secure it in place.