I was adding a new WD250 GB drive.  First, I ran a full disk test using a WD diagnostic diskette and came back with no errors.

 

Jumpered drive as CS (as all my drives are) and plugged into last connector on the promise TX2 (I only have 1 card installed presently and y model type set to MD800/IDE).  Started the UnRaid and the web manager showed the new disk as expected and clicked the button to start the format and clear.  After getting to 100% cleared, the next message said expanding array.  So far everything seemed normal.  Sometime after, the web manager screen refreshed with a message that the page I was looking for was unavailable.  I let everthing sit for over 2 hours since I didn't know the status of the array expansion.  After searching through the forum, I telnetted in and did a head and tail on the syslog.

 

  ...
Aug  9 02:47:12 Tower kernel: md: import hdg WDC WD2500JB-00GVC0 WD-WCAL78176670 offset: 63 size: 244198552
Aug  9 02:47:12 Tower kernel: md: import hdh WDC WD2500JB-00GVC0 WD-WCAL78378586 offset: 63 size: 244198552
Aug  9 02:47:12 Tower kernel: md7: new disk
Aug  9 02:49:38 Tower kernel: hdh: dma_timer_expiry: dma status == 0x61
Aug  9 02:49:48 Tower kernel: hdh: error waiting for DMA
Aug  9 02:49:48 Tower kernel: hdh: dma timeout retry: status=0x20 { DeviceFault}
Aug  9 02:49:48 Tower kernel:
Aug  9 02:49:48 Tower kernel: PDC202XX: Secondary channel reset.
Aug  9 02:49:49 Tower kernel: ide3: reset: master: error (0x0a?)
Aug  9 02:50:19 Tower kernel: hdh: lost interrupt
Aug  9 02:50:19 Tower kernel: hdh: set_multmode: status=0x00 { }
Aug  9 02:50:49 Tower kernel: hdh: lost interrupt
Aug  9 02:50:49 Tower kernel: hdh: recal_intr: status=0x10 { SeekComplete }
Aug  9 02:50:49 Tower kernel:
Aug  9 02:50:49 Tower kernel: hdh: status error: status=0x34 { DeviceFault SeekComplete CorrectedError }
Aug  9 02:50:49 Tower kernel:
Aug  9 02:50:49 Tower kernel: PDC202XX: Secondary channel reset.
Aug  9 02:50:49 Tower kernel: hdh: no DRQ after issuing WRITE
Aug  9 02:50:49 Tower kernel: end_request: I/O error, dev 22:41 (hdh), sector 15005374
Aug  9 02:50:49 Tower kernel: end_request: I/O error, dev 22:41 (hdh), sector 15005376
Aug  9 02:50:49 Tower kernel: end_request: I/O error, dev 22:41 (hdh), sector 15005378
   ...
Aug  9 02:51:51 Tower kernel: end_request: I/O error, dev 22:41 (hdh), sector 28902706
Aug  9 02:51:51 Tower kernel: end_request: I/O error, dev 22:41 (hdh), sector 28902708
Aug  9 02:51:51 Tower root@Tower:~#

 

From above syslog, hdg is a previous WD drive that was installed and working, hdh is the newest drive that is the same model as hdg.  By now it was very late so I did a stop and shut off the server.   Today, I started the server and the web manager showed that disk6 and disk7 shows up as missing with a message that the array is stopped and that there are "Too many wrong and/or missing disks!"  Tried shutting down and unplugging the newest disk7 and restarting.  I get the same message on the web manager.

 

Disk6 was almost filled so I really hope that I didn't lose any data.  Should I unplug the newest disk7 and reset the array and begin again?  Should I reset the array without unplugging the new disk?  Any ideas as to why the disk expansion failed?

 

I'm running version 1.050930

 

Thanks...

Ed

 

 

Ed,

Suggest you check all the cabling, then go to Tools and click Reset Array Config, then back to Main and click Start.  Probably new disk will show up as unformatted and the Format button will be there.  If so go ahead and format disk7 and see if errors persist.  Not likely you lost any data on disk6.

 

If you wanted to be absolutely safe about this, remove or leave powered off, all other disks, including parity.  (Only disk7 installed).  Then you can Reset Array Config & format & test disk to see if it works.  If all goes well, re-install other disks, reset array config again, and Start.

 

Also consider upgrading to the latest release.

Wow Tom,

 

Thanks for the quick reply,  I'll try the the safer method first.  I'm planning on upgrading but haven't had much time lately.

 

Thanks..

Ed

I disconnected all other drives except for the new drive and UnRaid seemed to see the drive OK.  I removed the new disk and reconnected the original drives and reset the array.  The next day, I decided to try again with another new in the box WD drive that was going into my main computer.  After about 24% into the clearing stage, I lost contact with the unRaid, both the web page and I was also telnetted in and the telnet window disconnected.  I let it sit for a few hours since I could not even ping the IP address.  I shut it off using the power switch.  Switching it on again, I was presented with a stopped array and a button to clear the new drive.  I agian started the clear and this time, it completed 100% of the clear and remounted all the drives.  When the web page refreshed, the new disk still said it was unformatted.  This has happpened to my array once before when I was adding my 4th or 5th drive.  I  reset the array and it is presently doing a parity sync, but the new disk still says it is unformatted.

 

So I seem to have a few semi-consistent problems,  I often lose contact with the server and have various problems adding a new drive.

I guess I should update my software, I am at 1.050930.  Since my main use of my unRaid is the archive HD recordings that really can't be replaced easily (ie I'm not serving rips of DVDs or CDs that I can just re-rip, I would have to hope to catch a rerun of the HD broadcast), which version should I try?  Can someone point me to the download and updat instructions?

 

Thanks again