System locked up today - black screen and no response to Ping. I restarted it and all drives were seen as "new" with the system Offline, I started it. Rebooted from console afterwards whenit seemed to hang and it came up fine while reporting Parity as bad - it began checking parity. It wasn't long before it was again unresponsive and I had to reboot it again.

 

This time I tailed the Syslog, sure enough it has locked up again - argh! I am not on the newest firmware, I am about 2 back actually and to this point have had ZERO issues. The log doesn't appear to have anything too interesting in it but I will post it below. I'd appreciate some suggestions cine I have quite a bit of data here and not being able to get to it is a PITA (lol).

 

Thanks!

 

P.S. Should I go ahead and upgrade? I am going to reboot one more time with fingers crossed....

 

 

BEAST login: root

Linux 2.4.31.

root@BEAST:~# tail -f /var/log/syslog

Aug 21 07:55:25 BEAST kernel: reiserfs: found format "3.6" with standard journal

Aug 21 07:55:25 BEAST last message repeated 2 times

Aug 21 07:55:26 BEAST kernel: reiserfs: checking transaction log (device md(9,2)                                                                                    ) ...

Aug 21 07:55:26 BEAST kernel: for (md(9,2))

Aug 21 07:55:29 BEAST smbd[1044]: [2006/08/21 07:55:29, 0] smbd/service.c:make_c                                                                                    onnection(798)

Aug 21 07:55:29 BEAST smbd[1044]:  monster (192.168.1.120) couldn't find servic                                                                                    e disk8

Aug 21 07:55:29 BEAST smbd[1044]: [2006/08/21 07:55:29, 0] smbd/service.c:make_connection(798)

Aug 21 07:55:29 BEAST smbd[1044]:  monster (192.168.1.120) couldn't find service disk8

Aug 21 07:55:32 BEAST kernel: get_token: status

Aug 21 07:55:33 BEAST kernel: reiserfs: found format "3.6" with standard journal

Aug 21 07:55:34 BEAST last message repeated 2 times

Aug 21 07:56:17 BEAST kernel: reiserfs: checking transaction log (device md(9,6)) ...

Aug 21 07:56:17 BEAST kernel: for (md(9,6))

Aug 21 07:56:30 BEAST kernel: reiserfs: checking transaction log (device md(9,4)) ...

Aug 21 07:56:30 BEAST kernel: for (md(9,4))

Aug 21 07:56:33 BEAST kernel: md(9,4):Using r5 hash to sort names

Aug 21 07:56:34 BEAST kernel: md(9,4):can't shrink filesystem on-line

Aug 21 07:56:38 BEAST kernel: reiserfs: checking transaction log (device md(9,7)) ...

Aug 21 07:56:38 BEAST kernel: for (md(9,7))

Aug 21 07:56:39 BEAST kernel: reiserfs: checking transaction log (device md(9,1)) ...

Aug 21 07:56:39 BEAST kernel: for (md(9,1))

Aug 21 07:56:39 BEAST kernel: reiserfs: checking transaction log (device md(9,) ...

Aug 21 07:56:39 BEAST kernel: for (md(9,)

Aug 21 07:56:41 BEAST kernel: md(9,:Using r5 hash to sort names

Aug 21 07:56:41 BEAST kernel: md(9,1):Using r5 hash to sort names

Aug 21 07:56:41 BEAST kernel: md(9,7):Using r5 hash to sort names

Aug 21 07:56:41 BEAST kernel: md(9,:can't shrink filesystem on-line

Aug 21 07:56:41 BEAST kernel: md(9,2):Using r5 hash to sort names

Aug 21 07:56:42 BEAST kernel: md(9,1):can't shrink filesystem on-line

Aug 21 07:56:42 BEAST kernel: md(9,7):can't shrink filesystem on-line

Aug 21 07:56:43 BEAST kernel: md(9,2):Removing [7303 17882 0x0 SD]..done

Aug 21 07:56:44 BEAST kernel: md(9,2):Removing [17833 17834 0x0 SD]..done

Aug 21 07:56:44 BEAST kernel: md(9,2):Removing [7303 17833 0x0 SD]..done

Aug 21 07:56:44 BEAST kernel: md(9,2):Removing [7303 17813 0x0 SD]..done

Aug 21 07:56:44 BEAST kernel: md(9,2):Removing [7303 17781 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17537 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17503 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [17479 17482 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17479 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17425 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17371 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17331 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [17310 17312 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17310 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17257 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 17010 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16806 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16787 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16767 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16752 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16679 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16516 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16327 0x0 SD]..reiserfs: checking transaction log (device md(9,3)) ...

Aug 21 07:56:45 BEAST kernel: for (md(9,3))

Aug 21 07:56:45 BEAST kernel: done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16313 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16294 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16274 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [16084 16087 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16084 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [16063 16066 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16063 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16038 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [16019 16021 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 16019 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 15944 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [15873 15875 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 15873 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 15764 0x0 SD]..done

Aug 21 07:56:45 BEAST kernel: md(9,2):Removing [7303 15727 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [15703 15705 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15703 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15658 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [15643 15645 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15643 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15621 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15590 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15467 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [15445 15447 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15445 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15422 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15404 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15250 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15231 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15197 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15180 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [15152 15154 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15152 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15134 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15101 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 15081 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [14927 14929 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14927 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14744 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14669 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [14636 14638 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14636 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14553 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14395 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14267 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [14248 14250 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14248 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [14228 14230 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14228 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [14209 14211 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14209 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14182 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 14068 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 13918 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [13877 13878 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 13877 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 13858 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 13835 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 13807 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [13761 13763 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 13761 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):Removing [7303 13715 0x0 SD]..done

Aug 21 07:56:46 BEAST kernel: md(9,2):There were 85 uncompleted unlinks/truncates. Completed

Aug 21 07:56:46 BEAST kernel: md(9,2):can't shrink filesystem on-line

Aug 21 07:56:46 BEAST kernel: reiserfs: checking transaction log (device md(9,5)) ...

Aug 21 07:56:46 BEAST kernel: for (md(9,5))

Aug 21 07:56:46 BEAST kernel: reiserfs: replayed 14 transactions in 29 seconds

Aug 21 07:56:46 BEAST kernel: md(9,3):Using r5 hash to sort names

Aug 21 07:56:46 BEAST kernel: md(9,6):Using r5 hash to sort names

Aug 21 07:56:46 BEAST kernel: md(9,6):can't shrink filesystem on-line

Aug 21 07:56:46 BEAST kernel: md(9,5):Using r5 hash to sort names

Aug 21 07:56:47 BEAST kernel: md(9,3):can't shrink filesystem on-line

Aug 21 07:56:47 BEAST kernel: md(9,5):can't shrink filesystem on-line

Aug 21 07:56:47 BEAST kernel: get_token: status

Aug 21 07:57:04 BEAST kernel: get_token: status

Aug 21 08:00:12 BEAST kernel: hdc: dma_timer_expiry: dma status == 0x61

Aug 21 08:00:22 BEAST kernel: hdc: error waiting for DMA

Aug 21 08:00:22 BEAST kernel: hdc: dma timeout retry: status=0x50 { DriveReady SeekComplete }

Aug 21 08:00:22 BEAST kernel:

Aug 21 08:00:42 BEAST kernel: hdd: dma_timer_expiry: dma status == 0x41

 

Oh, last commands on the console were:

 

shell_cmd: killall -w smbd nmbd

/usr/sbin/nmbd -D

/usr/sbin/smbd -D

 

That's all she wrote. First time it locked screenwas blackwhen I plugged it in. Second time it locked I saw this. 3rd time same thing. It wasn't likely to have been running parity the first time is locked...

Wellll - it's now 45% through the parity check. It hasn't locked up again so my fingers are crossed it's fine now. I'll be interested to see if the parity check finds any errors - I suspect it will.

 

To date the only weird thing other than this was the system having some files on it I'm unable to delete - even from the Root login via Telnet. Seems like if you have oddball characters in some filenames or attributes when copying from someplace else it screws things up. Dunno' if that has anything to do with this and it does look like it had some errors in the F/S that are hopefully cleaned up now - it reported the exact same errors on two boots. <shrug>

 

I'll report back when I know more - might be time to put the new firmware in place

Wellll - it's now 45% through the parity check. It hasn't locked up again so my fingers are crossed it's fine now. I'll be interested to see if the parity check finds any errors - I suspect it will.

 

I'll report back when I know more - might be time to put the new firmware in place

I hope your problems are behind you but...

 

I think one of the improvements with newer releases was better handling of disk errors. More importantly, until the most current release NONE of the prior releases would allow you to replace a failed drive without copying the data to a different drive in a different slot or on a different machine on your LAN,  resetting the array, and then copying the data back. unRaid would not restore a failed drive in place.

 

In my opinion, it is way past time for you to upgrade to the new firmware.  It may not fix your disk failure/system freezes, but it will matter if one of your disks is failing and you want to rebuild it from the remaining working drives.

 

Joe L.

 

Okay, looks like I'llupgrade. I can say though that I have swapped out a bad disk without too many issues however it was a Parity drive rather than a data drive so perhaps that doesn't count I've been a bit gunshy simply because my system has been working without issue and I'd seen some issues with a beta after the one I was running. FWIW I'm nto running the base code but the very first beta (as I recall). Will see about upgrading this evening if I can catch the network at a quiet period

 

thanks!

 

P.S. Weird that I got no e-mail notification of an update here...

Okay, looks like I'llupgrade. I can say though that I have swapped out a bad disk without too many issues however it was a Parity drive rather than a data drive so perhaps that doesn't count I've been a bit gunshy simply because my system has been working without issue and I'd seen some issues with a beta after the one I was running. FWIW I'm nto running the base code but the very first beta (as I recall). Will see about upgrading this evening if I can catch the network at a quiet period

 

thanks!

My unRaid server has also been very stable, only time it has gone down is when power failures occurred before I put it on a UPS. or when I rebooted it.

 

Understand about not wanting to be the first to upgrade... In this case, you are nowhere near the first and, more importantly, there was a fairly major bug in the code used when re-building a data drive in ALL the previous releases.  It did not work if the replacement drive was brand new and not previously partitioned/formatted using unRaid.  Tom kept re-using the same drives again and again in his tests, so he never stumbled across the failure users saw when a upgrade of an existing drive or replacement of a failed drive was attempted.

P.S. Weird that I got no e-mail notification of an update here...

I don't remember if one was ever sent by Tom...  I agree, sure would have been nice though..

Just another indication that customer communications is not Tom's strong point these days.

 

Joe L.

Am all upgraded now, system seems fine, maybe quicker but really hard to tell.

 

Notification I was referring to was the BBS letting us know about responses to posts here. I am actually pretty sure I'm subscribed to the announcements forum so new threads ought to get sent to me. <shrug> I do wish that we had some status so far as moving to the 2.6 kernel but overall I'm pretty happy. Just freak out a bit when something tips over my server and it doesn't come right back up 

Your issue was right near the end of that log dump, the DMA errors.  The newest version includes an OS upgrade which is said to handle DMA errors better but I can tell you all from personal experience that DMA errors like you had will STILL lock the system up, not fixed in the new release only less likely to happen I guess.

 

I have a handful of older 250GB drives now that work fine in Windows machines but trash the UnRaid everytime with these DMA errors.

The strange thing is this array has run for MONTHS without issue <shrug> It has now run for another couple of weeks without locking up too - very odd. I do now have another error I will post about in a second - doh!