April 2, 201412 yr Last night I finally installed the Parity disk into unRaid. Since I mostly use 4TB drives it should take close to 24h to finish. This morning I get up to check on the status but the server is dead. It's running but unresponsive. I connected a monitor to it, but it only showed the login, keyboard was not working, network was not working. Even the power button did nothing! I had to press it for 5 seconds to shut it off. Of course the logs from last night are gone, so I don't know what happened. What else can I do? My initial joy of unraid is starting to fade fast. I had so many issues, so many crashes, disks spinning all night even with 0 zero devices on the network (router / switch gets turned off during night, still the server continues to run) and last but not least I had hoped that the power consumption would decrease compared to my old Windows Raid 5 Server - well during Parity sync is takes 70W now instead of the 50W during a Raid 5 rebuild. That's 20W more just for it being Linux and not Windows. you see I'm kinda pissed off at the moment.
April 2, 201412 yr Author and it crashed again, at around 75%...PC is running but it seems to have shutdown all HDDs since power consumption dropped from 70W to 50W. network is not responding anymore, keyboard not responding as well. Computer is literally dead. This time I installed screen and had it tail -f /var/log/syslog > /boot/mylog so that I could actually see the log. Server died without even an entry to the syslog. Great, I'm running a Pro License and can't even get the initial Parity Sync to work, so that means I'm running just a regular Linux server with a bunch of disks without any parity.
April 2, 201412 yr The writes are not being synced before the crash. See here: http://lime-technology.com/forum/index.php?topic=9880.0 Leave a telnet session open.
April 3, 201412 yr Author I didn't want to keep another PC running (usually they are set to sleep automatically too), that's why I used screen to copy the output of tail -f to the sd card, but like I said it didn't show anything before the crash, except messages from the s3 plugin from dynamix. I finally managed to get the parity sync to complete while running unraid in safe mode - so I can only assume that dynamix is responsible for the crashes. But that doesn't help me a lot because I need most of the plugins from dynamix - that's the whole reason I chose unraid over something like FreeNAS. Because I want Email Notifications, SMART monitoring and most important, s3 sleep. If I can't use those plugins unRaid is essentially worthless to me. damn.
April 3, 201412 yr Lets see a full SYSLOG showing the entire startup sequence. Based on your other thread for Dynamix bugs, I suspect a conflict of plugins or dependencies. http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog
April 3, 201412 yr network is not responding anymore, keyboard not responding as well. Computer is literally dead. tamowish I'm sorry to hear that. Start a new thread for your issue so we don't confuse your problem with Falc410's That said, you say the network and keyboard are both dead. Is it just unRAID that's dead? If its just the unRAID server then do this: 1. Turn off unRAID for a full minute (on the power switch). 2. While you're waiting, put the flash drive in a PC or Mac and run chkdsk or Disk Utility on it to fix any file corruption. 3. turn unRAID back on...and from your attached display and key board, select 'SAFE MODE' right after the power comes on.
April 3, 201412 yr tamowish is a Spambot, just copied a line from a previous post. Did the same on another thread. I've reported it.
April 3, 201412 yr Author Well I posted it in the Dynamix Thread now, since it's likely that one of the plugins or slackware packages is the cause of the crashes. See here: http://lime-technology.com/forum/index.php?topic=30939.msg300217#msg300217
April 3, 201412 yr tamowish is a Spambot, just copied a line from a previous post. Did the same on another thread. I've reported it. Fool me once...
Archived
This topic is now archived and is closed to further replies.