I currently have one parity drive and one data drive in my unraid box and it was running just fine.  I just added today a second data drive, 500 gb.   It recognized the drive and I assigned it to a data drive 2.  Next, I went and selected the box, to start the clearing process under the main page.   It starts cleaning the new data drive, but after it gets to about 2%, I can no longer ping my unraid box from my Win7 pc, also, I can't access the unraid box via internet explorer on my win 7 pc.  \\tower

 

When I go to my unraid box, and try typing any commands in, it appears to be locked up.   The only way to get my unraid box going again is to cycle power.

 

Anyone have any ideas why it is locking up the unraid server during the clearing process?   Is the drive I just added a bad drive?  

 

running unraid server basic v4.7

 

parity drive - 1TB ide on primary IDE

data drive 1 - 40 gig on sata 1

data drive 2 - 500 gig on sata 2 (this is the drive that is being cleared)

 

running on a dell optiplex gx270

 

Any suggestions would be greatly appreciated... thanks...

 

 

Feb  5 20:02:54 UNRAID kernel: REISERFS (device md1): checking transaction log (

md1)

Feb  5 20:02:54 UNRAID kernel: REISERFS (device md1): Using r5 hash to sort name

s

Feb  5 20:02:54 UNRAID emhttp: shcmd (15): rm /etc/samba/smb-shares.conf >/dev/n

ull 2>&1

Feb  5 20:02:54 UNRAID emhttp: shcmd (16): cp /etc/exports- /etc/exports

Feb  5 20:02:54 UNRAID emhttp: shcmd (17): mkdir /mnt/user

Feb  5 20:02:54 UNRAID emhttp: shcmd (18): /usr/local/sbin/shfs /mnt/user  -o no

atime,big_writes,allow_other,default_permissions

Feb  5 20:02:56 UNRAID emhttp: shcmd (19): killall -HUP smbd

Feb  5 20:02:56 UNRAID emhttp: shcmd (20): /etc/rc.d/rc.nfsd restart | logger

Feb  5 20:08:22 UNRAID in.telnetd[1305]: connect from 192.168.1.120 (192.168.1.1

20)

Feb  5 20:08:29 UNRAID login[1306]: ROOT LOGIN  on `pts/0' from `192.168.1.120'

Feb  5 20:15:39 UNRAID emhttp: shcmd (21): /etc/rc.d/rc.samba stop | logger

Feb  5 20:15:39 UNRAID emhttp: shcmd (22): /etc/rc.d/rc.nfsd stop | logger

Feb  5 20:15:40 UNRAID emhttp: Spinning up all drives...

Feb  5 20:15:40 UNRAID emhttp: shcmd (23): sync

Feb  5 20:15:40 UNRAID kernel: mdcmd (: spinup 0

Feb  5 20:15:40 UNRAID kernel: mdcmd (9): spinup 1

Feb  5 20:15:40 UNRAID emhttp: shcmd (24): umount /mnt/user >/dev/null 2>&1

Feb  5 20:15:41 UNRAID emhttp: shcmd (25): rmdir /mnt/user >/dev/null 2>&1

Feb  5 20:15:41 UNRAID emhttp: shcmd (26): umount /mnt/disk1 >/dev/null 2>&1

Feb  5 20:15:41 UNRAID emhttp: shcmd (27): rmdir /mnt/disk1 >/dev/null 2>&1

Feb  5 20:15:41 UNRAID kernel: mdcmd (10): stop

Feb  5 20:15:41 UNRAID kernel: md1: stopping

Feb  5 20:15:41 UNRAID emhttp: shcmd (28): rm /etc/samba/smb-shares.conf >/dev/n

ull 2>&1

Feb  5 20:15:41 UNRAID emhttp: shcmd (29): cp /etc/exports- /etc/exports

Feb  5 20:15:41 UNRAID emhttp: shcmd (30): /etc/rc.d/rc.samba start | logger

Feb  5 20:15:41 UNRAID logger: Starting Samba:  /usr/sbin/nmbd -D

Feb  5 20:15:41 UNRAID logger:                  /usr/sbin/smbd -D

Feb  5 20:15:41 UNRAID emhttp: shcmd (31): /etc/rc.d/rc.nfsd start | logger

Feb  5 20:15:45 UNRAID emhttp: shcmd (32): modprobe -rw md-mod 2>&1 | logger

Feb  5 20:15:45 UNRAID emhttp: shcmd (33): modprobe md-mod super=/boot/config/su

per.dat slots=8,0,3,0,8,16 2>&1 | logger

Feb  5 20:15:45 UNRAID kernel: md: unRAID driver removed

Feb  5 20:15:45 UNRAID kernel: xor: automatically using best checksumming functi

on: pIII_sse

Feb  5 20:15:45 UNRAID kernel:    pIII_sse  :  3508.800 MB/sec

Feb  5 20:15:45 UNRAID kernel: xor: using function: pIII_sse (3508.800 MB/sec)

Feb  5 20:15:45 UNRAID kernel: md: unRAID driver 1.1.1 installed

Feb  5 20:15:45 UNRAID kernel: md: import disk0: [8,0] (sda) ST31000528AS     9V

P7Q4BX size: 976762552

Feb  5 20:15:45 UNRAID kernel: md: import disk1: [3,0] (hda) WDC WD400BB-75FJA1

WD-WCAJA3516806 size: 39062468

Feb  5 20:15:45 UNRAID kernel: md: import disk2: [8,16] (sdb) WDC WD5000AAKS-0 W

D-WCAPW0132027 size: 488386552

Feb  5 20:15:45 UNRAID kernel: md: disk2 new disk

Feb  5 20:15:45 UNRAID kernel: mdcmd (1): set md_num_stripes 1280

Feb  5 20:15:45 UNRAID kernel: mdcmd (2): set md_write_limit 768

Feb  5 20:15:45 UNRAID kernel: mdcmd (3): set md_sync_window 288

Feb  5 20:15:45 UNRAID kernel: mdcmd (4): set spinup_group 0 0

Feb  5 20:15:45 UNRAID kernel: mdcmd (5): set spinup_group 1 0

Feb  5 20:15:45 UNRAID kernel: mdcmd (6): set spinup_group 2 0

Feb  5 20:15:53 UNRAID emhttp: shcmd (34): /usr/local/sbin/set_ncq sda 1 >/dev/n

ull

Feb  5 20:15:53 UNRAID emhttp: shcmd (35): /usr/local/sbin/set_ncq hda 1 >/dev/n

ull

Feb  5 20:15:53 UNRAID emhttp: shcmd (36): /usr/local/sbin/set_ncq sdb 1 >/dev/n

ull

Feb  5 20:15:53 UNRAID emhttp: clearing disk2 ...

Feb  5 20:18:14 UNRAID emhttp: ... clearing 1% complete

Feb  5 20:20:36 UNRAID emhttp: ... clearing 2% complete

Feb  5 20:21:13 UNRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 ac

tion 0x6 frozen

Feb  5 20:21:13 UNRAID kernel: ata2.00: failed command: WRITE DMA

Feb  5 20:21:13 UNRAID kernel: ata2.00: cmd ca/00:80:3f:0f:2e/00:00:00:00:00/e1

tag 0 dma 65536 out

Feb  5 20:21:13 UNRAID kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00

Emask 0x4 (timeout)

Feb  5 20:21:13 UNRAID kernel: ata2.00: status: { DRDY }

Feb  5 20:21:18 UNRAID kernel: ata2: link is slow to respond, please be patient

(ready=0)

 

 

I swapped the sata cable from data disk 1 (working hd) to data disk 2, and same results.  I swapped the sata power cables as well, same results on data disk 2. 

 

Perhaps the hd is bad, is my guess....

I ran a hd diagnostics, and it appears the hd is DOA....

 

So, that explains the issue...... 

I ran a hd diagnostics, and it appears the hd is DOA....

 

So, that explains the issue...... 

Assuming  you used a different port on the disk controller, you are probably correct. If you did not, it could be the disk controller port itself.

 

What program did you use for the hd diagnostics?

 

Joe L.

I ran easy recovery professional to test the hard drive.

Did you happen to run pre_clear on your new drive before adding it to the array?

http://lime-technology.com/forum/index.php?topic=10202.0

 

If not I would highly recommend always running it. It would test your drive and you would know if its bad before disturbing your array.

I ran pre_clear, and everything came back ok.

 

 

thanks for the help.  The drive is back alive again and kicking....

 

 

I ran pre_clear, and everything came back ok.

 

 

thanks for the help.  The drive is back alive again and kicking....

 

 

 

It may be back alive, but with 159 re-allocated sectors and an attribute that has apparently failed in the past I'd strongly recommend replacement.

 

I would not want that disk in my array.  Too risky.

 

One more thing.. your disk shows a temperature of 46C. (114.8F)

Temperatures above 40C are not recommended... Get more cooling.  It might be a contributing factor.

 

Joe L.

yeah, I kind of punted on that drive.  It was that hot because I had it sitting on the table with no fan on it.  My mistake......I just ordered two WD20EARS.

 

thanks for the help.....