Tom,

 

So check this. I pulled the two Seagates out of the array because they were blank and I wanted to see what would happen if I moved disk8 (which has been working fine) into the disk6 position.  There is just something whacked going on with my Promise card.... I have tried a lot of different things tonight and I think this card might be shot. But, does that also mean that my second card has something strange happening? I am not sure.... right now I am rebuilding parity because of all crazy stuff that I have done....

 

The two Seagates that gave me problems were

ST3200826A

ST3300631A

 

There are both our of the system and so is my old /disk 8 which is a 200gb Hitachi.  Hopefully parity rebuilds with no problem. Question starts, where the hell should I go from here?

 

Also, as an FYI I bought your 'starter kit' and all of the problems really began once I got to /disk6 or /disk7.  I have two other hard drives that are waiting to go into the system (not the seagates or Hitachi, but new unformatted brand new to unRAID.)  well, i have more than this, I have 400 and 500 sata + another 3 ide I want to get into another system or mix and match, but I need to first figure out what the hell is going on here

Send me your contact info & I can send you another Promise card.  Which PCI slots are you using for the Promise cards? Of the 3 on the D865GLCLK, we leave the middle one empty, Promise controllers in the other 2 - shouldn't make a difference, but....

I am using 1 and 2 slots. I will move the second one down to #3 and report back I rebuilt parity with no problems at all.

 

My main question is how the hell do we RMA these mobile rack units? I have 3 confirmed bad ones, and as you know icydock.com f'ing sucks the big one when it comes to anything. I really, really dislike their their lack of return/warranty policy. You fill out a form on their website and then nothing, no RMA # no nothing!!!!!! I am going to contact the supplier that I purchased them from and see what they are willing to do! I really hate bad customer service since I am a manager @ Motorola in our call center and we have a best-in-class rating.... and we will do anything for our authorized two way dealers!!!

Update: so is anyone besides Tom even following this terrible thread  :

 

So, the two drives that were giving me problems... I pulled them from the array and I was running SeaTools on them last night and both drives locked up during those tests. I think I just might have some bad drives, I am going to RMA the drives to Seagate and I will report back.

 

Note2: I threw in a 120 GB hard drive into /disk7 and had ZERO problems. I have another 250 GB drive that I am going to put into /disk8 and see what happens tonight.

Update: so is anyone besides Tom even following this terrible thread  :

 

So, the two drives that were giving me problems... I pulled them from the array and I was running SeaTools on them last night and both drives locked up during those tests. I think I just might have some bad drives, I am going to RMA the drives to Seagate and I will report back.

 

Note2: I threw in a 120 GB hard drive into /disk7 and had ZERO problems. I have another 250 GB drive that I am going to put into /disk8 and see what happens tonight.

Yes... I've been following along

 

Ouch... both drives locked up when using the Seagate Diagnostic disk ... bummer.

Never figured on multiple disks being the issue.  Were they purchased at the same time? (from the same  production run perhaps?)

 

Joe L.

Joe,

 

Well it is a possible combination of problems

 

1. Hard drives have something wrong with them!

2. 2-3 of the mobile rack units are bad

3. Power supply issue? I can't be sure, but I am going to keep my 430watt Sea Sonic quiet P/S in there and just purchase a new one for my HTPC

4. Possible controller card? I will be testing out the second controller card.

5. I did have 2 bad IDE round cables (these things are junk and I stuck with ribbon cables)

 

That was a lot of testing, but the nice thing is that I didn't loose ANY DATA, the OS and unRAID software did not cause ANY of these problems (that we know of) and the OS seems to be pretty stable.

 

So tonight, I will be adding some hard drives to the second promise card and see what the hell happens!

 

Now, I need to figure out how-to RMA these mobile rack units (it is a joke of customer service)

Joe,

 

Also the hard drives, purchased at different times from different stores... so who knows.. but one made it through 3 times to about 75% on the SeaTools and the other made it to 50% before locking up the computer...

I'm still following along.  Ouch quite ride!

Well,

 

I added /disk8 and /disk9 last night. Everything seems to have went smooth. I moved the second promise card to the third PCI slot... did that have anything to do??? I don't know. I am out of IDE drives so I can't fully test out the rest of the promise card, but just wanted to let everyone know that things are looking good as or right now! I will keep you posted; as I am hoping to cause more problem by upgrading to 3.0 and I plan on doing a SATA/IDE mix 

Update: so is anyone besides Tom even following this terrible thread  :

 

So, the two drives that were giving me problems... I pulled them from the array and I was running SeaTools on them last night and both drives locked up during those tests.

 

I'm following, with morbid interest (it's like the rubberneckers on the other side of the Motorway (Interstate/Highway/Turnpike for you US types ), who slow down to look to see just *how bad* the accident is, that happened to someone else, on the other carriageway...

 

IIWY, I'd try running Spinrite (from GRC.com) on those drives to see if they can be recovered!

 

HTH,

 

Matt

Well, I tried to add /disk 9 and I got throught he clearing stage to about 85% and that was it.... I think it might be this promise card... because I was never able to get /disk9 to behave properly... ugh, this thing is just now messing my whole array up!!!!

 

Sep 19 19:45:08 Tower kernel: hdk: status timeout: status=0xd0 { Busy }

Sep 19 19:45:08 Tower kernel:

Sep 19 19:45:08 Tower kernel: PDC202XX: Secondary channel reset.

Sep 19 19:45:08 Tower kernel: hdk: drive not ready for command

Sep 19 19:45:08 Tower kernel: reiserfs: found format "3.6" with standard journal

Sep 19 19:45:08 Tower last message repeated 6 times

Sep 19 19:45:19 Tower kernel: reiserfs: checking transaction log (device md(9,1)

) ...

Sep 19 19:45:19 Tower kernel: for (md(9,1))

Sep 19 19:45:34 Tower kernel: reiserfs: checking transaction log (device md(9,3)

) ...

Sep 19 19:45:34 Tower kernel: for (md(9,3))

Sep 19 19:45:38 Tower kernel: ide5: reset timed-out, status=0x80

Sep 19 19:45:38 Tower kernel: hdl: set_geometry_intr: status=0x11 { SeekComplete

Error }

Sep 19 19:45:38 Tower kernel: hdl: set_geometry_intr: error=0x11 { SectorIdNotFo

und AddrMarkNotFound }, CHS=4369/1/17, sector=0

Sep 19 19:45:38 Tower kernel: hdl: recal_intr: status=0x10 { SeekComplete }

Sep 19 19:45:38 Tower kernel:

Sep 19 19:45:38 Tower kernel: hdl: recal_intr: status=0x10 { SeekComplete }

Sep 19 19:45:38 Tower kernel:

Sep 19 19:45:46 Tower kernel: reiserfs: checking transaction log (device md(9,2)

) ...

Sep 19 19:45:46 Tower kernel: for (md(9,2))

Sep 19 19:45:56 Tower kernel: reiserfs: checking transaction log (device md(9,5)

) ...

Sep 19 19:45:56 Tower kernel: for (md(9,5))

Sep 19 19:46:03 Tower kernel: reiserfs: checking transaction log (device md(9,4)

) ...

Sep 19 19:46:03 Tower kernel: for (md(9,4))

Sep 19 19:46:06 Tower kernel: reiserfs: checking transaction log (device md(9,

) ...

Sep 19 19:46:06 Tower kernel: for (md(9,)

Sep 19 19:46:13 Tower kernel: hdl: lost interrupt

Sep 19 19:46:15 Tower kernel: reiserfs: checking transaction log (device md(9,9)

) ...

Sep 19 19:46:15 Tower kernel: for (md(9,9))

Sep 19 19:46:23 Tower kernel: hdl: lost interrupt

Sep 19 19:47:03 Tower last message repeated 4 times

Sep 19 19:47:10 Tower kernel: get_token: status

Sep 19 19:47:10 Tower kernel: hdf: drive_cmd: status=0x51 { DriveReady SeekCompl

ete Error }

Sep 19 19:47:10 Tower kernel: hdf: drive_cmd: error=0x04 { DriveStatusError }

Sep 19 19:47:20 Tower kernel: hdl: lost interrupt

Sep 19 19:48:00 Tower last message repeated 4 times

Sep 19 19:49:10 Tower last message repeated 7 times

Sep 19 19:50:20 Tower last message repeated 7 times

Sep 19 19:51:30 Tower last message repeated 7 times

Is the hard drive for disk9 the Seagate?  If so, try installing it as a Master device (even numbered disk) & put some other non-Seagate as disk9.

Is the hard drive for disk9 the Seagate?  If so, try installing it as a Master device (even numbered disk) & put some other non-Seagate as disk9.

 

Yes, it is the Seagate  : I was able to run it through a drive fitness test and it didn't lock up the computer so I thought I would give it a shot 

 

So what I did was reboot the server and I decided to just remove the hard drive because I am just going to RMA it because it has some odd issues and Seagate and those places I don't really think they check the HD's.... but now, when I boot the array it gets frozen and won't come online it just sits there and repeats the same errors that I posted above. Also, is it possible that /disk9 knocked out the hard drives on the other controller card? It seem to have hdL the problem... man just when I thought things were going better... I had to mess around..... but I had to try it out and see what happened... now I have an array that won't boot and I can't see the management page 

 

Tom, advise what you think I should do because I pulled the hard drive, but it is now giving me errors and the array won't boot 

Tom,

 

if you look @ those errors, those are actually not the /disk9 I believe that it is /disk6 and /disk7 which are on the first promise card... is it possible that this hard drive (/disk9) is actually causing those hard drives to behave like this, and give them DMA errors, etc? Rather crazy.....

I am keep thinking that this was actually disk10... so maybe it is something to do with that second ide bus on that promise card   I don't know... I just wish my array was up and running