July 18, 200817 yr So i had the problems in 4.3.1 but from what i understand the spinup logic has changed in 4.3.3. But it still does not work. I did a shutdown lastnight when quite a few of the drives were spundown and that was fine. Had the server on this morning and thought i would try a complete spindown and spinup as if it crashed no biggy as i wanted to do a parity check anyway before doing some drive upgrades. Well i could here the drives spinning up but totally lost control of the server. no webpage, no ping to it nothing so had to hard powerdown. I'm still wondering about the new kernel that was used in 4.3b4. 4.3b3 had none of these issues and that was spinning up all the spundown drives at the same time. Any help would be apreciated. I hate having to have all drives spunup all the time when they so not need to be just to stop the server from hanging. Thanks Mark
July 18, 200817 yr I've also been having the same problems. I told unRAID to put the drives to sleep after one hour. Within 12 hours the server stopped responding. Dead as a doornail. If I keep all drives spinning I have no problems except I use about 100 extra watts. At least the system is stable. Phil
July 18, 200817 yr This dead as a doornail is when you click the spin up button, or just accessing one or two drives?
July 18, 200817 yr The dead as a doornail is just trying to access the server or the web admin. The server is just dead. I have a monitor hooked up & it will not respond either. I never had this problem with 4.1 - The only problem now is that we are running the Supermicro 8 port sata card & the drivers for that card are not in 4.1. It looks like the drives do not wake up & it hangs everything. I can use the spin down & spin up buttons just fine. This only happens when I let the drives go to sleep after one hour. Since the server hangs I cannot get a syslog. Phil
July 18, 200817 yr Author In my case in this last test it was hitting the spinup. Not sure what happens if all drives are spundown and it hit the stop server button which i believe spins them all up so they can be unmounted. If that uses the same code as the spinup then i guess the same result will happen. Like i said lastnight i did stop the server but not all drives were spundown and that did work fine. I'm still pointing at that new kernel that went in for 4.3b4, maybe some interrupt clashes on spinning all drives up causes the kernel to crash. Spinups spindowns were rock solid with 4.3b3. Mark
July 19, 200817 yr The dead as a doornail is just trying to access the server or the web admin. The server is just dead. I have a monitor hooked up & it will not respond either. I never had this problem with 4.1 - The only problem now is that we are running the Supermicro 8 port sata card & the drivers for that card are not in 4.1. It looks like the drives do not wake up & it hangs everything. I can use the spin down & spin up buttons just fine. This only happens when I let the drives go to sleep after one hour. Since the server hangs I cannot get a syslog. Phil I had this exact same problem. I actually thought maybe one of my components was dying. Good to know it's not that.
July 19, 200817 yr The dead as a doornail is just trying to access the server or the web admin. The server is just dead. I have a monitor hooked up & it will not respond either. I never had this problem with 4.1 - The only problem now is that we are running the Supermicro 8 port sata card & the drivers for that card are not in 4.1. It looks like the drives do not wake up & it hangs everything. I can use the spin down & spin up buttons just fine. This only happens when I let the drives go to sleep after one hour. Since the server hangs I cannot get a syslog. Phil I had this exact same problem. I actually thought maybe one of my components was dying. Good to know it's not that. Did you ever fix your problem? Phil P.S. Sorry for the thread hijack. I'll also post this post in it's own thread.
Archived
This topic is now archived and is closed to further replies.