October 26, 200619 yr I upgraded a 200GB drive to a 400GB drive no problem and added a 300GB Seagate to the array. It is drive 12 and it is taking FOREVER to clear. I don't notice any unusual errors... no dock, connected directly to Promise card... any idea why it would take thing long? I swear... Seagates give me lots of problems for some reason.....
October 26, 200619 yr teamhood, Both of my replacement parity drives (300GB to 400GB) are Seagate and I had no problem with the new parity generation. Regards, TCIII
October 27, 200619 yr Author /dev/hdf: Model=ST3300631A, FwRev=3.04, SerialNo=5NF1K9MF Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=off CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=no WriteCache=enabled Drive conforms to: device does not report version: looks like that is okay right? I don't get it... I will check the cable just to be sure! I tried to check parity and my speeds are terrible... I will let it run throughout the night and see what happens when I wake up
October 27, 200619 yr Author ok.. so I did what Tom said he had to do once... put it a Seagate as a master... well that seemed to work just fine.. that is just strange!! Parity is going like normal now w0000t
October 27, 200619 yr Author well.. I just woke up and things are still slow and parity did not complete. It was going about 18,000 KB before I went to sleep and now it is down to 2,000 KB What is this error Tom? Oct 27 04:44:07 Tower emhttp[1427]: smart ioctl: Input/output error I knew right away that it was going slow because the LEDs are blinking on the rack units instead of being pegged... ugh
October 27, 200619 yr That message means that a command to get the drive temperature failed. Is your syslog filled with errors? Also, post output of this command: cat /proc/ide/hda/settings
October 30, 200619 yr Author removed the other drive from the mobile rack unit that was using the same IDE BUS and it fixed everything. That now makes 6 BAD mobile rack units... and guess what good luck ever trying to warranty from icy dock... all I have to say is that I either purchased knock offs or I received 12 shitty units.... still, icy dock is impossible to get anywhere with when it comes to warranty.... I will never purchase anything from them again...
December 23, 200619 yr I'm building my second rig, 12 drives, mix of 50GB WD and 400GB Seagate, WD identified as parity. I started the array about 8 hours ago, from the time it started I have no web access, and not telnet access (the telnet session blanks out before I have access. Running 3.1 beta 2. I know that clearing takes a wile, but last time I was able to access the interface while it was happening. Could it be the Seagate problem? Should I step down to 3.0? Further: two (out of 4) of my Chieftec 3-2 Mobile Racks are now showing red lights (previously all green) for 4 drives affected, not sure whats going on there. update: fixed it with hard shutdown. The array "cleared" I guess some time within 12 hours... noway of knowing when. On reboot I could then go on to formating, etc..
Archived
This topic is now archived and is closed to further replies.