I'm posting another thread on this issue and hopefully a response from Tom will be forthcoming.

 

Looks like i have not been the only one with issues with spinup/spindown. Its really got to be a nuisance now.

 

Over the weekend i switched back to 4.3b3 and all the issues were gone.

 

I can spin all the drives down and spin them all up without any issues so i'm convinced its not a hardware or power issue.

 

Going back to 4.3.3 all the problems appear again.

 

Is it all all possible to go back to the linux kernel that was used in 4.3b3 as it changed in 4.3b4.

I'm really tending to believe that that is the cause of the problems people including myself are seeing.

 

I've recommended unraid to quite a few people and said it just plain works, which it has.

 

Due to recent troubles though i can no longer say that.

 

Mark

 

Marky

 

Not sure if this will help or not.  I also had a number of intermittent lockup issues after the kernel change in 4.3b4+, generally within a few hours of starting up.  I don't think it was spinup/down related, more the kernel change - feel free to ignore if it it does not match your problem.

 

I managed to catch the error a couple of times by running a tail -f on the syslog in a telnet session, so that when it locked up there was info on why - this process is described in a few places in the forums I believe.  Looking back now I cannot find the exact error but it involved interrupts and I seem to remember something like "irq 19: nobody cared!" just before the failure. 

 

Just like you the system had been stable for many versions up to that one.

 

In the end my problem was sorted out by adding irqpoll to the append line of syslinux.cfg.  After that back to rock solid.

 

Sorry I cannot be more specific - it is amazing what you forget once a problem goes away.

 

Oh - for reference my mobo is a rather old ASUS P4P800 SE with an additional 2 x 4 port Sil3114 controllers.

 

- Doug

Hi Doug,

 

I may just give that a try and see if it makes a difference.

 

Under normal use with 4.3.3 everything is fine, its only when there's a spinup of all drives that problems occur.

 

Mark

 

Hi Doug,

 

I may just give that a try and see if it makes a difference.

 

Under normal use with 4.3.3 everything is fine, its only when there's a spinup of all drives that problems occur.

 

Mark

 

 

Yes, I am still seeing the same thing with spinup/spindown. My mobo has integrated graphics and I have it connected via VGA to one of my desktop monitors, which is connected to my main PC via HDMI. The console displays a kernel panic on spinup/spindown commands which result in a 'hang'. This doesn't happen every time I spin up and spin down, but the kernel panic happens ONLY when spinning up/down occasionally. I thought it may be a power issue, but I'm not so sure. To add to the weirdness - and this has by no merans been tested systematically - when I spin up/down from my HTPC using the web interface, I have hitherto never duplicated the kernel panic. Weird indeed.

Is there any reason why I shouldn't go back to 4.3b3? I say 'go back to' in the sense that it may be an earlier, more stable version; I never used it before (upgraded directly from 4.2.1).

I don't think there is any reason to not use 4.3b3 apart from if you want cache disk support as i believe that was 4.3b4 onwards.

 

Of course 4.3b4 and onwards have the newer linux kernel which i think is the root cause of all these problems.

There was also a bug introduced i believe with clearing disks and giving incorrect parity or something.

 

I really would like to stay on latest and have this problem fixed but if not then it might be a case of going

back to 4.3b3 as that was rock solid for me.

 

Mark

 

I did install a cache drive, but then removed it because I wasn't sure how to use it properly. I'll see what happens in the next week or two, and then I'll just go back to 4.3b3 and try that. I really don't like the uncertainty that I now have with my unRAID server. It was rock solid before I made several concurrent changes. It's most likely something unrelated to the unRAID version in my case, but I'll undo the changes I made one at a time to get my unshaking faith back in my system if I have to.