Friday evening I:

 

stopped my array (5.06pro)

removed my 2Tb parity drive from listing

turned the system off

(all via http interface)

Replaced 2Tb parity drive w/ 4Tb precleared drive

Restarted the system

Went into menu and added new parity drive

System began rebuilding parity

And that's the last response I've gotten from the unraid http interface

Sabnzbd, Sickbeard and PLEX all function normally

My samba shares are available.

Telnet login works.

For the first 12 hours or so, ALL my drive LEDs were on (all 17)...which I expected

NOW, only the LED for the new cache drive is lit.

But....still no response via http

My sabnzbd screen shows "sysload 23.98" (it's usually much lower)

 

So far....

 

I've tried to restart emhttp using the instructions here: http://lime-technology.com/forum/index.php?topic=17239.0

The initial response was:

[1] 26148

 

I did it again, and the system responded:

[2] 27997

 

Neither attempt brought back a response to an http query.

 

I've pulled up a listing using the "TOP" command, have NO idea what to look for. I have 8Mb of RAM & haven't had any issues before.  I probably should've chosen to boot into safe mode before starting this, but what's done is done.

 

It looks like some things are okay, but I'd REALLY like to know why my system is unresponsive....and what it's doing.

 

??

That method of restarting emhttp no longer works in v5.

 

What do you get with

ps aux | grep emhttp

?

I get this:

 

root      8444  0.0  0.0  5776  1516 ?        D    Jan16  0:00 /usr/local/sbin/emhttp

root    20047  0.0  0.0  2452  588 pts/0    S+  18:09  0:00 grep emhttp

root    26148  0.0  0.0  3604  1228 pts/0    D    17:32  0:00 emhttp

root    27997  0.0  0.0  3604  1228 pts/0    D    17:34  0:00 emhttp

 

 

Looks like you have multiple emhttp. Don't know if that's because you tried to restart it or not. There have been other reports of this.

 

Don't know of any fix other than rebooting. Do you have the powerdown plugin installed? If so then you can run it from the command line to get a safe shutdown.

I looked at the 'reports' link. 

 

It's implied there, that the emhttp restart does work in 5.xx

 

I'm REALLY trying to avoid doing a dirty restart under the circumstances....

 

FWIW, a TOP command gives me this:

 

top - 19:30:48 up 21:32,  1 user,  load average: 26.54, 26.42, 26.35

Tasks: 316 total,  1 running, 315 sleeping,  0 stopped,  0 zombie

Cpu(s):  2.2%us,  5.1%sy,  0.7%ni, 91.5%id,  0.0%wa,  0.0%hi,  0.4%si,  0.0%st

Mem:  8311092k total,  7859224k used,  451868k free,  182316k buffers

Swap:        0k total,        0k used,        0k free,  6579020k cached

 

If you don't think you can do a safe shutdown that's probably not that bad from the situation you describe. None of your data disks are having problems, and it was trying to do a parity rebuild. If you have an unsafe shutdown, it is going to either 1) continue the parity rebuild after the reboot, or 2) start a correcting parity check, or 3) go back to wanting you to assign the new parity disk. All these are pretty much equivalent as far as your data is concerned, in that you have your data but your parity is invalid and you will rebuild it, which is what you have to do anyway.

 

Issued the powerdown command via telnet (It is installed, I just had this feeling it wouldn't work, given the server's unresponsiveness)

 

And it didn't.

 

Response:

 

Capturing information to syslog. Please wait...

version[4289]: Linux version 3.9.11p-unRAID (root@Develop) (gcc version 4.4.4 (GCC) ) #5 SMP Sat Dec 21 19:37:06 PST 2013

ls: cannot access /dev/hd[a-z]: No such file or directory

ls: cannot access /dev/hd[a-z]: No such file or directory

 

And that's where it sits.  Given my luck this weekend, I don't expect it will go further.  I'm going to force a restart, boot into safe mode and HOPE, I guess. 

 

Simply upgrading a drive shouldn't be this difficult!

 

Thanks for responding, trurl. 

 

[glow=red,2,300]Update:[/glow]

I've restarted and the system tells me it'll be about 2 days before it's done with the parity check...assuming it finishes without grinding to a halt.  :(

If you haven't already restarted, you might take the opportunity to put the flash in your pc and let it do checkdisk. Not clear that anything like that would have anything to do with your specific problem, but if unRAID thinks the flash is not writable it won't be able to save any changes.

Thanks for the suggestion, but I'm already on a road with no turns.  I'll just have to do without TV for a couple days...and hopefully any missed downloads will still be available when/IF I regain control of my system.

If the parity check doesn't speed up some it might be worth posting a syslog. My 4TB parity checks usually take about 10 hours.

 

Does the webGUI show any drive errors?

 

Edit: I would expect a parity rebuild to take longer than a parity check. I don't remember exactly what mine took when I upgraded my parity disk but I'm pretty sure it was still quite a bit less than a day.

Currently at 1%, 2500 minutes remaining (figure is very unstable), but no errors.  It automatically started doing a parity check.  My checks usually take about a day.  (My server is one of the Tams units- so it's not quite as fast as new hardware)

 

...the good news is- the http page is still responsive, whereas before it was almost instantly unresponsive, so maybe it'll FINISH this time.

The automatic parity check is correcting, and since the rebuild never finished it will probably have a lot of corrections to write so expect it to be somewhat slower than a normal parity check.

[glow=green,2,300]Results:[/glow]

 

After about 36 hours, my system finished the correcting parity scan:  with ZERO errors/corrections, so whatever was causing the unresponsiveness WASN'T preventing its first parity scan.

 

The only closing advice I can leave from my experience: When you replace a drive, restart in safe mode ...if you wanna be able to monitor its progress.