DaleWilliams

So unRAID has to be running...you can't get there from the Boot up screen. But after you've built your array, you'll see the flash identified on the main GUI screen...its just another 'drive'. In unRAID a 'drive share' is done from the main GUI page. click on the drive, then on SMB Security Settings, set the option to 'Export = Yes' then to access it from your PC, something like "smb://192.168.1.50/flash". or "smb://192.168.1.50/disk1" (that's my Mac 'Connect to Server...' string. Use your tower address. On a PC, i think 'flash' will show up in the network drop down on the left of windows explorer window.) I'm not sure--and have never tried-- 'starting the array' with no hard drives at all...which sounds like your situation..I've no idea what would happen. Its possible that it works, and you can then, from your PC, browse to 'tower'. LOL Be sure to copy your Flash to your PC before you try this! (actually, I keep a backup copy of my flash before every time I make any big change. (Like adding a new plug-in.) That way I can always and easily back out and revert to the prior flash version.

If 'md4' is physically in the array, and you just want to step through the files, itimpi's correct. In unRAID a 'drive share' is done from the main GUI page. click on the drive, then on SMB Security Settings, set the option to 'Export = Yes' then to access it from your PC, something like "smb://192.168.1.50/disk4". (that's my Mac 'Connect to Server...' string. Use your tower address. On a PC, i think 'disk4' will show up in the network drop down on the left of windows explorer window.) ummm...but then I got to thinking about your question...and I realize I don't really quite understand where you're at. You asked, 'Should I put the old md4 back into the array...' and 'manually check the contents of md4'... If you have a drive physically OUTSIDE OF THE ARRAY and you just want to see what's on it, you can mount it with a regular PC...you just need the Reiserfs driver loaded on the PC. BE CAREFUL TO NOT WRITE TO THE DISK...if you write to it, you'll destroy any hopes of using that disk as part of a parity recovery operation.

Memtest would be good to run...and I believe it will run without any drives. Installing the flash INSIDE the box is my goal, but after a year, mine still sticks out the back. So I have to tell you my own experience...I'm a neophyte with Linux. The whole 'telnet in' to the unraid to work on the flash drive was a bit strange at first. Out of frustration (because I wasn't really sure where I was at in the file structure), for the first month or so, I'd shut down unRaid, pull the flash, plug it into my Mac and install stuff. (plugins, scripts, etc.) Setting up the Flash as a shared network device didn't occur to me until later. Now it seems obvious, I suppose. I'm past that now...and could probably move the flash inside. Watching the forums, though, I see frequent instances where the flash needs to be removed and plugged into a PC for chkdsk fixes. (Mac uses Disk Utility). This is often after a bad shutdown, such as pushing the panic power off button, or a power failure. And so, since opening my case is a pain, I'll probably continue to let the flash stick out the back. Your mileage and comfort may vary.

I don't know that it was causing the shutdown issue, but it definitely was causing the web gui reload syslog spam. Any program that keeps a file open on the array will cause a shutdown issue. Theoretically plugins should monitor requests to stop the array and nicely terminate so the array can shut down, but that doesn't always work well when the array is healthy, so who knows how they will react when the array is having issues. I wouldn't necessarily throw dynamix under the bus, but you need to read the entire dynamix thread to understand the progression of things. I'm pretty sure the constant reload issue was discussed in the main thread, there is a setting to revert to manual refresh like the stock gui. +1 Dynamix (by default) continually updates page status...which is usually the behavior people want. That can be turned off in settings.

They are user contributed add-ons... unMenu is certainly not on the flash. While Tom likes the preclear script, I'd be very surprised if its on the flash. I'd go one step at a time. Get the stock unRAID up and running, that way if there are any hardware issues, etc. they can be sorted out. Then go out for the add-ons. If you're starting your first unRAID server, preclear isn't really required...it's a big help later if you want to ADD or REPLACE a drive to your existing array. If you're just starting up, the value in preclear is that it will 'stress test' the drives and can help spot potential problems.

version 5 does not ship with openssl so there is no vulnerability in stock unRAID. if you are installing plugins that use openssl you will need to get an updated version of the plugin to correct the issue. Oh, well, Heck! Sure enough...3 versions of openssl are in /packages. Never even thought to look... Thanks for the heads up, everyone

So I've seen those multiple 'plex servers'. Typically, while playing around on my Mac, I'd accidentally (well on purpose at the time, but didn't realize what would happen.)...I'd accidentally start the Plex Media Server on my Mac. This would then broadcast its presence on the network, and behold! Roku saw duplicate Plex servers, and movies, etc. The solution, of course, was to shut down all the Plex servers except the one running on unRAID. (Its been awhile, but if I recall, the PMS on the Mac would also auto-start on boot...so it took me a bit of fooling around before I figured out how to clean up after my play session.) Now I'm careful to run Plex as a viewer either just from a browser or from the Plex App (where I'm careful not to start the server. On my unRAID I have Plex in only the following two places in my Flash Drive: flash_root\config\plugins\plexmediaserver (this is a folder full of stuff) flash_root\extra\PlexMediaServer-0.9.8.18.290-11b7fdd-unRAID.txz (your version may vary)

and then attach a full syslog: http://lime-technology.com/forum/index.php?topic=9880.0

+1

I can't believe how much I've learned here in the forums. And without doubt, this is the friendliest, most helpful board on the net. Count me in for two clicks o' the free coffee/beer button!

On unRAID you created a regular 'user' and then gave him permission for the SHARES that he can access? (all of the above in the unRAID web gui interface) Then you logged into 'unRAID' using the unRAID 'user' discussed above?

Look in your BIOS at startup of the machine...that's easiest and where you'd have to change it, anyway.

at Line 1889: at which point your APCUPSD has started the shutdown sequence. There follow 5000 lines of SMART Reports, all PIDs are stopped and killed and the array successfully stops. Is your UPS plugged into a Timer that's shutting off at 2AM? When you go to bed, does turning off the light to the room with the unRAID array also turn off the power to the UPS?

Probably. I see you've been posting to individual boards...the Motheboards forum, the Hard Drives and Controllers forum, etc. If I understand where you're at: You've bought an ASrock mobo and it has the LSI SAS 3008 controller chip. You can see your drives in the BIOS, but not in unRAID.

LOL Sorry, we are so used to just jumping into debug mode! So I don't understand the exact nature of the under-the-hood constraint, but I believe it goes something like this: UnRAID is a 'commercial' product. The selling of KEYS hooked to specific USB sticks is how Tom makes the money needed to keep development going. And the security of the source code is paramount to maintaining his control of the software. The core of unRAID are the two programs bzroot and bzimage. A mechanism exists to allow 'plugins', and 'user defined GUI's' but the two core files are untouchable. Even the user defined GUI's work by querying the built-in web interface. In the 'Kernel' of unRAID, the web server used to serve up the standard GUI content is something called 'emHTTP'. 'Event Machine HTTP'. The use of that server is integral to maintaining the architectural integrity of the product...at least through v.5. There is a problem with emHTTP as implemented in *nix. It was never designed to NOT be running. Therefore, there was no need to provide and there is no way to 'Restart' it if it stops. That 'bug' is buried in the design of emHTTP and is beyond the control of any of us. As you've already discovered, this is a source of great anguish and frequent discussion on the forums. People ARE frustrated, and My understanding is that the Version 6 roadmap includes a replacement for emHTTP. (Full disclosure: I don't *know* any of the above for a proven fact. Its my interpretation from all that I've read on the forums and some side discussions. I'm not in touch with Tom, and don't speak for him.) Where I'm wrong, or I've made sh*t up from whole cloth, someone will correct me in the posts that follow below:

Do you use one of the add-on web gui interfaces? (the official extended GUI, Simple Features, unMENU, DYNAMIX, etc.) Post a complete syslog so we can see what's happening.

Your unraid shouldn't be accessing the external network. Your new service works like this: A cable comes into the office...on the end is a ROUTER that sits between the outside world and the devices in your office. FROM THE POINT OF VIEW OF THE DEVICES IN YOUR OFFICE: That router's address is either 192.168.1.1 or 192.16.1.2 (might be 10.10.10.1, also). That number is important because its how unRAID finds the router. The IP numbers to the outside world are NOT IMPORTANT to unRAID. Its the job of the Router to translate between internal and external addresses. Therefore, you should not change anything in your unRAID--except maybe the router's IP address--...it probably will work fine. Now...the underlined sentence above points out that the router between the inner and outer networks may have different IP numbers if you've moved. THIS NUMBER is determined (typically) by your choice of internet provider. You may need to update your unRAID network.cfg if you've changed providers. Here's an example my network.cfg: In BOLD is the only thing that should need to be changed and then, only *IF* the external/internal router has a new 'Gateway' address. Having said all that, This is of course, the Internet, so there are-of course-some weird cases. if the above doesn't work, post the contents of your network.cfg file from your flash drive. (its in the config folder)

Tell us more. Attach a complete syslog. http://lime-technology.com/forum/index.php?topic=9880.0 And what version were you using prior to the upgrade to 5.0.5? Was it an earlier 5.0.x a 5.0RC or 4.7 and earlier?

See here: http://lime-technology.com/forum/index.php?topic=28927.msg279478#msg279478 Simple Features COMPLETE Uninstall Then install Dynamix. There's a page of plugins fully supported by Dynamix builtin to the interface. You can add "CONTROL PANEL IKOSA" PlugIn Manager for an added page of 'managed' plug-ins for more capabilities. My "Control Panel" currently shows available AirVideo, Transmission, and two flavors of mySQL. Plex and Plex Updater are installed like normal (and then show up nicely in Dynamix). I always recommend backing up your flash to your PC frequently as you go along. That's a lot of changes and you may want to back up a step or two if something glitches. Also, take a SCREENSHOT of your current drive assignments showing DRIVE SERIAL NUMBERS (as shown on the WebGUI page.) IN particular, if something goes wrong, you want to be positive you know which drive is CACHE and which is PARITY....all others are data.

Its possible. But don't. That's likely to add more complications, and make the issue more difficult to resolve. Give folks a chance to read the syslog. This started when you opened the box to do maintenance. Odds are that you've knocked a cable loose. (power or SATA)... Powerdown cleanly and double check all connections. If you don't use them, this is a good time to get some LOCKING SATA cables. Make sure you've not wired two SATA cables together to make your box look 'neater'. SATA cables should be random like spaghetti! [Edit: Sorry, I have to go to work, but I quickly scanned your log. As you know you have problems...DO NOT change up the disks until you hear back from someone with time to read and interpret all the errors in your SYSLOG. if the box is still open, powerdown as cleanly as you can and check the cable connections as suggested, but DO NOT swap or remove disks.

cannot STAT A question to someone more knowledgeable on linux naming conventions: Could this be a problem with 'spaces' in the user share names? 'mnt/user/classic movies' instead of 'mnt/user/classic_movies'? 'mnt/user/All Music' instead of 'mnt/user/All_Music'?

POWERDOWN seems to be the standard for a clean shutdown. (search forums if you don't have it installed. I believe its also included as part of DYNAMIX, too.) It attempts to shutdown cleanly by ending all running processes, plugins, etc., and then dismounting the disks and shutting down power, etc... However, I seem to recall even it has trouble stopping some processes. Crashplan might very well be one of the ill-behaved that has to be stopped manually. You might search the forums for a discussion about stopping crashplan cleanly.

I vote with the smart guys above. Ignore split level. YOU"LL KNOW LATER if its a problem, and it can be easily fixed then. Otherwise, its a setting that helps in certain situations, but can otherwise be ignored. Same with INCLUDE EXCLUDE. I've found only rare examples where INCLUDE /EXCLUDE really matter. (in my case, I use MAC Time MAchine, and to work properly all time machine data MUST be INCLUDEd on One Physical Disk.)

I'd start a new thread. It sounds like you've got a slightly different problem. Add a reference link back to this post if you like. SYSLOG: http://lime-technology.com/forum/index.php?topic=9880.0

WDC_WD30EZRX-00MMMB0_WD-WMAWZ0124201 size: 2930266532 WDC_WD30EZRX-00MMMB0_WD-WMAWZ0117859 size: 2930266532 The above two disks are reporting many READ errors. I'd double check that SATA cables and POWER are plugged in properly. Then run a LONG SMART TEST and report back.