DaleWilliams

Glad to hear you're making progress. I think you're the first on the forums to come across this behavior....and a solution, too! But you didn't answer the real question, "Why does every wedding on GOT end with a bunch of dead people?"

Yeah....sorry you ran out of time. In July, you'll want still want to run chkdsk on the flash drive.

Its not clear from the log why you are crashing. The crash error doesn't show in the log. Try this: 1. put your FLASH drive in a PC and run chkdsk on it. (The log shows an unclean shutdown...and that often corrupts the flash drive) 2. Restart unRAID and run MEMTEST overnight. (Crashing for no reason is often a RAM memory problem.) 3. The Parity Check runs automatically when you start unRAID with after an unclean shutdown. (See #1) What the log shows is that there ARE parity errors. I would run Reiserfsck --check on EACH data drive (NOT on the parity drive). If Reiserfsck reports any errors on your data disks report back here. If Reiserfsck says your data is okay, then go ahead and run a correcting parity check. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

Are you saying I should change the unRaid Server name (Brunnhilde) to the static ip? Both PCs and MACs have a file called 'hosts' that maps names to IP addresses. Its 'hidden' in that users aren't encouraged to play with it. On my Mac I have THIS installed which adds a Preference Pane allowing easy editing: http://www.macupdate.com/app/mac/40003/hosts and here's a snapshot of what my Hosts file looks like (using the Pref Pane interface): The Hosts file is read FIRST before DNS lookups over the network...

You did a Hard Reboot! try: shutdown pull the flash drive Pop the flash in a PC (mac) run chkdsk (disk utility) put the flash back in unRAID boot unraid Hurry! The movers are coming! Be sure to shutdown properly before packing it up!

Another possibility might be to edit the HOSTS file on each of your PCs/MACs. Not positive how OpenDNS reacts to this...but HOSTS should be read first.

Ooo... I should have been more thoughtful...I too quickly copied and pasted from the first post.

Chkdsk doesn't give a lot of feedback when it repairs stuff. Your syslog was complaining about your flash drive. Glad you're back to running...and I'll keep my fingers crossed for you.

From the log, clearly your movies and PLEX data are on a disk that needs repair. run: reiserfsck --rebuild-tree /dev/sdb1 (Be sure that's the right disk...if you restart unRAID, the disk assignments may change). 1. As a check, you might want to run: reiserfsck --check /dev/sdXX on all your data disks (not Parity...there is no file system on Parity) and replace XX with the disks. 2. Check your PLUGIN versions...make sure you're running plugins that are the latest AND are the Version 6 compatible versions.

It looks like unRAID doesn't finish loading. The log just stops before it even gets to your plugins. I'd do 2 things: 1. stop unRAID as best you can...put the flash in your PC and run chkdsk ('disk utility' on a Mac). 2. #1 might fix the problem, but I'd also go ahead and copy onto the flash clean copies of bzimage and bzroot from the download of 5.0.5. http://lime-technology.com/download/ You may want to make a list of the plugins you have installed...if the above doesn't work, a clean install (save your key!) may be the next step.

Syslog, please: http://lime-technology.com/forum/index.php?topic=9880.0

*** I was reading this thread from the start, just to see what was going on... This may have been covered earlier and I just missed it or don't see it, but: Have you checked the BIOS of your unRAID server? To make sure ALL your harddrives are set up for AHCI? (also called SATA/AHCI in some BIOS) If not set, unRAID will still work, but disk read/write will be very slow.

You can remove the advanced gui by installing Dynamix (which removes it automatically) Dynamix is the 'successor' to SimpleFeatures and includes much of the 'advanced GUI' functionality.

There's some debate about this. As a 'boots and suspenders' type, I run a non-correcting and if there are errors decide what to do. (and that's always been to 'correct'). For that reason, others advocate just going straight to the correcting parity check. I believe there are RARE cases when parity correction is not appropriate. But very very very rare...hence the idea of going ahead and running a correcting parity check. Sorry..I realize that's not much help!

Did you search the forums for UPS sizing? If there's nothing there...and I don't recall seeing anything, then I suggest you post this as a new thread....I've seen several ways of 'calculating' the requirements, PLUS, depending upon how the UPS fail-signal-utility is setup, it may be necessary to keep the ROUTERS and SWITCHES up (for the PC with the UPS signal to issue the powerdowns to the other devices, for example.) Could be a thread of general interest.

A low level format probably wiped the drive completely clean. And 'low level format' means different things to different folks. What exact command did you give?

SimpleFeatures is NOT compatible with unRAID version 5.0.x You might try uninstalling it..see here: http://lime-technology.com/forum/index.php?topic=28927.msg279478#msg279478 Try using Dynamix instead...its similar to SF and is well supported.

No...can't restart it. The builtin GUI uses something called emHTTP. However, it was never 'designed' to fail, and therefore has no way to be restarted. Its hard to say why it crashed without a syslog. This is on the roadmap to be changed in version 6 (emHTTP goes away). All the GUI's (unMENU, DYNAMIX, etc.) rely upon the builtin web interface...so there's no good fix. As long as unMENU is working for you, keep on...when you restart, the default should come back up...if not, post the syslog.

release candidates are pre 5.0.0 If you jumped from 5RC1-5RC12-5.05, you skipped some 'final' releases. (5.0.1,5.0.2, etc.) Those 'point releases' had minor but important tweaks. (they were important to you if you had one of the affected configurations!

About that line in your 'GO' script... Is that there for a particular reason? I'm not sure that's actually the cause of your problem, but it sure has everyone confused! If there's no unique-to-you need, can you delete it? Also, there's something else odd in your syslog. (Sorry, I have to get to work and can't dig further), but it LOOKS like your initial system boot finds FOUR drives and mounts them, but then later unRAID finds FIVE drives. You might check your BIOS to see that all your drives are properly defined. The SATA Cable check was a good idea...you might also try swapping SATA ports on the motherboard to see if the problem disk changes (indicating the port on the MB is at fault). And how about power? Are the power connectors seated properly on all the drives? Then you have a ton of 'developer' oriented plugins...I'm not as familiar with which versions of those are current, but if you boot unRAID in 'SAFE MODE', that would allow you to fix the disk issues without a lot of plugins getting in the way.

Just a guess at the problem, but: In later install instructions, for later versions of unRAID, there is a note about being sure the BOOT partition on the Flash is large enough. On the current distributions, there's even a 'MAKE BOOTABLE' script to help you do that. See the 'Readme.txt' included in the current release download. http://lime-technology.com/forum/index.php?topic=31472.0

Make sure you ran Reiserfsck correctly. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems If you're not sure, post the SYNTAX of the Reiserfsck command you're trying. Also post a full syslog: http://lime-technology.com/forum/index.php?topic=9880.0

I run Dynamix and control-panel-ikusa together. They work fine. ...planning to add unMenu as well...just been to busy lately. as long as you're using the latest versions of these, they seem to be compatible with 5.0.3 and above.

[me=DaleWilliams]bookmarks this and adds it to his folder of 'unRAID Best Practices'. [/me] Excellent step-by-step directions!

Oh! My bad. I was under the [mistaken] impression that powerdown tried to work that way... [me=DaleWilliams]bookmarks Joe. L's helpful links.[/me]